ILS ASSOCIATES ILS / IPS STRATEGIES Lessons Learned by ILS Associates over 35 years HISTORY • Integrated Logistics Support (ILS) • Integrated Product Support (IPS) • ILS introduced into the UK in 1990 • Mil Stan 1388-1A – LSA Processes • Mil Standard 1388 2A then 2B • DEF STAN 00-60 • DEF STAN 00-600 • AECMA S2000M & S1000D (Now AECMA is ASD plus AIA) • ASD S Series of Standards ILS ASSOCIATES ILS ASSOCIATES SX000 i IPS Prior to IPS ASSOCIATES • CADMID Cycle • Concept, Assessment, Demonstration, Manufacture, In-Service and Disposal • Concept – Design - Operations • Use Cases – Operational – Support (Use Study) • RM&T Programme • Comparative Analysis (Lessons Learned) ILS Integrated Product Support & LSA Process ILS ASSOCIATES Analysis Suggested by S3000L • analysis for the identification of general LSA needs • comparative analysis • human factor analysis • product breakdown and configuration assessment • reliability analysis assessment • maintainability analysis assessment • testability analysis assessment • corrective maintenance analysis, based on existing FMEA/FMECA • damage analysis • special event analysis • PMA • LORA • Maintenance Task Analysis (MTA) • Software Support Analysis (SSA) • operations analysis • simulation operational scenarios • Training Needs Analysis (TNA) • LCC • obsolescence, refer to Chap 15 • disposal (consideration of environmental regulations) ILS ASSOCIATES S3000L Data Model • Units of Functionality – Sub-Models • Classes • Relationships • Attributes (Data Elements) ILS ASSOCIATES S3000L Guidelines ILS Depth of maintainability analysis depending of item type ASSOCIATES • Items currently used under comparable conditions • Moderate information and data transformation, a more detailed maintainability analysis is voluntary • Items currently in use, but not under comparable conditions • Data transformation is mandatory, a more detailed maintainability analysis under new conditions is recommended • COTS items without major modification • The customer must document and agree to any non-compliance of supportability features and/or requirements • Items currently available requiring minor modification • Moderate information and data transformation, a more detailed maintainability analysis is voluntary • Items currently available requiring major modification • Data transformation is mandatory, a more detailed maintainability analysis under new conditions is strongly recommended • Newly developed items based on well-known technology • Detailed maintainability analysis is strongly recommended • Newly developed items based on new technology • Detailed maintainability analysis is mandatory ILS ASSOCIATES UoFs (Qty 41) ILS 41 UoFs • Overall product, project, operational and maintenance context data • • • • • • UoF Product and Project UoF Product Usage Context UoF Facility UoF Location UoF Environment Definition Product structure and part characteristics • • • • • • • UoF Breakdown Structure UoF Part Definition UoF Aggregated Element UoF Hardware Element UoF Software Element UoF Zone Element UoF Product Design Configuration ASSOCIATES • LSA candidate selection, requirements and analysis activities • • • • Maintenance task analysis • UoF Task • UoF Circuit Breaker • UoF Task Resource • UoF Resource Specification • UoF Competence Definition • UoF Task Usage • In-service LSA • UoF Decision Tree Template Definition • UoF In Service Optimization Analysis • General capabilities • UoF Change Information • UoF Security Classification • UoF Organization Assignment • UoF Document • UoF Digital File • UoF Remark • UoF Applicability Statement • LSA messages • UoF Message • UoF Logistics Support Analysis Message Content UoF Performance Parameter UoF LSA Candidate • Corrective maintenance analysis • • • UoF Failure Mode UoF LSA Failure Mode Group UoF Failure Mode Symptom UoF Failure Mode Isolation • Damage and special event analysis • • • UoF Product Usage Phase UoF Special Event UoF Damage Definition • Task requirements and influence on design • • • UoF Task Requirement UoF Time Limit UoF Design Change Request Chap 19 Para 3.27 - S3000L UoF Product and Project Description ILS ASSOCIATES The Product and Project UoF defines the Product(s) which are in focus for the Integrated Product Support (IPS) program. Chap 19 Para 3.3 - S3000L UoF Breakdown Structure Description ILS ASSOCIATES The Breakdown Structure UoF provides the capability to define any number of hierarchical structures for a specific Product or Product variant. Chap 22 – Table 2 - Classes ILS ASSOCIATES Breakdown Class class Breakdown is a <<class>> that identifies a specific partitioning S3000L UoF Breakdown of a Product to form a parent-child structure of related instances Structure of BreakdownElement. Class name Type Stereotype Definition BreakdownElement Class class BreakdownElementInZone Class relationship S3000L UoF Breakdown BreakdownElement is a <<class>> defining a partition of a Structure Product that is used in one or many instances of Breakdown. S3000L UoF Zone Element BreakdownElementInZone is a <<relationship>> where a BreakdownElementInZoneItem relates to the ZoneElement where it BreakdownElementInZone Item Interface extend BreakdownElementRevisi on BreakdownElementRevisi onRel ationship Class class Class relationship BreakdownElementRevisi onRel ationshipItem Interface select BreakdownElements Class exchange BreakdownElementStruct ure Class relationship BreakdownElementStructure is a <<relationship>> that BreakdownElementUsageI nBrea kdown Class class establishes a hierarchical structure between two usages of BreakdownElement that belong to the same BreakdownRevision. BreakdownElementUsageInBreakdown is a <<class>> that UoF is located. BreakdownElementInZoneItem is an <<extend>> interface that S3000L UoF Zone Element provides its associated data model to those classes that implement it. S3000L UoF Breakdown BreakdownElementRevision is a <<class>> representing an Structure iteration applied to a BreakdownElement. S3000L UoF Breakdown BreakdownElementRevisionRelationship is a <<relationship>> where one BreakdownElementRevision relates to Structure another BreakdownElement or BreakdownElementRevision. S3000L UoF Breakdown BreakdownElementRevisionRelationshipItem is a <<select>> interface that provides the capability to be associated Structure with a BreakdownElementRevision. S3000L UoF Logistics BreakdownElements is a wrapper element that contains all Support Analysis Message instances of Content BreakdownElement that are in scope for a data exchange. represents a member of a BreakdownRevision. Note A BreakdownElementRevision can belong to multiple BreakdownRevisions. S3000L UoF Breakdown Structure S3000L UoF Breakdown Structure ILS Chap 22 – Table 3 - Attributes ASSOCIATES Attribute Name Type breakdownElementI dentifier IdentifierType Definition Class Name UoF breakdownElementIdentifier is an identifier that establishes a unique designator for a BreakdownElement and to differentiate it from other instances of BreakdownElement. BreakdownElement S3000L UoF Breakdown Structure BreakdownElement S3000L UoF Breakdown Structure Note Can be used to establish a hierarchical structure of the technical system. Example − The combination of Logistics Support Analysis Control Number (LCN) and Alternate Logistics Support Analysis Control Number (ALC) within SAE GEIA-STD-0007 − The Standard Numbering System (SNS) defined by S1000D breakdownElementName is a name by which the BreakdownElement is known and can be easily referenced. breakdownElementN ame NameType breakdownElementR evisionDate DateType breakdownElementRevisionDate is a date that specifies when the BreakdownElement was revised. BreakdownElement Revision S3000L UoF Breakdown Structure breakdownElementR evisionIdentifier IdentifierType breakdownElementRevisionIdentifier is an identifier that BreakdownElement establishes a unique designator for a BreakdownElementRevision and Revision S3000L UoF Breakdown Structure breakdownElementR evisionRationale DescriptorType breakdownElementR evisionRelationsh ipType ClassificationType to differentiate it from other instances of BreakdownElementRevision. breakdownElementRevisionRationale is a description that gives more information on the justification for revising the BreakdownElement. breakdownElementRevisionRelationshipType is a classification that identifies the meaning of the established relationship. Note The related breakdown elements do not need to be used in the same breakdown ie, it can be used to establish the relationship between a breakdown element in a functional breakdown and a breakdown element in a physical breakdown. BreakdownElement Revision S3000L UoF Breakdown Structure BreakdownElement RevisionRelation ship S3000L UoF Breakdown Structure Class Attributes ILS ASSOCIATES • A Class can have one or many attributes. Attributes are data elements that identify and describe instances of the Class. Each attribute is presented with its attribute name, data type, and cardinality (multiplicity). • Class attributes are divided into categories (stereotypes in UML). Each category is shown within double angle brackets (<<…>>) above the attribute name(s). • There are five categories of attributes: • − <<key>> • − <<compositeKey>> • − <<relationshipKey>> • − <<characteristic>> • − <<metadata>> • Attributes that are required to uniquely identify a Class instance are classified as either <<key>>, <<compositeKey>> or <<relationshipKey>>. Which type of key attribute that is used is dependent on how the Class is defined in relation to other Classes. Attributes that comprise the key are always defined first in the attribute list for the Class. • The Fig 1<<key>> category is used for Classes where the only key attributes needed to uniquely identify a Class instance is defined within the Class itself. Refer to . • The <<compositeKey>> category is used, when <<key>> attributes from a Class instance also require the <<key>> from a parent composition Class to uniquely identify a Class instance. • The 2.5<<relationshipKey>> category is used, when there can be more than one instance of the same relationship type between the same relating and related Class instances. Refer to Para . • The <<characteristic>> category is used for attributes that define the characteristics of a given Class instance (object). Characteristics typically include names, measurable properties, classifications and descriptions. • The <<metadata>> category is used for attributes that define metadata such as the means of creation, author, time and date of creation, etc. Tailoring – Guide Only • PBS - LCN – SNS Based • CI • RAMT • Maintenance • Disposal • Obsolescence • Assets Subject to Special Handling • GFX • ITAR • SSDs • Security • Nuclear – Nuclear Safety • Key Data ILS ASSOCIATES LSA Programme Plan • General • Scope • General Programme Definitions • Management Structure of the Programme on the Customer Side • Management Structure of the Programme on the Contractor Side • Time Sccale of the Programme • Definition of Milestones • Meeting Calendar • Responsibilities and Reporting Levels • Appendices ….. ILS ASSOCIATES LSA Programme Plan Appendicies ILS ASSOCIATES • Purpose of LSA and Supportability Analysis Tasks • System Breakdown Metholodgy • Breakdown Depth • Rules for LSA Candiadte Selection • Candidate Items List • Rules for Analysis Selection • Rules for Performing Measuring and Verification • IT Aspects LSA Guidance Document ILS ASSOCIATES • Data Element List (DEL) – a living document • Is the data element required for the proof of any specification values? • Is the data element required for the calculation of any supportability parameters? • Is the data element required for disciplines such as technical publication, material support, identification of special support equipment, and identification of facilities or training requirements? • Is the data element required for the performance proof of the LSA itself? • Is the data element required to document the results of supportability analysis activities? • Is the data element required for any report, necessary for the customer and/or the contractor? • Is the data element a special interest for the customer/contractor (eg, internal usage)? NEXT? • Tailor Out – Not Tailor In ILS ASSOCIATES
0
advertisement
Download
advertisement
Add this document to collection(s)
You can add this document to your study collection(s)
Sign in Available only to authorized usersAdd this document to saved
You can add this document to your saved list
Sign in Available only to authorized users