Single pane of glass for all AVEVA and Wonderware SMC logs
Reviewing System Management Console logs is the chore nobody volunteers for. Process LogShip collects them from every machine, consolidates them in SQL Server, and forwards them to a central web Receiver.
Process LogShip is a single pane of glass for all AVEVA and Wonderware System Management Console (SMC) logs from the entire network. Galaxy Repository, Historian, all AOS machines, all InTouch HMI and OMI stations. All logs in one place. It helps immensely to quickly discover issues with new development or ongoing system maintenance. Its deduplicated logs can be ingested by Power BI or Syslog.
Developed in house as an add-on for AVEVA and Wonderware System Platform or InTouch applications.
The chore nobody volunteers for
We all have done it. Multiple SMC windows open to review logs across multiple machines, often over a single RDP or VPN screen. Filtering by timestamp or other columns. Stitching events together by hand because the messages are scattered across multiple machines.
The pain is not that SCADA, HMI and MES logs do not exist. It is that they are machine centric rather than system centric, hard to search, and bloated with repeated errors over and over.
So we built Process LogShip, because we got tired of watching good operators and engineers spend mornings on log archaeology.
A tool that does the boring things right
Process LogShip collects SMC logs on each individual machine and consolidates them in a SQL Server database, local or remote. From there we forward the logs to a central web-based Receiver for single pane of glass analysis. While consolidating the logs, we deduplicate and auto-purge messages according to criteria you define.
The Receiver can be located on either the OT or the IT network. For the IT network we use outbound HTTP and HTTPS only, the same as AVEVA Tiered Historian does. Deduplicating repeated messages lets the reviewer concentrate on analysing what is actually happening. The Receiver can also serve data to a Syslog server or to Power BI for further analysis.
What that looks like on a real system
This is a textbook example of how Process LogShip helped us clean up a customer's logs. From more than 40,000 errors and warnings daily down to almost zero. By deduplicating repeated errors, LogShip allowed us to focus on addressing specific issues one by one and get the system to a clean state.
If you are interested in how Process LogShip can help your operations, we would love to talk.