SIMULATION SYSTEM, METHOD FOR CARRYING OUT A SIMULATION, GUIDANCE SYSTEM, AND COMPUTER PROGRAM PRODUCT

Abstract

A simulation system, in particular for a control system, which controls a process running in a technical system, is provided. The control system has at least one first process environment embodied as a container and which is also designed to simulate the automatic process to be run in the system and includes corresponding interfaces to the guidance system. The simulation system has, in addition to the first process environment, a second process environment embodied as a container for simulating the hardware of the periphery of the guidance system. In another embodiment variant of the simulation system, both of the process environments can also be combined to form one process environment. In both variants, the interfaces of the first process environment are practically identical to the interfaces of the second process environment. A method for carrying out a simulation and a corresponding control system and computer program product are also provided.

Description

FIELD OF INVENTION

The invention relates to a simulation system, in particular for a control system which controls a process running in a technical installation, the control system comprising at least one first execution environment which is in the form of a container, is designed to simulate the automation process on which the installation is based and has corresponding interfaces to the control system. The invention also relates to a method for carrying out a simulation using the simulation system according to the invention. A corresponding control system and a computer program product are also stated.

BACKGROUND

In large-scale technical installations, for example power plants, training simulators are being increasingly used in order to train control room personnel for operation of the power plant and in order to train them for exceptional situations and critical operating states which may occur during actual operation of the power plant. However, simulators are also used for test purposes during the engineering of a technical installation in order to make it possible for a project engineer to find optimal solutions for the connection of functions inside the technical installation or to detect faults before the installation is implemented and thus to shorten start-up.

A simulator is generally a computer system in which processes of a technical installation can be carried out or illustrated under realistic conditions.

In the power plant sector, for example, a power plant is, in principle, simulated in the simulator as software. In order to simulate the operation of a power plant as realistically as possible on a computer, it is necessary to simulate both the process engineering process, which runs in an actual power plant and affects the operating behavior and interaction of the power plant components, and the automation engineering process, which comprises the process control system used for operation and control with its automation and operation and observation components, with the aid of complex software. The simulator accordingly behaves in an identical manner to the actual power plant. If the power plant is run with a particular control system, for example the Siemens SPPA-T3000 control system, all details on the simulator screen correspond to those from the control room of the actual installation.

Simulation computers which are independent of the control system, that is to say are a separate computer system, are usually used to simulate power plants. The effort required for this usually requires a gigantic computer power of the simulation computer used. The hardware for the simulation computer must be constructed, installed and maintained at each place of use.

Nowadays, there are two different simulator approaches (cf. also description of FIG. 1A): simulators in which the operating and observation system of the original control system is used, and simulators which also concomitantly simulate the operating and observation system of the control system, that is to say the entire user interface—however, this is very complicated and the results are generally also unsatisfactory. This solution is usually only used in older control systems, for example if the operating and observation system cannot be simulated because there is no simulator time support, for example.

There are often simulators which have separate computers for the hardware, which is the automation servers of the control system and the hardware connected to the control system such as I/O subassemblies, motors, valves etc., and for the physical process on which the technical installation is based (cf. also description of FIG. 1A).

In both cases, the software, like the hardware of the simulators, is decoupled from the control system. Parts of the original software engineering data relating to the automation of the control system are often used, that is to say the inputs for the simulation software receive values from the control system which are written, however, to software separate from the control system. Furthermore, the configuration of these simulators is very complex (sometimes not accessible at all to the user in the case of process simulators) and is carried out using configuration tools of a completely different type to those of the control system. A consistency check between simulators and the control system does not take place. In addition, the configuration of simulators generally does not take into account the engineering data relating to the cabling or wiring of connected hardware (sensors, actuators).

SUMMARY OF THE INVENTION

Therefore, an object herein is to specify a simulation system, as a result of which the simulation becomes an integral part of a control system. This object is also to specify a control system with an integrated simulation system. Another object is to specify an improved simulation method. In addition, the intention is to specify a corresponding computer program product embodied on a non-transitory computer readable medium.

These objects are achieved by the features of the independent patent claim. Advantageous refinements are respectively described in the dependent patent claims.

