project by cuiliqing

VIEWS: 43 PAGES: 47

									Commercial Control Systems

      Axel Daneels - IT/CO
    Wayne Salter - Anite Systems
          Overview of Presentation
ï Recap  of Technology Survey
ï General Observations
ï General Product Capabilities
ï Specific Products
ï Engineering Aspects
ï Conclusions



19th May 1998                    JCOP Project Team - 2
     Recap of Technology Survey
ï   Began May 1997
ï   Documentation and major criteria
     u   Scalability
     u   Distributed multi-team development
     u   Openness
     u   WW academic licensing
ï   150 companies contacted
ï   40+ replies received of which 20 potentially
    interesting
ï   12 visited and detailed discussions with others
19th May 1998                                 JCOP Project Team - 3
          General Comments about
                Evaluation
ï Has   given a good overview of market and
  tendencies
ï Difficulties with language/terminology
ï Understanding of the products takes time
ï Basic understanding of the products’
  capabilities
ï Understanding of critical success factors
ï Further in-depth evaluation required

19th May 1998                     JCOP Project Team - 4
                 Tendencies
ï   NT with greater integration into business
    process
ï   PCs
ï   Soft PLC
ï   OPC
ï   Web
ï   Integration with commercial
    components/applications
ï   Applications increasing in size
19th May 1998                          JCOP Project Team - 5
                Categories
ï Full  Control Systems
ï SCADA
ï UNIX/VMS (basic system development
  effort ≥ 100 man years)
ï PC (basic system development effort 30
  man years)
ï Products used in safety or business
  critical areas
19th May 1998                  JCOP Project Team - 6
                Generic Product
ï Polling of process
ï Event driven within the product
ï Modular or layered software approach
ï C, Ada, C++
ï Distributed
ï Client/Server



19th May 1998                     JCOP Project Team - 7
                H/W Architecture




19th May 1998                      JCOP Project Team - 8
                S/W Architecture




19th May 1998                      JCOP Project Team - 9
                Openness
ï API’sto access RTDB, ADB, PDB
  supporting C, C++, VB
ï DDE and OLE I/F to PC Products
ï OPC Client
ï ODBC I/F to RTDB, ADB, PDB
ï SQL




19th May 1998               JCOP Project Team - 10
                Device Support
ï Multiplecommunication protocols
  supported in a single system
ï Support for major PLCs/DCSs but not
  VME
ï Device Driver Toolkit
ï More support for Profibus and WorldFip
  than CANbus
ï Time stamping of data in PLCs
ï OPC is developing as a standard
19th May 1998                    JCOP Project Team - 11
                    Scalability
ï No proven applications of 1M I/O
ï Some over 100K I/O
ï Large applications are typically ≈ 50K I/O
ï Scalability is linked to the process
  characteristics
ï Scalability is linked to correct engineering
     u Hierarchy,   partitioning, Tag definition


19th May 1998                              JCOP Project Team - 12
                Object Handling
ï Some   products support simple objects
  at database level
ï Graphical object classes with
  inheritance
ï Handling of ‘complex objects’ is
  sometimes possible through the use of
  sequencing and scripting


19th May 1998                     JCOP Project Team - 13
                   Configuration
ï   Database
     u   Parameter Templates
     u   Multiple Databases/Files
     u   Merging capabilities
     u   ASCII Import/Export
ï   Graphics
     u   Graphical editor and import
     u   Library of symbols
     u   ‘Drag and drop’
     u   Stored as files
19th May 1998                          JCOP Project Team - 14
                Access Control
ï Standard  login with PWD
ï Typically users in groups
ï Groups have a set of allocated privileges
ï Large number of groups possible
ï Privileges limit write access to process
  parameters
ï Some allow access to graphics and
  functionality to be limited

19th May 1998                     JCOP Project Team - 15
                  MMI
ï PC  graphics generally better than
  Unix/VMS
ï Multiple screens
ï Displays with combinations of synoptics
  and alphanumeric text
ï Library of "generic" symbols with defined
  TAG links
ï Dynamic linking of parameters to graphics
ï Standard window manipulation facilities
19th May 1998                    JCOP Project Team - 16
                MMI (cont.)
ï XY  and other statistical analysis plots
  are not standard - increasing use of
  ‘components’ to provide this
  functionality
ï On-line configuration and customisation
  of MMI
ï Links can be created between display
  pages
ï Animation and multimedia facilities
19th May 1998                   JCOP Project Team - 17
                Example Display




19th May 1998                     JCOP Project Team - 18
                Example Display




19th May 1998                     JCOP Project Team - 19
                Trending
ï Trending  charts may be pre-defined or
  configured on-line
ï Trending chart may be an graphical
  object or trending is a separate module
ï Charts contain multiple pens (typically 8)
ï Real-time and historical trending




19th May 1998                     JCOP Project Team - 20
                Trending (cont.)
ï Real-time      trending for any parameter in
  the RTDB
ï Historical trending for any archived
  parameter
ï Zooming, scrolling and panning
ï ‘Hairline’ feature




19th May 1998                        JCOP Project Team - 21
           Example Trending Chart




19th May 1998                 JCOP Project Team - 22
                Alarm Handling
ï   Alarm conditions are based on limit and status
    checking
ï   More complicated expressions developed by
    creating derived parameters
ï   Alarms are time stamped
ï   Alarms are logically handled centrally
ï   Alarm notifications (audible, visual, Email, GSM)
ï   Multiple alarm priority levels
ï   Grouping of alarms and handling of groups is
    possible
19th May 1998                             JCOP Project Team - 23
                Alarm Handling (cont.)
ï   Suppression of alarms either individually or
    as a complete group
