The Webinar has a duration of one hour, and consists of two main topics; a) dRofus Concept and Core functionality b) dRofus and modelconnection through buildingSMART
A video recording of the webinar is available. Click on the image below to view it online:
To save a local copy: right click this link and select “save target as” (86 MB)
During the one hour presentation, we experienced only one minor technical problem, when we showed the wrong(empty) screen of a Room Data Sheet report. Please excuse us for this.
In the Webinar, several questions came up :
1) Cutbooks or spec books - how are they created ? dRofus support document- and image attachment to all rooms and equipment articles in rooms through drag-and-drop. During procurement, when user-defined equipment are handled as individual occurences, it's common that all spec books, contracts etc. are attaced directly to the object.
2) How many buiding types do you have? Schools? kindergarden? dRofus is easily adjustable (by the dRofus-user themselves) to match different building types. The whole user interface is flexible, and when you do changes in a dialogue window (like a room data sheet setup), all reports are automatically adjusted. In this way, dRofus can rapidly be transformed to handle requirements to hospitals, operahouses, schools +++, in fact all building types.
3) Is there the ability for read only access to the system for project stakeholders/clients, so they can review progress? Yes - this is a common used feature. Those involved in the project with “administrator-rights” to dRofus, can give all users many different access levels to the system. In fact, if you, for instance, want to give an HVAC engineer access to change/update ONLY the RDS-fields that are relevant to him/her, he/she can be given write-access to these fields and read only to the rest of the system. (The log will anyway track all changes)
4) Someone has to key in the infromation? Could have been nice to have someting with some “meet” in. So the client will have to do it ?
Multi-users of dRofus are able to re-use a lot of information from project to project. They establish standard RDS's and equipment lists for different building types, and can through this do a lot of the programming in a new project already at start-up through use of these templates. dRofus is a system which can handle requirements and equipment, regardless of how complex or large the project is or how many people logged on at the same time, but yes - someone must type in the data
.
5) Does it have the ability to report out on the quantity of generic rooms against unique roooms?
Yes.
If anyone have additional questions about dRofus, please contact us. drofus@nosyko.no