MAINTENANCE PROGRAMS PROCEDURES MANUAL...REVISION HIGHLIGHTS MAINTENANCE PROGRAMS PROCEDURES MANUAL REVISION 18, DATED 11-26-13 Chapter 01, Section 01, Maintenance Programs Department

MAINTENANCE PROGRAMSPROCEDURES MANUAL

REVISION HIGHLIGHTS

MAINTENANCE PROGRAMS PROCEDURES MANUAL

REVISION 27, DATED 03-29-19

Chapter 01, Section 01, Maintenance Programs Department

Page 1, para 1.B., revised position title to “Manager, Maintenance Programs”, per MPRR 44156.

Page 1, para 2.A.(2)(a), revised position title to “Manager, Maintenance Programs”, per MPRR 44156.

Page 2, para 3.A., revised position title to “Manager, Maintenance Programs”, per MPRR 44156.

Page 3, para 3.A.(7)(a), revised position title to “Manager, Maintenance Programs”, per MPRR 44156.

Chapter 01, Section 02, Maintenance Programs Duties and Responsibilities (Ref. MNT 1.4.3)

Page 1, para 1., revised position title to “Manager, Maintenance Programs”, per MPRR 44156.

Page 1, para 1.A., revised position title to “Director, Quality Control”, per MPRR 44156.

Page 1, para 1.B.(1), revised position title to “Manager, Maintenance Programs”, per MPRR 44156.





Chapter 01, Section 03, Maintenance Programs Department Training

Page 1, para 2.F.(4), deleted para; renumbered subsequent steps, per MPRR 44156.

Page 2, para 2.F.(4), replaced “Job cards” with “Job Card System”, per MPRR 44156.

Page 2, para 2.F.(5), replaced “Check Definition” with “CMMS Processes”, per MPRR 44156.

Page 3, Maintenance Programs Training Checklist table, deleted step D.; renumbered subsequent steps; step D., replaced “Job Cards” with “Job Card System”; step E., replaced “Check Definition” with “CMMS Processes”, per MPRR 44156.

REVISION HIGHLIGHTS


Chapter 01, Section 04, Engineering Order Coordination Process

Page 1, para 1.B., revised position title to “Manager, Maintenance Programs”, per MPRR 44156.

Chapter 01, Section 17, Associate Writer Procedures


REVISION HIGHLIGHTS



Chapter 01, Section 09, Aircraft Maintenance and Inspection Program Bridging

Pages 1-9, old content is obsolete. Replaced this section with new content, per MPRR #43559.

REVISION HIGHLIGHTS



Chapter 01, Section 02, Maintenance Programs Duties and Responsibilities

Pages 1-3, moved and revised “Maintenance Programs Duties and Responsibilities” from GMM 02.03.02 to the MPPM, per MPRR #42419.

Page 1, added MNT reference to title of section, per MPRR #42419.

Chapter 01, Section 05, Maintenance Programs Revisions Policy

Page 1, para 1.A.(2)(a), added “Associate Writer” to description of process, per MPRR #42382.

Page 1, para 1.A.(3), added “Associate Writer” to description of process, per MPRR #42382.

Page 1, para 1.A.(3)(a), added “Associate Writer” to description of process, per MPRR #42382.

Page 1, para 1.A.(4)(a) thru (b), deleted steps; renumbered subsequent steps, per MPRR #42382.

Chapter 01, Section 17, Associated Writer Procedures

Page 1, para 2.I.(3), added step to procedures “Add time and date...”; renumbered subsequent step, per MPRR #42382.

Page 2, para 2.K.(4), revised step to read “MPRRs will be scanned...”, MPRR #42382.

REVISION HIGHLIGHTS



Chapter 01, Section 17, Associated Writer Procedures

Page 2, step 2.K.(5), updated location where final revisions are stored, per MPRR #42704.

Page 4, step 6.B.(3), deleted “Reliability” from step, per MPRR #42704.

REVISION HIGHLIGHTS




Page 4, deleted Para 4. “Maintenance Programs Organizational Chart” and the organizational chart, per MPRR #42462.

REVISION HIGHLIGHTS



Chapter 01, Section 13, Maintenance Programs Analysis and Adjustment Procedures

Revised paragraph 1.D., reference RAMP changed to SOM, per MPRR 42935.

REVISION HIGHLIGHTS




Revised section, per MPRR 42759.

REVISION HIGHLIGHTS




Added new Section, per MPRR 39989.

REVISION HIGHLIGHTS



Chapter 01, Section 16, Maintenance Programs Style Guide

Page 1, Item 1 deleted “MNT 1.6.3”, per MPRR 42641.

REVISION HIGHLIGHTS




Page 1, Item 2.A.(3) revised “ABX documents are published...” to “ABX documents are authored...”, per MPRR 41552.

Page 2, Item 2.A.(3)(d) revised from “Graphics are edited using commercially available graphics” to “Graphics are edited using commercially available graphics software”, per MPRR 41552.

Page 2, Item 3.A.(2) revised from “FAA Advisory Circular 120-16, manufacturer’s On Aircraft Maintenance Program (OAMP), and Maintenance Planning Document (MPD) documents, as well as applicable Maintenance Review Board (MRB) documents, are used as guides for ABX Maintenance Programs” to “FAA Advisory Circular 120-16, Maintenance Planning Document (MPD) documents, and Maintenance Review Board (MRB) documents are used as guides for ABX Maintenance Programs”, per MPRR 41552.

Page 2, Item 3.A.(3) revised “maintenance Task or process” to “maintenance Task”, per MPRR 41552.

Page 2, Item 3.A.(4) revised “check and inspection job cards” to “job cards”, per MPRR 41552.

Page 3, Item 3.A.(5)(b) revised “...determine how the trending items can be precluded” to “...determine how the trending items can be improved”, per MPRR 41552.

Page 3, Item 3.A.(7)(b) revised to read “Changes in Maintenance Steering Group 3 (MSG3) tasks and changes to intervals will be accomplished after applicable reliability and FAA approvals”, per MPRR 41552.

Page 4, added “Maintenance Information Specialist” to Maintenance Programs Organizational Chart, per MPRR 41552.

Chapter 01, Section 03, Maintenance Programs Department Training

Page 1, deleted Item 1.C. “All Maintenance Information related training is administered and maintained in the Maintenance Information HTML documents located on the server. See G:/MAMP/USERS/tp_web/index.htm for procedures and details”; renumbered subsequent items, per MPRR 41552.

Page 1, deleted Item 1.E. “Current department employees as of December 1, 2006 will be waived from completing the applicable checklist”; renumbered subsequent item, per MPRR 41552.

Page 1, Item 2.F.(3) revised from “Advisory Circular (A/C) 120-16D” to “Advisory Circular (A/C) 120-16”, per MPRR 41552.

REVISION HIGHLIGHTS


Page 3, Maintenance Programs Training Checklist, Item 5.B. revised from “OAMP/MPD/MRB Documents” to “MPD/MRB Documents”, per MPRR 41552.

Page 3, Maintenance Programs Training Checklist, Item 5.C. revised from “A/C 120-16D” to “A/C 120-16”, per MPRR 41552.

Chapter 01, Section 04, Engineering Order Coordination Process

Page 1, Item 1.B. revised to read “The Manager of Maintenance Programs is copied on the notification e-mail. He will be the contact person for the project or will delegate the responsibility and copy that person on the reply”, per MPRR 41552.

Chapter 01, Section 08, Bridging an Aircraft

Page 1, Item 2.A.(4) revised from “AFS-900-002-F-01 - (FAA Flight Standards Service Quality Management System - Aircraft Information Form)” to “FAA Order 8900.1, Vol 10, Ch 7, Sect 1 & 2 - (Major Change Process Document)”, per MPRR 41552.

Page 1, Item 2.A.(5) revised from “AFS-900-002-F-03 - (Aircraft Configuration Control Job Aid)” to “FAA Order 8900.1, Vol 10, Ch 6, Sect 3 - (Aircraft Configuration Control Document)”, per MPRR 41552.

Page 1, Item 2.A.(6) revised from “FAA Order 8300.10, Chapter 36 - (Monitor Continuous Airworthiness Maintenance Program/Revision)” to “FAA Order 8900.1, Vol. 3, Ch 43 - (Evaluate Continuous Airworthiness Maintenance Program/Revision)”, per MPRR 41552.

Chapter 01, Section 09, Instructions for Building Aircraft Bridging Document

Page 3, Item 3.C.(6) revised “floppy disc” to “data disc”, per MPRR 41552.

REVISION HIGHLIGHTS



Chapter 01, Section 15, PMI Engineering Order (EO) and Jobcard Procedures

Page 13, added new Item 8.G.(2)(c)1 “Once the Job Card has reached a revision letter of “Z”, the subsequent revision level will be listed as alpha characters beginning with “AA”, per MPRR 40984.

REVISION HIGHLIGHTS




Page 4, revised “Manager Maintenance Programs” to “Manager Reliability/Maintenance Programs”, per MPRR 38213.

Chapter 01, Section 16, Maintenance Programs Style Guide

Page 1, Item 1. added “(Ref. MNT 1.3.2, MNT 1.6.3)”, per MPRR 38883.

REVISION HIGHLIGHTS



Chapter 01, Section 03

Page 2, added new item 2.F.(12) “AC 120-102, EWIS ICA”, per MPRR 38273.

Page 3, Maintenance Programs Training Checklist, added new Item 5.L. “AC 120-102, EWIS ICA”, per MPRR 38273.

REVISION HIGHLIGHTS




Page 3, Item 2.A.(10)(c) Note revised “DC9” to “B767”, per MPRR 37823.

Page 15, deleted Item 8.G.(2)(r)2 “The letter designation “A” or “B” following the four-digit panel numbers on the DC-9 aircraft are not required. All reference to the alpha character used by the manufacturer should be disregarded”, per MPRR 37823.

CHAPTER:

SECTION:

PAGE:

LEP

1

REV. NO.:DATE:

00

SECTION PAGE SECTION PAGE DATE DATECHAPTER/ CHAPTER/

MAINTENANCE PROGRAMS PROCEDURES MANUAL27

03-29-19

LEP 1 03-29-19Contents 1-3 10-03-18

CH 0101 1-3 03-29-1902 1-3 03-29-1903 1-3 03-29-1904 1-2 03-29-1905 1 02-07-1806 1 08-05-0907 1 08-05-0908 1-3 11-26-1309 1 10-03-1810 1-7 06-12-0711 1 11-06-0912 1 06-12-0713 1 01-20-1714 1-2 02-24-1015 1-19 04-02-1316 1-19 05-13-1617 1-4 03-29-19

CHAPTER:

SECTION:

PAGE:

Contents

1

REV. NO.:DATE:

00


10-03-18

CHAPTER 01, SECTION 01

MAINTENANCE PROGRAMS DEPARTMENTGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Maintenance Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Maintenance Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2


MAINTENANCE PROGRAMS DUTIES AND RESPONSIBILITIES (REF. MNT 1.4.3)Manager Maintenance Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Associate Writer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Maintenance Programs Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Maintenance Programs Information Technologist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3


MAINTENANCE PROGRAMS DEPARTMENT TRAININGGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Maintenance Programs Specialist Training Checklist (See Page 3) . . . . . . . . . . . . . . . . . . . . . . . 1


ENGINEERING ORDER COORDINATION PROCESSGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


MAINTENANCE PROGRAMS REVISIONS POLICYGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


CONTRACT LABORGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


THIS SECTION IS INTENTIONALLY LEFT BLANK.


BRIDGING AN AIRCRAFTPurpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Preparing to Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Bridging Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

CHAPTER:

SECTION:

PAGE:

Contents

2

REV. NO.:DATE:

00


10-03-18


AIRCRAFT MAINTENANCE AND INSPECTION PROGRAM BRIDGINGGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


PMI ENTRY/REVISION PROCEDURESJob Cards in Maintenance Entry/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Part Codes/LAR Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


