Automation

Define data and control needs before automation

An automation request needs more than a screen or device selection. Start by defining what should be monitored and which decisions it should support.

An automation request needs more than a screen or device selection. Start by defining what should be monitored and which decisions it should support.

01

Distinguish monitoring from control

Viewing a value, generating an alarm and commanding equipment are different needs. Explain who will use each piece of information and why. Defined operating scenarios make the scope clearer than an undirected collection of data.

02

Review compatibility with existing systems

Devices, software and communication capabilities should be reviewed together. Approaches such as OPC UA support interoperability and structured information exchange, but a protocol name alone does not establish compatibility between every device. Specific implementation capabilities still need review.

03

Describe use and handover scenarios

Discuss user roles, how alarms will be handled and which records are needed during preparation. Describe the functions to demonstrate at handover and connections outside the scope. This creates a shared understanding of what the system will do.

Sources and further reading

OPC Foundation — Unified Architecture ↗
All articles

WORK WITH US

Let’s discuss your project.

Tell us what you need, and we can review the scope together.

Request a Quote0212 920 0 920