A simulator is a complex system of hardware and software components assembled and configured according to each customer's specific requirements. TechComm Simulation has developed the TICSS system as part of their on-going commitment to power plant business. TechComm Simulation has delivered over Fifteen utilising HP Tru64 (Compaq/DEC) Alpha computers running HP Tru64 and X-Windows. Microsoft Windows (r) based computers are configured as X-terminals. All requisite third party run-time software licenses are included.
TechComm Simulation also developed Linux-TICSS system which have a similar architecture as Unix operating system.
 

Benefits of UNIX-TICSS Simulation

• Drastically reduced need for writing computer code for modelling plant components and the interconnections between them

• Maximum re-use of standardised and proven code modules

• Limits potential for coding errors

• Simulator development can be application oriented - focus on plant simulation and performance tuning instead of coding

• Highly configurable - easy changes to both plant data and connections

• Configuration based primarily on plant data provides a ready source for documenting data requirements and design database

• Use of Unix/Linux gives a greater degree of platform independence and hardware can more easily be scaled according to customer requirements

Return To Top
 

Simulator Architecture

Each Unix/Linux-TICSS simulator consists of the following functional elements:

Common core components

• Instructor

• Executive

• Database Server

• IC Logger

• Messaging and Data Sharing Mechanism

• Application specific essential components

• Process Models

• Plant Controls

• Other application specific components

• Virtual Panel

• Emulated DCS

• Stimulated DCS

• I/O Panel Interface

Common core components

Instructor

The instructor is the user interface for the Simulator. It provides access to the simulator instructor functions through a Graphical User Interface and displays a variety of information covering simulator data, status, confirmation of operator action, on-line help and user guidance and trainee support. The Instructor provides the facilities that monitor and control the operation of the simulator and conduct training sessions. The user can display information covering simulator data, simulator mode, and confirmation of operator action. This information can be displayed either continuously or on user demand. The Instructor is a Unix process, which can be displayed on any simulator terminal. There is no limit to the number of Instructor processes active in a simulator at any one time. Typically, however, a single Instructor running on a dedicated terminal is all that is required.

Executive

The Executive controls and synchronises operation of the simulator components. Main executive functions:

• Co-ordinate the initialisation of simulator components.

• Schedule simulator cycles so that all processes remain synchronised.

• Ensure data is exchanged between real-time processes at the correct time and in the correct sequence.

• "Time-server" for the simulator, maintaining the simulator time in shared memory for other processes to read.

• Shared memory variable "server" for all instructor processes.

• Process malfunction scenarios and single malfunctions from the instructor.

• Alarm signalling.

Database Server

The Database Server is proprietary software with the following features:

• Provides a single database with uniform functionality for all simulator components.

• Multi-user access

• Processes are independent of the database implementation

• Processes and server may reside on different machines

• In the development environment, multiple projects may be supported by a single database or multiple databases

IC Logger

Simulator processes need to save and restore states upon demand and/or at periodic intervals.

The IC Logger provides a uniform, centralised mechanism for all processes that need to store and retrieve Initial Conditions, snapshots, backtrack and replay records.

Messaging and Data Sharing Mechanism

MDSM consists of two loosely coupled components, they are the:

1. messaging mechanism
   The messaging mechanism allows Unix processes to communicate to each other by sending and receiving binary messages. It allows a group of processes to communicate both within machine boundaries and across them.

2. data sharing mechanism
   The data sharing mechanism allows processes to exchange binary data. Processes may publish data items that are outputs which subscribe to data items (inputs) published by other processes.

TICSS ProModeller

The plant process models are simulated with TICSS Promodeller. It is organised as an integrated set of functional units:

• the Graphical User Interface (GUI)

• the Plant and Simulation Data Structures

• the Database Manager

• the Simulation Model Libraries

• the Simulation Configuration Builder.

UNIX-TICSS is completely data and table driven and produces no source code. The user enters plant parameters and configuration tables which completely define the components and interconnections of the simulated plant. These details cover all sub-systems of the plant - hydraulic, steam, air/gas and electrical as well as non-process elements such as actuators and transducers.

Other Simulator Components

COSLOG

Process controls are simulated with a tool known as Controls Simulation and Logic (COSLOG). The key attributes of COSLOG are that it is:

• a graphical process control data entry tool

• a code generator.

TechComm Simulation uses (COSLOG) to support the emulation of plant control systems, including: modulating loops;

• mode changing and status supervisory logic;

• interlocking logic

• sequence controls

• alarm formation

which includes integration of any or all of these within one control source schematic drawing.

COSLOG uses a graphical drawing tool to form schematics of the control systems, using the cursor to select function icons from a standard palette and to position them on the screen. The schematic is completed as the Technician joins appropriate outputs to inputs using the line-drawing function.

The COSLOG tool contains a library of models of standard control system logic and computation function blocks. Each specific instance of a control system function block module is configured by the definition of:

• a specific set of controller data parameters (as appropriate, since many function blocks require no configuring parameters); and;

• the input and output signals given by the interconnection table set up by the schematic drawing tool.

The COSLOG tool runs under Unix on the HP Tru64 (Compaq/DEC) Alpha. The output of the COSLOG code generator will compile and link directly into the Simulator.

Virtual Panel:

• Screen based

• Emulated control panel

• Animated panel equipment icons.

DCS/Control System

• Emulated Controls and Human Machine Interface

• Stimulated Controls and Human Machine Interface.

I/O Panel Interface

The I/O System is a set of microprocessor controlled panels which the Trainer and Trainees use to communicate with the simulator. Communication is achieved by the I/O System Interface that uses the I/O Signal File to carry messages between the Unix processes in the simulator and the I/O panel's microprocessors.

Return To Top
 

Basic Simulator Component Operation

Initialisation:

• Register itself by name with MDSM and the Executive

• Wait for Executive command: register variables to be Published

• Register all variables to be Published

• Wait for Executive command: register variables to be Subscribed

• Register all variables to be Subscribed.

Run time:

• Wait for start of cycle

• Read all subscribed variables

• Perform calculations and update outputs

• Advise Executive when calculations are complete

• Wait for publish command from Executive

• Publish all outputs.

Return To Top