GRASS: An Object-Oriented Framework for SCADA Systems

Abstract

This paper describes GRASS, an object-oriented framework for SCADA(Supervisory Control And Data Ac quisition) systems. The proposed framework consists of class libraries and tools, that support development of SCADA system software. The basic functional requirements of SCADA systems are similar, regardless of the particular application field,so substantial software sharing is possible. Nevertheless, productivity of SCADA software is impeded by dependence on details of the target system. The task of configuring the SCADA software for each target system is complex, typically involving manual input of a lot of system description data. GRASS simplifies this task by automatically generating system description data and providing editing tools for subsequent customization.

A model‐based method to design an application common platform for enterprise information systems

“…4] and the software assets classified as "Domain Commons" [shown as (c) in Fig. 4], we derive the ACP use-case models as use-case models whose granularity is at the subfunction level by using the use-case transformation rules described in the next section [shown as (4) in Fig. 4].…”

“…In order to improve the productivity of software development, system development organizations have been developing software assets such as middleware, application frameworks [3,4], components [5,6], and libraries. The main goal of this paper is to reduce the time and cost of the development of integrated enterprise information systems by reusing software assets.…”

Automatic generation of system descriptions for plant supervisory control systems

“…Accordingly, we have researched and developed ways to mitigate the problems of system dependency in SCADA system development and raise the software productivity [2,3]. For example, GRASS [2] is a framework for SCADA systems that combines automatic generation and customization of a lot of definition data.…”

“…For example, GRASS [2] is a framework for SCADA systems that combines automatic generation and customization of a lot of definition data. First, equipment definitions are input using equipment diagrams, such as circuit diagrams and system configuration diagrams.…”

“…Only by using the method in Ref. 2, the usable design information must be analyzed, equipment group patterns must be extracted, and equipment definitions are newly made using them. Otherwise, the equipment definitions for the old systems must be converted to a form that can be used by the new systems using conversion software.…”