Mpdv1 TSDF Spec

MPDS
MAGNETIC SUPPORT
A300
A310
A300-600
A318/A319/A320/A321
A330
A340
A350
A380
A400M
MPD
Task Structured Data File (TSDF)
Specification
Revision 06
Issue Apr 2018
Airbus Fleet MPD TSDF SPEC
Record of Revision
Version Revision 06
Date Apr 2018
Section Change(1) Reason for Revision
2 R Organization of Data – Supplementary Information added

7 R Example - adapted
(1)
: D = Deleted N=New R = Revised.
Reference: X03SP0501688
Issue Apr 2018
Page 2
MPD
SCOPE - ORGANIZATION OF DATA
TABLE OF CONTENTS
1- SCOPE
2- ORGANIZATION OF DATA
3- REVISION SERVICE
4- TECHNICAL CHARACTERISTICS
5- FILES AND RECORDS ORGANIZATION
6- FILES AND RECORDS DEFINITION SPECIFICATION
7- EXAMPLE
Issue Apr 2018
Page 3
Record of Revision
1- SCOPE
The Task Structured Data File (TSDF) is applicable to data from a Maintenance Planning Document
(MPD)
The TSDF enables the following to be carried out, provided that an applicable software is available:
- Load of all data into operators EDP environment (e.g. Maintenance Information System – MIS);
- Print of MPD data ;
- Update existing Planning Data
2- ORGANIZATION OF DATA
The data required for each task are contained in 4 files :
- File A contains Task Basic Data,

- File B contains Access and Preparation Data,
- File C contains Task Description Data,
- File D contains Reference Data,
R A task to be carried out in two or more zones, the task data (File A-D) is repeated for each zone.
N Files (File A to D) may contain several lines to distinguish different types of data.
N Files and lines are only displayed if data content is provided
Issue Apr 2018
Page 4
SCOPE - ORGANIZATION OF DATA
3- REVISION SERVICE
Reasons for revision :
- To incorporate changes resulting from developments in the maintenance program or in service

experience acquired by the operator.
The data is totally reissued at each revision.
The tasks which have been modified are identified by a movement code (see file A)
4- TECHNICAL CHARACTERISTICS
CD/DVD/Download
Format : txt
DATA : Task-Data-File of MPD
Issue Apr 2018
Page 5
REVISION SERVICE – TECHNICAL CHARACTERISTICS
5- FILES AND RECORDS - ORGANIZATION
A/C TYPE : X TASK IDENT N° : XXXXXXXXXXXXXXX ZONE : XXX
are included in each file.
FILE A contains basic data such as : nomenclature interval, skill, men, M/H,
etc ...
FILE B contains access data and preparation data such as : Σ M/H,

Identifier N° 1, Identifier N° 2 ... Identifier N° n
contains Task description data

FILE C
contains data such as : Amtoss ID, reference document IDs,

FILE D MRBR Reference, ALI Reference, …
Format :
X (n) = n alphanumeric characters

9 (n) = n numeric characters
[9 (X)]*n = n possible occurrences for this data
Issue Apr 2018
Page 6
FILES AND RECORDS - ORGANIZATION
6- FILES AND RECORD DEFINITION
6.1 - File A
6.10 - Data Field Description –Key data
Aircraft Type : X (1)
“A” will be shown as default.

Code identifying the type of aircraft to which the task applies, if required to distinguish
between different A/C Types refer to table below.
1 ^ A300
2 ^ A310
3 ^ A300-600
4 ^ A318/A319/A320/A321
5 ^ A350 ;
6 ^ A330
7 ^ A340
8 ^ A380
M ^ A400M
Task Number : X (21)
Identifies each separate task.
Zone : 9 (3)
Zone in which the task is mainly performed.
Line sequence N°: 9 (2)
Line Sequence Number of data presented

For EDP use only:
File A : 00 Basic Data
10 Event Data (Standard only), not supported from 2016
20 Operators MSN
30 MPD task applicability
40-64 Structured Event Data
6.11 - File A Line 00
6.111 - Data Field Description File A Line 00
Task Code : X (3)
Mnemonic code defining the type of task to be carried out.
Skill : X (3)
Code specifying the type of skill required for task accomplishment e.g. MEC, ERI,
ENG, etc.
Issue Apr 2018
Page 7
FILES AND RECORD DEFINITION
M/H : 9(2).9(2)
Manpower, per skill/zone, required for task accomplishment.
Men : 9 (1)
Number of men per skill, required for task accomplishment.
Source Document : [X (10)*6]
Source document indication of the task

