On the floor of a West Midlands machine shop, the truth of the business is in the noise: spindles cutting, a setter walking a first-off to inspection, a printed works order clipped to a job that finished an hour ago and nobody has closed off. Fifty feet away in the office, the MRP system shows a different shop entirely: a schedule that drifted out of date by mid-morning, a stock figure that is close but not right, a job costing run that will be reconstructed next week from memory and guesswork. That distance between what is happening at the machines and what the back office can see is the single biggest software problem facing component manufacturers and precision-engineering firms across Birmingham and the Black Country, and it is what brings operations and finance managers here looking for a developer.
The West Midlands is the densest automotive manufacturing cluster in the UK (roughly 32% of Great Britain’s automotive employment and more than a fifth of all UK parts and accessories manufacturers) and the largest automotive manufacturing base of any UK region. The buyers in that figure are not Jaguar Land Rover or the big tiers; they run their own IT and engineering. The firms with the shop-floor-to-back-office gap are the ones feeding them: the mid-size Tier 2 and Tier 3 component makers and the subcontract CNC shops (the owner-managed and family-run engineering SMEs named across the regional supply base from Birmingham Precision Engineering to T2K CNC machining since 1974) that run capable manufacturing systems but employ no developers to make them reach the machines.
The Gap Between the Shop Floor and the Back Office
The pattern is nearly identical from shop to shop. The plan lives in three places at once: a whiteboard the planner trusts, a spreadsheet that feeds the customer schedules, and the MRP system that is supposed to be authoritative. Within a couple of hours of the shift starting, none of them agree. Works orders are printed and walked to the floor. Job progress, scrap, setup time and machine hours are then re-keyed back later, if there is time, and often there isn’t. So the system never quite reflects what is running, and the floor learns to trust the paper and the foreman over the screen.
Most of these firms run a capable back office: Sage 200 Manufacturing for MRP, bills of materials and works order processing, often with Cim200 bolted on for the graphical scheduler and shop-floor data capture, or Sicon Manufacturing, 123insight or Sapman. None of these is the problem. The problem is that they were bought to run the office, and they stop at the office door. The machines, the operators and the inspection bench sit on the far side of a manual join that someone has to maintain by hand all day.
Why Job Costing and Stock Are Always a Guess
The cost of that gap shows up most sharply in two numbers a manufacturer cannot afford to have wrong: margin and stock.
Job costing gets reconstructed after the job is done. Actual machine hours, real setup time, material yield and the rework nobody logged are estimated back in, so true cost per part and true margin per customer is an educated guess rather than a measured fact. On automotive work, where a Tier 2 supplier is holding a fixed price across a long programme, guessing the cost of the part is guessing whether the contract is making or losing money. Stock and WIP carry the same flaw from the other direction: because consumption and completions are logged manually and late, inventory figures are perpetually slightly off, which is exactly how a shop ends up simultaneously stocked out of one item and over-ordered on another.
These are not failings of the people. They are the inevitable result of asking a person to be the live data link between a machine and a database, every hour, on top of their actual job.
Traceability That Lives in Spreadsheets — Until an Audit
For anyone in the automotive chain there is a third pressure that the others feed into: IATF 16949. The standard requires that any finished part can be traced back through every process step, material lot, machine, operator and inspection result. For a powertrain component, that can mean 30 to 50 process parameters across 8 to 12 operations, plus material certificates and SPC data. In most mid-size shops that traceability is held together by spreadsheets, paper travellers and inspection sheets filed in a cabinet.
It works right up until a customer audit or a containment request, at which point reconstructing the full history of a batch becomes a frantic manual hunt across systems that were never designed to be joined. The compliance pain comes not from the standard itself but from manual, spreadsheet-based processes that do not scale: precisely the join bespoke software is built to close.
How brittle these manual joins really are stopped being theoretical in autumn 2025. The cyber-attack that forced Jaguar Land Rover to shut its IT systems halted production at Solihull, Wolverhampton and Halewood and cascaded down a supply network of more than 5,000 companies; a regional Chambers survey found 77% of firms negatively hit. It exposed how much of a mid-size supplier’s operation runs on undocumented manual process and single points of failure, and how little resilient, internal system sits underneath the production line.
Building the Layer That Connects Your MRP to the Machines
The work here is almost never to replace Sage 200 or your MRP. It is to build the layer that makes what you already run reflect what is happening on the floor:
- Shop-floor data capture wired to the MRP: tablets or terminals at the machines that book job starts, completions, scrap and machine time once, at the point it happens, so the schedule and the stock figures stay live instead of being re-keyed later. This is our core API integration work, built around the Sage 200, Cim200 or 123insight system you already own.
- A real scheduling view that replaces the whiteboard-and-spreadsheet split with one plan the office and the floor both trust, fed by actual machine state rather than yesterday’s assumptions.
- Automated job costing that captures real machine hours, setup and yield against each works order, so margin per part and per customer is measured, not estimated after the fact.
- A traceability spine that ties material lot, machine, operator, process parameters and inspection results to each batch as it is made, so an IATF 16949 audit or a customer recall becomes a query, not a cabinet search.
This is custom software development for firms that are deeply expert in metal and machines and have no wish to employ a software team. The value here is in systems that run the operation for years.
Supplying the West Midlands Automotive Chain?
The fastest way to scope the first piece of work is to follow a single job from the customer schedule to the finished part and mark every point where a number is written on paper, walked across the floor, or typed into a second system. Each of those joins is a cost, a delay and an audit risk waiting to be designed out. Show us where the shop floor and the office stop agreeing and we will start with the join that takes the most cost and risk off the floor. For how this connects to the rest of the city’s economy, see software development in Birmingham.
