IRMIS Status

EPICS 2009Vancouver

D. A. Dohan

Outline

• IRMIS hardware model• cable/cable run• channel list• Equipment Inventory System

• RDB Domain separation• High Level Application support

• lattice• TRACY3/Elegant deck generator

• Process Variable Introspection• pv groups• pv aliases• pv to channel

• IRMIS Code-a-thon• PHP integration/support

• PHP work at APS• PHP work at MSU/NSCL• Architecture

• Future Plans

General observations:

• RDB services are now considered a basic requirement for machine commissioning and operation – support for High Level Applications• proven availability of RDB services (hardware

redundancy, load balancing, …)• shift in emphasis in IRMIS from descriptive to

prescriptive

• the RDB schema and application suite continues to evolve as each application is rolled out• requires an agile programming environment,

where enhancements to the relational database can be made to an operational production system

Cables(Signals)Cables

(Signals)

LatticeLattice

Software(Global

EPICS/PV Logic)

Software(Global

EPICS/PV Logic)

Hardware(component

model)

Hardware(component

model)

IRMIS Overview

IRMIS Hardware Model Enhancements

- separation of the Component Installation from the Equipment Inventory System:

- allows the ‘installation’ of infrastructure items that are not typical EIS inventory items (rooms, racks, etc).

- allows multiple configurations (e.g. ion source, RF, beamlines, etc)- the EIS contains items that are not installed (spares, stock)- completely separate applications (domain separation between the installer

and the EIS).

- The installation schema has strict validation requirements – the data can be independently verified by inspection, whereas the EIS will generally be unverifiable. (domain specific validation requirements)

“Parts Assembly Instructions”

Equipment Inventory (History)

IRMIS Loose Coupling and Domain Separation

• The Equipment Inventory System is a separate RDB sub-domain, (it contains the foreign key to the main install table)• The EIS has a separate schema and application development

prototyping cycle. Each site has different EIS requirements (maintenance cycles, certification, calibration, …)

• The install schema has stringent data integrity requirements – database constraints, application business rules, test routines, external validation.

• The install schema provides the basis for a number of domains/applications that are dependent on the install data consistency.

• Additional sub-domains loosely coupled to the install domain:• lattice• cable• pv::channel

IRMIS Domain Separation: Separate schema and application development cycles

IRMIS Lattice Schema

• The IRMIS lattice schema provides a 4th hierarchy – ‘the accelerator hierarchy’• a hierarchy of nested sequences, ultimately containing the

target beam delivery components (magnets, bpms, …)

• IRMIS Data Service Layer support

IRMIS lattice schema

I/OChannels

I/OChannels

Cables(Signals)Cables

(Signals)

LatticeLattice

Software(Global

EPICS/PV Logic)

Software(Global

EPICS/PV Logic)

Hardware(component

model)

Hardware(component

model)

IRMIS Overview

IRMIS codeathon, Apr. 21-23:

Participants: Debby Quock (ANL), Eric Berryman (National Superconducting Cyclotron Lab), Guobao Shen, Don Dohan, Bob Dalesio and Gabriele Carcassi (BNL).

Highlights: • Using WebStart to support GUIs on Macs • Import/export lattice information in Tracy-3 format • Fixed a couple of problems in the UI (including a concurrency bug that caused applications to fail with large datasets)• Improvements in the Java API (findByFieldName for components and saving the XML of a transaction)

IRMIS codeathon, Apr. 21-23, (cont’d)

We had a number of planning/design discussions, especially to coordinate future developments at ANL and at NSCL.

NSCL has already built PHP-based inventory tools on top of IRMIS3. Given the interest in PHP support, we are going to investigate how to take some of the work done at NSCL and turn it into a PHP library bundled in the IRMIS3 distribution.

We also need some kind of “issue tracker” to manage the todo list.

(G.C.)

Prescriptive PV

Prescriptive PV

I/OChannels

I/OChannels

Cables(Signals)Cables

(Signals)

LatticeLattice

PVIntrospection

PVIntrospection

Software(Global

EPICS/PV Logic)

Software(Global

EPICS/PV Logic)

Hardware(component

model)

Hardware(component

model)

IRMIS Overview –New Developments

IRMIS Plans

• PV introspection• centralized location of EPICS and physics name aliases• central management of pv service applications (archiver,

alarm handler, SCORE, machine snapshot, etc)

PV introspection (development)

pv

EIS

lattice, snapshot

crawlercrawler

install

IRMISData

Services

IRMISData

Services

HLAHLA

Accelerator RDB editors/applications - Loose Coupling

NSCL/NSLS/CIDB…

NSCL/NSLS/CIDB…

IRMIS Wish List

• ‘Link’ expander• expand link component network topology (network virtual

circuit, etc)

iocioc

ethernet linkethernet link

network attached devicenetwork attached device

network attached devicenetwork attached device

IRMIS plans/wishlist

• PV introspection• centralized location of EPICS and physics name aliases• central management of pv service applications (archiver,

alarm handler, SCORE, machine snapshot, etc)

• capture cable signal information – Petri-net analysis• end-to-end signal tracing (e.g. timing signal)• drill down for cable database application

pv

EIS

lattice, snapshot

crawlercrawler

install

IRMISData

Services

IRMISData

Services

HLAHLA

Accelerator RDB editors/applications – Technology Selection

NSCL/NSLS/CIDB…

NSCL/NSLS/CIDB…