1126 Labs PPC Platform
A shared operating picture for apparel production
The platform helps factory leaders see whether buyer commitments can be met, where finite capacity is under pressure, what plan is being released, what the floor is reporting, and who owns the next decision.
Local demonstration dataHow to use this prototype
The platform runs on synthetic local data. You can safely explore plan edits, local scenarios, output posting, and exception status changes; refresh the page to reset the demonstration state.
The Viewing bar sets the factory and role context. Use it to frame the same operating story as leadership, a planner, or a supervisor. It is a conversation tool in this prototype, not a login or permissions system.
Delivery: Which buyer commitment is exposed?
Capacity: Which line is overloaded or has recovery headroom?
Ownership: Who has the next action and by when?
The PPC operating loop
From commitment to controlled recovery
The platform connects the buyer promise to finite capacity, the released plan, shop-floor actuals, and a named response when delivery is exposed.
- 1
Control Centre
Which delivery commitment needs a decision now?
- 2
Order 360
Can we still honour this buyer commitment?
- 3
Capacity Workbench
Where is capacity constrained and what recovery option protects delivery?
- 4
Plan Builder
Which allocation and plan version should go to the floor?
- 5
Shop-floor
What is happening on this line during the current shift?
- 6
Exceptions
Who owns this operational risk and what action will resolve it?
Leadership walkthrough
Protecting the Aurora Rib Tee commitment
A practical narrative for explaining why the screens are connected.
Start at Control Centre
See Aurora as an at-risk order and identify the line constraint or exception that needs attention.
2Confirm the commitment
Open Order 360 to read the buyer promise, good output, critical path, and projected delivery risk.
3Choose a recovery
Use Capacity Workbench and Plan Builder to compare allocation options and release the plan you want the floor to follow.
4Close the loop
Use Shop-floor actuals and Exceptions to show whether execution is recovering and who owns any remaining risk.
One platform, three perspectives
Role guide
Find the right view
Screen guide
Control Centre
Which delivery commitment needs a decision now?
Order 360
Can we still honour this buyer commitment?
Plan Builder
Which allocation and plan version should go to the floor?
Capacity Workbench
Where is capacity constrained and what recovery option protects delivery?
Shop-floor
What is happening on this line during the current shift?
Exceptions
Who owns this operational risk and what action will resolve it?
Production Gantt
Where do dependencies or timing put an order at risk?
Factory Configuration
Are the factory settings and planning guardrails trustworthy?
Shared language
PPC glossary
- PPC
- Production Planning and Control: matching buyer commitments, capacity, plans, and factory actuals.
- Dispatch commitment
- The date the order is expected to be ready to leave the factory for the buyer.
- Finite capacity
- Planning against the actual minutes and capability a line has available, not unlimited theoretical capacity.
- Utilization
- The share of available line time already required by planned work.
- Headroom
- Capacity still available after planned work, downtime, and other constraints are considered.
- Plan version
- A recorded planning option compared with the baseline before release.
- Allocation
- The quantity or percentage of an order assigned to a specific line and operation.
- Scenario
- A safe local what-if comparison, such as moving work to another line or considering overtime.
- Actuals
- What the factory has actually produced or lost during execution, including output and downtime.
- Milestone
- A critical point in the order path, such as sewing complete or dispatch ready.
- Exception
- A named operational risk with severity, owner, due date, recommended action, and status.
This reference documents the current local prototype. Production data, authentication, integrations, and persistent approval workflows are intentionally outside its scope.