Experience Prototyping PVSS P. Sollander, March 2001 - PCR Software Meeting

1. Experience Prototyping PVSSP. Sollander,March 2001 - PCR Software Meeting An ST/SL/EP/IT collaboration

2. Is the recommended SCADA system suitable for the supervision of the CERN’s technical infrastructure? P. Sollander - ST/MO/IN

3. Collaboration • ST: drivers, data loader, mimics, data logging, trending • SL: alarm lists • EP: second PVSS system for data exchange • IT: PVSS support P. Sollander - ST/MO/IN

4. ST/MO Prototype plans • Phase I October 2000 to January 2001 • Functional model with alarms, mimics, trends • TDS data acquisition -> PVSS driver • TDS data loading -> use existing config. DB • Inter system communication with GIF experiment • Phase II February to April 200) • Performance tests • High data rates, full TDS data set • PVSS system redundancy evaluation • Phase III May to July 2000 • Development specification • Standard PVSS / Siemens driver (ISAP) • Library of reusable standard symbols • PVSS supervision modules and generic data loader (XML) • Phase IV August 2001 to December 2002? • Implementation and migration P. Sollander - ST/MO/IN

5. Phase I work areas • SmartSocket™ driver • first version implemented with pvss • Data loader • standard pvss ascii manager • Inter PVSS communication • interconnecting data from different domains • global naming scheme • User interfaces • mimics: reusable symbols matching DPTs • alarms: use of alert handlers, classes, … • trending and logging P. Sollander - ST/MO/IN

6. For later - not in prototype • Full alarm functionality • alarm reduction, grouping, archiving, … • Massive data integration • no intention to integrate all TDS data in this prototype • Performance evaluation • Scheduled for phase II only. • Custom tools • XML data loader • PVSS supervisor module, ... P. Sollander - ST/MO/IN

7. The Technical Data Server architecture CAS UMMI JavaGuils LogDB Dcli Dalm Dsa TDS server TDrefDB DAQ Dsec Scada EC Configuration data (~50000 DPE) P. Sollander - ST/MO/IN

8. ST/MO Prototype architecture PVSS UIM West zone cooling data • 245 Data point elements • 115 CAS alarms • 2 trending parameters • 6 commands • 1 mimic diagram PVSS RTDB PVSS EvtMgr GIF PVSS EvtMgr Data exchange RTDB loader PVSS GIF client PVSS TDS client TDS Configuration database TDS Configuration data P. Sollander - ST/MO/IN

9. PVSS system architecture Panel file server PVSS UI mgr distmgr NT PIII 800MHz 128MB RAM pcst429 PVSS DM PVSS EvtMgr PVSS redu PVSS redu PVSS EvtMgr PVSS DM dedicated network PVSS TDS driver PVSS TDS driver Linux 2xPIII 600MHz 256MB RAM Linux 2xPIII 600MHz 256MB RAM lnxspr1 srvtds3 Standard network Standard network TDS P. Sollander - ST/MO/IN

10. Prototype results • Data acquisition • TDS driver available on Linux and NT • Robust driver developed easily • User interfaces • PVSS standard alarm screen with CAS data • Works, but some configuration issues remain • A CERN wide PVSS alarm screen looked upon by SL/CO • Integrated alarm/mimics/trends in one application give interesting navigation possibilities • PVSS mimics • Reusable objects available, drag-and-drop view creation, easy to use, fair graphics, integrated trending tools P. Sollander - ST/MO/IN

11. Prototype results • Data loader • Loaded TDS data directly from current configuration database • Standard PVSS tool works, but should be improved with specialized tools to obtain better data integrity and allow all transactions (update/insert/delete) • Data distribution • Ok for small scale, to be tested more large scale • System reliability • PVSS does not provide standard modules for system supervision! • E.g. if a driver goes down, clients are not aware! • PVSS redundancy - Interesting feature for high-availability systems. Will be prototyped in phase II. P. Sollander - ST/MO/IN

12. PVSS view editor P. Sollander - ST/MO/IN

13. Alarm Handling in PVSS P. Sollander - ST/MO/IN

14. PVSS future in ST/MO • Phase II - performance validation • High data rates, full TDS data set • PVSS system redundancy evaluation • Phase III - specification • PLC drivers • Supervision/administration tools • Development tools • Migration strategy • Phase IV • Implementation and migration P. Sollander - ST/MO/IN

15. TDrefDB TDS - PVSS interface Siemens S5 Mimics Config Siemens S5 Siemens S7 Schneider Wizcon EC EFACEC EC SCADA Link OPC Siemens S7 Schneider Ddaq API UMMI Custom TDS (SmartSockets) EFACEC EC Wizcon EC Event Manager JGuils Trends Alarms CAS Equipment Equipment ST/MO Migration strategy P. Sollander - ST/MO/IN

16. ST/MO integration strategy LHCX PVSS LHC PVSS Access to all PVSS data • PVSS systems communicate • LDIWG communication • Common tools: • CAS alarms • standard symbols • User has access to all information • Former TDS data acquired directly from PLCs PVSS UI ST/AA PVSS TCR PVSS Databus driver LDIWG Configuration database GIF PVSS Direct equipment data acquisition Non PVSS systems P. Sollander - ST/MO/IN

17. Conclusions • SCADA systems propose a coherent set of tools • PVSS seems suitable for technical infrastructure, but • Some enhancements must be made • Supervision modules (ETM) • Standard tools, data loader, symbols (CERN) • Next phases will validate the tool and specify migration strategy • A general licensing policy must be found • PVSS development done by CERN or by contractors must be capitalized by the user community P. Sollander - ST/MO/IN