e.g. MRB 5 = Maintenance Review Board
Document MSG-Route 5
(Failure Effect Cat. 5)
ISB = Inspection Service Bulletin
Time Controlled Item Marker : X(1)
TCI markers are set in order to provide assistance in planning removable assets
installed on the A/C. See MPD General Introduction
Marker: ‘Y’
Corrosion Prevention and Control Program (CPCP) Marker : X(1)
Task which are part of the CPCP are marked with ‘C’
Marker: ‘C’ ‘
Temporary Protection System (TPS) : X(4)
Indicates the Type and Grade of TPS to be applied

TPS: ‘-’ or ‘1’ or ‘1+2‘ or ‘2‘ or ‘3’ or ‘NO’
Nomenclature : X (120)
Task title giving the designation of system/subsystem/component/zone/structural

Significant item affected by the task.
Movement code : X (1)
Revision marker related to previous issue

Code "N" if the task is new, "R" if task is revised.
Issue : X (10)
Issue date e.g. APR 13/05
Section : X (1)
Program Section Identifier e.g. 3
Issue Apr 2018
Page 8
6 - FILES AND RECORDS SPECIFICATION
Key data are identified by an asterisk.
6.112 - Table Definition File A Line 00
SEQ BYTE LENGTH DATA FORMAT Example
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*03 023 01 File identification ^A
*04 024 03 Zone 9 (3)
*05 027 02 Line 9 (2) ^ 00
06 029 03 Task Code X (3) FUC, …
07 032 03 Skill X (3) MEC, ERI, …
08 035 05 M/H 9 (2) . 9 (2) 10.50
09 040 01 MEN 9 (1)
10 041 60 Source Data [X(10)] *6 MRB 6
11 101 01 Time Controlled Item Marker X(1) Y or ‘ ‘
12 102 01 CPCP Marker X(1) C or ‘ ‘
13 103 04 Temporary Protection System X(4) 1,1+2,NO, …
14 107 120 Nomenclature X(120)
15 227 01 Movement code X (1) N, R
16 228 10 Issue X (10) DEC 30/05
17 238 1 Section X (1) 3
Issue Apr 2018
Page 9
6- FILES AND RECORDS DEFINITION

This record will be delivered for a transition period in 2013-2014
This record will not be supported beyond 2015
Following ‘Periobox’ Data fields concerning Interval, Threshold, Limit, Sample Interval,
Sample Threshold are structured as follows:
Each Periobox Type : [ X (9) ] * 4

The dimension is placed on digit 8 and 9 (17-18, 26-27)
The value is placed on digit 1-6 (10-16,19-24)
Free text information is not structured
1 2 3
1 5 0 5 0 5 0 5
123456789123456789123456789123456789
_____2_A_
_20000_FH__5000_CY_____2_YE
__ENG_CHG____OR_____NOTE_1___NOTE_2_
Interval/unit : [ X (9) ] * 4
Specific value of an operational parameter.

(FH, CY, EH, etc) or of a letter code defining the maximum time that can separate two
complete accomplishments of the task.
e.g. - 2 A
- 20000 FH 10000 CY (Read: 20000 FH OR 10000 CY whichever comes first)
Threshold/Unit : [X (9)] * 4
Specific value of an operational parameter (FH, CY, EO, EH, LG, etc) or of a letter
code defining the first accomplishment/deadline of the task.
e.g. – see above (Interval)
Sample Interval/unit : [ X (9) ] * 4

(FH, CY, EH, etc) defining the maximum time that can separate two complete
accomplishments of the task for the selected sample A/C.
e.g. 20000 FH 10000 CY (Read: 20000 FH OR 10000 CY whichever comes first)
Sample Threshold/Unit : [X (9)] * 4
Specific value of an operational parameter (FH, CY, EO, EH, LG, etc) defining the first
accomplishment/deadline of the first accomplishment deadline of the task for the
selected sample A/C.
Issue Apr 2018
Page 10
e.g. – see above (Sample Interval)
Sample (percent) : 9 (4)
Proportion of the aircraft fleet to be inspected at Sample Threshold and following