In an embodiment, the simulation system herein comprises execution environments for automation and for simulating the hardware of the peripherals of the control system. Both execution environments have the same interfaces and are connected to the bus system via these interfaces. The execution environments may also merge to form a single execution environment.

In addition, each execution environment may itself be a software component. Inside the execution environments and software components, there are embedded software components as representatives of functions, subassemblies and devices.

As a result of the simulation system herein, the automation function itself and the simulation of the hardware of the peripherals of the control system are incorporated in the software of the control system. In a control system having a universally usable execution environment for software components, this execution environment may now be used both in the normal control system in real time for the automation of a power plant, for example, and in other entities in order to simulate the hardware. The simulation of the entire automation operation and of the hardware of the peripherals of the control system advantageously take place here in one entity. For this purpose, the module library only needs to be expanded with simulation modules for the hardware of the peripherals of the control system.

In this manner, the control system and the hardware simulator merge, in terms of software and therefore also in terms of computer technology, to form a unit, which entails numerous advantages:

The simulation system is configured using the same engineering or planning tools as the configuration of the control system.

The simulation system is planned with graphical tools using modular technology, just like the planning of the actual installation inside the control system.

As a result of the use of the same tools for configuration and planning, a consistency check between the automation and simulation is possible for the first time. All functions of the control system can therefore be ensured with the greatest degree of reliability.

A result is a simplified simulation system for training and test purposes. This results in reduced downtimes during operation of a technical installation, shortening and improvements during start-up and improved simulation quality since there is consistency within the entire simulator solution and everything runs on one platform.

Some of the terms used in this application are explained below in order to ensure the same understanding:

A program which includes software code that can be directly executed on an operating system and which is closed to the outside, with the result that communication with other software components takes place only via exactly defined interfaces to other software components, is generally referred to as a software component. An embedded software component is a software component which is embedded in another software component. Although it is likewise closed to the outside and communicates only via exactly defined interfaces to other software components, it is not directly executed on the operating system but rather in the environment of the software component surrounding it.

A program which includes directly executable software code, has at least one interface to an embedded software component and at least one interface to the operating system and is directly executable on the operating system is referred to as a container in computer science. A container which, for its part, is in the form of a software component and forms a universally usable execution environment for one or more embedded software components is referred to as an “execution container” below. The execution container is therefore, on the one hand, a coupling element between any desired embedded software component and the operating system and makes it possible for the embedded software component to run on the computer. On the other hand, it also facilitates and manages, in its property as a software component, communication between the embedded software components and other software components outside the container by means of external interfaces.

In this context, an entity should be understood as meaning the specific use of a type of software component in the system.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is explained in more detail below using exemplary embodiments which are illustrated in the drawings, in which

FIG. 1A shows a block diagram of a possible implementation of a control system of a technical installation with its hardware components (prior art),

FIG. 1B shows a schematic illustration of the control software of an exemplary control system (prior art),

FIG. 2 shows a schematic illustration of a first embodiment variant of the simulation system according to an embodiment, and

FIG. 3 shows a schematic illustration of a second embodiment variant of the simulation system.

DETAILED DESCRIPTION

FIG. 1A illustrates, in a simplified form, the block diagram of a possible implementation of a control system of a technical installation. Only the hardware is shown in this illustration. The underlying physical process to be controlled using the control system is illustrated by the box P. This may be, for example, a process for producing energy in a power plant, refuse incineration or a chemical process. In principle, the process on which the technical installation is based may be a physical, chemical, biological or other technical process. The signals recorded using sensors are forwarded to input and output subassemblies EA1, EA2 to EAN. These may be pure input/output subassemblies or else intelligent field devices. At the same time, control signals are also forwarded to the field devices in the process via the subassemblies EA1, EA2 to EAN. The bidirectional signal flow is illustrated by the arrows. The subassemblies EA1, EA2 to EAN are connected, on the side remote from the process, to an external or internal bus system BS which collects the signals and forwards them, for example, to at least one automation server AUTS. The subassemblies EA1 to EAN may also be intelligent field devices in which the sensor and/or actuator is/are integrated together with processing logic in a device which is directly connected to the automation server AUTS via the bus system BS. The automation server AUTS in turn—as stated in this example—may be connected to at least one application server APPS via a communication bus KB. For reasons of availability, any connections between the servers and buses are generally usually redundant, which is indicated by the double connecting lines. Any desired user interface is also connected to the communication bus KB. This is any desired graphical user interface GUI. These may be thin clients, for example. GUI should be understood here as meaning any operating and observation systems, engineering clients or other display systems.

