Production management system: structural steel fabrication

Where a job has got to

In a fabrication shop, the work itself is well understood. Where any given job has got to, right now, is not.

A structural steel fabricator ran production on an Excel sheet.

• A spreadsheet holds whatever was last typed into it, so the only complete picture of a job is the one assembled by asking people.
• Progress is a number in a cell, which makes the weekly report an exercise in reconstruction.
• Quality records get gathered near the end, exactly when a missing document costs the most.
• A spreadsheet does not know who you are, so nothing separates an estimator from a coordinator except knowing not to touch a cell.

What was delivered

The replacement is one system covering the whole chain, from a drawing arriving to a truck leaving. It has fifteen operational modules on a single job spine. A job passes through seven stages: detailing, procurement, subcontract, fabrication, quality records, dispatch readiness and dispatch.

• One record per job. Every stage attaches to the job itself rather than to each department’s own list.
• Progress that is recorded, not reported. Fabrication progress is entered against the job and carries an audit trail, so the weekly report becomes a query.
• Quality records built during the work. Manufacturing data records are a checklist maintained as the job proceeds, so completeness is visible before dispatch instead of discovered after it.
• Dispatch against readiness rules. Truck runs are scheduled for jobs that are actually ready, with eligibility applied by the system rather than judged at the loading dock.

What it changes

The point was never a dashboard. A job’s state stops living in someone’s head and becomes something the system can be asked. Weekly reports and exports are generated from the same records the floor updates, so reporting is no longer a separate activity performed from memory.

Who may change what

Access control was a starting requirement rather than a hardening pass. Permissions are enforced on the server, so they cannot be bypassed by using the screens differently. Seventeen dedicated test suites check who may do what, module by module. A change that breaks an existing rule fails a test, rather than surfacing later as someone quietly doing something they should not. Sign-in runs through the business’s own Microsoft Entra directory, so there is no separate password store to breach.

Honest limits

This system is in build, and its production status is still to be confirmed with the delivery lead. The chain differs by trade, but the shape holds wherever a job crosses several departments.

A comparable fit if you are…

• Reconstructing weekly progress from conversations rather than reading it off the work itself.
• Assembling quality documentation at the end of a job and finding the gaps at the worst possible moment.
• Giving everyone the same access because separating it has never been worth the effort.

Show us how your jobs move today.

Talk to us