The truck leaves with two bundles of steel sheets. The warehouse ledger shows 5.800 tonnes leaving stock. The delivery readings total 5.760 tonnes. Accounts needs a quantity for the service bill, and the planner wants to know how much of the original coil is still available for work. All three are looking at the same shipment. Each needs a different answer.
In this fictional shipment, the customer owns the steel and the processor does the work. One coil can become smaller coils, sheets, trim, and scrap. The pieces can end up at different sites. A delivery document may leave with two bundles while other material from the same receipt stays in the warehouse. Weeks later, someone may need to explain exactly which work produced the steel on that shipment.
As the client’s sole software consultant, I designed, built, and deployed the application and still maintain it.
Dispatch starts from identified finished stock. Accounts starts from a completed delivery. When a figure looks wrong, the person investigating can work back to the record that explains it.
Three questions about the same coil
The planner reserves Coil B for the partner’s cutting job before it leaves the primary site. While the truck is on the road, the transfer shows the coil in transit and the reservation keeps it out of other jobs. The partner records receipt when the truck arrives. The customer owns the steel throughout.
That distinction drove the workflow. At the primary site, the planner needs to see that the coil has departed. At the partner, the operator needs a receiving action for assigned material. When the finished bundles are ready, the primary processor can arrange dispatch from the site holding them. Each person sees the decision they can make at that moment.
Weight has a similar problem. An operator may use a calculated estimate to check whether a measurement looks plausible. Inventory tracks recorded stock weight. Dispatch records the delivery measurement. The warehouse also needs to find two physical bundles, each containing 40 sheets. Each screen labels the quantity it uses so the reader can tell what it describes.
The job we’ll follow
Follow Coil B through the diagram to see how part of the original coil becomes the two bundles on the truck. Its sibling, Coil C, stays at the primary site.

| Who | Decision |
|---|---|
| Planner | Which coil can I reserve for the next job? |
| Production supervisor | Does the recorded output account for the steel that went into the cut? |
| Partner operator | Has the coil assigned to my job arrived so I can start cutting? |
| Dispatch clerk | Which released bundles can I put on this truck? |
| Warehouse clerk | Which bundles left, and how much recorded stock left with them? |
| Accounts clerk | Which delivery weight do I use for the service bill, and does the amount returned by accounting match? |
Of the original 10.000 t, 5.800 t shipped. Coil C accounts for 3.700 t still at the primary site. The remaining 0.500 t is trim and scrap. The planner checks whether Coil C is available before reserving it for another job.
The delivery readings total 40 kg less than the stock weight of those two bundles. Accounts uses the delivery weight for this job’s service bill.
Some orders can go straight to cut-to-length. Others call for reslitting or rewinding. We cover those routes separately, including how each records its result and when it needs a plan or review.
What the planner needs from the cutting line
The operator records the slitting result while the planner is waiting to use Coil B for the next job. If the job shows up as finished but the stock list still shows only Coil A, the planner has to call the operator to find out whether Coil B is ready. The application saves the accepted result, the stock movements, and the links to the source coil in one database transaction. Once the result posts, the planner can find Coil B and the supervisor can trace it to the same cut.
On the screen, the same choice has a quieter effect. The operator sees the plan and enters what actually came off the line. When the resulting bundles reach dispatch, the clerk can select the released stock instead of reconstructing it from a production note. If two clerks try to reserve the same bundle, one gets a specific conflict while there is still time to choose a different item.
The later handoffs follow the same pattern. Someone can tell whether a delivery is ready for billing, whether the accounting return still needs review, or whether the reconciled invoice is waiting to be generated. Those distinctions determine who needs to do something next and what information they should have in front of them.
Read the series
From the receiving desk to the shop floor
- Turning Shop-Floor Work Into Software Requirements — Follow a receipt through the hands of the people who will use it and see how their questions became requirements.
- A Modular Monolith for the Factory and Back Office — Follow an operator’s submission to the database and see what happens if the response never makes it back.
- Stock You Can Reconcile and Material You Can Trace — Balance a coil split and trace one bundle back through the operations that created it.
- Choosing the Right Process for a Coil — Decide what work an order needs when the width, physical form, and usable material differ.
- Keeping Custody Intact Across a Partner Site — See what each site can establish while a coil is in transit.
- Designing for the Person Doing the Work — Work through a result screen and find out which questions the software can answer before the operator arrives.
From the loading bay to accounts
- From Available Stock to a Customer Shipment — Find out what has to happen before a delivery document can leave with the truck.
- From Dispatch Evidence to Reconciled Billing — Follow a 0.01 discrepancy to the field where the expected amount and the return diverge.
- Reporting That Can Explain Its Numbers — Take apart an apparent 4.240 t gap and determine which evidence would justify calling it resolved.
- Security Across the Browser, Factory, and Partner Boundary — Follow the information different people can access about the same shipment.
From a code change to a running service
- Developing and Testing Against Real Workflow Risks — Turn a race between two dispatch clerks into a testable business rule.
- From Local Development to a Release Candidate — Follow one commit through continuous integration and client preview to the decision about production approval.
- Operating, Recovering, and Changing the System Safely — Work backward from an invoice PDF that has yet to arrive and see how the recovery path preserves the shipment.
A short glossary
| Term | Meaning in the series |
|---|---|
| Job work | Processing material on a customer’s behalf. |
| ERP and MES | The enterprise resource planning side coordinates back-office operations. The manufacturing execution side records planned and performed shop-floor work. |
| Custody | Where material is physically held or accounted for while moving. |
| Reservation | A commitment of eligible quantity to a particular task. |
| Ledger | The record of movements that explains stock position. |
| Genealogy | The links that show which operation transformed one material identity into another. |
| Reconciliation | Comparing records with a known basis, identifying the difference, and tracking what remains to be resolved. |
| t | Metric tonnes. |
Discussion
Comments 0
New comments are moderated before they appear publicly.
Be the first to leave a thoughtful comment.