Establishing Orbit
Capabilities
All capabilities Operations & Transformation Consulting Shop Floor Digitisation Machine Connectivity & Integration Custom Software, Data & AI Adoption, Support & Scale
Company
The Connected Floor The Orbit Method Industries About Book an Audit →
Home/The Connected Floor
What We Deliver

Ten functions. One operating record. Zero rip-and-replace.

Your plant already runs all of this. The problem is that each function keeps its own version of the truth, in its own format, on its own timescale. The Connected Floor is what it looks like when they share one — sitting on top of the ERP and MES you already own.

The straight answer

What is the Connected Floor?

It is OrbitX's term for the end state of a shop floor digitisation programme: ten operating functions — production, quality, maintenance, safety, utilities and ESG, traceability, warehouse and supply chain, suppliers, workforce, and a control tower over all of them — running on one shared operational record, integrated with existing enterprise systems. Every event carries context: what happened, where, when, who acted, what was decided, and what happened as a result. Depending on fit, it is delivered on a manufacturing platform we implement and configure, on software we build, or on a combination of both.

CORE
The Shift

What actually changes on the floor.

Not an abstraction. This is the difference between a Tuesday before and a Tuesday after.

Before

Fragmented operations

  • Downtime reasons reconstructed from memory at the morning meeting
  • Quality records in binders; last quarter's are somewhere in a cupboard
  • Shift handover in a notebook and a messaging group
  • Preventive maintenance in a spreadsheet one person maintains
  • Energy known monthly, as a bill
  • Traceability answerable in days, by hand
  • Exceptions with no owner and no clock
  • Every department confident their number is the right one
After

One connected operating layer

  • Downtime logged as it happens, with reason, owner and response time
  • Inspection records filterable and exportable in seconds
  • Handover structured, complete and reviewable across shifts
  • PM scheduled, tracked and escalated automatically
  • Energy measured per unit produced, per shift
  • Backward and forward trace in a single query
  • Every exception carrying a named owner and an SLA clock
  • One shared record every function reads from
The Layers

How it's put together.

Four layers, built bottom-up. Skipping a layer is the most common way these programmes produce a beautiful dashboard nobody trusts.

01

Signal

Machines, PLCs, sensors, meters and instruments connected through edge gateways, with retrofit sensing where assets expose nothing. Protocols normalised into one structure.

02

Record

Operator capture, machine telemetry, material lots and system data written to one reconciled operational record — the shared truth every function reads from.

03

Workflow

Checks, approvals, deviations, work orders, permits and escalations configured to your process logic, with owners, due times and closure tracking.

04

Decision

Control tower views, automated reviews, cross-plant comparison, and analytics or predictive models where the record is deep enough to support them.

Why the order matters

Most stalled programmes started at layer four. A dashboard built on incomplete capture is worse than no dashboard, because people make decisions from it — and when the numbers are eventually shown to be wrong, trust in the whole programme goes with them. We build upward, and we're prepared to spend the first phase on unglamorous capture work.

Coexistence

It sits on top of what you already run.

No rip-and-replace. The systems you've already paid for keep doing what they're good at.

Your ERP stays

ERP holds the plan, the order and the transaction. We integrate to it — pulling production orders and BOMs down, pushing confirmed output, consumption and quality releases back — so plans and actuals reconcile without anyone re-keying at shift end.

Your MES stays

Where you have an MES, it keeps executing against work orders. We cover the connective layer around it — maintenance, safety, utilities, supplier quality, workforce — that MES scope typically doesn't reach, and read from it rather than duplicating it.

Your SCADA stays

SCADA does control and we don't touch that. We read from the existing system or historian to contextualise machine events, which is faster and considerably cheaper than any replacement programme.

Sequencing

Where plants usually start.

Attempting all ten functions at once is how a programme becomes an eighteen-month project that gets cancelled at month eleven. This is the sequencing that tends to work.

PhaseFunctionsWhy here
Phase 1
Prove it
Production & OEE, MaintenanceLargest measurable loss in a typical plant, fastest visible payback, and the data that makes the case for everything after it.
Phase 2Quality, SafetyHigh compliance value and strong frontline buy-in — these are the functions where digitisation visibly reduces paperwork rather than adding it.
Phase 3Utilities & ESG, Warehouse & Supply ChainSignificant cost recovery, and increasingly non-negotiable reporting obligations.
Phase 4Traceability, Suppliers, WorkforceDepends on the record built in earlier phases — genealogy is only as good as the capture underneath it.
Phase 5Control Tower, Multi-siteMeaningful only once enough functions are live to be worth a single view, and once the standard is stable enough to replicate.
Regulated plants differ

Pharmaceutical, food and medical device plants usually invert this — quality and traceability come first, because the compliance exposure outweighs the OEE opportunity. The audit determines the sequence for your operation rather than applying a template.

Questions

Frequently asked

No. It's the outcome we deliver, not a thing we license. Depending on what fits your operation, it's delivered by implementing and configuring a proven manufacturing platform, by building bespoke software, or by combining both with systems you already own. Because we don't own a platform, the choice is made on fit rather than on what we need to sell.
No, and most plants shouldn't start that way. Two functions done properly, with real adoption and a measured result, is worth more than ten deployed shallowly. The sequencing table above reflects what tends to work; the audit determines the right order for your plant.
A line pilot typically produces measurable results in six to ten weeks. A first plant-wide function deployment is usually eight to sixteen weeks. Anyone promising plant-wide transformation in under a quarter is describing a demo rather than a deployment.
Most get retired, because they were compiled manually from sources that now feed the record directly. A few get kept and repointed. Part of the design work is deciding which reports actually drive a decision — in most plants the honest answer is a minority of them.
Yes, that's the control tower function — consolidated views with drill-down from group to plant to line to machine. The prerequisite is that KPI definitions are standardised across sites, which is a governance decision more than a technical one, and it needs making early.
Related capabilities
Start Here

Find out which two functions to start with.

The Connected Floor Audit maps your operation, quantifies where the losses sit, and tells you what to digitise first — with costs and a sequence attached.