Sample Interval of an associated task.
e.g. 20 %
Limit/Unit : [X (9)] * 2
Specific value of an operational parameter (FH, CY, EH, LG,

etc) which indicates the 100% limit at which point the Sampling
Program finishes. If the Limit is expressed in two or three terms, the
limit which is reached first applies.
Fatigue Rating : 9(1).9(2) applicable for WB A/C
e.g. 0.13
Indicates the level of fatigue sensitivity for fatigue related SSIs.
Low Utilization Recommendation : X (3)
The MPD provides additional calendar time interval values called “Low
Utilization Recommendation” (LUR) in order to allow operator’s airplane utilization below
the range stated in the MRBR. Each MPD task, where a calendar time value has been
added for this purpose, is provided with an additional “LUR” marker in the source column.
The calendar time value represents the time, which would be reached with a utilization of
1800 FH/YE, or 1000 FC/YE, whatever will result to the lower time value. This is to ensure
that the time between two consecutive inspections on a “Low Utilization Aircraft” will not
be higher than on an aircraft that is operated at the lower limit of the utilization range in
accordance with the MRBR.
Issue Apr 2018
Page 11
This record will be delivered for a transition period in 2013-2014

This record will not be supported beyond 2015
Key data are identified by an asterisk
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*04 024 03 Zone 9 (3)
*05 027 02 Line 9 (2) ^ 10
06 029 36 Interval/Unit [X(9)] *4 2000 FH
07 065 36 Threshold [X(9)] *4 10000 FH
08 101 36 Sample Interval/Unit [X(9)] *4 8000 FC
09 137 36 Sample Threshold [X(9)] *4 20000 FC
10 173 03 Sample % X (4) 20%
11 176 36 Limit [X(9)] * 4 15000 FH
12 212 04 Fatigue Rating 9(1).9(2) 0.13
13 216 03 Low Utilization Recommendation X (3) LUR
Issue Apr 2018
Page 12
A/C - S/N : [9 (4)] *n
Aircraft manufacturers serial number (MSN) to which the task is applicable.

e.g. ALL = valid for all A/C - S/N of an
A/C-Type
or
e.g. 0009001200130015 = valid only for these
certain A/C - S/N
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*04 024 03 Zone 9 (3)
*05 027 02 Line 9 (2) ^ 20-29
06 029 220 A/C-S/N [9 (4)] *55 0231
Issue Apr 2018
Page 13
A/C - S/N : [X (15)] *n
MPD Task Effectivity expression.

e.g. ALL = valid for all A/C - S/N of a
A/C-Type
or
e.g. POST 44430 = valid only for those A/C - S/N of this
A/C-TYPE where Mod 44430 is
embodied
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*04 024 03 Zone 9 (3)
*05 027 02 Line 9 (2) ^ 30-39
06 029 210 Effectivity [9 (15)] *14 POST 44430
Issue Apr 2018
Page 14
6.15 - File A Lines 40-44, 51-54, 61-64
6.151 - Data Field Description File A Lines 40-44, 51-54, 61-64

These records will be the standard formats for all Event data
Event marker
Line 40 : LUR Marker
Event data grouped by:
Lines 41-44 : Standard Event Data
Lines 51-54 : FH Optimized Event Data
Lines 61-64 : FC Optimized Event Data
Event Type
Line 41, 51, 61 : 100% Interval
Line 42, 52, 62 : 100% Threshold
Line 43, 53, 63 : Sample Interval
Line 44, 54, 64 : Sample Threshold
Event Data are structured as follows:
Each Event Type : [ X (13) ] * 10

The dimension is placed on digit 8-13 (21-26, 34-39, ….)
The value is placed on digit 1-6 (14-19, 27-32, …)
Free text information is not structured
1 2 3 4 5 6
1 5 0 5 0 5 0 5 0 5 0 5 0...
123456789012345678901234567890123456789012345678901234567890...
2400 FH NOTE 15
42 DY OR NR NOTE 1
48 MO OR 3000 FC OR 30000 FH
Interval/unit : [ X (13)]

(FH, CY, EH, etc) or of a letter code defining the maximum time that can separate two
complete accomplishments of the task.
e.g. 2 A
3000 FC OR 30000 FH OR 10 YE
1500 ACT FC
NOTE 1 VR
Threshold/Unit : [X (13)]
Specific value of an operational parameter (FH, CY, EO, EH, LG, etc) or of a letter
code defining the first accomplishment/deadline of the task.
Sample Interval/unit : [ X (9)]
Issue Apr 2018
Page 15

