How Do I Connect Two RIB Environments?

You connect two RIB environments with a CDE integration that moves models, documents and cost metadata from one organisation's RIB environment into another's, and returns updates on the reverse path. CDE Sync™ links both through dedicated service accounts, maps fields between them and logs every transfer.

Why two RIB environments need to share

RIB's tools, including RIB 4.0 and iTWO, are used for BIM-integrated cost planning, estimating and project control. Cost consultants, contractors and some owners all use them, so a project can involve more than one RIB environment. A client's cost manager may hold the cost plan in one, while the contractor's estimators build tender and delivery estimates in another.

When the two need the same models and documents, the usual method is exporting, renaming and importing by hand. Models arrive without the metadata the cost team relies on, revisions get confused, and estimators spend time checking whether they are pricing the latest design instead of pricing it.

What carries across between RIB environments

CDE Sync™ moves models and documents with their version history and preserves workflow state, so nothing is flattened or overwritten in transit. Metadata, including the fields cost teams use to link quantities to the model, is mapped to the receiving environment's schema. Responses can return on the reverse path. Every transfer is logged, which gives both organisations a clear record of what was priced and when.

The RIB integration page describes the connector in more detail.

How to connect two RIB environments, step by step

  • Agree between both organisations which models and documents should move, and in which direction.

  • Compare the two field configurations and agree how each field maps.

  • Arrange a RIB service account in each environment with your RIB administrators.

  • Connect both environments in the CDE Sync™ wizard and choose locations on each side.

  • Map fields and set the schedule.

  • Run a test transfer, check it with both cost teams, then switch on the full flow.

Cost plans, estimates and design changes

The value of this connection shows up when design changes. Each time a model is updated, the cost plan and the estimate need to follow. If one organisation receives the new model days after the other, their numbers drift apart and the conversation about cost turns into a conversation about which model is right. Keeping both environments on the same revision means discussions focus on the numbers themselves.

It also supports a cleaner audit trail. Because every transfer is logged, both organisations can show exactly which model revision a cost plan or estimate was based on. That matters for variations, value engineering and later disputes. Our article on keeping a single source of truth across CDEs explains why that traceability matters.

Field mapping needs attention at the start. Cost codes, work breakdown structures and classification systems often differ between a consultant and a contractor. Writing the translation into the mapping means each side sees information in its own structure, and estimators do not have to re-code quantities by hand.

Many teams also use the connection for supporting documents, such as specifications and schedules, that drive pricing. Moving them alongside the models means estimators have the full context of each design issue, not just the geometry.

Once running, the connection needs little attention. Anything that fails a mapping rule is reported for a person to fix. Because CDE Sync™ is configured through a wizard, mappings can change as the project moves through stages.

Security and data residency

CDE Sync™ streams files directly between the two environments without storing them, encrypts data in transit and processes it in the Azure region you choose, which suits European, UK and Australian residency requirements. Each organisation controls its own service account. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.

RIB to RIB and the Utopiaverse™

A RIB to RIB connection is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Sync™ keeps both environments aligned, CDE Backup™ keeps an independent copy in your own Azure, CDE Migrate™ handles moves onto or off RIB, and CDE Archive™ captures the record at completion. AI Insights searches models, documents and cost content together, with cited answers. See also How Do I Connect Autodesk Forma and RIB? and How Do I Connect Bentley ProjectWise and RIB?

See two RIB environments connected in the monthly live demo, or talk to the team about your project.

Previous
Previous

How Can I Enable AI to Read Oracle Aconex?

Next
Next

How Do I Connect Two Procore Accounts?