A simulator is a complex system of hardware and software packages assembled and configured according to each customer's specific requirements.

TechComm Simulation has developed not only the Unix based simulators, but also the Windows based simulators as part of their on-going commitment to power plant business. To date, TechComm Simulation has successfully delivered five Windows NT simulators to power plant industry, one running in Australia and the other four running in Central America. TechComm Simulation has developed very powerful simulators, which run on Windows NT/2000/XP with model/component drag and drop and C/C++ executable file linking.

Benefits of WIN-TICSS Simulation

• Improved GUI (Graphical User Interface ) compared to that on Unix

• Drastically reduced needs for writing computer code for modelling plant components and the interconnections between them by using drag and drop technology.

• 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 Windows NT/2000/XP allows the users to maintain the simulator more easily with flexibility of hardware to be scaled according to customer needs easily.

Return To Top
 

Simulator Architecture

Windows based simulators are designed by using distributed system principles, running on latest Pentium based personal computers. The simulator consists of one server (called master, running on the computer server) and a number of clients ( running on the computer workstations) interconnected through TCP/IP via an Ethernet local area network However, the Windows based simulators can run on only one single computer, even a notebook computer through TCP/IP via no Ethernet connection.

The TICSS NT simulator consists of the following functional elements:

Common Modules

• Master

• Instructor

• ProModeller

• LogicDisplay

• Synchroscope

Application specific Modules

• DCSClient

• IOClient

• EmuDCS

• FDT

• TRU

• Off-line Modules

• TSLogic

• CMS

Common Modules

Master

The master, controls and synchronises operation of the simulator components which includes Main executive functions:

• Communicates via an Ethernet link to clients.

• Access any type of relational databases using ODBC (Open DataBase Connectivity) interface.

• Manages simulation calculation, real time data storage and exchange management.

• Schedule simulator cycles so that all clients remain synchronised.

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

• Process malfunction scenarios and single malfunctions from the instructor.

• Saves/Loads IC/Snapshot or backtrack and Replay

• Alarm signalling.

Instructor

The Instructor system consists of one VDU and keyboard. And is the user interface for the Simulator. It provides access to the simulator instructor functions through a GUI 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 as a client is connected to the Master via Ethernet. The Master on the computer server acts as its server, which handles all of the instructor function requests:

• Selects Simulator Operating Mode:

• Recall Backtrack Record State.

• Initial Condition Management:

• Malfunction Management:

• Trip Inhibit,

• Select Simulation Speed,

• System Maintenance Functions,

• Database Functions,

• Video Trend Display Functions,

• Training Exercise Operations,

• Diagnostic Functions.

Promodeller

The Promodeller is part of the WIN-TCSS (TechComm Simulation Model Drag and Drop Tools). This tool contains all functionality of both the Promodeller and the TSLogic modules which is a powerful off-line visualisation tool for logic sheet, power plant network configuration, relational database table creation, and C/C++ source code generation through drag and drop on the drawing windows.

Normally the Promodeller consists of many DLL modules linked by the master, but it can be an executable module as a client connecting to the Master via Ethernet by the customers' request.

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

• Graphical User Interface (GUI) when runs in stand-alone

• Model Calculation

• Simulation Configuration Builder

• C/C++ source code generation based on the plant network configuration

• Database Access

• Simulation Model Libraries

• Simulation Configuration Builder.

Promodeller is completely drag and drop driven and automatically generates source code. Plant parameters and network configuration for interconnections of the simulated plant, and their corresponding tables will completely generated by the user dragging and dropping the ICONS (components) and enters their properties on the drawing windows. 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.

LogicDisplay

The LogicDisplay module is used to display logic sheets which run time dynamic behaviour. Users can use this module to debug those sheets previously generated by the off-line module (TSLogic). The LogicDisplay as a client is connected to the Master via Ethernet

Synchroscope

