Control System and Software Engineering Process Elder Matias

Development Approach Based on CLS Beamline Development Guide –Derived from APS approach System and Software Engineering Approach –Moving towards use of automated tools and mainstream software engineering processes (unified process) –Extensive use of P&ID drawings and requirements documents for requirements capture –P&ID are partially based on the American Instrumentation Society Standards Once a beamline is into the construction stage, the system analyst and scientists iterate and evolve the system

Development Approach

Project Phases

Background SAL was established in 1964, the control system has evolved along the way With the CLS project In 1999 the design architecture changed to: –EPICS (from Lucid and other custom software) –Linux and RTEMS (from NeXT, SunOS, BSD) –Momentum and S7 PLC (from Micro84 & TSX) –VME Hardware (from CAMAC)

Background (cont.) Standards: –CNSC C-138 – Provides guidance on control software under CLS operating license –IEC – For Systems Important to Safety –Canadian Electrical Code – For Control Hardware and Electrical Installations –Codes of conduct and practice - for ISP (Comp. Sci/Software Eng.) and P. Eng (Elec. Eng. …) certified/licensed staff

Major Projects Phase I and Accelerator Operational Support Phase II beamlines CANARIE Remote Access Infrastructure –VME Monitor Program Upgrade (Russ, Neil J. + Intern) –CS-Studio Tree Explorer (Glen W. + Intern) –Data Acquisition Program Upgrade (Glen W, & Ru) –Next Generation Motor Control (Mike M. & Tony W.) Upgrades –Diagnostics Kicker, X-ray BPM and time resolve (Johannes) –Linac Gun &RF (Neil J. & Hao) –Linac ACIS System (Robby) –Replace remaining pre-1980 controls (Hao + summer student)

Moving Forward Current CLS Control System –Built on a common design (circa 2000 and 2002) –Homogonous – Common structure and design across the facility –Built on 6 years of EPICS experience –Built on SAL (30 years) of accelerator and nuclear physics science Critical Questions –Does it represent best industry practice? –How can we improve quality (scientific capability and the user experience)? –How can we improve efficiency? –Is it safe and ethical? How Do We Answer These Questions? –Collectively (cross-disciplinary) –Open to new ideas and methods –Invite people from inside/outside of EPICS to help us…. –Invite people from inside/outside synchrotrons to help us… –Built on our in-house experts… –Decisions to change are technically driven with backup (ECR) –Exploit automation to reduce costs and increase reliability Shift in approach, from just-in-time make-it-work  building well designed, structured reusable applications  support highly configurable applications configured just-in-time

VLANs for: each beamline, machine control, development, office, visitors VME Crate (Reflective Memory) MicroStep EROC IOC RTEMS Field Dev. RS-232 Devices OPI Linu x IOC Step Controller RTEMS Motors MicroStep OPI Linu x OPI Linu x Touch Panel OPI Linux Network Server (bootp, dhcp, auto restore) Linux Data Archive Server Linux Alarm Server MS-Win MS-SQL Server MS-Win PowerEdge IOC Linux PS Boards IOC RTEMS Power Supplies EROC IOC RTEMS Field Dev. Ethernet Devices PLC & GPIB Field Dev. MagnetsMotors 1Gig Bridge IOC Linux Field Dev. Profibus PLC System Architecture (3.0)

Network