working with indiss 122000 1/1 - · pdf fileworking with indiss 122000 1/1 working with indiss...

Working with INDISS 122000 1/1

WORKING WITH INDISS

Version Reference Causes de l’évolution / Reasons of evolution Date

1 122000 création 17/06/03

Written by Checked by Approved by

JTO \\Ws023\documentation\IndissOnline\WorkingWithIndiss\hardwareandhandling.doc-17/06/2003 ? RSI. Unauthorised reproduction strictly prohibited


Table of contents

\\Ws023\documentation\IndissOnline\WorkingWithIndiss\hardwareandhandling.doc-17/06/2003 ? RSI. Unauthorised reproduction strictly prohibited

1. HARDWARE CONFIGURATION...........................................................................................3

2. INSTALLING INDISS............................................................................................................3

3. WORKING WITH FILES .......................................................................................................4

4. USING TOOLBARS .............................................................................................................6

5. STARTING & STOPPING INDISS .........................................................................................7

6. INDISS SIMULATORS AND COMPONENTS.........................................................................9

7. NETWORKING ENVIRONMENT .........................................................................................11

8. CONNECTION TO THIRD PARTY SOFTWARE ..................................................................14



1. HARDWARE CONFIGURATION

System requirements for installing INDISS INDISS needs a personal computer (PC) with the following minimum configuration:

Processor : Pentium

RAM : 32 MB

Hard disk: 400 MB

Media : CD-ROM

Video : SVGA, 800x600, 256 colours

Mouse : MicrosoftTM Compatible

Operating System: MS Windows NT 4 and 2000

The full capabilities of INDISS can be obtained with the following recommended configuration:

Processor : Pentium 200 M Hz or higher

RAM : 128 MB

Hard disk: 1 GB or more

Media : CD-ROM

Video : XGA, 1024x768 or more , 16 bits colours with Windows accelerator

Mouse : MicrosoftTM Compatible

Operating System: MS Windows NT 4 and 2000

2. INSTALLING INDISS

INDISS package contains:

? a CD ROM of the INDISS simulation environment

? a hard key (dongle),

? a floppy disk containing the file "licence.dat”.

First, the hard key must be installed on the parallel port of the computer.

INDISS is delivered on CD-ROM. The media contains the file Setup.exe that helps you to install INDISS automatically.

First place INDISS CD-ROM on the drive (supposed afterwards to be D: ), and then select the Windows Start ? Run menu...

... to run the program: D:SETUP.EXE.



The rest is entirely automatic ! You will get self-explanatory indications as the installation progresses.

At the end of the software installation, the licence file will be requested. Just insert the given floppy disk containing the file "licence.dat" and follow the instructions.

Important:

You do not have to be an expert in computer science in order to use and enjoy working with INDISS.

All that you need to know are a few simple operations like the use of menus, selection of objects using the mouse pointing device, drag-and-drop objects, scroll bars etc... If necessary, ask an experienced colleague to show you these operations.

INDISS gives you an on-line help facility, to explain operations necessary for working.

3. WORKING WITH FILES

INDISS uses files to store de various components of the simulator. You will have to know about these files to manage the simulator and understand how it works. The type of files is identified by the extension:

.sim Simulator: contains the description of all components and configuration options of the simulator. This is the file that allows you to select your workspace.

.wsm Process Diagram: contains the description of the simulated process and initial conditions.

.syn Mimic Display : contains the description of one mimic display (a mimic display can include other mimic displays and recursively to any number of levels)



.wda Process Diagram data : snapshot (or backtrack) file containing initial condition data associated with a process diagram.

.sc Indiss Scenario: file containing a series of actions to be loaded within an exercise.

.exr Training Exercise : contains the description of training exercises configured for trainee evaluation.

.ope Trainee Evaluation: contains the description and results of a trainee evaluation.

.dll Unit Operation Library: contains the programs that compute Unit Operation models.

The following files are associated with each simulator, but you should not have to manipulate them:

.thd Thermodynamic data configuration : contains the description of thermodynamic data configured for the simulator (only for process models using the INDISS HPI models library)

.ord Calculation order: contains manually configured Unit Operations calculation order.



4. USING TOOLBARS

INDISS provides toolbars for the most commonly used menu commands.

Toolbars are selected by use of the following dialog:

The following figure shows a summary of currently available toolbars:



Toolbars can be moved into the top or left margin of the window.

5. STARTING & STOPPING INDISS

Starting INDISS You can start INDISS just like any other MS-Windows program, by a double click on the INDISS icon in the start menu, or by a double click on the icon of a ".sim" file in the explorer.

