Choose an article
Get started
Prepare a PlantWatch rollout
Define the production questions, data sources, infrastructure, and technical contacts needed for a focused PlantWatch rollout.
Updated
Begin with a production question
A focused rollout starts with the information the production team needs—not with a list of every available PLC tag.
Useful first questions include:
- Why did production stop?
- Which events occur repeatedly?
- How do shifts or time periods compare?
- Which process values changed before a fault?
Choose one machine, line, or production area for the first scope. Additional data sources can be added after the initial view is useful.
Identify the data sources
Document the controllers, machines, and existing interfaces in the selected area. Relevant data commonly includes operating states, alarms, counters, loads, temperatures, and other process values.
PlantWatch can use interfaces such as OPC UA, Siemens S7, Modbus TCP, databases, or APIs. The appropriate route depends on the installed controllers and network design.
Prepare the infrastructure
The installation needs network access to the selected data sources and an on-premise server, virtual machine, or industrial PC. Keep controller or interface documentation available where possible.
PlantWatch does not require a PLC replacement, a new HMI, a SCADA migration, or a cloud connection.
Assign technical contacts
Nominate someone who understands the production process and someone who can clarify controller and network access. These roles can be covered by the same person in smaller installations.
The production contact confirms whether the resulting views answer the original question. The technical contact supports data access and commissioning.
Review before commissioning
- The initial production question is clear.
- The machine or area is defined.
- Relevant controllers and interfaces are known.
- Network access can be provided.
- On-premise compute is available.
- Production and technical contacts are assigned.
For a detailed technical checklist, continue with Integration and system requirements.