CREATING/REVISING EO’S OR TASKSPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


CREATING/REVISING JOB CARDSPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


MAINTENANCE PROGRAMS ANALYSIS AND ADJUSTMENT PROCEDURESGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Non-Routine/Logpage Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


MAINTENANCE AND INSPECTION PROGRAM (MIP) MANUALS PROCEDURESGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1MIP Origination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1


PMI ENGINEERING ORDER (EO) AND JOB CARD PROCEDURESGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Creating EOs (See Figure 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2EO Updates, Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9EO Task Deletion, Cancellation, and Re-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9EO Task Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10EO Task Cancellation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11EO Re-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Creating Job Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

CHAPTER:

SECTION:

PAGE:

Contents

3

REV. NO.:DATE:

00


10-03-18


MAINTENANCE PROGRAMS STYLE GUIDEGeneral (Ref. MNT 1.3.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Presentation Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Capitalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Change (Revision) Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15WARNINGS, CAUTIONS, and NOTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Abbreviations and Acronyms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18


ASSOCIATE WRITER PROCEDURESGeneral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Standard Publication Revision Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Maintenance Forms (M-Forms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Publications That Require FAA Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Publications That Require Distribution of Paper Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Job Card Diagram Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

CHAPTER:

SECTION:

PAGE:

01

1

REV. NO.:DATE:

01

MAINTENANCE PROGRAMS PROCEDURES MANUAL 2703-29-19


MAINTENANCE PROGRAMS DEPARTMENT

1. General

A. Maintenance Programs Department is made up of two sections: Maintenance Information and Maintenance Programs.

(1) Maintenance Information is responsible to create, revise, publish, and distribute ABX Policy and Procedure publications.

(2) Maintenance Programs is responsible to develop and maintain ABX aircraft Maintenance and Inspection Programs.

B. These areas report to the Manager, Maintenance Programs.

2. Maintenance Information

A. Maintenance Information is staffed with Maintenance Information Specialist, Associate Writer, and Document Coordinator.

(1) Writers create and revise approved and accepted information to publish the various controlled ABX documents. Refer to ABX GMM for a listing of these documents.

(2) Changes to these documents are accomplished through the use of Maintenance Program Revision Request (MPRR, M-101); see GMM Section 01.03; and per requirements called out in Engineering Authorizations.

(a) The Manager, Maintenance Programs monitors MPRR work flow and will prioritize the order of accomplishment as required.

(3) ABX documents are authored in the following Software formats:

(a) MS Word

(b) Adobe FrameMaker

(c) Standard Generalized Markup Language (SGML) using Arbortext or Textpad.

CHAPTER:

SECTION:

PAGE:

01

2

REV. NO.:DATE:

01


(d) Graphics are edited using commercially available graphics software.

(4) Management of the distribution of ABX Maintenance and Engineering (M&E) controlled documents is accomplished with the use of an SQL database named (DistributionDocTrack).

(a) The database identifies copy holders of the various documents distributed throughout Maintenance and Engineering.

(b) Updates are made daily to the Purchasing, Maintenance and Inventory (PMI) System from this database providing the latest revision level and date the revision was issued.

(c) Maintenance Information also distributes documents published by the Flight Department to Maintenance personnel, and to Maintenance libraries.

3. Maintenance Programs

A. Maintenance Programs is staffed with Maintenance Programs Specialists who report to the Manager, Maintenance Programs.

(1) The Maintenance and Inspection Program (MIP) for each aircraft fleet type is maintained separately, with portions of the operations specifications contained in a Maintenance Inspection Program (MIP) manual.

(2) FAA Advisory Circular 120-16, Maintenance Planning Document (MPD) documents, and Maintenance Review Board (MRB) documents are used as guides for ABX Maintenance Programs.

(3) Specification sections in the MIP contain ATA system identification, component description, maintenance Task, and frequency of accomplishment.

(4) Specifications outlined in the MIP are used to create job cards detailing the various procedures with applicable signature requirements based on ABX Required Inspection Item (RII) policy.

(5) Continuing analysis of the various maintenance programs controlled by ABX is accomplished by a periodic review of Non-Routine documents generated during heavy maintenance.

CHAPTER:

SECTION:

PAGE:

01

3

REV. NO.:DATE:

01


(a) ABX has compiled databases from PMI and from some ABX heavy maintenance vendors.

(b) When trends are identified, a detailed review is made to determine how the trending items can be improved.

(6) Maintenance Programs monitors the Corrosion Programs for the various aircraft fleet types.

(a) Internal policy provides a process of notification when corrosion exceeding Level Two is found (ref. ABX MIP).

(7) Changes to the MIP and job cards are accomplished through the use of Maintenance Program Revision Request (MPRR, M-101), and GMM Section 01.03.

(a) The Manager, Maintenance Programs monitors MPRR work flow and will prioritize the order of accomplishment as required.

(b) Changes in Maintenance Steering Group 3 (MSG3) tasks and changes to intervals will be accomplished after applicable reliability and FAA approvals.

(8) Reliability provides the organization with information relating to possible negative trends to fleet and aircraft reliability.

(a) Maintenance Programs evaluates information collected from heavy maintenance Non-Routine database as well as Log items generated, to determine if there is some adjustment required to improve reliability.

CHAPTER:

SECTION:

PAGE:

02

1

REV. NO.:DATE:

01



MAINTENANCE PROGRAMS DUTIES AND RESPONSIBILITIES (REF. MNT 1.4.3)

1. Manager, Maintenance Programs

A. Reports to the Director, Quality Control.

(1) Has the responsibility and authority for the quality, establishment, and modification of policies, procedures, instructions and information, controls, process measurements, and interfaces of the processes listed below. He also has the authority to delegate his responsibility and authority to the Maintenance Program Specialist.

(a) Aircraft Maintenance and Inspection Programs

(b) General Maintenance Manual

(c) Cargo Handling Equipment, Systems, and Appliances

(d) Manual Currency

(e) Content Consistency Across Manuals

(f) Distribution of Manuals

(g) Availability of Manuals

(h) Supplemental Maintenance Manual Requirements

B. Additional Responsibilities:

(1) In the absence of the Manager, Maintenance Programs, the Programs Specialists will assume the responsibilities.

(2) Any or all duties of the Manager, Maintenance Programs may be delegated to any qualified individual as deemed necessary; however, such delegation does not relieve the Manager, Maintenance Programs of the overall responsibility.

(3) Supervises the Maintenance Program Specialist, Maintenance Programs Information Technologist and Associate Writer.

(4) Assesses the impact of any changes to the associated interfaces within the Flight Operations Manual.

CHAPTER:

SECTION:

PAGE:

02

2

REV. NO.:DATE:

01


(5) Provide liaison to the Maintenance Department.

(6) Perform any other duties assigned.

2. Associate Writer

A. Reports to the Manager, Maintenance Programs and is responsible for, but not limited to, the following:

(1) Create and edit original text from markup provided by ABX entities for policy/procedure documents/manuals ensuring conformity to ABX and ATA 2200 standard format, and an accurate conveyance of information to the end user.

(2) Create graphic illustrations using graphic illustration software.

(3) Assist in the design, development, and revision of forms which are required for the administration and accomplishment of aircraft maintenance.

(4) Establish and maintain document control for the distribution of technical documents necessary for the proper maintenance of ABX aircraft, and for support of the airline.

(5) Procure and distribute current revisions for all documents maintained.

(6) Create and track revision transmittals issued to copyholders.

(7) Oversee and maintain all master documents in a secure and logical manner.

(8) Perform other duties as assigned.

3. Maintenance Programs Specialist

A. Reports to the Manager, Maintenance Programs and is responsible for, but not limited to, the following:

(1) Perform a periodic, zero-based review of the ABX Maintenance Program at intervals not to exceed 5 yrs.

(2) Establish and maintain history of each maintenance task, as defined in the Maintenance and Inspection Program (MIP).

CHAPTER:

SECTION:

PAGE:

02

3

REV. NO.:DATE:

01


(3) Analyze and make recommendations to add, delete or change task intervals or inspection level based on actual reliability operating experience, manufacturer’s recommendations or airworthiness directives.

(4) Ensure that the MIP is in continual compliance with all corporate and regulatory requirements, with an emphasis on quality and economics.

(5) Responsibility for reviewing maintenance program non-routine data, conducting analysis, and compiling data.

(6) Review program tasks for improvement by the incorporation of new products, processes, and technologies.

(7) Review Boeing MPD and Task Card revisions for incorporation into the ABX MIP and Task Card system to maintain currency with the OEM program.

(8) Bridge newly acquired aircraft into the ABX Maintenance Program.


4. Maintenance Programs Information Technologist

A. Reports to the Manager, Maintenance Programs.

(1) Mine and analyze reliability program and maintenance program data, compile required data and assemble or populate reports in various formats.

(2) Train others in the functionality of the Maintenance & Engineering OTS software applications.

(3) Revise task cards and graphics per submitted Maintenance Program Revision Requests (MPRRs) and set task controls within the M&E software to ensure regulatory compliance of given task.

(4) Facilitate special projects and process improvement efforts using project management software and continuous improvement skills.


CHAPTER:

SECTION:

PAGE:

03

1

REV. NO.:DATE:

01



MAINTENANCE PROGRAMS DEPARTMENT TRAINING

1. General

A. This training section complies with ABX Training Program outlined in GMM Section 03.01. This section will not supersede the GMM.

B. Department training will be accomplished for all new hires or transfers within 90 days of employment in the department.

C. The Maintenance Program Training will be accomplished utilizing the informal On the Job Training (OJT) method and will be recorded on the Maintenance Programs Specialist Training Checklist.

D. A copy of all completed checklists will be maintained in the employees training file and by the department manager.

2. Maintenance Programs Specialist Training Checklist (See Page 3)

A. Department overview and introductions to be conducted by manager of the department.

B. PC Network, AS400, E-Mail, and Telephone requests submitted as necessary.

C. Schedule Company training mandatory and/or elective courses as necessary.

D. Review Maintenance Programs Department Procedures Manual.

E. Review ABX Air Inc. General Maintenance Manual (GMM).

F. Review the following documents:

(1) ABX Air Inc. Maintenance Inspection Program (MIP)

(2) Maintenance Planning Document (MPD), and Maintenance Review Board (MRB) documents.

(3) Advisory Circular (A/C) 120-16

(4) Job Card System

CHAPTER:

SECTION:

PAGE:

03

2

REV. NO.:DATE:

01


(5) CMMS Processes

(6) Reliability Analysis and Maintenance Planning Program (RAMP) Manual

(7) ABX Ops Specs

(8) Aircraft Bridging

(9) Non-Routine Analysis

(10) Escalations/De-escalations

(11) AC 120-102, EWIS ICA

CHAPTER:

SECTION:

PAGE:

03

3

REV. NO.:DATE:

01


29MAR19Page 1 of 1

MAINTENANCE PROGRAMS TRAINING CHECKLIST

Employee Name: ID No.:

Occupational Title:

ITEM TASK DATE INITIALS

1. Department Overview (Manager)

2. PC/AS400/Voice Mail Requests

3. Attend company training mandatory courses and/or elected courses as necessary.

4. Review Maintenance Programs Department Procedures Manual.

5. Review of the following:

A. ABX MIP Manuals

B. MPD/MRB Documents

C. A/C 120-16

D. Job Card System

E. CMMS Processes

F. RAMP Manual

G. ABX Ops Specs

H. A/C Bridging

I. Non-Routine Analysis

J. Escalations/De-Escalations

K. AC 120-102, EWIS ICA

CHAPTER:

SECTION:

PAGE:

04

1

REV. NO.:DATE:

01



ENGINEERING ORDER COORDINATION PROCESS

1. General

A. Maintenance Program procedures related to the Engineering project notification e-mail form:

(1) Engineering Procedures control the process to prepare and send the project notification.

(2) Maintenance Program Procedures for the follow-up of Engineering projects.

B. The Manager, Maintenance Programs is copied on the notification e-mail. He will be the contact person for the project or will delegate the responsibility and copy that person on the reply.

C. The contact person in Maintenance Programs will contact the Engineer assigned to the project and review the scope of the project to determine if there is an impact to the program or publications.

D. The following is a list of potential issues that will be addressed with the Engineer:

(1) Are there parts changed?

(2) Is there an inspection required?

(3) Is there, or will there be terminating action?

(4) How will we be notified when terminating action will be completed?

(5) What repeat action is required?

E. Maintenance Programs will review the information provided by the Engineer and determine the following:

(1) If there is a repeat action, who is responsible, Programs or Engineering?

(2) Is there any action required that may already be part of the current program?

CHAPTER:

SECTION:

PAGE:

04

2

REV. NO.:DATE:

01


(3) Are there any changes required to ABX manuals as a result of the requirements of the project?

F. Coordination with Engineering

(1) If after review of the project documentation, it is determined that there is action to be taken by Maintenance Programs, the contact person from the Programs area will contact the Engineer assigned to the project and coordinate the time line for completion of the supporting information.

(2) Within this coordination it must be agreed that the EO Core Review and EO release will not occur until the supporting changes have been made and documents revised.

CHAPTER:

SECTION:

PAGE:

05

1

REV. NO.:DATE:

01



MAINTENANCE PROGRAMS REVISIONS POLICY

1. General

A. The following procedures shall be initiated in the process of issuing a revision to any manual or document:

(1) Once an author completes the incorporation of an Engineering Order or an MPRR, another peer will proof the document for content and technical accuracy.

(2) Once the document is returned from being checked for content and technical accuracy and corrected.

(a) Manuals will be forwarded to Associate Writer/Document Distribution with appropriate supporting documents (i.e., Table of Contents if impacted, List of Effective Pages, and Transmittal).

(3) The Associate Writer/Document Coordinator will proof controlled documents for correct Revision Number and Date, as well as to ensure documents listed on the Transmittal are included in the revision package.

(a) The Associate Writer/Document Coordinator will also ensure Style Guide compliance is accomplished in the Documents prior to issue.

(b) Any errors detected will be corrected by the original author.

(4) If the publication is to be issued to an aircraft, see procedures in GMM Section 07.08.01.

CHAPTER:

SECTION:

PAGE:

06

1

REV. NO.:DATE:

01

1008-05-09



CONTRACT LABOR

1. General

A. Contractor orientation is similar to new employee orientation. Contractors will receive training relative to the assigned task. The contractor orientation will be conducted by appropriate department personnel.

B. All contractors will be under direct supervision of department personnel.

CHAPTER:

SECTION:

PAGE:

07

1

REV. NO.:DATE:

01



THIS SECTION IS INTENTIONALLY LEFT BLANK.

CHAPTER:

SECTION:

PAGE:

08

1

REV. NO.:DATE:

01



BRIDGING AN AIRCRAFT

1. Purpose

A. The purpose of bridging is to determine an aircraft’s maintenance status, as compared to the ABX Maintenance Program and ensure all maintenance tasks are accounted for and accomplished within the proper interval in order to add the aircraft to the Company’s Operation Specifications (OpSpec).

(1) An aircraft may be purchased with or without being maintained on a current Maintenance Program, but typically it will go from an approved Maintenance Program to the ABX Air Inc. approved Maintenance Program.

(2) Once an aircraft’s required maintenance tasks and all time controlled tasks are current or with hours remaining, the aircraft can be considered bridged and added to the Company’s Operations Specifications.

2. Preparing to Bridge

A. One will need working knowledge of the following rules, regulations and guidelines prior to starting the aircraft bridging process:

(1) FAR 43, Appendix A, B, D, E, and F - (Maintenance)

(2) FAR 121.379 - (Maintenance Authority)

(3) Advisory Circular 120-16D - (Air Carrier Maintenance Programs)

(4) FAA Order 8900.1, Vol 10, Ch 7, Sect 1 & 2 - (Major Change Process Document)

(5) FAA Order 8900.1, Vol 10, Ch 6, Sect 3 - (Aircraft Configuration Control Document)

(6) FAA Order 8900.1, Vol 3, Ch 43 - (Evaluate Continuous Airworthiness Maintenance Program/Revision)

(7) Maintenance Planning Document - (MPD), Maintenance Review Board - (MRB)

CHAPTER:

SECTION:

PAGE:

08

2

REV. NO.:DATE:

01


(8) Company General Maintenance Manual - (GMM), Aircraft Maintenance Manual - (AMM), Aircraft Illustrated Parts Catalog - (AIPC)

B. Gather the following Aircraft Information from the previous operator:

(1) Aircraft type, model, and series

(2) Aircraft manufacturer date

(3) Aircraft serial number, previous tail number, and post bridge tail number

(4) Aircraft status (Current hours, cycles, and flying/parked)

(5) Engine status (type, configuration, current hours, cycles, program)

(6) Availability of acquired aircraft records

(7) Is this aircraft new to the Company?

C. Gather the following Maintenance Program information from the previous operator:

(1) Which type of Maintenance Program is the aircraft currently maintained i.e., MSG3, blocked, phased, segmented, etc.

(2) Determine if the aircraft maintenance is current on current program

(a) Be sure to include AD’s, S/B’s, STC’s, etc.

(3) Determine which of the Maintenance Programs this aircraft is going to be bridged from and to:

(a) MSG-3 analysis - (ABX Air Inc. B767 Maintenance Program is based on MSG-3 analysis).

1 MSG-3 analysis determines the maintenance tasks intervals.

a These maintenance tasks are accomplished as determined to ensure discrepancies are discovered when they are most likely to occur.

CHAPTER:

SECTION:

PAGE:

08

3

REV. NO.:DATE:

01


b The aircraft owner/operator will monitor/research the findings of these maintenance tasks and adjust their programs accordingly.

(4) New programs require an approval request submitted to the FAA.

(a) A letter of intent is required for all new aircraft types and all new aircraft configurations.

(5) Bridging methods

(a) Inclusion method requires accomplishing all maintenance tasks in the ABX Air Inc. Maintenance Program prior to adding the aircraft to the OpSpec.

1 Inclusion method is used when historical data is not available from the previous owner/operator or the aircraft was not maintained under any maintenance program.

(b) Review method requires an analysis of the aircraft’s previous Maintenance Program to determine which maintenance tasks need to be accomplished to satisfy the ABX Air Inc. Maintenance Program.

3. Bridging Data

A. Perform the following actions:

(1) Create an aircraft timeline to place the aircraft in its life from date of manufacture to the current ABX program.

(2) Compare the previous operator cards/task to the ABX cards/tasks for applicability.

(3) Identify last accomplishment of owner/operator maintenance program job cards, Service Bulletins (SB’s); Certification Maintenance Requirements (CMR’s); Airworthiness Directives (AD’s) and other time/cycle limited tasks.

(4) Based on the items above review, develop a list of all required maintenance to be accomplished at the Bridging Check using ABX Air Inc. tasks/jobcards/forms.

(5) Upon completion of the Bridging Check, the aircraft will be fully bridged into the ABX Air Maintenance Program.

CHAPTER:

SECTION:

PAGE:

09

1

REV. NO.:DATE:

01



AIRCRAFT MAINTENANCE AND INSPECTION PROGRAM BRIDGING

1. General

A. This section will provide general guidance to bridge an airplane from a previous operator’s maintenance program to the ABX Maintenance and Inspection Program (MIP). No two operator’s maintenance programs are alike. Individuals who are tasked with bridging maintenance programs must have a working knowledge of the manufacturer’s Maintenance Program Document (MPD), CFR Parts 91 and 121 applicable to airworthiness, Part 25 and Part 39. FAA Order 8900.1, Volume 10, Chapter 9, Section 1, Safety Assurance System: Aircraft Configuration Control Document should be reviewed as it relates to Maintenance Program requirements.

B. The delivery documents provided with the airplane must be analyzed to determine its current configuration and maintenance history. This analysis will determine what will be required to bridge the airplane into the ABX maintenance program.

C. A documentation package should be assembled that will readily identify how each requirement of the ABX maintenance program has been or will be met before adding the airplane to the ABX OpSpecs. The documentation can be in the format of a marked up ABX MIP manual, individual spread sheets, various reports, etc., provided the assembled information will satisfy any probable inquiry from the FAA Principal Maintenance Inspector (PMI) or Assistant Safety Inspector (ASI) as assigned.

D. A bridging letter to the PMI must be written that describes the work accomplished in sufficient detail to indicate the airplane is in compliance with the ABX maintenance program.

E. ABX Maintenance Programs will sign for the applicable sections of the B767-7 Adding Aircraft to ABX Fleet Checklist and M-183 Airworthiness Directive Bridging Document Routing and Signature Form.

CHAPTER:

SECTION:

PAGE:

10

1

REV. NO.:DATE:

01

306-12-07



PMI ENTRY/REVISION PROCEDURES

1. Job Cards in Maintenance Entry/Update

A. The following procedures are used to revise active Job Cards in PMI.

(1) Select PMI Menu Option 33, Engineering Menu; press ENTER.

(2) Select Option 17, Job Card Entry/Update - Maintenance; press ENTER.

(3) Enter the Job Card number in the “Active” field, and press ENTER. Confirm card header is the card intended to revise, and press ENTER.

(4) Tab down to insert a “Y” in the “Copy Card to Maintenance” field, press ENTER, and insert “Y” to confirm.

NOTE: This places a copy into maintenance. The original Job Card is still active and available for use while the copy in Maintenance is updated and moved back to Active.

(5) Enter the Job Card number in the “Job Card in Maintenance” field, and press ENTER to proceed. Ref. Figure 1.

(6) Move cursor to the appropriate field and enter data; press ENTER.

NOTE: See Figure 2 for reference numbers for entry fields.

(a) Enter Job Card description (left justify).

(b) Enter revision number (left justify).

(c) Enter Area (left justify).

(d) Enter required skill group Labor Code (left justify). F4 to see options.

(e) Total number of elapsed hours to complete the task (right justify).

(f) Total number of Technicians required to complete the task (right justify).

CHAPTER:

SECTION:

PAGE:

10

2

REV. NO.:DATE:

01

306-12-07


(g) Enter Schedule Code (left justify). F4 to see options.

(h) “Y” or leave blank.

(i) “Y” or leave blank.

(j) “Y” or leave blank.

(k) “Y” or leave blank.

(l) Enter Job Card number of conflict card, if applicable.

NOTE: Subject Job Card currently in maintenance will not issue to future work orders when the Conflict Card is issued to the same work orders.

(m) Enter the manufacturer’s Job Card that this card is designed from, if applicable.

(n) Leave blank.

NOTE: Steps (o) - (u) are optional “Y” or leave blank fields. Inserting a “Y” and pressing ENTER will open an additional screen for editing/inputting zone numbers, panel numbers, Job Card descriptions, data entry, etc.

(o) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

(p) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

(q) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

(r) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

(s) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

CHAPTER:

SECTION:

PAGE:

10

3

REV. NO.:DATE:

01

306-12-07


(t) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

(u) Leave blank or “Y”, enter text, press ENTER, then F3 to return to Entry/Update screen.

(7) Complete the update/revision by pressing ENTER; insert “Y” in the Update field; press ENTER.

NOTE: Pressing “F3” to exit before pressing ENTER may lose unsaved edited data.

(8) F3, select Menu #18 “Move Job Card from MAINT to Active”, press ENTER.

(9) Insert Job Card number in the “Start at Job Card” field, or page down to scroll to desired card, insert “Y” beside desired Job Card, and press ENTER (Ref. Figure 3).

(10) The next screen is “Continue With Maintenance Job Card Activation.” Enter “Y” to continue, or “N” to edit Maintenance Job Card (Ref. Figure 4).

(11) “Do You Wish To Apply 27-079-0101 to Open Job Cards?” Enter valid option to continue: (Y)es or (N)o: (Ref. Figure 5).

(12) If (Y) was chosen: Open Work Orders will be listed to select for replacing with the new Job Card. Record Open Work Orders and send notifications to Planning if Planning has already printed (Ref. Figure 6).

Figure 1

CHAPTER:

SECTION:

PAGE:

10

4

REV. NO.:DATE:

01

306-12-07


Figure 2

CHAPTER:

SECTION:

PAGE:

10

5

REV. NO.:DATE:

01

306-12-07


Figure 3

Figure 4

CHAPTER:

SECTION:

PAGE:

10

6

REV. NO.:DATE:

01

306-12-07


Figure 5

Figure 6

2. Part Codes/LAR Flags

A. The following procedures are for new part codes/P/Ns without a Load at Receiving (LAR) flag, where interchangeable part codes/P/Ns have LAR flags.

(1) Select PMI Menu 33, Engineering Menu, press ENTER, then Option 12 “Engineering Order Entry/Update.” Insert Task Number, press ENTER [this opens a dialogue box with options (U) or (D): (U)pdating or (D)uplicating]. Place (U) and press ENTER.

(2) Move cursor to the Memo field and insert (Y), press ENTER to list new Memo, add text/reason for update, press ENTER to move the new entry into the Notes field, then press F3 to return to the ENGINEERING ORDER ENTRY/UPDATE screen.

(3) Press ENTER and insert (Y) to update, tab to Effectivity For Part, (Y), then ENTER.

CHAPTER:

SECTION:

PAGE:

10

7

REV. NO.:DATE:

01

306-12-07


(a) On the next screen, place P/N in the Vendor P/N field; ensure (Y) is in the Load at Receiving field.

(b) Place the new Part Code in the Part Code field, press ENTER, F3 to exit to Engineering Menu.

(c) Verify Job Cards are effective to new parts.

1 From the ENGINEERING MENU screen select (84 Inquiry Menu), (15 Task Inquiry), type task number into Task Field and press ENTER, press (Y) and ENTER at View J/C field, write or copy Card numbers for later use. Press F3 to exit five times to return to Engineering Menu screen.

(d) Apply Cards to Task.

1 Select 17 Jobcard Entry/Update - Maintenance, type Job Card number in Jobcard Active field and press ENTER, review card information, press ENTER to continue, place (Y) in Apply Card to Task Field, press ENTER, type Task number in Task field and (Y) in Load at Receiving field, press ENTER.

2 Review all tasks listed at Load at Receiving screen to verify that all Tasks listed have (Y) inserted in SEL field. If not, press (Y) and ENTER, press F3 to exit.

CHAPTER:

SECTION:

PAGE:

11

1

REV. NO.:DATE:

01



CREATING/REVISING EO’S OR TASKS

1. Policy

A. The following policy will be followed when creating or revising Engineering Orders (EOs) or Tasks that would have a direct effect on maintenance due and program compliance.

B. Each specialist will address the following as they pertain to each request:

(1) Do the changes or additions requested involve:

(a) An increase or decrease in the time remaining for any effective aircraft or component?

(b) Will the new adjusted time remaining result in the task being due within six months of the date of the change?

(c) The changes made were only corrections or typographical errors during input but have an impact on maintenance due times.

(2) All revision requests must be evaluated to determine if the aircraft system or component is ETOPS related IAW GMM 04.44 Item 6. ETOPS Significant Systems. If an ETOPS related system is being modified the specialist must ensure compliance with the ECMC program described in EPM 01.28 if the system is to be effective to an aircraft tail number which is listed in the D086 Operation Specification.

(3) If the answer to any of the above is yes, the request cannot be signed off until Planning is advised in writing and their questions are completely addressed.

(4) Does the applicable MIP manual reflect the changes and identify the new or revised frequencies correctly?

(5) All revision requests must be evaluated to determine if the proposed revision will change a voluntary disclosure’s comprehensive fix element. A comprehensive fix element is identified in a Job Card’s memo or text with a note that alerts the reader the item is related to a voluntary disclosure. If the proposed revision involves a voluntary disclosure, QC must review the proposed revision and either accept or reject the revision by signature.

CHAPTER:

SECTION:

PAGE:

12

1

REV. NO.:DATE:

01



CREATING/REVISING JOB CARDS

1. Policy

A. The following policy will be followed when creating or revising a job card that would have a direct effect in effectivity and program compliance.

(1) Each specialist will address the following as they pertain to each request:

(a) Do the changes or additions requested involve:

1 More than one fleet?

2 More than one model?

3 More than one tail number?

(b) If the answer to any of the above is yes, the request cannot be signed off until all tail numbers in the applicable fleets are completely addressed and cards created or revised.

(c) Does the applicable MIP manual reflect the changes and identify all effectivities?

CHAPTER:

SECTION:

PAGE:

13

1

REV. NO.:DATE:

01

2201-20-17



MAINTENANCE PROGRAMS ANALYSIS AND ADJUSTMENT PROCEDURES

1. General

A. Maintenance Programs continuously performs analysis of the MIPs for each aircraft in the ABX Air fleet.

B. For “Interval Change Control Policy” procedures, refer to RAMP manual (Chapter 04, Section 01).

C. For “Utilization of MSG-3 Analysis Methods”, refer to RAMP manual (Chapter 07, Section 02).

D. For “Short-Term Escalation (STE) Interval Procedures” refer to SOM (Chapter 05, Section 01).

2. Non-Routine/Logpage Analysis

A. Continuing analysis of the various maintenance programs controlled by ABX Air is accomplished by periodic reviews of non-routine and/or logpage entries generated by maintenance personnel.

B. Maintenance Programs automated this process with a compiled database or the analysis may be done manually through AS400 queries.

C. When non-routine trends are identified, a detailed review will be made to determine how these trends can be precluded.

CHAPTER:

SECTION:

PAGE:

14

1

REV. NO.:DATE:

01

1202-24-10



MAINTENANCE AND INSPECTION PROGRAM (MIP) MANUALS PROCEDURES

1. General

A. Maintenance Programs maintains the Maintenance and Inspection Procedures (MIP) Manual. Detailed procedures and instructions are contained within the manual.

B. The ABX MIP is controlled by the ABX Reliability Analysis and Maintenance Planning Program, Document No. 80-81, (Reference ABX RAMP Manual) as described in Advisory Circular 120-17A.

C. The MIP is applicable as listed in the ABX Maintenance Operations Specifications, Part D, Item D085.

2. MIP Origination

A. B767

(1) The Boeing 767 Maintenance Planning Data (MPD) document provides maintenance planning information necessary for ABX to develop a customized scheduled maintenance program.

(2) The MPD lists all Boeing recommended scheduled maintenance tasks and satisfies (in part) the FAA requirement that a manufacturer provide “instructions for continued airworthiness” as specified in FAR 25.1529 Appendix H.

(3) Periodic (scheduled) maintenance tasks outlined in this document include, but are not limited to, the 767 Maintenance Review Board (MRB) Report.

(4) The Scheduled Maintenance Tasks in this document are not all-inclusive. ABX has the final responsibility to decide what to do and when to do it except for those maintenance requirements identified as “Airworthiness Limitations” or “Certification Maintenance Requirements”.

CHAPTER:

SECTION:

PAGE:

14

2

REV. NO.:DATE:

01

1202-24-10


(5) Airworthiness Directive (AD) repetitive maintenance or inspection tasks are listed in the MIP manual. The AD number that mandates the task must be referenced with the task.

NOTE: AD references are required by the comprehensive fix to Self Disclosure 2009GL234007. Do not remove item (5)’s requirements or this note without QC concurrence.

CHAPTER:

SECTION:

PAGE:

15

1

REV. NO.:DATE:

01

1704-02-13



PMI ENGINEERING ORDER (EO) AND JOB CARD PROCEDURES

1. General

A. The Engineering Order (EO) is an official medium used by Maintenance Programs to issue and authorize specifications and specification changes to the ABX Air Maintenance Program.

B. The EO is the mechanism which allows for tracking and scheduling of aircraft maintenance tasks. The EO also provides for aircraft and component maintenance, modification, repair, and overhaul specifications by the defined work instructions in the PMI jobcards.

C. Maintenance Programs is responsible for developing the complete modification process for all requirements including, but not limited to, external originating documents and ABX internal requirements which are defined as not having terminating action.

D. The ABX AS400 computer PMI software database, hereafter called PMI, is the tool for creating and maintaining EOs.

E. There are three types of ‘work requirement’ EOs which are created by the Maintenance Programs Department. They are as follows:

(1) “CHK” EOs are used to accomplish routine tasks at an assigned interval.

(2) “N” EOs consists of items that have time intervals which may not coincide with any other scheduled maintenance program interval, or are of such nature that special handling is required.

(3) “J” EOs are used to accomplish the removal and replacement of components during scheduled and unscheduled maintenance. These tasks can have an assigned interval or can be accomplished at any time.

F. EOs can be revised or updated after the initial release of the EO to make any necessary changes. See paragraph 3 for EO revision and update procedures.

CHAPTER:

SECTION:

PAGE:

15

2

REV. NO.:DATE:

01

1704-02-13


2. Creating EOs (See Figure 1)

A. All EOs regardless of type, are created in the same manner. Refer to GMM Chapter 1, Section 07.16 for standard EO entries.

(1) E.O. Code: Required entry, see PMI inquiry menus for EO Codes.

(2) CHP: ATA Chapter, required entry, see PMI inquiry menus for standard ABX ATA Chapter numbers and descriptions.

(3) SEC: ATA Section, required entry, see PMI inquiry menus for standard ABX ATA Section numbers and descriptions.

(4) SEQ: EO sequence number PMI System generated.

(5) REV: EO Revision, $=Initial Release, subsequent revisions will be listed as alpha characters beginning with A.

(6) Description: Enter title of what the EO is to accomplish.

(7) Prepared by: Enter initial of first name and complete last name

(8) Applicable: Enter “Y” or “X”. If the EO is applicable to the ABX fleet and the limits against that EO (hours, cycles, or days) is based on the total accumulated hours, cycles, or days against the aircraft or serialized rotable component, put an “X” in the Applicable field. If the EO applicability is based on time other than airframe or serialized rotable total accumulated time enter a “Y”. Enter “N” if EO does not apply to ABX aircraft or components.

(9) Mandatory: Enter “Y” if EO is mandatory by an AD or other FAA requirements for accomplishment to applicable ABX aircraft or components. Enter “N” if EO is not mandated by regulatory requirements.

(10) MEMO: Enter “Y” to go to the EO memo section. The EO memo will consist of the following sections and headings (additional sections and headings can be added as required for a particular project):

NOTE: All memo section headings should be used, but are not required.

(a) DESCRIPTION - Brief description of what EO is to accomplish or what work is to be done.

CHAPTER:

SECTION:

PAGE:

15

3

REV. NO.:DATE:

01

1704-02-13


(b) REASON - Reason for requiring compliance with this EO.

(c) STATEMENT OF COMPLIANCE - If the EO complies with any part of an official FAA or manufacturer’s document, a specific Statement of Compliance must be entered. Include all document revision levels, amendments and dates within the Statement of Compliance.

NOTE: Example: “Compliance with this EO, accomplishes the intent of SB B767-57-123 R4, dated 05-10-96.”

(d) REFERENCE - Include miscellaneous information which may be pertinent to the EO.

(e) REVISION HISTORY - List revision history of the EO.

1 The revision history will include the date of the EO update followed by description followed by initials of individual updating EO.

(11) Internal REF: Not currently used for new EOs, certain EOs will contain reference to previous EO’s. This is due to a conversion process which created EO numbering for the old system.

(12) Check Value: Check definition fleet, type, value.

(13) Task Type: EO Line of work code, enter task type code to identify at what type of maintenance visit the EO should be accomplished. See PMI inquiry menus for task type codes and descriptions.

(14) Task: EO Task number, created by the PMI system, consists of the EO code and system generated sequence number.

(15) NXT Task: If a related task (EO) must be scheduled contingent on accomplishment of the current task, the next EO task number is entered here. The PMI system will automatically schedule the next task when the current task is completed. The next task to be accomplished must exist in the PMI system with a start accumulation date of 99999999 in order to be accepted in this field.

(16) Ground Time REQ: Enter the estimated total down time required for the completion of the EO. Time estimation is entered in hours and minutes and includes and/or assumes the following:

CHAPTER:

SECTION:

PAGE:

15

4

REV. NO.:DATE:

01

1704-02-13


(a) All parts and materials are on hand.

(b) The EO is the only work to be performed on aircraft or component.

(c) Preparation of modification, defueling, purging, placing work stands, opening standard access doors, and jacking when essential to the modification.

(d) Nonproductive elapsed time; sealant or adhesive cure time, cleaning, paint drying time, lunch and/or rest periods, and quality control inspections.

(e) Productive elapsed time; actual completion of work steps, Engineering liaison and shift change coordination.

(17) Start ACCUM Date: Enter the date from which hours/cycles/days will be tracked against established limits.

(a) If accomplishment of the EO is only based upon the findings of another EO or inspection requirement, the Hours/Cycles/Days fields are left at “0” for both 1st and repeat fields with “Start Accumulation Date” left blank (will be completed by the system).

(b) If accomplishment of the EO is based on the findings of another EO or inspection requirement but has a specific Hour/Cycle/Days limit, input the specified limit and set the start accumulation date to all 9’s. This will cause the EO to show inactive until a valid start date is set via a “records” card or override.

(18) 1st Hours: Enter the latest hours at which an EO may be accomplished.

(19) 1st Cycle: Enter the latest cycles at which an EO may be accomplished.

(20) 1st Days: Enter the latest days at which an EO may be accomplished.

(a) The 1st Hours/Cycles/Days requirement must exist if used with the repeat Hours/Cycles/Days. If there is a repetitive requirement to accomplish an inspection every 1000 hours the 1st hours must indicate 1000 and the repeat must also indicate 1000 under the hours heading.

CHAPTER:

SECTION:

PAGE:

15

5

REV. NO.:DATE:

01

1704-02-13


(21) Complete By Date: Enter the date the EO is to be completed by (if any). This field overrules any Hours/Cycles/Days specifications. If the maintenance requirement calls for 1000 hours, and 01/01/1996 is entered in the complete by date, the PMI system will schedule the EO by the date and ignore the hour limit.

NOTE: If the limits for compliance specify cumulative hours or a specific date, whichever comes first, the restriction may be overridden. Calculate the number of days from the “Start Accumulation Date” to the “Complete By Date” and enter that number in the “Days” field. Enter the hours limitation in the “Hours” field. Leave the “Complete By Date” field blank.

(22) Repeat Hours: Enter the hours the EO will be due on a repetitive basis.

(23) Repeat Cycle: Enter the cycles the EO will be due on a repetitive basis.

(24) Repeat Days: Enter the days the EO will be due on a repetitive basis.

(a) Repeat requirements will become effective after the 1st. Hours/Cycles/Days requirement is met. The 1st. Hours/Cycles/Days must be used to schedule the first time the EO must be accomplished.

(25) G/L: Field used for accounting purposes.

(26) Co-Compliant Tasks: A task where the intent of that task is embedded within another task. When a task that has a Co-Compliant task is accomplished, the system will write a compliance record for both the Primary and Co-Compliant tasks and perform necessary system updates for those tasks. There can be multiple Co-Compliant tasks for a task.

(a) When Task “A” requires the same work to be accomplished as defined within Task “B”, the Co-Compliant task field is selected in Task “A” and the EO task number for Task “B” is entered on the next screen.

(b) Task “A” and “B” must have the same effectivities (i.e. aircraft to aircraft or P/N and S/N to P/N and S/N).

CHAPTER:

SECTION:

PAGE:

15

6

REV. NO.:DATE:

01

1704-02-13


(c) A task that has a Co-Compliant task can not have conditional criteria. When Task “A” is accomplished, the intent of Task “B” is always accomplished without exception.

NOTE: EXAMPLE: A C-Check task contains the intent of A-Check and Service Check tasks. The C-Check task contains the Co-Compliant task numbers. When the C-check task is accomplished, the computer creates compliance records for the C-Check, A-Check, and Service Check tasks; performs any updates such as re-setting Start Accumulation dates for all defined tasks.

(27) Engineering Order Document REF: The EO Document Reference section is used to reference document numbers, document revision levels, and document dates. The revision level of the OD which is being used for compliance must be specifically referenced by the EO (i.e. no generic references to Service Bulletins).

(a) Enter “Y” to open the document reference section of the EO. Each data line in the Document REF section contains four data fields: Type, Document REF, Revision, and Date.

1 Type – Type of document referenced, AD, SB, DR, OT

a AD - Airworthiness Directive

b SB - Service Bulletin

c DR - Drawing

d OT – Other

2 Document REF – Document number being referenced

3 Revision – Revision level of document number being referenced.

4 Date – Date of referenced document revision.

(b) AD – Airworthiness Directive. EO’s complying with a specific AD requirement must be referenced with a Document Type of “AD”. Previous AD’s which have been superseded or require reference in a particular EO to tie it to another EO, must be referenced with a

CHAPTER:

SECTION:

PAGE:

15

7

REV. NO.:DATE:

01

1704-02-13


Document Type of “OT”. If the required AD reference for the EO is unclear or special circumstances are involved, contact ABX Quality Control to determine the ABX AD compliance reporting requirements.

(c) SB – Service Bulletin. Service Bulletins are referenced as “SB” Document Types. The SB number is referenced in the Document REF field. SB revision level is referenced in the Revision field, and the release date is referenced in the Date field. All SB “Original Releases” or “Initial Releases” are referenced with a “$” in the revision filed. Subsequent SB revision levels are referenced with 1, 2, 3 or A, B, C etc. depending upon the manufacturer’s revision sequencing method.

(d) OT – Other. All other document references, EO Classification, labels, identifiers, or flags will be entered using “OT” as the Document Reference Type

(28) Effectivity For A/C: Enter “Y” to display the ABX aircraft listing. Enter “Y” for each aircraft EO is effective.

NOTE: When establishing EO effectivity for aircraft parts, it is essential to check for all variations of applicable P/N entry into PMI part master file. Base part numbers listed in an originating document may be in PMI with suffixes (i.e., P/N 5910081-105, 5910081-105-ABX, and 5910081-105ABX1) or have cross references to specification numbers (i.e., P/N BDC5 and specification S283T019-4). Perform part master file inquiry and determine all applicable OEM part numbers, variations of part numbers and specifications (if applicable) to be made effective to the EO.

(29) Effectivity For Part: Enter “Y” to display part listing for aircraft components.

NOTE: Load At Receiving default is set to “Y”. If it remains “Y” when Vendor P/N is entered, Load At Receiving will be set for the Vendor P/N entered. If Load At Receiving is not required for the Vendor P/N, remove the “Y” by entering a space.

NOTE: Enter Vendor P/N or Part Code to obtain list of serial numbers in PMI. Enter “Y” for each serial number (S/N) part EO will be effective. Enter “Y” to confirm P/N and S/N effectivity. Repeat to include all applicable part numbers and Load At Receiving as required.

CHAPTER:

SECTION:

PAGE:

15

8

REV. NO.:DATE:

01

1704-02-13


(30) Revision Date: Date EO was created (PMI system generated).

(31) Cancel: - Enter “Y” to cancel the EO. Canceling an EO removes any open effectivity but retains history of EO accomplishment.

Engineering Order Entry/UpdateFigure 1

CHAPTER:

SECTION:

PAGE:

15

9

REV. NO.:DATE:

01

1704-02-13


3. EO Updates, Revisions

A. EOs may need to be updated or revised.

B. The EO requires revision to the next revision letter if:

(1) It is determined that the revision provides a greater benefit for tracking or compliance requirements compared with an EO update.

(2) Rework is required to aircraft in compliance with a previous EO revision.

(3) The intent of the EO is changed.

C. EO changes outside of the EO revision process will be considered EO updates.

D. If an EO is revised/updated due to the AD being superseded or rescinded, the “AD” in the Type field of Document Reference is changed to “OT”. If there is a superseding AD, and the EO meets the compliance requirements of the superseding AD, another document reference line is added to reference the superseding AD.

E. An EO update is defined as any change required to an EO which does not require a complete revision.

NOTE: EO updates are not required when Job Cards are being added to new part and serial numbers that were added by the “Load At Receiving” function of PMI.

(1) The EO update information will be communicated in the EO memo revision history section. The EO update revision history information will be entered as a dated sub-entry of the EO revision letter (Example: 3-28-02 - Updated EO to add SB 767-53-0088 to document reference).

4. EO Task Deletion, Cancellation, and Re-Activation

A. Terms

(1) The status of an EO Task may change over time for various reasons. The following terms describe the status of an EO Task which is no longer considered active:

(a) DELETED – An EO Task that may or may not have been authorized that does not have an EO Task compliance. This includes tasks which were made effective but never accomplished. Deleted EO Tasks are erased in

CHAPTER:

SECTION:

PAGE:

15

10

REV. NO.:DATE:

01

1704-02-13


their entirety from PMI and the Task number is not able to be re-issued. Some examples for EO Task deletion are as follows:

1 The EO Task was started but determined it was no longer needed.

2 The EO Task was completed, authorized, but never accomplished on an aircraft or component when requirements changed, eliminating the need for the EO Task.

3 EO Task was written but never issued when Engineering procedures changed, eliminating the need for an EO Task.

(b) CANCELLED – An EO Task that has been authorized and issued, but has been determined that this task is no longer required. An EO Task that has been cancelled remains in the PMI system, EO Task compliance records are retained, and EO Task active effectivity and load at receiving effectivity are deleted. A cancelled EO Task may be returned to active status by performing the re-activation procedures. Some examples for EO Task cancellation are as follows:

1 The EO Task has been replaced by another EO Task.

2 The work performed by the EO Task is still valid and acceptable, but this specific EO Task will no longer be issued.

3 The EO Task has been repealed or authority to perform the specified work has been withdrawn.

4 An EO Task has been revised and the previous EO Task will be cancelled during the new EO Task approval process.

5. EO Task Deletion

A. Before performing EO Task deletion, it is important to determine if the Task has had a previous compliance. If the EO Task has a previous compliance, do not perform EO Task deletion, refer to EO Task cancellation procedures for EO Tasks with compliance. If the EO Task has no compliance, ensure that the EO Task has not been assigned to a Work Order. If it has been assigned to a Work Order and EO Task deletion is desired, contact the Work Order creator to remove the EO Task from the Work Order.

(1) To delete an EO Task, perform the following PMI steps:

CHAPTER:

SECTION:

PAGE:

15

11

REV. NO.:DATE:

01

1704-02-13


(a) From the PMI Engineering Menu (option 33), select EO Entry/

(b) Update (option 12) and press ENTER. Enter the EO number or Task number and press ENTER (if EO number was entered, it will be necessary to select the appropriate Task from the pop-up dialogue box and press ENTER).

(c) Enter “U” for updating EO and press ENTER.

(d) Press F23 (shift and F11) Delete.

(e) Enter “E” for entire EO and press ENTER. (This option will only delete the affected EO Task. Other Tasks of the same EO number will not be affected.)

6. EO Task Cancellation

A. Before performing EO Task cancellation, it is important to determine if the Task has had a previous compliance. If the EO Task has not had a previous compliance, the Task may be deleted. Ensure that the EO Task has not been assigned to a Work Order. If it has been assigned to a Work Order, and EO Task cancellation is desired, contact the Work Order creator to remove the EO Task from the Work Order.

(1) To cancel an EO Task, perform the following PMI steps:

(a) From the PMI Engineering Menu (option 33), select EO Entry/ Update (option 12) and press ENTER.

(b) Enter the EO number or Task number and press ENTER (if EO number was entered, it will be necessary to select the appropriate Task from the pop-up dialogue box and press ENTER).

(c) Enter “U” for updating EO and press ENTER.

(d) Enter “Y” in the MEMO field and press ENTER.

(e) Edit the MEMO revision history to include cancellation date, reason for cancellation, and initials of person canceling the EO. Press F3 to exit the MEMO field.

(f) Enter “Y” in the CANCEL field and press ENTER.

CHAPTER:

SECTION:

PAGE:

15

12

REV. NO.:DATE:

01

1704-02-13


(g) Enter “Y” for yes in the UPDATE field and press ENTER.

(h) Enter “E” for entire EO and press ENTER. (This option will only cancel the affected EO Task. Other Tasks of the same EO number will not be affected.)

7. EO Re-Activation

A. Cancelled EOs can be re-activated if the need arises to perform the same task.

(1) From the PMI Engineering Menu (option 33), select EO Entry/Update (option 12) and press ENTER.

(2) Enter the EO number or Task number and press ENTER.

(3) Enter “U” for updating EO and press ENTER.

(4) Enter “Y” in the MEMO field and press ENTER.

(5) Edit the MEMO revision history to include re-activation date, reason for re-activation, and initials of person re-activating the EO Task. Press F3 to exit the MEMO field.

(6) Determine effectivity desired A/C or Part and enter “Y” in the appropriate field. Set effectivity as required.

(7) Remove the “Y” in the CANCEL field by pressing the space bar and press ENTER.

(8) Enter “Y” for yes in the UPDATE field and press ENTER.

(9) If required, assign Job Cards to EO Task.

8. Creating Job Cards

A. Refer to GMM Chapter 1, Section 07.12 for Job Card format and description.

B. As a general rule Job Cards are created for each skill level. Although general inspection steps do not require a separate Job Card.

C. Multiple Job cards can also be created to accomplish different tasks within an EO requirement to keep work sequence organized.

CHAPTER:

SECTION:

PAGE:

15

13

REV. NO.:DATE:

01

1704-02-13


D. If work accomplishment involves multiple positions (e.g., No. 1 engine, No. 2 engine, or Left and Right, etc.) separate Job Cards must be created.

E. If an EO is incorporating a Service Bulletin which may be previously incorporated, the Job Card work instructions must verify the status by using a method of indicating previous compliance (e.g., part number check, physical appearance, dimension check etc.) A statement such as “verify if this SB is complied with” is not acceptable.

(1) This type of Job Card set-up will avoid “PCW” entries in a Job Card work step.

F. It will not be necessary to create work steps which remove and/or reinstall standard aircraft access panels. This will be handled by the PMI Job Card access panel reporting feature of the PMI system.

G. Creating Job Cards

(1) The Job Card Entry/Update screen (see Figure 2) is used to create the Job Card as referenced in GMM Chapter 1, Section 07.12.

(2) The procedures which follow are used to create Job Cards using the Job card Entry/Update screen.

(a) Job Card: - (1) - Job card number is displayed

(b) Description: (2) - Enter description of what the Job Card is to accomplish.

(c) Revision NO: (3) - Enter the Job Card revision letter. The initial release of the Job Card will be denoted as “$” and subsequent revisions will be listed as alpha characters beginning with “A”.

1 Once the Job Card has reached a revision letter of “Z”, the subsequent revision level will be listed as alpha characters beginning with “AA.”

(d) Date: (4) - Date Job Card is created, system generated.

(e) Area: (5) - Enter a brief description of the general area of the aircraft the Job Card work is to be performed.

CHAPTER:

SECTION:

PAGE:

15

14

REV. NO.:DATE:

01

1704-02-13


(f) Labor Code: (6) - Enter the Job Card labor code for the skill level required to accomplish the Job Card, see PMI inquiry menus for effective labor codes and descriptions.

(g) Estimate Man Hours: (7) - Enter the estimated man-hours required to perform the Job Card in hours and minutes.

NOTE: See GMM Section 01.04 for definition of man-hour.

(h) Man Require: (8) - Enter the number of people required to accomplish the work requirements of the Job Card.

(i) Schedule: (9) - Enter Job Card schedule code. This field is used as an aid to help determine when Job Card should be accomplished during an aircraft maintenance visit. ABX schedule codes are as follows:

1 05 - Planning

2 10 - Pre-dock

3 15 - Pre-mod

4 20 - Dock

5 30 - Prep for Inspection

6 40 - Inspect

7 50 - Work

8 60 - Corrosion Treat

9 70 - Final

10 80 - Shot Peening

11 90 - Records Instructions

NOTE: Other schedule codes exist which are used for Work Control Center scheduling. These are not used by Engineering.

CHAPTER:

SECTION:

PAGE:

15

15

REV. NO.:DATE:

01

1704-02-13


(j) N.D.T: (10) - Enter “Y” if Job Card performs any type of non-destructive testing procedures. This flag is used to compile Job Card reports which require NDT procedures.

(k) No Go Item: (11) - Not currently used by ABX.

(l) Corrosion: (12) - ---------------------------------------

(m) SSID: (13) - Not currently used by ABX.

(n) Conflict Job Card: (14) - Enter a Job Card number which contains the exact requirements as this Job Card.

NOTE: Example: if this Job Card performs a specific test or procedure, and the same test or procedure is included in another Job Card, the PMI system will drop this card from a work package.

(o) Manufacture Job Card: (15) – Originating document/task card.

(p) Interval: (16) – Task interval.

(q) Zones: (17) - Enter “Y” to go to the Zone entry screen. Enter the area(s) and zone(s) of the aircraft where the Job Card work will be accomplished. Use the aircraft manufacturers standard area(s) and zone(s). PMI inquiry menus can also be used to list effective areas and zones. Area is listed first and the zone after the “/”.

NOTE: Example: Area 4, Zone 7. Would be entered as 04/007.

(r) Access Panels: (18) - Enter “Y” to go to the Access Panel entry screen. List the access panels required to be removed or doors to be opened to perform this Job Card, not all panels required to perform the EO. PMI inquiry menus can also be used to list access panel numbers.

1 The aircraft manufacturers access panel manuals are used to identify panels. ABX specific panels such as gilliner and floor panels can be found in the ABX Diagram Manual for each aircraft.

2 Access panels listed for gilliner and floor panels indicate the area to be accessed, not the actual area the section of gilliner or floor

CHAPTER:

SECTION:

PAGE:

15

16

REV. NO.:DATE:

01

1704-02-13


panel is covering due to variance in aircraft configurations. Sections of gilliner or floor panels may require only partial removal to access area required.

(s) Spare Parts/Tools: (19) - Enter “Y” to go to the Parts/Tooling Requirements screen. Enter part numbers and tool numbers required to accomplish the work requirements of the Job Card. Only the part numbers required to accomplish the Job Card are entered. List only special or unique tools required to accomplish the Job Card.

NOTE: If generic/standard type tooling must be listed on a Job Card, the tooling can be listed within the work instructions.

1 Only the part number and quantity is required to be entered. If the item is listed in inventory, the part number will be accepted and the part nomenclature and part code information will be entered by the PMI system.

a |LG AS REQD| - Actual fastener length required may vary from listed fastener.

b |IF REQD, INSP| - Part may be required depending upon inspection findings.

c |QTY AS REQD| - Actual quantity listed is estimated (used for consumable or bulk items).

d |TOOLING| - If listed item is a tool. If equivalent tools are available, add |OR EQUIVALENT| to the description of the tool.

e |FAB| - If part is designed by ABX and/or not commercially available.

f |QTY/LG AS REQD| - Quantity and length listed are estimates and may vary from actual usage.

g |FAB MATL| - If listed material is needed to fabricate another part.

(t) Maintenance Manual: (20) - Enter “Y” to go to the Maintenance Manual entry screen. Enter only Maintenance Manual references listed as

CHAPTER:

SECTION:

PAGE:

15

17

REV. NO.:DATE:

01

1704-02-13


required for accomplishment in the text of the Job Card. If the Job Card is related to the ABX Maintenance Inspection Program (MIP) a MIP reference number must be entered here.

(u) Job Card Description: (21) - Enter “Y” to go to the work instruction entry section of the Job Card. The Job card work instructions are entered in this section. There is an on-line help feature available to help with text editing.

1 Enter the work compliance instructions allowing for appropriate sign-off. The individual items should be broken down into work steps, which can be completed in approximately an eight-hour shift. If necessary the work steps can be divided further if the nature of the work requirement dictates the need.

2 Each work step will require a Mechanic and/or Inspection signoff space be provided in the right-hand columns of the Job Card. These are created by the system by inserting the command in the proper position of the description field. Enter one blank line immediately following the text of the work step. In the first column, enter &M for Mechanic’s sign-off or &I for Inspection sign-off.

3 Requirements for Quality Control (QC) Sign-Off:

a Verification of installed part number and serial number (for regulatory compliance issues only), adjustments and rigging, installation tests/checkouts, Required Inspection Items (ref. Chapter 01, Section 12), or any other item that requires verification of conformity or safety.

b QC Sign-off is not required for items that do not require verification as described above. QC does not oversee the complete task in process. Their responsibility is for specific items only as indicated by the sign-off column.

(v) Attachment: (22) - Enter “Y” to go to the Job Card Attachment screen. Job Card attachments are any required documents needed to accomplish the work requirements of the Job Card.

(w) Memo: (23) - Enter “Y” to go to the Job Card memo screen. The Memo will contain a brief description of the card and the revision history.

CHAPTER:

SECTION:

PAGE:

15

18

REV. NO.:DATE:

01

1704-02-13


1 The description will provide a short description of what the Job Card accomplishes.

(x) User CRT: (24) - Computer ID of current user (entered by system).

(y) User Last UPD: (25) - User name of person who last entered information to the Job Card. (Entered by system).

(3) After all Job Card entries are completed the Job Card must be assigned to the EO. The Job Card is assigned to the EO by assigning it to the associated task number.

(a) Press enter at the Job Card entry/update screen.

(b) Select Assign to Task by entering “Y” and enter.

(c) Enter the EO task number.

(d) All aircraft made effective for the EO will be displayed. Enter “Y” for each aircraft the Job Card will be effective for and then update Job Card effectivity.

CHAPTER:

SECTION:

PAGE:

15

19

REV. NO.:DATE:

01

1704-02-13


Job Card Entry/UpdateFigure 2

CHAPTER:

SECTION:

PAGE:

16

1

REV. NO.:DATE:

01

1905-13-16



MAINTENANCE PROGRAMS STYLE GUIDE

1. General (Ref. MNT 1.3.2)

A. This section is intended to provide guidelines to facilitate standardization of information in the production of ABX documents and publications by the Maintenance Programs Department. These guidelines represent the ABX preferred style, and include only those features that are frequently questioned. Precise word usage, proper capitalization, careful spacing, and accurate punctuation are highly important in technical writing.

B. These guidelines have been intentionally written in general terms, and in most cases conform to recognized industry and/or company practices. Should there be questions which are not specifically covered by these guidelines, common sense and direct comparison to existing document format, text, and content should provide a satisfactory guideline to answer the question.

C. This Style Guide is not intended to be a complete or comprehensive document on common English usage on any of the topics covered. This Style Guide is not a complete substitute for any required specification or standard. It is intended only to highlight and summarize the important elements of technical writing style.

D. This Style Guide considers the following Human Factors issues:

(1) Layout of a maintenance item

(2) Language used

(3) Clear and concise instructions that are as brief and succinct as possible.

(4) Standardization of all task cards at the beginning to include the appropriate personnel safety warnings and cautions

(5) All notes, warnings, and cautions are apparent to the reader.

(6) Clear instructions for the mechanic/inspector as to where to sign, certify, initial, date the task.

(7) Where a Maintenance Item has important graphic details, the graphics are included in the appropriate diagram manual.

CHAPTER:

SECTION:

PAGE:

16

2

REV. NO.:DATE:

01

1905-13-16


(8) Full amplification of some tasks rather than referral to a separate document that may distract the mechanic.

(9) Referral to the applicable Approved Data.

2. Presentation Methods

A. Text Content

(1) Writing should follow ATA 2200 Specification whenever possible.

(2) Writing should follow Simplified English whenever possible.

(3) Text shall be as brief and concise as practical. Discussions of theory shall be avoided except where essential for practical understanding and application.

(4) All related data should be grouped in a logical manner.

(5) All formatted paragraph text should be plain, 12 point, Times New Roman script, unless otherwise noted.

B. Text Style

(1) Wording

(a) Use the simplest common words and phrases which convey the intended meaning.

(b) Common (user, industry, company) jargon may be used whenever it makes material easier to understand.

(c) Use words that are concrete rather than vague, specific rather than general, or familiar rather than formal.

(d) Words or phrases that are subject to interpretation should be avoided.

(e) Key words that may be understood in more than one sense should be defined.

(f) Words which are easily misinterpreted or unfamiliar should be avoided.

(g) Words used in titles should be brief, accurate, and specific.

CHAPTER:

SECTION:

PAGE:

16

3

REV. NO.:DATE:

01

1905-13-16


(h) The words “shall/will” indicate a mandatory requirement.

(i) The word “should” indicates a non-mandatory desired/preferred method, procedure, or practice.

(j) The word “may” indicates an acceptable or suggested method.

(2) Sentences

(a) Sentences should be short, simple, and as concise as practical.

(b) A sentence should start with what the reader first needs to know or remember to understand the sentence.

(c) Parts of a sentence should be arranged so the meaning of the sentence is clear when first read.

(d) Write only one topic per sentence whenever possible. Unrelated topics shall not be combined in one sentence.

(e) Write only one instruction per sentence whenever possible. Unrelated thoughts should not be combined in a compound sentence.

(f) When two actions have to be done at the same time, write more than one instruction per sentence when necessary.

(g) Use connecting words to join separate sentences and to make the relationship between sentences/paragraphs clear.

(h) Any sentence that is confusing, illogical, awkward, obscure, or may be misunderstood by the user should be rewritten.

(i) Break up long sentences using words such as “and”, “but”, “if”, and “also.” Breaking a sentence at these words will usually require the addition of a pronoun such as “it”, “they”, “this”, or “these”, and/or a noun.

(j) Use tabular layout (vertical layout) for complex text.

(k) The maximum length of a sentence is normally 20 words.

CHAPTER:

SECTION:

PAGE:

16

4

REV. NO.:DATE:

01

1905-13-16


(3) Paragraph Style and Outline

(a) Material should be prepared in a modified block style.

(b) Text subdivisions should be identified and each breakdown indented as shown below:

(c) Each paragraph should deal with only one topic or idea.

(d) Each paragraph should always start with the topic sentence.

(e) Paragraph sentences should show text in logical order.

(f) One sentence paragraphs should be avoided whenever possible.

(g) Paragraph length should be a maximum of 6 sentences whenever possible.

(4) Titles

(a) The full name of the subject/unit/system should be shown in the Primary Heading of the text.

(b) If the full name of the unit is susceptible to abbreviation for common usage, the abbreviation should also be shown (in parenthesis) in the title.

(c) The lead title of major text subdivisions should indicate in a brief descriptive phrase the subject covered or the function performed.

TITLE

1. Major Breakdown (with capitalization and underline)

A. Major Subdivision (with first letter capitalized)

(1) Steps of procedures

(a) Any necessary further breakdown

1 Any necessary further breakdown

a Any necessary further breakdown

CHAPTER:

SECTION:

PAGE:

16

5

REV. NO.:DATE:

01

1905-13-16


(5) Person and Voice

(a) Procedures use only the active voice and present tense. This creates clear and concise procedures by simplifying direction and sentence structure.

(b) Tense denotes time, either present or passed.

(c) Descriptions and Operations use the active voice as much as possible. Use the passive voice only when absolutely necessary.

(d) In the active voice the subject of the sentence does the action (denotes activity).

(e) In the passive voice the subject of the sentence suffers the action (acted upon).

(f) Use the passive voice when:

1 Object/receiver of the action is more important than the doer.

2 Doer of the action is unknown.

3 Emphasis is placed on the receiver instead of the doer.

(g) To change a passive voice to the active:

1 Change the subject at the beginning of the sentence.

2 Change an infinitive verb to an action verb.

3 Change the verb to the commanding form.

4 Use the personal pronouns “we” or “you.”

(h) Second person imperative should not be used for major breakdowns or subdivisions.

(i) The third person imperative should be used for descriptive discussion.

CHAPTER:

SECTION:

PAGE:

16

6

REV. NO.:DATE:

01

1905-13-16


(6) Nomenclature and Abbreviations

NOTE: Also see “Abbreviations and Acronyms.”

(a) Nomenclature and abbreviations should be consistent throughout all technical data for all systems, components, parts, etc. for maintenance practices or procedures.

(b) Nomenclature and abbreviations should be consistent with all wording, placards, etc. as displayed on the aircraft.

(c) Nomenclature and abbreviations used should be common to the industry, well understood, and have only one meaning.

(d) Nomenclature should conform to a recognized standard.

(e) Abbreviations should conform to a recognized standard.

(f) Nonstandard abbreviations that spell simple words should not be used.

(7) Numerals

(a) Numbers should be expressed in numeral form when it is a:

1 Single number greater than nine (unless it is the first word of a sentence)

2 Serial Number

3 Part Number

4 Page number

5 Unit of measurement

6 Unit of time

(b) Numbers should be spelled out if it is:

1 A single number of nine or less

2 The first word of a sentence

CHAPTER:

SECTION:

PAGE:

16

7

REV. NO.:DATE:

01

1905-13-16


3. Punctuation

A. General

(1) Punctuation marks are used to show how parts of the text are related to each other.

(2) Punctuation marks help to make text more readable and help make the meaning clear.

(3) Punctuation marks must not be scattered in the text according to the writer’s taste.

B. Types and Usage

(1) Apostrophes

(a) Use apostrophes to show possession and contractions.

(b) Do not use apostrophes to pluralize an acronym, e.g., MFDs, not MFD’s.

(2) Brackets

(a) Use brackets only in mathematical equations.

(b) Do not use brackets to avoid parentheses within parentheses. Rewrite the sentence.

(3) Colons

Use colons to:

(a) Show that text/material is to follow.

(b) Indicate a series, list, or complete sentence.

(c) After a salutation

(d) Express a clock time.

(e) Separate book titles and sub-titles.

CHAPTER:

SECTION:

PAGE:

16

8

REV. NO.:DATE:

01

1905-13-16


(4) Semicolons

Use semicolons to:

(a) Separate clauses containing commas.

(b) Set off explanatory abbreviations or words that summarize or explain preceding information.

(c) Separate compound sentence clauses where usual conjunction (such as “and”, “but”, etc.) has been omitted.

(d) Separate groups of similar or related items in run-on lists.

(e) Separate tabular entries or procedural items that do not form complete sentences.

(f) Separate relatively simple tabulation of short sentences.

(5) Commas

Use commas to:

(a) Separate two words or numbers that might otherwise be misunderstood; e.g. Instead of 20, 50 arrived.

(b) Complete dates within a sentence; e.g. Sept. 4, 1995.

(c) Set off an introductory clause or phrase; e.g. Since we have seen this before, we will discuss this.

(d) Complete a conditional statement with “if” or “when” phrase; e.g. If you can’t go, I will.

(e) Separate items in a series, including prior to the conjunction before the last item listed; e.g. Red, white, or blue.

(f) Separate four or more digits of a number; e.g. 1,400,635.

(g) Between the title and name of a person; e.g. John Doe, Lead Mechanic.

CHAPTER:

SECTION:

PAGE:

16

9

REV. NO.:DATE:

01

1905-13-16


(6) Hyphens

(a) Use hyphens to join two or more words.

(b) Do not hyphenate compound words.

(c) Avoid using hyphens at syllable breaks in words at end of a typed line of text.

(7) Parenthesis

Use parenthesis to:

(a) Specify an acceptable range or tolerance.

(b) Set off explanatory information.

(c) Set off text that is not part of the main statement but is important enough to be indicated.

(d) Mark text for which separation by commas is insufficient.

(e) Mark condensed figure/text references.

(f) Mark letters or numbers that indicate items of a list within a sentence, or that indicate steps of a procedure.

(g) Set off text within parentheses.

(h) Set off a complete sentence within a sentence.

(8) Periods

(a) Use period to:

1 End a sentence.

2 Set off titles; e.g. Dr., Mr., Mrs., Ph.D.

3 After an abbreviation that spells a word

CHAPTER:

SECTION:

PAGE:

16

10

REV. NO.:DATE:

01

1905-13-16


4 After each sentence of a WARNING, CAUTION, NOTE, or Footnote.

5 After a parenthetic entry that forms a complete sentence (within closing parenthesis).

6 After each tabular entry which is a long, complete sentence.

7 After a group of words that immediately precedes a complete sentence.

8 After each paragraph number, paragraph heading, or figure number in headings and/or titles in text.

9 After a letter or number denoting a series.

(b) Do not use period after:

1 Lines in title pages

2 Headers

3 Symbols

4 Acronyms

5 Figure title, section number, or section title

6 Figure number and/or title in list of illustrations

7 Abbreviations, except as noted above

8 Parentheses entries if not a complete sentence

9 List of entries if none of the entries are complete sentences, or entries are very short. Lists have either periods after each entry or no periods after any entry.

CHAPTER:

SECTION:

PAGE:

16

11

REV. NO.:DATE:

01

1905-13-16


(9) Quotation Marks

NOTE: Use quotation marks sparingly.

(a) Use quotation marks to:

1 Enclose a brief direct quotation.

2 Enclose titles when used in reference.

3 Enclose the first use of slang, jargon, or figurative language. Thereafter omit quotation marks for repeated usage.

(b) Do not use quotation marks to:

1 Show emphasis.

2 Enclose titles of technical manuals or other publications.

3 Enclose controls, control positions, indicating devices, and/or test points.

(10) Underlining

NOTE: Use underlining sparingly so the highlighting effect is not destroyed. Underlining should not be used for emphasis.

Use on:

(a) Titles of other technical manuals or publications

(b) Letters designating items or procedural steps

(c) Primary paragraph headings

(d) Unusually important words or phrases

(11) Slant Line ( / )

Use to indicate:

(a) An either/or relationship in condensed form

CHAPTER:

SECTION:

PAGE:

16

12

REV. NO.:DATE:

01

1905-13-16


(b) “Per” in a condensed matter

4. Capitalization

A. General

(1) Minimize use of capitals. If excessive capitals are used, the contrast, clarity, and/or purpose of capitalization is lost.

(2) Unrestricted use of capitals for other purposes weakens the impact for required uses.

(3) Capitalize to avoid confusion.

(4) Capitalize for formal identification to distinguish one particular object from a general class.

(5) Capitalize for emphasis.

(6) When the word is derived from an individual’s name or title, capitalize to show respect.

B. Usage Modes

(1) All capitals - EVERY LETTER OF EVERY WORD:

(a) Defining special purposes such as WARNINGS, CAUTIONS, and NOTES.

(b) Primary headings

(c) Manual headings

(d) Table titles, if at top of table

(e) Acronyms and initialisms

(f) Abbreviations on illustrations

(2) Initial Capital - First letter of each important word:

(a) Beginning of a sentence/statement

CHAPTER:

SECTION:

PAGE:

16

13

REV. NO.:DATE:

01

1905-13-16


(b) In headings other than primary

(c) Table titles, if at bottom of table

(d) Captions or titles of documents, illustrations, figures, diagrams, etc

(e) Column headings in tables or charts

(f) Personnel or staff titles

(g) Terms expressing modes of conditions of aircraft operation (e.g. Shutdown)

(h) Some abbreviations, in accordance with the same rules that would apply if the words were spelled out

(i) Copyrighted trade names (Freon, Heli-Coil, etc.)

(j) Manufacturers names (Bendix, Honeywell, etc.)

(k) Formal titles of items of formal nomenclature such as Captain, First Officer, Fire Control System, Auto Pilot System, etc., regardless of sentence placement.

(3) First Word Capital - First letter of first word only:

(a) First word of each new sentence or statement

(b) First word in procedure sections and subsections

(c) References to section, step, figure, table, or attachment when followed by a designating number

(d) Each entry in a table, chart, or legend

(e) Each entry in a tool or equipment list

(f) Each item of a formatted list

(g) Single letter in single-letter compound nouns such as X-ray and I-beam

CHAPTER:

SECTION:

PAGE:

16

14

REV. NO.:DATE:

01

1905-13-16


(4) Do not capitalize:

(a) Articles (a, an, the) in titles unless it is the first word in the title

(b) Conjunctions (and, or, etc.)

(c) Prepositions (with, on, between, etc.)

(d) Words that are not proper nouns

5. Change (Revision) Bar

A. Change (Revision) Identification

(1) Definition

(a) A change (revision) bar is a 2.0 weight, black vertical line, located parallel to the edge of revised text or graphic.

(b) Change bars allow immediate identification of the text/graphic which has been revised.

(2) Usage

(a) Change bars should be used to identify:

1 Addition of text which changes the intent or idea of the original sentence or paragraph

2 Deletion of text which changes the intent or idea of the original sentence or paragraph

3 Deletion of text at the end of a paragraph

4 Text pages where revised material has caused unchanged text to appear on a different page(s)

5 Extensive text revision that requires a complete rewrite/retype of an existing section. The change bar should appear the full length of the text

6 Change/revision of a procedure

CHAPTER:

SECTION:

PAGE:

16

15

REV. NO.:DATE:

01

1905-13-16


7 Change/revision of a graphic which changes the intent or idea of the original

8 Deletion of a graphic

9 Addition of a graphic

10 Text revision, addition, or deletion on a graphic

(b) A change bar should not be used to identify the original publication of a document.

(3) Placement

(a) Change bars shall be located 0.10 inches to the left of the text or graphic block.

(b) If text has been deleted at the end of a paragraph, the revision bar shall extend down through the blank space used to separate paragraphs.

(c) Change bar shall be placed beside the page header on all affected pages where the revision has caused unchanged text to appear on a different page(s).

(d) When art in an existing section is revised, revision bar will align parallel to the area of the art revised.

(e) New art added to an existing section will be identified by a full length revision bar parallel to the graphic.

(4) Change bars from the previous revision must be removed prior to application of revision bars for the current revision.

6. WARNINGS, CAUTIONS, and NOTES

A. General

(1) WARNINGS, CAUTIONS, and NOTES must not state or provide a requirement, procedure, direction, or instruction to accomplish and/or comply with a task, work step, or function.

CHAPTER:

SECTION:

PAGE:

16

16

REV. NO.:DATE:

01

1905-13-16


(2) When more than one WARNING, CAUTION, and/or NOTE type statement is required, the statements must be arranged and listed according to their priority of importance as follows:

(a) WARNING(S) - Highest priority; indicates potential for injury to personnel.

(b) CAUTION(S) - Second highest priority; indicates potential for damage to equipment.

(c) NOTE(S) - Third highest priority; provides descriptive, supportive, or explanatory information which assists in the performance or understanding of the procedure or instruction.

B. WARNINGS

(1) WARNINGS call attention to the use of materials, processes, methods, procedures, or limits which must be followed precisely to avoid injury to personnel.

(2) WARNINGS should be located directly above and vertically in line with the numerical or alphabetical breakdown of the text to which the WARNING applies.

(3) Text should be in all uppercase letters to emphasize and highlight the importance of the information provided in the WARNING.

(4) WARNINGS should always be on the same page of text to which the WARNING applies.

C. CAUTIONS

(1) CAUTIONS call attention to the use of materials, processes, methods, procedures, or limits which must be followed precisely to avoid damage to equipment.

(2) CAUTIONS should be located directly above and vertically in line with the numerical or alphabetical breakdown of the text to which the CAUTION applies.

(3) Text should be in all uppercase letters to emphasize and highlight the importance of the information provided in the CAUTION.

CHAPTER:

SECTION:

PAGE:

16

17

REV. NO.:DATE:

01

1905-13-16


(4) CAUTIONS should always be on the same page of text to which the CAUTION applies.

D. NOTES

(1) NOTES call attention to processes, methods, or procedures which make the job easier.

(2) NOTES should be located directly below and vertically in line with the numerical or alphabetical breakdown of the text to which the NOTE applies.

(3) Text should be in all lowercase letters except for the first word in each sentence.

(4) NOTES should be in standard print format using the rules of simplified English.

(5) NOTES should always be on the same page of text to which the NOTE applies.

7. Abbreviations and Acronyms

A. General

(1) When a manual contains a number of terms requiring definition, a glossary should be provided in the front of the manual.

(2) Abbreviation is an accepted shortened form of a written word or phrase used in place of the whole word or phrase.

(3) Abbreviation is something that stands for or suggests something else by reason of relationship, association, convention, or accidental resemblance.

(4) An acronym is comprised of the first letter of each word of a compound term, and is pronounced as a word.

(5) Initializing is comprised of the first letter of each word of a compound term, and is pronounced separately.

B. Abbreviations and Symbols

(1) Abbreviations must be spelled out when first used in a document, then followed by the unit symbol or abbreviaion in parentheses; e.g. Ram Air Temperature (RAT).

CHAPTER:

SECTION:

PAGE:

16

18

REV. NO.:DATE:

01

1905-13-16


(2) Define each abbreviation when first used in a document.

(3) When unit symbols and common abbreviations appear together, they should be separated by a space; e.g. 115V AC. Accordingly, VAC for volts AC is unacceptable.

(4) Abbreviaion shall convey only one meaning. For example, do not use TERM for both terminal and terminate.

(5) Abbreviaion may be used extensively only in tabular matter (charts and tables) to conserve space.

(6) Abbreviations should not be used to begin a sentence.

(7) Abbreviations shall be used in only one form. Do not make it plural or possessive. Be guided by the rule “When in doubt, spell it out.”

(8) Abbreviations shall be consistent with all placards, markings, etc. displayed on the aircraft.

(9) Abbreviations shall be well understood, of common use, and conform to a recognized standard.

C. Acronyms and Initialism

(1) Acronym is pronounced as a word.

(2) Acronym is a word that is formed from the first letters of each word.

(3) Acronyms are written with all letters capitalized; e.g. ADs, SBs, etc.

NOTE: Historically, a popular acronym becomes absorbed into the language and is then written in lower case; e.g. radar, sonar, laser, etc.

(4) Acronyms must be defined (spelled out, present the words of the acronym first) when first used in a document, then followed by the unit symbol or acronym enclosed in parentheses; e.g. Ram Air Temperature (RAT). This should be done even if the acronym’s meaning is common knowledge.

(5) Use acronyms without a period.

(6) Acronyms shall convey only one meaning.

CHAPTER:

SECTION:

PAGE:

16

19

REV. NO.:DATE:

01

1905-13-16


(7) Acronyms can be made plural by adding a lowercase “s.”

(8) Once an acronym is used, use it consistently. Do not alternate between the use of the full term and the acronym.

(9) Apostrophes shall not be used to pluralize an acronym.

(10) Initialism is pronounced individually.

(11) Initialism is comprised of the first letter of each word.

(12) Generally, initialism is referred to as an acronym.

(13) Acronym and initialism rules of use are the same.

CHAPTER:

SECTION:

PAGE:

17

1

REV. NO.:DATE:

01

2703-29-19



ASSOCIATE WRITER PROCEDURES

1. General

A. File Location

(1) FrameMaker files are located at the following path:

(a) ILNSVR07:G:MAMP:PUBN

(2) Graphics are located at path:

(a) G:MAMP:GRAPHICS

2. Standard Publication Revision Process

A. Remove change bars from previous revision.

B. Edit file.

C. Make revised text blue.

D. Put change bar at text and graphics which are revised.

E. Verify correct revision number and date on each page.

F. Update Index/LEP.

G. Update Table of Contents (generated in FrameMaker).

H. Type Revision Highlights.

I. To Issue Completed Revision:

(1) Generate PDF file.

(2) Create bookmarks as necessary.

(3) Add time and date stamp to PDF using Java Script procedures located in G:MAMP:USERS:Moore, Lori:DateStamp Instructions:

CHAPTER:

SECTION:

PAGE:

17

2

REV. NO.:DATE:

01

2703-29-19


(4) Transfer revision PDF file to E-drive to be posted at path:

(a) E:LMP or

(b) E:Other

J. Email Manager when verified posted.

(1) Also attach to email PDF of revision highlights.

K. Final Revision Steps

(1) Sign MPRRs completed.

(2) Attach copy of revised pages to signed MPRR.

(3) Include any subsequent pages marked during revision process.

(4) MPPRs will be scanned by Document Coordinator and saved to G:MAMP:USERS:MPPRs scanned.

(5) Save copy of revision PDF file to appropriate folder at path:

G:MAMP:USERS:Moore, Lori:REVISIONS

3. Maintenance Forms (M-Forms)

A. When maintenance forms are created, revised, or deleted, update GMM forms listing (Section 08.01).

B. Update form illustration and procedures in any other publication in which they appear.

C. Update M-Forms Digital File if necessary.

4. Publications That Require FAA Approval

A. FAA Approval Process

(1) Scan or copy original MPRR and attachments for file folder.

(2) Send PDF of revision file to Manager as email attachment.

CHAPTER:

SECTION:

PAGE:

17

3

REV. NO.:DATE:

01

2703-29-19


(3) Give original MPRR and attachments to Manager.

(4) Give original print of Approval Record to Manager for FAA signature.

B. When FAA approval signature are received:

(1) Scan signature page.

(2) Import into Revision Approval Record document.

5. Publications That Require Distribution of Paper Copies

A. Coordinate revisions with Document/Training Coordinator.

B. Generate PDF file that includes Transmittal and revision pages only.

C. Notify Document/Training Coordinator this file is ready to issue.

6. Job Card Diagram Attachments

A. General

(1) Diagrams are not issued as a published manual, but are programmed to electronically attach to Job Cards.

(2) Diagrams are available as PDF files at path G:MAMP:PUBN:ABX_Diagrams.

(3) Highlights, LEP, Preamble, and Index are not updated/maintained. Revision history is shown by entries in an Excel spreadsheet located at path:

G:MAMP:PUBN:ABX_Diagrams:DIAGRAMS.xlsx.

(a) Column headings are Diagram Number, MPRR number, Added/Deleted/Revised, and date.

(4) Graphics are available at path:

(a) MAMP:GRAPHICS:767:DIAGRAM

(5) FrameMaker files are at path:

(a) MAMP:PUBN:DIAMNL:B767

CHAPTER:

SECTION:

PAGE:

17

4

REV. NO.:DATE:

01

2703-29-19


B. Maintenance Programs Specialist Procedures

(1) Obtain/create diagram.

(2) Save to path G:MAMP:GRAPHICS as .tif file.

(3) Submit request to add/delete/revise diagrams on MPRR to Manager, Maintenance Programs.

C. Associate Writer Procedures

(1) Place diagrams in the standard publishing diagram template.

(a) Header includes ABX logo, diagram number, Aircraft: B767, and page number.

(b) Footer includes MPRR number and date.

(2) Process Diagrams

(a) Add, delete, or revise diagrams as required.

(b) Place added/revised diagrams in folder noted in Item 6.A.(2) above, to attach to Job Cards.

(c) Move deleted diagrams to folder at path:

G:MAMP:PUBN:ABX_Diagrams:OBSOLETE

(d) Document diagram action taken in Excel spreadsheet specified in Item 6.A.(3) above.