Download Presentation

Why Choose TiPS?

LogMate is the most reliable, proven software solution since 1990

    • Leadership Participation in Alarm Standards Committees
    • Dedicated Alarm Management Focus
    • Comprehensive Alarm Management Software Solutions
    • Adaptable Services Model
    • Flexible and Extensive Software Connectivity Portfolio
    • Broad Industry Experience

In a distributed design, one or more LogMate components may be separated and located on different computers. Following are a few examples of LogMate system designs using this approach:

Separate Data Node

A common distributed LogMate design separates the data collection and database node from the web services node. This maintains potentially sensitive data within the control network and requires only a single (non-HTTP) port open between LogMate Web Services and SQL Server®.

LogMate AMS Architecture Separate Data Node


Isolated Database

Many companies already have large database server farms. LogMate allows the use of an existing database server, leveraging existing IT assets and preventing any additional computer maintenance. When this design is selected, the LogMate data collection and thin-client server components may be combined or separated. The example graphic shows them as separate systems. This configuration requires only a single (non-HTTP) port open between LogMate Capture and SQL Server.

LogMate AMS Architecture Separate Database


Individual Data Collection Nodes (Store and Forward) – Example 1

Another design uses separate data collection nodes for each connected control system. These can create independent databases, locally or on a remote database server. This design is typically used on networks with poor reliability or chronic latency. In this configuration you can employ multiple firewalls between all LogMate components and between LogMate and browser clients. This can ensure that only the authorized LogMate database connection is allowed and only authorized clients are allowed to see data.

In this configuration, HTTP traffic across the firewall would be required if LogMate was to be accessed from outside the plant network. As in the centralized design, many other options exist, including redundant installations of web services and replicated databases on different network segments, eliminating the need for any open HTTP ports.

LogMate AMS Architecture Individual Data Nodes


Individual Data Collection Nodes (Store and Forward) – Example 2

This optional design places redundant web services and a replicated database on the “office network”. Doing so prevents the need for HTTP traffic between the plant and office network segments and still leverages the plant site database server which enhances data collection stability.

LogMate AMS Architecture - Individual Data Nodes With SQL Replication