Operating model
Optimon CoreSync — Demonstration & Product Definition Workspace. This environment exists for demonstrations, product reviews and developer reference. It is not the deployed industrial ingestion runtime and not a separate branded platform.
Environment purpose
This environment uses synthetic sources and simulated connector, role and execution behaviour. It does not connect to or control live industrial systems. Runs, receipts and permits shown here are simulation artifacts, not production evidence.
Studio readiness is assessed against working demonstration and specification workflows and executed checks. Native adapters and production runtime qualification belong to the separate deployment workstream and are tracked in the second ledger.
Local review work and configuration survive a reload in this browser. Snapshots and versioned export/import are available from the workspace page.
Deliberate environment boundaries
- No live industrial connectivity
The browser does not connect to a PLC, camera, WMS, ERP or message broker. A host or credential reference typed into a form never causes an external request, and no real secret is collected here. This is an environment boundary, not a studio defect.
- Simulated roles, not identity enforcement
Role perspective switching demonstrates separation of duties, and the simulator service layer rejects prohibited operations rather than only hiding buttons. That is simulated policy behaviour; it is not authentication or authorization enforcement.
- Studio contracts are proposals
Contracts live in an isolated studio namespace. Approved source definitions remain authoritative. A well-defined normalized fixture demonstrates a declared post-decoder workflow; it is not a captured vendor payload and not evidence that the protocol works.
- Simulated time, not measured throughput
Scenarios run on a seed and a virtual clock. Counts and dispositions derive from actual simulated transitions. No figure on any screen implies measured industrial throughput or latency.
- Browser-local workspace
Saved work, snapshots and exports live in this browser. They are not shared team state, an authenticated approval or a backup. Use the team's authorized review process for authoritative changes.
- Production integration tracked separately
Native adapters, runtime implementation and environment qualification belong to the deployment workstream and are reported as unassessed here. They do not gate studio completion.
Studio backlog — actual open work
| Item | State | Detail |
|---|---|---|
| Connector service-layer depth (WS-1) | open | Some connector families still reuse a shared screen template; profile-specific validation coverage is recorded per profile rather than assumed from the family. |
| Connector to use-case mapping | unassessed | Exact per-profile mapping to the 192 use cases has not been assessed. Family-level references are shown and never presented as exact coverage. |
| Review-ready sign-off | open | No feature is review-ready until a reviewer decision is recorded against its feature version. The ledger reports the real count, which starts at zero. |
| Assisted diagnosis end-to-end validation | not_run | The diagnosis workflow is implemented and role-gated; a full user-run validation has not been recorded. |