Rail Review 14 September 2001

RCM Tools Developed for the RAIL project

Project web Page: http://arcos.inf.uc3m.es/~rail

Jesus Carretero: jcarrete@arcos.inf.uc3m.es

Rail Review 14 September 2001

Main tasks

Developing the database

Developing the RCM CMS

Rail Review 14 September 2001

Specifications and structure of

the database developed

Rail Review 14 September 2001

WP5: WP5: DDatabase requirements I

System Architecture is:

Modular: local database per company, but same structure

Interactive: to promote cooperation and information exchange inside the

company (and inter-companies)

Scalable: local databases should be able to include new information.

Open: to include heterogeneous information and legacy systems

Extensible: to guarantee future usability by including new elements and

operations.

Methodology is:

Based on standards: JAVA, CORBA, SQL, …

WEB oriented to promote remote access and cooperation

Distributed to allow co-operation, integration and scalability

Client-Server paradigm to provide and retrieve information

Rail Review 14 September 2001

WP5: WP5: DDatabase requirements II

RAIL database to:

Extend existing experience from companies, manufacturers, railway

associations, … Similar databases in OREDA, NRPDS, CCPS, US Navy

Mainly used to store anonymous statistical information related with

SCRI LCC, failures, maintenance operations, LCC info and to get feedback

from other sources.

Should be open to external sources of information, and should pervive

the RAIL project.

Integrate existing data bases with legacy information.

Other Company databases to:

Store day-to-day maint. data and operations, local LCCs, local

monitoring, …

Databases should be compatible to exchange information: providing

functions to load and unload data.

Rail Review 14 September 2001

WP5: WP5: DDatabase Functionality

Store lines and their sections and evaluate their states.

Store the components and their SCRIC values of a section and line.

SCRIC analysis of the functional failures, detection of the functional failure

and evaluate for each functional failure the frequency and severity, and the

criticality criteria.

Decision making help and maintenance tasks planning.

Reports on different aspects of the system (lines, SCRIC, functions, etc.) and

statistics of the RCM analysis.

To provide a decomposition of the SCRICs and information of their parts. Store and view the information about the meetings during the RCM process.

Facilities to load and unload data from/to existing databases and plain files

(format to be defined...)

Rail Review 14 September 2001

WP5: WP5: Database Integration

System Integration:

All Data base interfaces in Java: easy communication and

interfacing

Co-operation using Java through RCM Internet Tool

Friendly user interface: all data acquisition using RCM

predefined forms through an Internet based tool.

To define cooperation methods among different data bases

Rail Review 14 September 2001

WP5: WP5: Database organization

RAIL Da ta Ba se

RAIL In fo rm a tio n

Se rve r

C o m p a nyM a inte na nc e

Da ta Ba se

Exte rna lDa ta Ba se

M a int. Kno wle d g eDa ta Ac q u isitio nSta te Pre d ic tio n

M o nito ringLC C

Sta te Pre d ic tio nM o nito ring

M a int. M g m nt.M a int. Pla n

LC C

Da ta Ac q u isitio nM o nito ring

Rail Review 14 September 2001

High Level Design of the RAIL Data Base

Rail Review 14 September 2001

InfrastructureInfrastructure

Infrastructuredata

Line Section Component

Rail Review 14 September 2001

Cost model & LCC

Infrastructuredata

Cost model data Line costs Section costs Component cost ¿LCC data?

Rail Review 14 September 2001

CriticalityCriticality

Infrastructuredata

Cost model data Criticallity data

Line criticality Section criticality Component criticality Component state

Rail Review 14 September 2001

DecompositionDecomposition

Infrastructuredata

Cost model data Criticallity data

Descompositiondata

System Subsystem Mantenible item

Rail Review 14 September 2001

FMECAFMECA

Infrastructuredata

Cost model data Criticallity data

Descompositiondata

FMECA data

Function Failure mode Failure cause

Rail Review 14 September 2001

Failure CriticalityFailure Criticality

Infrastructuredata

Cost model data Criticallity data

Descompositiondata

FMECA data

Failure mode criticality Safety Availability in the line Av. In other lines Cost

Frequency Time to repair

Rail Review 14 September 2001

TASKTASK

Infrastructuredata

Cost model data Criticallity data

Descompositiondata

FMECA dataTask data

Task proposed Selected task

Rail Review 14 September 2001

TASK cost model & LCCTASK cost model & LCC

Infrastructuredata

Cost model data Criticallity data

Descompositiondata

FMECA dataTask data

Cost model LCC

Rail Review 14 September 2001

Groups & MeetingsGroups & Meetings

Infrastructuredata

Cost model data

Criticallity data

Descompositiondata

FMECA dataTask data

Group andmeeting data

Maintenance Group Pilot group Corridor Group Meetings

Rail Review 14 September 2001

RAIL Data Base Management

Rail Review 14 September 2001

Data acquisition

Active maintenance is done based on maintenance people reports.

Preventive maintenance needs: retrieval of qualitative information,

information on reliability parameters and information regarding

maintenace resources, LCC info. Historical information related to

failures.

Predefined forms for maintenance reports (based on expert’s

knowledge)

Condition information acquired via network (Inet, ATM, GSM-R, …)

using RCM predefined forms through an Internet based tool.

Future:

Condition monitoring.

All process should be mechanized: maintenance inspectors with

portable laptops?

Rail Review 14 September 2001

Data format (load)Data format (load)

RAILDB

Company Database

Plain Text FilePlain Text File

Loader

Plain text format: ASCII File with separators Database exchange format: e.g.: Oracle LOAD

Rail Review 14 September 2001

Data format (unload)Data format (unload)

RAILDB

Unloader

Plain Text FilePlain Text File

Reports

Plain text format: ASCII File with separators Reports Maintenance plans

Rail Review 14 September 2001

Results

Database reports:

Retrieval of qualitative information.

SCRIC information.

Information on reliability parameters and information

regarding maintenace resources.

LCC info.

Historical information related to failures.

Maintence plans: flexibility to generate plans with different criteria

Criticality, Urgency, Efficiency ….

Data exploitation: the prototype supports future applications.

Rail Review 14 September 2001

RAIL Internet RCM Toolbox

Rail Review 14 September 2001

Main Functionalities of the DB Main Functionalities of the DB ToolBoxToolBox

Editing lines, sections and components.

Introducing criticallity and failures in a friendly-user mode.

Helping to develop the RCM analysis: templates.

LCC method integrated with the tool and the DB.

Elaboration of reports of proposed task.

Posibility of doing several statistic analysis.

Administration: Data base and project creation. Data feeding using automated methods.

Rail Review 14 September 2001

RAIL Internet RCM Toolbox

Rail Review 14 September 2001

RAIL ToolBoxRAIL ToolBox

Rail Review 14 September 2001

RAIL ToolBoxRAIL ToolBox

Rail Review 14 September 2001

RAIL ToolBoxRAIL ToolBox

Rail Review 14 September 2001

RAIL ToolBoxRAIL ToolBox

Rail Review 14 September 2001

RAIL ToolBoxRAIL ToolBox

Rail Review 14 September 2001

RAIL ToolBoxRAIL ToolBox

Rail Review 14 September 2001

Better to see a DEMO ....