Update Requirements are usually written follow a standard:
CSI MasterFormat
CAWS
Uniclass
Other/ Unknown
Requirements will be organize under a Word document where bullet points will define the structure of the requirements.
Same if they are written in an Excel document, each row can be a section OR each level are define using column
Once we receive those requirements, the documents are stored in ProjectWise.
Then using and import tool we can import into in the Requirements module in the same logic we import 3D model in an Imodel.
Once the requirement document have been digest by the module, it will allow the project to manage requirements in garanular way, like linking to a disciline to a zone or sub-zone etc.....
If the original document is revise, eac en every entry in the requirements management modue relate to the update document, will be flag for review and will Kick the change mamahement process
Luc Poulin
More info
https://www.youtube.com/watch?v=vE3nT1SmPMU&t=159s
Update
Requirements are usually written follow a standard:
CSI MasterFormat
CAWS
Uniclass
Other/ Unknown
Requirements will be organize under a Word document where bullet points will define the structure of the requirements.
Same if they are written in an Excel document, each row can be a section OR each level are define using column
Once we receive those requirements, the documents are stored in ProjectWise.
Then using and import tool we can import into in the Requirements module in the same logic we import 3D model in an Imodel.
Once the requirement document have been digest by the module, it will allow the project to manage requirements in garanular way, like linking to a disciline to a zone or sub-zone etc.....
If the original document is revise, eac en every entry in the requirements management modue relate to the update document, will be flag for review and will Kick the change mamahement process
This one is date back, but the concept is still actual
https://youtu.be/P4oh0Nd-ewo?si=QrMcVTaGR1-eTqNy&t=186