Control Interventions Registration
E N D
Presentation Transcript
Control Interventions Registration A proposal from BE-ICS-AP E. Blanco (6/June/18) 6/6/18 E. Blanco BE-ICS 1
Scope • Focus on the registration mechanism only • Goal: Homogenize the way BE-ICS makes the announcement of changes on the BE-ICS Industrial controls projects • A proposal for the procedure of QA and/or management of change procedure will come (Q4 2018) 6/6/18 E. Blanco BE-ICS 2
Interventions • Any change of a control systems • Hardware • Components (e.g. PLCs, batteries) • OS • Firmware • Software • New features • Bug corrections • New versions or patches of the base components (e.g. WinCC OA patches or versions) 6/6/18 E. Blanco BE-ICS 3
Bodies & procedures TIOC: Technical Infrastructure Operation Committee SUWG: Smooth Upgrades Working Group TIOC SUWG • IMPACT • CCR • Not included in the discussion: • ECR (Engineering Change Request) • Note de coupure 6/6/18 E. Blanco BE-ICS 4
BE-OP-TI Technical Groups Approval Bodies Workflow Yes Tech. Infra TIOC IMPACT Execution DOMAIN JIRA Control Change(s) Yes SUWG Accelerator CCR Accelerators operation Technical Groups 6/6/18 E. Blanco BE-ICS 5
Track of the control changes JIRA Control Change(s) 6/6/18 E. Blanco BE-ICS 6
Technical infrastructure vs. Accelerator • TI (or facilities) • CRYOGENICS (LHC cryogenics) • C&V (Cooling and Ventilation controls) • GCS (LHC gas control) • CIET (Cryogenics Instrum. Expert tool) • PSEN (Electrical distribution) • Elevators • TIP (Tech. Infrastructure portal) • … • Accelerator • QPS (Quench Protection System) • PIC (Powering Interlock Controls) • LHC Circuit • WIC (Warm Interlock Controls) • LHC Collimators • SURVEY Inner Triplet allignment • AWAKE plasma control • POPS (SPS) • … * There will be cases where the same intervention will affect both worlds : e.g. SCADA global interventions as the ones occurring on the Oracle databases (IT-DB). 6/6/18 E. Blanco BE-ICS 7
Intervention information • IMPACT (http://impact.cern.ch) • CCR (http://asm.cern.ch) • Format & Contents • Web application • What, Where When, Who • Impact, Risk, Mitigation (rollback) • Links to external sources (EDMS, JIRA, …) • Possible merge having (an improved) IMPACT as unique tool? 6/6/18 E. Blanco BE-ICS 8
CCR (Control Change Request) • Initially created to record early plans of control systems changes and/or new control developments with the goal of identifying the impact in the operation of the accelerator complex. No as a deployment awareness. • Then, merged with the SUWG list of software updates for the accelerators that was done in an wiki-like form. 6/6/18 E. Blanco BE-ICS 9
Conclusion • Q&A • We want to register all control changes we do in production systems • Optimization • Make the announcement in the proper body • Keep the same procedure for all the projects we handle : JIRA + Intervention document (IMPACT/CCR) • Ideally having all the interventions in the same place * In the near future Infor EAM work orders will be used as well for all asset (hardware) interventions (e.g. maintenance, replacements) 6/6/18 E. Blanco BE-ICS 10