(FH, CY, EH, etc) defining the maximum time that can separate two complete
accomplishments of the task for the selected sample A/C.
Sample Threshold/Unit : [X (9)]
Specific value of an operational parameter (FH, CY, EO, EH, LG, etc) defining the first
accomplishment/deadline of the first accomplishment deadline of the task for the
selected sample A/C.
Low Utilization Recommendation : X (3)
The MPD provides additional calendar time interval values called “Low
Utilization Recommendation” (LUR) in order to allow operator’s airplane utilization below
the range stated in the MRBR. Each MPD task, where a calendar time value has been
added for this purpose, is provided with an additional “LUR” marker in the source column.
The calendar time value represents the time, which would be reached with a utilization of
1800 FH/YE, or 1000 FC/YE, whatever will result to the lower time value. This is to ensure
that the time between two consecutive inspections on a “Low Utilization Aircraft” will not
be higher than on an aircraft that is operated at the lower limit of the utilization range in
accordance with the MRBR.
Issue Apr 2018
Page 16
6.152 - Table Definition File A Line 40 - Line 44 – Standard Event Data
Key data are identified by an asterisk in Column SEQ
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*04 024 03 Zone 9 (3)
Line 40
*05 027 02 Line 9 (2) ^ 40
13 029 03 Low Utilization Recommendation X (3) LUR
Line 41
*05 027 02 Line 9 (2) ^ 41
Line 42
*05 027 02 Line 9 (2) ^ 42
06 029 130 Threshold [X(13)] *10 10000 FH
Line 43
*05 027 02 Line 9 (2) ^ 43
Line 44
*05 027 02 Line 9 (2) ^ 44
Issue Apr 2018
Page 17
6.153 - Table Definition File A Line 51 - Line 54 – FH Optimized Event Data
Key data are identified by an asterisk in Column SEQ
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*04 024 03 Zone 9 (3)
Line 51
*05 027 02 Line 9 (2) ^ 51
Line 52
*05 027 02 Line 9 (2) ^ 52
06 029 130 Threshold [X(13)] *10 10000 FH
Line 53
*05 027 02 Line 9 (2) ^ 53
Line 54
*05 027 02 Line 9 (2) ^ 54
Issue Apr 2018
Page 18
6.154 - Table Definition File A Line 61 - Line 64 – FC Optimized Event Data
Key data are identified by an asterisk in column SEQ
*1 001 01 A/C type X (1) 6 (A330)
*02 002 21 Task number X (21)
*04 024 03 Zone 9 (3)
Line 61
*05 027 02 Line 9 (2) ^ 61
Line 62
*05 027 02 Line 9 (2) ^ 62
06 029 130 Threshold [X(13)] *10 10000 FH
Line 63
*05 027 02 Line 9 (2) ^ 63
Line 64
*05 027 02 Line 9 (2) ^ 64
Issue Apr 2018
Page 19
6.2 - Access and Preparation Data Information File B
6.20 - Data Field Description –Key data
Code identifying the type of aircraft to which the task applies.
1 ^ A300 ;
2 ^ A310 ;
3 ^ A300-600 ;
4 ^ A318/A319/A320/A321;
5 ^ A350 ;
6 ^ A330 ;
7 ^ A340 ;
8 ^ A380 ;
M ^ A400M ;
Zone : 9 (3)
Line : 9 (2)

For EDP use only:
File B : 10 - 19 Access Data
20 - 29 Preparation Data
6.21 - Data Field Description –File B
Σ Access M/H : 9 (2) . 9 (2)
Manpower required to open and close the associated access panel(s) or door(s).
Access identifier : X (6) * n
Alphanumeric code identifying each access panel which must be opened to

accomplish the task.
Σ Preparation M/H : 9 (2) . 9 (2)
Manpower required to carry out associated preparation(s).
Preparation Nomenclature : X (75) * n
Nomenclature describing each preparation to be carried out to accomplish the task.

