Industrial software

Custom industrial software, written by people who know the line.

Supervision web apps, apps for operators and maintenance, web-based HMIs, and integrations: the tools that connect production processes to the information needed to run them. Built by the same team that programs the PLCs the data comes from.

What we build

Supervision and dashboards

Plant supervision web apps and management dashboards: production status read from the same data that runs the line.

web apps · dashboards · KPIs and OEE

Apps for operators and maintenance

iOS and Android mobile apps for operators, maintenance, and field technicians, on the phone or tablet they already use.

iOS · Android · shop-floor tablets

Web-based HMI

Web-based operator interfaces reachable from panel, tablet, or workstation, consistent across the stations of a line.

web HMI · touch · IT/EN

Data collection and maintenance

From field data collection to maintenance planning: scattered readings that become a schedule of interventions and a KPI analysis.

data collection · planned maintenance · KPI analysis

Machine and process configuration

Tools for machine configuration and process parameters, with values that reach the machine instead of staying in a spreadsheet.

configurators · process parameters · OPC UA

Integrations and APIs

APIs and integrations between the systems already in use — MES, SCADA, ERP, WMS — so the new software doesn't become another island.

APIs · MES · SCADA · ERP · WMS

Custom or product

When a product is enough

Line supervision, OEE, traceability, warehouse: problems many factories share, where a product already in production costs less and starts sooner. That's what ARIA is for.

ARIA MES/SCADA · ARIA Warehouse · ARIA HMI

When custom is needed

A process that is your competitive edge, a system no product knows, a flow that fits no catalogue: that's where custom software pays off.

specific processes · existing systems · own flows

When you need both

A platform for the common part and a custom module for the part that's only yours, on the same data: often the shortest path in a plant with a history.

platform + dedicated module · shared data

How we work

Start from the data

Before the screens, where the data comes from: PLC, SCADA, MES, ERP. People who program PLCs know what comes out of the field and how reliably.

Designed for the shop floor

Gloves, touch screens, shifts, and haste: the interface is designed for the people using it in production, not for a meeting room.

OT security from the start

Software that talks to PLCs is part of the OT infrastructure: network segregation, access, and permissions are decided at design time, not afterwards.

After release

Factory software changes with the factory: teleservice and ongoing development with the same people who wrote it.

ARIA platform

Discover the ARIA platform

MES/SCADA, Warehouse, and HMI already in production: the common part, without writing it from scratch.

IT/OT integration

Go to IT/OT integration

Connectivity between PLC, MES, and ERP: consistent data from the field to the business system.

OT cybersecurity

Go to OT cybersecurity

IT/OT segregation, hardening, and access management to IEC 62443 and NIS2.

Frequently asked questions

What is industrial software?

It's software that manages, controls, or improves a production process: from the logic in PLCs to SCADA supervision, from the MES that runs production to the apps operators and maintenance use. It differs from business software for a practical reason: it works on field data, often in real time, and an error stops a machine rather than delaying an invoice.

Custom software or a standard product?

It depends on how common the problem is. Supervision, OEE, traceability, and warehouse are problems many factories share, and there a product already in production — like ARIA — costs less and starts sooner. Custom pays off where the process is specific or a system no product knows needs integrating. IOMA does both, which is why it can recommend the shortest path rather than the one on its price list.

Can the software read data directly from PLCs?

Yes, and that's the right way to do it: IOMA connects software to controllers over OPC UA or the S7 protocol on Siemens PLCs, and exposes the data to the other systems from there. The PLC stays the process source of truth; the software observes, records and, where intended, sends parameters through defined channels.

Does it run on shop-floor tablets and smartphones?

Yes: IOMA builds web apps that open from panel, tablet, or workstation, and native iOS and Android apps when device features are needed. The choice is made on the work to be done — who uses the software, where, with which gloves and which network — not on the format that's easiest to develop.

Does it integrate with our ERP?

Yes, through APIs and data exchanges agreed with the ERP vendor: orders, master data, consumption, and progress flow both ways. IOMA designs it as part of the software, not as an export at the end of the project, because that's where shop-floor data becomes business data.

Who maintains the software after release?

IOMA, through teleservice and ongoing development: factory software changes when machines, products, and processes change. Before starting it's still worth putting in writing what gets handed over — documentation, environments, access — with any supplier: it's the condition for not being tied to a single person.
Let's talk

Got a project in mind?

Describe the line and the problem on a 30-minute technical call: we tell you straight away whether it's in our wheelhouse. We typically reply within 24 hours. From the first call to commissioning, you speak to the same person.

Let's talk about your project

Or:explore the ARIA platformhey@ioma.ai