Blog

How to Connect New Machines to Your Existing SCADA System.

Plan SCADA system integration with PLC checks, tag mapping, network security, historian setup, testing, and alarm validation.

By ITHENA ITHENA Insights 5 min read

TL;DR

Connecting a new machine to an existing SCADA system starts with understanding the PLC interface, the data the plant needs, and the controls and security boundaries already in place. Agree on tag names and meanings, map signals, test data quality, configure historical storage where needed, and validate alarms with operators before production use. A staged commissioning plan helps avoid confusing displays and unreliable records. ITHENA's SELEE case study describes onboarding a new kiln into an existing Ignition environment, including PLC tag connectivity, SQL database integration, operator screens, and alarm workflows.

Key Takeaways

  1. Confirm protocols, data ownership, network boundaries, and required signals before connecting.
  2. Map and test tags with consistent names, units, timestamps, and machine context.
  3. Validate screens, history, alarms, and failure behavior with controls and operations teams before handover.

Quick Q&A

What should I check before connecting a new machine to SCADA?

Confirm the PLC make and communication options, available tags, network and security requirements, time synchronization, naming conventions, historian needs, and the plant's change-control process. Identify which system owns each value and which teams may read or write it.

Does a new PLC need the same protocol as the existing SCADA system?

Not always. The SCADA environment may support multiple drivers or use a gateway, but compatibility, licensing, security, and maintainability must be checked for the specific versions and architecture. Validate the selected method with the controls team and equipment supplier.

How do I test SCADA alarms for a new machine?

Test each alarm condition, threshold, priority, text, routing, acknowledgement behavior, and return-to-normal state using an approved commissioning method. Confirm that alarms are meaningful to operators and do not create duplicate or nuisance notifications.

Integration area Check Validation
PLC communication Protocol, driver or gateway, address, version, and read/write scope. Confirm expected values update and connection-loss behavior is visible.
Tags and context Naming, units, scaling, quality flags, machine identity, and timestamp. Compare sample values with PLC and operator observations.
Historian Required tags, sampling or event rules, retention, and database ownership. Verify stored values, time alignment, and retrieval for representative events.
Alarms and screens Thresholds, priorities, operator workflow, navigation, and access. Run approved alarm tests and collect operator feedback before release.

Table: PLC-to-System Integration Verification Table.

Integrating New Industrial Equipment into Existing SCADA Systems

1. Define the use case and boundaries.

Begin with the operational questions the connection should answer. Do teams need current run state, temperatures, cycle counts, recipe or batch context, alarm history, or a production total? Document the signals and intended users instead of forwarding every available PLC tag by default.

Map the existing architecture: machine PLC, plant network, SCADA server, historian, MES or reporting applications, and any approved gateways. Decide which system is authoritative for each value. Follow plant cybersecurity and change-management procedures, including access controls, network segmentation, backup, and a rollback plan. Do not make direct write access available simply because read access is needed.

2. Review PLC protocols and tag definitions.

Ask the machine builder for its PLC model, firmware, communication details, tag export, data types, units, scaling, and any restrictions. Check what the installed SCADA version supports and whether an existing standard driver or gateway is appropriate. Verify that the selected connection is supported by the plant team.

Create a mapping between machine tags and the plant's naming convention. Record tag meaning, engineering units, valid range, update behavior, and quality or status indicators. Include context such as line, asset, product, and shift when needed for later analysis. Test representative values against the PLC and the machine's own HMI.

3. Configure historian and alarms deliberately.

Decide which signals need historical storage and whether they should be sampled periodically or captured on events. Confirm retention, time synchronization, database ownership, and how missing or bad-quality values will appear. A trend without consistent timestamps or units can create false conclusions.

For each alarm, document the condition, operator action, priority, delay or deadband if applicable, recipient, and reset behavior. Test alarms with authorized procedures and involve operators in reviewing message clarity. Check for chattering, duplicate alarm sources, and conditions that should be events rather than alarms.

4. Test, commission, and hand over

Test in stages: confirm network reachability, validate tag reads, check scaling and status, verify trends and stored records, and exercise alarm scenarios. Record expected and observed results. Test connection interruption and recovery so operators know how the system indicates stale or unavailable data.

ITHENA's SELEE industrial monitoring case study describes integrating a newly commissioned kiln into an existing Ignition V8.1.12 environment. The published example includes direct PLC tag connectivity, MS SQL database integration, operator visualization, trending, and alarm drill-down. It also notes challenges around tag mapping and database integration. Treat this as one documented project, not a promise that every integration has the same scope or outcome.

5. Plan for maintenance

Keep the tag map, connection settings, network diagram, alarm list, test evidence, and ownership details with the plant's controlled documentation. Agree who manages PLC changes, SCADA changes, credentials, backups, and future machine upgrades. Re-test affected tags, alarms, and historical records after a relevant change.

An MES may consume selected production data for execution and reporting, but it serves a different operational role from SCADA. ITHENA describes its MES services as providing manufacturing visibility and integrating disparate systems. Determine which layer should own each workflow before duplicating logic or records.

Conclusion

Reliable SCADA system integration is built on clear signal definitions, controlled connectivity, and evidence from testing. Scope the operational need, verify protocols and security, map tags with context, configure history and alarms, and commission with the people who will use the system. A documented handover makes the connection easier to support as the machine and plant evolve.

Sources

  1. ITHENA SELEE metal filtration case study: new kiln integration into Ignition, PLC tags, SQL integration, visualization, and alarms.
  2. ITHENA Manufacturing Execution System: published manufacturing visibility and integration service description.
  3. ITHENA Industrial IoT: supplied internal destination; page retrieval timed out during drafting.

Next Step

Start with one machine and document its signals, owners, network path, and alarm test plan. Discuss manufacturing integration with ITHENA.

Get started

Connect one line. See the deviation before it becomes downtime.

Start with one line on your own data and expand use case by use case.