Each Nomenclature is delimited by a semicolon.
Issue Apr 2018
Page 20
6.2 - Access and Preparation Data Information File B
6.22 - Data Field Definition – Access data
*1 001 01 A/C Type X (1)
*02 002 21 Task number X (21)
*03 023 01 File identification ^B
*04 024 03 Zone 9 (3)
*05 027 02 Line ^ 10 - 19
Line 10
06 029 05 Σ M/H Access 9 (2) . 9 (2) 10.73
07 034 210 Access N° [X (6)] * 35 121AL
Line 11-19
06 029 210 Access N° [X (6)] * 35 121AL
6.23 - Data Field Definition – Preparation data
*1 001 01 A/C Type X (1)
*02 002 21 Task number X (21)
*03 023 01 File identification ^B
*04 024 03 Zone 9 (3)
Issue Apr 2018
Page 21
*05 027 02 Line ^ 20 - 29
Line 20
06 029 05 Σ M/H Preparation 9 (2) . 9 (2) 10.73
07 034 150 Preparation Nomenclature X (75) * 2 FLAPS

EXTENDED;
Line 21-29
06 029 150 Preparation Nomenclature X (75) * 2 FLAPS

EXTENDED;
Issue Apr 2018
Page 22
6.3 - File C
6.30 - Data field description Key data File C
1 ^ A300 ;
2 ^ A310 ;
3 ^ A300-600 ;
4 ^ A318/A319/A320/A321;
5 ^ A350 ;
6 ^ A330 ;
7 ^ A340 ;
8 ^ A380 ;
M ^ A400M ;
Zone : 9 (3)
Line : 9 (2)
6.31 - Data field description File C
Task Description : X (53)
Text defining the action to be performed (task description as in OMP/MPD).
Issue Apr 2018
Page 23
6.32 - Table Definition File C
*1 001 01 A/C Type X (1)
*02 002 21 Task number X (21)
*03 023 01 File identification ^C
*04 024 03 Zone 9 (3)
*05 027 02 Line X(2) ^ 01 - 99
06 029 212 Task Description [ X (53) ] 4
Issue Apr 2018
Page 24
6.4 - File D
6.40 - Data Field Description – Key data
1 ^ A300 ;
2 ^ A310 ;
3 ^ A300-600 ;
4 ^ A318/A319/A320/A321;
5 ^ A350 ;
6 ^ A330 ;
7 ^ A340 ;
8 ^ A380 ;
M ^ A400M
Zone : 9 (3)
Line : 9 (2)

For EDP use only:
File D : 00 Amtoss Identifier/DMC
01 - 19 Reference Data
40 - 49 MSI References
50 - 59 SSI References
60 - 69 ZIP References
70 - 72 ALI References
73 - 76 SEMR References
77 - 79 FAL References
80 - 89 CMR References
90 - 99 CMP References
6.41 - Data Field Description
Amtoss Reference : X(18)
Amtoss reference of the task in the Aircraft Maintenance Manual.

Data Modul Code A350
References : [X (53)] * 4
Issue Apr 2018
Page 25
Gives references to Technical Publications in which additional information for

accomplishment of the task can be found and/or reference to the official documents
related to the task
MRB - Reference : [X (25)] * 8
Gives reference to the related GVI & Visual Check MSI’s and SSI’s and ZIP listed in
the MRBR.
ALI - Reference : [X (25)] * 8
Gives reference to the related Items in the ALI Document (ALS Part 2 - Damage
Tolerant Airworthiness Limitation Items).
SEMR - Reference : [X (25)] * 8
Gives reference to the related Items in the SEMR Document (ALS Part 4 - System
Equipment Maintenance Requirements).
FAL - Reference : [X (25)] * 8
Gives reference to the related Items in the FAL Document (ALS Part 5 - Fuel
Airworthiness Limitations).
CMR - Reference : [X (25)] * 8
Gives reference to the related items in the CMR Document (ALS Part 3 - Certification
Maintenance Requirements)
CMP - Reference : [X (25)] * 8
Gives reference to the related Items in the ETOPS CMP Document (Configuration,
Maintenance, Procedure and Dispatch Standards for Extended Diversion Time
Operators).
6.42 - Table Definition File D
*1 001 01 A/C Type X (1)
*02 002 21 Task number X (21)
*03 023 01 File identification ^D
*04 024 03 Zone 9 (3)
Issue Apr 2018
Page 26
*05 027 02 Line ^ 01-99
References see below See below
06 029 18 Line 00 X(28) 491200-210-004
Amtoss Reference
DataModuleCode
06 029 212 Line 01 - 19 [X(53)] 4 SB 27-304