The base window of INDISS will then be displayed. Select the simulator by use of the File/Open/Simulator menu:



An explorer window allows you to move to the desired directory:

Once you have selected the file, the simulator is loaded into INDISS.



From this point you can access all the INDISS facilities, running or freezing the simulation is achieved through the Simulation/Run menu:

INDISS comes with demonstration files, which will help you to learn using the software.

Stopping INDISS You must know how to stop and come out of INDISS gracefully... If you wish to stop INDISS, on the main menu: select the option File and then select Exit. It may sometimes be necessary to cancel/abandon an operation you are doing currently, before you can exit INDISS.

INDISS will ask you to confirm your decision to exit or ask you if you wish to save the files you are using. At this point, you can also Cancel your decision to Quit, if you have changed your mind. Select Yes for saving if you so wish. Select No if you do not wish to keep a copy, and would like to start afresh. This second option may be useful if you have made too many errors and do not wish to retain the erroneous files.

Never stop INDISS without going through the above procedure e.g. do not switch off your PC when INDISS is running. You can destroy many important files and INDISS may not function correctly thereafter.

6. INDISS SIMULATORS AND COMPONENTS

INDISS contains a set of tools for creating simulators, and for conducting simulation sessions. You must know a few fundamental concepts and terminology for using INDISS. Although we have kept these to a minimum, we strongly recommend that you read the next few paragraphs very carefully.

The INDISS window is organised as follows:



The window is organised into 3 main zones:

? the simulator components (shown as a tree) in the left-hand side

? the toolbars (optional) in the upper part

? the process view in the right-hand side.

The "Simulator" is the highest level of organisation in INDISS. It defines all the components that are going to be used. Different simulators can exist on you disk, stored on corresponding directory. When you start -up INDISS, you will be asked to select the name of the simulator you want to use.

The two types of simulator components are:

? "Process diagrams" that define the process to be simulated,

? "Mimic displays" that provide a graphic human machine interface (HMI) to operate the simulated process.

"Users" may connect to INDISS by using the Viewer application and display a human machine interface to operate the simulated process.

A component can be selected by clicking on its icon. When selected, the component is displayed in the right side of the INDISS window. Only one component can be selected at the same time.

Users access level INDISS has four access levels:

? Maintenance : which gives full access to all functionality,

? Engineer : for simulator developers,

? Instructor : for training and course preparation,

? Trainee: restricted to simulated process operation only.

The default value when you log in INDISS is Trainee. You can then change to another level, each level might be protected by a password.



The "Window menu", "Toolbars" and "Toolboxes" will allow you to carry out the various tasks you expect from the simulator. Depending on the selected component and on your access level, they will show different possible actions.

7. NETWORKING ENVIRONMENT

INDISS offers the facility to allow multiple users to connect to the current simulator. This connection is designed to allow multi-users training sessions.

To achieve this networking capability, two extra software components need to be used: the INDISS POSTMASTER and the INDISS VIEWER.

The POSTMASTER is used to allow the communication between INDISS and the connected INDISS VIEWERS . This communication is based on the TCP/IP protocol.

The VIEWER can be used as a remote Mimic Display running on another machine and communicating with INDISS through a Local Area Network. Several instances of this component can run at the same time on various machines on the network and even on the same machine. VIEWERS need to have access to the application files through a shared folder (to be able to read displays files).

To use the INDISS networking capability the system must run the Windows NT operating system.



To accept connections from the VIEWERS , INDISS must establish the connection to the POSTMASTER. This is achieved by the following dialog:

Where you have to type the name of the PC where the postmaster is running.

To set-up a Viewer on a remote machine:

1. Share the directory where the simulator is located in the host machine.

2. On the remote machine, create a shortcut on the Viewer.exe program

3. Specify the directory of the target simulator in the command line of the shortcut.

Example:

The simulator is located in the computer named HOST1, in the directory C:\INDISS\simulator1. This directory is shared as \\HOST1\simulator1 by HOST1.



On the remote computer named HOST2, where the VIEWER.EXE file is located in C:\INDISS, we can call a view on the simulator by creating a shortcut as follows (the location of the shortcut itself is not significant):

NB: in the Diagram/Options menu of the simulator, the graphic libraries must be defined using the network path instead of the local path (i.e. \\HOST1\INDISS\Mmi instead of C:\INDISS\Mmi) in order to have the Viewer displaying graphic elements correctly.



Users To be authorised to connect to the simulator, users must be declared in INDISS (you can declare as many users as required).

To create a new user, just select the folder "Users" and click on the right button of the mouse.

