- Home
- The Connected Floor
Ten functions. One operational record.
Your plant already runs production, quality, maintenance, safety, stores and utilities. The trouble is that each keeps its own version of the truth. This is what it looks like when they stop.
What is a connected factory?
A plant where every operating function writes to, and reads from, the same operational record.
The test is simple: can you trace a customer complaint back to a machine, a shift, an operator and a supplier lot without opening a spreadsheet?
It is the practical core of what Industry 4.0 and smart factory programmes set out to build.
The value is in the joins, not the functions.
Ten separate digital systems are ten silos with better screens. What changes an operation is that a quality escape can be joined to the machine that made it, the operator on shift, the material lot and the maintenance done that week, by anyone, without a reconciliation exercise.
Quality to production
A defect trend that only appears on one machine, on night shift, after a changeover. Invisible when quality and production keep separate records.
Maintenance to downtime
Which preventive tasks actually reduce breakdowns, and which are done because they always have been.
Energy to output
Consumption per unit produced rather than per month billed, which turns a fixed overhead into something a shift can influence.
Supplier to escape
Incoming lots linked to the defects they caused downstream, so supplier scorecards reflect reality rather than paperwork.
Skills to scrap
Whether the operator on that machine tonight is certified for it, and whether certification correlates with quality.
Everything to the review
A daily meeting run from live exceptions with owners and clocks, instead of a deck assembled early that morning.
What each function captures
Choose a function to see what it records and the measures it moves.
Production and throughput
Output, plan against actual, cycle time, downtime reasons and changeovers captured at source instead of reconstructed from a whiteboard the next morning. Supervisors see the line as it runs, not as it was.
What it moves- OEE
- cycle time
- availability
- changeover time
- plan adherence
Quality and compliance
Digital inspection plans, in-process checks, non-conformance capture and CAPA closure, so a defect is caught at the station that caused it rather than at dispatch, or at your customer.
What it moves- first-pass yield
- escape rate
- CAPA closure time
- NC ageing
Maintenance and reliability
Preventive schedules, breakdown logging, spares consumption and machine history in one place, with condition data feeding predictive models once there is enough of it to trust.
What it moves- MTBF
- MTTR
- PM compliance
- breakdown frequency
Safety and EHS
Permits to work, incident and near-miss reporting, hazard identification and safety observations, so compliance is evidenced continuously rather than assembled before an audit.
What it moves- LTIFR
- near-miss reporting rate
- permit compliance
- action closure
Utilities, energy and ESG
Power, compressed air, water, steam and effluent metered against production output, turning a monthly bill into a number each shift can manage.
What it moves- energy per unit
- specific energy consumption
- peak demand
- water intensity
Traceability and genealogy
A searchable thread from raw material receipt through every process step to the pallet that left your gate, traced backward from a complaint or forward from a suspect supplier lot without a manual search.
What it moves- trace time
- recall scope
- yield reconciliation
- audit preparation time
Warehouse and supply chain
Plans, orders and actual consumption reconciled against what the floor really produced, so shortages surface days ahead instead of at the moment the line stops.
What it moves- stock accuracy
- OTIF
- inventory turns
- shortage events
Procurement and suppliers
Supplier quality, audits and risk managed as a running relationship, with incoming performance linked to the production problems it actually caused.
What it moves- supplier PPM
- audit closure
- on-time supply
- rejection rate
Workforce and skills
Attendance, shift allocation, skill matrices and training records connected to the lines people run, so you know whether the operator on that machine tonight is certified for it.
What it moves- skill coverage
- training compliance
- utilisation
- certification lapses
Control tower and reviews
One live view across every function, with exceptions surfaced against an owner and a clock, comparison between plants, and daily reviews run from the system instead of a compiled spreadsheet.
What it moves- review preparation time
- action closure rate
- escalation ageing
- reporting lag
What sits underneath
The core is not a product name. It is a data model, an integration layer and a set of definitions that everything else agrees to use.
At the moment it happens
Machine data from PLCs, SCADA, meters and retrofit sensors, plus operator entries, written with the same timestamps and context.
One set of definitions
One definition of a part, a line, a shift, a batch, a reason code and an asset. This decides whether any join is possible.
Connected outward
The core linked to ERP, MES and QMS, so confirmations, movements and quality results reconcile without a person in the middle.
Everyone reads one record
Operator screens, supervisor views, the control tower and reports all read the same record, so nobody asks which number is right.
All four layers can run on a platform we implement, on software we build, or on a combination, which is the most common outcome. What matters is that the core is designed deliberately rather than inherited from whichever product was bought first. Our ISA-95 guide explains how we draw the boundaries.
Start with the audit, not the software.
A fixed-scope diagnosis of where your plant loses information, what it costs you and what to fix first. The roadmap is yours to keep, whoever builds it.