A common data environment that keeps the record after the project ends.
For asset owners and project teams working to ISO 19650. Lunr is engineering document management that serves as your common data environment: one agreed source of information, controlled states and approvals, and transmittals to external parties, with a full audit trail behind every change.
10M+ documents under management · Hosted in Australia and the US · SAML · Full audit trail
A shared drive is not a common data environment.
Information sits in nested folders on SharePoint or a shared drive. Nothing holds an agreed state, the current revision is a guess, and files go to external parties by email with no record of what was sent. When an ISO 19650 review asks who changed a drawing, and when, the answer is an email thread.
Lunr is engineering document management that serves as your common data environment. Every information container carries its state and revision history, sharing with external parties is controlled and logged, and the record stays with the owner after the project ends.
Read how the common data environment will evolve- 01There is no agreed state on a document, so no one can tell work in progress from a published, approved sheet.
- 02The current revision is a guess. Superseded information containers sit in the same folder as the live one.
- 03External parties are sent files by email, with no transmittal record of what went out, to whom, or when.
- 04There is no audit trail, so an ISO 19650 review cannot show who changed a drawing, or when.
- 05At project close, the record scatters across inboxes and drives, and the asset owner inherits a mess.
One agreed source of information, under revision control.
A common data environment holds one agreed source of information, so the team works from the same record rather than a copy on someone's drive. Each drawing, model, and document is an information container with its own number, metadata, and revision history. Book a container in and Lunr numbers it, reads its title-block tags into metadata, and keeps every earlier revision marked as superseded.
- One controlled record for every drawing, model, and document, held as an information container.
- Automatic numbering and title-block tag parsing, applied as containers are booked in.
- A full revision history on every DWG, DGN, RVT, PDF, and IFC, with superseded copies kept and marked.
- Unique identification and metadata on each container, the naming discipline ISO 19650 asks for.
agreed source of information · information containers · automatic numbering · metadata · revision history
See document control
Work in progress, shared, published, and archived, on the record.
ISO 19650 moves each information container through states: work in progress, shared, published, and archived. Lunr runs those states as configurable workflows, so a container advances only when the right person approves it. The state sits on the record and in the audit trail, so anyone can see where a drawing stands without asking.
- Configurable workflows that move each container through work in progress, shared, published, and archived.
- Review and approval steps, so a container advances only when the right person signs it off.
- The current state is on every container, visible to the team without an email.
- Every transition is logged in the audit trail, ready for an ISO 19650 review.
configurable workflows · states · review and approval · audit trail
See configurable workflows
Share with external organisations, and keep the transmittal trail.
A project runs across organisations, and a common data environment has to share information beyond your own staff without losing control. External parties join as collaborators with access to only what they need. Issue a transmittal to send controlled drawings and documents to a contractor or a vendor, and the transmittal tracks itself, so you can show what was sent, to whom, and when.
- External organisations join as collaborators, with controlled access to only the information they need.
- Issue tracked transmittals to send controlled drawings and documents to contractors and vendors.
- Every transmittal records what was sent, to whom, and when, for the audit trail.
- Comment and mention on a container, so a question stays with the drawing, not in an inbox.
collaborators · transmittals · controlled access · audit trail
Search and open every drawing and model in the browser.
A common data environment is only useful if the team can find and read what is in it. XRAY runs OCR and full-text search across every drawing and document, scans included, so a valve tag or a title-block reference on any sheet is findable. Open DWG, DGN, and PDF in the Rift viewer, IFC and RVT models in Foundry, and point clouds in Nimbus, all in the browser with no CAD licence.
- XRAY OCR and full-text search across every DWG, DGN, RVT, PDF, IFC, and scanned sheet.
- Open BIM models in Foundry, drawings in Rift, and point clouds in Nimbus, all in the browser.
- Toggle layers, measure, and mark up a drawing straight in the viewer, with no CAD licence.
- Deep XRAY re-scans a dense sheet tile by tile, so nothing on the drawing is missed.
XRAY OCR · full-text search · Foundry · Rift · Nimbus · no CAD licence
Read and write CAD, and tie the record to GIS and facilities systems through the connectors.
At project close, the owner keeps the record.
Most common data environments are built for the project and close with it. Lunr is built for the asset owner, so when the project ends the record stays. Validate the handover package against a manifest, so a missing as-constructed drawing is caught on upload, then the owner keeps every information container, its revision history, and the full audit trail for the operating life of the asset.
- Validate each handover package against a manifest, so a missing as-constructed drawing is caught on upload.
- The asset owner keeps every information container, its revisions, and the audit trail after the project closes.
- One record runs from project delivery through the operating life of the asset, not just to handover.
- Export all metadata, drawings, and models at any time, so the record stays yours.
manifest validation · handover · owner keeps the record · export anytime
Trusted with the record owners keep for decades.
Universities, utilities, energy companies, and government departments run their information record on Lunr, from project delivery through the operating life of the asset.
documents under management on Lunr. Proof the information record holds up at owner-and-portfolio scale.
Read the University of Canberra case study“Lunr is a simple solution that provides the flexibility to develop the system to our needs. Lunr is simple to use, and minimal training is required.”
Questions teams ask about a common data environment.
What it is, what ISO 19650 asks of it, and how it differs from a shared drive.
- What is a common data environment?
- A common data environment (CDE) is the single agreed source of information for a project or an asset. It holds every information container, meaning each drawing, model, and document, in one controlled place, with an agreed state on each one, controlled access, and a record of every change. ISO 19650 uses the term for the workflow that moves information through work in progress, shared, published, and archived states. Lunr gives you that controlled record for DWG, DGN, RVT, PDF, and IFC.
- What does ISO 19650 require of a common data environment?
- ISO 19650 describes a CDE as the agreed source of information for a project or asset, with each information container held in a defined state and moved through work in progress, shared, published, and archived by an agreed process. It expects controlled access, unique identification and metadata on every container, and an audit trail of transitions. Lunr supports this workflow with configurable states, naming and metadata discipline, controlled sharing with external parties, and a full audit trail. Lunr is engineering document management that serves as your common data environment, so the ISO 19650 process is something you configure, not a certification we claim on your behalf.
- How is a common data environment different from a shared drive or SharePoint?
- A shared drive holds files in folders. It does not record which revision is current, it does not hold an agreed state on each information container, and it keeps no audit trail of who changed what. A CDE adds revision control, defined states and approvals, controlled sharing with external organisations, and a log of every transition. The University of Canberra moved more than 20,000 documents off SharePoint onto Lunr for this reason.
- Is a common data environment only for BIM projects?
- No. A CDE suits any project or asset with a controlled document record, from a single building to a whole estate. BIM projects use one because ISO 19650 asks for it, and Lunr opens IFC and RVT models in the Foundry viewer. The same controlled record holds DWG, DGN, PDF, Word, and Excel, so a team with no BIM models still gets one agreed source of information.
- What happens at handover, when the project closes?
- At project close, the information passes to the asset owner. Validate the handover package against a manifest, so a missing as-constructed drawing is caught on upload, then the owner keeps the full record, including revision history and audit trail, for the operating life of the asset. This is the difference between a project-only CDE and a record the owner holds for decades.
- Can external parties access the common data environment?
- Yes. Staff sign in over SAML with your identity provider, and external organisations join as collaborators with controlled access to only the information they need. Issue transmittals to send controlled drawings and documents to contractors and vendors, and every transmittal tracks itself, so you can show what was sent, to whom, and when.
- Where is the data hosted, and how is it secured?
- Lunr is hosted in Australia and the US, and your instance sits in the region you require. Staff sign in over SAML, external parties join as collaborators, and every controlled information container carries a full audit trail. Over 10 million documents are under management on Lunr today.
See it run as your common data environment.
Book a walkthrough with someone who knows what a transmittal, an information container, and an as-constructed drawing are, and watch Lunr run against a set of your own.
10M+ documents under management · Hosted in Australia and the US · SAML · Full audit trail · Export anytime
- entity
- Lunr Labs Pty Ltd
- location
- Melbourne AU
- workspace
- documents.lunr.app
- rev
- 2026