Specifications are very important on most construction projects. If everyone works to the mandated specifications, then project standards are maintained. There may be more than one consultant that needs to work to the same specification. There may even be multiple projects on which the same specifications are of interest.

It would therefore make sense that the specifications should be generally accessible in a project that is created specifically to host them.

There is also a case to be made that item like the corporate BIM Protocol and other generic documentations be established as specifications. Clearly the BIM Execution Plan is specific to a project and needs to be developed there, but any generic reference can be in the Specifications Project created for this purpose. If you update them in one place, then everybody works to the same specification.

Create the Specification as usual. Add the files and set the version. Enter the specification details. Use groups to subdivide the specification. If you need to delete one of the standards, then you can do so by deleting the version it was loaded under.

Deleting a version deletes the files but leaves a record of the transaction in the publish logs.

I created a custom role called Prj.Specifications as the hub administrator and then added that role to members I added to the specifications project. These members can now create specifications.

Those that need to view the specifications can do so under the built-in role, Everyone. This makes the administration of the project easy.

Here is the result available to everyone that is invited.

If you need help adopting the AEC Collection or the Autodesk Construction Cloud in your practice or you are looking to invest in hardware, please contact Micrographics so that we may be of assistance.