IRMIS Integrated Model of Installed Systems D Dohan

Скачать презентацию IRMIS Integrated Model of Installed Systems D Dohan

22ed07c31b2dc25fca46270040fb20ff.ppt

Количество слайдов: 40

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

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

Accelerators and RDBs - RDB technology: manage the complexity of modern accelerators (10 Ks of components, 100 Ks of PVs, 100 Ks 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. 3 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). 4 BROOKHAVEN SCIENCE ASSOCIATES

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

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

Process Variable (EPICS software) schema 7 BROOKHAVEN SCIENCE ASSOCIATES

Process Variable Client schema 8 BROOKHAVEN SCIENCE ASSOCIATES

IOC ioc boot File System Crawler IRMIS RDB operations 9 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 | +----------+--------+ 10 BROOKHAVEN SCIENCE ASSOCIATES

11 BROOKHAVEN SCIENCE ASSOCIATES

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 1 2 12 BROOKHAVEN SCIENCE ASSOCIATES

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) 1 3 13 BROOKHAVEN SCIENCE ASSOCIATES

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 1 4 14 BROOKHAVEN SCIENCE ASSOCIATES

Housing Graph bldg/APS_412 room/B 102 ‘is housed in’ rack/L 3: RA: IO; 3 VME Chassis/z 42 IO_Card/4 1 5 15 BROOKHAVEN SCIENCE ASSOCIATES

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 1 6 16 BROOKHAVEN SCIENCE ASSOCIATES

Housing, Power (Orthogonal) Graphs bldg/APS_412 room/B 102 ‘is housed by’ AC Panel/L 3: El: SO 1 rack/L 3: RA: IO; 3 is powered by Circuit/11 Power Strip/R VME Chassis/z 42 VME Power Supply/ IO_Card/4 1 7 17 BROOKHAVEN SCIENCE ASSOCIATES

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 1 8 18 BROOKHAVEN SCIENCE ASSOCIATES

Housing, control, and power graphs: Accelerator components bldg/APS_412 room/B 102 ‘is housed by’ AC Panel/L 3: El: SO 1 rack/L 3: RA: IO; 3 ‘is controlled by’ Power Strip/R MVME-167/ioc_xyz VME Chassis/z 42 Circuit/11 is powered by VME Power Supply/ IO_Card/4 1 9 19 BROOKHAVEN SCIENCE ASSOCIATES

Component schema 20 BROOKHAVEN SCIENCE ASSOCIATES

Component schema 21 BROOKHAVEN SCIENCE ASSOCIATES

Cables 2 3 23 BROOKHAVEN SCIENCE ASSOCIATES

24 BROOKHAVEN SCIENCE ASSOCIATES

25 BROOKHAVEN SCIENCE ASSOCIATES

26 BROOKHAVEN SCIENCE ASSOCIATES

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

Accelerator Cmpnts: Hierarchy + Network (wiring) bldg/APS_412 room/B 102 ‘is housed by’ AC Panel/L 3: El: SO 1 rack/L 3: RA: IO; 3 Circuit/11 ‘is powered by’ ‘is controlled by’ ‘part of acc. sequence’ Power Strip/R MVME-167/ioc_xyz VME Chassis/z 42 VME Power Supply/ IO_Card/4 interlock power supply/ps 1 a magnet/BL 1 A 29 2 9 BROOKHAVEN SCIENCE ASSOCIATES

Component schema 30 BROOKHAVEN SCIENCE ASSOCIATES

Cable schema 31 BROOKHAVEN SCIENCE ASSOCIATES

Cable schema 32 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. 33 BROOKHAVEN SCIENCE ASSOCIATES

Lattice schema 34 BROOKHAVEN SCIENCE ASSOCIATES

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

IRMIS To_Do/Wish List - Web-based PV viewer • inter-IOC/db graphical logic presentation (use the cable gui) • Web. CA 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? 36 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) 37 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? 38 BROOKHAVEN SCIENCE ASSOCIATES

IRMIS To_Do/Wish List (cont’d) 39 BROOKHAVEN SCIENCE ASSOCIATES

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