Scope and confidence
How this prototype works
This is a local-memory prototype built to make the PPC operating model understandable before production systems are introduced.
What local means here
The demonstration starts with synthetic data in the browser. When you post output, record downtime, adjust a plan, create a scenario, release a plan, or update an exception, you are changing the current local session only.
Refreshing the page resets local planning and execution actions to the starting dataset. The selected factory and role remain in this browser so a walkthrough can retain its chosen context. Nothing affects a real factory or buyer commitment.
Available now
What a walkthrough can accurately demonstrate.
- Synthetic apparel orders, factories, production lines, capacity snapshots, milestones, plan versions, and exceptions.
- Local interactions for plan allocation edits, scenario records, plan-version release, shop-floor output and downtime capture, and exception status changes.
- Recording downtime or output can create or update a local exception for the same order and line.
- Role and factory context controls that persist in this browser and frame the walkthrough; factory filtering is limited to selected Control Centre sections.
- Visible feedback patterns for stale data, permissions, empty states, and unsaved local changes.
Deliberately not included yet
These are future production-platform capabilities, not claims made by this prototype.
- Persistent shared data between users or browser sessions.
- Authentication, real user permissions, and production approvals.
- Live factory feeds, ERP integrations, and production rules that automatically create or route exceptions from external events.
- Production-grade database, audit, and integration infrastructure.
Reading the product with confidence
What is a live operating idea versus a demonstration device?
Operating model
The connection between commitments, capacity, plans, execution, and exceptions is the product concept being validated.
Demo mechanics
Buttons and local updates make that concept tangible without needing a backend or real factory data.
Future platform
Persistent data, user identity, integrations, and automated processes are intentionally deferred until the UI and operating model are validated.