Specifications

Specifications is commonly refer to as Requirement Management.

Which allow importing any documents (PDF, Word, excel etc...) that is refer as the voice of the customer ( what the customer waants)

Requirements also refer to any Govermement regulation from differet level ( Federal, State or city)

Requirements also refer to industry standard, like Building code or NHAST, ISO etc...

Also Bentley already have ComplyPRO to manage requirement ( Specifictions)

As such the specificatin we see under BIC should allow beter granularity when importing Specifications into a project.

We should be able to brakedown the document in page, in paragraphe, in phrase

Once break down in the simplest requirement element. each element will need to be qualify using attribute.

Each element will then be save in it's own hierarhy so the quality team can start manage the requirements and the changement management process.

The idea to allow create issue to create a requirements hierachy is good but tedious and manual process ( assuimng it was one of the intent :-) )


Once the requirements is approve and release, they will be accessible to project participant to be refert to, in term or design or construction or inspection/handover. ( we can then create the inspection plan)

Qualifying a requirement element

Example Number, should be like a Document Code, a Specification Code and the user should be guide in creaing that Number. Which in turn will make this a unique number to help track individual requirement.

Discipline, same here shoud be part of the Number or Specification Code

So Number-Discipline-Section-Division should form a unique Specification Code

Update

At a later time if we import a new spécification sheet PDF ( it could be as well a word or Excel sheet)

The system will say, this specification element already exist please conduct a review to either revise with the new informaiton or reject the new specification as it already exist.

AI
Since we have AI being integrated, we could have AI use to review all the requirement documents being submit to the project and break it down etc.....

Version
if we drop the same document, the system does not seems to recognize a previous one was drop and the new document will be an update of an existing requiement

Share specifications

Specifications should be a common module between, Project, Build and Assetwise