Skip to content
Zorix Systems — software that powers your business

Industries

Manufacturing software built around the job, not the ledger

Manufacturers rarely lack systems. They have an ERP for finance and stock, a CAD and PDM estate for drawings, spreadsheets for estimating, a whiteboard for scheduling and paper travellers on the shop floor. Each is defensible on its own. Together they mean nobody can answer the two questions that decide profitability: what did that job actually cost, and where is it right now.

We build the manufacturing layer that closes those loops — quoting, routing, shop-floor booking, material traceability, machine data and job costing — and integrate it with the ERP and engineering systems you already run.

Where it breaks

What breaks in a mixed-mode manufacturing operation

Estimating lives in one estimator's spreadsheet

Quotes are produced from a workbook that encodes material rates, cycle-time assumptions, setup allowances and a margin the estimator applies by feel. It is often accurate, but it is not inspectable, it cannot be compared against outturn, and it leaves with the person who built it. Win rates and quoted margin cannot be analysed because the inputs were never stored as data.

Estimated versus actual cost is never reconciled

Time is booked on paper or not at all, scrap is absorbed silently, and rework is rebooked against the original job number. At month end the finance system reports a blended margin across all work, which conceals the fact that a subset of jobs is being run at a loss and repeat-quoted at the same price.

Material offcuts and remnants are invisible

Usable remnant stock sits on racks with no record, so new bar, sheet or billet is bought while material that would have done the job is written off months later. A digital remnant library with dimensions, grade, certificate reference and location turns that stock back into inventory the estimator can quote against.

Scheduling is a whiteboard that only one person can read

Sequence, machine capability, tooling availability, operator skill and promised dates are held informally. When a hot job arrives the plan is rebuilt in someone's head, downstream impacts are discovered late, and customer service promises delivery dates the shop cannot support.

Traceability is reconstructed after the fact

Certificates, inspection sheets and non-conformance reports sit in folders and email. Producing a genealogy pack for a customer audit takes days of manual retrieval, and a genuine containment exercise — which parts came from that heat number, which shipped, to whom — cannot be done quickly at all.

The ERP is asked to do work it was not built for

Business Central, Sage 200 and SAP Business One handle ledgers, purchasing and stock competently. Bespoke routing, dynamic operations, part-quantity splits, concessions and shop-floor realities get bolted on through customisation until upgrades become risky and the workaround becomes the system.

Regulatory context

What the sector has to satisfy

Product conformity
UKCA and CE marking evidence packs, declarations of conformity and technical files that must be reproducible for the retention period applicable to the product class.
ISO 9001 quality system
Controlled documents, calibration records, inspection evidence, non-conformance and corrective action records, and demonstrable management review — all auditable rather than assembled for the audit.
Material compliance
REACH and RoHS declarations, material certificates against heat or batch number, and conflict-minerals or customer-specific material restrictions where the supply chain demands them.
Customer quality standards
PPAP, FAIR and first-off inspection packs for automotive, aerospace and medical supply chains, each with its own document set and sign-off route.
Health, safety and environment
COSHH records, LOLER and PUWER inspection scheduling for lifting and work equipment, and waste transfer documentation held against the assets and jobs they relate to.

Integration surface

The systems we connect to, named

ERP and finance

Sage 200SAP Business OneDynamics 365 Business CentralXeroUnleashed

Engineering and CAD

SolidWorks PDMAutodesk VaultSTEP and IGESDXF nestingFusion 360

Shop floor and machine data

OPC UAMQTTModbus TCPFanuc FOCASSiemens Sinumerikedge gateways

Identification and logistics

Zebra ZPLGS1 barcodesRFIDcarrier APIscustomer EDI

Solutions

What we build in this sector

Custom manufacturing platforms

RFQ and estimating, job routing, shop-floor booking, remnant and material control, and estimated-versus-actual costing built to your process rather than a vendor's reference model.

Explore custom manufacturing platforms

ERP and machine integration

Two-way integration with Business Central, Sage 200 or SAP Business One, plus OPC UA and MQTT capture from controllers and edge gateways where the machines expose data.

Explore erp and machine integration

Manufacturing data and reporting

A warehouse layer that turns booking, telemetry and quality data into OEE, margin-by-customer and quote-to-outturn reporting that survives audit.

Explore manufacturing data and reporting

Legacy shop-floor system replacement

Phased replacement of Access databases, unsupported MRP installs and Visual Basic tooling using a strangler pattern, so production never stops for a cutover.

Explore legacy shop-floor system replacement

Engagement shapes

Typical scope, duration and budget band

Discovery and process survey
Three to five weeks covering estimating, routing, booking, quality and the machine-by-machine data survey. Produces an architecture document, integration map, phased estimate and risk register.
Phase one build
Typically three to six months to deliver RFQ and estimating, job creation and routing, and shop-floor booking with ERP write-back.
Subsequent phases
Machine telemetry, scheduling, traceability packs, remnant control and executive reporting, delivered in two-week iterations against an agreed architecture.
Budget band
Quoted per engagement following discovery, driven mainly by integration surface, number of sites and how much machine data is genuinely readable.
How discovery and scoping works

Questions

Frequently asked

Do you replace our ERP or sit alongside it?

Usually alongside. Sage 200, SAP Business One and Business Central hold finance and stock adequately; what they handle badly is quoting bespoke work, routing a job across mixed machine groups, and reconciling estimated against actual cost. We build the manufacturing layer around the ERP and write back the transactions finance needs, rather than attempting a rip-and-replace that would put the ledger at risk.

Can you capture data from our machines?

Where the machines expose it. Modern CNC controllers and PLCs speak OPC UA or can publish over MQTT through a gateway; older equipment often only offers dry contacts, a serial feed or a counter that can be read by an edge device. We survey the shop floor during discovery, list what is readable per asset, and design around the gaps instead of assuming full telemetry that does not exist.

How do you handle traceability and quality records?

Material batch, operator, machine, program revision, inspection result and non-conformance are recorded against the job and the individual part where serialisation applies. That gives you a genealogy record you can produce for an ISO 9001 audit, a customer PPAP pack or a recall investigation without reconstructing it from paper travellers.

What does a first phase usually cover?

RFQ and estimating, job creation and routing, and shop-floor booking, because those three restore the estimated-versus-actual loop that most manufacturers have lost. Machine telemetry, scheduling optimisation and executive dashboards follow once the transactional data is trustworthy — dashboards built on bad booking data simply publish the error faster.

Do you work with subcontract and mixed-mode manufacturers?

Yes. Subcontract machining, fabrication and assembly are the hardest cases because every job is different, the routing changes mid-flight and outwork has to be tracked off site. Those constraints are the reason a configured product usually fails and a bespoke manufacturing layer holds.

Tell us what your systems are doing wrong.

Send the problem, not a brief. We will tell you whether it is a project we should be involved in.

Talk to us