ï   Alarms displayed in chronological sequence
ï   Filtering of alarms seen on the alarm page or
    when viewing the alarm log is possible on at
    least priority and group
ï   Relationships between alarms cannot be
    defined
ï   Automatic action on alarm, e.g., Email
ï   Annotation of alarm log
19th May 1998                         JCOP Project Team - 24
                Example Alarm Page




19th May 1998                   JCOP Project Team - 25
                Logging and Archiving
ï   No major difference between logging and archiving
ï   Data stored in compressed format
ï   Logging is typically performed either for a set
    number of parameters or for a set period of time
ï   Logging/archiving can be frequency or event driven
ï   Logging of user actions is performed together with
    a user ID
ï   Logging/archiving is time-stamped
ï   Selective viewing of archive/log is possible
ï   VCR facility for playback of stored data
19th May 1998                             JCOP Project Team - 26
                Report Generation
ï Reports  created using SQL type queries
  to the archive, RTDB or logs
ï ‘Cut and paste’ capability is rarely
  provided
ï Automatic generation, printing and
  archiving of reports
ï Increasing use of ‘components’ for
  report generation
19th May 1998                       JCOP Project Team - 27
                 Automation
ï Actions can be initiated automatically
  triggered by an event
   u Typically to bring up specific display, send
     Email, or run a user defined application
ï Recipes
ï FSM         is not provided
ï Sequences and scripting possibilities
ï Expert systems provided by two
     products
19th May 1998                  JCOP Project Team - 28
                Development Tools
ï Graphics editor
ï Configuration through parameter
  templates with perhaps some basic
  development tools
ï Basic form of scripting language
ï Driver Development Tool Kit
ï Process level development generally not
  provided
ï When provided based on IEC1131
19th May 1998                    JCOP Project Team - 29
      Typical Configuration Effort
            (ohne Gewähr)
ï Dependent    on complexity
ï Order of 30-50K I/O
ï Diversity of 30 different devices
ï Devices have of the order of 4 - 5
  parameters
ï 5 - 10 man years assuming 1000
  displays
ï Comparable with L3 Muon experience
19th May 1998                JCOP Project Team - 30
                Licensing
ï Better definition required
ï Typically per station and per number of
  I/O
ï World-wide / academic licensing is open
  to discussion
ï Range 10KCHF to 100KCHF
ï Linked to engineering effort supplied


19th May 1998                  JCOP Project Team - 31
                Specific Products
ï Very similar functionality to a first order
  of approximation
ï Architecture
ï Specific Features & Issues




19th May 1998                       JCOP Project Team - 32
                CUBE




19th May 1998          JCOP Project Team - 33
                 CUBE Features
ï Additional      modules:
     u   EXAD (Expert System and Rule Based
         Sequencing)
     u   Batch Management System
     u   Maintenance Support System (MSS)
     u   Event Management System (EMS)
     u   On-Call Management System
     u   Statistical Process Control (SPC)
     u   Soft Control (Control Core)
     u   CUBE-Web
19th May 1998                             JCOP Project Team - 34
                CUBE Features (cont.)
ï Configuration database population
ï DBIII/IV Import/Export
ï Access management for user
  applications
ï Remote connection
ï No concept of object in the configuration
  database
ï COM/DCOM and support of ActiveX
19th May 1998                      JCOP Project Team - 35
                WizCon




19th May 1998            JCOP Project Team - 36
                WizCon Features
ï Additional     Modules:
     u WizPLC
     u WizDCS
     u Wizcon   for Internet
     u SPC
     u ACRON    (Maintenance Management)
     u On-call Management



19th May 1998                      JCOP Project Team - 37
            WizCon features (cont.)
ï Graphics concept (zones, layers)
ï OPC client and server
ï Animation and multi-media
ï Development studio on actual node
ï API
ï Language support



19th May 1998                   JCOP Project Team - 38
                CIMVIEW




19th May 1998             JCOP Project Team - 39
                CIMVIEW Features
ï Additional      Modules:
     u Explorer
     u SPC
             Management System
     u On-call
     u Calendar Management System




19th May 1998                       JCOP Project Team - 40
           CIMVIEW Features (cont.)
ï Reference   database (DBII)
ï API, Analog Functions, AIL-GOI
  Scripting
ï Strong and flexible functionality
ï Archiving lists
ï Current limitation about 100K I/O
ï Large library of graphics (Autocad
  translator)
19th May 1998                   JCOP Project Team - 41
                DAMATIC




19th May 1998             JCOP Project Team - 42
                DAMATIC Features
ï Includes  process level
ï Engineering approach
ï Split between process and information
  handling
ï Partitioning




19th May 1998                  JCOP Project Team - 43
                Engineering
ï Extremely  important aspect
ï Engineering to be done in advance
ï Engineering should be done centrally
ï Good engineering will significantly
  reduce effort and risk
ï More homogeneous system




19th May 1998                  JCOP Project Team - 44
                Engineering (cont.)
ï Typical       issues:
     u Naming   Conventions
     u ‘Look and Feel’
     u Symbol Library
     u System Partitioning
     u Database Structure
     u Standard Controls
     u Integration Approach

19th May 1998                     JCOP Project Team - 45
                Conclusions
ïA  large number of commercial SCADA
  products
ï Products used in a wide range of critical
  applications
ï No clear best product
ï Products have strong and weak points
ï Companies claim that products will
  scale
19th May 1998                    JCOP Project Team - 46
                Conclusions (cont.)
ï Some    weak points need addressing
ï Need to perform further evaluation
  activities addressing important areas
ï Constant evolution
ï Watch market
ï Engineering is extremely important




19th May 1998                     JCOP Project Team - 47

								
To top