Omega 365 and ISO 19650
Omega 365 enables organizations to manage project and asset information in compliance with ISO 19650 standards, providing a configurable common data environment, controlled workflows, robust audit trails, and seamless support across delivery and operational phases.
How Omega 365 enables working in accordance with the ISO 19650 series for information management across the asset life cycle.
1. Executive Summary
More and more owners, operators, and delivery organizations require that project and asset information is managed in accordance with the ISO 19650 series. If your organization has set that goal, this document explains how Omega 365 supports you in reaching it.
The short version:
Omega 365 provides the common data environment (CDE) and the controlled information registers at the core of ISO 19650: information containers with metadata, revision and status control, gated workflows from Work in Progress through Shared and Published to Archive, controlled exchange between parties, and a complete audit trail.
Omega 365 covers both the delivery phase (ISO 19650-2) and the operational phase (ISO 19650-3) in one platform, so the information handed over from a project continues life as a managed asset information model rather than a static archive.
Omega 365 is configured to your project’s information standard: your naming convention, your metadata schema, and your status and revision codes, including national annex schemes where they apply.
One point we state openly, because it builds the right expectations: working in accordance with ISO 19650 is a property of your processes, not of any software product. No software is “ISO 19650 certified”. What Omega 365 provides is the controlled environment in which compliant processes are implemented, enforced, and evidenced. This document shows exactly where that support lies, and where complementary tools are used alongside Omega 365.
2. About ISO 19650
The ISO 19650 series defines how information should be managed across the life cycle of built assets. It originated in the British BS 1192 and PAS 1192 standards and is today the internationally recognized framework for structured information management in projects and operations.
Part | Scope |
|---|---|
ISO 19650-1 | Concepts and principles: information containers, the common data environment, and the information requirements hierarchy |
ISO 19650-2 | The delivery phase: information management during design and construction, from assessment of need to project close-out |
ISO 19650-3 | The operational phase: information management during operations, maintenance, and asset management |
ISO 19650-4 | Information exchange between parties and acceptance criteria for exchanges |
ISO 19650-5 | A security-minded approach to managing sensitive information |
Although the series carries “building information modelling (BIM)” in its title, its core requirements are general information management requirements. An information container in ISO 19650 is any named, persistent set of information: a datasheet, a procedure, a drawing, a P&ID, or a model file. The CDE workflow, status and revision metadata, delivery plans, and party structures apply to all of them equally. This means ISO 19650 is just as relevant, and just as achievable, on projects where document-based information dominates as on model-intensive projects.
3. The Common Data Environment in Omega 365
ISO 19650-1 defines the CDE as the agreed source of information for the project or asset: a workflow combined with the technology that supports it. Information containers move through four states, and Omega 365 implements each of them:
ISO 19650 CDE state | How Omega 365 supports it |
|---|---|
Work in Progress | Draft revisions and working files are held under access control scoped to the originating team, with check-in and check-out. Information is not visible to other parties until it is deliberately shared. |
Shared | Structured review workflows with configurable review codes, reviewer roles, deadlines, commenting, markup, and revision comparison. Distribution is governed by roles and distribution matrices, and controlled contractor-to-contractor sharing is supported with request, approval, revocation, and audit trail. |
Published | Gated approval workflows record who authorized what, when, and with which code. End users always retrieve the current approved revision by default, on desktop and mobile, so no one works from a stale copy. |
Archive | Every revision, review record, transmittal, and distribution event is retained. Superseded revisions are never lost; they remain accessible to authorized roles with their full history. Retention and disposition rules manage the long-term lifecycle without breaking the audit record. |
Your information standard, implemented as configuration
ISO 19650 requires each project to agree an information standard: a container identification convention, a metadata schema, and status and revision codes. In Omega 365 this is configuration, not customization:
Naming conventions: Document numbering is generated automatically from predefined rules per document type and originator, and incoming submissions are validated automatically, so non-conforming deliveries are rejected before they reach the register.
Status and revision codes: Suitability codes such as the UK National Annex S- and A-codes, or your company-specific scheme, are implemented directly in the register together with configurable revision sequences.
Metadata: Discipline, system, tag, equipment, area, and project-specific attributes connect each container to your asset and project structure, and support search on both metadata and file content.
4. The Delivery Phase (ISO 19650-2)
ISO 19650-2 structures a project into activity groups from invitation to tender through to close-out. Omega 365 supports the information management backbone of each:
ISO 19650-2 activity | How Omega 365 supports it |
|---|---|
Tender and appointment | Exchange Information Requirements (EIR), BIM Execution Plans, and responsibility matrices are held as controlled documents, and the agreed deliverable lists are structured directly in the register. |
Delivery planning (MIDP and TIDP) | The document register operates as a live Master Information Delivery Plan: every planned deliverable with responsible party, planned dates, status, and review history. Each appointed party’s scope is available as a filtered Task Information Delivery Plan view. |
Mobilization of parties | Contractor and supplier portals let external parties request document numbers, submit deliverables through the browser, and track review status, without access to your internal systems. Validation rules test conformance from the very first submission. |
Collaborative production and review | Review cycles with codes and deadlines, visual and semantic revision comparison, and dashboards showing progress, overdue items, and review performance per party and discipline. |
Information model delivery and acceptance | Gated authorize-and-accept workflows implement the formal exchanges. Rejections return containers to the responsible party with recorded reasons, and transmittal records evidence every formal delivery. |
Close-out and handover | Accepted as-built and life cycle information transfers into the operational register with tag and system metadata intact, while the complete project archive is retained. |
A recurring question in ISO 19650 audits is simple: can you demonstrate that the agreed process actually ran? Because every review, status change, and distribution in Omega 365 is recorded, your evidence base builds itself continuously instead of being reconstructed afterwards.
5. The Operational Phase (ISO 19650-3)
ISO 19650-3 requires the asset information model (AIM) to be maintained as a current, trustworthy resource throughout operations, updated through planned, unplanned, and life cycle trigger events. This is where Omega 365’s combined project and asset scope makes a real difference:
Continuity: The same controlled register continues from project handover into operations. There is no migration to a separate archive product, so revision history, metadata, and audit trails survive the phase transition intact.
Asset structure: Tag, system, and equipment metadata link every container to the asset hierarchy, so operations and maintenance personnel find current, approved information through the structures they already work with.
Trigger events: Modifications and maintenance projects run in the same platform, drawing reference information from the AIM and returning updated revisions to it through the same controlled workflow.
Long-term stewardship: Retention rules and document disposition automate long-term lifecycle handling in line with your policies, and a complete, auditable AIM can be handed over intact through changes of operatorship or contract structure.
6. Security-Minded Information Management (ISO 19650-5)
ISO 19650-5 asks organizations to take a risk-based approach to sensitive information. The security strategy itself is yours to define; Omega 365 provides the enforcement and the evidence:
Role-based access control at register, document, and revision level, with distribution governed by matrices rather than ad hoc forwarding
Managed handling of confidential content with restricted visibility and administrative oversight, inside the same controlled environment rather than in parallel systems
Controlled external access through portals and managed document interfaces, with the ability to revoke access at any time
Full audit trails of access, distribution, review, and status changes
7. Scope and Complementary Tools
To set expectations accurately, these areas sit outside Omega 365 and are covered by complementary tools or by your own organization:
Model authoring and coordination: Omega 365 is not a BIM authoring tool and does not perform model creation, clash detection, or advanced constructability analysis. Native and IFC model files are stored, revised, distributed, and controlled as information containers within the CDE. Omega 365 supports visualization of both standalone IFC models and federated models, enabling users to review and coordinate information across multiple disciplines. Detailed geometric coordination or clash detection are typically performed in dedicated model coordination applications, with resulting issues and workflows managed and tracked in Omega 365.
Combined environments: On projects with significant geometric coordination requirements, a model coordination platform often operates alongside Omega 365. In this architecture, Omega 365 serves as the controlled environment for information management and model governance, while specialized tools provide model authoring and advanced coordination functions. ISO 19650-1 explicitly allows the CDE workflow to span multiple technology solutions, making this a standard-conformant implementation rather than a compromise.
Content validation: Omega 365 validates metadata and register conformance. In addition, Omega 365 supports validation of model properties and information requirements through the use of Information Delivery Specifications (IDS), enabling automated verification of model data against defined project requirements. This allows project teams to assess compliance of model attributes and structured information directly within the CDE environment.
8. How We Work With You
A typical ISO 19650-aligned implementation of Omega 365 follows six steps, carried out together with our consultants:
Implement your information standard: Your identification convention, metadata schema, and status and revision codes are configured per the applicable national annex or your company standard.
Build the register as your MIDP: Planned deliverables are loaded with responsible parties, dates, and review requirements from the agreed delivery plans.
Configure the CDE gates: Review codes, approval workflows, and distribution matrices implement the state transitions and the authorize-and-accept steps.
Mobilize external parties early: Portal access, number request procedures, and validation rules are tested during mobilization, as ISO 19650-2 requires, not discovered during first delivery.
Define handover metadata from day one: Tag, system, and equipment attributes are specified up front, so delivery-phase information lands correctly in the operational register at close-out.
Stand up the evidence base: Dashboards for deliverable progress, review performance, and outstanding actions give you a continuous audit record.
9. Summary
Beneath its BIM title, ISO 19650 is a standard for disciplined information management: controlled states, explicit suitability, planned delivery, auditable exchange, and continuity from project into operations. That is precisely the territory Omega 365 occupies. With Omega 365 as your common data environment and controlled information register, combined with dedicated model coordination tools where your geometric scope requires it, your organization has a practical, auditable route to working in accordance with ISO 19650, from the first tender deliverable to decades of asset operation.
.png?scale=thumbnail)