For each user you will define a name, a password, an access level (trainee or instructor) and the mimics that will be displayed when the user logs in.

8. CONNECTION TO THIRD PARTY SOFTWARE

INDISS Object-Oriented:

INDISS is the result of an object-oriented development of ten years. The software is coded in C++ under Windows environment. The opening of its architecture is visible in multiple functionalities:



- development of Unit Operations is independent from INDISS software. They can be produced into dynamic libraries and then loaded by INDISS. All the loaded objects are available under the flow-sheet editor.

- INDISS proposes its internal thermodynamic package, and an external thermodynamic package is also available to provide thermodynamic calculations in specific conditions.

- INDISS provides a Graphic User Interface builder. This tool is used to build customer interface based on a standard simulator.

INDISS client/server architecture

INDISS OLE interface :

INDISS takes advantage of being developed under MicrosoftTM tools by providing several levels of MicrosoftTM interfaces. INDISS is a server that presents OLE interfaces. Those interfaces allow simulation monitoring and access in reading and writing mode to each Variable of INDISS Unit Operations. It is useful to automate test sequence and provide automatic report. This link is easy to establish under Excel or with Visual Basic.

Component Object Model (COM) and can be seen as a code maintenance utility. This is a programming model that defines the way in which software components communicate and provide services to another, regardless of where the components reside. COM is a standard that provides for language independence and location independence. COM is the MicrosoftTM Middleware and INDISS can use COM objects. The interfaces in Computer Aided Process Engineering are standardised in CAPE-OPEN. INDISS is using COM objects for thermodynamic calls.

INDISS and CAPE-OPEN:

INDISS is able to use an external thermodynamic server to perform all calculations of the specified thermodynamic area. The thermodynamic calls from Unit Operations are linked to the external CAPE-OPEN thermodynamic server.

INDISS and DCS interface :

INDISS can be connected to several DCS. The connection is established with FOXBORO DCS by using FSIM software from ESCOR, or with YOKOGAWA CS3000 DCS by using the EXATIF software from OMEGA. In each case, INDISS uses a cross-reference file to link tagnames from INDISS simulation and tagnames from DCS. The connection is based on RPC protocol that is independent from computer operating system.

This interface provides several services from INDISS:

- starts and stops DCS execution

- saves and loads data snapshots

- transfers cross data between INDISS and DCS on each computation step

- changes computation time

INDISS DDE:

INDISS has the capability to exchange data with any other application using Dynamic Data Exchange (DDE). In this context INDISS behaves only as a server. This means that any client application can ask the "INDISS" application on the "SIMULATION" Topic for INDISS items. INDISS items are any expression involving simulation Variables for the running simulator. The expression should be between quotation marks if it includes array brackets.

The usage in an Excel spreadsheet should use the following syntax:

=INDISS|SIMULATION!10V1002.Pressure or

=INDISS|SIMULATION!'10K1002.FlowArray[1]'

The following sample uses VBA to invoke dynamic data exchange with INDISS from any other application to evaluate the INDISS expression 10V1001.Pressure*100000:



'Connect to INDISS

Chanel = DDEInitiate("INDISS", "SIMULATION")

'Execute the request

returnValue = DDERequest(Chanel, "10V1001.Pressure*100000")

'close the DDE communication

DDETerminate Chanel

INDISS and Active X

INDISS and XML

INDISS and OPC:

OPC is an emerging software standard designed to provide automation applications with easy access to industrial plant floor data. The goal of OPC is to define a standard interface based on MicrosoftTM's Component Object Model (COM) technology that allows greater interoperability between automation and control applications; control devices; and business and office applications.

Using OPC, INDISS can communicate directly with:

? any OPC server:

Indiss

OPC client

DCS

OPC server

? or any OPC client like iFix supervisor:

OPC server

Indiss

OPC client

iFix

INDISS and PITM DataBase :

INDISS is capable to dialog with OSI Software’s PITM real-time database. The PITM Universal DataBase Server (PITM -UDS) is used to store the results of INDISS simulations, and client applications, such PITM ProcessBook (PITM graphical user interface) are used to view data.

DCS can be connected with the PITM -UDS using PITM-interface. INDISS can read all values recorded in PITM-UDS, and therefore the DCS values.



Indiss simulatorPI

Measuredvariables

Archivedvariables

Configuration file :- List of archivevariable - link Indiss variable /PI tag

PI-SDK :-Connection-SetPIValue-GetPIValue

PI-UDS server

DCS

User interface PIPI-Interface

DataBase

working with indiss 122000 1/1 - · pdf fileworking with indiss 122000 1/1 working with indiss...

Documents