As already stated in the introduction, prior simulation systems are usually designed in such a manner that either a very powerful computer which simulates the entire user interface GUI of the control system (as indicated by the box SIM1 in the figure) is provided or a separate simulation computer SIM2 rather than the automation server AUTS is accessed via the user interface GUI of the control system. The latter solution may also be implemented by means of two computers, for example by means of a computer SIMHW, which simulates the hardware of the underlying automation process, and by means of a computer SIMP which simulates the underlying process.

FIG. 1B illustrates a possible embodiment variant for the software architecture of an exemplary control system as described in FIG. 1A using the hardware. In this exemplary embodiment, the control technology software has been reduced to a few components in order to ensure a better overview: the basic functions which can be mentioned here are presentation software 51 which makes it possible to present a wide variety of operational images. This may be, for example, a web browser which runs on a thin client. The execution environment is denoted by 50. There are also numerous software modules, for example 61, 62 and 63, which are responsible, for example, for engineering the installation, archiving data, message management or resource management. All of these software modules therefore perform different functions. They may run in a separate execution environment which is denoted by 60 here. All of the software modules are connected to one another, that is to say data can be interchanged between all modules.

The automation function of the control system is illustrated in this exemplary embodiment by separate software. This is an execution container 10, that is to say a container which, for its part, is in the form of a software component 1 and forms a universally usable execution environment for one or more embedded software components 101, 102, 111 and 112. The execution container 10 manages and carries out all existing automation functions including the processing functions. The execution container 10 typically has a plurality of interfaces. An interface is used to mean a data interface below. This may be, for example, an interface 13 for the engineering or the interfaces 11 and 12 which are connected to the remaining control technology, inter alia also to other entities of an execution environment. In addition, interfaces for diagnosis, for particular messages or for operation may be provided. Embedded software components 101 and 102 are illustrated inside the execution container 10 in FIG. 1B. Said software components in turn have internal standardized interfaces which are illustrated as dots. The embedded software components 101 and 102 contain main functions such as all automation tasks, control operations, regulating operations, calculations, processing functions, alarm management and execution management.

Furthermore, so-called representative modules 111 and 112 are illustrated inside the execution container 10. The representative modules substantially represent existing hardware components, for example an input or output subassembly. Their software is illustrated by 81 and 82 here. The representative modules 111 and 112 ensure that the input raw data are connected to/from the field devices and monitor them and are therefore responsible for communicating with the field devices. The bus interface 18 is used for this connection. This interface of the execution container 10 leads to an automation bus (bus interface to the bus system BS) via which the input and output subassemblies and the intelligent field devices are connected to the automation server. The representative modules 111 and 112 inside the execution container 10 communicate with the input and output subassemblies (and intelligent field devices) which are indeed outside the automation server (and therefore outside the execution container 10) via this interface. Depending on the design, the automation bus may be, for example, a Profibus, a Modbus, another serial bus or else an Ethernet-based bus (for example Profinet or pure TCP/IP or UDP-based communication).

During ongoing operation of the control system, the software component 1 and therefore also the software components 101, 102 and representative modules 111 and 112, which are embedded inside 1 and are connected via their internal interfaces in such a manner that the entire automation process is implemented, are executed.

FIGS. 2 and 3 illustrate embodiment variants of the simulation system herein. This is respectively software architecture which can be directly combined with the architecture shown in FIG. 1B and is connected to the latter.

