An interesting question came my way the other day regarding barcodes for Revit elements within the build platform. Now the identification of elements on a building site could originate from various sources. For instance, do you rely on the bar code of the manufacturer or from within a supplier within the supply chain? Alternatively, do you choose to identify the element from within the modeling software like Revit? Within database programming the identification of elements by the ID is common and a short ID within a Revit project is generally acceptable. However, when large projects are considered with many models or many databases then short ID will not suffice and in general a unique global identifier or GUID is used for identification purposes. The above discussion holds for Revit elements which both have a short ID and GUID for identification within Revit. You can use both to select elements using the ID selector in Revit. The GUID is exposed using Dynamo.
If we wanted the property of an element within a Revit model to be mapped onto the Autodesk construction cloud Build platform then we would need to read the GUID of the elements and write the GUID to a property that we create for that Revit element. The best way to do this is to use a shared instance parameter. Whoever creates the shared instance text parameter should also manage the process across different models on the project. Consistency is important on a project with regards to shared parameters.
Shown below is the definition of the shared instance parameter.
Shown below is the creation of the project parameter note that you would have to apply the parameter across all the elements that you would like to create as assets within the ACC build platform.
The Dynamo graph is a simple one that could be adjusted to service multiple categories at once. In my case I will just choose the categories 1 by 1 and run the graph. 1st, the category of element is chosen. Then every element of that category is selected.
The global unique identifier for the element is read and then written to the shared instance parameter.
Next the file must be uploaded onto the Autodesk construction cloud platform. For the design team an ACC Docs or ACC Collaborate Pro license will be sufficient since the ACC Docs capability is shared across the ACC platforms. When we consider the creation of assets, I would suggest that the stage complete model might be best suited for creating the assets. Such a model would have been approved for purpose and would not be subject to frequent change.
That said, the assets from models can be configured to update certain linked parameters. I would suggest that managing asset updates from Revit into the cloud is not the ideal situation. The ACC Build platform serves as the CDE and the project information model is developed as such. If the information were to be written back into Revit the Autodesk Platform Services would have to be used to extract the information from the cloud. Since the GUID of the Revit elements will be common, one can then identify the elements and write the information back to the Revit model using Dynamo.
When you manage the Assets in Build, you will notice that you can create a custom status set before converting model elements to assets. Whatever purpose you could envision to create such a status set would have to apply exclusively to the elements that you select for that Status Set to apply to since element categories are mutually exclusive. I would suggest having a look at the Default Status Set and adopting it until such a time comes that a compelling reason exists to create a custom Status Set.
Next, we must create categories and subcategories to extract specific elements from the model. Each category can subscribe to only one Status Set and the subcategories inherit this Status Set.
Systems behave in a similar way and act as containers for elements that combine into a large whole.
After loading the model, we then use the categories to extract the model elements, after which we map parameters across, optionally pushing their values from the Revit model to the Cloud. In other words, if the Revit information changes, this will change the cloud information. Mapping the Revit level unique identity onto the bar code of the element within the Autodesk ACC Build module is an easy way to generate a QR code for identification. Were you to print this QR code onto a sticker and paste it onto a building element, you would easily be able to locate that in the model from which you created the asset.
The creation of assets that are visible graphically in a model makes them easy to manage. Not only can you assign the status of the asset, but you can also attach references to, for instance, forms. You may have the quality assurance form as a checklist for whomever it is installing the asset. Then you may have a form for quality checking (the successful conclusion of which will ensure the payment of the subcontractor). Any exceptions can be managed through the creation of issues, the taking of photos videos and assigning it to the appropriate parties.
Communicating on the ACC Build platform is preferable over a disconnected combination of telephone calls, WhatsApp messages, emails and a variety of other mediums because everything is centralized and recorded. There should therefore be no reason for substandard performance on the project.
There is quite a lot of work that goes into setting up a project on a platform like ACC Build and ensuring compliance. Adoption also requires industry (including the subcontractors) to buy into the technology for it to be utilized to its full extent. Instead of seeing learning curve as an impediment to the adoption of the digital age it should be seen as an opportunity for research and development and adoption should it prove profitable.
At Micrographics, we maintain that it would be imprudent to subject an entire organization to suddenly adopt new technologies (there is invariably a learning curve and an associated productivity drop). Instead, we advise that you identify a specific group to run with the technology on a pilot project. If the pilot is successful and the technology proves useful and profitable then you could consider transforming the rest of your organization to achieve a similar result.
This is the perfect time for those with human resources and a research and development budget to invest in the digital future. Do not miss your opportunity, do so. Our technical consultants often advise on the technology to be used on projects and can evaluate your employees as to their suitability to fulfill their roles on the pilot project. Similarly, we are able also make a call on the suitability of your hardware and other relevant devices. Also remember that it isn’t necessary to adopt every capability of a solution for it to be financially profitable. Begin with easily achieved goals that can give you the best result and you may find that the software and hardware pay for itself. A classical example of this is the saving of around 20% on the construction cost just by modeling in 3D and clash detecting.
If you need help adopting the AEC Collection or the Autodesk Construction Cloud in your practice or if you are looking to invest in hardware, please contact Micrographics so that we may be of assistance.
