What does “now” mean inside a simulated company?
The software may be running today.
But the simulated company may believe it is operating at:
August 5, 2026 — 14:00
Metrolane therefore separates business time from technical time.
Without that distinction, a simulator can generate records — but it cannot reliably create a believable business history.
Two clocks, two meanings
Both timestamps can be correct.
They answer different questions.
Why this matters
Imagine a CRM opportunity closes at:
The ERP Sales Order does not need to exist at exactly the same instant.
- 14:00CRM Opportunity = WON · ERP Sales Order = not yet presentCRM · ERP
- 15:00CRM Opportunity = WON · ERP Sales Order = createdCRM · ERP
- 18:00connector extraction runsConnector
- 18:30canonical projection catches upCanonical
That sequence gives Metrolane something a static data generator cannot provide:
committed intermediate enterprise states.
A Day-0 lag
SCN-X04 · Won deal order lag
At Day-0:
expected
This is current, inspectable Day-0 evidence.
Phase 10 gives us the mechanism to let situations like this progress through controlled business time.
The clock is not just a timestamp generator
If the simulator simply stamps every new record with the computer's current time, then business causality, lags, replay and deterministic scenario timing all become unreliable.
Instead, business time is an explicit runtime concept.
If a business operation requires simulated business time and the runtime has not established it, the safer behavior is:
not:
Why? Because a plausible-looking timestamp can still create false enterprise history.
Timeline — one day on the enterprise clock
Business time7 points · illustrative
- 09:00CRM work startsCRM
- 11:00Opportunity progressesCRM
- 14:00Opportunity closes WONCRM
- 15:00CRM → ERP handoff · Sales Order createdCRM → ERP
- 18:00Connector extractionConnector
- 18:30Canonical projectionCanonical
- laterEnterprise grounding sees the canonical Sales OrderGrounding
The exact times are illustrative business-time points. They are not a rule that every Metrolane day uses these times.
Current vs instructional content
The visitor must be able to distinguish:
- 14:00 close
- 15:00 relay
- 18:00 extract
- 18:30 project
The runtime timeline teaches the Phase-10 architecture.
It is not pretending that a current Day-0 runtime-control page already exists.
Chapter takeaway
- Business time is the enterprise's simulated now.
- Technical time is when software really runs.
- Separating them lets business processes unfold with meaningful lags.
- Those intermediate states are essential to realistic simulation.