This project has received funding from the European Union’s Horizon 2020 Research and Innovation programme

under Grant Agreement No 730871.

Concept of RAMS Information System

CERN/18th Sept 2017/Workshop

AIT Austrian Institute of Technology
A. Preinerstorfer, H. Humer, T. Gruber, P. Böhm

1
High Level Architecture of Information System
by Johannes Gutleber
Fault tracking,
Logbooks,
Historical Observations,
records Estimates

Handbooks,
Data initatives
Information
System

PDF(characteristics, quality, conditions)

Model driven
Design and improvement

2
Overview
• RAMS parameter

MIL-Handbook 127, ISO 14224 (OREDA), ISO 6527,

etc.

Taxonomy of parameters

• Scheme of information element

• Components of Information System

3
RAMS parameter
• Operational information
Operating pressures & temperatures, materials of
construction, medium characteristics, age
• Equipment data
describing the "life" of some equipment notably related to
failures and maintenance.
• Event data
describing all events concerning the system functioning,
maintenance, etc. These data can be divided into classes:
o failure data: information about all accidents/incidents
(time of happening of event, site, conditions,
consequences, persons involved, etc)
o maintenance data –information about corrective and
preventive maintenance (time, duration, conditions,
cost, etc);
4
 ISO 14224:2016
Aim:
• Collection of reliability and maintenance (RM) data in a
standard format for equipment in all facilities and
operations within the petroleum, natural gas and
petrochemical industries during the operational life cycle of
equipment
• Defines equipment taxonomy and standard processes for
collection, merging and analysis of reliability data

Key Aspects
• Equipment data e.g. class boundary definitions
• Failure and activity codes
• Time definitions
• Consequence severity assessment
• Quality of data e.g. completeness of data

7
 ISO 14224:2016
Taxonomy
• systematic classification of items into generic groups based on factors possibly
common to several of the items

8
 ISO 6527:1982 Nuclear power plants - Reliability data exchange - General guidelines

This standard was last reviewed and confirmed in 2015. Therefore this version remains current.
This standard identifies the typical parameters of a component that permit it to be characterized
unequivocally and to allow the corresponding reliability data to be associated with those of other
components having equivalent typical parameters. Parameters refer to technical characteristics
including the physical principle of operation and quality level and to actual operating conditions
and maintenance and test intervals.
• Component characteristics are separated into
• Technical characteristics
• Quality characteristics

• Operation characteristics
• Normal operating conditions
• Maintenance and test intervals
• Environmental conditions

• Failure data may be represented both

• in a historical and
• in a statistical form.

• Mode-of-failure classification
• The failures shall be linked to their
mode of failure

9
Taxonomy of parameters
• Equipment
• System
• Subsystem
• Component Equipment

• What else?
System

Subsystem

Component (Specific ID-code)

10
9/18/2017 Document reference 11
 Scheme of information element
In this proposed scheme the COMPONENT is the smallest unit. Each
component has a defined component boundary.
Origin
(manufacturer)

Master Data
Design
(Technical
Characteristics
Attributes)

Operating
Parameters

Component Operation
Operating Time Derived from ZEDB
(specific ID-code) Reports database
Standby Time

Failure Event

Event Reports
Maintenance &
Inspection
Intervals

12
 Components of Information System
Roles
Data Collection
Administrator
Origin Objects Taxonomy
• Historical • Components • Equipment
Component
Records • Operation • System Provider
• Fault Tracking • Failure • Subsystem
• Logbooks • Maintenance • Component
• Observations Quality
Manager
• Handbooks
• Data Initiatives
Information
User
• Role model
Anonymization
• Validation & trust of user

• Statistical data (MTTF, MTTR)

Analysis • Queries (by component,
subsystem, system)

User Interface
• Import & Export of data
(GUI)
13
Role Concept

Links between
roles possible!

14