Who this is for: Production managers, IT teams and manufacturers considering new industrial software.
SCADA, MES and ERP answer different questions. SCADA supports process supervision; MES manages and records production execution; ERP supports business activities such as orders, purchasing and resource planning. Products can overlap, so their marketing category is not enough to determine the right choice.
Start with the problem that currently requires phone calls, separate spreadsheets or repeated data entry. Before adding another application, establish what the existing systems already provide and what information the people running production actually need.
Start with the decision the software must support
Write down three real situations: an operator needs to understand a stoppage; a supervisor needs to see which orders are in progress; an office team needs confirmed quantities for a delivery. These requests are related, but they may involve different applications and different update intervals.
For each situation, identify who acts, which information they need and what happens after the decision. Without that description, a dashboard can display plenty of data while leaving the operational problem untouched. The expected result should be something that the people using the system can demonstrate during an ordinary working day.
A practical distinction between the three systems
ISA-95 provides a reference for discussing the connection between manufacturing activities and business systems. The table turns that discussion into initial supplier questions. It is a starting point for assessment, rather than a mandatory division between commercial software products.
Scroll horizontally to see every column.
| Primary need | System to assess | Question to resolve |
|---|---|---|
| Plant states, alarms and process trends | SCADA | Which signals are available, and who may intervene? |
| Order progress, operations and traceability | MES | How are operations, quantities and batches linked? |
| Orders, purchasing and business resources | ERP | Which production information must be returned? |
| Information spread across applications | Integration | Which system owns the data, and how is it updated? |
References: ISA — ISA-95: Enterprise-Control System Integration
Define responsibilities before designing screens
Follow one representative order from confirmation through completion. Record where its identifier originates, who changes quantities, who assigns operations and where scrap is recorded. This exercise exposes duplication: two applications should not independently correct the same information without agreed ownership and reconciliation rules.
Also distinguish viewing information from sending commands that change a physical process. A connection to business software should not become an uncontrolled way to operate a machine. Industrial operational technology has particular availability, reliability and safety considerations; NIST’s OT guidance explicitly recognises these constraints. Decide which functions must keep working if an upstream application becomes unavailable.
References: NIST — SP 800-82 Rev. 3, Guide to OT Security
Compare configuration, integration and custom development
Ask for the whole workflow to be demonstrated using representative data. Existing functionality might need configuration and training; a limited gap might need an interface; an unusual process might justify custom development. Compare these options against the same requirements, including the awkward cases that a polished sales demonstration may omit.
Include licences, connectors, migration, shop-floor devices, support and upgrades in the cost comparison. Establish how data and documentation can be exported if the supplier changes. Starting with one department can help validate the approach, but the requirements for extending it to other areas should be understood before the first implementation is accepted.
What to prepare for a technical discussion
- Existing applications, versions and supplier contacts.
- One representative order and its complete operational journey.
- Three priority problems, their users and their practical consequences.
- The machines involved and documented interfaces already available.
- Rollout, shift, training and operational continuity constraints.
- Essential functions and improvements that can follow later.
Common questions
Does an MES always replace the ERP?
No. First decide which responsibilities belong in business software and which need to sit closer to production. Many projects require a controlled exchange between existing systems. Replacement only makes sense if analysis shows that the current application cannot support the agreed requirements.
Do we need to purchase all three?
Not necessarily. A business may need to improve one workflow, use existing features more effectively or connect two applications. The number of products purchased does not determine the quality of the result. Requirements coverage, clear ownership and usability are better decision criteria.
Sources and further reading
Apply this to your project.
Tell us which systems you use and where production work becomes difficult. We can help define the scope of the software and its integrations.
Discuss your industrial software