Application guide · 13 September 2026. Illustrative project guidance; verify device, version and license compatibility separately.
Map existing connections
In an established plant, SCADA, maintenance and reporting clients may belong to different teams while connecting to the same PLC. Record existing clients and communication load before adding another connection. Check supported connection counts and access methods in the device documentation. Network reachability alone is not enough to approve an integration.
Choose a representative dataset
Select a small set of tags that describes production: state, counters, key process values and the identifiers that explain them. Expand by device group and critical function. Observe device response and existing system behavior at each step. Choose sampling rates around the reporting need rather than defaulting to the fastest possible read.
Start with the required access only
Establish whether the pilot only needs reads and avoid unnecessary write permissions. Back up project files and schedule changes in a maintenance window. Changing firmware, drivers and server versions simultaneously makes it harder to identify the cause of a problem. Split independent changes into separate, verifiable steps.
Leave a standard for expansion
Document naming conventions, timestamp handling and fault monitoring alongside the working connection. Later lines should be able to reuse these decisions. Verify Kepware driver and option selection for each device family. Pilot evidence informs the next stage; it is not a performance guarantee for the entire plant.
Review with your team
- Existing clients and load understood.
- Pilot tag scope limited.
- Only necessary access granted.
- Rollback steps tested.
