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.
We review every request and aim to reply within two business days.
Request beta access. We review every request and aim to reply within two business days.
Start with a requirement your team already uses
Choose one recurring requirement, such as the fire rating needed for every door in a design delivery. Identify the relevant objects, the property to check, and the accepted value.
Save the reviewed specification by purpose. Record its scope and assumptions, and name the person responsible for questions or updates.
IDS Compass keeps reusable specifications beside project work so teams can start from an agreed requirement instead of rewriting it.
Match each requirement to a delivery stage
An early design review may need a space classification. A handover delivery may need a serial number and warranty date for every maintainable asset.
For each item, record when it is needed, which objects it applies to, and who must provide it. Grouping specifications by project phase makes those decisions visible.
Test a small set on the next delivery. Keep the requirements that support a real review or decision, then expand the library carefully.
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.
Turn standards into checkable project instructions
A standards reference alone does not identify the exact information needed for a delivery. The team must still decide which objects are in scope, what information is required, and what result is acceptable.
For example, replace a broad request for asset information with a clear instruction: every IfcPump in the handover model must include manufacturer, model number and serial number.
The client can define the intended outcome while an information manager prepares the detailed specification. Agree who reviews it and who answers delivery questions.
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.
We review every request and aim to reply within two business days.
Private beta · free while in beta.