Payment can control production release
A customer order does not automatically become authorised production work. Commercial state and factory activity need to be connected.
ALT Steel manufactures roofing and building materials across multiple locations.
The systems challenge was to connect what happens commercially — customer orders, payments and sales — with what happens physically inside the business: steel coils, production jobs, machines, quality control and dispatch.
The resulting platform creates operational traceability between the customer transaction and the manufacturing process required to fulfil it.
In a manufacturing business, recording an order does not mean the work is complete.
A customer order can create a requirement for physical production.
Management therefore needs visibility across both the commercial and physical sides of the business.
A disconnected system can answer one question: what did we sell?
A manufacturing operating system has to reach past the transaction and describe the physical work behind it.
What must we make?
What material will it consume?
Which machine should produce it?
Has it been produced?
Did it pass quality control?
Is it ready for the customer?
The system is designed around the relationship between commercial events and physical manufacturing events.
A customer order provides the demand. Payment can determine when production becomes authorised.
The production job converts that demand into work for the factory. The machine performs the work. The steel coil provides the physical material.
Quality control verifies the output. Dispatch completes the operational fulfilment process.
A command centre should help management understand where attention is required.
Instead of forcing users to inspect individual tables, the system surfaces operational states such as orders waiting for payment, jobs waiting for production, stock exceptions and dispatch readiness.
These are operational states recorded in the system at the time of capture. Different views can reflect different scopes or moments in the workflow, so the numbers are not forced to match.
The production queue connects customer demand to factory activity.
A paid order that requires manufacturing can become a production job.
The important design principle is that the production floor should not operate as an isolated system. Commercial state determines what work is authorised to move into production.
This is a single order visible in the production interface at the time of capture, shown as evidence of how commercial state feeds the production queue.
Production capacity depends on physical machines.
The platform therefore models manufacturing equipment as operational entities rather than treating production as a generic status.
The system currently models eight production machines, including Machine 2 HQ, Machine 4 HQ, Machine 1 HQ, Machine 7 HQ, Machine 1 GWR and Machine 6 HQ.
The production view also exposes machine running state, job queue, meters produced, OEE, maintenance status and downtime.
These values represent the system state at the moment the screenshot was captured. They are not permanent performance metrics, and the platform is not presented as their cause.
Steel manufacturing requires inventory to reflect physical reality.
A steel coil is not simply an SKU with a quantity. Each physical coil can carry its own dimensional and consumption attributes.
The system therefore models individual steel coils as physical inventory assets, which creates traceability between manufacturing activity and physical material consumption.
Once physical inventory is modelled correctly, the system can derive operational intelligence from it.
For example, remaining coil length can support estimates of available production capacity.
The displayed estimate of 151 days is based on the system’s recorded assumption of approximately 90m/day average production. It is a point-in-time estimate, not guaranteed future capacity.
Manufacturing workflows require quality controls after production.
The system includes inspection workflows so manufactured output can be evaluated rather than automatically considered complete.
NCR refers to a Non-Conformance Report. CAR refers to a Corrective Action Request.
The single failed inspection is not an indication of overall production quality. It is evidence that the platform supports quality-control states and exceptions.
Different operational views can reflect different scopes or moments in the workflow.
The broader operational command view shows 18 orders as Ready for Pickup, while the dispatch view captured 2 ready for pickup and 1 currently loading.
These numbers are not forced to match. Normal operational differences between dashboard contexts are left visible.
Customer operations sit alongside manufacturing rather than outside it.
The goal is to allow commercial and customer-facing teams to understand fulfilment status without needing to manually reconstruct what is happening on the production floor.
The Customer Liaison area also supports inbound WhatsApp interactions.
A customer order does not automatically become authorised production work. Commercial state and factory activity need to be connected.
Do not reduce manufacturing inventory to a generic quantity field. Width, thickness, weight, length and remaining material affect what the factory can actually produce.
A completed job should have an operational relationship with the material used to produce it. This creates a foundation for material traceability and production intelligence.
Manufacturing completion and quality acceptance are separate operational events. Inspection, non-conformance and corrective actions need explicit states.
Management should be able to see what requires attention: orders waiting for payment, production waiting to start, material becoming critical, quality failures, maintenance issues, and fulfilment waiting for the customer.
“The system doesn’t treat manufacturing as a collection of forms. It models the physical events behind the business.”
My role centred on understanding ALT Steel’s operational model and translating it into a connected system spanning customer demand, manufacturing, inventory and management visibility.
“Model the physical reality first: coils, meters, machines and jobs — then let the dashboards emerge from those events.”
I start with the operation, not the software.
ALT Steel demonstrates a different kind of systems problem from Island Group. Here the challenge is deeply physical. Customer demand becomes production work. Production work consumes real material on real machines. The manufactured output must pass through quality and fulfilment before the customer receives it. The software becomes useful when those events form one connected operational model.