top of page
Frequently asked questions
You can examine the architecture, published models, metadata, demonstrations, and reference environments without committing to adopt them.Some publications and models are useful on their own. The Offerings page explains what else is available and the terms that apply.Review Offerings
We have implemented and exercised the 3D Platform in generated environments with multiple systems, including the Government Lab with approximately 100 business-unit systems.That shows what has been implemented and tested. It does not establish production readiness at organizational scale. A production deployment still needs validation of performance, topology, security, disaster recovery, high availability, and operating support.Review Status
No. Business units can run separate systems suited to their work. Those systems use common rules for identity, Core data, authority, exchange, history, and aggregation so they can work together as a federation.Read Architecture
No. Each system can keep its own application and database. Native 3D systems use the common architecture directly.An existing application can participate through a stub or adapter that translates between its structures and the federation. It does not have to be rewritten first.Read Architecture
Core Models are reusable definitions for information that systems have in common. The layers are:3D Core → Domain Core → Business-Unit Core → Local ExtensionA Business-Unit System implements the shared layers it needs, together with its Local Extensions. Auditing, governance, security, and exchange are mechanisms supplied by the architecture; a Core model alone does not provide them.Read about Core Models
Each record’s ID combines a System ID with a sequential Record ID. The reference implementation uses 30 bits for the System ID and 33 bits for the Record ID.System IDs must be uniquely assigned, and a system must not reuse its Record IDs. The combined ID stays with the record when it is exchanged or aggregated.Two systems can still create separate records for the same person or other real-world subject. Those records need reconciliation; unique IDs alone do not resolve that.Read about primary keys
Systems can hold copies of the same record. Each copy keeps the same ID.Record Governance identifies the system authorized to maintain the record. Subscriptions specify which other systems receive it. Sharing a copy does not transfer maintenance authority.Read Record Governance
No. Governance tells us which system may maintain a record. It does not tell us that the record is accurate, complete, or up to date. Validation, review, and operating procedures are still needed.Read Record Governance
The audit log identifies changed records. Record Groups specify which information travels together. Subscriptions specify what to send, and Subscribers identify the receiving systems.Change → Audit Capture → Record Group → Subscription → Subscriber → ExchangeRead Audit-Driven Data Exchange
They may be able to participate through a stub or adapter that translates their information into the 3D exchange structures.This lets an organization modernize gradually. Each application still needs suitable mapping, interfaces, and validation. Participation is not automatic.Read Architecture
The warehouse needs continuing updates; generating it once is not enough. Master data arrives through subscription-based exchange. Transactional data arrives through the warehouse update process.Records retain their IDs and origins when they are brought together. How current the warehouse is depends on when those updates run and arrive.Read Data Warehouse
AI helps interpret business requirements and make design choices. Deterministic processing handles results that can be derived mechanically.We validate the resulting metadata before generating systems. AI works within the architecture’s rules and review process; it does not design the architecture on its own.Read Architecture
No. Government is the reference domain developed and described in the publications. Healthcare is the next planned domain.Municipal government, education, supply chain, and oil and gas are other possible domains. Listing them does not mean they have been implemented.Explore Future Domains
It is a government reference model covering 101 business units and 246 system capabilities, with shared structures, reusable Business-Unit Cores, and metadata relationships.Use it as a starting point. Refine it against actual requirements, legislation, and operating knowledge, and add Local Extensions where needed. It is not a certified specification for a jurisdiction.Read Government Domain
The Government Lab is a generated reference environment with synthetic test data, user interfaces, data exchange, and aggregation. We use it to test and improve the enterprise model.The dictionary describes the metadata. The Government Lab exercises the generated systems. Neither establishes that the systems have been deployed in production.Explore Digital Twin
No. Start with the government model, implement one business function, learn from it, and improve the model before implementing the next.Each project can stay manageable while its system is designed to work with the larger federation.Explore Digital Twin
Yes, where their information and exchange requirements overlap. Government may need to exchange information with healthcare, municipal government, or education. Supply chain and oil and gas provide other possible examples.Each domain keeps its own Domain Core and uses the common identity and exchange rules. The systems still need compatible definitions and authorization to exchange the information. These are possible applications of the architecture, not claims that each connection has been implemented.Explore Future Domains
Yes. Released Government model metadata is available under CC BY 4.0. You may reuse, adapt, and redistribute it, including commercially, provided you give attribution and follow the license terms.That license covers the model metadata. The framework, generation pipeline, implementation software, and Government Lab environment are proprietary to 766958 Alberta Ltd. They are available separately, subject to availability and terms.Review Offerings
Start with Architecture and Principles, then read Government Domain and Digital Twin.Publications links to released material and identifies the revised books. Offerings explains the models, schemas, software, environments, and services, along with availability and terms.View ArchitectureView PrinciplesOpen Publications
bottom of page
