A day in the life of the S Series - ASD/AIA SX000i ILS Day S4000P-Haslam P.pdf · "A day in the life of the S ... S1000D S2000M Logistic Support Design of Product systems and support

© 2015 ILS Spec Council 2015‐09‐24

"A day in the life of the S‐Series"International specification for developing and

continuously improving preventive maintenance

Stefan Schiele

September 24, 2015

Prepared by:

Organization:

ILS S‐Series Spec Day

Presented by:

Organization:

Paul Haslam

© 2015 ILS Spec Council© 2015 ILS Spec Council

SX000i / SX001G / SX002D

S4000P

S3000L

S1000D

S2000M

LogisticSupportAnalysis

Des

ign

ofP

rodu

ctsy

stem

san

dsu

ppor

tequ

ipm

ent

Pro

duct

In

-ser

vice

use

Orderadmini-stration

Technicalpubli-

cations

IETM, other media

Source: Airbus D&S - Saab

Developing and cont.improving preventive

maintenance

S6000TTraining

information

Operationaldata

S5000FProduct In-service feedback and other relevant data

LSAdata

Taskdata

Designdata

Designdata

Provisioningdata Logs mat

and data

IP DataSubsets

Pro-visioning

Designdata


Title of initial version ASD S4000M Issue 1.0(not officially published):International specification for developing scheduled maintenance programs

Development of ASD S4000P Issue 1.0 since 2012 and published on 24th May 2014 with the following new title:International specification for developing and continuously improving preventive maintenance

New ASD scope,extented applicationson technical Products,coverage of the whole

Product life cycle

History:

ASD S4000P, Issue 1.0 History of the specificationASD S4000P, Issue 1.0 History of the specification

www. s4000p.org


• Chapter 1 Introduction to the specification

• Chapter 2 Development of preventive maintenance task requirementsAnalysis methodologies for Product

Systems Structure Zones (modular)

• Chapter 3 Continuously improving preventive maintenance

In-Service Maintenance Optimization (ISMO) process

• Chapter 4 Interfaces of S4000PInterfaces from S4000P to outside the S-Series of AIA/ASD S-Series of Specifications and inside the S-Series

• Chapter 5 Terms, abbreviations and acronyms

• Chapter 6 Examples

ASD S4000P, Issue 1.0 Content of the specificationASD S4000P, Issue 1.0 Content of the specification


ASD S4000P, Issue 1.0 Scope of Chapter 2ASD S4000P, Issue 1.0 Scope of Chapter 2



Analysis methodologies for Product systems, structure and zones to evaluate the

maintainability (including accessibility) of the Product design prior to its Critical

Design Review (CDR) during the Product development phase in order to

determine applicable and effective scheduled maintenance tasks and/or to

require or recommend design changes in due time


ASD S4000P, Issue 1.0 Chapter 2, System Analysis (1/5)ASD S4000P, Issue 1.0 Chapter 2, System Analysis (1/5)



The Product System Analysis is

composed of four sequential steps:

Step 1

Step 2

Step 3

Step 4

Analysis RelevantCandidate (ARC)





Step 1





Step 2





Step 3





Step 4

Time Change Item (TCI)


ASD S4000P, Issue 1.0 Mountain bike example and application of Chapter 2, System Analysis (1/7)


Selected candidate for an S4000P System analysis:Brake system

Front Brake SubsystemFront Wheel V‐Brake

Allocation of Product Breakdown

Items 1,2,3,4 belong to

Items 5,6,7 belong to

Item 8 belongs to

DA1Brake System

DA1‐10Front Brake Subsystem

DA1‐10‐30Front Wheel V‐Brake

DA1‐10‐30Front Wheel V‐Brake

BC‐2000015Front Brake

Activation Cable

DA3‐30Fork


ASD S4000P, Issue 1.0 Mountain bike Product breakdown example and application of Chapter 2, System Analysis (2/7)

ASD S4000P, Issue 1.0 Mountain bike Product breakdown example and application of Chapter 2, System Analysis (2/7)

….

…

…




DA1 BrakeSystem

YES NO YES NO YES08/15007Worst caseFF is safetyimpactduringdownhillperiod

Result of ARC determination:Break System is selected as an Analysis Relevant Candiatebecause of the YES answer in the determination questions

System AnalysisStep 1




Brake System

DA108/15

… … … … … …Front brake toproduce frictionfor deceleration

Frictionfor decelerationis reduced

No reductionof frictionfor deceleration

F41

… … … …

FF41‐1

FF41‐2

FFE41‐1‐1

FFE41‐2‐1

Potential crashduring downhillsafey impact

FFC41‐1‐1‐1

Front brakeactivationcable looseor seperatedFront brakelever brokenor jammed

FFC41‐1‐1‐2

Extended brakingdistanceduring downhill ‐safey impact

