<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
The product structure and the production sequence — versioned, alternated, engineering-change controlled.
Multi-level bills of materials with alternates, phantom assemblies, by-products and co-products; routings that link operations to work centres with setup, run and queue times. Engineering change orders that move the production world from one version to the next without losing the audit trail.
Multi-level BOMs
Hierarchical product structure with arbitrary depth. Phantom assemblies for sub-structures that exist on paper but not in stock; by-products and co-products handled natively.
Alternate components
Primary and alternate components per BOM line with substitution rules — preferred, allowed, prohibited. The planner sees what they can substitute when supply is short.
Routings
Operation sequence linked to work centres, with setup time, run time per unit, move time, queue time and tear-down time tracked separately.
Engineering change control
Engineering change orders move the BOM and routing from version to version with effectivity dates. The audit trail preserves what was true on each production date.
What the BOM and routing engine covers
BOM types
Production BOM, engineering BOM, sales BOM (for configured products), planning BOM, cost BOM — each with its own visibility scope and its own use case.
Alternate management
Primary, alternate, substitute and obsolete-replacement components with effectivity windows. Approval workflow for adding alternates.
Routing operations
Sequence-driven operation list with parallel and serial branches, work-centre assignment, time elements broken out for accurate cost and capacity computation.
Engineering change order
Multi-step ECO workflow — request, technical review, approval, deployment — with effectivity-date control on the production cutover.
Cost roll-up
Standard cost computed from BOM components and routing operations. Cost rolled up on demand or on a policy cadence, with variance against actual surfaced at order close.
Where-used analysis
From a component to every BOM that uses it; from a work centre to every routing that touches it. Engineering-change impact assessed before commitment.
Why effectivity dates beat version numbers
Some PLM and ERP combinations track BOM versions and rely on the user to select the right version at the right time. When an engineering change happens mid-month, the planner has to know which work orders are under the old BOM and which under the new — and the chance of mistake is high.
Axional uses effectivity dates on the BOM and routing components themselves. A work order with a 15-March start uses whatever was effective on 15 March, automatically. The audit reconstruction of a production batch on a specific date is a query against the effectivity records, not a manual reconstruction.