References
06 029 208 Line 40 – 49 [X(25)] 8 281100-00004-

01M
MSI References
321100-00002-
06 029 208 Line 50 – 59 [X(25)] 8 01S
SSI References
ZL-110-00001-
06 029 208 Line 60 – 69 [X(25)] 8 01Z
ZIP References
521303-01-01
06 029 208 Line 70 – 72 [X(25)] 8
ALI References
275420-09-1-E
06 029 208 Line 73 – 76 [X(25)] 8
SEMR References
281800-01-1
06 029 208 Line 77 – 79 [X(25)] 8
FAL References
32.40.00/03
06 029 200 Line 80 – 89 [X(25)] 8
CMR References
32-2-0000-002
06 029 200 Line 90 – 99 [X(25)] 8
CMP References
Issue Apr 2018
Page 27
R 7 - Example
column 1 2
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901…
8ZL-110-00001-01 A11000GVIAF 0.101MRB RADOME NOSE CONE TO FR0 NJUL 15/06 4

8ZL-110-00001-01 A11010 48 MO
8ZL-110-00001-01 A11030A380-800
8ZL-110-00001-01 B11010 0.20125 126
8ZL-110-00001-01 B11020 0.10LINERS TO BE REMOVED
8ZL-110-00001-01 C11001GENERAL VISUAL INSPECTION OF RADOME NOSE CONE TO FR0.
8ZL-110-00001-01 D11000052110-210-801
8ZL-110-00001-01 D11040ZL-110-00001-01Z
Line
Task Ident
A/C-Type Task Zone
File Ident
Issue Apr 2018

Page 28

Mpdv1 TSDF Spec

Uploaded by

Copyright:

Available Formats

Mpdv1 TSDF Spec

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mpdv1 TSDF Spec

Uploaded by

Copyright:

Available Formats

MPDS

Date Apr 2018

Section Change(1) Reason for Revision

2 R Organization of Data – Supplementary Information added

Issue Apr 2018

5- FILES AND RECORDS ORGANIZATION

6- FILES AND RECORDS DEFINITION SPECIFICATION

Issue Apr 2018

- Print of MPD data ;

- Update existing Planning Data

The data required for each task are contained in 4 files :

- File A contains Task Basic Data,

N Files and lines are only displayed if data content is provided

Issue Apr 2018

Reasons for revision :

- To incorporate changes resulting from developments in the maintenance program or in service

The data is totally reissued at each revision.

Issue Apr 2018

5- FILES AND RECORDS - ORGANIZATION

A/C TYPE : X TASK IDENT N° : XXXXXXXXXXXXXXX ZONE : XXX

are included in each file.

FILE B contains access data and preparation data such as : Σ M/H,

contains Task description data

contains data such as : Amtoss ID, reference document IDs,

X (n) = n alphanumeric characters

Issue Apr 2018

6- FILES AND RECORD DEFINITION

6.10 - Data Field Description –Key data

Aircraft Type : X (1)

“A” will be shown as default.

Task Number : X (21)

Identifies each separate task.

Zone in which the task is mainly performed.

Line sequence N°: 9 (2)

Line Sequence Number of data presented

6.11 - File A Line 00

6.111 - Data Field Description File A Line 00

Task Code : X (3)

Mnemonic code defining the type of task to be carried out.

Issue Apr 2018

Manpower, per skill/zone, required for task accomplishment.

Number of men per skill, required for task accomplishment.

Source Document : [X (10)*6]

Source document indication of the task

Time Controlled Item Marker : X(1)

Corrosion Prevention and Control Program (CPCP) Marker : X(1)

Temporary Protection System (TPS) : X(4)

Indicates the Type and Grade of TPS to be applied

Task title giving the designation of system/subsystem/component/zone/structural

Movement code : X (1)

Revision marker related to previous issue

Issue date e.g. APR 13/05

Program Section Identifier e.g. 3

Issue Apr 2018

6 - FILES AND RECORDS SPECIFICATION

Key data are identified by an asterisk.

6.112 - Table Definition File A Line 00

SEQ BYTE LENGTH DATA FORMAT Example

*1 001 01 A/C type X (1) 6 (A330)