australian defence force airworthiness

Copyright 2008Pennant Australasia Pty Ltd

OmegaPS and Analyzer Users Group Meeting2008

Australian Defence Force Airworthiness

a general overview

David StephanGeneral Manager

Melbourne, Australia


Australian Airworthiness

• Australian aviation controlling bodies:

– CASA Civil Aviation Safety Authority• Equivalent to the US FAA

– DGTA Directorate General Technical Airworthiness• Manages procedural framework for maintaining airworthiness of

defence assets


DGTA-ADF

• Provides military technical airworthiness services for the ADF influencing:– Design– Maintenance– Quality assurance regulation– Systematic risk management approaches

• Systems Program Offices (SPO) are the front line for these services


Systems Program Office

• Systems Program Offices (SPO) are responsible for specific platforms or equipment types– Equipment

• GWEOSPO – Guided Weapons & Explosive Ordnance• GTESPO – Ground Telecommunications Equipment

– Platforms• LIFSPO – Lead In Fighter (Hawk 127)• SRSPO – Strike Reconnaissance (F-111)• TFSPO – Tactical Fighter (F/A-18)

• Senior Engineers manage SPO activities


Senior Engineers

• Technical responsibility for platform/equipment airworthiness:– General Airworthiness– Engineering approvals– Maintenance– Procedural airworthiness (DGTA)


Simplified Process Chain

DGTA

SPO

SeniorEngineer

Policy

Implementation

Authorisation

Maintainers Action


Australian Airworthiness &the LSAR

• ADF utilises LSAR as a source of airworthiness engineering and maintenance data

• 1993 - RAAF airworthiness extensions to 1388-2B• 1994 - RAN (Naval Air Logistics Office) adopted most RAAF extensions

and added several others.• 1996 – Extensions formalised as defence publication - AAP 5102.003


Evolution - Airworthiness LSARs

• 2000 - Revised extensions to support tri-service business:– DEF(AUST)5691 – Logistic Support Analysis– DEF(AUST)5692 – Logistic Support Analysis Records

• DEF(AUST)5692 embodies general LSA/LSAR and airworthiness


Evolution from Standards to Tools

US MIL-STD-1388 2B

RAAF

NALO

Omega2B

US MIL-STD-1388 2B

Airworthiness

Tri-Service

OmegaPS

Old Current

AAP 5102.003 DEF(AUST)5692


DEF(AUST)5692

• ADO Table Groups– M – Memo Narratives

• Primarily for reports– R – ADO Tasking

• Separates ADO task data from 1388-2B C tables– V & W – ADO functionality

• Extensions to core table (eg. Attributes additional to XB, HG etc)• Additional ADO data

– ZL – ALC relationships• Allows ALCs within ALCs• Clarifies XB record parentage

• Addresses four broad functional areas:– Standard 1388-2B– Equipment Configuration– Technical Maintenance Plans– Servicings


Equipment Configuration

• Physical and Functional configurations using 1388-2B principles• For each configuration a complete Physical structure is built as an ALC

to the “A” indenture• UOC rules for “A” indenture prevent cross ALC links• The ZL table is utilised to clarify ALC relationships, also permitting ALCs

to exist with other ALCs.• Most 1388-2B structures can be adapted to ADO requirements• Alternate Configuration Reference Numbers provide specific fitment

authority for alternate parts


Alternative Configuration Reference Numbers

LCN/ALC CAGE/REFNUM

UOC

ACRN Set 00•CAGE/REFNUM•CAGE/REFNUM•CAGE/REFNUM•CAGE/REFNUM•CAGE/REFNUM•CAGE/REFNUM

A set of alternates•For this ‘prime’ part•Not related to ALCs•Not related to ARNs

Authorised To Fit (ATF) as an alternate for this LCN/ALC/UOC?•Various Codes

• Sets are built to a primary CAGE/REFNUM and reusable• Identifies Authority To Fit specific parts to a configuration

• Related functionality includes Role Required Fit


Technical Maintenance Plans

• Maintenance policy is identified for system and sub-systems• LCN - General information

– Work Area Codes– Required Fitment– Roles and fitment– Alternative Configuration Reference Numbers (ACRNs)– And others…

• TMP Task – Specific policy– Action (eg. Total Repair)– Interval (multiple types)– Initiating Conditions (specific triggers)– Skills– Technical Manuals– Facilities

