BROOKHAVEN SCIENCE ASSOCIATES IRMIS Integrated Model of Installed Systems D. Dohan NSLS2 Controls Group EPICS Meeting, Padua, 2008

2 BROOKHAVEN SCIENCE ASSOCIATES The IRMIS RDB Project IRMIS is a collaborative effort involving APS, SNS, TRIUMF, SLAC, CLS, SLS,... - IRMIS Inaugural Meeting, APS, March IRMIS Collaboration Meeting, APS, May IRMIS meetings are usually held in collaboration with EPICS meetings. The present BNL work extends this collaborative effort.

3 BROOKHAVEN SCIENCE ASSOCIATES Accelerators and RDBs - RDB technology: manage the complexity of modern accelerators (10Ks of components, 100Ks of PVs, 100Ks of cables) - the accelerator relational database problem is not technology limited: it is dominated by details of the accelerator facility domain (i.e. how much you want to capture, how much effort you wish to invest to make it work. Management buy-in is essential). - does not require sophisticated Relational Database technology or expertise. By keeping the schema simple the goal is to foster active participation by accelerator experts, as well as by other collaborating laboratories (the EPICS model.) - work flow. Too big and too cultural to discuss.

4 BROOKHAVEN SCIENCE ASSOCIATES IRMIS General Guidelines/Goals - Flexible schema design – site neutral. Wide range of users and use cases  lowest common denominator - (Minimalist) modeling approach is to define and use extensible tables, rather than schema extensions to manage ‘scope creep’ (  use of key-values pairs, where key/value relationships are application dependent. No ‘xx-type-specific’ tables.) - Resist inserting site-specific or application-driven schema structures. (Relational vs. object-oriented approach). - Pragmatic. Follow RDB standards (database normalization, etc) where possible unless it adversely affects performance. Maximize emphasis on problem domain, minimize RDB specialty technology. - Business rules stored in the application layer (the secular layer).

5 BROOKHAVEN SCIENCE ASSOCIATES RDB Application Layer IRMIS EPICS PV Crawler Operations Cabling Controls Group Accelerator Physics Power Supplies Infrastructure/ Installation Vacuum Beamlines Users/Use Cases

6 BROOKHAVEN SCIENCE ASSOCIATES Process Variables (Software) Components (Hardware ) associated with Cables connected by signals integrated approach

7 BROOKHAVEN SCIENCE ASSOCIATES Process Variable (EPICS software) schema

8 BROOKHAVEN SCIENCE ASSOCIATES Process Variable Client schema

9 BROOKHAVEN SCIENCE ASSOCIATES Crawler IRMIS RDB File System IOC ioc boot operations

10 BROOKHAVEN SCIENCE ASSOCIATES select * from rec_client_type; | rec_client_type_id | description | | 1 | MEDM | | 2 | Alarm Handler | | 3 | Save/Restore | | 4 | Sequencer | | 5 | sddslogger | | 6 | PEM |

11 BROOKHAVEN SCIENCE ASSOCIATES

12 BROOKHAVEN SCIENCE ASSOCIATES 12 Component, Connection, Signal Modeling Goals of the component model:  capture the relationships, interaction and interdependence of the components making up the accelerator/system  integrate physicist/engineer/operator perspectives  provide an interactive ‘as-built’, query-able, documentation model  vs. ‘revision controlled drawing’ approach

13 BROOKHAVEN SCIENCE ASSOCIATES 13 Components  What is a component?  original motivation: something that has EPICS device support  this did not address the vast number of infrastructure components (crates, racks, cpus..)  successive partitioning of the facility  arrive at ‘replaceable unit’  IO card, chassis, magnet, rack, power supply, COTS..  familiar day-to-day items: (good ‘buy-in’)  system partitioning promotes (more) complete coverage  more primitive granularity than a ‘device’  do not assign a high level physics ‘role’ to a component  less subjective – no (user-oriented) naming convention issue  a component definition is influenced by how it is assembled, as well as how it functions  a component may be a ‘soft’ entity: link, sequence, etc  how do we model the relationships between the components that make up a facility? (i.e., how do we model the facility)

