CONSTRUCTION INTELLIGENCE / MIDDLE EAST
AI construction software for contractors and EPC teams in the Middle East
Mirage reads drawings, BOQs, specifications, contracts and project records, then runs source-traceable workflows across tendering, engineering, procurement and delivery: quantity takeoff and MTO, design revisions, variations, claims and project controls.
Clients in Saudi Arabia and Egypt. Deployed in your infrastructure or your cloud.
On a megaproject, late drawings and design changes become variations and claims, and the evidence for each sits across Aconex, email and shared drives.
Start with one workflow, then extend it
Most teams start with takeoff, BOQ checks or tender analysis. Once Mirage knows your drawings, BOQ structure and systems, the same project data serves revisions, variations, claims and project controls.
Tendering and preconstruction
- Quantity takeoff
- Drawing packages measured across civil, structural, architectural and MEP disciplines, structured around your BOQ and cost codes, each quantity tied to its sheet and revision.
- BOQ review and reconciliation
- Drawings, specifications and the BOQ compared before submission: missing quantities, duplicated items, scope gaps, specification conflicts and unpriced requirements.
- Tender document analysis
- Drawings, specifications, conditions of contract and addenda read together: requirements, exclusions and commercial risks listed for clarification.
- Subcontractor bid comparison
- Quotations read in the format suppliers send them; scope, quantities, exclusions and prices compared side by side.
Engineering and MEP
- MTO and bill of materials
- Structured material take-offs and bills of materials from piping, electrical, structural and MEP drawings.
- Isometrics and P&IDs
- Isometrics, P&IDs and line lists read together, quantities and design data checked across the package.
- Drawing revision comparison
- Complete packages compared across revisions: what was added, removed or modified, and the quantity and scope impact.
- Electrical takeoff
- Device counts, conduit and cable runs and panel loads from the electrical set, each quantity traced to its sheet.
Variations, claims and commercial control
- Variation records
- Revised drawings and instructions tied back to the original scope: the quantities, BOQ items and specification clauses affected, and a traceable record of what changed and why.
- Claims documentation
- Drawings, correspondence, instructions, RFIs and revisions linked to the event behind a claim, with the dates the contract's notice periods run from. Contractual decisions stay with your team.
- Interim payment review
- Payment applications and subcontractor invoices checked against measured work, the contract and approved variations.
RFIs, submittals and document control
- RFIs and submittals
- Submittals checked against specifications and drawings, RFIs prepared from what the documents already say.
- Construction document search
- Drawings, specifications, BOQs, contracts, method statements, material approvals and minutes searchable, every answer with its document, page and revision.
Built around how the region contracts
- FIDIC
- Red, Yellow and Silver Book conditions and their particular conditions read as contracts: variation procedures, notice periods and the records each requires. Under the 1999 and 2017 editions, a contractor's claim starts with a notice within 28 days of becoming aware of the event.
- Measurement
- Quantities structured to the BOQ and the measurement method the contract names, or to your engineering MTO format.
- Document control
- Oracle Aconex read as the project's record: every result links back to its document and revision.
- Planning
- Changes linked to the Primavera P6 activities they affect, for your planners to assess.
- Languages
- Documents in English and in Arabic read in the same package, none ignored.
- Hosting
- Deployed in your infrastructure or your cloud, with your keys and logs; Mirage's access can be limited or removed.
Every result comes with its evidence
A tender, a variation or a claim cannot rest on an unsupported answer. Mirage keeps every output connected to its source:
- Drawing
- Sheet
- Revision
- BOQ item
- Specification clause
- Contract clause
- Correspondence
Your engineers and commercial team check the evidence before anything enters a tender, a variation, a claim or a project system.
Configured to your company's rules
A forward deployed engineer works with your estimating, engineering and commercial teams to set Mirage up on:
- BOQ structures
- Measurement rules
- Cost codes
- Engineering standards
- Tender checklists
- Commercial rules
- Document conventions
- Approval workflows
- Project exceptions
Corrections and validated rules are reused on the next project.
Results from production deployments
Mirage's clients in Saudi Arabia and Egypt are not published by name. The figures below come from published case studies, one of them on engineering and fabrication drawings.
John Cockerill
80-90% reduction in measurement time, from 3-4 days down to a few hours
1 month → a few clicks for a manufacturing bill of materials
3 engineering disciplines running on the same platform
OCBM
100% of extracted quantities traceable to a source drawing
3 agents in production, from measurement through to pricing
Dedicated agent cross-checks drawing revisions to surface discrepancies as they occur
Works with your project systems
Mirage adds a layer to the systems in place instead of replacing them. Where a system has an API, Mirage connects to it (Aconex and Primavera P6 both publish one); where it does not, our engineers build the connector during deployment.
- Oracle Aconex
- Primavera P6
- Autodesk Construction Cloud
- Revit
- SAP
- Oracle
- Microsoft SharePoint
- Procore
- Internal systems
See your own package measured and checked
Send us a real drawing set, BOQ or engineering package, and we'll show you exactly what Mirage extracts and what it flags for your team.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
Prefer to talk it through first? Book a call
FAQ