• TMP are identified by a “T” in the 5th position of the task code– Sub-ordinate data stored in separate data tables.– Technical Mainintenance Plan documents generated via Publisher– TMP documents are part of airworthiness


TMP Reports

• Part 2– Summarises Scheduled Servicings

• Type• Intervals• Publications• Facilities

• Part 3– Identifies Maintenanance Managed Items (MMIs)– Maintenance Policy Summary– Maintenance Description

• Part 4– Cross references CAGE/REF NUM and relevant ADO management

codes• Technical Management Codes (older method)• TMC and LCN (hybrid)• LCN (new method)


Servicing Tasks

• TMP tasks define maintenance policy• Servicing Tasks detail the maintenance activity to support policy

– Identified by a “P” in the 5th position of the task code• Sub-ordinate data stored in separate data tables.• Appear in Planned Servicing Schedule documents generated via

Publisher• PSS documents are part of airworthiness


Servicings

• Servicings embody Technical Maintenance Policy• Result in detailed work card instructions for maintainers• Servicings Codes

– Special– Routine– Others as required

• Servicing Codes may be common to a platform• Servicing Codes tied to UOC identify variant specifics


Servicings

• May require maintainer or Senior Engineer signatures• Title and description• Specific

– Intervals– Technical Manuals– Facilities– Claimed Servicings– Sequenced Servicing Tasks arranged in groups


Outputs

InputsOtherPolicy Servicing Data

Functional ElementsAirworthiness•One or more EIAC•Platform or Equipment based•All variants

LCN Data•Work Area Code•Required Fitment•Role Fitments•ADO Criticality•ACRN

TMP Reports•Part 2 -Summary•Part 3 – MMI detail•Part 4 – Cross Reference

Planned Servicing Schedules•By Servicing ID•UOC•Sign Up Requirement

TMP Tasks•Interval•Initiation Events•Facilities•Technical Manuals

Servicings•ID•Sign Up requirements•Title•Intervals•Facilities•Technical Manuals•Claimed Servicings•Grouped & Sequenced

Servicing Tasks

Servicing Tasks•Work Area Code•Skills•Intervals•Facilities•Technical Manuals•Claimed Tasks• etc.

•Traditional 1388-2B•Additional ADO elements•Customer extensions

Other•TMP Change Reports•LSA reports w/ADO•Viper•LinkOne


In-Service Application

• Repository for TMP and PSS airworthiness data• Outputs TMP and PSS documents• SPO managed for revisions to equipment or maintenance• Feeds the CAMM2 (Computer Assisted Maintenance Management)

system• CAMM2 is the in-service maintenance management tool• Links between the LSAR and CAMM2 to be developed using XML• Provides outputs for other defence applications

– LinkOne– Viper


ADO Projects and Industry

• Existing platforms/equipment– ADO developed over past 15 years– Minimum data entry to support TMP and PSS– Maintained by SPOs, sometimes sub-contracting Primes/OEMs

• New platforms/equipment acquisition– OEM developed LSARs– Based on 1388-2B or 00-60 in-house LSARs– Revised to suit 5692 or,– Developed from scratch for 5692– May form part of in-service maintenance contracts


Questions for industry to Project Offices

• Does the ADO project have airworthiness requirements?– Yes, ADO Module is required– No, ADO Module may not be required

• What are the DED requirements?– Equivalent to DD Form 1949-3 should be supplied– Identifies if TMP/PSS or other tri-service DEDs are required

• Are TMP/PSS reports a contract deliverable?– Yes, Publisher is required to produce the PDF reports– No, Publisher is optional

• RCM required?– Yes, ADO & RCM-E Modules may be required (airworthiness)– No, RCM-E may not be required – RCM-E supports ADO requirements for decision logging/tracking

and ADO Criticality identification


Points of Interest

• When the ADO module is used:– Most add-on modules recognise the additional DEDs and tables

– RCM-E has some additional functions• Logging of all justifications in the Reasoning Narrative• Generates ADO Criticality codes based on logic

– Change Management• Tracks individual users and DEDs, or• Tracks all changes

– Failure Mode Referencing– LSA to ADO Task mapping– Libraries for ADO data


DEF(AUST)5692 future

• Ongoing development of tables and functionality to support ADF• JP2077 Ph 2D – Logistics Integration• SCR3 – further expansion for airworthiness• Integration with other standards


Thankyou for your time

australian defence force airworthiness

Documents