The Synchroscope module emulates hard synchroscope functionality by display bus voltages, frequencies, turbine speed and phase needle rotation. It indicates when synchronisation is permitted and when operator can close circuit breaker. Synchroscope as a client is connected to the Master via Ethernet

Application specific Modules

IOClient

The IOClient module interfaces with third part hardware IO systems (panels). It initiates the requests to scan any input data (Digital and Analog) from panels and to send out applicable new I/O output data (Digital and Analog) to panel using TCP/IP via Ethernet.

Normally the IOClient is a DLL module linked by the master, but it can be an executable module as a client connecting to the Master via Ethernet by the customers' request.

DCSClient

The DCSClient module is only applied to a stimulated simulator. Generally the DCSClient is a DLL module linked by the master, but it can be an executable module as a client connecting to the Master via Ethernet by the customers' request.

A typical DCSClient module is a link between the Master and the DCSServer, which communicates with DCS and is written by calling DCS API supplied by the DCS vendor. The DCSClient transfers DCS signals between the Master and the DCSServer.

EmuDCS

The EmuDCS (Emulated DCS) module is only applied to the emulated simulator. It acts as a client connecting to the Master via Ethernet.

The EmuDCS emulates the functions of DCS owned by DCS vendor. Normally the customer specifies what kind of DCS need to be emulated.

FDT

The FDT (Field Device Terminal or sometimes-called Remote Function) module is primarily intended to allow operation of valves and other equipment that can not be controlled from the simulator panel. This includes manually operated valves and motors with only local stop/start stations.

The FDT is arranged in a group/subgroup structure, with a group representing a plant area and each subgroup representing an individual FDT graphic screen.

The FDT as a client is connected to the Master via Ethernet.

TRU

The TRU (Turbine Run Up) module is optional based on the customer demand. The different project has different functionality. It as a client is connected to the Master Computer via Ethernet.

Off-line Modules

TSLogic

The TSLogic is also part of the TCSS NT (TechComm Simulation Model Drag and Drop Tools). TSLogic is an object-oriented logic control drawing MFC (Microsoft Foundation Class) application with ANSI C/C++ source code generation support for each logic control sheet. TSLogic will meet the following requirements:

Icons (referred to as gates) are selected from a menu or a toolbar and placed anywhere on the screen (or logic control sheet).The gates are interconnected to show data flows. Control sheets are automatically checked for errors and then ANSI C source code for any computer, programmable controller or control system is generated. The code produced can be either compiled by C/C++ compiler and loaded into the computer or directly loaded into the programmable controller or control system. Once the code has been generated, TSLogic has an automatic dynamic status display for debugging, which displays the actual values of operands on the graphic drawing. These values are displayed on the inputs and outputs of the gates and are a very effective way of debugging the program. The target computer sends the required data back cyclically to the PC running TSLogic either via a network or serial link. TSLogic automatically generates the ASCII net list file for dynamic status display including operands.

Relational database accessed using ODBC for the project and specific hardware data with a flexible graphic drawing user-interface will be integrated in TSLogic which include the following key features:

• Easy to use for new or experienced operators.

• Automatic ANSI C code generation.

• Relational database for project management and symbolic addressing.

• On-line debugging during actual program execution (option)

• Off-line simulation of user programs without target system (option).

• Automatic line drawing "auto-routing" (option)

What is the CMS ?

The Configuration Management System (CMS) provides an integrated support and quality assurance functionality for a project from the initial design phase through to the end-of-life.

o   To provide storage and version control of the documents generated during the project’s life-cycle.

o   To provide a common storage location for design information, construction data, test results, discrepancy reports, customer requests, and for cross referencing between this information.

The CMS is built on top of Microsoft Access® [relational database] and uses forms to provide an easy to use graphical interface.  All data is entered through form templates, and the resultant data is stored in tables.

The CMS uses Visual Basic for Application to automate complex operations within the database.

The CMS provides database management facilities such as:

o   automatic database defragmentation & compacting.

o   table import and export

o   queries and reports

The CMS can be on Windows NT/2000/XP operating system.
 

Return To Top