Transcript Slide - Cern

Data Management section
Controls group
Accelerator & Beams department
Limits of Responsibilities in our
Domains of Activities
Ronny BILLEN, CERN AB/CO/DM
14 December 2006
CO3
Domains of Data Management
Technology:
ORACLE, in-house design;
ASP browsing interfaces;
Oracle Forms data
manipulation
Scope:
all physical equipment,
installed or not, requiring
maintenance or follow-up
Technology:
D7i commercial software;
custom layer by CERN/TS:
Manufacturing and Test
Folder (MTF), integrated in
Engineering Data
Management Service
(EDMS)
14 December 2006
Controls
Configuration
Machine Layout
QA
Assets
Operational
Data
Scope:
Equipment classification,
identification, naming
Technology:
Quality Assurance Plan,
document approval cycle
CO3
Scope:
Controls system topology;
software device mapping &
addressing, front-end
computer configuration,
communication mechanism
Technology:
ORACLE, in-house design;
Oracle Forms (legacy);
JAVA APIs
Scope:
On-line data for operations:
Settings, measurements,
long-term logging, alarms,
post-mortem
Technology:
ORACLE, in-house design;
APIs in Java, PL/SQL, XML
R. Billen
Scope:
All components in the
accelerator installations:
magnets,..., electrical
circuits, racks, electronic
modules,...
Data Management - 3
Data management responsibilities
–what has changed over the years–
General policy has evolved


AB/CO provides necessary database and interfacing software
implementation (DB objects, DB APIs, generic applications)
All data can be –and should be – centrally managed, organized
in the distinct interlinked areas:
•
•
•
•




Operational data: LSA settings, measurement, logging, alarms, P-M
Controls Configuration: s/w devices, h/w config, working sets, knobs
Layout: all installed equipment (machine, electronics,...)
Assets: real equipment characteristics, maintenance, traceability
The owners of the information (equip & operation groups) have
the responsibility to enter, validate and keep the data up-to-date
AB/CO provides active support, advise and guidelines to the
clients for effectively using the tools
AB/CO does perform data entry in case of bulk loading of initial
data sets, data migration from one place to another
AB/CO is open to respond to specific requests on reporting tools
and data manipulation such as global updates
14 December 2006
CO3
Data Management - 4
R. Billen

General responsibilities
CO/DM responsibility








Client responsibility




Providing & maintaining necessary database and interfacing software
implementation (DB objects, DB APIs, generic applications)
Data migration & bulk loading of initial data sets
Providing of necessary data browsing tools
Providing of necessary data manipulation tools
Providing support, advise and guidelines on the database and tools
usage
On request, cater for specific data manipulations
Ensure quality of service, required availability of data, diagnostics
Enter the data. Semantically Validate & Maintain correctness of the
data. The data is owned by the equipment group
Provide specs on additional requirements on top of the generic tools
Note that CO/DM clients are Equipment Groups (incl. CO) and AB/OP
IT service and responsibilities


Database hosting: operating system and Oracle system software
installation, maintenance (upgrades, patches)
Interventions in case of system failures
14 December 2006
CO3
Data Management - 5
R. Billen

Responsibilities – Machine Layout
LHC, TI2, TI8, TD62, TD68







SPS, TT10, TT20, TT40, TT41, TT60




Functional Layout database infrastructure & tools: CO/DM
Data capture racks, electronics, electrical circuits, optics: CO/DM +
EquipGroups
Initial data capture transfer lines : CO/DM
Other data capture: TS/IC + EquipGroups
Data maintenance (beyond 2007): EquipGroups
Note: the database can cover any installed equipment
SPS ring (old) database and data: CO/DM (R. Billen)
TL not managed any more; data directly in LSA: AB/OP + AB/ABP
Note: limited scope (does not include vacuum chambers, apertures,...)
PS complex



ACCIS (old) database infrastructure (ABS): CO/AP (J. Schinzel)
Data maintenance: AB/OP
Note: medium-term maintenance uncertain
14 December 2006
CO3
Data Management - 6
R. Billen

Responsibilities – Controls Configuration

Database, browsing tools, data manipulation tools : CO/DM

Infrastructure development and maintenance
• Includes APIs (JDS, FESA DMS)
• Does not include the FESA toolset (CO/FE)
Data entry and data maintenance : EquipGroups




Data entry and maintenance : AB/OP



Software configuration of front-end devices (e.g. classes, properties,
fields) for implementations GM, SL-Equip and FESA
Hardware configuration of front-end devices (e.g. memory addressing,
straps)
Expert working sets and knobs configuration
Console manager definitions
Operational working sets and knobs configuration
Data propagation tools to other services : CO/DM




Local data generation: FEC boot files; PLC firmware; SCADA config file
Controls communications middleware (CMW)
High level operational controls database (LSA)
On request: additional reporting facilities, ad-hoc expert queries, bulk
uploads, updates
14 December 2006
CO3
Data Management - 7
R. Billen

Responsibilities – Assets
EDMS-MTF



ABCAM portal : CO/DM





Hosting of assets data before going to MTF
Development of limited set of data entry tools in ABCAM
Development of custom reporting tools on the asset management
Explain, advise, initiate, help the equipment group with the usage of
ABCAM
Assets data : EquipGroups


Single central asset management system for all equipment that needs
maintenance or follow-up. TS/CSE
Explain, advise, initiate, liaise, help the equipment group with the usage
of MTF : CO/DM
Gather, check, validate and provide assets data in the required format
Quality Assurance : CO/DM


Assist equipment groups in the definition of equipment codes for the
SPS and the PS-complex
Endorse and publish official equipment codes, to be used in equipment
design, drawings, documents, assets, layouts and operational data
14 December 2006
CO3
Data Management - 8
R. Billen

Responsibilities – Operational data
Operational settings





Measurements and Logging






LSA database infrastructure : CO/DM
LSA application database APIs : LSA team, assisted by CO/DM
Definition and generation of parameters and their values : AB/OP
Propagation of external data into LSA : by CO/DM on LSA
request
Database infrastructure, APIs (Java, PL/SQL, XML) : CO/DM
Measurement applications : CO/AP (Java) and CO/IS (PVSS)
Measurement to logging (filtering) API: CO/DM
Providing tools for operational summaries, statistics,
performance reports : CO/DM
Definition and generation of variables and their meta data :
EquipGroups (...but validation can take some effort of CO/DM)
Alarms – Post-Mortem

R. Billen

No direct responsibility of CO/DM
14 December 2006
CO3
Data Management - 9