OCBM
100%of quantities traceable to a source drawing.
Agents for takeoff, pricing, and consistency checks across drawing revisions and tender documents.
See the OCBM case studyCatch clashes before they reach the site.
Mirage's AI agents check your plan set across structure, architecture and MEP, and flag every place the drawings contradict each other, marked on the sheets it comes from.
For general contractors, EPC and MEP teams and heavy civil contractors. Works on PDF and DWG sheets, and IFC where a model exists.
Plan setTOWER-B_issue-B.pdf
- CheckedStructure, architecture and MEP on one grid
- IssueC-014: duct 600×400 crosses beam B-12 at C/2
RoutedC-014
MEP coordinator
Waiting for review, M-201 and S-201 attachedIn production at
35+
Deployments in production
5M+
Operational records processed
6
Countries with clients
Company-wide figures, across all Mirage clients: more than 30, in six countries. Six of the twelve companies named on this site are contractors or engineering groups.
01The problem
A coordination error is cheapest on paper.
Each discipline draws on its own sheets
A duct on the mechanical plan and a beam on the structural plan can take the same space, and nobody sees it before installation.
Revisions arrive faster than reviews
A change on one discipline's sheet is not carried to the others, and the conflict appears in the next issue.
Review time goes to searching
Checking one detail means opening five sheets and the specification, set by set, floor by floor.
What is found late becomes an RFI or a change order
Each one costs time on site and margin on the job, and some reach the client.
02How it works
From the issued set to closed issues.
One plan set, followed through the five stages. The agent reads, aligns and checks; a person decides what is a real issue.
Sheet M-201, structure S-201 overlaid
What the agent recordsStage 1 of 5
The plan set arrives
The issued set lands from your document platform or by email: architecture, structure, MEP and the specifications.
- Issue B, 148 sheetsPDF
- Architecture, structure, MEP
- Specifications, 2 volumes
Sheets are read and aligned
The agent reads each sheet, its grid, levels and references, and puts every discipline on the same grid.
- Grid A to E, 1 to 4 matchedS-201, A-201, M-201
- Level 2 at +4.20 on every sheet
- 2 detail references point to no sheetA-501
Conflicts are flagged
Where two disciplines claim the same space, or one shows what the other leaves out, the agent raises an issue with its location and its sheets.
- C-014: duct 600×400 crosses beam B-12C/2
- C-015: pipe DN100 through wall W-3, no openingD/3
- Other crossings on level 2: no conflict
A person reviews each issue
Each issue goes to whoever owns that discipline, with the sheets side by side. Nothing leaves until they decide.
- C-014 confirmed, RFI drafted for the designerMEP coordinator
- C-015 dismissed: opening shown on S-310Structural engineer
Issues are tracked to close-out
Confirmed issues go to your project platform and are checked again on the next revision of the set.
- RFI-087 issued in the project platformC-014
- Revision C: duct rerouted below the beam
RFI-087C-014 closed on revision CChecked
03What it checks
The checks your coordinators do by hand, on every sheet.
Checks are configured per deployment around the ones your team already does. The usual ones:
Clashes between disciplines
Ducts, pipes, cable trays and equipment against beams, columns, slabs and walls.
Openings and sleeves
Penetrations drawn on MEP sheets with no opening on the structural or architectural sheets.
Levels and dimensions
Heights, levels and dimensions that differ between plans, sections and elevations.
References and callouts
Detail, section and sheet references that point to nothing, or to the wrong sheet.
Schedules against plans
Doors, equipment and fixtures listed on a schedule and missing from the plans, or the reverse.
Drawings against specifications
A material, size or product on the drawing that the specification describes differently.
Mirage does not check drawings against building codes.
Every issue arrives with
- Its location and its sheetsGrid reference, level, and every sheet involved side by side, marked where the conflict is.
- A severity you setYour rules decide what is critical and what can wait, so a clash on a main beam comes before a missing tag.
- Its repeats groupedThe same conflict repeated on every floor is reviewed once, not forty times.
- A path to close-outSent to your project platform, Procore and Autodesk Construction Cloud among them, and checked again on the next revision.
04Who it is for
For the teams who pay when coordination fails.
General contractors
Find coordination issues at tender and preconstruction, while they are still questions and not site problems.
See general contractorsEPC and MEP contractors
Check your routes against structure and architecture before fabrication, and send each clash to the discipline that owns it.
See EPC and MEPHeavy civil contractors
Check the drawings of several designers against each other before work starts on site.
See heavy civil
05In production
Mirage already reads construction drawings in production.
Clash detection is configured project by project. These are the drawing workflows running today, with their published results.
John Cockerill
80-90%less time spent on piping takeoff.
Isometric drawings turned into a material take-off in Excel, each line traceable to its drawing. Morocco operations.
See the John Cockerill case study06Deployment
Built with your team. Deployed on your projects.
Our forward deployed engineers sit with your coordinators. They see how your sets are checked today, configure the agent on your drawings and conventions, then run it in production with your team deciding on each issue.
Observe
- Your team brings
- Time with the people who check the sets today, and a few of your drawing sets.
- What you get
- A system map: who does what, in which tool, with which exceptions
Map
- Your team brings
- Your checks, your conventions and severities, and who decides on each discipline.
- What you get
- The technical architecture: systems read and written, rules, approval points
Build
- Your team brings
- Access to your document and project platforms, through an API or file exchange.
- What you get
- A working agent, on your own data and in your own systems
Run
- Your team brings
- A person per discipline to decide on what the agent routes to them.
- What you get
- The operator interface: review queue, approvals, action history
Expand
- Your team brings
- The next check or the next project you want to hand over.
- What you get
- A production report: volumes, exceptions, corrections, and the next workflow
2Business hours to answer a request
1Week from the first meeting to a proof of concept on your drawings
4-6Weeks to the first workflow in production
Workflows that span several systems can take longer; they are scoped at the first meeting.
See how we deploy07Questions
Frequently asked questions
Most issued sets are 2D. The agent works on the sheets as they are, scanned or vector, with the specifications alongside.
Where a federated model and coordination meetings exist, they stay. Mirage checks what is actually issued, sheet by sheet, including the sheets that never made it into the model.
Mirage does not check drawings against building codes. It checks the set against itself and against its specifications.
Each issue is marked on the sheets involved and listed with its severity. Connections to the platform you use, Procore and Autodesk Construction Cloud among them, are built during deployment.
Mirage runs in your infrastructure, in your own cloud account, or hosted by Mirage. Data and processing stay in the environment you control, and access is set by role. Security
The proof of concept runs on a sample of your own drawings. The pilot puts one workflow into production with our engineers on site, from $10,000 to launch. Production is an annual subscription priced by volume, from $1,000 a month.
Which plan set should we check first?
Tell us about the project and the disciplines involved. We reply within two business hours, then send a written plan: which checks fit your sets, what a deployment involves, and the shortest path to production. No commitment.
Prefer to talk it through? Book a call