14 BROOKHAVEN SCIENCE ASSOCIATES 14 Connections: component relationships  Component Installation/Assembly  A component is ‘housed’ in some other component. This essentially tells us how the facility is assembled.  This ‘housed in’ relationship is captured in a graph:  the components are the ‘nodes’  the housing relationships are the edges  the graph is (directed) acyclic  simple hierarchy  concept of components as subassemblies

15 BROOKHAVEN SCIENCE ASSOCIATES 15 Housing Graph VME Chassis/z42 IO_Card/4 bldg/APS_412 room/B102 rack/L3:RA:IO;3 ‘is housed in’

16 BROOKHAVEN SCIENCE ASSOCIATES 16 Component Power Relationship  each active component is dependent on its (AC) power source  it is ‘powered-by’ some other unique component  acyclic graph  power hierarchy  a component always has a housing parent: the power parent is optional  component power failure is the second most common source of control system failure

17 BROOKHAVEN SCIENCE ASSOCIATES 17 Housing, Power (Orthogonal) Graphs IO_Card/4 AC Panel/L3:El:SO1 Circuit/11 Power Strip/R VME Power Supply/ bldg/APS_412 room/B102 is powered by ‘is housed by’ rack/L3:RA:IO;3 VME Chassis/z42

18 BROOKHAVEN SCIENCE ASSOCIATES 18 Component Control Hierarchy  each active component is ‘controlled by’ its parent controller component  acyclic graph  control hierarchy. This is a logical hierarchy – typically realized over shared hardware networks (e.g. ethernet)  components in the control hierarchy exchange messages (A component is in the control hierarchy if it can be addressed by the IOC. This excludes power supplies, magnets, etc )  a component always has a housing parent: the control parent is optional  the housing, control and power parents might be the same component – eg card cage module (VME, etc)  loss of communication between control system infrastructure components is the most common source of control system failure

19 BROOKHAVEN SCIENCE ASSOCIATES 19 Housing, control, and power graphs: Accelerator components MVME-167/ioc_xyz IO_Card/4 AC Panel/L3:El:SO1 Circuit/11 Power Strip/R VME Power Supply/ bldg/APS_412 room/B102 rack/L3:RA:IO;3 is powered by ‘is controlled by’ ‘is housed by’ VME Chassis/z42

20 BROOKHAVEN SCIENCE ASSOCIATES Component schema

21 BROOKHAVEN SCIENCE ASSOCIATES Component schema

22 BROOKHAVEN SCIENCE ASSOCIATES 22 Housing, control, and power graphs: Accelerator components MVME-167/ioc_xyz IO_Card/4 AC Panel/L3:El:SO1 Circuit/11 Power Strip/R VME Power Supply/ bldg/APS_412 room/B102 rack/L3:RA:IO;3 magnet/BL1A power supply/ps1a is powered by ‘is controlled by’ ‘is housed by’ VME Chassis/z42

23 BROOKHAVEN SCIENCE ASSOCIATES 23 Cables

24 BROOKHAVEN SCIENCE ASSOCIATES

25 BROOKHAVEN SCIENCE ASSOCIATES

26 BROOKHAVEN SCIENCE ASSOCIATES

27 BROOKHAVEN SCIENCE ASSOCIATES 27 Housing, control, and power graphs: Accelerator components MVME-167/ioc_xyz IO_Card/4 AC Panel/L3:El:SO1 Circuit/11 Power Strip/R VME Power Supply/ bldg/APS_412 room/B102 rack/L3:RA:IO;3 magnet/BL1A power supply/ps1a is powered by ‘is controlled by’ ‘is housed by’ VME Chassis/z42

28 BROOKHAVEN SCIENCE ASSOCIATES 28 IO_Card/4 Ports: extending the component definition signal: - command, data or energy flow media connections are made by means of component ‘ports’ - ‘component’ definition extended to include port configuration at the control hierarchy ‘leaf’ component, the ‘signal’ maps to a software tag -e.g., EPICS ‘process variable’ this is where the connection is made between hardware and software. IO_Card/4 magnet/BL1A power supply/ps1a component: a ‘signal transformer’ -each of its output signals is some function of its input signals examples: -fanout module -O j = I 0 -power supply -output excitation curve vs input reference end-to-end signal tracing. The PV usually refers to the ‘end’ of the signal path. EPICS ‘PV’