In this first exemplary embodiment in FIG. 2, the simulation system 100a comprises, in addition to the execution environment 10 for the automation function described in FIG. 1B, a further execution environment 20, which simulates the hardware of the peripherals of the control system with all of its connections in software. So-called representative modules 211 and 212 which represent the control system peripherals which are connected, for example, directly to the bus system BS from FIG. 1A are embedded in this execution environment 20. These may be, for example, subassemblies, other bus connection modules, intelligent field devices such as actuators (actuating drives, motor controllers) and sensors or else communication modules for third-party systems. The software component 201 simulates, for example, the behavior of an actuating drive with open or close commands and corresponding feedback or simulates the behavior of the withdrawable part of the switchgear for a motor of a process engineering component. For this purpose, the software modules 201, 211, 212 each have internal interfaces via which, for example, physical variables or other data and parameters can be interchanged. The connecting lines between the individual modules and interfaces represent this signal interchange which is carried out in the actual installation using existing cables/wires in the control system or by means of data transmission in field bus systems, for example. (Depending on the wiring or cabling variant, clamping points may also be included, for example, as distributors or repeaters on the field bus. These components are not illustrated in the diagram for the purpose of simplification). The representative modules 211 and 212 are formed inversely to representative modules 111 and 112. In this case, inversely means that inputs and outputs of the respective interfaces have been swapped. Whereas a representative module of the type 111 and 112 generally ensures that the input raw data are connected to/from the control technology interface, a representative module of the type 211 and 212 already simulates a subassembly and is therefore responsible for converting the field data into the input raw data for higher software modules. Furthermore, both actual process variables and predefined or simulated variables can be supplied to the representative modules.

The entire execution environment 20 can now be in the form of an execution container according to the container definition described above or may be in the form of a software component 2. In both cases, there are a particular number of external interfaces, for example 21, 22 and 23, which make it possible to communicate with the other program parts of the control system. Like the interface 13 of the first execution environment 10 responsible for automation, the interface 23 may be responsible for filling the container with engineering data and may be connected to the component bus 90. The software components 1 and 2 and the execution environments 10 and 20 can communicate via the interfaces 18 and 28. Depending on the type of bus, the interface 28 is either identical to the interface 18 (generally for Ethernet-based bus systems) or, depending on the bus system, provides the complementary interface to the interface 18 (generally for serial bus systems with a master/slave functionality). In addition, there may be a further interface 24 which allows connection to the process. This interface 24 can be used to transmit process data which are transmitted from a process simulator, i.e. a simulation computer responsible for the technical process.

According to an embodiment, the interfaces 11, 12, 13 of the first execution environment 10 (responsible for the automation of the control system) are virtually identical to the interfaces 21, 22, 23 of the second execution environment 20 (responsible for the hardware of the peripherals). This means that the two containers 10 and 20 communicate via the same interface(s) which leads to the control system. The interfaces 11, 12 and 13 are designed in exactly the same manner, in terms of their function and physically, as the interfaces 21, 22 and 23. Minor changes for adaptation to particular boundary conditions may be possible.

In a second embodiment variant which is illustrated in FIG. 3, the two execution environments 10 and 20 have been combined to form a single execution environment 15. In this embodiment variant, the simulation system 100b now has only one execution environment. This may also be designed as a software component 15′. Embedded software components and representative modules of the individual software components 1 and 2 are now executed in an execution environment 15. Previously container-encompassing connections between the embedded components and modules from previously 10 and 20 now become container-internal connections. Previously external interfaces now become internal interfaces (included in the container). The connections between the representative modules 111 and 112 of the first software component 1 and the representative modules 211 and 212 of the second software component 2 are one example of this. At least the interfaces 11, 12 and 13 are now available for communication with the control system. A further interface 24 which allows connection to the process may also be additionally provided here.

Irrespective of whether the simulation system is now formed from two execution environments for automation and hardware of the peripherals of the control system according to FIG. 2 (variant 100a) or both functions are executed in one execution environment according to FIG. 3 (variant 100b), there are different possibilities for connecting process data. The latter may be gathered from a process simulator 200, for example.

According to FIG. 2, the process simulator 200 can be directly connected to the simulation system 100 via various interfaces. On the one hand, the process simulator 200 may be connected to the interface 24 of the hardware simulator via an interface 33 additionally provided for this purpose. On the other hand, the process simulator 200 can be connected by converting the interfaces 11, 12 or 21, 22 of the simulation system 100 to interfaces 31, 32 of the process simulator 200. In another embodiment variant according to FIG. 3, it is also possible to connect the process simulator 200 via an adapter 99 specifically provided for this purpose. In this case, a program for assigning and converting any desired process data may be involved. In this case too, connection to the simulator 100b is possible via an interface 24 specifically provided for this purpose or by converting interfaces 11 and 12.

