JCOP Review Closeout

1. JCOP Review Closeout March 13, 2003 Chip Watson, Robin Lauckner, Jim Olsen, Hans von der Schmitt

2. Overall • Excellent review materials & presentations • Significant accomplishments thus far, in the framework, tools, and applications • Reaching an important transition point from development towards deployment • Only one outstanding technical concern, with several possibilities for resolution • Didn’t find anything important that the team and management were not already aware of

3. PVSS / SCADA • PVSS appears to be a capable tool with a number of useful features • Distributed architecture; separation of supervisory & control functions • Support for Windows & Linux • Device oriented data management • Open architecture (text config files, API) • Standard SCADA tools (archiving, trending, GUI tools, …) • Scalability is one remaining concern • Some early indications of problems • Several possibilities for resolution • (additional studies needed to clarify real issues)

4. SMI++ • Finite State Machine is clearly an appropriate and proven tool for detector controls • SMI++ within the JCOP framework provides nice support for • Hierarchical (and distributed) state machines • Partitioning of the control system • Ownership (and sharing) of a partition • Flexibility: • SMI++ for all of online is elegant • Integration with non-SMI++ agents (DAQ) is possible

5. JCOP Framework • Hides some of the complexity of PVSS (good) • Integrates SMI++ functionality • Integrates support for a number of network protocols: OPC, DIM, <future: DIP> • Standardizes many style issues (color, alarm types, etc.) aiding useability • Multiple views of DCS (physical, logical) • Still needs better means of configuring large numbers of devices (in development already) • Still unclear: conditions and configuration databases

6. Device Support • Support for CERN specified field buses • High and Low Voltage devices • Abstract device model • Supported on CAEN, ISEG, Wiener, … • ELMB • Generic, rad hard I/O points (standard software) • Custom software to re-use in GCS • PLC’s => Already good support for a large number of the devices needed.

7. Applications • Gas Control System • Good opportunity for savings (23 systems), and good job at achieving consensus on most of the requirements • UNICOS tools for PLC + / - • Detector Safety System • Rack Controls

8. Schedule • All major components appear to be on track. • Staffing may be tight in some places, but not uncomfortably so (for now) • A current reference document, which is updated and shared by management and technical staff, does not exist.

9. Management • Steering Board • Executive Board • Strong project leader • Sub-project teams • Many external interfaces (a challenge) • Experiments (non-JCOP part) • Service groups: GCS, JVOC, … • Accelerator

10. Transition • JCOP is now moving from primarily development towards deployment • Positive: find bugs, obtain feedback • Negative: drain on R&D effort • Current structure may need to evolve to reflect this • Technical coordination across experiments, for example sequencing gas system installation and commissioning • Decisions on resource allocations for deployment and long term support

11. Recommendations • Set up a persistent testbed for testing current and future releases of PVSS and the JCOP framework and tools, including scalability (multiple large memory machines) • Perform additional studies to better understand PVSS scalability, especially for hierarchical systems as envisaged for LHC (will help in discussions with ETM) • Plan to support multiple releases of PVSS and the JCOP software – this is necessary so that the detectors can independently maintain their own release control • Pursue at least basic access controls, with a strong preference for device server level implementation

12. Recommendations • Work with the detectors to ensure the staging of deployment of JCOP software into the detectors, preferably with each of the detectors involved by the end of the year.

13. Recommendations • Develop / negotiate a support and maintenance plan for both near-term (deployment phase) and long-term, with clear ownership and staffing commitments (suggest within 6 months) • JCOP framework, devices, tools • SMI++ • ELMB • UNICOS • GCS, DSS, RCS, …

14. Recommendations • Conditions databases and configuration databases remain areas of opportunity for common solutions and savings, and a sub-project to further investigate this should be initiated soon or the opportunity will be lost.

15. Recommendations • Identify an appropriate forum to deal with installation and commissioning conflicts in the DCS, particularly the gas sub-systems (Installation Committee / Board, preferably an existing body ?)

16. Recommendations • Separate the functions of information exchange and coordination from the functions of high level management • Coordination Board (the details) • GLIMOS, Controls Coordinator, DAQ Coordinator, Technical Coordinator, liasons to external groups, JCOP project leader (+ others as needed) • Oversight Board (high level responsibility, resource allocations) • One representative of each detector • One representative of each division

17. Thanks • Presentations were interesting • Atmosphere is congenial (esp. coffee) • Weather is terrific