Brownfield Machine Data for Plant Modernization

Manufacturers can use machine data to improve maintenance and guide further modernization.

Connecting existing industrial equipment to new and advanced plant monitoring software gives manufacturers a comprehensive view of different operating data. The challenge then shifts to using this information efficiently to support predictive maintenance and dynamic production schedules.

As more assets are connected, teams need a manageable way to incorporate huge amounts of data into operations and decision-making. Otherwise, simply adding more data will increase the workload of reviewing it without making necessary upgrades to existing operations.

The first part of this brownfield modernization blog series discussed approaches to connecting isolated machines, monitoring motors, and adding vision inspection to production lines. Here, we explore how manufacturers can transform information into maintenance responses, organize mixed-generation equipment around consistent data models, and accurately measure modernization benefits against their full implementation costs.

Transforming Machine Signals into Accountable Maintenance Response

Let’s take an example of a motor monitoring system that reports abnormal vibration. Before maintenance teams can understand the reading, they need to know which motor it belongs to, its operating state, when the measurements were taken, and whether the data is still valid.

This context changes the maintenance team’s response. For example, vibration can rise during the motor start, but an increase that continues during steady operation requires closer inspection. Furthermore, if the measurements are outdated, it cannot establish the motor’s current condition, which can lead to false diagnosis.

An analytics platform organizes these measurements and compares them with established baseline operating rules. Depending on the equipment being monitored, the system can notify maintenance personnel only when a measurement deviation persists for a defined period. But some use cases may require a prompt alert because excessive delay can hide a developing problem.

When an anomaly triggers an alert, its severity should determine the response time. For example, a reliability engineer might review gradual drift during maintenance planning but arrange prompt inspection for a more consequential change. The notification should include the motor identity, recent trend, operating context, and data quality.

If inspection justifies maintenance, a work order in a computerized maintenance management system records the work and responsibility. The inspection findings and subsequent monitored conditions help the maintenance team assess whether the alert was useful and if its settings need adjustment. Ultimately, every actionable alert must lead to a defined response.

Organizing Mixed-Generation Equipment Around Consistent Data Models

Machines from different vendors may define an operating state differently.

For example, “running” could mean that one machine has received a run command and that another is actively producing parts. Engineers therefore need to check these definitions before combining the data. Gateways can translate the communication protocols and make the values accessible, but the state mappings still need to preserve what each machine reports.

For instance, Open Platform Communications Unified Architecture (OPC UA) gives measurements, states, and relationships of equipment in a structured information model. On the other hand, Message Queuing Telemetry Transport (MQTT) distributes published messages through a broker to subscribing applications. These technologies can work together, but neither protocol alone can ensure that applications interpret the information consistently.

Engineers can use a shared asset model to give each machine a persistent identity and organize its measurements, states, and events. They can then map machine-specific information into this structure, aligning names, engineering units, state definitions, timestamps, and data quality information.

From that point, the information can be organized and shared through a unified namespace, giving plant applications a consistent way to find the data they need. For example, an existing inspection result can be made available to production software along with its machine identity, inspection outcome, timestamp, and product context. Production software can then use the defined result without having to interpret the machine’s original data format.

Continue reading at Mouser

 

Sign up for our eNewsletters
Get the latest news and updates

Voice Your Opinion!

To join the conversation, and become an exclusive member of Machine Design, create an account today!