Manufacturing Software Development
Manufacturing software sits between two worlds with incompatible assumptions: plant-floor equipment that may be twenty years old and cannot be casually patched, and business systems that expect modern APIs.
- Reply within one business day
- NDA on request
- No obligation
Constraints specific to manufacturing
The problems that shape software here, and that generic engineering tends to discover late.
Operational technology cannot be treated like IT
Machine controllers run for years without patching because downtime is measured in lost output. Anything touching that network has to work within constraints IT security practice would normally reject.
Traceability to lot and batch level
When a defect surfaces, the question is which units are affected and where they went. That requires genealogy recorded continuously during production, because it cannot be reconstructed afterwards.
Plant data is high-volume and mostly uninteresting
Sensors produce readings continuously, and the vast majority are never queried. Deciding what to aggregate at the edge versus retain at full resolution is the difference between a useful system and an expensive one.
The network is not the office network
Plant floors have interference, physical separation and equipment that predates modern protocols. Connectivity assumptions from an office environment do not transfer.
Software we build for manufacturing
Production monitoring
Real-time visibility of line state, throughput and downtime, with the loss categorisation needed to make efficiency figures actionable.
Traceability systems
Lot and serial genealogy captured through the process, so a recall query returns a definitive answer rather than an estimate.
Planning and scheduling
Production scheduling against real constraints — machine availability, changeover cost, material supply — integrated with ERP rather than duplicating it.
OT/IT integration
Bridging SCADA, PLC and historian data into business systems through a boundary that respects the isolation the plant network requires.
Standards that apply to software in this sector
What the software has to be built to satisfy. Which of these apply to you depends on your jurisdiction, your data and your customers.
[ 01 ]
Industrial cybersecurity
- IEC 62443
[ 02 ]
Quality management
- ISO 9001
[ 03 ]
Regulated production
- GxP
- 21 CFR Part 11
[ 04 ]
Product identification
- GS1
- UDI
[ 05 ]
Information security
- ISO/IEC 27001
These are the standards we design and build to meet. Certification or attestation of your organisation is a separate exercise, carried out by a qualified assessor — we can support that process with documentation and evidence, but we do not certify it.
Tell us what your plant floor can't see
Discuss a manufacturing projectHow we'd approach it
The service lines this sector most often needs.
IoT & Connected Devices
Connectivity, telemetry pipelines and fleet management for physical estates in the field.
Custom Software Development
Bespoke systems shaped around your operations, integrated with the tools and data you already run on.
Data Analytics & Engineering
Pipelines, warehousing and reporting built so the numbers reconcile and people act on them.
Cloud & DevOps
Migration, deployment automation and infrastructure on AWS, Azure and Google Cloud, built to be operated.
Manufacturing: common questions
Something specific to your operation?
Send it over — sector questions are the ones we most like getting.
Ask us01
Can you connect to our existing PLCs and SCADA systems?
Usually, through OPC UA where equipment supports it, or through the historian or vendor interface where it does not. The approach depends heavily on equipment age, and the constraint that matters most is that plant networks are generally isolated for good reason — so the integration is designed around that boundary rather than through it.
02
How much sensor data should we actually store?
Considerably less than the equipment can produce, in most plants. Aggregating at the edge and retaining full resolution only around events of interest — alarms, deviations, quality failures — typically preserves everything anyone actually queries at a fraction of the storage cost.
03
Do you replace our MES or ERP?
Rarely, and usually we would advise against it. The more common and more valuable work is building what sits between and around them — the visibility, traceability and reporting those systems do not provide well — while leaving transactional systems of record in place.
04
How do you handle security on a plant network?
By treating the OT boundary as real. Data generally flows outward to business systems rather than allowing inbound control paths, segmentation is preserved, and IEC 62443 informs the architecture. Where remote control genuinely is required, it is designed explicitly with its own controls rather than arriving as a side effect.
Adjacent sectors
Tell us what your plant floor can't see
Describe your equipment, what data it produces and what operations needs to know. We'll come back with an approach.
- Reply within one business day
- NDA on request