MFG - production system of record
One controlled
production record.
MFG defines one controlled production record connecting demand, materials, capacity and shop-floor evidence to work orders, WIP, quality-gated completion and auditable decisions.
production order
Assemble finished SKU
release readiness
- Production versionmBOM + routing snapshot
- Material readiness1 component short (WMS)
- Capacity readinesswork-center + shift
- Asset availabilityno EAM downtime
Production capabilities
What one production record needs to hold.
Connect planning, readiness, execution, quality and completion without splitting the production truth across disconnected systems.
Orders
Work orders
Carry each production order through a controlled lifecycle rather than a loose status flag.
Recipe
BOM + routing snapshots
Freeze an mBOM and routing into a production version so the build definition stays known.
Readiness
Material + capacity readiness
Check WMS stock, SCM supply and work-center capacity before work reaches the floor.
Execution
WIP truth
Capture confirmations, moves, yield, scrap, rework and downtime as production evidence.
Quality
Quality-gated completion
Block completion after a failed mandatory checkpoint until an authorised approver releases it.
Handoff
Output declaration
Declare finished output with lot or serial traceability, then hand it to WMS and FMS.
The production lifecycle
Follow production from plan to completion.
A make-to-stock order moves through one controlled sequence, with each step writing append-only evidence to the same record rather than silently changing a status.
01
Planned
Version + readiness checked
02
Released
Planner releases the order
03
Staged
Materials staged from WMS
04
In progress
Operators confirm on the floor
05
Completed
Output declared, quality-gated
The problem it targets
The facts exist. The record does not.
- Demand, materials, and maintenance each live in their own tool
- Shop-floor events and finance records rarely agree
- No single record traces a finished lot back to what made it
SignalsReadiness controls
Release only against approved readiness.
- Material readiness would read WMS on-hand and SCM incoming supply
- Capacity would read work-center calendars and EAM availability
- A failed mandatory quality checkpoint would block completion until approved
Shop floorMFG in the production stack
One record from plan to completion.
MFG connects demand, material, capacity, execution and quality across the Splenta operating fabric while preserving clear ownership between systems.
Architecture
How the production record holds together.
The architecture combines a controlled make-to-stock lifecycle, a governed agent surface and clear ownership boundaries across the Splenta family.
The make-to-stock flow
A production order begins with demand and moves through material, capacity and quality controls. Each step would write append-only evidence, with corrections represented as reversals, adjustments or rework loops rather than silent edits.
- 01version
Pick the recipe
A demand signal would select a production version - an mBOM snapshot plus a routing snapshot with operations, work centers, and quality checkpoints.
ProductionVersion
- 02readiness
Check before release
Material readiness would read WMS on-hand and SCM incoming supply; capacity would read work-center calendars and EAM availability. Shortages surface first.
MaterialReservationRequest
- 03release
Release with a reason
A planner would release the order once readiness passes, or record an approved exception. No release against missing critical components without an approved shortage reason.
ProductionOrder
- 04execute
Confirm on the floor
Operators would confirm operation start, stop, and partial completion; WIP moves, labor and machine time, yield, scrap, rework, and downtime captured as evidence.
OperationConfirmation
- 05quality
Hold or release
Inspection checkpoints would record measurements and either release, hold, or route to rework. A failed mandatory checkpoint would block completion until approved.
QualityCheckpoint
- 06complete
Declare and hand off
Finished output would be declared with lot or serial traceability, handed to WMS for finished-goods receipt, and costing evidence handed to FMS. Close would need both.
OutputDeclaration
production-order lifecycle
The dashed state is the exception branch - work could be held for quality, material, safety, maintenance, or engineering reasons and resumed by the owning function. Cancelled, scrapped, split, merged and reworked provide explicit paths for other outcomes.
The Arin-over-MCP surface
Arin would read production readiness, timelines, quality holds, shortages and variance evidence, explain the exception and prepare an approval-bound action. MFG would validate policy and human approval before executing any change.
mfg:schedule:write
- production-order.plan
- production-order.release
mfg:operation:write
- production-order.hold
- production-order.resume
- operation.confirm
mfg:material:write
- material.substitution.request
mfg:quality:write
- quality.hold.release
- output.declare
- production-order.close
Every mutating tool would declare its required mfg:* scope, carry an idempotency key, and high-impact actions would require an approval state and a reason. Reads and writes would share one service layer behind REST, the UI and MCP.
The family boundary
MFG would own the production record without replacing WMS, SCM, FMS, EAM, PLM, an external MES or Arin. Systems exchange information through REST, MCP and events, with no shared database tables.
ICE
Identity and tokens for the family.
MFG would be an ICE resource server, validating ICE-issued tokens on mfg:* scopes.
Arin
Agent and decision-support layer.
Would read MFG facts and prepare approval-bound actions over MFG MCP - never own truth.
SCM
Procurement, suppliers, purchase orders.
Would supply incoming-supply and delay evidence; MFG owns the production effect.
WMS
Physical stock and locations.
Would reserve, stage, issue materials and receive finished goods; MFG owns production use.
EAM
Asset registry and maintenance.
Would supply availability and downtime evidence; MFG owns the production impact.
RMS / FMS / PLM
Demand, finance, engineering truth.
Demand signals in, costing evidence out, engineering BOM in - all through contracts.
the designed boundary
Arin would explain, classify, recommend, and prepare actions. MFG would validate the action, enforce approval and shop-floor controls, and execute through its own services. This is the intended arrangement, not running software.
Shape the concept
Help shape the production record.
If demand, materials, capacity and shop-floor evidence are difficult to reconcile, tell us how your production stack works today. Your operating priorities will help shape the first MFG implementation.