The control system or parts of the latter is/are now simulated as follows:

The first execution environment 10 is produced using a planning tool of the control system.

The second execution environment 20 with all embedded software components, for example 201, the representative modules 211, 212 and connections is likewise produced using the planning tool of the control system previously used for the first execution environment.

The execution environment 10, which is designed to simulate the automation process on which the installation is based with its connections, is then changed to a simulation mode without changing the existing planning.

In a next step, the execution environments 10 and 20 are executed either separately or together, in which case the technical installation or parts of the technical installation is/are simulated.

Claims

1. A simulation system for a control system which controls a process running in a technical installation, the control system comprising at least one first execution environment which is in the form of a container, is designed to simulate the automation process on which the installation is based and has corresponding interfaces to the control system, wherein, in addition to the first execution environment, the simulation system comprises, at least one second execution environment which is in the form of a container, designed to simulate the hardware of the peripherals of the control system with its connections and has interfaces to the control system and at least one further optional interface which can be used to transmit process data, andwherein the interfaces of the first execution environment are virtually identical to the interfaces of the second execution environment.

2. The simulation system as claimed in claim 1, wherein the execution environments are themselves software components.

3. The simulation system as claimed in claim 1, Wherein communication between the first execution environment or the first software component and the second execution environment or the second software component is carried out via bus interfaces.

4. The simulation system as claimed in claim 1, wherein the first execution environment and the second execution environment are combined to form a single execution environment.

5. The simulation system as claimed in claim 4, wherein the execution environment itself is a software component.

6. The simulation system as claimed in claim 1, wherein the execution environments or the software components comprise embedded software components and representative modules which are connected to one another according to a function, and wherein the software components and representative modules are executed when this function is called.

7. The simulation system as claimed in claim 6, Wherein the second execution environment comprises embedded software components and representative modules for subassemblies and devices, including their networking or wiring in the peripherals of the control system.

8. The simulation system as claimed in claim 7, Wherein the interfaces of the representative modules (211, 212) of the second execution environment are formed in such a manner that they simulate the interfaces of the inputs and outputs of the wire connectors of the control system.

9. The simulation system as claimed in claim 7, wherein the representative modules of the second execution environment are formed inversely to representative modules of the first execution environment, with inputs and outputs of the interfaces being swapped.

10. The simulation system as claimed in claims 7, wherein both actual process variables and predefined or simulated variables can be supplied to the representative modules of the second execution environment.

11. The simulation system as claimed in claim 1, wherein the simulation system is connected to a process simulator.

12. The simulation system as claimed in claim 11, wherein the process simulator is connected by converting the interfaces of the simulation system to interfaces of the process simulator.

13. The simulation system as claimed in claim 11, Wherein the process simulator is connected via an adapter, the interfaces of the simulation system being converted to interfaces of the adapter.

14. A method for carrying out a simulation using a simulation system according to claim 1, wherein the first execution environment is produced using a planning tool of the control system,the second execution environment with its embedded software components, representative modules and connections is likewise produced using the planning tool of the control system previously used for the first execution environment,the execution environment which is designed to simulate the automation process on which the installation is based with its connections is changed to a simulation mode without changing the existing planning,and the technical installation or parts of the technical installation is/are then simulated in the execution environments.

15. The method as claimed in claim 14, wherein the planning of hardware with wiring or networking of the second execution environment is automatically produced from the hardware planning of the installation.

16. A control system which controls a process running in a technical installation and includes a simulation system, wherein the simulation system is adapted to carry out a simulation using the method of claim 14.

17. The control system as claimed in claim 16, wherein the simulation system is configured using the same planning tools as other parts of the control system.

18. The control system as claimed in claim 16, wherein the simulation system is graphically planned using modular technology.

19. A computer program product embodied on a non-transitory computer readable medium which is loaded into the memory of a computer and comprises software code sections which are used to carry out the method as claimed in claim 14 when executed on a computer.