Custom performance displays, andon and OEE dashboards for manufacturing

It varies — scope, integrations and on-site access all move the number. As a rough guide, most first-line installs land in eight to sixteen weeks from kick-off: around two weeks of discovery, six to twelve weeks of sprint build with weekly demos, then commissioning. Multi-line and multi-site rollouts extend from there.

Yes — that's the usual pattern. A single-line pilot shakes out the integration assumptions and KPI definitions with minimum risk. Everything we build is designed to scale horizontally; additional lines, cells or sites reuse the same data model and dashboard framework.

You own the source and the deployment. We offer an optional retainer for new lines, evolving KPIs, integration changes and infrastructure support — but it isn't a lock-in. Some clients take the handover and run it themselves; some keep us on for years.

If your kit emits a signal, we can build the bridge — that's the whole point of bespoke. Production integrations to date have run over SQL and MQTT; OPC-UA and HTTP are familiar territory, REST is routine, and for historians and time-series databases we fit to whatever you already run. The protocols we haven't touched yet are, by definition, exactly what bespoke engagements exist to handle.

No. We sit alongside them. The MES remains the system of record for orders, routings and genealogy; our work is the shop-floor-facing layer — andon, OEE, performance displays — that consumes MES data and adds the operator-facing visibility it typically lacks.

We defer to whatever network architecture and change-control rules your OT and IT teams already operate. Data flows are designed with your security team in the loop, not around them, and we don't push control signals back to the floor unless the scope explicitly requires it and it's been signed off.

Productised tools front-load low and back-load high: modest first-line licences, with per-line, per-machine or per-user fees that compound across the estate and the years. Bespoke front-loads the build cost, then flattens — you pay for engineering once and for optional support thereafter. Whether bespoke wins on total cost depends on how many lines you have, how long you plan to run the software, and how much customisation you'd otherwise pay the productised vendor to bolt on.

The source code, the data model, the deployment configuration, and the documentation. Nothing phones home. You can host it in your cloud, your on-prem, your hybrid, and you can hand it to another developer to maintain if you ever need to.

Yes — we engineer in the UK and deliver for clients worldwide, with on-site discovery and commissioning visits where the work warrants them. Time-zone overlap with Europe and the Middle East is comfortable; the Americas and APAC need more scheduling discipline around live demos.