29 BROOKHAVEN SCIENCE ASSOCIATES 29 Accelerator Cmpnts: Hierarchy + Network (wiring) MVME-167/ioc_xyz IO_Card/4 AC Panel/L3:El:SO1 Circuit/11 Power Strip/R VME Power Supply/ bldg/APS_412 room/B102 rack/L3:RA:IO;3 magnet/BL1A power supply/ps1a interlock ‘is powered by’ ‘is controlled by’ ‘is housed by’ ‘part of acc. sequence’ VME Chassis/z42

30 BROOKHAVEN SCIENCE ASSOCIATES Component schema

31 BROOKHAVEN SCIENCE ASSOCIATES Cable schema

32 BROOKHAVEN SCIENCE ASSOCIATES Cable schema

33 BROOKHAVEN SCIENCE ASSOCIATES Lattice RDB - A schema to describe a general accelerator lattice has been defined for IRMIS. This RDB is the driver for model-based accelerator control - The schema introduces a single new ‘sequence’ element type. The primary purpose of the a sequence is to group real lattice elements. Examples of sequence elements are: girder, cell, ring. The RDB contains an ‘accelerator’ hierarchy of sequences. No naming convention is required or assumed. - Investigation into creating generators for MAD, Elegant, Tracy, etc input decks directly from the RDB. Possible mechanism is to use the ADXF format defined by Nicholas Malitsky.

34 BROOKHAVEN SCIENCE ASSOCIATES Lattice schema

35 BROOKHAVEN SCIENCE ASSOCIATES lattice Process Variables (Software) Components (Hardware ) Cables connected by integrated approach

36 BROOKHAVEN SCIENCE ASSOCIATES IRMIS To_Do/Wish List - Web-based PV viewer inter-IOC/db graphical logic presentation (use the cable gui) WebCA for direct access to live PVs - XML schema for HLA access to the lattice RDB - ‘Prescriptive-PV’ IRMIS component-type aware EPICS database configuration tool remove macro substitutions from the st.cmd file? (table editing) cross ioc/db configuration tool component-type:device/driver support schema?

37 BROOKHAVEN SCIENCE ASSOCIATES IRMIS To_Do/Wish List (cont’d) - component history application link to asset management/procurement installation history calibration, validation, NRTL certification, etc - component_installation key/value properties table: lattice component alignment information component GPS coordinates (e.g. racks) - link exploder related to the cable database. Presentation of the logical control hierarchy implemented over shared hardware (e.g. ethernet NADs)

38 BROOKHAVEN SCIENCE ASSOCIATES IRMIS To_Do/Wish List (cont’d) - extensible component-types? Replace the function, mfg, form-factor with key-value table, allowing general component-type attributes. This increases the complexity of the application layer. Introspection concept: define and store a set of allowed component-type:attribute-keys, and how they are to be interpreted. - process flow diagrams (Canadian Light Source) - Application development environment ‘Prescriptive AOI’ – application-centric EPICS build system?

39 BROOKHAVEN SCIENCE ASSOCIATES port port_id PK cmpnt_installation_id FK port_type_id port_name port_order port_id PK cmpnt_installation_id FK port_type_id port_name port_order rec rec_id PK ioc_boot_id FK rec_nm rec_type_id ioc_resource_id FK rec_id PK ioc_boot_id FK rec_nm rec_type_id ioc_resource_id FK fld fld_id PK rec_id FK fld_type_id fld_val ioc_resource_id FK pin_id FK fld_id PK rec_id FK fld_type_id fld_val ioc_resource_id FK pin_id FK IRMIS To_Do/Wish List (cont’d) fld__pin fld__pin_id PK pin_id FK rec_name fld_type fld__pin_id PK pin_id FK rec_name fld_type

40 BROOKHAVEN SCIENCE ASSOCIATES lattice Process Variables (Software) Components (Hardware ) associated with Cables/ Pins connected by signals integrated approach