Historian - TMOS SCADA - Turbine Monitoring System

Yesterday, today, tomorrow - analyze trends

Historian programs record and archive all the important plant process information such as alarms, events, measurements, calculations and outputs so that diagnostic and troubleshooting effort can be much effective and efficient.

TMOS SCADA's Historian can record any signals in its database at any selected sampling speed (up to max 1ms), provided that it is supported by the data supplier or control system. For example, Mark V can serve data request at a maximum rate of 31.25 millisecond (or 62.5 millisecond by older version of Mark V), and that sets a threshold for TMOS SCADA interfacing with a Mark V.

Data archiving can be stored in any storage mediums, from basic stand-alone hard disk drive to RAID arrays, Network Attached Storage (NAS), Storage Area Network (SAN) attached Hard Disk Drives, or clustered servers. Historian server programs that process the data search requests from client programs are also capable of being redundant to realize a robust network architecture.

Storage and Diagnosis


Easy made graphical presentation to be informed earlier

The trending tool in TMOS SCADA is known as the TrendViewer. This analytical tool is built to be intuitive and rich in features. It can be used to trend real­‐time (current), historical, or both signal values retrieved from the historian server.

TrendViewer is highly customizable. Built trend files can be saved for future reuse. Expanded or combined viewing options for Y-axis on different scales is possible.

Process Alarms, Diagnostic Alarms, Events and Digital Inputs Interlinked

Sometimes it is useful or necessary to correlate process values to the alarms and/or events. With Trendviewer, this dream has become a reality with its built-in function to retrieve historical DEA (Digitals, Diagnostics, Events and Alarms), that happened within the time frame of the trend. The dynamic scroll bar can be assigned to the DEA viewing object so that it will position itself according to the timestamp of a selected DEA.


Chronological sequence of past events

In the past, traditional HMI users had to rely on printers to record the occurence of alarms, for future reference when troubleshooting faults. This not only caused extra maintenance work but also made information searching and retrieval a hectic process. TMOS SCADA's Historian program captures and archives each and every status change of all process and diagnostic alarms. Storage and retrieval of the alarms historian is done with the highly efficient and centralized SQL engine.

Features of TMOS SCADA Alarms Historian

Events, Digitals and Syslog

Reduce to the essentials, monitor the operations

Apart from the alarms, GE SPEEDTRONIC™ control system has two more types of annunciator signal for Mark V and beyond. Events is a custom type of annunciator that is user definable using non-alarm and non-contact input type signals. The second additional annunciator is called Digitals or SOE in some contexts, recording status changes on digital contact inputs.

TMOS SCADA introduced one more annunciator type, known as the Syslog event, to help the system administrator keep track on all the events happening on the HMI level. Syslog records events like operators' actions (which buttons pressed, what setpoint entered etc.) and detection of fault or failure of a certain diagnosis process on a server or network component.

Time Referencing and Synchronization

Basement of comparability, clock synchronisation and ready to go

We recognize that it is crucial to establish a common time reference for the entire control network. Without a common time reference, an engineer or maintenance personnel may be misled and make a false decision when he or she is checking process information, especially when comparing data across multiple systems, during the troubleshooting process.

Each TMOS SCADA station is able to adjust its CPU clock proactively in respect of a time master, be it a GPS or network signal. In certain situations, TMOS SCADA can be a time master too. For example a TMOS SCADA server interfacing with SPEEDTRONIC™ Mark V, is able to be assigned as the time-sync master, sending periodic time-sync commands to all the nodes in a Stage Link network.

In situations where no good time reference is available, meaning that the TMOS SCADA and the control systems could be counting and recording time separately, TMOS SCADA will always refer to the signals, alarms and events as timestamped by the control system, for both displaying and historian archiving. The intention is to avoid the possibility of confusion to the users.

This implies, regardless of the physical computer where a TMOS SCADA display, alarm, historian is opened, or a notification received by a user, the timestamps will always be reliably accountable.

Screenshots >

If you have any  questions or requests, please contact us:

Fabriksplatz 1, 4662 Laakirchen, Austria


Mo - Fr: 6:00 to 16:00 (UTC)

Information about our other products you can find on the corresponding pages:

Premium Class Flame Scanners for Gas Turbines
GE™ Spare Parts
Turbine Control System MACH7 by ITS