Metrolane Day-0
Explore a realistic synthetic enterprise.
A permanent reference state spanning operational systems, canonical enterprise data, documents, cross-system scenarios, and end-to-end data provenance.
Synthetic data · Read-only · No sign-in required
What is Day-0?
Day-0 is Metrolane's permanent frozen reference-enterprise state. It represents an established company before runtime simulation begins.
The data is intentionally consistent enough to explore end to end, while also containing a small set of deliberate cross-system lags, duplicates and ordering conditions.
Day-0 at a glance
10
Operational systems
74
Enterprise entities
85
Business objects
29
Documents
12
Day-0 scenarios
Explore Metrolane
Enterprise
Explore the organizations, people, products, locations, assets and devices that make up Metrolane.
For example
Kestrel Auto Retail
ORG-000012
Business
Orders, invoices, payments, shipments, production, service, and the events and observations around them.
For example
Customer Invoice
CINV-2026-000001
Systems
Browse the ten operational source systems in their own source-native terms.
For example
CRM Opportunity
OPP-2026-900001
Documents
Policies, procedures, contracts, specifications, manuals, reports and personnel documents.
For example
Extended 36-Month Warranty Policy
DOC-000050
Scenarios
Deliberate cross-system lags, duplicate source records and event-ordering conditions built into the frozen Day-0 reference estate.
For example
Won deal order lag
SCN-X04
Data Journey
Trace source records through extraction, raw ingestion, mapping, entity resolution and lineage into canonical enterprise data.
For example
ERP Customer Invoice → Canonical Invoice
CINV-2026-000001
Follow a business hand-off
A closed-won CRM opportunity becomes an ERP sales order.
CRM · Opportunity
OPP-2026-900001
Meridian — roof rail programme
CLOSED_WON
Opportunity → Sales Orderexisting operational link
ERP · Sales Order
SO-2026-000001
D
See an intentional Day-0 lag
SCN-X04
Won deal order lag
process lag · CRM → ERP · Standing at Day-0
A CRM opportunity reached Closed Won after the last CRM-to-ERP hand-off, so the corresponding ERP sales order has not yet been created.
Explore SCN-X04One enterprise identity, multiple source representations
ERP · Customer
CUST-2026-000002
Kestrel Auto Retail Private Limited
A
CRM · Account
ACC-2026-900001
Kestrel Auto Retail Private Limited
ACTIVE
CRM · Account
ACC-2026-900002
Kestrel Auto Retail
ACTIVE
resolve to
Organization
Kestrel Auto Retail
ORG-000012
See where canonical facts come from
Trace an ERP invoice from its source record through extraction and mapping into the canonical enterprise model.
- ERP Customer Invoice CINV-2026-000001
- → Raw extraction
- → MAP-INV-ERP-CUSTOMER v1
- → Canonical Customer Invoice CINV-2026-000001
Explore enterprise knowledge
Browse policies, SOPs, contracts, specifications and reports, or search indexed documents by meaning.
Browse DocumentsSearch documents by meaningView as
Switch persona to compare what each reader can see.
| Viewing as | Documents |
|---|---|
| 13 | |
| 5 | |
| 0 | |
| 16 |
Clearance and document access are separate. Clearance determines which classifications a reader may access; Documents-system content may also require an explicit grant. Neither one automatically gives the other.
View as demonstrates visibility in the synthetic Day-0 estate. It is not production authentication or authorization.
How Metrolane is built
Source systems → connectors → raw ingestion → mapping and resolution → canonical enterprise. 114 connectors, 39 mapping rules and 635 field-lineage rows. Field lineage traces canonical values back to their source contributions and mapping rules.
Open Data Journey