Industrial IoT Software Development
Most industrial IoT guides are written by platform vendors counting your devices. This one starts from the plant: whether connecting the machines is worth it at all, platform versus custom development, what a digital twin actually requires — and per-machine costs before anything is committed.
What is industrial IoT actually for?
Industrial IoT (IIoT) connects production machines to software: sensors and PLC data flow off the equipment into systems that track output, downtime, quality, and energy — turning what operators currently write down, or nobody records at all, into live numbers a plant can act on.
The industrial half of the term is what separates it from smart-home gadgetry: industrial IoT survives heat, vibration, three-shift duty cycles, and networks that drop mid-shift. It is also the data layer under everything Industry 4.0 promises — an IIoT and Industry 4.0 roadmap are the same project wearing two names, and neither goes anywhere until the machines are actually connected. In practice, industrial IoT software development is three trades in one — controls engineering to get the data off the machines, systems engineering to move it reliably, and software to make it mean something — and projects fail when a team brings only one of the three.
What changes when the machines are connected?
Three numbers appear that most plants have never actually measured: true OEE instead of a guess — the OEE calculator shows what goes into it — downtime priced per hour as it happens via the downtime cost calculator, and energy per unit produced instead of per electricity bill.
The second-order change matters more: arguments end. When availability, scrap, and cycle times come off the machines rather than from three people’s notebooks, the morning meeting stops debating what happened and starts deciding what to do — which is where the payback actually lives. The same stream compounds quietly: IoT data analytics on six months of history finds the slow drifts — a machine losing three seconds a cycle, a shift running 4% more scrap — that no single day ever shows.
Do you need an IoT platform, or custom development?
The machine count and the oddity of your stack decide it. Under ~10 machines from one vendor, use the vendor’s own dashboard and don’t hire us — custom work would cost more than the insight. Past that, the choice is a platform configured to your plant or software built around it — and if the honest answer is “we don’t know yet,” a short consulting engagement to instrument one machine and look at the data beats either commitment; most IoT consulting services exist because plants bought the platform before the question.
| Your situation | Vendor dashboards | IoT platform (configured) | Custom development |
|---|---|---|---|
| Under ~10 machines, single vendor | Use what shipped with the machines | Overkill | Overkill |
| Mixed fleet, standard monitoring needs | Data stays in vendor silos | Best fit — one layer over every machine | Rarely worth it yet |
| Old machines, odd protocols, no two alike | No dashboards exist | Platform + custom connectors covers most | Justified where connectors don't exist |
| Telemetry must drive MES/ERP/twin logic | Cannot | Platform APIs get you partway | Best fit — the integration is the product |
How is an industrial IoT system architected?
Three layers, and the middle one decides the project. Sensors and PLCs speak whatever they were born speaking — OPC UA on modern equipment, Modbus on older lines, raw signals on the oldest. A site gateway translates those protocols for IIoT into one stream — MQTT, usually — buffers it through network drops, and filters at the edge so the cloud gets signal, not noise. The software layer turns the stream into dashboards, alerts, and feeds for other systems.
Edge versus cloud is not a religion, it is a latency budget: anything that must react within a cycle stays at the edge; anything that informs a decision tomorrow can live in the cloud. Plants that push every reading upstream pay cloud bills for data nobody queries.
What does industrial IoT development cost?
Per machine, not per project — that is the honest unit. Connectivity is the variable that moves quotes: a 2019 CNC with OPC UA costs a fraction of a 1998 press that speaks nothing. The downtime you already suffer prices the other side — the downtime cost calculator runs that number.
| Cost line | Platform route | Custom development |
|---|---|---|
| Pilot — one line instrumented (6–10 weeks) | $3,000–$12,500 | $10,000–$30,000 |
| Machine connectivity, modern (OPC UA) | $200–$400 per machine | $200–$400 per machine |
| Machine connectivity, legacy retrofit | $400–$750 per machine | $400–$1,250 per machine |
| Platform subscription | $1,500–$10,000 per plant/yr | None — you own it |
| Annual support | From $200/month | From $250/month |
Budget the pilot as its own decision with its own payback. A plant-wide quote given before one line has run is a guess wearing a spreadsheet. It is also the cleanest way to compare vendors: ask any IoT development company to quote the same one-line pilot, same machines, same outputs — the spread in those quotes tells you more than any capability deck.
Which IoT platforms are worth evaluating?
Five realistic routes and a build option. Intellyx is Perimattic’s own platform — its row carries the same honest-weakness column as the rest, drawn from deployments delivered rather than datasheets.
| Platform | Best fit | Strength | Honest weakness |
|---|---|---|---|
| Intellyx (Perimattic) | Plants that want machine data inside production tracking, not beside it | IoT telemetry lands directly in MES-style production, quality, and downtime views | Not a general IoT toolkit — built for factories, wrong tool for fleet or consumer devices |
| AWS IoT / Azure IoT | Enterprises with cloud teams in-house | Infinite scale, every integration imaginable | You are buying parts, not a product — the assembly is the project, billed monthly |
| ThingsBoard | Cost-sensitive plants with dev capacity | Open source, solid dashboards, own your stack | Self-hosting and upgrades are real work; manufacturing features are generic |
| Ignition | Plants with strong controls engineers | Unbeatable PLC connectivity, unlimited licensing | A toolkit, not an application — what you build on it is on you |
| Vendor ecosystems (Siemens MindSphere-class) | Single-vendor fleets | Deep integration with their own machines | Walled garden — the mixed fleet you actually have fits badly |
| Custom development | Odd machines, or telemetry driving core systems | Fits exactly; no per-device tax | You own the roadmap, which means you fund it |
Is a digital twin worth building?
A digital twin is a model of a machine, line, or plant fed by its live data — useful exactly in proportion to the telemetry behind it. A twin without machine data is a CAD file with marketing. That is why twin projects start where IIoT projects end: the data layer this page describes is the prerequisite, and digital twin data processing — cleaning, aligning, and contextualising the machine stream — is most of the build.
The honest maturity ladder: watch (a live mirror of current state — cheap, and where ~most of the value sits), predict (simulate what happens next — needs history and modelling), optimise(let the model tune the process — rare, and only after the first two work). Buy the ladder one rung at a time; vendors sell rung three, plants get their payback on rung one. In manufacturing, the twin’s first honest jobs are downtime prediction and what-if scheduling — both of which run on the same gateway data as everything else here.
Can 20-year-old machines be retrofitted?
Yes — retrofit is most of real-world industrial IoT, because the average plant is not new. Industrial IoT sensors bolt measurement onto machines that never had it: current clamps infer machine state from power draw, vibration sensors hear bearing wear, counters watch parts pass. None of it touches the machine’s controls, which keeps warranties and safety certifications intact.
The retrofit trap is instrumenting everything. Instrument the constraint line first; a plant that knows its bottleneck’s true state beats one with a thousand sensors and no question being answered.
How is industrial IoT secured?
IIoT security is mostly network discipline: machine networks segmented from office IT, the gateway as the single controlled crossing point, data flowing outbound only, and no PLC ever addressable from the internet. The dramatic failures in the news are almost always a violated version of one of those four sentences.
The operational half matters as much: unattended credentials rotated, gateway firmware patched on a schedule, and an inventory of what is connected — because the device nobody remembers is the device nobody patched. Treat the audit as quarterly hygiene, fifteen minutes with the gateway’s device list — not as a project that needs a committee.
How does IIoT feed MES, ERP, and the rest of the stack?
Telemetry is a means; the systems it feeds are the point. Machine states and counts flow into MES software for live production tracking; actuals roll up to ERP for costing; condition data trains failure prediction; camera-based inspection rides the same infrastructure.
Where each system sits in the full floor stack is mapped on the manufacturing software hub — and how the same data cuts unplanned downtime is worked through in how AI cuts unplanned downtime and defects.
Frequently asked questions
What is industrial IoT?
Industrial IoT (IIoT) is the software layer that connects industrial equipment - PLCs, sensors, motors, pumps, control systems - to a data platform that ingests, contextualises and acts on their telemetry. It turns machines that ran in isolation for decades into a plant-wide data stream, and lets the systems above (MES, ERP, quality, maintenance) work from live conditions rather than daily summaries or paper logs.
What are the 5 C's of IoT?
Connectivity, continuity, compliance, coexistence, and cybersecurity — a checklist for whether a deployment survives the real world: can devices connect reliably, run continuously, meet regulations, share crowded networks without interference, and resist attack. Industrial deployments live or die on the first and last.
What are the top 10 IoT platforms?
The names that recur are AWS IoT, Azure IoT, Siemens MindSphere, PTC ThingWorx, ThingsBoard, and Ignition — but platform lists are a weak way to choose. Machine mix, protocol ages, and what the data must feed decide fit, which is what the comparison table above sorts by.
Industrial IoT vs IoT - what's the difference?
Consumer IoT connects phones, watches, appliances, and thermostats over the public internet. Industrial IoT connects factory equipment over local, often segregated OT networks, using industrial protocols (OPC UA, MQTT, Modbus) rather than home-automation standards. The reliability, latency, and security expectations are also different - a dropped smart-bulb reading is invisible; a dropped machine event can scrap a batch or trip a safety interlock. The software patterns and the underlying network design differ end-to-end.
How much does an industrial IoT project cost?
A platform pilot on one line typically runs $3,000-$12,500 including sensor kits, edge gateway, and platform configuration. A custom-development pilot with bespoke integrations runs $10,000-$30,000. Plant-wide rollouts scale roughly with machine count but share landing-zone costs (identity, network segmentation, cloud back-end) - most plants land at $50,000-$250,000 for a full first-line-to-plant migration. Monthly platform support runs from $200/mo depending on managed-service scope.
How long does industrial IoT implementation take?
A single-line pilot on an off-the-shelf IoT platform runs 4-8 weeks from kick-off to first live telemetry, including sensor commissioning. A custom-development pilot with bespoke integrations runs 8-16 weeks. Plant-wide rollout after a successful pilot typically adds 3-6 weeks per additional line for platform-based work; sites that share a common machine profile finish faster.
How does industrial IoT integrate with SCADA and PLCs?
Modern PLCs (Siemens S7-1500, Rockwell ControlLogix, Beckhoff TwinCAT) speak OPC UA natively - the IIoT layer subscribes as an OPC client or brokers through MQTT/Sparkplug B. Older PLCs need a protocol gateway (Kepware, Ignition, Cogent) that translates their native protocol into OPC UA. SCADA feeds are consumed the same way. The rule: instrument the machine without modifying it - the retrofit sits outside the safety-certified envelope and adds no regulatory burden.
Is industrial IoT secure?
When designed correctly, yes. The standard pattern: OT (machines) and IT (corporate) networks live on separate VLANs with a firewall between them. IIoT edge components live on the OT side; the aggregated data and dashboards live on the IT side. Communication between them is one-directional where possible (OT publishes, IT subscribes) and uses signed messages with rotating credentials. Machines themselves are not exposed to the internet - updates arrive via the edge gateway. Compliance to IEC 62443 for industrial estates is the standard reference.
What are the main industrial IoT protocols?
OPC UA is the modern default for machine-to-platform communication - it's vendor-neutral, secure by design, and supported by every major PLC vendor. MQTT (typically with the Sparkplug B specification) is the standard for edge-to-cloud publish/subscribe. Modbus TCP and RTU survive on older machines. Between IIoT and enterprise systems, REST APIs and message queues (Kafka, RabbitMQ) are the norm. Field buses like Profibus, EtherCAT and CANopen sit below the IoT layer, on the machine side.
Which industries use industrial IoT most?
Discrete manufacturing (CNC lines, presses, packaging), process manufacturing (chemicals, food and beverage), utilities (water treatment, power generation), oil and gas (rotating machinery, pipeline compressors), and logistics (warehouse automation, cold chain). The common thread: expensive equipment, unplanned downtime costs an order of magnitude more than the sensor investment, and existing SCADA/PLC infrastructure that IIoT extends rather than replaces.
Instrument One Line First
A 6–10 week pilot on your constraint line: machines connected, data flowing, downtime and OEE measured for a month — then a plant-wide decision made on numbers. Fixed scope; if the data says stop, stop.