SPEC 2000 MODIFICATION REQUEST - Honeywell
SPEC 2000 MODIFICATION REQUEST
Type or Print Clearly
For ATA Use Only
SMR CONTROL NO. __________________
1. TITLE OF PROPOSAL: Reliability Data Collection
2. MAIN DOCUMENT AND DATA DICTIONARY CHAPTERS/SECTIONS OF PRIMARY IMPACT: (Include Attachments)
This SMR proposes the first draft of the entirely new chapter 11 for spec 2000.
It includes proposed modifications and additions to data dictionary (CSDD).
3. DESCRIPTION OF CHANGE:
The purpose of this chapter is to provide a set of standardized record formats for collecting and exchanging aircraft reliability data.
4. USER JUSTIFICATION:
To date a variety of collection methods, unique to individual companies, make any attempt to exchange data or measure reliability across the industry time-consuming, costly and subject to error. The development and implementation of standard record formats for collecting and exchanging aircraft reliability data will enable the industry to collect, measure and exchange this information in a consistent format – ultimately improving efficiency and reducing both costs and errors.
5. SUBMITTER INFORMATION
ROBIN___________________________________ 2 May 2000________
(Print Name) (Date)
_____________________________________________
(Signature)
Director Logistics Engineering______________________________________________
(Title)
Thomson-Csf Sextant ______________________________________________________
(Company)
Aerodrome de Villacoublay Velizy France_____________________________________
(Address)
(33) 1 46 29 72 21_ (33) 1 46 29 53 20 bernard.robin@thomson-csf.
(Phone) (Fax) (E-Mail)
SPEC 2000 MODIFICATION REQUEST
INSTRUCTIONS
A. Statement of Purpose
A SPEC 2000 Modification Request (SMR) is a form prepared by a user to initiate changes to the Specification, report urgent maintenance requirements, or propose enhancements to system operation under Specification 2000. The SMR Control No. will be assigned by ATA and used for control and references as the SMR proceeds through the review process. Any SPEC 2000 user may submit an SMR.
B. Form Completion Instructions:
| | | |
|1. |Title of Proposal |A short, descriptive phrase identifying the topic of the requested change. This |
| | |will be used along with the SMR Control No. to identify the SMR. |
| | | |
|2. |Main Document and Data Dictionary |A detailed citation of the SPEC 2000 Data Dictionary or Common Support Data |
| |Chapters/Sections of Primary Impact |Dictionary and the Specification chapter and section to be modified. |
| | | |
| | |SPEC-ready documentation is required (see explanation below). |
| | | |
|3. |Description of Change |A detailed explanation of the proposal and objective of the modification. Include|
| | |estimated impact on resources and existing users/systems. |
| | | |
|4. |User Justification |Explain why the modification should be made, including tangible and intangible |
| | |benefits, anticipated cost savings, or regulatory requirement. |
| | | |
|5. |Submitter Information |All information must be completed. Submitters must have the appropriate authority|
| | |within their companies/organizations to request the modification. |
C. SPEC-Ready Documentation:
All SMRs must be submitted with detailed and comprehensive attachments clearly showing the proposed changes (e.g., marked up copies of affected pages). If applicable, documentation should include SPEC 2000 examples.
D. Routing Instructions:
Send completed form with attachments to:
Air Transport Association of America
SPEC 2000 Program
1301 Pennsylvania Avenue, N.W., Suite 1100
Washington, D.C. 20004-1707. USA
Tel. 202-626-4039
ARINC/SITA: WASMMXD
Fax. 202-626-4081
TABLE OF CONTENT OF THE SMR
CHAPTER 11 SPECIFICATION
Overview
Purpose
General use of reliability data
Aircraft reliability data
Glossary of terms
Section 1 - Component Reliability Data Collection/Exchange
TEI In-Front Method
CSDD CHANGES
Section 1 : Modifications of existing Spec 2000 data elements
Section 2 : Modifications of existing non Spec 2000 data elements
Section 3 : New data elements
CHAPTER 11
Reliability Data Collection/Exchange
Overview
Purpose
General Use of Reliability Data
Aircraft Reliability Data
Standardized Record Format
Overview of Reliability Data Exchange Between Parties
Glossary of Terms
Section 1 - Component Reliability Data Collection/Exchange
Overview of the Component Removal Tracking Process
Standardized Record Formats contained in this Section
Removal/Findings Flow Chart
LRU Removal Record Structure
Purpose
Input contents and sequence
Shop Findings Record Structure
Purpose
Input contents and sequence
Piece Part Record Structure
Purpose
Input contents and sequence
Aircraft Hours and Landings Record Structure
Purpose
Input contents and sequence
Procedures
Update Change Codes
Create a LRU Removal Record
Delete a LRU Removal Record
Revise a LRU Removal Record
Multiple Occurrence of a TEI in LRU Removal
Data Set Groups
Create a Shop Findings Record
Delete a Shop Findings Record
Revise a Shop Findings Record
Multiple Occurrence of a TEI in Shop Findings
Data Set Groups
Create a Piece Part Record
Delete a Piece Part Record
Revise a Piece Part Record
Create a Aircraft Hours and Landings Record
Delete a Aircraft Hours and Landings Record
Revise a Aircraft Hours and Landings Record
Supporting Technical Information
Coding of Removal Type Code
Coding of Shop Findings Text
Data Audits
Reliability Data Audits
LRU Removal Record Audit
Shop Findings Record Audit
Piece Part Record Audit
Aircraft Hours and Landings Record Audit
TEI In-Front Method
CHAPTER 11 – RELIABILITY DATA COLLECTION/EXCHANGE
OVERVIEW
Currently, reliability data is being collected by virtually every aircraft operator as well as airframe, engine and component manufacturer in the world. Each day, individual companies collect and analyze thousands of pieces of vital information regarding aircraft components, operations and maintenance in an effort to further enhance aircraft reliability. This process, while successful within individual companies, is not properly structured for the collection and exchange of aircraft reliability data between companies.
To date a variety of collection methods, unique to individual companies, make any attempt to exchange data or measure reliability across the industry time-consuming, costly and subject to error. The development and implementation of standard record formats for collecting and exchanging aircraft reliability data will enable the industry to collect, measure and exchange this information in a consistent format – ultimately improving efficiency and reducing both costs and errors.
PURPOSE
The purpose of this chapter is to provide a set of standardized record formats for collecting and exchanging aircraft reliability data.
GENERAL USE OF RELIABILITY DATA
There are many reasons for collecting/exchanging and analyzing aircraft reliability data.
One reason is for understanding in-service airplane and component reliability performance and to quickly identify problems so that root cause analyses can be performed for problem identification and resolution. An outcome of this type of analysis may uncover an operator’s training, logistics and/or operations problems being the cause of an apparent reliability issues as well as being caused by the aircraft or components.
In-service reliability data is often used by manufacturers to compare design-phase predictions to the in-service actuals to assess the accuracy and validity of the analyses performed during design.
Other uses of in-service reliability data:
Determine if certain problem areas are unique to an operator or if others are experiencing the same problems.
Determine if the Mean Time Between Unscheduled Removals or No Fault Found rate one operator is experiencing is better or worse than the industry norm.
Determine which modification has a better payback by comparing removal and failure rates of operators incorporating various Service Bulletins/modifications.
Determine schedule interruption rates.
Determine aircraft flight hours, flight lengths, number of landing cycles as well as utilization rates.
Understand shop findings to determine if a removal confirms the reason for removal.
Determine failure mode rates.
AIRCRAFT RELIABILITY DATA
The data necessary to determine aircraft reliability can be broken into seven categories.
1) Aircraft data. This data contains aircraft configuration, operator and time-of-delivery component part numbers and serial numbers.
2) Aircraft general statistics data. This data contains flight hours, landings and revenue departures.
3) Aircraft event data. This data contains significant events such as mechanical dispatch delays, cancellations, substitutions, air & ground turnbacks, diversions, incidents, and structural difficulties.
4) Component removal data. This data contains the part number, serial number, manufacturer’s code and the reported defect pertaining to each part that was removed from the aircraft during a maintenance action.
5) Aircraft logbook data. This data contains information that was written up by pilots, cabin crews and maintenance crews concerning aircraft discrepancies. It also includes the corrective actions taken by maintenance personnel.
6) Scheduled maintenance/dock maintenance data. This data contains information concerning scheduled maintenance performed during inspection intervals as called out in the Maintenance Planning Documents.
7) Component Shop repair data. This data contains repair information pertaining to fixing internal problems related to a part that was removed or returned to the supplier or to an airline repair shop with a reported defect.
Standardized Record Format
The purpose of the Standardized Record Format (SRF) is to provide a standard record layout for transferring data organized by subject matter. These records will be organized in a computer readable data file to facilitate data transfer. The essential fields in each record contain enough information to support the loading of these data into a database.
It is important to remember the difference between the SRF data file and a database. The data file is for data collection and transfer from one computer (site) to another. The intent of a database is to create an official repository of collected data, forming a homogenous and seamless set of data structures. The SRF files do not themselves constitute a database but only serve to collect and transfer data.
The SRF is independent of the media used to contain the data files. Traditionally, customers and suppliers provided high volume data in individualized file formats on magnetic tape compatible with IBM mainframes. With desktop computing becoming more powerful, and the availability of good data compression software, files stored on Compact Discs (CD), are the popular choice for smaller data samples. In any case, (tape, diskette or CD) the media has to be mailed from one company to another, introducing the overhead and added expense of postal services.
Thus the SRF facilitates direct electronic exchange of the raw data and is a cost effective and efficient solution to optimize data exchange.
In summary, the SRF is a standardized collection of data, in a readable format, that allows the data to be easily shared by any company that wants to be involved in the data exchange process.
Overview of Reliability Data Exchange Between Parties
Although this chapter focuses only on reliability data collection/exchange, these figures have been included to show the larger picture of reliability data collection and exchange today. Figure 1 depicts the current reliability data flow within our industry. Currently reliability data is exchanged using several different means from paper copies to non-standard electronic formats. Figure 2 depicts the proposed method of reliability data flow using the standardized record formats.
[pic]
FIGURE 1
[pic]
FIGURE 2
| |
|Glossary of Terms |
AHLR = Aircraft Hours and Landings Record
Aircraft Operator = Airline Operator, Cargo Operator, Business Jet Operator, Regional Aircraft Operator, Helicopter Operator
ATA = Air Transport Association
CRDC = Component Reliability Data Collection
IATA = International Air Transport Association
ICAO = International Civil Aviation Organization
LRR = LRU Removal Report
LRU = Line Replaceable Unit (Component)
MTBF = Mean Time Between Failure
MTBUR = Mean Time Between Unscheduled Removal
PPR = Piece Part Report
SFR = Shop Finding Report
SRU = Shop Replaceable Unit
SECTION 1
COMPONENT RELIABILITY DATA COLLECTION/EXCHANGE
The Component Reliability Data Collection/Exchange section defines the standardized record formats necessary for collecting and exchanging aircraft component reliability data. Contained in this section are the aircraft general statistics data (hours and landings), component removal data and shop repair data including shop replaced or reworked piece parts.
Overview of the Component Removal Tracking Process
The component removal tracking process can be summarized by the following diagram :
[pic]
FIGURE 3
For example, an aircraft event (e.g. a pilot report) may cause an LRU to be removed from the aircraft. For each LRU removed, an LRU Removal Record is produced. This LRU could then be sent to the shop for repair, and in that case at least one Shop Finding Record is produced.
Note : The repair can generate several reports. This would be the case where the LRU is sent to the Airline shop. The test localizes a failed SRU which is sent to the original equipment manufacturer workshop for repair. In this example the airline shop may produce one Shop Finding Record and the original equipment manufacturer will produce a second Shop Finding Record related to the SRU. The repair of the SRU may in turn generate Piece Part Records (from 0 to n). There will be one Piece Part Record per replaced or reworked part.
Standardized Record Formats Contained in this Section
The component or Line Replaceable Unit (LRU) REMOVAL RECORD. This Standardized Record Format (SRF) is for collecting LRU removal data identified by part number, serial number and Commercial And Government Entity (CAGE) code as well as the aircraft from which it was removed and the details surrounding why the LRU needed to be removed. It is to be completed by an aircraft operator or third party repair facility or whomever is removing the defective or high time component.
The SHOP FINDING RECORD. This SRF is for collecting and exchanging LRU shop repair/teardown findings. It is to be completed by an aircraft operator’s repair shop, third party repair facility or original equipment manufacturer for the purpose of detailing the findings associated with an LRU that enters a shop.
Key fields will link the LRU Removal Record to the Shop Finding Record.
The PIECE PART RECORD. This SRF is for collecting defective or suspect Shop Replaceable Units (SRU’s) and other piece parts associated with the shop received LRU. It is to be completed by an aircraft operator’s repair shop, third party repair facility or original equipment manufacturer for the purpose of detailing the findings associated with an LRU that enters a shop.
One field will link the Shop Findings Record to the Piece Part Record.
The AIRCRAFT HOURS AND LANDINGS RECORD. This SRF is for detailing the total flight hours and total cycles of an operator’s fleet. It is for the purpose of calculating reliability measures such as Mean Time Between Unscheduled Removals (MTBUR), Mean Time Between Failure (MTBF), etc. It is to be completed by an aircraft operator using one record per aircraft.
Later in this section the data terms and formats for the LRU Removal Record, Shop Finding Record, Piece Part Record, and Aircraft Hours and Landings Record will be detailed including the definition of each field and its length.
LRU Removal Record
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|RECORD MANAGEMENT | | | | | | | | | | | |
| |RECORD |REC_CODE |Record Type Code |RTC |MM00281 |Mandatory | |N |2 |2 |Always "33" for LRU Removal |
| |IDENTIFICATION | | | | | | | | | |Record |
| |RECORD STATUS |REC_STAT |Change Code |CHG |MM00047 |Mandatory | |AN |1 |1 |N=new ; D=delete ; T=total |
| | | | | | | | | | | |replacement |
|REPORTING | | | | | | | | | | | |
|ORGANIZATION | | | | | | | | | | | |
| |REPORTING |RPT_ORG_CODE |Supplier Code |SPL |MM00354 |Mandatory | |AN |5 |5 | Use ZZZZZ if no CAGE/NSCM/FSCM|
| |ORGANIZATION CODE | | | | | | | | | |Code exists. |
| |REPORTING |RPT_ORG_NAME |Reporting Organization |RON |MM 00x xx |Conditional | |AN |1 |55 |New data element. Required if |
| |ORGANIZATION NAME | |Name | | | | | | | |the reporting organization has |
| | | | | | | | | | | |no cage code. |
| |OPERATOR CODE |OPER_CODE |Operator Code |OPR |MM00209 |Mandatory |YES |AN |3 |5 |Outstanding issue:Business Rule|
| | | | | | | | | | | |should support ICAO |
| | | | | | | | | | | |3-digit airline designator for |
| | | | | | | | | | | |reliability applications.Use |
| | | | | | | | | | | |ZZZZZ if no ICAO code exists. |
| |OPERATOR NAME |OPER_NAME |Company Name |WHO |MM00052 |Conditional | |AN |1 |55 |Add to spec, represents the |
| | | | | | | | | | | |name of the operator in |
| | | | | | | | | | | |reliability applications. |
| | | | | | | | | | | |Required if the operator of |
| | | | | | | | | | | |the aircraft has no operator |
| | | | | | | | | | | |code. |
|FLEET | | | | | | | | | | | |
| |AIRCRAFT MODEL |AC_MDL_NO |Aircraft_Model_Code |AMC |DM00032 MM |Mandatory |YES |AN |1 |20 |MM will need to add this data |
| | | | | |00x xx | | | | | |element |
| |AIRCRAFT SERIES |AC_SERIES_NO | | | | | | | | | |
| |AIRCRAFT ENGINE TYPE|AC_ENGINE_TYPE |Model of Applicability |MOA |MM00193 |Conditional | |AN |4 |4 | |
| | | |Code | | | | | | | | |
|ENGINE | | | | | | | | | | | |
| |ENGINE POSITION CODE|ENG_POSITION_CODE |Engine Position Code |EPC |MM 00x xx |Conditional | |AN |1 |1 |New Data Element. |
LRU Removal Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|AIRCRAFT ID | | | | | | | | | | | |
| |AIRCRAFT |AC_MFG_SER_NO |Aircraft Identification |AIN |MM00012 |Mandatory |YES |AN |1 |6 |Code ZZZZZ if submitting either|
| |MANUFACTURER SERIAL | |Number | | | | | | | |reg number or internal |
| |NUMBER | | | | | | | | | |identifier when MSN not sent |
| |AIRCRAFT |AC_REG__NO |Aircraft Registration |REG |MM 00x xx |Conditional | |AN |1 |8 |New Data Element Required |
| |REGISTRATION NUMBER | |Number | | | | | | | | |
| |OPERATOR AIRCRAFT |AC_ID_NO |Operator Aircraft |OIN |MM 00x xx |Conditional | |AN |1 |10 |New Data Element Required |
| |INTERNAL IDENTIFIER | |Internal Identifier | | | | | | | | |
|EVENT DETAILS | | | | | | | | | | | |
| |REMOVAL REASON TEXT |REMV_REASON_TEXT |Removal Reason Text |RMT |MM 00x xx |Mandatory | |AN |1 |1000 |New Data Element Required |
| |MAINTENANCE ACTION |MAINT_ACTION_TEXT |Maintenance Action Text |MNT |MM 00x xx |Conditional | |AN |1 |1000 |New Data Element Required |
| |TEXT | | | | | | | | | | |
| |AIRCRAFT MESSAGE |AC_MSG_TEXT |Aircraft Message Text |AMT |MM 00x xx |Conditional | |AN |1 |1000 |New Data Element Required |
| |TEXT | | | | | | | | | | |
| |AIRCRAFT MESSAGE |AC_MSG_CODE |Fault Code |FLT |TE00226 MM |Conditional | |AN |8 |8 |Needs TEI and Structure info. |
| |CODE | | | |00x xx | | | | | | |
| |REMOVAL DATE |REMV_DATE |Part Removal Date |RED |MM00234 |Mandatory |YES |N |6 |6 |DDMMYY |
| |STATION CODE |STATION_CODE |Removal Station Code |RST |MM00286 |Conditional | |AN |3 |3 |ATA CODES |
| |OPERATOR EVENT |OPER_EVENT_ID |Operator Event |OEI |MM 00x xx |Conditional | |AN |1 |20 |New Data Element Required |
| |IDENTIFIER | |Identifier | | | | | | | | |
LRU Removal Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|REMOVED LRU | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
| | | | | | | | | | | |Code for Removed LRU and use |
| | | | | | | | | | | |existing data elements. |
| | | | | | | | | | | |Coded "RLS" |
| |REMOVED MANUFACTURER|REMV_MANUF_PART_NO |Part Number |PNR |MM00228 |Mandatory |YES |AN |1 |15 |Code ZZZZZ if submitting |
| |PART NUMBER | | | | | | | | | |airline stock number (operator |
| | | | | | | | | | | |P/N)when PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |REMOVED OPERATOR |REMV_OPER_PART_NO |Airline Stock Number |ASN |MM00017 |Conditional | |AN |1 |11 | |
| |PART NUMBER | | | | | | | | | | |
| |REMOVED MANUFACTURER|REMV_MANUF_SER_NO |Part Serial Number |SER |MM00235 |Mandatory |YES |AN |1 |15 |Code ZZZZZ if submitting unique|
| |SERIAL NUMBER | | | | | | | | | |component identification number|
| | | | | | | | | | | |(operator S/N)when SER not |
| | | | | | | | | | | |sent. |
| |REMOVED OPERATOR |REMV_OPER_SER_NO |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 |Remove Application Area Remarks|
| |SERIAL NUMBER | |Identification Number | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 |Used if Operator assigned the |
| | | | | | | | | | | |UCN. |
| |REMOVED PART |REMV_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Mandatory |YES |AN |5 |5 |Essential to control data base |
| |MANUFACTURER CODE | | | | | | | | | |access |
| |REMOVAL TYPE CODE |REMV_TYPE_CODE |Removal Type Code |TYC |MM 00x xx |Mandatory | |AN |1 |1 |New Data Element Required |
| | | | | | | | | | | |U=Uncheduled,S=Scheduled,O=othe|
| | | | | | | | | | | |r |
| |REMOVAL TYPE TEXT |REMV_TYPE_TEXT |Reason for Removal |RET |MM00274 |Conditional | |AN |1 |64 |Modify definition to include |
| | | |Clarification Text | | | | | | | |CRDC definition for reliability|
| | | | | | | | | | | |applications. |
LRU Removal Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|NHA OF THE REMOVED | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
|LRU | | | | | | | | | | |Code for Next Higher Assembly |
| | | | | | | | | | | |of the Removed LRU and use |
| | | | | | | | | | | |existing data elements. Coded |
| | | | | | | | | | | |"NHS". |
| |NHA MANUFACTURER |NHA_MANUF_PART_NO |Part Number |PNR |MM00228 |Conditional | |AN |1 |15 |ie. ENGINE, APU,etc. Code |
| |PART NUMBER | | | | | | | | | |ZZZZZ if submitting airline |
| | | | | | | | | | | |stock number (operator P/N)when|
| | | | | | | | | | | |PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |NHA OPERATOR PART |NHA_OPER_PART_NO |Airline Stock Number |ASN |MM00017 |Conditional | |AN |1 |11 | |
| |NUMBER | | | | | | | | | | |
| |NHA MANUFACTURER |NHA_MANUF_SER_NO |Part Serial Number |SER |MM00235 |Conditional | |AN |1 |15 |ie. ENGINE, APU, etc. Code |
| |SERIAL NUMBER | | | | | | | | | |ZZZZZ if submitting unique |
| | | | | | | | | | | |component identification number|
| | | | | | | | | | | |(operator S/N)when SER not |
| | | | | | | | | | | |sent. |
| |NHA OPERATOR SERIAL |NHA_OPER_SER_NO |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 | |
| |NUMBER | |Identification Number | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 |Used if Operator assigned the |
| | | | | | | | | | | |UCN. |
| |NHA PART |NHA_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |MANUFACTURER CODE | | | | | | | | | | |
| |NHA PART NAME |NHA_PART_NAME |Additional Descriptive |ADT |MM00005 |Conditional | |AN |2 |260 | |
| | | |Text | | | | | | | | |
| |PART POSITION |PART_POSITION_CODE |Component Position Code |CPI |MM00053 |Conditional | |AN |1 |5 | |
| |ATA NUMBER |ATA_NO |Catalog Sequence Number |CSN |MM00043 |Conditional | |AN | |13 |Modify business rules to |
| | | | | | | | | | | |include the reliability file, |
| | | | | | | | | | | |not just the V file. |
LRU Removal Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|INSTALLED LRU | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
| | | | | | | | | | | |Code for Installed LRU and use |
| | | | | | | | | | | |existing data elements. |
| | | | | | | | | | | |Coded "ILS". |
| |INSTALLED |INST_MANUF_PART_NO |Part Number |PNR |MM00228 |Conditional | |AN |1 |15 |Code ZZZZZ if submitting |
| |MANUFACTURER PART | | | | | | | | | |airline stock number (operator |
| |NUMBER | | | | | | | | | |P/N)when PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |INSTALLED OPERATOR |INST_OPER_PART_NO |Airline Stock Number |ASN |MM00017 |Conditional | |AN |1 |11 | |
| |PART NUMBER | | | | | | | | | | |
| |INSTALLED |INST_MANUF_SER_NO |Part Serial Number |SER |MM00235 |Mandatory | |AN |1 |15 |Code ZZZZZ if submitting unique|
| |MANUFACTURER SERIAL | | | | | | | | | |component identification number|
| |NUMBER | | | | | | | | | |(operator S/N)when SER not |
| | | | | | | | | | | |sent. |
| |INSTALLED OPERATOR |INST_OPER_SER_NO |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 |Remove Application Area Remarks|
| |SERIAL NUMBER | |Identification Number | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 |Used if Operator assigned the |
| | | | | | | | | | | |UCN. |
| |INSTALLED PART |INST_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |MANUFACTURER CODE | | | | | | | | | | |
LRU Removal Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|LRU TIME AND CYCLES | | |Total Time Text |TTM |MM00390 |Conditional | |AN |5 |15 |Change definition of Data Set |
| | | | | | | | | | | |Group to include null values in|
| | | | | | | | | | | |LRU Removal applications. |
| | | |Operating Time | |MM00208 | | |N |1 |6 |Need to change definition of |
| | | | | | | | | | | |Operating Time to represent |
| | | | | | | | | | | |flight hours. |
| | | |Operating Cycle Count | |MM00207 | | |N |1 |6 |In Landings |
| | | |Time/Cycle Reference | |MM00374 | | |A |1 |1 | |
| | | |Code | | | | | | | | |
| |TSN-TIME SINCE NEW |TSN_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| | | | | | | | | | | |"N" |
| |CSN-CYCLES SINCE NEW|CSN_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |TSI-TIME SINCE |TSI_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| |INSTALLATION | | | | | | | | | |"I". New code |
| |CSI-CYCLES SINCE |CSI_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |INSTALLATION | | | | | | | | | | |
| |TSR-TIME SINCE |TSR_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| |REPAIR | | | | | | | | | |"R" |
| |CSR-CYCLES SINCE |CSR_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |REPAIR | | | | | | | | | | |
| |TSC-TIME SINCE CHECK|TSC_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| | | | | | | | | | | |"C". New code |
| |CSC-CYCLES SINCE |CSC_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |CHECK | | | | | | | | | | |
| |TSV-TIME SINCE VISIT|TSV_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| | | | | | | | | | | |"V". New code |
| |CSV-CYCLES SINCE |CSV_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |VISIT | | | | | | | | | | |
| |TSO-TIME SINCE |TSO_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| |OVERHAUL | | | | | | | | | |"O" |
| |CSO-CYCLES SINCE |CSO_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |OVERHAUL | | | | | | | | | | |
LRU Removal Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
| |AIRCRAFT CUMULATIVE |AC_CUM_TOT_HRS |Aircraft Cumulative |CTH |MM 00x xx |Conditional | |N |1 |9 |New Data Element Required. |
| |TOTAL FLIGHT HOURS | |Total Flight Hours | | | | | | | | |
| |AIRCRAFT CUMULATIVE |AC_CUM_TOT_LDGS |Aircraft Cumulative |CTC |MM 00x xx |Conditional | |N |1 |9 |New Data Element Required. |
| |TOTAL CYCLES | |Total Cycles | | | | | | | | |
|MISC | | | | | | | | | | | |
| |REMOVAL TRACKING |REMV_TRACK_ID |Removal Tracking |RTI |MM 00x xx |Conditional | |AN |1 |20 |New Data Element Required |
| |IDENTIFIER | |Identifier | | | | | | | |(Removal Identifier) |
Shop Findings Record
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|RECORD MANAGEMENT | | | | | | | | | | | |
| |RECORD |REC_CODE |Record Type Code |RTC |MM00281 |Mandatory | |N |2 |2 |Always "34" for Shop Findings |
| |IDENTIFICATION | | | | | | | | | |Record |
| |RECORD STATUS |REC_STAT |Change Code |CHG |MM00047 |Mandatory | |AN |1 |1 |N=new ; D=delete ; T=total |
| | | | | | | | | | | |replacement |
|REPORTING SOURCE | | | | | | | | | | | |
| |REPORTING |RPT_ORG_CODE |Supplier Code |SPL |MM00354 |Mandatory | |AN |5 |5 | Use ZZZZZ if no CAGE/NSCM/FSCM|
| |ORGANIZATION CODE | | | | | | | | | |Code exists. |
| |REPORTING |RPT_ORG_NAME |Reporting Organization |RON |MM 00x xx |Conditional | |AN |1 |55 |New data element. |
| |ORGANIZATION NAME | |Name | | | | | | | |Required if the reporting |
| | | | | | | | | | | |organization has no cage code. |
|SHOP DETAILS | | | | | | | | | | | |
| |SHOP LOCATION TEXT |SHOP_LOC_TEXT |Repair Location Code |RLC |MM00293 |Conditional | |AN |1 |5 | |
| |REMOVAL TRACKING |RMV_TRACK_ID |Removal Tracking |RTI |MM 00x xx |Conditional | |AN |1 |20 |New Data Element Required |
| |IDENTIFIER | |Identifier | | | | | | | |(Removal Identifier) |
| | | | | | | | | | | |example : P.O. |
| |SHOP FINDING RECORD |SHOP_RCRD_ID |Shop Finding Record |SFI |MM 00x xx |Mandatory | |AN |1 |20 |New Data Element Required |
| |IDENTIFIER | |Identifier | | | | | | | | |
| |RELATED SHOP FINDING|RLTD_SHOP_RCRD_ID |Related Shop Finding |RSI |MM 00x xx |Conditional | |AN |1 |20 |New Data Element Required |
| |RECORD IDENTIFIER | |Record Identifier | | | | | | | | |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|UNIT REMOVAL | | | | | | | | | | | |
|INFORMATION (Also on | | | | | | | | | | | |
|LRU Removal Report) | | | | | | | | | | | |
| |OPERATOR CODE |OPER_CODE |Operator Code |OPR |MM00209 |Mandatory |YES |AN |3 |5 |Outstanding issue:Business Rule|
| | | | | | | | | | | |should support ICAO 3-digit |
| | | | | | | | | | | |airline designator for |
| | | | | | | | | | | |reliability applications. |
| | | | | | | | | | | |Use ZZZZZ if no ICAO code |
| | | | | | | | | | | |exists. |
| |OPERATOR NAME |OPER_NAME |Company Name |WHO |MM00052 |Conditional | |AN |1 |55 |Add to spec, represents the |
| | | | | | | | | | | |name of the operator in |
| | | | | | | | | | | |reliability applications. |
| | | | | | | | | | | |Required if the operator of |
| | | | | | | | | | | |the aircraft has no operator |
| | | | | | | | | | | |code. |
| |AIRCRAFT MODEL |AC_MDL_NO |Aircraft_Model_Code |AMC |DM00032 MM |Mandatory |YES |AN |1 |20 |MM will need to add this data |
| | | | | |00x xx | | | | | |element. |
| | | | | | | | | | | |Essential only if unit removed |
| | | | | | | | | | | |from an aircraft |
| |AIRCRAFT |AC_MFG_SER_NO |Aircraft Identification |AIN |MM00012 |Mandatory |YES |AN |1 |6 |Code ZZZZZ if submitting either|
| |MANUFACTURER SERIAL | |Number | | | | | | | |reg number or internal |
| |NUMBER | | | | | | | | | |identifier when MSN not sent. |
| | | | | | | | | | | |Essential only if unit removed |
| | | | | | | | | | | |from an aircraft |
| |AIRCRAFT |AC_REG_NO |Aircraft Registration |REG |MM 00x xx |Conditional |YES |AN |1 |8 |New Data Element Required |
| |REGISTRATION NUMBER | |Number | | | | | | | | |
| |OPERATOR AIRCRAFT |AC_ID_NO |Operator Aircraft |OIN |MM 00x xx |Conditional | |AN |1 |10 |New Data Element Required |
| |INTERNAL IDENTIFIER | |Internal Identifier | | | | | | | | |
| |REMOVAL DATE |REMV_DATE |Part Removal Date |RED |MM00234 |Mandatory |YES |AN |6 |6 |DDMMYY |
| | | | | | | | | | | |If not available, use received |
| | | | | | | | | | | |date |
| |REMOVAL REASON TEXT |REMV_REASON_TEXT |Removal Reason Text |RMT |MM 00x xx |Conditional | |AN |1 |1000 |New Data Element Required |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|REMOVED LRU | | |Segment Identifier Code |SEG |MM00316 | | | | | |Use the same new Segment |
| | | | | | | | | | | |Identifier Code as in the LRU |
| | | | | | | | | | | |Removal record. |
| | | | | | | | | | | |Coded "RLS" |
| |REMOVED MANUFACTURER|REMV_MANUF_PART_NO |Part Number |PNR |MM00228 |Mandatory |YES |AN |1 |15 |Code ZZZZZ if submitting |
| |PART NUMBER | | | | | | | | | |airline stock number (operator |
| | | | | | | | | | | |P/N)when PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | | |16 |32 | |
| |REMOVED OPERATOR |REMV_OPER_PART_NO |Airline Stock Number |ASN |MM00017 |Conditional | |AN |1 |11 | |
| |PART NUMBER | | | | | | | | | | |
| |REMOVED MANUFACTURER|REMV_MANUF_SER_NO |Part Serial Number |SER |MM00235 |Mandatory |YES |AN |1 |15 |Code ZZZZZ if submitting unique|
| |SERIAL NUMBER | | | | | | | | | |component identification number|
| | | | | | | | | | | |(operator S/N)when SER not |
| | | | | | | | | | | |sent. |
| |REMOVED OPERATOR |REMV_OPER_SER_NO |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 |Remove Application Area Remarks|
| |SERIAL NUMBER | |Identification Number | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 |Used if Operator assigned the |
| | | | | | | | | | | |UCN |
| |REMOVED PART |REMV_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Mandatory |YES |AN |5 |5 |Essential to control data base |
| |MANUFACTURER CODE | | | | | | | | | |access |
| |REMOVAL TYPE CODE |REMV_TYPE_CODE |Removal Type Code |TYC |MM 00x xx |Mandatory | |AN |1 |1 |New Data Element Required |
| | | | | | | | | | | |U=Uncheduled,S=Scheduled,O=othe|
| | | | | | | | | | | |r |
| |REMOVAL TYPE TEXT |REMV_TYPE_TEXT |Reason for Removal |RET |MM00274 |Conditional | |AN |1 |64 |Modify definition to include |
| | | |Clarification Text | | | | | | | |CRDC definition for reliability|
| | | | | | | | | | | |applications. |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|LRU TIME AND CYCLES | | |Total Time Text |TTM |MM00390 |Conditional | |AN |5 |15 |Change definition of Data Set |
| | | | | | | | | | | |Group to include null values in|
| | | | | | | | | | | |LRU Removal applications. |
| | | |Operating Time | |MM00208 | | |N |1 |6 |Need to change definition of |
| | | | | | | | | | | |Operating Time to represent |
| | | | | | | | | | | |flight hours. |
| | | |Operating Cycle Count | |MM00207 | | |N |1 |6 |In Landings |
| | | |Time/Cycle Reference | |MM00374 | | |A |1 |1 | |
| | | |Code | | | | | | | | |
| |TSN-TIME SINCE NEW |TSN_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| | | | | | | | | | | |"N" |
| |CSN-CYCLES SINCE NEW|CSN_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |TSI-TIME SINCE |TSI_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| |INSTALLATION | | | | | | | | | |"I". New code |
| |CSI-CYCLES SINCE |CSI_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |INSTALLATION | | | | | | | | | | |
| |TSR-TIME SINCE |TSR_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| |REPAIR | | | | | | | | | |"R" |
| |CSR-CYCLES SINCE |CSR_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |REPAIR | | | | | | | | | | |
| |TSC-TIME SINCE CHECK|TSC_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| | | | | | | | | | | |"C". New code |
| |CSC-CYCLES SINCE |CSC_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |CHECK | | | | | | | | | | |
| |TSV-TIME SINCE VISIT|TSV_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| | | | | | | | | | | |"V". New code |
| |CSV-CYCLES SINCE |CSV_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |VISIT | | | | | | | | | | |
| |TSO-TIME SINCE |TSO_HRS |Operating Time | |MM00208 |Conditional | |N | | |Time/Cycle Reference Code coded|
| |OVERHAUL | | | | | | | | | |"O" |
| |CSO-CYCLES SINCE |CSO_LDGS |Operating Cycle Count | |MM00207 |Conditional | |N | | | |
| |OVERHAUL | | | | | | | | | | |
| |RECEIVED DATE |RCVD_DATE |Material Receipt Date |MRD |MM00185 |Conditional | |AN |6 |6 |MMDDYY |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|UNIT RECEIVED DETAILS| | |Segment Identifier Code |SEG |MM00316 |Conditional | | | | |Define a new Segment Identifier|
| | | | | | | | | | | |Code for unit received details.|
| | | | | | | | | | | | |
| | | | | | | | | | | |Coded "RCS" |
| |RECEIVED |RECV_MANUF_PART_NO |Part Number |PNR |MM00228 |Mandatory | |AN |1 |15 |Code ZZZZZ if submitting |
| |MANUFACTURER PART | | | | | | | | | |airline stock number (operator |
| |NUMBER | | | | | | | | | |P/N)when PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |RECEIVED OPERATOR |RECV_OPER_PART_NO |Airline Stock Number |ASN |MM00017 |Conditional | |AN |1 |11 | |
| |PART NUMBER | | | | | | | | | | |
| |MANUFACTURER PART |MANUF_PART_DESC |Additional Descriptive |ADT |MM00005 |Conditional | |AN |2 |260 | |
| |DESCRIPTION | |Text | | | | | | | | |
| |RECEIVED |RECV_MANUF_SER_NO |Part Serial Number |SER |MM00235 |Mandatory | |AN |1 |15 |Code ZZZZZ if submitting unique|
| |MANUFACTURER SERIAL | | | | | | | | | |component identification number|
| |NUMBER | | | | | | | | | |(operator S/N)when SER not |
| | | | | | | | | | | |sent. |
| |RECEIVED OPERATOR |RECV_OPER_SER_NO |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 |Remove Application Area Remarks|
| |SERIAL NUMBER | |Identification Number | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 |Used if Operator assigned the |
| | | | | | | | | | | |UCN |
| |RECEIVED PART |RECV_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |MANUFACTURER CODE | | | | | | | | | | |
| |INCOMING |INC_MOD_LVL |Configuration/ |CMS |MM00055 |Conditional | |AN |1 |26 | |
| |MODIFICATION LEVEL | |Modification Status | | | | | | | | |
| | | |Number | | | | | | | | |
| |INCOMING INSPECTION |INC_INSP_TEXT |Incoming Inspection / |INT |MM 00x xx |Conditional | |AN |1 |1000 |New data element required |
| |TEXT | |Shop action Text | | | | | | | | |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|SHOP FINDINGS | | |Shop Finding Text |FIT |MM 00x xx |Mandatory | |AN |12 |23 |New data set group (Shop |
| | | | | | | | | | | |Findings Text -FIT) with 6 |
| | | | | | | | | | | |occurences of Inspection |
| | | | | | | | | | | |Findings Code. |
| | | | | | | | | | | |Examples: |
| | | | | | | | | | | |/FIT FT - CR - - -/ |
| | | | | | | | | | | |/FIT NT - - - - -/ |
| | | |Inspection Findings Code|IFC |MM00140 | | |AN |1 |3 |Need to add new codes to IFC to|
| | | | | | | | | | | |cover all 6 of these |
| | | | | | | | | | | |possibilities. |
| |FAILURE/ FAULT FOUND|FLR_FND_IN |Inspection Findings Code|IFC |MM00140 |Mandatory | |AN | | |Coded "FT" or "NT" |
| |FAILURE/ FAULT |FLR_INDC_IN |Inspection Findings Code|IFC |MM00140 |Mandatory | |AN | | |Coded "IN" or "NI" or "-" |
| |INDUCED | | | | | | | | | | |
| |FAILURE/ FAULT |FLR_CNFRM_IN |Inspection Findings Code|IFC |MM00140 |Mandatory | |AN | | |Coded "CR" or "NC" or "-" |
| |CONFIRMS REASON FOR | | | | | | | | | | |
| |REMOVAL | | | | | | | | | | |
| |FAILURE/ FAULT |AC_MSG_CNFRM_IN |Inspection Findings Code|IFC |MM00140 |Mandatory | |AN | | |Coded "CM" or "NM" or "-" |
| |CONFIRMS AIRCRAFT | | | | | | | | | | |
| |MESSAGE | | | | | | | | | | |
| |FAILURE/ FAULT |AC_BITE_CNFRM_IN |Inspection Findings Code|IFC |MM00140 |Mandatory | |AN | | |Coded "CB" or "NB" or "-" |
| |CONFIRMS AIRCRAFT | | | | | | | | | | |
| |PART BITE MESSAGE | | | | | | | | | | |
| |HARDWARE/ SOFTWARE |FLR_TYPE_IN |Inspection Findings Code|IFC |MM00140 |Mandatory | |AN | | |Coded "HW" or "SW" or "-" |
| |FAILURE | | | | | | | | | | |
| |SHOP FINDINGS CODE |SHOP_FNDG_CODE |Shop Findings Code |SFC |MM 00x xx |Conditional | |AN |1 |10 |New data element required. Need|
| | | | | | | | | | | |to change CRDC name |
| |SHIPPED DATE |SHIP_DATE |Shipped Date |SHP |MM 00x xx |Conditional | |AN |6 |6 |New data element required : 2 |
| | | | | | | | | | | |digit year. |
| | | | | | | | | | | |DDMMYY |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|UNIT SHIPPING DETAILS| | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
| | | | | | | | | | | |Code for unit shipping details.|
| | | | | | | | | | | | |
| | | | | | | | | | | |Coded "SUS". |
| |SHIPPED MANUFACTURER|SHIP_MANUF_PART_NO |Part Number |PNR |MM00228 |Mandatory | |AN |1 |15 |Code ZZZZZ if submitting |
| |PART NUMBER | | | | | | | | | |airline stock number (operator |
| | | | | | | | | | | |P/N)when PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |SHIPPED OPERATOR |SHIP_OPER_PART_NO |Airline Stock Number |ASN |MM00017 |Conditional | |AN |1 |11 | |
| |PART NUMBER | | | | | | | | | | |
| |MANUFACTURER PART |MANUF_PART_DESC |Additional Descriptive |ADT |MM00005 |Conditional | |AN |2 |260 | |
| |DESCRIPTION | |Text | | | | | | | | |
| |SHIPPED MANUFACTURER|SHIP_MANUF_SER_NO |Part Serial Number |SER |MM00235 |Mandatory | |AN |1 |15 |Code ZZZZZ if submitting unique|
| |SERIAL NUMBER | | | | | | | | | |component identification number|
| | | | | | | | | | | |(operator S/N)when SER not |
| | | | | | | | | | | |sent. |
| |SHIPPED OPERATOR |SHIP_OPER_SER_NO |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 |Remove Application Area Remarks|
| |SERIAL NUMBER | |Identification Number | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 |Used if Operator assigned the |
| | | | | | | | | | | |UCN |
| |SHIPPED PART |SHIP_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |MANUFACTURER CODE | | | | | | | | | | |
| |SHIPPED MODIFICATION|SHIP_MOD_LVL |Configuration/ |CMS |MM00055 |Conditional | |AN |1 |26 | |
| |LEVEL | |Modification Status | | | | | | | | |
| | | |Number | | | | | | | | |
Shop Findings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED|FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS|DATA TYPE |min length|Max length|COMMENTS |
|SHOP ACTION | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
| | | | | | | | | | | |Code for shop action details. |
| | | | | | | | | | | |Coded "SAS". |
| |SHOP ACTION TEXT |SHOP_ACT_TEXT |Incoming Inspection / |INT |MM 00x xx |Mandatory | |AN |1 |1000 |use same new element as for |
| | | |Shop action Text | | | | | | | |incoming inspection text |
| |MOD(S) INCORPORATED |MOD_INC_TEXT |Manufacturer's Authority|MAT |MM00179 |Conditional | |AN |1 |40 |Change definition to include |
| |(THIS VISIT) TEXT | |Text | | | | | | | |mod levels in reliability |
| | | | | | | | | | | |applications. |
| |SHOP ACTION CODE |SHOP_ACT_CODE |Repair Process Code |RPC |MM00295 |Conditional | |AN |1 |5 |CRDC to confirm addition of |
| | | | | | | | | | | |this new data requirement. |
Piece Part Record
|INFORMATION LEVEL |DATA TO BE COLLECTED |FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY |DATA TYPE |min length|Max length|COMMENT |
| | | | | | | |FIELDS | | | | |
|RECORD MANAGEMENT | | | | | | | | | | | |
| |RECORD IDENTIFICATION |REC_CODE |Record Type Code |RTC |MM00281 |Mandatory | |N |2 |2 |Always "35" for Piece Part |
| | | | | | | | | | | |Record |
| |RECORD STATUS |REC_STAT |Change Code |CHG |MM00047 |Mandatory | |AN |1 |1 |N=new ; D=delete ; T=total |
| | | | | | | | | | | |replacement |
|REPORTING SOURCE | | | | | | | | | | | |
| |REPORTING ORGANIZATION |RPT_ORG_CODE |Supplier Code |SPL |MM00354 |Mandatory | |AN |5 |5 | Use ZZZZZ if no CAGE/NSCM/FSCM|
| |CODE | | | | | | | | | |Code exists. |
| |REPORTING ORGANIZATION |RPT_ORG_NAME |Reporting Organization |RON |MM 00x xx |Conditional | |AN |1 |55 |New data element. Required if |
| |NAME | |Name | | | | | | | |the reporting organization has |
| | | | | | | | | | | |no cage code. |
|SHOP DETAILS | | | | | | | | | | | |
| |REMOVAL TRACKING |REMV_TRACK_ID |Removal Tracking |RTI |MM 00x xx |Conditional | |AN |1 |20 |see LRU removal record. Example|
| |IDENTIFIER | |Identifier | | | | | | | |: P.O. |
| |SHOP FINDING RECORD |SHOP_RCRD_ID |Shop Finding Record |SFI |MM 00x xx |Mandatory | |AN |1 |20 |see shop finding record |
| |IDENTIFIER | |Identifier | | | | | | | | |
| |PIECE PART RECORD |PART_RCRD_ID |Piece Part Record |PPI |MM 00x xx |Mandatory | |AN |1 |20 |New Data Element Required |
| |IDENTIFIER | |Identifier | | | | | | | | |
| |RECEIVED DATE |RCVD_DATE |Material Receipt Date |MRD |MM00185 |Conditional | |AN |6 |6 |MMDDYY |
|WORKED PIECE PART | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
| | | | | | | | | | | |Code for worked piece part. |
| | | | | | | | | | | |Coded "WPS". |
| |PIECE PART VENDOR CODE |FAIL_PART_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |VENDOR PIECE PART NUMBER|FAIL_PART_NO |Part Number |PNR |MM00228 |Mandatory | |AN |1 |15 |Code ZZZZZ if submitting piece |
| | | | | | | | | | | |part description when PNR not |
| | | | | | | | | | | |sent. |
| | | |Overlength Part Number |OPN |MM00223 | | |AN |16 |32 | |
| |VENDOR PIECE PART |FAIL_PART_DESC |Additional Descriptive |ADT |MM00005 |Conditional | |AN |2 |260 | |
| |DESCRIPTION | |Text | | | | | | | | |
| |VENDOR PIECE PART SERIAL|FAIL_SER_NO |Part Serial Number |SER |MM00235 |Conditional | |AN |1 |15 | |
| |NUMBER | | | | | | | | | | |
Piece Part Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED |FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY |DATA TYPE |min length|Max length|COMMENT |
| | | | | | | |FIELDS | | | | |
| |PIECE PART REFERENCE |FAIL_REF_DESIG |Geographic and/or |GEL |TE00277 MM |Conditional | |AN |1 |30 |add "and/or electrical" to the |
| |DESIGNATOR SYMBOL | |Electrical Position | |00x xx | | | | | |name and definition after the |
| | | | | | | | | | | |word geographical |
| |PRIMARY PIECE PART |FAIL_IN |Primary Piece Part |PFC |MM 00x xx |Conditional | |A |1 |1 |New Data Element Required |
| |FAILURE INDICATOR | |Failure Indicator | | | | | | | |Y/N/D |
| |PIECE PART FAILURE |FAIL_DESC |Piece Part Failure |FDE |MM 00x xx |Mandatory | |AN |1 |1000 |New Data Element Required |
| |DESCRIPTION | |Description | | | | | | | | |
|NEXT HIGHER | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
|ASSEMBLY OF THE | | | | | | | | | | |Code for next higher assembly |
|WORKED PIECE PART | | | | | | | | | | |of worked piece part. |
| | | | | | | | | | | |Coded "NHS". |
| |FAILED PIECE PART NEXT |FAIL_NHA_PART_NO |Part Number |PNR |MM00228 |Conditional | |AN |1 |15 |Code ZZZZZ if submitting |
| |HIGHER ASSEMBLY PART | | | | | | | | | |airline stock number (operator |
| |NUMBER | | | | | | | | | |P/N)when PNR not sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |FAILED PIECE PART NEXT | |Airline Stock Number |ASN |MM00235 |Conditional | |AN |1 |11 | |
| |HIGHER ASSEMBLY OPERATOR| | | | | | | | | | |
| |PART NUMBER | | | | | | | | | | |
| |FAILED PIECE PART NEXT |FAIL_NHA_SER_NO |Part Serial Number |SER |MM00235 |Conditional | |AN |1 |15 |Code ZZZZZ if submitting unique|
| |HIGHER ASSEMBLY SERIAL | | | | | | | | | |component identification number|
| |NUMBER | | | | | | | | | |(operator S/N) when SER not |
| | | | | | | | | | | |sent. |
| |FAILED PIECE PART NEXT |FAIL_NHA_PART_NAME |Additional Descriptive |ADT |MM00005 |Conditional | |AN |2 |260 | |
| |HIGHER ASSEMBLY PART | |Text | | | | | | | | |
| |NAME | | | | | | | | | | |
| |FAILED PIECE PART NEXT | |Unique Component |UCN |MM00397 |Conditional | |AN |1 |15 | |
| |HIGHER ASSEMBLY OPERATOR| |Identification Number | | | | | | | | |
| |SERIAL NUMBER | | | | | | | | | | |
| | | |Supplier Code |SPL |MM00354 |Conditional | |AN |5 |5 | |
Piece Part Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED |FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY |DATA TYPE |min length|Max length|COMMENT |
| | | | | | | |FIELDS | | | | |
| |FAILED PIECE PART NEXT | |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |HIGHER ASSEMBLY PART | | | | | | | | | | |
| |MANUFACTURER CODE | | | | | | | | | | |
| |FAILED PIECE PART NEXT |FAIL_NHA_NHA_PART_NO |Failed Piece Part Next |NPN |MM 00x xx |Conditional | |AN |1 |30 |New Data Element Required. |
| |HIGHER ASSEMBLY NHA PART| |Higher Assembly NHA Part| | | | | | | | |
| |NUMBER | |Number | | | | | | | | |
|REPLACED PIECE | | |Segment Identifier Code |SEG |MM00316 | | | | | |Define a new Segment Identifier|
|PART | | | | | | | | | | |Code for replaced piece part. |
| | | | | | | | | | | |Coded "RPS". |
| |REPLACED PIECE PART |REPL_PART_MANUF_CODE |Manufacturer Code |MFR |MM00177 |Conditional | |AN |5 |5 | |
| |VENDOR CODE | | | | | | | | | | |
| |REPLACED VENDOR PIECE |REPL_PART_NO |Part Number |PNR |MM00228 |Conditional | |AN |1 |15 |Code ZZZZZ if submitting |
| |PART NUMBER | | | | | | | | | |Additional Descriptive Text |
| | | | | | | | | | | |(Piece part name)when PNR not |
| | | | | | | | | | | |sent. |
| | | |Overlength Part Number |OPN |MM00223 |Conditional | |AN |16 |32 | |
| |REPLACED VENDOR PIECE |REPL_PART_DESC |Additional Descriptive |ADT |MM00005 |Conditional | |AN |2 |260 | |
| |PART DESCRIPTION | |Text | | | | | | | | |
| |REPLACED VENDOR PIECE |REPL_SER_NO |Part Serial Number |SER |MM00235 |Conditional | |AN |1 |15 | |
| |PART SERIAL NUMBER | | | | | | | | | | |
Aircraft Hours and Landings Record
|INFORMATION LEVEL |DATA TO BE COLLECTED |FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS |DATA |min |Max |COMMENTS |
| | | | | | | | |TYPE |length |length | |
|RECORD MANAGEMENT | | | | | | | | | | | |
| |RECORD IDENTIFICATION |REC_CODE |Record Type Code |RTC |MM00281 |Mandatory | |N |2 |2 |Always "36" for Aircraft Hours |
| | | | | | | | | | | |and Landings Record |
| |RECORD STATUS |REC_STAT |Change Code |CHG |MM00047 |Mandatory | |AN |1 |1 |N=new ; D=delete ; T=total |
| | | | | | | | | | | |replacement |
|REPORTING | | | | | | | | | | | |
|ORGANIZATION | | | | | | | | | | | |
| |REPORTING ORGANIZATION CODE |RPT_ORG_CODE |Supplier Code |SPL |MM00354 |Mandatory | |AN |5 |5 | Use ZZZZZ if no CAGE/NSCM/FSCM |
| | | | | | | | | | | |Code exists. |
| |REPORTING ORGANIZATION NAME |RPT_ORG_NAME |Reporting Organization |RON |MM 00x xx |Conditional | |AN |1 |55 |New data element. |
| | | |Name | | | | | | | |Required if the reporting |
| | | | | | | | | | | |organization has no cage code. |
|OPERATOR | | | | | | | | | | | |
| |OPERATOR CODE |OPER_CODE |Operator Code |OPR |MM00209 |Mandatory | |AN |3 |5 |Outstanding issue:Business Rule |
| | | | | | | | | | | |should support ICAO 3-digit |
| | | | | | | | | | | |airline designator for |
| | | | | | | | | | | |reliability applications.Use |
| | | | | | | | | | | |ZZZZZ if no ICAO code exists. |
| |OPERATOR NAME |OPER_NAME |Company Name |WHO |MM00052 |Conditional | |AN |1 |55 |Add to spec, represents the name |
| | | | | | | | | | | |of the operator in reliability |
| | | | | | | | | | | |applications. |
| | | | | | | | | | | |Required if the operator of the|
| | | | | | | | | | | |aircraft has no operator code. |
|FLEET | | | | | | | | | | | |
| |AIRCRAFT MODEL |AC_MDL_NO |Aircraft_Model_Code |AMC |DM00032 MM |Mandatory | |AN |1 |20 |MM will need to add this data |
| | | | | |00x xx | | | | | |element |
| |AIRCRAFT SERIES |AC_SERIES_NO | | | | | | | | | |
Aircraft Hours and Landings Record (cont'd)
|INFORMATION LEVEL |DATA TO BE COLLECTED |FIELD |CSDD DATA ELEMENT NAME |TEI |CSDD KEY |Application |KEY FIELDS |DATA |min |Max |COMMENTS |
| | | | | | | | |TYPE |length |length | |
|AIRCRAFT ID | | | | | | | | | | | |
| |AIRCRAFT MANUFACTURER SERIAL|AC_MFG_SER_NO |Aircraft Identification|AIN |MM00012 |Mandatory | |AN |1 |6 |Code ZZZZZ if submitting either |
| |NUMBER | |Number | | | | | | | |reg number or internal identifier|
| | | | | | | | | | | |when MSN not sent |
| |AIRCRAFT REGISTRATION NUMBER|AC_REG__NO |Aircraft Registration |REG |MM 00x xx |Conditional | |AN |1 |8 |New Data Element Required |
| | | |Number | | | | | | | | |
| |OPERATOR AIRCRAFT INTERNAL |AC_ID_NO |Operator Aircraft |OIN |MM 00x xx |Conditional | |AN |1 |10 |New Data Element Required |
| |IDENTIFIER | |Internal Identifier | | | | | | | | |
|REPORTING PERIOD | | | | | | | | | | | |
| |REPORT MONTH |RPT_MONTH |Report period date |RDT |MM00305 |Mandatory | |N |6 |6 |Change definiton :remove the word|
| | | | | | | | | | | |consumption from the definition. |
| | | | | | | | | | | |MMYYYY |
|AIRCRAFT | | | | | | | | | | | |
|STATISTICS | | | | | | | | | | | |
| |AIRCRAFT MONTHLY TOTAL |AC_MONTH_TOT_HRS |Aircraft Monthly Total |MTH |MM 00x xx |Conditional | |N |1 |6 |New Data Element Required. |
| |FLIGHT HOURS | |Flight Hours | | | | | | | |Decimal allowed however no more |
| | | | | | | | | | | |than 2 digits |
| |AIRCRAFT MONTHLY TOTAL |AC_MONTH_TOT_LDGS |Aircraft Monthly Total |MTC |MM 00x xx |Conditional | |N |1 |6 |New Data Element Required. |
| |CYCLES | |Cycles | | | | | | | | |
| |AIRCRAFT CUMULATIVE TOTAL |AC_CUM_TOT_HRS |Aircraft Cumulative |CTH |MM 00x xx |Mandatory | |N |1 |9 |New Data Element Required. |
| |FLIGHT HOURS | |Total Flight Hours | | | | | | | | |
| |AIRCRAFT CUMULATIVE TOTAL |AC_CUM_TOT_LDGS |Aircraft Cumulative |CTC |MM 00x xx |Mandatory | |N |1 |9 |New Data Element Required. |
| |CYCLES | |Total Cycles | | | | | | | | |
Removal/Findings Flow Chart
The following flow chart is intended to illustrate the logic used to categorize components that have been removed from an aircraft and have undergone a shop investigation.
The Spec 2000 Reliability Working Group has noted that our industry has difficulty with the various nuances of the terms MTBUR and MTBF. This diagram was developed to define these terms using a flow diagram approach instead of using words. This flow chart is important when populating the Failure/Fault Found, Failure/Fault Induced, Failure/Fault Confirms Reason for Removal fields contained in the Shop Findings Record.
[pic]
Note : one category of removal has been voluntarily omitted : “ OTHER ” ( may be used for convenience, robbery, ....)
FIGURE 4
LRU REMOVAL RECORD STRUCTURE
PURPOSE
This Record is for collecting LRU removal data identified by part number, serial number and Commercial And Government Entity (CAGE) code as well as the aircraft from which it was removed and the details surrounding why the LRU needed to be removed. It is to be completed by an aircraft operator or third party repair facility or whomever is removing the defective or high time component.
INPUT CONTENTS AND SEQUENCE
An Lru Removal Record is including up to three types of Segment Identifier Codes (SEG). Only one occurrence of each type is allowed.
The removed LRU segment (RLS) is mandatory in all data transmission. The Next Higher Assembly segment (NHS) and Installed LRU segment (ILS) are optional.
1. Record Type Code (RTC) (/)
Always coded "33"
2. Change Code (CHG) (/)
3. Supplier Code (SPL) (/)
Reporting organization must send its cage code. Code ZZZZZ if the reporting organization has no cage code (transmission of RON - Reporting Organization name - then required) or if the reporting organization is the Operator (RON not required in this case).
4. Operator Code (OPR) (/)
Use 3 digit ICAO code only. Code ZZZZZ if no ICAO code exists (bizjet operator for instance), transmission of name -WHO- is then required.
5. Aircraft_Model_Code (AMC) (/)
6. Aircraft Identification Number (AIN) (/)
Code ZZZZZ if submitting Aircraft Registration Number- REG- or Operator Aircraft Internal Identifier- OIN- when AIN not sent.
However use of AIN (serial number assigned by the aircraft manufacturer) is strongly recommended.
7. Removal Reason Text (RMT) (/)
8. Part Removal Date (RED) (/)
9. Removal Type Code (TYC) (/)
Must be coded U, S, or O
Refer to figure 4 (Removal/Findings Flow chart) above in Section 1 and to figure 6 in Supporting Technical Information for details on how to code TYC.
REMOVED LRU SEGMENT (RLS)
Removed LRU Segment (RLS) details the various elements that allow to fully identify the part that has been removed from the aircraft. A RLS segment will be provided in each LRU Removal Record and in each Shop Finding Record. A Removed LRU Segment starts with the following Control Data elements:
10. Segment Identifier Code (SEG) (/)
Coded "RLS"
11. Part Number (PNR) (/)
Code ZZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
12. Part Serial Number (SER) (/)
Code ZZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
13. Manufacturer Code (MFR) (/)
The above thirteen data elements are positional, mandatory and must be transmitted in the order shown.
14. + Overlength Part Number (OPN) (/)
15. + Airline Stock Number (ASN) (/)
Required if PNR coded ZZZZZ
16. + Unique Component Identification Number (UCN) (/)
Required if SER coded ZZZZZ
17. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
Example Removed LRU Segment
SEG RLS/PNR 101222-3/SER 118/MFR 87112/
18. +Company Name (WHO) (/)
Required if OPR coded ZZZZZ
19. +Aircraft Registration Number (REG) (/)
20. +Operator Aircraft Internal Identifier (OIN) (/)
One of REG or OIN required if AIN coded ZZZZZ.
If REG or OIN are used, the operator must then provide a cross reference table to the receiver of this record prior to implementation and maintain this table up to date (method and periodicity to be agreed between sender and receiver).
21. +Reporting Organization Name (RON) (/)
Required if Reporting Organization Code coded ZZZZZ
22. +Operator Event Identifier (OEI) (/)
23. +Removal Tracking Identifier (RTI) (/)
24. +Aircraft Message Text (AMT) (/)
25. +Component Position Code (CPI) (/)
26. +Model of Applicability Code (MOA) (/)
Used to identify the engine installed on the aircraft
27. +Engine Position Code (EPC) (/)
NHA SEGMENT (NHS)
Next Higher assembly Segment (NHS) details the various elements that allow to fully identify the next higher assembly of either the part that has been removed from the aircraft (LRU Removal Record) or the worked piece part (Piece Part Record). The entire segment is optional in both records, however if provided it must contain as a minimum the first 4 data elements (which then become mandatory). A Next Higher assembly Segment starts with the following Control Data elements:
28. +Segment Identifier Code (SEG) (/)
Coded "NHS"
29. +Part Number (PNR) (/)
Code ZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
30. +Part Serial Number (SER) (/)
Code ZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
31. +Manufacturer Code (MFR) (/)
The above four data elements are positional, mandatory and must be transmitted in the order shown, when NHS segment is transmitted.
32. + Overlength Part Number (OPN) (/)
33. + Additional Descriptive Text (ADT) (/)
34. + Airline Stock Number (ASN) (/)
Required if PNR transmitted and coded ZZZZZ
35. + Unique Component Identification Number (UCN) (/)
Required if SER transmitted and coded ZZZZZ
36. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
Example NHA Segment
SEG NHS/PNR 101222-3/SER 118/MFR 87112
37. +Maintenance Action Text (MNT) (/)
38. +Reason For Removal Clarification Text (RET) (/)
39. +Total Time Text (TTM) (/)
Total Time Text can occur a maximum of six times corresponding to :
TSN (Time Since New) and CSN (Cycles Since New)
TSI (Time Since Installation) and CSI (Cycles Since Installation)
TSR (Time Since Repair) and CSR (Cycles Since Repair)
TSC (Time Since Check) and CSC (Cycles Since Check)
TSV (Time Since (engine) Visit) and CSV (Cycles Since (engine) Visit)
TSO (Time Since Overhaul) and CSO (Cycles Since Overhaul)
40. +Fault Code (FLT) (/)
41. +Catalog Sequence Number (CSN) (/)
42. +Removal Station Code (RST) (/)
43. +Aircraft Cumulative Total Flight Hours (CTH) (/)
44. +Aircraft Cumulative Total Cycles (CTC) (/)
INSTALLED LRU SEGMENT (ILS)
Installed LRU Segment (ILS) details the various elements that allow to fully identify the part that has been installed on the aircraft to replace the removed LRU (LRU Removal Record). The entire segment is optional, however if provided it must contain as a minimum the first 4 data elements (which then become mandatory). An Installed LRU Segment starts with the following Control Data elements:
45. +Segment Identifier Code (SEG) (/)
Coded "ILS"
46. +Part Number (PNR) (/)
Code ZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
47. +Part Serial Number (SER) (/)
Code ZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
48. +Manufacturer Code (MFR) (/)
The above four data elements are positional, mandatory and must be transmitted in the order shown, when ILS segment is transmitted.
49. + Overlength Part Number (OPN) (/)
50. + Airline Stock Number (ASN) (/)
Required if PNR transmitted and coded ZZZZZ
51. + Unique Component Identification Number (UCN) (/)
Required if SER transmitted and coded ZZZZZ
52. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
Example Installed LRU Segment
SEG ILS/PNR 101222-3/SER 223/MFR 87112/
+Indicates conditional data elements
SHOP FINDINGS RECORD STRUCTURE
PURPOSE
This Record is for collecting and exchanging LRU shop repair/teardown findings. It is to be completed by an aircraft operator’s repair shop, third party repair facility or original equipment manufacturer for the purpose of detailing the findings associated with an LRU that enters a shop.
Key fields will link the LRU Removal Record to the Shop Finding Record.
INPUT CONTENTS AND SEQUENCE
A Shop Findings Record is including up to four types of Segment Identifier Codes (SEG). Only one occurrence of each type is allowed.
The four segments are mandatory in all data transmission : Removed LRU segment (RLS), Received LRU segment (RCS), Shipped Unit segment (SUS), and Shop Action Details segment (SAS).
1. Record Type Code (RTC) (/)
Always coded "34"
2. Change Code (CHG) (/)
3. Supplier Code (SPL) (/)
Reporting organization must send its cage code. Code ZZZZZ if the reporting organization has no cage code(transmission of RON - Reporting Organization name - then required) or if the reporting organization is the Operator (RON not required in this case).
4. Shop Findings Record Identifier (SFI) (/)
5. Operator Code (OPR) (/)
Use 3 digit ICAO code only. Code ZZZZZ if no ICAO code exists (bizjet operator for instance), transmission of name -WHO- is then required.
6. Aircraft_Model_Code (AMC) (/)
7. Aircraft Identification Number (AIN) (/)
Code ZZZZZ if submitting Aircraft Registration Number- REG- or Operator Aircraft Internal Identifier- OIN- when AIN not sent.
However use of AIN (serial number assigned by the aircraft manufacturer) is strongly recommended.
8. Part Removal Date (RED) (/)
9. Removal Type Code (TYC) (/)
Must be coded U, S, or O
Refer to figure 4 (Removal/Findings Flow chart) above in Section 1 and to figure 6 in Supporting Technical Information for details on how to code TYC.
10. Shop Finding Text (FIT) (/)
This data element is vital for the computation of reliability (MTBF(J), MTBF(N), MTBF(C)). Refer to figure 7 in Supporting Technical Information which details the various situations with corresponding FIT coding.
FIT is a data set group and is used only once.
REMOVED LRU SEGMENT (RLS)
Removed LRU Segment (RLS) details the various elements that allow to fully identify the part that has been removed from the aircraft. A RLS segment will be provided in each LRU Removal Record and in each Shop Finding Record. A Removed LRU Segment starts with the following Control Data elements:
11. Segment Identifier Code (SEG) (/)
Coded "RLS"
12. Part Number (PNR) (/)
Code ZZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
13. Part Serial Number (SER) (/)
Code ZZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
14. Manufacturer Code (MFR) (/)
The above fourteen data elements are positional, mandatory and must be transmitted in the order shown.
15. + Overlength Part Number (OPN) (/)
16. + Airline Stock Number (ASN) (/)
Required if PNR coded ZZZZZ
17. + Unique Component Identification Number (UCN) (/)
Required if SER coded ZZZZZ
18. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
Example Removed LRU Segment
SEG RLS/PNR 101222-3/SER 118/MFR 87112/
RECEIVED LRU SEGMENT (RCS)
Received LRU Segment (RCS) details the various elements that allow to fully identify the part that has been received in the shop for repair. A RCS segment will be provided in each Shop Finding Record. A Received LRU Segment starts with the following Control Data elements:
19. Segment Identifier Code (SEG) (/)
Coded "RCS"
20. Part Number (PNR) (/)
Code ZZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
21. Part Serial Number (SER) (/)
Code ZZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
22. Manufacturer Code (MFR) (/)
The above four data elements are positional, mandatory and must be transmitted in the order shown.
23. + Overlength Part Number (OPN) (/)
24. + Airline Stock Number (ASN) (/)
Required if PNR coded ZZZZZ
25. + Unique Component Identification Number (UCN) (/)
Required if SER coded ZZZZZ
26. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
27. + Additional Descriptive Text (ADT) (/)
28. + Configuration/Modification Status Number (CMS) (/)
29. + Incoming Inspection/Shop Action Text (INT) (/)
Example Received LRU Segment
SEG RCS/PNR 101222-3/SER 118/MFR 87112/
SHIPPED UNIT SEGMENT (SUS)
Shipped Unit Segment (SUS) details the various elements that allow to fully identify the part that has been shipped out of the shop after repair. A SUS segment will be provided in each Shop Finding Record. A Shipped Unit Segment starts with the following Control Data elements:
30. Segment Identifier Code (SEG) (/)
Coded "SUS"
31. Part Number (PNR) (/)
Code ZZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
32. Part Serial Number (SER) (/)
Code ZZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
33. Manufacturer Code (MFR) (/)
The above four data elements are positional, mandatory and must be transmitted in the order shown.
34. + Overlength Part Number (OPN) (/)
35. + Airline Stock Number (ASN) (/)
Required if PNR coded ZZZZZ
36. + Unique Component Identification Number (UCN) (/)
Required if SER coded ZZZZZ
37. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
38. + Additional Descriptive Text (ADT) (/)
39. + Configuration/Modification Status Number (CMS) (/)
Example Shipped Unit Segment
SEG SUS/PNR 101222-4/SER 118/MFR 87112/
SHOP ACTION DETAILS SEGMENT (SAS)
Shop Action Details Segment (SAS) details the various elements that allow to identify the work and actions performed in the shop during repair of the unit. A SAS segment will be provided in each Shop Finding Record. A Shop Action Details Segment starts with the following Control Data elements:
40. Segment Identifier Code (SEG) (/)
Coded "SAS"
41. Incoming Inspection/Shop Action Text (INT) (/)
The above two data elements are positional, mandatory and must be transmitted in the order shown.
42. + Manufacturer's Authority Text (MAT) (/)
43. + Repair Process Code (RPC) (/)
Example Shop Action Details Segment
SEG SAS/INT replaced lamp in on-off push-button/
44. +Related Shop Finding Record Identifier (RSI) (/)
45. +Company Name (WHO) (/)
46. +Aircraft Registration Number (REG) (/)
47. +Operator Aircraft Internal Identifier (OIN) (/)
One of REG or OIN required if AIN coded ZZZZZ.
If REG or OIN are used, the operator must then provide a cross reference table to the receiver of this record prior to implementation and maintain this table up to date (method and periodicity to be agreed between sender and receiver).
48. +Reporting Organization Name (RON) (/)
Required if Reporting Organization Code coded ZZZZZ
49. +Removal Tracking Identifier (RTI) (/)
50. +Repair Location Code (RLC) (/)
51. +Removal Reason Text (RMT) (/)
52. +Material Receipt Date (MRD) (/)
53. +Shop Findings Code (SFC) (/)
54. +Reason For Removal Clarification Text (RET) (/)
55. +Total Time Text (TTM) (/)
Total Time Text can occur a maximum of six times corresponding to :
TSN (Time Since New) and CSN (Cycles Since New)
TSI (Time Since Installation) and CSI (Cycles Since Installation)
TSR (Time Since Repair) and CSR (Cycles Since Repair)
TSC (Time Since Check) and CSC (Cycles Since Check)
TSV (Time Since (engine) Visit) and CSV (Cycles Since (engine) Visit)
TSO (Time Since Overhaul) and CSO (Cycles Since Overhaul)
56. +Shipped Date (SHP) (/)
+Indicates conditional data elements
PIECE PART RECORD STRUCTURE
PURPOSE
This Record is for collecting defective or suspect Shop Replaceable Units (SRU’s) and other piece parts associated with the shop received LRU. It is to be completed by an aircraft operator’s repair shop, third party repair facility or original equipment manufacturer for the purpose of detailing the findings associated with an LRU that enters a shop.
One field will link the Shop Findings Record to the Piece Part Record.
INPUT CONTENTS AND SEQUENCE
A Piece Part Record is including up to three types of Segment Identifier Codes (SEG). Only one occurrence of each type is allowed.
The Worked Piece Part segment (WPS) is mandatory in all data transmission. The Replaced Piece Part segment (RPS) and Next Higher Assembly segment (NHS) are optional.
1. Record Type Code (RTC) (/)
Always coded "35"
2. Change Code (CHG) (/)
3. Supplier Code (SPL) (/)
Reporting organization must send its cage code. Code ZZZZZ if the reporting organization has no cage code(transmission of RON - Reporting Organization name - then required) or if the reporting organization is the Operator (RON not required in this case).
4. Shop Findings Record Identifier (SFI) (/)
5. Piece Part Record Identifier (PPI) (/)
WORKED PIECE PART SEGMENT (WPS)
Worked Piece Part Segment (WPS) details the various elements that allow to fully identify the piece part that has been worked in the shop during repair. A WPS segment will be provided in each Piece Part Record. A Worked Piece Part Segment starts with the following Control Data elements:
6. Segment Identifier Code (SEG) (/)
Coded "WPS"
7. Part Number (PNR) (/)
Code ZZZZZ if submitting Additional Descriptive Text- ADT-(name of the part) when PNR not sent or not available.
The above seven data elements are positional, mandatory and must be transmitted in the order shown.
8. + Overlength Part Number (OPN) (/)
9. + Additional Descriptive Text (ADT) (/)
Required if PNR coded ZZZZZ
10. + Manufacturer Code (MFR) (/)
11. + Part Serial Number (SER) (/)
Example Worked Piece Part Segment
SEG WPS/PNR F232/
12. Piece Part Failure Description (FDE) (/)
13. +Geographic and/or Electrical Position (GEL) (/)
14. +Primary Piece Part Failure Indicator (PFC) (/)
15. +Reporting Organization Name (RON) (/)
Required if Reporting Organization Code coded ZZZZZ
16. +Removal Tracking Identifier (RTI) (/)
17. +Material Received Date (MRD) (/)
REPLACED PIECE PART SEGMENT (RPS)
Replaced Piece Part Segment (RPS) details the various elements that allow to fully identify the piece part that has been replaced in the shop during repair (Piece Part Record). The entire segment is optional, however if provided it must contain as a minimum the first 2 data elements (which then become mandatory). A Replaced Piece Part Segment starts with the following Control Data elements:
18. +Segment Identifier Code (SEG) (/)
Coded "RPS"
19. +Part Number (PNR) (/)
Code ZZZZZ if submitting Additional Descriptive Text- ADT-(name of the part) when PNR not sent or not available.
The above two data elements are positional, mandatory and must be transmitted in the order shown, when RPS segment is transmitted.
20. + Overlength Part Number (OPN) (/)
21. + Additional Descriptive Text (ADT) (/)
Required when PNR coded ZZZZZ
22. + Manufacturer Code (MFR) (/)
23. + Part Serial Number (SER) (/)
Example Replaced Piece Part Segment
SEG RPS/PNR 10122/
NHA SEGMENT (NHS)
Next Higher assembly Segment (NHS) details the various elements that allow to fully identify the next higher assembly of either the part that has been removed from the aircraft (LRU Removal Record) or the worked piece part (Piece Part Record). The entire segment is optional in both records, however if provided it must contain as a minimum the 4 mandatory data elements. A Next Higher assembly Segment starts with the following Control Data elements:
24. +Segment Identifier Code (SEG) (/)
Coded "NHS"
25. +Part Number (PNR) (/)
Code ZZZZZ if submitting Airline Stock Number- ASN-(part number assigned by operator) when PNR not sent.
However use of PNR (part number assigned by the manufacturer) is strongly recommended.
26. +Part Serial Number (SER) (/)
Code ZZZZ if submitting Unique Component Identification Number- UCN-(serial number assigned by operator) when SER not sent.
However use of SER (serial number assigned by the manufacturer) is strongly recommended.
27. +Manufacturer Code (MFR) (/)
The above four data elements are positional, mandatory and must be transmitted in the order shown.
28. + Overlength Part Number (OPN) (/)
29. + Airline Stock Number (ASN) (/)
Required if PNR coded ZZZZZ
30. + Unique Component Identification Number (UCN) (/)
31. + Supplier Code (SPL) (/)
Used in conjonction with UCN if the operator assigned the UCN (not needed when the manufacturer assigned the UCN)
32. + Additional Descriptive Text (ADT) (/)
Example NHA Segment
SEG NHS/PNR 101222-3/SER 118/MFR E4632/
33. +Failed Piece Part Next Higher Assembly NHA Part Number (NPN) (/)
+Indicates conditional data elements
AIRCRAFT HOURS AND LANDINGS RECORD STRUCTURE
PURPOSE
This Record is for detailing the total flight hours and total cycles of an operator’s fleet. It is for the purpose of calculating reliability measures such as Mean Time Between Unscheduled Removals (MTBUR), Mean Time Between Failure (MTBF), etc. It is to be completed by an aircraft operator using one record per aircraft.
INPUT CONTENTS AND SEQUENCE
1. Record Type Code (RTC) (/)
Always coded "36"
2. Change Code (CHG) (/)
3. Supplier Code (SPL) (/)
Reporting organization must send its cage code. Code ZZZZZ if the reporting organization has no cage code(transmission of RON - Reporting Organization name - then required) or if the reporting organization is the Operator (RON not required in this case).
4. Operator Code (OPR) (/)
Use 3 digit ICAO code only. Code ZZZZZ if no ICAO code exists (bizjet operator for instance), transmission of name -WHO- is then required.
5. Aircraft_Model_Code (AMC) (/)
6. Aircraft Identification Number (AIN) (/)
Code ZZZZZ if submitting Aircraft Registration Number- REG- or Operator Aircraft Internal Identifier- OIN- when AIN not sent.
However use of AIN (serial number assigned by the aircraft manufacturer) is strongly recommended.
7. Report Month (RDT) (/)
8. Aircraft Cumulative Total Flight Hours (CTH) (/)
9. Aircraft Cumulative Total Cycles (CTC) (/)
10. +Company Name (WHO) (/)
Required if OPR coded ZZZZZ
11. +Aircraft Registration Number (REG) (/)
12. +Operator Aircraft Internal Identifier (OIN) (/)
One of REG or OIN required if AIN coded ZZZZZ.
If REG or OIN are used, the operator must then provide a cross reference table to the receiver of this record prior to implementation and maintain this table up to date (method and periodicity to be agreed between sender and receiver).
13. +Reporting Organization Name (RON) (/)
Required if Reporting Organization Code coded ZZZZZ
14. +Aircraft Monthly Total Flight Hours (MTH) (/)
15. +Aircraft Monthly Total Cycles (MTC) (/)
+Indicates conditional data elements
PROCEDURES
Several data conditions applicable to various portions of this section are of prime importance to the methods of transmitting data. The data conditions are broken into the following categories:
● Update Change Codes
● Multiple Occurrences of a Text Element Identifier (TEI)
● Data Set Groups
Each of the above data conditions will be explained in detail in the pages that follow.
Each record is variable in length. To illustrate the examples, a record may be represented on several lines in this document. Therefore realize that a continuation of a record on the next line does NOT depict a break in the record.
If alpha "O" is encountered in a numeric field, it will be converted to a numeric zero.
If a supplier duplicates a TEI that is only required once, the record will be rejected if the data element is mandatory. If the duplicated TEI is conditional, only the data element will be rejected except as noted in the data audit section. This same rejection procedure will be used when multiple occurring TEI's are applied and the allowable number exceeds the limit.
To establish some of the rules stated in this section it has been assumed that both the sender and the receiver are maintaining their own data base.
Update Change Codes
Change Codes are transmitted with each record to indicate the type of change being requested. To keep the change management as simple as possible there are three Change Codes - New, Total Replacement, and Delete - that are allowed in reliability applications.
The changes are managed at the record level only (not at the segment or data element level).
NEW - CHANGE CODE = N
When establishing a new record, all mandatory data elements must be present. All other conditional data elements can be added if needed.
TOTAL REPLACEMENT - CHANGE CODE = T
When Change Code T is used, the existing data base record will be replaced in total at the receiver. If the record does not exist , the record will be added to the data base. All mandatory data elements are required to do a total replacement. Conditional data elements are included as required.
DELETE - CHANGE CODE = D
A delete is accomplished by providing a Change Code of D. All mandatory data elements are required to do a delete. All conditional data elements in the existing data base record will be deleted as well.
The following diagram explains the use of the N, D, T values to manage changes to the record.
FLOW DIAGRAM FOR RECORD CHANGES MANAGEMENT
[pic]
FIGURE 5
Create a LRU Removal Record - Update Change Codes (Change Code N)
N - To establish a new LRU removal record, the Change Code of N is applied. The minimum data elements required to establish a record are:
Record Type Code
Change Code
Supplier Code
Operator Code
Aircraft_Model_Code
Aircraft Identification Number
Removal Reason Text
Part Removal Date
Removal Type Code
REMOVED LRU SEGMENT (RLS)
Segment Identifier Code
Part Number
Part Serial Number
Manufacturer Code
Note : The specification allows some of the above mandatory elements to be coded as ZZZZZ when not transmitted. In this case it is required to send the corresponding conditional data element when the record is created. If this requirement is not met, the record is rejected (refer to data audit section further in this chapter).
TRANSMISSION EXAMPLES
RTC 33/CHG N/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 431/MFR 81205/
RTC 33/CHG N/SPL 92130/OPR ZZZZZ/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 431/MFR 81205/WHO MY AIRLINE/
Delete a LRU Removal Record - Update Change Codes (Change Code D)
D - The Change Code of D is used to delete an entire record from the Receiver Data Base.
When deleting a record, all the mandatory data elements must be sent.
TRANSMISSION EXAMPLE
RTC 33/CHG D/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 431/MFR 81205/
Revise a LRU Removal Record
When revising a LRU Removal Record two situations may occur.
If the change involves one of the key element of the record, the existing record must first be deleted (using change code D), then the modified record is submitted as a new record (change coded N).
Modify a key data elements of LRU Removal Record
|List of Key data elements - LRU Removal Record |
|Unconditional Data Element |TEI |Comment |
|Operator Code |OPR | |
|Aircraft_Model_Code |AMC | |
|Aircraft Identification Number |AIN | |
|Part Removal Date |RED | |
|Part Number |PNR |Part number of the removed LRU within RLS segment |
|Part Serial Number |SER |Serial number of the removed LRU within RLS segment |
|Manufacturer Code |MFR |Manufacturer code of the removed LRU within RLS segment |
| | | |
|On condition Data Elements |TEI |Condition |
|+Overlength Part Number |OPN |Within RLS segment if OPN necessary (P/N > 15 digits) |
|+Airline Stock Number |ASN |Within RLS segment if PNR coded ZZZZZ |
|+Unique Component Identification Number |UCN |Within RLS segment if SER coded ZZZZZ |
|+Supplier Code |SPL |Within RLS segment if SER coded ZZZZZ and SPL different from MFR |
|+Company Name |WHO |If OPR coded ZZZZZ |
|+Aircraft Registration Number |REG |If AIN coded ZZZZZ and REG used to identify aircraft |
|+Operator Aircraft Internal Identifier |OIN |If AIN coded ZZZZZ and OIN used to identify aircraft |
+Indicates conditional data elements
TRANSMISSION EXAMPLE
RTC 33/CHG D/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 431/MFR 81205/
RTC 33/CHG N/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 432/MFR 81205/
If the change does not involve a key data element, for instance adding/modifying a conditional data element or modifying a non key mandatory data element, the revised record is transmitted with a change code of T.
Update Change Codes (Change Code T)
T -The Change Code of T is used to totally replace a record. Revising an already sent record may be effected by submitting a complete replacement record, change coded T. This technique simply overlays the current record on file with the replacement record. If the record does not exist on the central file, the record will be added to the data base.
When the "T" Change Code is used, all mandatory data elements must be restated.
TRANSMISSION EXAMPLE
RTC 33/CHG T/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 431/MFR 81205/TTM 10000 - N/TTM 2000 1000 O/RST LHR/
Multiple Occurrences Of A Text Element Identifier in LRU Removal Record
Only one TEI in LRU Removal Record can have multiple occurrences :
Total Time Text (TTM)
TTM can have up to 6 occurences. Multiple occurrences of the above TEI must appear consecutively in the record.
When a supplier changes any data with multiple occurrences, all occurrences which should remain on the receiver Data Base must also be transmitted. The receiver will delete all existing occurrences and insert the new information transmitted by the sender.
Data Set Groups
Data set groups are a method of collecting groups of information together within a Text Element Identifier (TEI). There is one data set group which apply to LRU Removal Record :
Total Time Text (TTM)
When a supplier changes any data within the TTM data set group, all sets which should remain on the Data Base, must also be transmitted. The receiver will delete all existing TTM records and insert the new information transmitted by the sender.
|TOTAL TIME TEXT |
|Data Elements |Data Base Record (receiver) |Sender Transmission |Updated Data Base Record |
| | | |(receiver) |
|Record Type Code | |33 | |
|Change Code | |T | |
|Supplier Code | |ZZZZZ | |
|Operator Code |VIR |VIR |VIR |
|Aircraft_Model_Code |A340-300 |A340-300 |A340-300 |
|Aircraft Identification Number |121 |121 |121 |
|Removal Reason Text |Broken switch |Broken switch |Broken switch |
|Part Removal Date |230699 |230699 |230699 |
|Removal Type Code |U |U |U |
|Segment Identifier Code | |RLS | |
|Part Number, of removed LRU |65-7234 |65-7234 |65-7234 |
|Part Serial Number, of removed LRU |431 |431 |431 |
|Manufacturer Code, of removed LRU |81205 |81205 |81205 |
| +Total Time Text | |TTM | |
| (Operating Time) | |10000 | |
| (Operating Cycle Count) | |- | |
| (Time/Cycle Reference Code) | |N | |
| +Total Time Text | |TTM | |
| (Operating Time) | |2000 | |
| (Operating Cycle Count) | |1000 | |
| (Time/Cycle Reference Code) | |O | |
|TSN : Time Since New |10000 | |10000 |
|TSO : Time Since Overhaul |2000 | |2000 |
|CSO : Cycles Since Overhaul | | |1000 |
+ = Conditional Data Elements
( ) = Components of a Data Set Group
The sender is adding a third information CSO (Cycles Since Overhaul). Since TSN and TSO are still valid information, they must be repeated.
SUPPLIER TRANSMISSION
RTC 33/CHG T/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RMT Broken switch/
RED 230699/TYC U/
SEG RLS/PNR 65-7234/SER 431/MFR 81205/
TTM 10000 - N/TTM 2000 1000 O/
Create a Shop Findings Record - Update Change Codes (Change Code N)
N - To establish a new Shop Findings record, the Change Code of N is applied. The minimum data elements required to establish a record are:
Record Type Code
Change Code
Supplier Code
Shop Findings Record Identifier
Operator Code
Aircraft_Model_Code
Aircraft Identification Number
Part Removal Date
Removal Type Code
Shop Finding Text
REMOVED LRU SEGMENT (RLS)
Segment Identifier Code
Part Number
Part Serial Number
Manufacturer Code
RECEIVED LRU SEGMENT (RCS)
Segment Identifier Code
Part Number
Part Serial Number
Manufacturer Code
SHIPPED UNIT SEGMENT (SUS)
Segment Identifier Code
Part Number
Part Serial Number
Manufacturer Code
SHOP ACTION DETAILS SEGMENT (SAS)
Segment Identifier Code
Incoming Inspection/Shop Action Text
Note : The specification allows some of the above mandatory elements to be coded as ZZZZZ when not transmitted. In this case it is required to send the corresponding conditional data element when the record is created. If this requirement is not met, the record is rejected (refer to data audit section further in this chapter).
TRANSMISSION EXAMPLES
RTC 34/CHG N/SPL F9111/SFI A10012/OPR VIR/AMC A340-300/AIN 121/RED 230699/
TYC U/FIT FT - CR - - - /
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/
RTC 34/CHG N/SPL F9111/SFI A10012/OPR ZZZZZ/AMC A340-300/AIN 121/RED 230699/
TYC U/FIT FT - CR - - - /
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/WHO MY AIRLINE/
Delete a Shop Findings Record - Update Change Codes (Change Code D)
D - The Change Code of D is used to delete an entire record from the Receiver Data Base.
When deleting a record, all the mandatory data elements must be sent.
TRANSMISSION EXAMPLE
RTC 34/CHG D/SPL F9111/SFI A10012/OPR VIR/AMC A340-300/AIN 121/RED 230699/
TYC U/FIT FT - CR - - - /
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/
Revise a Shop Findings Record
When revising a Shop Findings Record two situations may occur.
If the change involves one of the key element of the record, the existing record must first be deleted (using change code D), then the modified record is submitted as a new record (change coded N).
Modify a key data elements of Shop Findings Record
|List of Key data elements - Shop Findings Record |
|Unconditional Data Element |TEI |Comment |
|Operator Code |OPR | |
|Aircraft_Model_Code |AMC | |
|Aircraft Identification Number |AIN | |
|Part Removal Date |RED | |
|Part Number |PNR |Part number of the removed LRU within RLS segment |
|Part Serial Number |SER |Serial number of the removed LRU within RLS segment |
|Manufacturer Code |MFR |Manufacturer code of the removed LRU within RLS segment |
| | | |
|On condition Data Elements |TEI |Condition |
|+Overlength Part Number |OPN |Within RLS segment if OPN necessary (P/N > 15 digits) |
|+Airline Stock Number |ASN |Within RLS segment if PNR coded ZZZZZ |
|+Unique Component Identification Number |UCN |Within RLS segment if SER coded ZZZZZ |
|+Supplier Code |SPL |Within RLS segment if SER coded ZZZZZ and SPL different from MFR |
|+Company Name |WHO |If OPR coded ZZZZZ |
|+Aircraft Registration Number |REG |If AIN coded ZZZZZ and REG used to identify aircraft |
|+Operator Aircraft Internal Identifier |OIN |If AIN coded ZZZZZ and OIN used to identify aircraft |
|+Related Shop Findings Record Identifier |RSI | |
+Indicates conditional data elements
TRANSMISSION EXAMPLE
RTC 34/CHG D/SPL F9111/SFI A10012/OPR VIR/AMC A340-300/AIN 121/RED 230699/
TYC U/FIT FT - CR - - - /
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/
RTC 34/CHG N/SPL F9111/SFI A10012/OPR VIR/AMC A340-300/AIN 131/RED 230699/
TYC U/FIT FT - CR - - - /
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/
If the change does not involve a key data element, for instance adding/modifying a conditional data element or modifying a non key mandatory data element, the revised record is transmitted with a change code of T.
Update Change Codes (Change Code T)
T -The Change Code of T is used to totally replace a record. Revising an already sent record may be effected by submitting a complete replacement record, change coded T. This technique simply overlays the current record on file with the replacement record. If the record does not exist on the central file, the record will be added to the data base.
When the "T" Change Code is used, all mandatory data elements must be restated.
TRANSMISSION EXAMPLE
RTC 34/CHG T/SPL F9111/SFI A10012/OPR VIR/AMC A340-300/AIN 121/RED 230699/
TYC U/FIT FT - CR - - - /
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/MRD 140799/
Multiple Occurrences Of A Text Element Identifier in Shop Findings Record
Only one TEI in Shop Findings Record can have multiple occurrences :
Total Time Text (TTM)
TTM can have up to 6 occurences. Multiple occurrences of the above TEI must appear consecutively in the record.
When a supplier changes any data with multiple occurrences, all occurrences which should remain on the receiver Data Base must also be transmitted. The receiver will delete all existing occurrences and insert the new information transmitted by the sender.
Data Set Groups
Data set groups are a method of collecting groups of information together within a Text Element Identifier (TEI). There are two data set groups which apply to Shop Findings Record :
Shop Finding Text (FIT)
Total Time Text (TTM)
When a supplier changes any data within the FIT, and TTM data set groups, all sets which should remain on the Data Base, must also be transmitted. The receiver will delete all existing FIT, or TTM records and insert the new information transmitted by the sender.
|SHOP FINDING TEXT |
|Data Elements |Data Base Record (receiver) |Sender Transmission |Updated Data Base Record |
| | | |(receiver) |
|Record Type Code | |34 | |
|Change Code | |T | |
|Supplier Code |F9111 |F9111 |F9111 |
|Shop Finding Record Identifier |A10012 |A10012 |A10012 |
|Operator Code |VIR |VIR |VIR |
|Aircraft_Model_Code |A340-300 |A340-300 |A340-300 |
|Aircraft Identification Number |121 |121 |121 |
|Part Removal Date |230699 |230699 |230699 |
|Removal Type Code |U |U |U |
|Shop Finding Text | |FIT | |
|(Inspection Findings Code) | |FT | |
|(Inspection Findings Code) | |NI | |
|(Inspection Findings Code) | |CR | |
|(Inspection Findings Code) | |- | |
|(Inspection Findings Code) | |- | |
|(Inspection Findings Code) | |- | |
|Failure/Fault Found |Y | |Y |
|Failure/Fault Induced |D | |Y |
|Failure/Fault Confirms Reason for Removal |Y | |Y |
|Failure/Fault Confirms Aircraft Message |D | |D |
|Failure/Fault Confirms Aircraft Part Bite Message |D | |D |
|Hardware/Software Failure |D | |D |
|Segment Identifier Code | |RLS | |
|Part Number, of removed LRU |65-7234 |65-7234 |65-7234 |
|Part Serial Number, of removed LRU |431 |431 |431 |
|Manufacturer Code, of removed LRU |F9111 |F9111 |F9111 |
|Segment Identifier Code | |RCS | |
|Part Number, of received LRU |65-7234 |65-7234 |65-7234 |
|Part Serial Number, of received LRU |431 |431 |431 |
|Manufacturer Code, of received LRU |F9111 |F9111 |F9111 |
|Segment Identifier Code | |SUS | |
|Part Number, of shipped LRU |65-7234-1 |65-7234-1 |65-7234-1 |
|Part Serial Number, of shipped LRU |431 |431 |431 |
|Manufacturer Code, of shipped LRU |F9111 |F9111 |F9111 |
|Segment Identifier Code | |SAS | |
|Incoming Inspection/Shop Action Text |Replaced QFE-QNH Switch |Replaced QFE-QNH Switch |Replaced QFE-QNH Switch |
+ = Conditional Data Elements ( ) = Components of a Data Set Group
The sender is adding a third information : the failure is not induced. Since previous information (failure has been found and failure confirms reason for removal) is still valid information, it must be repeated.
SUPPLIER TRANSMISSION
RTC 34/CHG T/SPL F9111/SFI A10012/OPR VIR/AMC A340-300/AIN 121/
RED 230699/TYC U/FIT FT NI CR - - -/
SEG RLS/PNR 65-7234/SER 431/MFR F9111/
SEG RCS/PNR 65-7234/SER 431/MFR F9111/
SEG SUS/PNR 65-7234-1/SER 431/MFR F9111/
SEG SAS/INT Replaced QFE-QNH Switch/
Create a Piece Part Record - Update Change Codes (Change Code N)
N - To establish a new Piece Part record, the Change Code of N is applied. The minimum data elements required to establish a record are:
Record Type Code
Change Code
Supplier Code
Shop Findings Record Identifier
Piece Part Record Identifier
WORKED PIECE PART SEGMENT (WPS)
Segment Identifier Code
Part Number
Piece Part Failure Description
Note : The specification allows some of the above mandatory elements to be coded as ZZZZZ when not transmitted. In this case it is required to send the corresponding conditional data element when the record is created. If this requirement is not met, the record is rejected (refer to data audit section further in this chapter).
TRANSMISSION EXAMPLES
RTC 35/CHG N/SPL F9111 /SFI A10012/PPI A10013/
SEG WPS/PNR A12345/FDE QFE-QNH switch broken due to a crack. Replaced/
RTC 35/CHG N/SPL ZZZZZ/SFI 181114/PPI 234567/
SEG WPS/PNR A12345/FDE QFE-QNH switch broken due to a crack. Replaced/RON MY NAME/
Delete a Piece Part Record - Update Change Codes (Change Code D)
D - The Change Code of D is used to delete an entire record from the Receiver Data Base.
When deleting a record, all the mandatory data elements must be sent.
TRANSMISSION EXAMPLE
RTC 35/CHG D/SPL F9111 /SFI A10012/PPI A10013/
SEG WPS/PNR A12345/FDE QFE-QNH switch broken due to a crack. Replaced/
Revise a Piece Part Record
When revising a Piece Part Record two situations may occur.
If the change involves one of the key element of the record, the existing record must first be deleted (using change code D), then the modified record is submitted as a new record (change coded N).
Modify a key data elements of Piece Part Record
|List of Key data elements - Piece Part Record |
|Unconditional Data Element |TEI |Comment |
|Shop Findings Record Identifier |SFI | |
| | | |
|On condition Data Elements |TEI |Condition |
|Part Number |PNR |Within NHS segment when transmitted |
|Part Serial Number |SER |Within NHS segment when transmitted |
|Manufacturer Code |MFR |Within NHS segment when transmitted |
|+Overlength Part Number |OPN |Within NHS segment if OPN necessary (P/N > 15 digits) |
|+Airline Stock Number |ASN |Within NHS segment if PNR coded ZZZZZ |
|+Unique Component Identification Number |UCN |Within NHS segment if SER coded ZZZZZ |
|+Supplier Code |SPL |Within NHS segment if SER coded ZZZZZ and SPL different from MFR |
+Indicates conditional data elements
TRANSMISSION EXAMPLE
RTC 35/CHG D/SPL F9111 /SFI A10011/PPI A10013/
SEG WPS/PNR A12345/FDE QFE-QNH switch broken due to a crack. Replaced/
RTC 35/CHG N/SPL F9111 /SFI A10012/PPI A10013/
SEG WPS/PNR A12345/FDE QFE-QNH switch broken due to a crack. Replaced/
If the change does not involve a key data element, for instance adding/modifying a conditional data element or modifying a non key mandatory data element, the revised record is transmitted with a change code of T.
Update Change Codes (Change Code T)
T -The Change Code of T is used to totally replace a record. Revising an already sent record may be effected by submitting a complete replacement record, change coded T. This technique simply overlays the current record on file with the replacement record. If the record does not exist on the central file, the record will be added to the data base.
When the "T" Change Code is used, all mandatory data elements must be restated.
TRANSMISSION EXAMPLE
RTC 35/CHG T/SPL F9111 /SFI A10011/PPI A10013/
SEG WPS/PNR A12345/FDE QFE-QNH switch broken due to a crack. Replaced/PFC Y/
Create Aircraft Hours & Landings Record-Update Change Codes (Change Code N)
N - To establish a new aircraft hours and landings record, the Change Code of N is applied. The minimum data elements required to establish a record are:
Record Type Code
Change Code
Supplier Code
Operator Code
Aircraft_Model_Code
Aircraft Identification Number
Report Month
Aircraft Cumulative Total Flight Hours
Aircraft Cumulative Total Cycles
Note : The specification allows some of the above mandatory elements to be coded as ZZZZZ when not transmitted. In this case it is required to send the corresponding conditional data element when the record is created. If this requirement is not met, the record is rejected (refer to data audit section further in this chapter).
TRANSMISSION EXAMPLES
RTC 36/CHG N/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RDT 0399/CTH 10000/CTC 2000/
Delete Aircraft Hours & Landings Record-Update Change Codes (Change Code D)
D - The Change Code of D is used to delete an entire record from the Receiver Data Base.
When deleting a record, all the mandatory data elements must be sent.
TRANSMISSION EXAMPLE
RTC 36/CHG D/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RDT 0399/CTH 10000/CTC 2000/
Revise an Aircraft Hours and Landings Record
When revising a LRU Removal Record two situations may occur.
If the change involves one of the key element of the record, the existing record must first be deleted (using change code D), then the modified record is submitted as a new record (change coded N).
Modify a key data elements of LRU Removal Record
|List of Key data elements - LRU Removal Record |
|Unconditional Data Element |TEI |Comment |
|Operator Code |OPR | |
|Aircraft_Model_Code |AMC | |
|Aircraft Identification Number |AIN | |
|Report Month |RDT | |
| | | |
+Indicates conditional data elements
TRANSMISSION EXAMPLE
RTC 36/CHG D/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RDT 0399/CTH 10000/CTC 2000/
RTC 36/CHG N/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 122/RDT 0399/CTH 10000/CTC 2000/
If the change does not involve a key data element, for instance adding/modifying a conditional data element or modifying a non key mandatory data element, the revised record is transmitted with a change code of T.
Update Change Codes (Change Code T)
T -The Change Code of T is used to totally replace a record. Revising an already sent record may be effected by submitting a complete replacement record, change coded T. This technique simply overlays the current record on file with the replacement record. If the record does not exist on the central file, the record will be added to the data base.
When the "T" Change Code is used, all mandatory data elements must be restated.
TRANSMISSION EXAMPLE
RTC 36/CHG T/SPL ZZZZZ/OPR VIR/AMC A340-300/AIN 121/RDT 0399/CTH 10000/CTC 2000/
MTH 300/MTC 62/
SUPPORTING TECHNICAL INFORMATION
Coding of Removal Type Code (TYC)
This data element is the key and direct entry for computation of reliability values (MTBR, MTBUR, and then various MTBFs). Referring to figure 4 (Removals/Findings Flow Chart) earlier in this chapter the following diagram (figure 6) specifies how Removal Type Code (TYC) must be coded in each situation that may occur. Strict adherence to this diagram is required to allow an accurate computation.
[pic]
FIGURE 6
Coding of Shop Findings Text (FIT)
Shop Findings Text is a Data Set Group. It is made of six different coding positions. Each position corresponds to one piece of information that allows to categorize shop findings. The specified sequencing must be respected.
The allowed values of the data element Inspection Findings Code (IFC) are listed in the following table :
|Shop Findings Text (FIT) |IFC value |
|Position 1 |Failure/Fault Found |FT |
| |Failure/Fault Not Found |NT |
| |Comment : this value indicates that a failure/fault was found, whether or not the failure/fault substantiates the |
| |reason for removal and whether or not the failure/fault is induced. Refer to figure 7. |
|Position 2 |Failure/Fault Induced |IN |
| |Failure/Fault Not Induced |NI |
| |Don't know |- |
| |Comment : this value indicates whether or not the faults or failures found in a component were caused by an |
| |out-of-spec condition i.e. externally induced failure. Refer to figure 7. |
|Position 3 |Failure/Fault Confirms Reason for Removal |CR |
| |Failure/Fault Does Not Confirm Reason for Removal |NC |
| |Don't know |- |
| |Comment : this value indicates whether or not the failure/fault found substantiates the reason for removal. Refer |
| |to figure 7. |
|Position 4 |Failure/Fault Confirms Aircraft Message |CM |
| |Failure/Fault Does Not Confirm Aircraft Message |NM |
| |Don't know |- |
| |Comment : this value is an indication of the validity that the component's built-in-test-equipment (BITE) |
| |indications were correctly processed by the aircraft's message system. |
|Position 5 |Failure/Fault Confirms Aircraft Part BITE Message |CB |
| |Failure/Fault Does Not Confirm Aircraft Part BITE Message |NB |
| |Don't know |- |
| |Comment : this value is an indication of the validity of the built-in-test-equipment of the component positively |
| |identifying a component failure : i.e. BITE indication correlated with the true component failure? |
|Position 6 |Hardware Failure |HW |
| |Software Failure |SW |
| |Don't know |- |
| |Comment : this value is an indication of the type of failure that indicates whether or not the component failure |
| |was due to either hardware or software. |
For position 1 the use of dash ("-") is not allowed.
Referring to figure 4 (Removals/Findings Flow Chart) earlier in this chapter the following diagram (figure 7) specifies how positions 1, 2, and 3 of FIT must be coded in each situation that may occur. Strict adherence to this diagram is required to allow an accurate computation of reliability (MTBF(J), MTBF(N), MTBF(C)).
The ability of the repair shop to populate all positions above depends upon the results of tests and analyses performed by the repair shop, but it also heavily depends upon information that the shop is provided with. This information is transmitted through LRU Removal Record with the main following data elements : Removal Reason Text (RMT), Maintenance Action Text (MNT), Fault code (FLT), Aircraft Message Text (AMT). Although some of these data elements are conditional it is highly recommended to send them.
Coding positions 1, 2, and 3 of Shop Finding Text (FIT)
[pic]
FIGURE 7
Data Audits
Each data field or relationship audit found to be in error as a result of these audit routines should be identified by the receiver as one of the following:
1. Rejection of the entire record
2. Rejection of a conditional segment
3. Rejection of a conditional TEI
All audited data regardless of audit message should be reported to the supplier in writing as soon as possible.
An entire record rejection, conditional segment reject, or conditional TEI reject should not be updated in the receiver's file as applicable.
In order to maintain the integrity of the receiver's data base all audit reports should be returned to the supplier within ten (10) working days following receipt of the file.
The following lists indicates the audit by record type (i.e. LRU Removal Record, Shop Findings Record, etc.)
RELIABILITY DATA AUDITS
Note: All data field characteristics, definitions, structure, remarks and audits can be found in the ATA Common Support Data Dictionary (CSDD). Any exceptions will be indicated in the "Type Audit" column.
The "Action" column indicates the action to be taken in the event of an error condition in order to maintain compatibility between the user's and transmitter's databases.
LRU REMOVAL RECORD AUDIT
Following are the edits that should be performed by the receiver of the LRU Removal Record
|LRU REMOVAL RECORD - RECORD TYPE 33 |
|DATA FIELD | TYPE AUDIT | ACTION |
|Change Code |Must be N, T, or D | Reject record |
|Supplier Code | | Reject record |
|Operator Code |Must be 3 positions alphanumeric or ZZZZZ | Reject record |
|Aircraft_Model_Code | | Reject record |
|Aircraft Identification Number | | Reject record |
|Removal Reason Text | | Reject record |
|Part Removal Date | | Reject record |
|Removal Type Code |Must be U, S, or O | Reject record |
|Segment Identifier Code |Must be RLS, NHS, or ILS | Reject record |
|Part Number | | Reject record if RLS |
| | |Reject segment if NHS or ILS |
|Part Serial Number | | Reject record if RLS |
| | |Reject segment if NHS or ILS |
|Manufacturer Code | | Reject record if RLS |
| | |Reject segment if NHS or ILS |
|Overlength Part Number | | Reject record if RLS |
| | |Reject segment if NHS or ILS |
|Airline Stock Number | | Reject record if RLS |
| | |Reject segment if NHS or ILS |
|Unique Component Identification Number | | Reject record if RLS |
| | |Reject segment if NHS or ILS |
|Company Name | | Reject record |
|Aircraft Registration Number | | Reject record |
|Operator Aircraft Internal Identifier | | Reject record |
|Reporting Organization Name | | Reject record |
|Operator Event Identifier | | Reject TEI |
|Removal Tracking Identifier | | Reject TEI |
|Aircraft Message Text | | Reject TEI |
|Component Position Code | | Reject TEI |
|LRU REMOVAL RECORD - RECORD TYPE 33 |
|DATA FIELD | TYPE AUDIT | ACTION |
|Model of Applicability Code | | Reject TEI |
|Engine Position Code | | Reject TEI |
|Additional Descriptive Text | | Reject TEI |
|Maintenance Action Text | | Reject TEI |
|Reason For Removal Clarification Text | | Reject TEI |
|Total Time Text | | Reject TEI |
|Fault Code | | Reject TEI |
|Catalog Sequence Number | | Reject TEI |
|Removal station Code | | Reject TEI |
|Aircraft Cumulative Total Flight Hours | | Reject TEI |
|Aircraft Cumulative Total Cycles | | Reject TEI |
|LRU REMOVAL RECORD RELATIONAL EDITS |
|DATA FIELD | EDIT | ERROR MESSAGE | RECEIVER ACTION |
| Relational | CHG=N, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational | CHG=D, all mandatory TEIs must be |Missing Mandatory TEI. If applied against non |Record Rejected |
| |submitted |existent record, Record Not Present | |
| Relational | CHG=T, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational |If SPL coded ZZZZZ RON must be submitted|Missing Reporting Source Identification |Record Rejected |
| Relational |If OPR coded ZZZZZ WHO must be submitted|Missing Operator identification |Record Rejected |
| Relational |If AIN coded ZZZZZ REG or OIN must be |Missing Aircraft Identification |Record Rejected |
| |submitted | | |
| Relational |If PNR coded ZZZZZ ASN must be submitted|Missing Part Number |Record Rejected if RLS segment, or |
| | | |reject segment if NHS or ILS |
| Relational |If SER coded ZZZZZ UCN must be submitted|Missing Serial Number |Record Rejected if RLS segment, or |
| | | |reject segment if NHS or ILS |
| Relational |If NHS sent, PNR and SER and MFR must be|Invalid NHS segment |Reject Segment |
| |submitted | | |
| Relational |If ILS sent, PNR and SER and MFR must be|Invalid ILS segment |Reject Segment |
| |submitted | | |
| Relational | Only TEI of TTM can have multiple |Invalid Repeating TEI |Record Rejected or if TEI |
| |occurrences | |conditional, reject TEI |
| Relational | TEI of TTM has a maximum number of 6 |Invalid Repeating TEI |Reject TEI |
| |occurrences | | |
| Relational |Repeating occurrences of TTM not listed |Repeating TEI Not Listed Consecutively |Reject TEI |
| |consecutively | | |
| Relational | TTM, Operating Time, Operating cycle |Invalid TTM |Reject TEI |
| |count, Time/Cycle Reference Code | | |
| |relationship must be in accordance with | | |
| |the Common Support Data Dictionary | | |
SHOP FINDINGS RECORD AUDIT
Following are the edits that should be performed by the receiver of the Shop Findings Record
|SHOP FINDINGS RECORD - RECORD TYPE 34 |
|DATA FIELD | TYPE AUDIT | ACTION |
|Change Code |Must be N, T, or D | Reject record |
|Supplier Code | | Reject record |
|Shop Findings Record Identifier | | Reject record |
|Operator Code |Must be 3 positions alphanumeric or ZZZZZ | Reject record |
|Aircraft_Model_Code | | Reject record |
|Aircraft Identification Number | | Reject record |
|Part Removal Date | | Reject record |
|Removal Type Code |Must be U, S, or O | Reject record |
|Shop Finding Text | | Reject record |
|Segment Identifier Code |Must be RLS, RCS, SUS, or SAS | Reject record |
|Part Number | | Reject record |
|Part Serial Number | | Reject record |
|Manufacturer Code | | Reject record |
|Overlength Part Number | | Reject record |
|Airline Stock Number | | Reject record |
|Unique Component Identification Number | | Reject record |
|Additional Descriptive Text | | Reject TEI |
|Configuration/Modification Status Number | | Reject TEI |
|Incoming Inspection/Shop Action Text | | Reject Record if SAS |
| | |Reject TEI otherwise |
|Manufacturer's Authority Text | | Reject TEI |
|Repair Process Code | | Reject TEI |
|Related Shop Finding Record Identifier | | Reject record |
|Company Name | | Reject record |
|Aircraft Registration Number | | Reject record |
|Operator Aircraft Internal Identifier | | Reject record |
|Reporting Organization Name | | Reject record |
|SHOP FINDINGS RECORD - RECORD TYPE 34 |
|DATA FIELD | TYPE AUDIT | ACTION |
|Removal Tracking Identifier | | Reject TEI |
|Repair Location Code | | Reject TEI |
|Removal Reason Text | | Reject TEI |
|Material Receipt Date | | Reject TEI |
|Shop Findings Code | | Reject TEI |
|Reason For Removal Clarification Text | | Reject TEI |
|Total Time Text | | Reject TEI |
|Shipped Date | | Reject TEI |
|SHOP FINDINGS RECORD RELATIONAL EDITS |
|DATA FIELD | EDIT | ERROR MESSAGE | RECEIVER ACTION |
| Relational | CHG=N, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational | CHG=D, all mandatory TEIs must be |Missing Mandatory TEI. If applied against non |Record Rejected |
| |submitted |existant record, Record Not Present | |
| Relational | CHG=T, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational |If SPL coded ZZZZZ RON must be submitted|Missing Reporting Source Identification |Record Rejected |
| Relational |If OPR coded ZZZZZ WHO must be submitted|Missing Operator identification |Record Rejected |
| Relational |If AIN coded ZZZZZ REG or OIN must be |Missing Aircraft Identification |Record Rejected |
| |submitted | | |
| Relational |If PNR coded ZZZZZ ASN must be submitted|Missing Part Number within RLS (or RCS or SUS) |Record Rejected |
| | |segment | |
| Relational |If SER coded ZZZZZ UCN must be submitted|Missing Serial Number within RLS (or RCS or SUS) |Record Rejected |
| | |segment | |
| Relational | Only TEI of TTM can have multiple |Invalid Repeating TEI |Record Rejected or if TEI |
| |occurrences | |conditional, reject TEI |
| Relational | TEI of TTM has a maximum number of 6 |Invalid Repeating TEI |Reject TEI |
| |occurrences | | |
| Relational |Repeating occurrences of TTM not listed |Repeating TEI Not Listed Consecutively |Reject TEI |
| |consecutively | | |
| Relational | TTM, Operating Time, Operating cycle |Invalid TTM |Reject TEI |
| |count, Time/Cycle Reference Code | | |
| |relationship must be in accordance with | | |
| |the Common Support Data Dictionary | | |
PIECE PART RECORD AUDIT
Following are the edits that should be performed by the receiver of the Piece Part Record
|PIECE PART RECORD - RECORD TYPE 35 |
|DATA FIELD | TYPE AUDIT | ACTION |
| Change Code | Must be N, T, or D | Reject record |
| Supplier Code | | Reject record |
| Shop Findings Record Identifier | | Reject record |
| Piece Part Record Identifier | | Reject record |
| Segment Identifier Code | Must be WPS, RPS, or NHS | Reject record if WPS |
| | |Reject segment if RPS or NHS |
| Part Number | | Reject record if WPS |
| | |Reject segment if RPS or NHS |
| Overlength Part Number | | Reject record if WPS |
| | |Reject segment if RPS or NHS |
| Additional Descriptive Text | | Reject record if WPS |
| | |Reject segment if RPS or NHS |
| Manufacturer Code | | Reject segment if NHS |
| | |Reject TEI otherwise |
| Part Serial Number | | Reject segment if NHS |
| | |Reject TEI otherwise |
| Piece Part Failure Description | | Reject record |
| Geographic and/or Electrical Position | | Reject TEI |
| Primary Piece Part Failure Indicator | | Reject TEI |
| Reporting Organization Name | | Reject record |
| Removal Tracking Identifier | | Reject TEI |
| Material Received Date | | Reject TEI |
| Airline Stock Number | | Reject NHS segment |
| Unique Component Identification Number | | Reject NHS segment |
| Failed Piece Part Next Higher Assembly NHA Part| | Reject TEI |
|Number | | |
|PIECE PART RECORD RELATIONAL EDITS |
|DATA FIELD | EDIT | ERROR MESSAGE | RECEIVER ACTION |
| Relational | CHG=N, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational | CHG=D, all mandatory TEIs must be |Missing Mandatory TEI. If applied against non |Record Rejected |
| |submitted |existent record, Record Not Present | |
| Relational | CHG=T, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational |If SPL coded ZZZZZ RON must be submitted|Missing Reporting Source Identification |Record Rejected |
| Relational |If RPS sent, PNR must be submitted |Invalid RPS segment |Reject Segment |
| Relational |Within WPS or RPS segment if PNR coded |Missing Part Number/Identification of Piece Part |Record Rejected if WPS segment, or |
| |ZZZZZ ADT must be submitted | |reject segment if RPS |
| Relational |If NHS sent, PNR and SER and MFR must be|Invalid NHS segment |Reject Segment |
| |submitted | | |
| Relational |Within NHS segment if PNR coded ZZZZZ |Missing NHA Part Number |Reject NHS segment |
| |ASN must be submitted | | |
| Relational |Within NHS segment if SER coded ZZZZZ |Missing NHA Serial Number |Reject NHS segment |
| |UCN must be submitted | | |
AIRCRAFT HOURS AND LANDINGS RECORD AUDIT
Following are the edits that should be performed by the receiver of the LRU Removal Record
|AIRCRAFT HOURS AND LANDINGS RECORD - RECORD TYPE 36 |
|DATA FIELD | TYPE AUDIT | ACTION |
|Change Code |Must be N, T, or D |Reject record |
|Supplier Code | |Reject record |
|Operator Code |Must be 3 positions alphanumeric or ZZZZZ |Reject record |
|Aircraft_Model_Code | |Reject record |
|Aircraft Identification Number | |Reject record |
|Report Month | |Reject record |
|Aircraft Cumulative Total Flight Hours | |Reject record |
|Aircraft Cumulative Total Cycles | |Reject record |
|Company Name | |Reject record |
|Aircraft Registration Number | |Reject record |
|Operator Aircraft Internal Identifier | |Reject record |
|Reporting Organization Name | |Reject record |
|Aircraft Monthly Total Flight Hours | |Reject TEI |
|Aircraft Monthly Total Cycles | |Reject TEI |
|AIRCRAFT HOURS AND LANDINGS RECORD RELATIONAL EDITS |
|DATA FIELD | EDIT | ERROR MESSAGE | RECEIVER ACTION |
| Relational | CHG=N, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational | CHG=D, all mandatory TEIs must be |Missing Mandatory TEI. If applied against non |Record Rejected |
| |submitted |existant record, Record Not Present | |
| Relational | CHG=T, all mandatory TEIs must be |Missing Mandatory TEI. |Record Rejected |
| |submitted | | |
| Relational |If SPL coded ZZZZZ RON must be submitted|Missing Reporting Source Identification |Record Rejected |
| Relational |If OPR coded ZZZZZ WHO must be submitted|Missing Operator identification |Record Rejected |
| Relational |If AIN coded ZZZZZ REG or OIN must be |Missing Aircraft Identification |Record Rejected |
| |submitted | | |
TEI IN-FRONT METHOD
Introduction
The section 1 details the specification of the different records needed for component reliability data collection based on the traditional Spec2000 method of transmitting data.
This paragraph proposes an alternate method that would allow companies wishing to use common PC based spreadsheets or database software to still participate to reliability data exchange.
This method uses the exact same data elements as defined by the data dictionary including their Text Element Identifier (TEI).
The Method
Assuming that a file is being transmitted as an ASCII text file.
1-The first line should define the type of data being transmitted, e.g. one of the following:
LRU Removal Record : /RTC 33/
Shop Findings Record : /RTC 34/
Piece Part Record : /RTC 35/
Aircraft Hours and Landings Record : /RTC 36/
2-The second line should contain a list of the TEI of the parameters being transmitted (leaving out those optional parameters that have not been opted for) separated by the Spec2000 delimiter (/).
The structure of the records as defined in the relevant paragraphs is entirely applicable.
3-Then following this line would be all the records of the selected type for the month, each record containing data for one event and contain data for each parameter as specified in the second line in the same order as the parameters specified, one record per line.
Note: The second line would list the maximum number of parameters intended to be populated by the supplier of the data. Then in the following data lines, if an optional field has no data for a particular event, the field could be left blank – which would be captured by having two delimiters following each other (//).
The above file can easily be imported into most common spreadsheets software, and the second line being a statement of the variable names, would enable the file to be imported into a database software through an appropriate query.
Example
Figure 8 shows a sample removal file submitted by an operator in ASCII text format. Figure 9 shows what it would look like if imported into a spreadsheet software.
In this example the transmission includes only the mandatory data elements of the record (refer to LRU Removal Record Structure section).
Figure 8 : LRU Removal Records-TEI In-Front
RTC 33/
CHG/SPL/OPR/AMC/AIN/RMT/RED/TYC/RLSPNR/RLSSER/RLSMFR/
N/ZZZZZ/OP2/D8Q200/471/NVS PRESS XDCR TROUBLE SHOOTING/070997/U/P55D-1-N-6-38-W-4-A/100767/11111/
N/ZZZZZ/OP1/D8Q200/435/NOISE ON R/H SIDE OF CABIN GOES OFF WITH NVS PUT ON PAUSE. REPLACED #27 ACTUATOR. SYSTEM TESTED; FOUND OKAY./201297/U/8-800-52-005/9625133/22222/
N/ZZZZZ/OP3/D8Q200/477/UNIT LOCKS UP ---CONTROLLER-LFCU/250298/U/8-811-01-008/2043/33333/
N/ZZZZZ/OP3/D8Q200/480/CONTROLLER-LFCU ; CODES 15 AND 19/110797/U/8-811-01-008/2041/33333/
N/ZZZZZ/OP3/D8Q200/480/CONTROLLER-LFCU ; FAILS TO READ; ID SWITCH PRESSURE CABIN SWITCH WOW PAUSE CTL SWITCH & FAILS/071097/U/8-811-01-008/2041/33333/
N/ZZZZZ/OP3/D8Q200/480/UNIT FAILS SELF TEST STEPS COMPUTER BAD RETURN FOR WARRANTY./040897/U/8-811-01-008/2010/33333/
N/ZZZZZ/OP3/D8Q200/480/FAILS TO ACCEPT DOWNLOAD DISC./190897/U/8-811-01-008/2095/33333/
N/ZZZZZ/OP3/D8Q200/484/FAILED...AMPLIFIER-POWER/260398/U/8-800-50-014/2950/22222/
N/ZZZZZ/OP3/D8Q200/490/FAILS TO DRIVE VIBRATION...AMPLIFIER-POWER/080398/U/8-800-50-014/4172/22222/
N/ZZZZZ/OP3/D8Q200/488/FAILED TO SHOW UNIT SN ON INITAILIZATION OF MTX TERM...CONTROLLER-LFCU/010498/U/8-811-01-008/2077/33333/
N/ZZZZZ/OP1/D8Q200/435/NOISE IN PROP ARC AREA INTERMITTENT BANGING IN AREA OF RH EMGY EXIT F/O ADVISES THAT NOISE STOPS WHEN NVS IS PUT IN PAUSE./010198/U/8-800-52-005/9625133/22222/
N/ZZZZZ/OP2/D8Q200/471/NVS PX TDUCER UNSERVICEABLE/070398/U/P55D-1-N-6-38-W-4-A/100767/11111/
N/ZZZZZ/OP2/D8Q200/473/NVS PRESS XDCR TROUBLESHOOTING/070997/U/P55D-1-N-6-38-W-4-A/97774/11111/
N/ZZZZZ/OP2/D8Q200/473/NSV SYS FAULT/220198/U/P55D-1-N-6-38-W-4-A/100767/11111/
N/ZZZZZ/OP4/D8Q200/462/NVS ACTIVE NOISE CONTROL UNIT (ANCU) - NVS COMPUTER TO BE CHANGED FOR UPGRADED SOFT WARE/160798/S/8-811-01-008/2082/33333/
N/ZZZZZ/OP3/D8Q200/502/ANVS INOP...CONTROLLER-LFCU/170698/U/8-811-01-008/2028/33333/
N/ZZZZZ/OP3/D8Q200/502/BITE TEST FAIL CONTROLLER HARD FAIL...CONTROLLER-LFCU/050798/U/8-811-01-008/2077/33333/
Figure 9
|LRURemovals |
|OPR |AMC |AIN |RMT |RED |TYC |RLSPNR |RLSSER |RLSMFR |
|OP2 |D8Q200 |471 |NVS PRESS XDCR TROUBLE SHOOTING |07-sept-97 |U |P55D-1-N-6-38-W-4-A |100767 |11111 |
|OP1 |D8Q200 |435 |NOISE ON R/H SIDE OF CABIN GOES OFF WITH NVS PUT ON PAUSE. REPLACED #27 ACTUATOR. |20-déc-97 |U |8-800-52-005 |9625133 |22222 |
| | | |SYSTEM TESTED; FOUND OKAY. | | | | | |
|OP3 |D8Q200 |477 |UNIT LOCKS UP ---CONTROLLER-LFCU |25-févr-98 |U |8-811-01-008 |2043 |33333 |
|OP3 |D8Q200 |480 |CONTROLLER-LFCU ; CODES 15 AND 19 |11-juil-97 |U |8-811-01-008 |2041 |33333 |
|OP3 |D8Q200 |480 |CONTROLLER-LFCU ; FAILS TO READ; ID SWITCH PRESSURE CABIN SWITCH WOW PAUSE CTL SWITCH |07-oct-97 |U |8-811-01-008 |2041 |33333 |
| | | |& FAILS | | | | | |
|OP3 |D8Q200 |480 |UNIT FAILS SELF TEST STEPS COMPUTER BAD RETURN FOR WARRANTY. |04-août-97 |U |8-811-01-008 |2010 |33333 |
|OP3 |D8Q200 |480 |FAILS TO ACCEPT DOWNLOAD DISC. |19-août-97 |U |8-811-01-008 |2095 |33333 |
|OP3 |D8Q200 |484 |FAILED...AMPLIFIER-POWER |26-mars-98 |U |8-800-50-014 |2950 |22222 |
|OP3 |D8Q200 |490 |FAILS TO DRIVE VIBRATION...AMPLIFIER-POWER |08-mars-98 |U |8-800-50-014 |4172 |22222 |
|OP3 |D8Q200 |488 |FAILED TO SHOW UNIT S/N ON INITAILIZATION OF MTX TERM...CONTROLLER-LFCU |01-avr-98 |U |8-811-01-008 |2077 |33333 |
|OP1 |D8Q200 |435 |NOISE IN PROP ARC AREA INTERMITTENT BANGING IN AREA OF RH EMGY EXIT F/O ADVISES THAT |01-janv-98 |U |8-800-52-005 |9625133 |22222 |
| | | |NOISE STOPS WHEN NVS IS PUT IN PAUSE. | | | | | |
|OP2 |D8Q200 |471 |NVS PX TDUCER UNSERVICEABLE |07-mars-98 |U |P55D-1-N-6-38-W-4-A |100767 |11111 |
|OP2 |D8Q200 |473 |NVS PRESS XDCR TROUBLESHOOTING |07-sept-97 |U |P55D-1-N-6-38-W-4-A |97774 |11111 |
|OP2 |D8Q200 |473 |NSV SYS FAULT |22-janv-98 |U |P55D-1-N-6-38-W-4-A |100767 |11111 |
|OP4 |D8Q200 |462 |NVS ACTIVE NOISE CONTROL UNIT (ANCU) - NVS COMPUTER TO BE CHANGED FOR UPGRADED SOFT WARE|16-juil-98 |S |8-811-01-008 |2082 |33333 |
|OP3 |D8Q200 |502 |ANVS INOP...CONTROLLER-LFCU |17-juin-98 |U |8-811-01-008 |2028 |33333 |
|OP3 |D8Q200 |502 |BITE TEST FAIL CONTROLLER HARD FAIL...CONTROLLER-LFCU |05-juil-98 |U |8-811-01-008 |2077 |33333 |
PROPOSED MODIFICATIONS TO CSDD
ASSOCIATED TO
CHAPER 11-RELIABILITY DATA COLLECTION
CONTENT
Section 1 : Modification of existing Spec 2000 data elements
Section 2 : Modification of existing non Spec 2000 data elements
Section 3 : New data elements
Section 1 : Modification of existing Spec 2000 data elements
|CSDD DATA ELEMENT NAME |TEI |CSDD KEY |
|Additional Descriptive Text |ADT |MM00005 |
|Aircraft Identification Number |AIN |MM00012 |
|Airline Stock Number |ASN |MM00017 |
|Catalog Sequence Number |CSN |MM00043 |
|Change Code |CHG |MM00047 |
|Company Name |WHO |MM00052 |
|Component Position Code |CPI |MM00053 |
|Configuration/Modification Status Number |CMS |MM00055 |
|Data Set Group | |MM00090 |
|Inspection Findings Code |IFC |MM00140 |
|Manufacturer Code |MFR |MM00177 |
|Manufacturer's Authority Text |MAT |MM00179 |
|Material Receipt Date |MRD |MM00185 |
|Model of Applicability Code |MOA |MM00193 |
|Operating cycle count | |MM00207 |
|Operating Time | |MM00208 |
|Operator Code |OPR |MM00209 |
|Overlength Part Number |OPN |MM00223 |
|Part Number |PNR |MM00228 |
|Part Removal Date |RED |MM00234 |
|Part Serial Number |SER |MM00235 |
|Reason for Removal Clarification Text |RET |MM00274 |
|Record Type Code |RTC |MM00281 |
|Removal Station Code |RST |MM00286 |
|Repair Location Code |RLC |MM00293 |
|Repair Process Code |RPC |MM00295 |
|Report period date |RDT |MM00305 |
|Segment Identifier Code |SEG |MM00316 |
|Supplier Code |SPL |MM00354 |
|Time/Cycle Reference Code | |MM00374 |
|Total Time Text |TTM |MM00390 |
|Unique Component Identification Number |UCN |MM00397 |
Name
ADDITIONAL DESCRIPTIVE TEXT
Ver
1 2
Key
MM00005
SGML Tag TEI: ADT
Definition: Additional Descriptive Text is the additional nomenclature modifying the Keyword Name.
For reliability applications Additional Descriptive Text gives the full name of a part : the component (LRU) itself, its subassemblies (SRU), or piece parts.
Class: AN Remark: Fixed Record Character Length: 26
Class : AN
COBOL Picture : X(26)
Decimal:
Min_Length: 2
Max_Length: 260
Case_Sensitive: False
Business Rules:
Provisioning S/T File Format - Explanation Code 52 (EC52) Text
POS. 01-26 Free Form Text X(26)
Provisioning V File and, Delivery Configuration Data Format and Reliability Applications - TEI: ADT
Free Form Text X(02) to X(260)
|APPLICATION AREAS |
| Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 03 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Nam e
AIRCRAFT IDENTIFICATION NUMBER
Ve r
1 2
Ke y
MM000 12
SGML Tag TEI : AIN
Definit ion: The Aircraft Identification Number is the manufacturer's permanently-applied serial number for the airframe, which is assigned prior to aircraft registration.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 6
Case_Sens itive: False
Business Rules: For reliability applications, code ZZZZZ if submitting either Aircraft Registration Number (REG) or Operator Aircraft Internal Identifier (OIN) when AIN not sent.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Used within the data set group, Aircraft Number Text (ANT) in Warranty Claims |
| | | |(Chapter14). |
| | | |Used in reliability applications to identify the aircraft from which the LRU was|
| | | |removed. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 22 |
| MM | Record Type Code | Data Element | 26 |
| MM | Record Type Code | Data Element | 28 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Nam e
AIRLINE STOCK NUMBER
Ve r
1 2
Ke y
MM000 17
SGML Tag TEI : ASN
Definit ion: Identifies the owner's stock number.
Class: AN Remark: Fixed Record Character Length: 11
Class : AN
COBOL Picture : X(11)
Decimal:
Min_Lengt h: 1
Max_Lengt h: 11
Case_Sens itive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 12 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | A1ADDPRT |
| MM | Command Code | Data Element | A1CHANGE |
| MM | Command Code | Data Element | A1STOCKS |
| MM | Command Code | Data Element | A1UPDATE |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
CATALOG SEQUENCE NUMBER
Ve r
1 2
Ke y
MM000 43
SGML Tag TEI : CSN
Definit ion: Catalog Sequence Number (CSN) identifies a specific location of a part number in the Illustrated Parts Catalog (IPC) or Illustrated Parts List (IPL) by its component elements: Aircraft System Code, Sub-System Code, Sub-Sub-System Code, Unit/Assembly Number, Figure Number and Variant, and Item Number and Variant.
Class: AN Remark: Fixed Record Character Length: 13
Class : AN
COBOL Picture : 9(8)A9(3)
Decimal:
Min_Length:
Max_Length: 13
Case_Sen sitive: False
Business Rules: 99999999A999A
99 AIRCRAFTSYSTEM CODE
9 SUB-SYSTEM CODE
9 SUB-SUB-SYSTEM CODE
99 UNIT/ASSEMBLY NUMBER
99 FIGURE NUMBER
A VARIANT-FIGURE NUMBER
999 ITEM NUMBER
A VARIANT-ITEM NUMBER *
The lack of Variant - Figure Number is designated by a blank (space) in both fixed and variable format records.
The lack of a Variant - Item Number is designated by a blank (space) in fixed length records and truncated in variable length records. When providing preliminary data in the 'V' File system only and the complete Catalog Sequence Number has not yet been assigned, (1) the Aircraft System Code (two positions) must be provided as a minimum in Line Maintenance Segments and (2) the Aircraft System, Sub-System, Sub-Sub-System and Unit/Assembly Number (six positions) must be provided as a minimum in Component Breakdown Segments.
For reliability applications either (1) the Aircraft System and Sub-System Codes (four positions) or (2) the Aircraft System, Sub-System, Sub-Sub-System and Unit/Assembly Number (six positions) can be provided.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to individual component data elements for definitions and codes. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 04 |
| MM | Record Type Code | Data Element | 05 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 29 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
Na me
CHANGE CODE
Ve r
2 3
Ke y
MM000 47
SGML Tag TEI : CHG
Definit ion: Change Code indicates the transaction status of the individual record or Explanation Code Segment being transmitted.
Class: A Remark: Fixed Record Character Length: 01
Class : A
COBOL Picture : A(01)
Decimal:
Min_Leng th: 1
Max_Leng th: 1
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Applies to S and T Files and to reliability applications. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 8 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | P1DISUPD |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | R1CDBACK |
| MM | Command Code | Data Element | R1CDBUPD |
| MM | Record Type Code | Data Element | 02 |
| MM | Record Type Code | Data Element | 03 |
| MM | Record Type Code | Data Element | 04 |
| MM | Record Type Code | Data Element | 05 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 08 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 17 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Record Type Code | Data Element | 36 |
|PERMITTED VALUES |
| Permitted Value | S e q # | D ef au lt | Description |
|T | | F |Total (full image) replacement of an established record. (Not used in Provisioning) |
|R | | F |Revision to an established record or Explanation Code Segment. (Not used in Reliability) |
|N | | F |Transmission of a new record or Explanation Code Segment. |
|D | | F |Deletion of an established record or Explanation Code Segment. |
|A | | F |Annual price update (Not used in Provisioning, and Reliability) |
ALIAS
Na me
COMPANY NAME
Ve r
1 2
Ke y
MM000 52
SGML Tag TEI : WHO
Definit ion: Formal name of a company.
For reliability applications Company Name represents the name of the aircraft operator (LRU Removal record, Shop Finding record or Aircraft Hours and Landings record).
Class: AN Remark:
Decimal:
Min_Leng th: 1
Max_Leng th: 55
Case_Sen sitive: False
Business Rules: Free Form Text
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 12 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | A1STOCKS |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | R1CDBRSP |
| MM | Chapter | Data Element | 8 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
COMPONENT POSITION CODE
Ve r
1 2
Ke y
MM000 53
SGML Tag TEI : CPI
Definit ion: Component Position Code is a code agreed upon between trading partners to denote the physical position of individual serialized components.
Class: AN Remark:
Decimal:
Min_Leng th: 1
Max_Leng th: 5
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | The Component Position Code may be used where the Catalog Sequence Number |
| | | |(CSN) relates to more than one serial number within a Delivery Configuration |
| | | |file/transmission. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
Na me
CONFIGURATION/MODIFICAT ION STATUS NUMBER
Ve r
1 2
Ke y
MM000 55
SGML Tag TEI : CMS
Definit ion: Indicates the modification status of an avionics a component.
Class: AN Remark:
Decimal:
Min_Leng th: 1
Max_Leng th: 26
Case_Sen sitive: False
Business Rules: Composed of part number and a letter code which indicates the modification status of the component.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Na me
DATA SET GROUP
Ve r
2 3
Ke y
MM000 90
SGML Tag TEI :
Definit ion: Data Set Group is a group of interdependent data elements identified by a single Text Element Identifier Code.
Class: Remark:
Decimal:
Min_Leng th:
Max_Len gth:
Case_Sen sitive: False
Business Rules: The Data Set Group structure consists of the TEI code (three alpha letters plus a space),the multiple data elements separated by one position delimiters (the space character), and a terminating delimiter (the slash (/) character) unless end of record. All component data elements of a Data Set Group must be transmitted when initiating or revising a given Data Set Group.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to individual TEI's for definition and structure. |
| | | |Refer to the various application chapters regarding procedures for revising and |
| | | |deleting Data Set Groups. In data set groups applied to Warranty Claims and, |
| | | |Delivery Configuration and Reliability only, dash(es) (depending on the minimum |
| | | |length of the data element) must be used as null character(s) when there is no |
| | | |appropriate entry. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
ALIAS
Na me
INSPECTION FINDINGS CODE
Ve r
1 2
Ke y
MM001 40
SGML Tag TEI: IFC
Defini tion: Inspection Findings Code is the claimant's verified reason for removal of the subject part, or the warrantor's technical findings when accepting or denying a warranty claim. In reliability applications Inspection Findings Code is used by the Shop to define the technical findings when repairing the unit.
Class: AN Remark:
Decimal:
Min_Len gth: 1
Max_Len gth: 3
Case_Se nsitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | W1CDNXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 34 |
|PERMITTED VALUES |
| Permitted Value |S e q # | D ef au lt | Description |
|ZZ | | F |Requires "Inspection Findings Clarification Text" |
|SC | | F |Beyond Physical Repair |
|NT | | F |No Trouble Found (No Failure/Fault Found) |
|FT | | F |Failed Test (Failure/Fault Found) |
|FO | | F |Foreign Object Damage |
|CR | | F |Confirmed Removal |
|CD | | F |Customer Damage |
|BE | | F |Beyond Economic Repair |
|NC | | F |Non Confirmed Removal |
|IN | | F |Induced Failure |
|NI | | F |Non Induced Failure |
|HW | | F |Hardware Failure |
|SW | | F |Software Failure |
|CM | | F |Failure/Fault confirms aircraft message |
|NM | | F |Failure/Fault does not confirm aircraft message |
|CB | | F |Failure/Fault confirms aircraft part bite message |
|NB | | F |Failure/Fault does not confirm aircraft part bite message |
ALIAS
N a m e
MANUFACTURER CODE
Ve r
2 3
Ke y
MM001 77
SGML Tag TEI: MFR
Defin ition: Manufacturer Code identifies the manufacturer, government agency or other organization controlling the design and the part number assignment of the subject part.
Class: AN Remark: Fixed Record Character Length: 05
Class : AN
COBOL Picture : X(05)
Decimal :
Min_Le ngth: 5
Max_Le ngth: 5
Case_S ensitive: False
Busines s Rules:
Use the five position alphanumeric codes specified in Cataloging Handbook H4/H8:Sections A and B, Commercial and Government Entity (CAGE) Codes (United States and Canada only) and Sections C and D, NATO Supply Codes for Manufacturer(NSCM) (excluding United States and Canada).
For standard parts (Standard/Attaching Part Codes 3, 4, and 6) the following part number types will be identified by the referenced Manufacturer Code (CAGE Code/NATO NSCM).
TYPE CAGE CODE TYPE NATO NSCM AC 88041 A K7766
AF 99238 AFNOR F0110
AMS 81343 AGS U1653
AN 88044 AS U1653
AND 99237 BNA F0112
JAN 81350 BNAE F0111
MIL 81349 CCTU F0115
MS 96906 DIN D8286
NAS 80205 EN (AECMA) I9005
NAF 80020 LN D8442
NASA 88006 UTE F0114
SAE 81343
USA 81351
USN 88827
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | For manufacturers and suppliers not having an assigned CAGE Code or NATO NSCM, |
| | | |contact the Air Transport Association (ATA) at the following address or |
| | | |communication link for assignment application: |
| | | |AIR TRANSPORT ASSOCIATION OF AMERICA |
| | | |SPEC 2000 PROGRAM |
| | | |1301 PENNSYLVANIA AVE. N.W. |
| | | |WASHINGTON, D.C. 20004-1707 |
| | | | |
| | | |PHONE: (202) 626-4039 |
| | | |FAX: (202) 626-4081 |
| | | |SITA: WASMMXD |
| | | |Applies to S and T files. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 10 |
| MM | Chapter | Data Element | 12 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 3 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 8 |
| MM | Chapter | Data Element | 9 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | A1ADDPRT |
| MM | Command Code | Data Element | A1CHANGE |
| MM | Command Code | Data Element | A1QTYDEC |
| MM | Command Code | Data Element | A1QTYINC |
| MM | Command Code | Data Element | A1QUOTES |
| MM | Command Code | Data Element | A1STOCKS |
| MM | Command Code | Data Element | A1UPDATE |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | R1CDBACK |
| MM | Command Code | Data Element | R1CDBINQ |
| MM | Command Code | Data Element | R1CDBRSP |
| MM | Command Code | Data Element | R1CDBUPD |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1CUSSHP |
| MM | Command Code | Data Element | R1DSPXMT |
| MM | Command Code | Data Element | R1QTNINT |
| MM | Command Code | Data Element | R1QTNREQ |
| MM | Command Code | Data Element | R1QTNXMT |
| MM | Command Code | Data Element | R1SPLSHP |
| MM | Command Code | Data Element | S1BOOKED |
| MM | Command Code | Data Element | S1ORDEXC |
| MM | Command Code | Data Element | S1PNSTAT |
| MM | Command Code | Data Element | S1POSTAT |
| MM | Command Code | Data Element | S1QUOTES |
| MM | Command Code | Data Element | S1SHIPPD |
| MM | Command Code | Data Element | S1STOCKS |
| MM | Record Type Code | Data Element | 02 |
| MM | Record Type Code | Data Element | 03 |
| MM | Record Type Code | Data Element | 04 |
| MM | Record Type Code | Data Element | 05 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 17 |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 24 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 29 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Reference Document | Data Element | UN/EDIFACT Implementation Convention |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|ALTERNATE PART NUMBER TEXT | Data Set Group |
| CATEGORY I CONTAINER PART NUMBER TEXT | Data Set Group |
| CONTROL SPECIFICATION/DRAWING NUMBER TEXT | Data Set Group |
| MODIFIED COMMERCIAL PART NUMBER TEXT | Data Set Group |
| OPTIONAL PART NUMBER TEXT | Data Set Group |
| PREFERRED SPARE PART NUMBER TEXT | Data Set Group |
| REPLACED PART DATA TEXT | Data Set Group |
| REPLACING PART DATA TEXT | Data Set Group |
| SELECTED ITEM REFERENCE PART NUMBER TEXT | Data Set Group |
| USED ON ASSEMBLY PART NUMBER TEXT | Data Set Group |
Name
MANUFACTURER'S AUTHORITY TEXT
Ver
1 2
Key
MM00179
SGML Tag TEI: MAT
Definition: Manufacturer's Authority Text specifies the Service Bulletin number, ATA Spec 100 technical reference or other technical authority authorizing replacement of the subject part by the replacing part number or warrantable modification of a part number.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 40
Case_Sensitive: False
Business Rules: In reliability applications this element is used to indicate the modifications that have been incorporated in this shop visit.
|APPLICATION AREAS |
| Area | Application | Category | Remarks |
|MM | Spec 2000 | | Caution - |
| | | |In Procurement Planning applications the document specified in the |
| | | |Manufacturer's Authority Text is not an approved source for replacing|
| | | |part number information. The reference number shown may not apply in|
| | | |a given customer fleet. Review Spec 100 documentation for |
| | | |applicability. |
| | | |Refer to data set groups, Replacing Part Data Text (RPD) and Replaced|
| | | |Part Data Text(RPE), for field application. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|REPLACED PART DATA TEXT | Data Set Group |
| REPLACING PART DATA TEXT | Data Set Group |
N a m e
MATERIAL RECEIPT DATE
Ve r
1 2
Ke y
MM001 85
SGML Tag TEI: MRD
Defin ition: Material Receipt Date specifies when the subject material was received by the repairing agency (Supplier Code) for repair.
Class: N Remark:
Decimal :
Min_Le ngth: 6
Max_Le ngth: 6
Case_S ensitive: False
Busines s Rules: 99 99 99 Day Month Year
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | R1CPORSP |
| MM | Command Code | Data Element | R1MATRCP |
| MM | Command Code | Data Element | R1PNRRSP |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
N a m e
MODEL OF APPLICABILITY CODE
Ve r
1 2
Ke y
MM001 93
SGML Tag TEI: MOA
Defin ition: Model of Applicability Code identifies a specific airframe or engine model to which
(1)procurement data for subject part applies,
(2) provisioning data in a transmitted "V" File applies,
(3) a repair quotation request (R1QTNREQ) or repair order placement(R1CPOXMT) applies,
(4) warranty data applies,
(5) consumption data applies or
(6) delivery configuration data for a subject part applies.
(7) for reliability applications use MOA to identify engine model of the aircraft.
Class: AN Remark:
Decimal :
Min_Length: 4
Max_Length: 4
Case_S ensitive: False
Busines s Rules: POS. 1-2 Airframe/Engine Manufacturer A(02)
POS. 3-4 Specific Airframe/Engine Model 9(02)
A maximum of 99 MOA TEI's may be specified for a given part number by a supplier in the Centralized Procurement Data File.
Manufacturers and suppliers not wishing to modelize procurement or consumption data will apply the generic code ZZ99.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Used by the Centralized Procurement Data System to determine which population of |
| | | |part numbers is accessible to a given airline. |
| | | |Contact the Air Transport Association of America for further information. |
| | | |For Provisioning applications refer to Provisioning Model Code. |
| | | |For consumption data the codes used in the procurement data system may be applied |
| | | |or alternatively specific codes may be agreed between supplier and customer. |
| | | |Used in Warranty Administration to identify a specific aircraft/engine type under |
| | | |warranty. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element |11 |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1QTNREQ |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 01 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 11 |
| MM | Record Type Code | Data Element | 20 |
| MM | Record Type Code | Data Element | 22 |
| MM | Record Type Code | Data Element | 26 |
| MM | Record Type Code | Data Element | 28 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
N a m e
OPERATING CYCLE COUNT
Ve r
1 2
Ke y
MM002 07
SGML Tag TEI:
Defin ition: Operating Cycle Count is the total number of operating cycles accumulated since the subject part was installed or since it was installed as new, last overhauled or , last repaired , last checked , or since last shop visit (as designated by the Time/Cycle Reference Code).
Class: N Remark:
Decima l:
Min_Le ngth: 1
Max_Le ngth: 6
Case_S ensitive: False
Busine ss Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to data set groups Serial Number Data Text (SND) or Total Time Text (TTM) |
| | | |for application. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element |11 |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|SERIAL NUMBER DATA TEXT | Data Set Group |
| TOTAL TIME TEXT | Data Set Group |
N a m e
OPERATING TIME
Ve r
1 2
Ke y
MM002 08
SGML Tag TEI:
Defin ition: Operating Time is the total number of operating flight hours accumulated since the subject part was installed or since it was installed as new, last overhauled or , last repaired , last checked , or since last shop visit (as designated by the Time/Cycle Reference Code).
Class: N Remark:
Decima l:
Min_Le ngth: 1
Max_Le ngth: 6
Case_S ensitive: False
Busine ss Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to data set groups Serial Number Data Text (SND) or Total Time Text (TTM) |
| | | |for application. |
|USES | |
|Applicati on Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element |11 |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|SERIAL NUMBER DATA TEXT | Data Set Group |
| TOTAL TIME TEXT | Data Set Group |
N a m e
OPERATOR CODE
Ve r
1 2
Ke y
MM002 09
SGML Tag TEI: OPR
Defin ition: Operator Code identifies the airline actually using the subject part submitted for repair where the airline is not the customer submitting the part for repair or warranty.
For reliability applications Operator Code identifies the airline actually operating the aircraft from which the LRU was removed.
Class: AN Remark:
Decima l:
Min_Le ngth: 3
Max_Le ngth: 5
Case_S ensitive: False
Busine ss Rules: As specified by the International Air Transport Association (IATA) Airline Coding Directory.
For reliability applications use the ICAO 3-digit airline designator. Code ZZZZZ for operators who have no ICAO designator, i.e. bizjet operators (name of the operator must then be sent).
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
N a m e
OVERLENGTH PART NUMBER
Ve r
1 2
Ke y
MM002 23
SGML Tag TEI: OPN
Defin ition: Overlength Part Number identifies a complete part identity exceeding fifteen positions in length.
Class: AN Remark: Fixed Record Character Length: 26
Class : AN
COBOL Picture : X(26)
Decima l:
Min_Le ngth: 16
Max_Le ngth: 32
Case_S ensitive: False
Busine ss Rules:
Provisioning S/T File Format - Explanation Code 11 (EC11) Text
Explanation Text Counter 01
POS. 01-26 Overlength Part Number (P/N POS 01-26) X(26)
Explanation Text Counter 02 (when required)
POS. 01-26 Overlength Part Number (P/N POS 27-32) X(06)
POS. 07-26 Filler (Spaces) X(20)
Prov. V File, Info/Data Exchange, Delivery Config. Data & Procmt.
Planning, Reliability applications TEI format - OPN
Overlength Part Number (Complete) X(16) to X(32)
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | The Part Number field for the subject overlength number contains a unique|
| | | |reference number(15 positions maximum) which is used as the part number |
| | | |for Spec 2000 processing. |
| | | |Refer to Part Number for definition and structure. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element |11 |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | W1CDNXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 03 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 29 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
N a m e
PART NUMBER
Ve r
1 2
Ke y
MM002 28
SGML Tag TEI: PNR
Defin ition: Part Number is the manufacturer's, supplier's or industry standard identity for the subject part, assembly, kit or material item. Part Number when linked with its Manufacturer Code provides a unique identity for the given item.
Class: AN Remark: Fixed Record Character Length: 15
Class : AN
COBOL Picture : X(15)
Decimal:
Min_Le ngth: 1
Max_Le ngth: 15
Case_S ensitive: False
Busine ss Rules: 1.Each alpha "O" appearing in the part number will be replaced by a numeric zero.
2. Blank spaces and/or special characters separating two numeric characters will be replaced by a single dash (-) and closed up as necessary.
3. Blank spaces and/or special characters not separating two numeric characters will be eliminated and closed up.
4. Part Numbers are not to exceed 15 characters in length. Established part numbers exceeding 15 characters will be changed to conform with the 15 character limit.
5. When an item lacks a part number, or when a part number cannot be reduced to fifteen characters, a unique reference number will be assigned to the Part Number field. This number will be used as the Part Number for all Spec 2000 processing. The complete, overlength Part Number will be stated in the corresponding Explanation Code 11 text in Provisioning fixed format applications and TEI "OPN" for Procurement Planning and Provisioning variable format applications and reliability applications.
6. The dash (-) is the only special character permitted in the
Part Number (reference number) field, however the dash (-) is not allowed as the last position of a part number.
7. For reliability applications, code ZZZZZ if submitting Airline Stock Number-ASN: operator part number- (RLS, NHS, ILS, RCS, SUS segments) or if submitting Additional Descriptive Text-ADT: part name- (WPS, RPS segments) when PNR not sent.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Applies to S and T files. |
| | | |Applies to reliability applications. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 10 |
| MM | Chapter | Data Element | 12 |
| MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 3 |
| MM | Chapter | Data Element | 4 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 8 |
| MM | Chapter | Data Element | 9 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | A1ADDPRT |
| MM | Command Code | Data Element | A1CHANGE |
| MM | Command Code | Data Element | A1QTYDEC |
| MM | Command Code | Data Element | A1QTYINC |
| MM | Command Code | Data Element | A1QUOTES |
| MM | Command Code | Data Element | A1STOCKS |
| MM | Command Code | Data Element | A1UPDATE |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | R1CDBACK |
| MM | Command Code | Data Element | R1CDBINQ |
| MM | Command Code | Data Element | R1CDBRSP |
| MM | Command Code | Data Element | R1CDBUPD |
| MM | Command Code | Data Element | R1CPORSP |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1CUSSHP |
| MM | Command Code | Data Element | R1DSPXMT |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | R1INVACK |
| MM | Command Code | Data Element | R1INVXMT |
| MM | Command Code | Data Element | R1INXACK |
| MM | Command Code | Data Element | R1INXXMT |
| MM | Command Code | Data Element | R1MATRCP |
| MM | Command Code | Data Element | R1PNRINQ |
| MM | Command Code | Data Element | R1PNRRSP |
| MM | Command Code | Data Element | R1QTNINT |
| MM | Command Code | Data Element | R1QTNREQ |
| MM | Command Code | Data Element | R1QTNXMT |
| MM | Command Code | Data Element | R1SPLSHP |
| MM | Command Code | Data Element | S1BOOKED |
| MM | Command Code | Data Element | S1INVEXC |
| MM | Command Code | Data Element | S1NVOICE |
| MM | Command Code | Data Element | S1ORDEXC |
| MM | Command Code | Data Element | S1PNSTAT |
| MM | Command Code | Data Element | S1POSTAT |
| MM | Command Code | Data Element | S1QUOTES |
| MM | Command Code | Data Element | S1SHIPPD |
| MM | Command Code | Data Element | S1STOCKS |
| MM | Command Code | Data Element | W1CDNXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 02 |
| MM | Record Type Code | Data Element | 03 |
| MM | Record Type Code | Data Element | 04 |
| MM | Record Type Code | Data Element | 05 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 17 |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 24 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 29 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Reference Document | Data Element | UN/EDIFACT Implementation Convention |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|APPROVED MATERIAL DETAIL TEXT | Data Set Group |
| MATERIAL USED TEXT | Data Set Group |
| USED ON ASSEMBLY PART NUMBER TEXT | Data Set Group |
N a m e
PART REMOVAL DATE
Ve r
1 2
Ke y
MM002 34
SGML Tag TEI: RED
Defin ition: Part Removal Date is the date the customer removed the subject part for cause.
Class: N Remark:
Decima l:
Min_Le ngth: 6
Max_Le ngth: 6
Case_S ensitive: False
Busine ss Rules: DD MM YY 99 99 99
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | For reliability applications it is the calendar date a component |
| | | |was removed from an aircraft during an airline maintenance activity.|
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
N a m e
PART SERIAL NUMBER
Ve r
1 2
Ke y
MM002 35
SGML Tag TEI: SER
Defin ition: Part Serial Number is the manufacturer's serialized identity for an individual part, component or component end item.
Class: AN Remark:
Decima l:
Min_Le ngth: 1
Max_Le ngth: 15
Case_S ensitive: False
Busine ss Rules: The dash (-) is the only special character permitted in the Part Serial Number field, however the dash (-) is not allowed as the last position of a Part Serial Number.
For reliability applications, code ZZZZZ if submitting Unique Component Identification Number-UCN-(operator serial number) when SER not sent.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 12 |
| MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 9 |
| MM | Chapter | Data Element |11 |
| MM | Command Code | Data Element | A1STOCKS |
| MM | Command Code | Data Element | A1UPDATE |
| MM | Command Code | Data Element | R1CPOINQ |
| MM | Command Code | Data Element | R1CPORSP |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1DSPXMT |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | R1PNRINQ |
| MM | Command Code | Data Element | R1PNRRSP |
| MM | Command Code | Data Element | R1SPLSHP |
| MM | Command Code | Data Element | W1CDNXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 22 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 28 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Chapter | Data Element | 2 |
| MM | Command Code | Data Element | A1ADDPRT |
| MM | Command Code | Data Element | P1PDINQY |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|MULTIPLE SERIAL NUMBER TEXT | Data Set Group |
| SERIAL NUMBER DATA TEXT | Data Set Group |
N a m e
REASON FOR REMOVAL CLARIFICATION TEXT
Ve r
1 2
K ey
MM002 74
SGML Tag TEI: RET
Definition: 1. Reason for Removal Clarification Text is a removal reason not accommodated by Reason for Removal Code.
2. For reliability applications, when the Removal Type Code is "O" (other), Reason for Removal Clarification Text can be used to define the nature of an "other" removal (ex: convenience, robbery, ….).
Class: AN Remark:
Decima l:
Min_L ength: 1
Max_L ength: 64
Case_S ensitive: False
Busine ss Rules: Each occurrence in a message is transmitted as a separate line starting with the TEI"RET" and ending with "/(CRLF)", or, if the last line, "(CRLF)" only.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Reason for Removal Clarification Text can be used in combination with Reason for |
| | | |Removal Codes other than ZZ by mutual agreement between trading partners. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Name
RECORD TYPE CODE
Ve r
2 3
Ke y
MM002 81
SGML Tag TEI : RTC
Definiti on: Record Type Code identifies the format of each Provisioning or Procurement Data record transmitted on magnetic tape or Repair Agency Data file transmission.
For Reliability Applications, Record Type Code identifies the format of each record to be exchanged between parties.
Class: N Remark: Fixed Record Character Length: 02
Class : N
COBOL Picture : 9(02)
Decimal:
Min_Length : 2
Max_Lengt h: 2
Case_Sensitive: False
Business Rules:
|APPLICATION AREAS |
| Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 8 |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 01 |
| MM | Record Type Code | Data Element | 02 |
| MM | Record Type Code | Data Element | 03 |
| MM | Record Type Code | Data Element | 04 |
| MM | Record Type Code | Data Element | 05 |
| MM | Record Type Code | Data Element | 06 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 08 |
| MM | Record Type Code | Data Element | 11 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 16 |
| MM | Record Type Code | Data Element | 17 |
| MM | Record Type Code | Data Element | 20 |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 22 |
| MM | Record Type Code | Data Element | 23 |
| MM | Record Type Code | Data Element | 24 |
| MM | Record Type Code | Data Element | 26 |
| MM | Record Type Code | Data Element | 27 |
| MM | Record Type Code | Data Element | 28 |
| MM | Record Type Code | Data Element | 29 |
| MM | Record Type Code | Data Element | 31 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 99 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Record Type Code | Data Element | 36 |
|PERMITTED VALUES |
| Permitted Value | Se q # | Def ault | Description |
|20 | | F |Information/Data Exchange Fleet Record - Customer to Supplier |
|02 | | F |S/T File Provisioning Part Number Record Fixed (PNRF) |
|03 | | F |S/T File Provisioning Part Number Record Variable (PNRV) |
|04 | | F |S/T File Provisioning Application Data Record Fixed(ADRF) |
|05 | | F |S/T File Provisioning Application Data Record Variable(ADRV) |
|06 | | F |Procurement Data Header Record - Procurement Data |
|07 | | F |Procurement Data Part Number Record |
|08 | | F |Discount Matrix Table Record |
|11 | | F |V File Provisioning Header Record |
|12 | | F |V File Provisioning Data Record |
|01 | | F |S/T File Provisioning Header Record (HR) |
|17 | | F |Central Repair Data Part Number Record |
|29 | | F |M File Detail Record |
|21 | | F |Information/Data Exchange Part Number Header Record - Customer To Supplier |
|22 | | F |Information/Data Exchange Part Number Detail Record - Customer To Supplier |
|23 | | F |Information/Data Exchange Header Record - Supplier To Customer |
|24 | | F |Information/Data Exchange Part Number Record - Supplier To Customer |
|26 | | F |Delivery Configuration Data Header Record To Customer |
|27 | | F |Delivery Configuration Data Part Number Record To Customer |
|31 | | F |Procurement Contract Parts File Header Record - Supplier to Customer |
|32 | | F |Procurement Contract Parts File Detail Record - Supplier to Customer |
|99 | | F |Procurement Data Header Record - Discount Matrix Table |
|28 | | F |M File Header Record |
|16 | | F |Central Repair Data Header Record |
|33 | | F |LRU Removal Record |
|34 | | F |Shop Findings Record |
|35 | | F |Piece Part Record |
|36 | | F |Aircraft Hours and Landings Record |
ALIAS
N a m e
REMOVAL STATION CODE
Ve r
1 2
K ey
MM002 86
SGML Tag TEI: RST
Defin ition: Removal Station Code is the location where the subject part was removed.
Class: A Remark:
Decimal:
Min_L ength: 3
Max_L ength: 3
Case_S ensitive: False
Busine ss Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Used in reliability applications to identify commercial and military airports. The|
| | | |codes are assigned by the International Air Transport Association (IATA), or other |
| | | |station identifier if no IATA standard code exists. For the purpose of reliability,|
| | | |this is the station where the discrepancy was recorded. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
ALIAS
N a m e
REPAIR LOCATION CODE
Ve r
1 2
K ey
MM002 93
SGML Tag TEI: RLC
Defin ition: Repair Location Code identifies the location of the repair site where a repairing agency has multiple sites for repair and overhaul or where the repair site is different from the location specified by the Supplier Code in the purchase order.
Class: AN Remark:
Decima l:
Min_L ength: 1
Max_L ength: 5
Case_S ensitive: False
Busine ss Rules: As specified by the repair agency.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 7 |
|MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1CUSSHP |
| MM | Command Code | Data Element | R1QTNXMT |
| MM | Record Type Code | Data Element | 34 |
ALIAS
N a m e
REPAIR PROCESS CODE
Ve r
1 2
K ey
MM002 95
SGML Tag TEI: RPC
Defin ition: Repair Process Code specifies the applicable types of repair for a subject part.
Class: AN Remark:
Decima l:
Min_L ength: 1
Max_L ength: 5
Case_S ensitive: False
Busine ss Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | The alpha codes will be edited so that only those found above are considered valid. |
| | | |The numeric codes referencing specific tasks in the repairing agency's Repair Catalog|
| | | |may be used in lieu of the above alpha generic codes. |
| | | |It is invalid to combine alpha and numeric codes. |
| | | |For the Central Repair Data Base, the allowable maximum is 50 occurrences per Part |
| | | |Number(PNR). |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 8 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | R1CDBRSP |
| MM | Command Code | Data Element | R1CDBUPD |
| MM | Command Code | Data Element | R1CPORSP |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | R1INVXMT |
| MM | Command Code | Data Element | R1PNRRSP |
| MM | Command Code | Data Element | R1QTNREQ |
| MM | Command Code | Data Element | R1QTNXMT |
| MM | Record Type Code | Data Element | 17 |
| MM | Record Type Code | Data Element | 34 |
|PERMITTED VALUES |
| Permitted Value | S e q # | D ef au lt | Description |
|X | | F |Exchange Unit |
|U | | F |Unrepairable |
|T | | F |Test |
|S | | F |See Remarks |
|R | | F |Repair |
|P | | F |Partial Repair |
|O | | F |Overhaul/Heavy Repair |
|M | | F |Modification |
|L | | F |Shelf Life Renewal |
|E | | F |Estimate |
|C | | F |Calibration |
|B | | F |Beyond Economic Repair |
|A | | F |Special Agreement |
ALIAS
N a m e
REPORT PERIOD DATE
Ve r
1 2
K ey
MM003 05
SGML Tag TEI: RDT
Defin ition: Report Period Date specifies the end of the monthly Consumption Period being reported.
Class: N
Remark:
Decimal:
Min_Length: 6
Max_Length: 6
Case_S ensitive: False
Busine ss Rules:
POS. 01-02 Month 9(02)
POS. 03-06 Year 9(04)
|APPLICATION AREAS |
| Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 5 |
|MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 20 |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 23 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Name
SEGMENT IDENTIFIER CODE
Ve r
1 2
Ke y
MM003 16
SGML Tag TEI : SEG
Definiti on: Segment Identifier Code identifies each section within a variable formatted, Provisioning V-File record. For reliability applications Segment Identifier Code identifies each section within LRU Removal Record, Shop Findings Record, and Piece Part Record.
Class: A Remark:
Decimal:
Min_Length : 3
Max_Lengt h: 3
Case_Sensitive: False
Business Rules:
|APPLICATION AREAS |
| Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to Chapter 1 or Chapter 11 for segment structure. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
|MM | Chapter | Data Element | 11 |
|MM | Record Type Code | Data Element | 12 |
|MM | Record Type Code | Data Element | 33 |
|MM | Record Type Code | Data Element | 34 |
|MM | Record Type Code | Data Element | 35 |
|PERMITTED VALUES |
| Permitted Value | Se q # | Def ault | Description |
|PNS | | F |Part Number Segment. Details the identity of the subject part plus that information |
| | | |remaining constant regardless of application or supplier. |
|PDS | | F |Procurement Data Segment. Details procurement data information for the subject part and |
| | | |specified supplier. |
|LMS | | F |Line Maintenance Segment. Details the maintenance aspects of the subject part at a specific|
| | | |location (Catalog Sequence Number) in the IPC for a given aircraft or engine. |
|EIS | | F |End Item Segment. Details the identity and related constant information for an end item in|
| | | |which the subject part is a component. |
|CBS | | F |Component Breakdown Segment. Details a Catalog Sequence Number and related application |
| | | |data for a specific location of the subject part in the Component Maintenance Manual (CMM) |
| | | |for a given end item. |
|RLS | | F |Removed LRU Segment. Details the various elements that allow to fully identify the part |
| | | |that has been removed from the aircraft. A RLS segment will be provided in each LRU Removal|
| | | |Record and in each Shop Finding Record. |
|NHS | | F |Next Higher assembly Segment. Details the various elements that allow to fully identify |
| | | |the next higher assembly of either the part that has been removed from the aircraft (LRU |
| | | |Removal Record) or the worked piece part (Piece Part Record). The entire segment is |
| | | |optional in both records. |
|ILS | | F |Installed LRU Segment. Details the various elements that allow to fully identify the part |
| | | |that has been installed on the aircraft to replace the removed LRU (LRU Removal Record). |
| | | |The entire segment is optional. |
|RCS | | F |Received LRU Segment. Details the various elements that allow to fully identify the part |
| | | |that has been received in the shop for repair. A RCS segment will be provided in each Shop |
| | | |Finding Record. |
|SUS | | F |Shipped Unit Segment. Details the various elements that allow to fully identify the part |
| | | |that has been shipped out of the shop after repair. A SUS segment will be provided in each |
| | | |Shop Finding Record. |
|SAS | | F |Shop Action Details Segment. Details the various elements that allow to identify the work |
| | | |and actions performed in the shop during repair of the unit. A SAS segment will be provided|
| | | |in each Shop Finding Record. |
|WPS | | F |Worked Piece Part Segment. Details the various elements that allow to fully identify the |
| | | |piece part that has been worked in the shop during repair. A WPS segment will be provided |
| | | |in each Piece Part Record. |
|RPS | | F |Replaced Piece Part Segment. Details the various elements that allow to fully identify the |
| | | |piece part that has been replaced in the shop during repair. A RPS segment will be provided|
| | | |in Piece Part Record. The entire segment is optional. |
ALIAS
N a m e
SUPPLIER CODE
Ve r
1 2
K ey
MM003 54
SGML Tag TEI: SPL
Defi niti on: Supplier Code identifies:
a) The originator of Procurement Data and a source of supply for the subject part in Procurement Planning, Provisioning V File and Delivery configuration Data applications.
b) The actual supply source for the subject part in Order Administration, Invoicing and Information/Data Exchange transactions.
c) The repair agency for the subject part in Repair Administration transactions.
d) The lister of the AIRS material(generated from AIRS owner code) in P1PDINQY.
e) The organization assigning a Unique Component Identification Number (UCN), where the organization is not the manufacturer, government agency, or other organization controlling the design of the serialized component.
f) The organization reporting LRU removal record, shop finding record, piece part record, or aircraft hours and landings record in reliability applications.
Class: AN Remark: Fixed Record Character Length: 05
Class : AN
COBOL Picture : X(05)
Decima l:
Min_L ength: 5
Max_L ength: 5
Case_ Sensitive: False
Busine ss Rules: For reliability Applications code ZZZZZ if reporting organization has no cage code ; transmission of Reporting Organization Name (RON) is then required.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to Manufacturer Code for structure. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 1 |
| MM | Chapter | Data Element | 10 |
| MM | Chapter | Data Element | 12 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 3 |
| MM | Chapter | Data Element | 4 |
| MM | Chapter | Data Element | 5 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element | 8 |
| MM | Chapter | Data Element | 9 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | A1CNTACT |
| MM | Command Code | Data Element | P1ADVISE |
| MM | Command Code | Data Element | P1CNTACT |
| MM | Command Code | Data Element | P1DISUPD |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Command Code | Data Element | P1UPDATE |
| MM | Command Code | Data Element | R1ADVISE |
| MM | Command Code | Data Element | R1CDBACK |
| MM | Command Code | Data Element | R1CDBINQ |
| MM | Command Code | Data Element | R1CDBRSP |
| MM | Command Code | Data Element | R1CDBUPD |
| MM | Command Code | Data Element | R1CNTACT |
| MM | Command Code | Data Element | R1CPOACK |
| MM | Command Code | Data Element | R1CPOINQ |
| MM | Command Code | Data Element | R1CPORSP |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1CUSSHP |
| MM | Command Code | Data Element | R1DSPACK |
| MM | Command Code | Data Element | R1DSPXMT |
| MM | Command Code | Data Element | R1EXCACK |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | R1INVACK |
| MM | Command Code | Data Element | R1INVXMT |
| MM | Command Code | Data Element | R1INXACK |
| MM | Command Code | Data Element | R1INXXMT |
| MM | Command Code | Data Element | R1MATRCP |
| MM | Command Code | Data Element | R1PNRINQ |
| MM | Command Code | Data Element | R1PNRRSP |
| MM | Command Code | Data Element | R1QTNINT |
| MM | Command Code | Data Element | R1QTNREQ |
| MM | Command Code | Data Element | R1QTNXMT |
| MM | Command Code | Data Element | R1SPLSHP |
| MM | Command Code | Data Element | S1BOOKED |
| MM | Command Code | Data Element | S1CNTACT |
| MM | Command Code | Data Element | S1INVEXC |
| MM | Command Code | Data Element | S1NVOICE |
| MM | Command Code | Data Element | S1ORDEXC |
| MM | Command Code | Data Element | S1REJECT |
| MM | Command Code | Data Element | S1SHIPPD |
| MM | Record Type Code | Data Element | 06 |
| MM | Record Type Code | Data Element | 07 |
| MM | Record Type Code | Data Element | 08 |
| MM | Record Type Code | Data Element | 12 |
| MM | Record Type Code | Data Element | 16 |
| MM | Record Type Code | Data Element | 17 |
| MM | Record Type Code | Data Element | 21 |
| MM | Record Type Code | Data Element | 23 |
| MM | Record Type Code | Data Element | 26 |
| MM | Record Type Code | Data Element | 31 |
| MM | Record Type Code | Data Element | 32 |
| MM | Record Type Code | Data Element | 99 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Record Type Code | Data Element | 36 |
| MM | Reference Document | Data Element | UN/EDIFACT Implementation Convention |
ALIAS
N a m e
TIME/CYCLE REFERENCE CODE
Ve r
2 3
K ey
MM003 74
SGML Tag TEI:
Defi niti on: Time/Cycle Reference Code designates the operating time and cycles as those accumulated since a part was newly installed, last overhauled or , last repaired , last installed , last checked or last visited.
Class: A Remark:
Decim al:
Min_Length: 1
Max_Length: 1
Case_ Sensitive: False
Busine ss Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Refer to data set groups Serial Number Data Text (SND) or Total Time Text (TTM) for |
| | | |application. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 14 |
| MM | Chapter | Data Element | 15 |
| MM | Chapter | Data Element | 7 |
| MM | Chapter | Data Element |11 |
| MM | Command Code | Data Element | R1CPOXMT |
| MM | Command Code | Data Element | R1EXCXMT |
| MM | Command Code | Data Element | W1CLMXMT |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
|PERMITTED VALUES |
| Permitted Value | S e q # | D ef au lt | Description |
|R | | F |Time/Cycles accumulated since last repair |
|O | | F |Time/Cycles accumulated since last overhaul |
|N | | F |Time/Cycles accumulated since installation as a new part |
|I | | F |Time/Cycles accumulated since last installation of the part |
|C | | F |Time/Cycles accumulated since last check |
|V | | F |Time/Cycles accumulated since the engine was last in repair shop |
ALIAS
|GROUPS CONTAINING THIS ENTRY |
| Group Name | Group Type |
|SERIAL NUMBER DATA TEXT | Data Set Group |
| TOTAL TIME TEXT | Data Set Group |
N a m e
TOTAL TIME TEXT
Ve r
1 2
K ey
MM003 90
SGML Tag TEI: TTM
Defi niti on: Total Time Text is a data set group specifying the Operating Time, Operating Cycles and Time/Cycle Reference Code of a given application since repair, overhaul or, new , installation , check or visit.
Class: AN Remark:
Decim al:
Min_L ength: 5
Max_L ength: 15
Case_ Sensitive: False
Busine ss Rules: Operating Time 9(01) to 9(06)
Delimiter (Space) A(01)
Operating Cycle Count 9(01) to 9(06)
Delimiter (Space) A(01)
Time/Cycle Reference Code A(01)
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | TTM can have up to three six occurrences, one for each Time/Cycle Reference Code. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Set Group | 14 |
| MM | Chapter | Data Set Group | 15 |
| MM | Chapter | Data Set Group |11 |
| MM | Command Code | Data Set Group | W1CLMXMT |
| MM | Record Type Code | Data Set Group | 26 |
| MM | Record Type Code | Data Set Group | 27 |
| MM | Record Type Code | Data Set Group | 33 |
| MM | Record Type Code | Data Set Group | 34 |
ALIAS
|ENTRY IS A GROUP WHICH CONTAINS |
| GROUP TYPE: Data Set Group |
|Member Name | Ver # | Seq # |
|OPERATING TIME |1 2 |1 |
| OPERATING CYCLE COUNT |1 2 |2 |
| TIME/CYCLE REFERENCE CODE |1 2 |3 |
N a m e
UNIQUE COMPONENT IDENTIFICATION NUMBER
Ve r
1 2
K ey
MM003 97
SGML Tag TEI: UCN
Defi niti on: Unique Component Identification Number is the permanent tracking identity assigned to an in-service part in lieu of the manufacturer's serial number.
Class: AN Remark:
Decim al:
Min_L ength: 1
Max_L ength: 15
Case_ Sensitive: False
Busine ss Rules: The dash (-) is the only special character permitted in the Unique Component Identification number field, however the dash (-) is not allowed as the last position of the UCN.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | Used when retroactively bar-coding an in-service part. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|MM | Chapter | Data Element | 2 |
| MM | Chapter | Data Element | 9 |
| MM | Chapter | Data Element | 11 |
| MM | Command Code | Data Element | A1STOCKS |
| MM | Command Code | Data Element | A1UPDATE |
| MM | Chapter | Data Element | 12 |
| MM | Command Code | Data Element | A1ADDPRT |
| MM | Command Code | Data Element | P1PDINQY |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Section 2 : Modification of existing non Spec 2000 data elements
|CSDD DATA ELEMENT NAME |TEI |CSDD KEY |
|Aircraft_Model_Code |AMC |DM00032 MM 00x xx|
|Fault Code |FLT |TE00226 MM 00x xx|
|Geographic and/or Electrical Position |GEL |TE00277 MM 00x xx|
Nam e
AIRCRAFT_MODEL_CODE
Ve r
1 2
Ke y
DM000 32-MM00X XX
SGML Tag TEI : AMC
Definit ion: It is the code for an Aircraft Model. This code is given by the manufacturer and registered with the Airworthiness authorities. It uniquely identifies the entity. Examples of possible permitted values include; B767-300 (with P&W Engines), A320-211 (with CFM56-5A1 Engines), DHC8-102 (according performances)
Class: A Remark:
Decimal:
Min_Lengt h: 1
Max_Lengt h: 20
Case_Sens itive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|DM | SPEC 2100 - Ch 2 | CREATED | |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|DM | Subject Area | Attribute | AIRCRAFT |
|MM |Chapter |Data Element |11 |
|MM |Record Type Code |Data Element |33 |
|MM |Record Type Code |Data Element |34 |
|MM |Record Type Code |Data Element |36 |
ALIAS
Na me
Fault Code
Ve r
1 2
Ke y
TE0022 6-MM00X XX
SGML Tag FALTCODE TEI: FLT
Definit ion: An 8-digit alphanumeric code which uniquely identifies a fault listed in the FRM and FIM.
Class: AN Remark:
Decimal:
Min_Length: 8
Max_Length: 8
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|TE | SPEC 2100 - Ch 3 | | |
|MM |Spec 2000 | | Used in reliability applications LRU removal record to convey |
| | | |technical information about suspected problems on the aircraft |
| | | |recorded by the flight crew. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|TE | DTD | Element | FRMFIM |
|MM |Chapter |Data Element |11 |
|MM |Record Type Code |Data Element |33 |
ALIAS
Na me
Geographic and/or Electrical Location
Ve r
1 2
Ke y
TE0027 7-MM 00x xx
SGML Tag GEOLOC TEI: GEL
Definit ion: This tag is the geographical and/or electrical location of components on a circuit card or assembly given in alphanumeric coordinates. Alpha is vertical and numerical is horizontal. Refer to ATA Specification 100 2-5-2 for additional details.
Class: AN
Remark:
Decimal:
Min_Len gth: 1
Max_Len gth: 30
Case_Se nsitive: false
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|TE | SPEC 2100 - Ch 3 | | |
| MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
|TE | DTD | Element | CMM |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Section 3 : New data elements
|CSDD DATA ELEMENT NAME |TEI |CSDD KEY |
|Aircraft Cumulative Total Cycles |CTC |MM 00x xx |
|Aircraft Cumulative Total Flight Hours |CTH |MM 00x xx |
|Aircraft Message Text |AMT |MM 00x xx |
|Aircraft Monthly Total Cycles |MTC |MM 00x xx |
|Aircraft Monthly Total Flight Hours |MTH |MM 00x xx |
|Aircraft Registration Number |REG |MM 00x xx |
|Engine Position Code |EPC |MM 00x xx |
|Failed Piece Part Next Higher Assembly NHA Part Number |NPN |MM 00x xx |
|Incoming Inspection / Shop action Text |INT |MM 00x xx |
|Maintenance Action Text |MNT |MM 00x xx |
|Operator Aircraft Internal Identifier |OIN |MM 00x xx |
|Operator Event Identifier |OEI |MM 00x xx |
|Piece Part Failure Description |FDE |MM 00x xx |
|Piece Part Record Identifier |PPI |MM 00x xx |
|Primary Piece Part Failure Indicator |PFC |MM 00x xx |
|Related Shop Finding Record Identifier |RSI |MM 00x xx |
|Removal Reason Text |RMT |MM 00x xx |
|Removal Tracking Identifier |RTI |MM 00x xx |
|Removal Type Code |TYC |MM 00x xx |
|Reporting Organization Name |RON |MM 00x xx |
|Shipped Date |SHP |MM 00x xx |
|Shop Finding Record Identifier |SFI |MM 00x xx |
|Shop Findings Code |SFC |MM 00x xx |
|Shop Findings Text |FIT |MM 00x xx |
Na me
AIRCRAFT CUMULATIVE TOTAL CYCLES
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : CTC
Definition: Identifies the cumulative landings on the identified aircraft flown by the operator since entry into service.
Note : calculations begin after the delivery date.
Class: N Remark:
Decimal:
Min_Length: 1
Max_Length: 9
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
AIRCRAFT CUMULATIVE TOTAL FLIGHT HOURS
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : CTH
Definition: Identifies the cumulative flight hours on the identified aircraft flown by the operator since entry into service.
Note : calculations begin after the delivery date.
Class: N Remark:
Decimal:
Min_Length: 1
Max_Length: 9
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
AIRCRAFT MESSAGE TEXT
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : AMT
Definition: Text containing the comments relating to the aircraft message code.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1000
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
Na me
AIRCRAFT MONTHLY TOTAL CYCLES
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : MTC
Definition: Identifies the number of landings on the identified aircraft flown by the operator for the current month.
Note : calculations begin after the delivery date.
Class: N Remark:
Decimal:
Min_Length: 1
Max_Length: 6
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
AIRCRAFT MONTHLY TOTAL FLIGHT HOURS
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : MTH
Definition: Identifies the number of flight hours on the identified aircraft flown by the operator for the current month.
Note : calculations begin after the delivery date.
Class: N Remark:
Decimal:
Min_Length: 1
Max_Length: 6
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
AIRCRAFT REGISTRATION NUMBER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : REG
Definition: The registration number assigned to the aircraft by the local airworthiness regulatory agency, e.g. N123BG, G-ABCD, JA8158. The registration number is unique to an operator, country and time.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 8
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
ENGINE POSITION CODE
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : EPC
Definition: Identifies the engine install position on the aircraft. From the rear of the aircraft facing forward, pod positions are counted left to right. APU is designated with aircraft pod location = 8 or 9.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | Used in reliability applications when the removed LRU is|
| | | |an engine component. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
Na me
FAILED PIECE PART NEXT HIGHER ASSEMBLY NHA PART NUMBER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : NPN
Definition: Part number of the next higher assembly's next higher assembly.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 30
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
INCOMING INSPECTION/SHOP ACTION TEXT
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : INT
Definition: Text description of shop maintenance inspection findings. This can be used also for comments about shop activity.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1000
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Na me
MAINTENANCE ACTION TEXT
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : MNT
Definition: Text containing the details of a line maintenance action.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1000
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
Na me
OPERATOR AIRCRAFT INTERNAL IDENTIFIER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : OIN
Definition: The number assigned by an airline operator to identify a specific aircraft within their fleet.
Note : this number is internal to the particular operator that assigns the number.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 10
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM | Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
OPERATOR EVENT IDENTIFIER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : OEI
Definition: A number assigned by the operator identifying a specific occurrence of a complaint generated by an airline and recorded in a logbook (pilot, cabin, maintenance).
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 20
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
ALIAS
Na me
PIECE PART FAILURE DESCRIPTION
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : FDE
Definition: Full description of why this piece part was worked.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1000
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
PIECE PART RECORD IDENTIFIER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : PPI
Definition: Identifies in a unique way the piece part record.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 20
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
PRIMARY PIECE PART FAILURE INDICATOR
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : PFC
Definition: Is this piece part the primary defect/failure (or its cause)?
Class: A Remark:
Decimal:
Min_Length: 1
Max_Length: 1
Case_Sen sitive: False
Business Rules: Y/N/D
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
RELATED SHOP FINDING RECORD IDENTIFIER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : RSI
Definition: Identifies in a unique way the original Shop Finding Record. This could be were the earlier record is an LRU and this record is a SRU which was removed from that LRU , or both records could be for the same LRU repair when it is transferred to a second shop for final repair.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 20
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Na me
REMOVAL REASON TEXT
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : RMT
Definition: This attribute is the text explaining the reason a component was removed from an aircraft. It should indicate the observed fault in the operational environment (for example : PIREP).
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1000
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Na me
REMOVAL TRACKING IDENTIFIER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : RTI
Definition: Identifies in a unique way the LRU Removal Record and it can be used in Shop Finding and Piece Part records to link to original LRU removal.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 20
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
REMOVAL TYPE CODE
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : TYC
Definition: Removal Type Code identifies the type of maintenance mode (unscheduled ; scheduled ; other) the mechanics were operating in at the time that the complaint was addressed
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 1
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
|PERMITTED VALUES |
| Permitted Value | S eq # | D ef au lt | Description |
|U | | F |Unscheduled |
|S | | F |Scheduled |
|O | | F |Other |
ALIAS
Na me
REPORTING ORGANIZATION NAME
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : RON
Definition: The name of the company reporting the LRU removal record, shop finding record, piece part record, or aircraft hours and landings record in reliability applications.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 55
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | Used in reliability applications. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 33 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
| MM | Record Type Code | Data Element | 36 |
ALIAS
Na me
SHIPPED DATE
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : SHP
Definition: Shipped Date is the calendar date a component was shipped from shop inspection and repair and returned to service, scrapped, etc.
Class: N Remark:
Decimal:
Min_Length: 6
Max_Length: 6
Case_Sen sitive: False
Business Rules:
99 99 99 DAY MONTH YEAR
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Na me
SHOP FINDING RECORD IDENTIFIER
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : SFI
Definition: Identifies in a unique way the shop finding record.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 20
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 34 |
| MM | Record Type Code | Data Element | 35 |
ALIAS
Na me
SHOP FINDINGS CODE
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : SFC
Definition: This is a code of shop findings. These codes are defined by the data provider.
Class: AN Remark:
Decimal:
Min_Length: 1
Max_Length: 10
Case_Sen sitive: False
Business Rules:
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Element | 11 |
| MM | Record Type Code | Data Element | 34 |
ALIAS
Na me
SHOP FINDINGS TEXT
Ve r
1
Ke y
MM00x xx
SGML Tag TEI : FIT
Definition: Shop Findings Text Data Set Group identifies the technical findings of the shop when repairing the unit.
Class: AN Remark:
Decimal:
Min_Length: 12
Max_Length: 23
Case_Sen sitive: False
Business Rules: Reliability applications in Shop Findings Record
Inspection Findings Code Failure/Fault Found(FT) or not(NT) X(01) to X(03)
Delimiter (space) A(01)
Inspection Findings Code Failure/Fault Induced(IN) or not(NI) X(01) to X(03)
Delimiter (space) A(01)
Inspection Findings Code Failure/Fault Confirms Reason for Removal(CR) or not(NC) X(01) to X(03)
Delimiter (space) A(01)
Inspection Findings Code Failure/Fault Confirms Aircraft Message(CM) or not(NM) X(01) to X(03)
Delimiter (space) A(01)
Inspection Findings Code Failure/Fault Confirms A/C Part Bite message(CB) or not(NB) X(01) to X(03)
Delimiter (space) A(01)
Inspection Findings Code Hardware(HW) or Software(SW) Failure X(01) to X(03)
Use dash (-) when information is not transmitted except for the first data element (Failure/Fault Found or Not) where dash is not allowed. Positions specified above must be respected, i.e. the first data element must be FT or NT, the second must be IN or NI or -, etc.
|APPLICATION AREAS |
|Area | Application | Category | Remarks |
|MM |Spec 2000 | | Refer to Inspection Findings Code for definition and |
| | | |structure. |
|USES | |
|Application Area | Usage | Type | Specific Usage |
| MM | Chapter | Data Set Group | 11 |
| MM | Record Type Code | Data Set Group | 34 |
ALIAS
|ENTRY IS A GROUP WHICH CONTAINS |
| GROUP TYPE: Data Set Group |
|Member Name | Ver # | Seq # |
| INSPECTION FINDINGS CODE |1 2 |1 |
| INSPECTION FINDINGS CODE |1 2 |2 |
| INSPECTION FINDINGS CODE |1 2 |3 |
| INSPECTION FINDINGS CODE |1 2 |4 |
| INSPECTION FINDINGS CODE |1 2 |5 |
| INSPECTION FINDINGS CODE |1 2 |6 |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- rushmore loan modification package
- fha modification guidelines for servicers
- us bank loan modification application
- usda loan modification program
- bank of america home loan modification status
- honeywell generator 22kw
- honeywell air purifiers replacement filters
- honeywell ultraviolet light treatment system
- us bank loan modification package
- behavioral modification techniques
- hud loan modification payoff
- mortgage modification program 2020