Manage BIM information requirements across projects
IDS Compass helps BIM and information management teams organise the specifications behind a model delivery. Build reusable requirement libraries, apply them to a project and manage the specification sets for its phases and releases.
Use a clear requirement structure to make the team's expectations easier to explain, review and maintain.
Request a demo — beta access includes a walkthrough with our team.
Give recurring requirements an identifiable starting point
A team working on several projects may request similar information many times. Without a maintained starting point, small differences in names, assumptions and descriptions can become difficult to explain.
Organise reusable specifications by purpose. Record the intended scope, the information expected and any project assumptions that need review before reuse. Give the library an owner so that questions have somewhere to go.
In IDS Compass, reusable libraries provide a place to organise those specifications alongside project work.
Match the requirement to the delivery stage
Consider a hypothetical estates programme delivering several teaching buildings. An early review might need agreed space-use information. A later delivery might need additional asset details for the receiving team.
The people defining the requirements should decide when each item is needed and who will supply it. Organising the specification sets by project phase makes that decision visible in the team's working structure.
Start with a small delivery in the programme. Review what the receiving team actually uses, then expand the library where reuse is justified.
Make requirement changes clear
When a project requirement changes, identify the release in which the change takes effect. Explain its purpose and the delivery to which it applies. Ensure the producing team can distinguish the current instruction from a previous issue.
IDS Compass organises specifications in the context of projects and releases. Use that structure alongside the project's agreed communication and review process.
We already specify the relevant standards
Start by examining what the team still has to decide for a particular delivery. What information will the receiving team use? On which objects? At which stage? What will happen if it is absent?
Those questions reveal whether there is a practical specification task. Work with the responsible designers and information managers to turn the relevant, agreed information expectations into checkable requirements where appropriate.
The client can describe the intended outcome while a specialist prepares the detailed specification. The responsibility split should be agreed by the project team.
Try a focused pilot
Choose one upcoming information delivery and a small set of requirements that matter to its recipient. Review the specifications, identify the release, and test them using the agreed checking workflow.
After the delivery, record which questions arose, which issues the check revealed and which requirements were useful. Use that evidence to decide what belongs in the reusable library and what remains project-specific.
Make BIM information requirements predictable.
Join the IDS Compass beta and organise your team's requirements around projects, phases and releases.
Private beta · free while in beta.