Overview of Distributed Control Systems Formalisms 253
Total Page:16
File Type:pdf, Size:1020Kb
View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by DSpace at VSB Technical University of Ostrava Overview of distributed control systems formalisms 253 OVERVIEW OF DISTRIBUTED CONTROL SYSTEMS FORMALISMS P. Holeko Department of Control and Information Systems, Faculty of Electrical Engineering, University of Žilina Univerzitná 8216/1, SK 010 26, Žilina, Slovak republic, tel.: +421 41 513 3343, e-mail: [email protected] Summary This paper discusses a chosen set of mainly object-oriented formal and semiformal methods, methodics, environments and tools for specification, analysis, modeling, simulation, verification, development and synthesis of distributed control systems (DCS). 1. INTRODUCTION interconnected by a network for the purpose of communication and monitoring. Increasing demands on technical parameters, In the next section the problem of formalizing reliability, effectivity, safety and other the processes of DCS’s life-cycle will be discussed. characteristics of industrial control systems initiate distribution of its control components across the 3. FORMAL METHODS plant. The complexity requires involving of formal The main motivations of using formal concepts methods in the process of specification, analysis, are [9]: modeling, simulation, verification, development, and ° In the process of formalizing informal in the optimal case in synthesis of such systems. requirements, ambiguities, omissions and contradictions will often be discovered; 2. DISTRIBUTED CONTROL SYSTEM ° The formal model may lead to hierarchical semi- A common general definition of a distributed automated (or even automated) system system describes it as a system consisting of several development methods; intelligent devices cooperating for common purpose. ° The formal model can be verified for correctness Intelligent devices (microcomputers, workstations, by mathematical methods; robots etc.) support processes, which coordinate ° A formally verified subsystem can be activities and information exchange via a incorporated into a larger system with greater communication network. In order to call a device confidence that it behaves as specified; “intelligent”, it must fulfill following requirements ° Different designs can be evaluated and compared. (Fig. 1): ° Contain some kind of processor or CPU for In general, formal methods for distributed control processes realization and decision making; systems must address the following problems: ° Dispose sufficient memory capacity for I. Modeling - Select appropriate models and information storage. formal notations for adequately describing sensors/actuators controlled and control system. These notations must deal with the dynamic and reactive nature of the I/O controlled system, and allow for the proper P P RAM expression of timing properties. CPU ROM II. Verification - The verifier is presented with a IU IU IU ASIC formal mathematical model of the system, and a Comm. controller specification S of how the controlled system should P behave. The verification problem involves demonstrating that the model of the system satisfies IU IU GW IU – Intelligent Unit the specification S. GW – Gateway III. Development - In controller development a P P – Process specification S is given that the plant must satisfy ASIC – Application GW IU IU (the controller is not given). A disciplined method is Specific Integrated sought whereby designers can be helped to construct Circuit a controller so that system model satisfies S. In development the controller should be built in a Fig. 1 Example of distributed control system and modularly structured compositional fashion intelligent device structure (controller architecture) . The term Distributed Control System (DCS) IV. Synthesis – If controller development is fully denotes a control system, usually of a manufacturing automated, then such process is called synthesis. system, process or other type of dynamic system, in A chosen set of methodics, environments and which the control elements are distributed and tools fully or partially satisfying the specified 254 Advances in Electrical and Electronic Engineering requirements related to formalisms will be approach is dedicated to a special class of DCS, introduced. which are organized as several periodic processes, with nearly the same working period, but without 3.1 Sequential Function Chart common clock, and which communicate by means of shared memory through serial links or field The primary objective of Sequential Function busses. Chart (SFC++) is the implementation of graphical modeling formalism for design, validation, simulation and automatic code generation of Specification: centralized model industrial systems, graphical language for programming its control software and supervisory level control tool for control, monitoring, SCADE editor diagnostics etc. [10]. The aim of the running project Simulation Automated tests is also creation of visual programming environment, SCADE generation which integrates the advantages of object-oriented function Formal verification modeling for design and simulation and the model performance of distributed control systems (i.e. Distribution computers with real-time operating systems SCADE editor protocol interconnected via industrial networks). To bypass the differences between object-oriented model and SCADE Robust properties implementation level, on which run several parallel Distributed analyzator tasks, a standard formalism (IEC, 1988; UTE, 1992) functions is used for describing of system dynamics and programming of control system based on Sequential Environment SCADE editor Function Chart (SFC). emulation Distributed Simulation Debugging I/O Module Module implementation Automated tests model generation Formal verification Performance validation RunTime Module Local Data SCADE code Communication System SFC++ generator library Model Editor Evolution Event Module Manager Development Subsystem RunTime Subsystem code code code Fig. 3 CRISYS methodology scheme Fig. 2 SFC++ logical architecture 3.3 The ISILEIT project SFC++ is intended for control systems using single or multiprocessor computers or PLCs with The ISILEIT (Integrative Specification of real-time operating systems ((RTOS) interconnected Distributed Control Systems for the Flexible by local networks and with control buses connecting Automated Manufacturing) project aims at the the process and other devices. development of a seamless methodology for the integrated design, analysis and validation of 3.2 The Crisys project distributed production control systems [6]. Its focus is the use of existing techniques which should be The Crisys project aims at improving, improved with respect to formal analysis, simulation unification and formalization of the actual methods, and automatic code generation. The integration of techniques and tools used in the industries concerned SDL block diagrams, UML statecharts and with process control, in order to support a global collaboration diagrams formed an executable system approach when developing DCS [2],[3]. The specification language that allows specifying main result of Crisys project is quasi-synchronous reactive behavior as well as complex application approach based on synchronous language Lustre [7] specific object structures. To ensure the correctness and associated tool SCADE (Safety Critical of the design at the earliest stage, validation in form Application Development Environment) [1]. This of simulation and formal verification is integrated Overview of distributed control systems formalisms 255 into the process. The developed simulation common object-oriented problems in general environment can be used to prove that the generated domain. executable code meets the requirements. 3.5 Architecture Description Language The Architecture Description Language (ADL) System Create system Create system specification is defined as a language which disposes of model specification (FUJABA) capabilities for modeling conceptual architecture of both hardware and software systems [8]. The System object Instance of ASM language provides models, notations and tools for model V data structure V description of components and its interactions, E particularly with regard to large-scale high-level A R designs. It supports the selection of principles, Generate Instantiate system in application of architecture paradigms, abstraction executable model L I ASM meta-model and designs implementation. I F Java D I ASM model The main properties of the language include appliaction explicit specification of: C A ° components, Validate system T A Prepare ASM for ° connectors, model by model-checking ° interfaces, execution I T ° configurations. I O Model checking O input A component represents a computation unit or N data store and forms loci of computation and state. A N connector is a construction block used for modeling Run model-checker of interactions among components and for modeling Design errors or rules, which govern those interactions. The Fig. 4 ISILEIT methodology evaluation activities interfaces ensure correct connectivity and communication of components. Architectural configuration or topology is connected graph of 3.4 DCS Modeler, DCS Simulator components and connectors which describes architectural structure. During design of object-oriented simulation model of a DCS several requirements were considered [4]: 3.6 IEC 614 99 a) Dynamic behavior of each component device The IEC 61499 standard modified the Function within DCS can be considered to be a Finite State Block