FFC41‐2‐1‐1

Front brakepads max. detertiorated

… … … … … …… … … …

60%

20%

50%

main FFCidentifiedfor FF 41‐1

FFC

FFC

FFC


FunctionalFailureCause(FFC)

One or moreFailureCause(s) allocated toeach FF with FFE




System AnalysisStep 3 FF categorization for FF41‐1 and FF41‐2

Result of FF categorization:BothFunctional Failures (FF)FF41‐1 and FF41‐2may result in Evident Effects Safety(FFEC1)





PMTR 1: Operational test by activation of brake leverINTERVALL: Prior to start a mountainbike tour

PMTR 2. Inspect front cable assy for visible wearPMTR 3. Check torque moment of fixation nuts of front brake cable assyINTERVALL: Yearly (*)

(*) depending on usage scenario

FFEC1

Result of FC assessmentof FFC 41‐1‐1‐1:

PMTR 1: Operational test…Interval: Prior to MB Tour

PMTR 2: Inspection of front cable assyfor wearInterval: 1 Y

PMTR 3: Check torque moment offixation nut (Item 6) of front brake cable assyInterval: 1 Y

Remark:All PMTR selected in parallel due tocriticality FFEC 1




Summary for the system analysis of the mountain bike example:1. Based on the System‐FMEA (Step 2) the FF categorization sheet (Step 3) must be applied for each

identified FF. 2. Based on the System‐FMEA (Step 2) the FC assessment sheet (Step 4) must be applied for each

identified FC. The selection of PMTR or the intensity to require design changes/improvements depend on the criticality category (= FFEC) of the FF.

In this example, one FFC 41‐1‐1‐1 has been assessed and 3 PMTR with 2 different intervals have been determined:

S3000L CandidatePMTR 1: Operational test of front brake sub‐systemInterval: Prior to MB TourS4000P criticality code: FFEC1

S3000L CandidatePMTR 2: Inspection of front brake cable assy for wearInterval: 1 YS4000P criticality code: FFEC1

S3000L CandidatePMTR 3: Check torque moment of fixation nut (Item 6) of front brake cable assyInterval: 1 YS4000P criticality code: FFEC1

TransferPMTRinto S3000LDatabase


Activation Cable

DA1‐10Front Brake Subsystem


Activation Cable


ASD S4000P, Issue 1.0 Chapter 3 InformationASD S4000P, Issue 1.0 Chapter 3 Information

In Service Maintenance Optimization (ISMO):

ASD S4000P is not limited to the development of PMTR only but it also covers the

assessment of scheduled maintenance of a Product during the Product In‐Service Phase

ISMO is a logic based optimization methodology that uses In‐Service experience/data and

other sources (eg, test/simulation results, experience from other Products or customers)

Uses S5000F to evaluate the applicability and effectivity of existing scheduled maintenance

tasks which are allocated to criticalty safety or law (eg. to delete, substitute those tasks or

to adjust intervals), the need of additional scheduled tasks or to provide feedback to

Product design.

Therefore ASD S4000P is the only specification covering the whole Product Life Cycle from

the scheduled maintenance point of view

© 2015 ILS Spec Council

Inputs

DesignOEM/Manufacturer/SupplierEngineering drawingsEngineering data (failure rates)Product design breakdownFMEA/FMECA (ILS domain)

LegalCustomer legal requirementsGeneral applicable lawsEnvironmental lawsHealth & safetyCertification & qualification

Customer requirementsThe ProductUse case (normal & crisis)Maintenance philosophy, rules, guidanceReliability requirementsAvailability requirementsCriteria of significanceIn‐service budget

S4000P

Systems analysis

Structure analysis

Zonal analysis

In‐Service Maintenance

Optimization (ISMO)Ha

rmon

ize re

sults

Preventive Maintenance

Task Requirements (PMTR) with intervals

plusbackground

data for each PMTR(eg. criticalityallocation)

Outputs

Maintenance Task Analysis (MTA), PMTR packaging, Operator Maintenance Plan (OMP)

Maintenance planning Data Module Code (DMC)

Usage

Feedback from In‐Service phase on preventive maintenance tasks:‐ Missing‐ Not required‐ Improvement etc.

Elaboration of

Policy & Procedures Handbook (PPH)for

developing PMTR (incl.identification of systems requiringan analysis)

or forISMO

to improve preventive maintenance

during In‐Service

Collection ofIn‐Service Data and Feedback

© 2015 ILS Spec Council

Please visit: www.s4000p.org

Contact: ASD‐[email protected]

Request a free specification download http://www.s4000p.org/docs/S4000P_Issue_1.0.pdf

More information?

Documents

A day in the life of the S Series - ASD/AIA SX000i ILS Day S4000P-Haslam P.pdf · "A day in the life of the S ... S1000D S2000M Logistic Support Design of Product systems and support