BY ORDER OF THE COMMANDER AIR FORCE MATERIAL …

BY ORDER OF THE COMMANDER

AIR FORCE MATERIEL COMMAND

AIR FORCE MATERIAL COMMAND

MANUAL 63-1202

25 JANUARY 2018

Incorporating Change 1, 27 January 2021

Acquisition

AIR FORCE MATERIEL COMMAND

ENGINEERING TECHNICAL

ASSISTANCE REQUEST (ETAR)

PROCESS

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available on the e-Publishing website at

http://www.e-Publishing.af.mil for downloading or ordering.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: HQ AFMC/A4FI

Supersedes: AFMCMAN21-1,

15 January 2005

Certified by: HQ AFMC/A4F

(Mr. Raymond H. Gaier III)

Pages: 55

This publication provides policy, responsibilities, and procedures for implementing and

managing the Air Force (AF) Engineering Technical Assistance Request (ETAR) process and

adheres to the direction of AFI (AFI) 63-101/20-101, Integrated Life Cycle Management; and

AFMC Instruction (AFMCI) 63-1201, Implementing Operational Safety Suitability and

Effectiveness (OSS&E) and Life Cycle Systems Engineering (LCSE). This publication is the

prescribing publication for the AFMC Form 202, Engineering Technical Assistance Request

(ETAR). This publication incorporates the six Centers, three Air Logistics Complexes, and

applies to all AFMC depot maintenance organizations. This instruction does not apply to the Air

National Guard or Air Force Reserve Command units and members. This publication may be

supplemented by AFMC Centers, but all supplements must be routed to the OPR listed above for

coordination prior to certification and approval. Refer recommended changes and questions

about this publication to the OPR using the AF Form 847, Recommendation for Change of

Publication; route AF Forms 847 from the field through the appropriate chain of command.

Submit requests for waivers through the chain of command to this Publication OPR for non-

tiered compliance items. Ensure that all records created as a result of processes prescribed in this

publication are maintained IAW (IAW) Air Force Manual (AFMAN) 33-363, Management of

Records, and disposed of IAW AF Records Disposition Schedule located in the Air Force

Records Information Management System (AFRIMS). See Attachment 1 for a glossary of

http://www.e-publishing.af.mil/

2 AFMCMAN63-1202 25 JANUARY 2018

references and supporting information. The authorities to waive wing/unit level requirements in

this publication are identified with a Tier (“T-0, T-1, T-2, T-3”) number following the

compliance statement. See AFI 33-360, Publications and Forms Management, for a description

of the authorities associated with the Tier numbers. Submit requests for waivers through the

chain of command to the appropriate Tier waiver approval authority, or alternately, to the

Publication OPR for non-tiered compliance items.

SUMMARY OF CHANGES

SUMMARY OF CHANGES

Changes incorporate the (eNCMR) Electronic Non-conforming Material Review as the current

practice and policy to strengthen the engineering disposition practice. Processes and policy are

solely coordinated between 76 PMXG and to AFLCMC/LPS to expedite the depot control of

nonconforming engine parts.

1. General Business Practices, Guidance, and Information ........................................ 2

Figure 1. AFMC Form 202 Process Flow .............................................................................. 5

2. Completion of the AFMC Form 202, ETAR .......................................................... 9

Figure 2. AFMC Form 202. Engineering Technical Assistance Request .............................. 10

3. ETARs Responsibilities .......................................................................................... 15

Figure 3. Workscope Meeting Minutes Sheet. ....................................................................... 24

4. Special Handling 252 (SH 252) for Requesting Engineering Assistance for

Nonconforming Maintenance Technical Problems Beyond Published Authority ... 25

5. Metrics .................................................................................................................... 25

6. AFMC Engineering Support Provided to the DLA 339 Process ............................ 26

7. Depot Control of Nonconforming Engine Parts. ................................................... 28

Attachment 1— GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 39

Attachment 2— SAMPLE DLA FORM 339 44

1. General Business Practices, Guidance, and Information

1.1. Purpose. This publication standardizes the process for requesting engineering and

depot maintenance procedure assistance at organic depots. ETARs from contractor-managed

depots are to follow contract-specific direction through the applicable contracting officer.” It

is intended to provide the engineering and depot maintenance communities with a clear

process to develop necessary procedures to mitigate maintenance operation anomalies and

work stoppages. This publication addresses business practices to be implemented, and

AFMCMAN63-1202 25 JANUARY 2018 3

explains the roles and responsibilities of AFMC in providing assistance to depot maintenance

organizations. This publication provides information for use by personnel at Air Force Life

Cycle Management Center (AFLCMC), Air Force Sustainment Center (AFSC), and Air

Force Nuclear Weapons Center (AFNWC). Separate and unique local assistance request

processes may exist only as approved waivers to this publication.

1.2. Business Practices and Guidance . The AFMC Form 202, ETAR, is the official

method to request and provide engineering technical assistance in support of maintenance

operations. AFMC Form 202 Disposition Instructions are used to provide technical assistance

for (a) conditions or procedures beyond published technical data and authority under work

stoppage and anticipated work stoppage conditions; (b) instances where technical data does

not exist and must be developed, approved, and provided to maintenance technicians; (c)

procedures and engineering authorization for rework and restoration of damaged or worn

parts and components for return to serviceable condition through repair, overhaul, or

processes not covered by applicable technical data; (d) engineering authorization for a one-

time substitution of parts, components, or materials determined to be suitable replacements

for specified items; and (e) engineering authorization for a one-time substitution of support

equipment (SE), special tools, test equipment, fixtures or ground handling equipment

determined to be suitable replacements for specified items. For the purposes of this manual,

the cognizant technical authorities (CTA) in the ETAR process are the Program Manager

(PM), Lead Systems Engineer (LSE) and Chief Engineer (CE) as identified in paragraphs

1.2.1. and 1.2.2. below.

1.2.1. PM . The PM is responsible for investigating and documenting user-identified

changes in operational usage as de-facto requirements baseline changes, and adjusts the

engineering support accordingly IAW AFMCI 63-1201, Implementing Operational

Safety, Suitability and Effectiveness (OSS&E) and Life Cycle Systems Engineering

(LCSE).

1.2.2. Engineering Authority . In accordance with AFMCI 63-1201, the terms Lead

Systems Engineer (LSE) and Chief Engineer (CE) are synonymous, referring to the

senior responsible engineer in a Program Office (PO).

1.2.3. Information Links . URL links to information in other databases or forms

(drawings, electronic technical orders (eTOs), etc.) pertinent to the recommended

solution shall be included on AFMC Forms 202.

1.2.4. Limitations . Dispositons listed on AFMC Forms 202 must not degrade

reliability, performance, form, fit or function beyond acceptable limits as determined by

the CE, or Delegation of Engineering Authority (DEA). The AFMC form will not be

used:

1.2.4.1. As authorization for part or material substitution unless there is a critical

shortage and the item is needed urgently to prevent maintenance or modification work

stoppage;

1.2.4.2. As a change to the intent of a Time Compliance Technical Order (TCTO) or

to extend TCTO rescission dates or reinstate rescinded TCTOs;

1.2.4.3. To change nuclear certified equipment, systems or technical data unless

authorized by the responsible CE (or designee);


1.2.4.4. To change Test, Measurement & Diagnostic Equipment (TMDE)

requirements specified in Technical Orders (TOs) 00-20-14 and 33K-1-100;

1.2.4.5. As authorization for obtain funding for tools, equipment and other

Government expenditures;

1.2.4.6. AFMC Form 202 will not be used for routine TO changes.

1.2.5. Restriction . The AFMC Form 202 is the only acceptable method for submitting

an ETAR.

1.3. AFMC Form 202 Flow and Approval Process. Requests for engineering technical

assistance will be initiated via the AFMC Form 202, and will follow the process flow

depicted in Figure 1, AFMC 202 Process Flow, which identifies a step-by-step process.

1.3.1. Completion Timeline. Completion of ETAR Instructions, development/revision

of technical data when required, and coordination and approval of submitted AFMC

Forms 202 shall be accomplished within 5 business/workdays after Industrial

Engineering Technician (IET) has submitted the request to engineering for a work

stoppage condition, and within 15 business/workdays for an anticipated work stoppage. If

a solution cannot be evaluated and completed within the specified time limits, the

requesting facility must be contacted by e-mail and provided (a) the intended course of

action; (b) and expected resolution date. This must be documented in the Disposition

Instructions block of the AFMC From 202. The responsible engineer shall include the

required maintenance action, reference sketches, drawings, photographs, and other

documents to the AFMC Form 202. The control number shall be annotated in the upper

right corner of the AFMC Form 202.

1.3.2. Immediate Priority. An Immediate Priority, accomplished within 1

business/workday, may be instituted for an AFMC Form 202 by the cognizant CE in

conjunction with the weapon system PM. The immediate need must be substantiated

IAW the AFMC Form 202 urgency of mission need entered in the Problem Description

and Recommendation block of the AFMC Form 202. When justified, an immediate

priority ETAR may only be extended by a memorandum of agreement (MOA) between

the submitting and performing engineering organizations and must be approved by the

CE.

1.4. ETAR Funding Policies. All AFMC Organizations. Centralized Asset Management

(CAM) under the direction of AFMC assumes all programming, budgeting and execution

responsibilities for the Department of the AF to including Depot Purchased Equipment

Maintenance, Depot Level Reparable (DLRs), Sustainment Engineering, TOs, Contractor

Logistics Support, and Support Equipment (Operational and Maintenance only).

1.5. Unprogrammed Depot Level Maintenance (UDLM) Support . UDLM support for

operating weapon/support systems is a priority task for AFLCMC, AFSC, and AFNWC. In

addition, when justified on the basis of mission urgency, ULDM support shall be given

precedence over programmed workloads.


Figure 1. AFMC Form 202 Process Flow


1.6. Engineering Order (EO) . When the solution to the problem reported on an AFMC

Form 202 is an engineering drawing (ENG DWG) change, an EO will be completed and

processed. If a solution requires a change to an ENG DWG, an AF Form 3925, Engineering

Order, must be completed, a project number obtained, and a copy of the EO must be attached

to the AFMC Form 202 providing the solution.

1.7. Automated Systems.

1.7.1. Enhanced Technical Information Management System (ETIMS) . ETIMS is

the AF System of Record, a secure web, GCSS-AF application accessible via the AF

portal with the TO catalog, ordering and the TO Distribution Office (TODO) account

management functions. ETIMS system functions to acquire, improve, publish, catalog,

manage, store, distribute and display official TOs needed for the safe and effective

operation of AF weapon systems and equipment. An organizational TODO must establish

an account and register electronic Tools (eTools) devices for non-repudiated electronic

distribution.

1.8. Item Unique Identification (IUID) . If the IUID marking is not legible on an asset

identified for serialized tracking, an ETAR shall be submitted to include all available

information about the part as well as instructions as to how to mark the part (including a

replacement data label or data plate as required). ETARs initiated for this reason shall be

forwarded to the Item Manager (IM) for the asset.

1.9. Delegation of Authority.

1.9.1. DEA . DEA will be documented in writing via a delegation letter IAW with

AFMCI 63-1201. Typical tasks include those that have the following characteristics:

negligible consequences IAW Military-Standard (MIL-STD) 882, DoD Standard

Practice System Safety; known approved repair using standard process; qualified proven

process; repair expected to last through Programmed Depot Maintenance (PDM) cycle.

Depot maintenance tasks that typically have these characteristics include, but are not

limited to AFMC Form 202 rejection, condemnations, reclamations, oversize

holes/fasteners, rework assessment, primary and secondary structure repairs, clarification

of TO, troubleshooting, catalog analysis, remove and replace a qualified part, temporary

Systems Engineering (SE) substitutes, repairing beyond TO limits due to limited supply,

repeat authority, sequencing of subsystem/component removal/installation, and parts

substitution where previously approved or not yet in TO and Consumables (Common,

Recurring, Bench Stock). (T-2).

1.9.2. Delegable and Non-Delegable Tasks. IAW AFI 63-1201, the CE may delegate

down to a qualified person. Delegations will be documented in a delegation letter IAW

AFMCI 63-1201. Tasks must be specific in nature, documented by official memo and

regularly reviewed/updated over time. IAW applicable policy and local instructions,

individuals with delegated authority may temporarily sub-delegate one level down to a

qualified person; however, responsibility for sub-delegated actions remain with the

delegated authority. Sub-delegations will be documented IAW AFMCI 63-1201. (T-2).

1.9.3. AFMC Form 202, Engineering Technical Assistance Request (ETAR). All

AFMC activities shall submit requests for engineering technical assistance to the

applicable LSE/CE/Engineering Approval Authority (EAA) using the AFMC Form 202.


1.9.4. Requests for Assistance by Non-AFMC Activities . Non-AFMC requests for

engineering technical assistance should submit requests to the applicable PM using

automated systems, if available, or by completing the AFMC Form 202 and send via

encrypted e-mail to the responsible LSE/CE.

1.9.5. Attachments to Approved ETARs . The DEA for ETAR Instructions may attach

an EO or SH 252, TO PCR, that will be an integral part of the ETAR Instructions

approved for use by the depot maintenance activity. Supplemental information may also

be included as part of an approved ETAR. All attachments/supplemental information will

be marked with corresponding ETAR Control Number IAW paragraph 1.3.1 and

appropriate distribution statement IAW AFI 61-201, Management of Scientific and

Technical Information (STINFO). (T-2).

1.9.5.1. The evaluation of an ETAR by the assigned DEA may result in the

development of an EO, when the solution requires an ENG DWG change. The DEA

will complete and expedite processing of an EO IAW AF Pamphlet 63-128,

Integrated Life Cycle Management. A copy of the EO may be attached to the ETAR

as illustration.

1.9.5.2. AFMC Form 252, TO Publication Change Request. When evaluation of an

ETAR by the DEA results in the need to change information in a published TO, the

DEA will submit the results to the Equipment Specialist (ES) and/or Technical

Content Manager (TCM) who will prepare an AFTO Form 252 to document the

specific changes required to the affected TO. The Publication Change Request (PCR)

requires immediate implementation to support the approved ETAR Instructions and

will be processed as a SH 252 IAW TO 00-5-3, AF Technical Order Life Cycle

Management. If the change prescribed on the approved SH 252 cannot be published

within 120 days, an Interim Operational Supplement (IOS) cover sheet will be

attached to the SH 252 IAW TO 00-5-3. The SH 252 shall be removed from the

ETAR once the PCR has been formally published in the affected TO.

1.9.5.3. Weapon System POs and maintenance units may develop supplemental

information and attach to an ETAR as supporting information and reference the

applicable block of the ETAR. Examples of supplemental information include an

assembly or component schematic specifically formatted for use in reporting a

recurring Non-Destructive Inspection (NDI) task, drawings, a list for data which must

be fully reported to properly address a specific hazard, and tailored “bad actor”

information forms. All supplemental information shall include an ETAR control

number.

1.10. ETAR SH 252 Procedure Verification . When a SH 252 is attached as part of ETAR

instructions, verification of revised TO procedures shall be conducted IAW TO 00-5-3.

1.11. Nuclear and Non-AFMC ETARs.

1.11.1. Nuclear ETARs . Assistance for all items listed as Nuclear Accountability

Reporting System in D086 Mission Workload Assignment System shall be provided to

the organizations (POs) listed in the system when furnishing assistance on AF owned and

procured components associated with nuclear weapons. This does not include


organizational and intermediate level support to an operational unit’s non-nuclear

munitions.

1.11.2. Nuclear System CE . The Nuclear CE or designee for each nuclear system shall

determine the conditions for which a Nuclear Surety review is required. (T-2).

1.11.2.1. The Center Nuclear Surety Office (NSO), or designee, shall review

forwarded ETARs for nuclear surety compliance and coordinate on these ETARs by

electronic or digital signature. (T-2).

1.11.2.2. If the weapon system has no resident NSO or designee, then the weapon

system PO shall establish procedures with the AFNWC for Nuclear Surety reviews.

1.11.2.3. The NSO (if required) shall be included as an additional reviewer parallel

with the Base Environmental Engineer and/or Base Safety reviews.

1.11.3. ETARs for Nuclear Systems. ETARs for nuclear systems shall include the

following information in the request:

1.11.3.1. Nuclear Weapons Personnel Reliability Program Department of Defense

Directive (DoDD) 5210.42, Nuclear Weapons Personnel Reliability Program,

applicability.

1.11.3.2. Other information as required by AFI 21-202V1, Missile Maintenance

Management, applicability Intercontinental Ballistic Missile systems and AFI 21-

202V2, Cruise Missile Maintenance Management, applicability Air Launched Cruise

Missile systems. (T-2).

1.11.4. Nuclear Weapons Related Materiel (NWRM). PO/Supply Chain (e.g.,

engineers and ESs) personnel providing technical assistance which drives updates to any

identifying information on NWRM (i.e., data plate changes or updates to National Stock

Number (NSN), Part Number, Serial Number, etc.) must contact the applicable IM before

taking any action IAW AFI 20-110, Nuclear Weapons-Related Materiel Management.

This must be done to ensure measures are in place to update the applicable NWRM

Accountable Property System of Record (APSR) and prevent NWRM discrepancies.

PO/Supply Chain personnel must receive written approval (e-mail or written

correspondence) from the applicable IM before directing any change in identifying

information on NWRM. Any direction provided to a customer to update identifying

information on NWRM must contain instructions for the customer to notify the

applicable NWRM Accountable Officer or NWRM Property Custodian prior to making

directed change to ensure the local Supply Chain Management organization updates the

applicable APSR to maintain positive inventory control. (T-2).

1.11.5. Aerospace Maintenance and Regeneration Group. For desert storage

operations at Aerospace Maintenance and Regeneration Group, refer to TO 00-2-1,

Aerospace Equipment Maintenance Inspection, Documentation, Policies and Procedures

and TO 00-20-2, Maintenance Data Documentation.

1.11.6. ETARs from Outside the AF.

1.11.6.1. Security Assistance Program (SAP) recipient country requests for

engineering assistance shall be submitted through the designated country

representative using the AFMC Form 202. ETARs shall be submitted via secure e-


Mail by the designated country representative to the Weapon System PO via the

Foreign Military Sales Foreign Disclosure Office.

1.11.6.2. ETAR for SAP aircraft under the control of Air Combat Command Air

Defense Group during flight delivery shall be submitted directly to the LSE/CE.

1.12. Records . Copies of completed AFMC Form 202s shall be physically and/or

electronically stored until such time that the approved AFMC Form 202 procedure has either

been merged into the affected TO, and published in the ETIMS, or the CE deems that they

are no longer required. (T-2).

2. Completion of the AFMC Form 202, ETAR

2.1. ETAR. Requests for engineering technical assistance to complete depot maintenance

tasks beyond the scope of published technical data are documented and submitted using an

AFMC Form 202, ETAR. An ETAR is initiated by a depot maintenance technician and

validated by an IET/Maintenance Planner when technical problems are encountered during

depot maintenance that are beyond the scope of technical data (Process Order, TO, ENG

DWGs) prescribed within the depot maintenance Work Control Document (WCD). The

following general procedures apply to the preparation, submission, processing, and execution

of all AFMC Form 202’s, as shown in Figure 2. There are three Parts to the AFMC Form 202

as displayed in Figure 2. Part A, Maintenance, represents the initial submittal of the AFMC

Form 202 and defines the urgency of need (i.e., work stoppage or anticipated work stoppage).

Part B, Engineering Direction, represents disposition direction provided by the LSE/CE,

including whether to repair, rework, use as current, or condemnation of the item/part and

coordination and approval of the proposed disposition within the applicable engineering

offices. Part C, Maintenance Coordination/Approval, documents coordination and approval

of the AFMC Form 202 submittal.


Figure 2. AFMC Form 202. Engineering Technical Assistance Request

2.1.1. Any entries on paper/handwritten forms must be typed or neatly printed in blue or

black ink. The PO shall be responsible to ensure all form information is maintained in the


official repository system. The AFMC Form 202 is available from AF ePublishing at the

following link http://www.e-publishing.af.mil/index.asp.

2.2. Part A – Maintenance . A complete and validated Part A is submitted to the

responsible LSE/CE for the problematic system/end item. An ETAR may be initiated to

request one-time authority to use a specific defective part/commodity item or deviate beyond

technical data limits, and/or receive authorization for limited use of non-listed substitutes

(supplies, components, support equipment, etc.) to prevent depot maintenance work

stoppages. Part A is completed by the Initiator and reviewed/validated by the responsible

IET/Maintenance Planner before being submitted to the LSE/CE for assistance. The Problem

Description and Recommendation section must completely describe the problem (non-

conforming situation), and provide information to support the data included in the End Item

Serial/Tail/Work Rqst No. section of AFMC Form 202. Once Part A information is complete,

priority is established and validated by the IET/Maintenance Planner, will assign the control

number at the initiation state, and the AFMC Form 202 is delivered to the responsible

Disposition Engineer (DE)/EAA.

2.2.1. To Block. Enter the office symbol, address, and/or name of the cognizant

technical authority (PM, LSE/CE) from whom engineering assistance is being requested.

2.2.2. From Block. Enter the name, office symbol, phone number and e-mail of the

depot maintenance organization requesting assistance. Enter the name of the requestor as

it appears in the Microsoft© Outlook™ Global Address List. If the paper version of the

Form is used, the entry must be made in permanent ink.

2.2.3. Date Submitted. Enter the date that the IET/Maintenance Planner approves the

Work Stoppage condition, Need Date, and the completeness and clarity of Problem

Description and Recommendation section.

2.2.4. Control Number Assigned. If an automated 202 system is not available, a

manually generated AFMC Form 202 will be entered into the automated 202 system as

soon as the system becomes accessible. (T-2).

2.2.4.1. If manually prepared, enter the next available control number from a log

maintained by the IET/Planner for the depot maintenance activity. The local depot

maintenance activity establishes requirements for the construction of the AFMC Form

202 Control Number.

2.2.4.2. The control number must be included in the upper right hand corner of all

attachments regardless of the method created. This is required to maintain

configuration control and ensure safety of the technicians performing maintenance.

(T-2). NOTE: There are no exceptions. The LSE/CE is responsible for ensuring

control numbers are included on all attachments.

2.2.5. Nomenclature. Enter the nomenclature of the part(s)/item(s) affecting the

problem. Use the associated Illustrated Parts Breakdown (IPB) TO nomenclature

reference whenever possible. If applicable, include the affected Mission Design Series

(MDS) of the system/end item.

2.2.6. Part Number. Enter the number of the affected part(s)/item(s) in the Part

Number block. Enter the corresponding Commercial and Government Entity (CAGE)

http://www.e-publishing.af.mil/index.asp


Codes in the Problem Description and recommendation block of the AFMC Form 202.

Parts may be manufactured by multiple companies, therefore, the CAGE Code will be

used to be certain that the correct part is addressed.

2.2.7. NSN . Enter the NSN for the item(s) and/or part(s) affected to be used in the

Instructions section for the AFMC Form 202. The NSN in conjunction with the part

number(s) ensure that the identical part number(s) used by different manufacturers for

completely different parts are not confused with each other.

2.2.8. End Item Serial/Tail/Work Request No. Enter the affected end item serial

number, tail number, and/or work request number. When an ETAR applies to the repair

or substitution of more than a specific end item serial, tail number, or work request

number, enter ‘Not Applicable (N/A).’ A period of time, not to exceed 120 days to which

the ETAR instructions, will be entered in the instructions block of the AFMC From 202.

Select from the following boxes: Serial Number; Tail Number; Work Request Number or

N/A.

2.2.9. Location(s) . Enter the physical location(s) (Resource Control Center [RCC],

post/building number, shop, etc.) where the item causing the problem is located.

2.2.10. TO/ENG DWG Number. If the ETAR is associated with a specific TO

process, operation, or ENG DWG, enter the affected TO Number or the ENG DWG

Number.

2.2.11. Work Stoppage . If depot maintenance cannot be completed, check the ‘YES’

box and enter the date the work stoppage has or will occur. If the ‘NO’ box is checked,

describe the impact in the Problem Description and Recommendation section. The

initiating depot maintenance organization shall first determine the urgency of the request.

NOTE: Work stoppage refers to the inability to proceed with production on a repair or

modification of an end item or commodity, or where a given process stops due to

nonconforming material, inadequate technical data, or lack of proper parts, materials,

components, tooling or facilities. Halted production of a component or part that

negatively impacts the critical path of an end item or scheduled flow of a commodity

prodcuton line (from an operational/systemic view) constitutes a work stoppage.

2.2.12. Organically Caused. Check the appropriate response to indicate if the problem

was or was not caused by an organic maintenance action. If the ‘YES” box is checked,

enter the date that Quality Assurance (QA) was notified in Block 13.

2.2.13. QA Notified . If the ETAR was organically caused during the performance of

depot maintenance, enter the office symbol, date and time that the responsible QA office

was notified.

2.2.14. Problem Description and Recommendation. List the MDS and include

aircraft serial number or Type, Model, Series (TMS), as well as applicable software

version numbers of corresponding Line Replaceable Units for involved equipment

(include the serial number for serialized items). In addition, for non-end items of

equipment, list the nomenclature and the part number.

2.2.14.1. Enter a complete, concise description of the problem and include any

recommended corrective actions. Indicate if the problem is related to a faulty TO or


Process Order operation. If so, identify the TO number, Process Order, and operations

reference. Include a detailed description of visible damage; malfunctioning items; and

operating anomalies. As applicable, include left/right, forward/aft, upper/lower,

inboard/outboard dimensions (length/width/depth); fuselage station; wing station;

water line; photographs; plus applicable ENG DWG, TO IPB figure, and index; part

number; stock number; Next Higher Assembly (NHA) part number; serial number;

and aircraft tail number.

2.2.14.2. If a SH 252 is attached as part of the ETAR Instructions, it will apply to the

Effectivity Record block End Date specified. The TO Manager (TOMA) will attach a

SH 252 IOS cover sheet to update the corresponding TO. A formal TO update will be

published and distributed to incorporate the SH 252 PCR. See TO 00-5-3 for

additional information. (T-2).

2.2.14.3. Any attachments provided with the ETAR must be annotated with the

Control Number of the ETAR as well as the appropriate Distribution statement IAW

AFI 61-201. (T-2).

2.2.15. Initiator Name. Enter the signature and/or printed name, office symbol and

phone number of the maintainer reporting the problem.

2.2.16. IET/Planner. Enter the signature and/or printed name, office symbol, phone

number of the IET/Maintenance Planner or other designated person validating that

information entered into the ETAR, Part A. Ensure information is complete and accurate

before the ETAR is assigned a Control Number.

2.3. Part B – Engineering Direction . Part B of the Form is completed by the DE to

evaluate the non-conforming deficiency description, and develop and document disposition

instructions. The designated DE will enter their name and the date the ETAR was received.

2.3.1. Disposition . The DE will determine and document the type of disposition

(Repair, Rework, Use As-Is, Condemn or Other) and document the procedure to resolve

the problem in the Disposition Instructions block. The DE must also indicate the event or

date when the Disposition Instructions are to be rescinded, identify authoritative technical

data that must be updated; e.g., Process Order, TO, or ENG DWG; and, whether Safety,

or Biological Environmental (BIO ENV) reviews are required.

2.3.2. Instructions. As defined by AFI 61-201 and Department of Defense Instruction

(DoDI) 5230.24, Distribution Statements on Technical Documents, technical

documents/information attached to or documented as ETAR Instructions are considered

to be STINFO, and shall be marked with the appropriate Distribution Statement. The

LSE/CE, or delegated engineering authority, will determine and mark the ETAR

Instruction, as well as any attachments, with appropriate Distribution Statements (DoDI

5230.24). Additional information to be included in the Instructions include the

organization/office symbol of the DEA responsible for providing Direction to resolve the

reported problem if applicable; if the ‘Other’ box is checked in the Disposition block,

explain in the ETAR Instruction block.

2.3.2.1. If the solution requires a change, attach the SH 252 prepared by the

responsible ES/TCM containing the corrected maintenance operation. The SH 252

must be referenced in this block and attached to the ETAR.


2.3.2.2. If the solution requires a change to an ENG DWG, reference section 1.5.

Any draft EO must be referenced in the Instructions block and attached to the ETAR.

2.3.2.3. If the solution requires a change to a Process Order, reference the process

order and the specific changes required. Attach corrected Process Order to the ETAR.

2.3.2.4. If the solution does not immediately require a TO, ENG DWG or Process

Order change, enter the complete, concise, step-by-step instructions for resolving the

problem.

2.3.2.5. Any attachments provided with the ETAR must be annotated with the

Control Number of the ETAR as well as the appropriate Distribution statement IAW

AFI 61-201. NOTE: A corresponding entry in the End Item Historical Form/Record

Notes Block will be required to specify the notation that will be made in the

appropriate Form/Record.

2.3.3. Authorized Until Date or Completion Of . Enter the date at which the

instruction will be valid, or select the applicable box if it is to be based upon the serial

number, tail number or a work request.

2.3.4. Requirements. Check the applicable box or boxes from TO Change, ENG DWG

Change, Safety Review, or Biological – Environmental Engineering (BEE). The

following paragraphs provide the instructions for each of the options.

2.3.4.1. Check TO Change Box if a SH 252 will be completed, and attached to the

ETAR Instructions. ETAR Instructions are incomplete without SH 252 if this Box is

checked.

2.3.4.2. Check the ENG DWG Change Box if an AFMC Form 3925, Engineering

Order (EO), will be completed and attached to the ETAR Instructions. ETAR

Instructions are incomplete without SH 252 if this Box is checked.

2.3.4.3. Check the Safety Review Box if Safety Office review of the ETAR

Instructions are required. If required, the designated Safety Office will sign in the

Coordination/Approval Block.

2.3.4.4. Check Biological-Environmental Engineering (BEE) Review Box if

Biological-Environmental (BIO-ENV) Review of the ETAR Instructions is required.

If required, the designated BIO-ENV Office will sign in Coordination/Approval

Block.

2.3.4.5. Enter ‘Not Applicable’ or document the exact wording of statements to be

placed on the applicable End Item Historical Form/Record form (AFTO 95,

Significant Historical Data, or AFTO 781 series, DoD Form 1574, Service Tag, etc.).

(T-2).

2.3.4.6. Provide instructions as required to document weapon system’s historical

records concerning significant maintenance actions resulting in conditions that could

have a bearing on future maintenance actions, deferment until future maintenance,

and nonstandard repairs, which will be readily apparent to field/owning organizations.

2.3.4.7. If future actions are required on aircraft, such as inspections or component

replacement, an AFTO Form 781 entry shall be made.


2.3.4.8. Include a complete description and location of nonstandard repairs (e.g.,

fuselage station) as well as the AFMC Form 202 control number, and the name, office

symbol and phone number of the engineer authorizing the repair IAW TO 00-20-1,

Aerospace Equipment Maintenance Inspection, Documentation, Policies and

Procedures.

2.3.5. Equipment Historical Entry . Enter the historical historyof the equipment.

2.4. Engineering Coordination/Approval. In the Coordination/Approval section, the

name, signatures, and signature dates of the following will be required as stated in the

following paragraphs.

2.4.1. DE. Enter the Name, Signature, Office Symbol, Phone, e-Mail address, and Date

of the of the DE preparer of the disposition or repair instructions.

2.4.2. Safety Office . When Safety Review is checked in the Requirements Block, the

individual designated by the applicable Safety Office will enter their Name, Signature,

Office Symbol, Phone, e-Mail address, and Date of their signature.

2.4.3. Bio-Environmental Review . When BIO-ENV Review is checked in the

Requirements Block, the BEE office representative will enter the Name, Signature,

Office Symbol, Phone, e-Mail address, and the date signed.

2.4.4. ES/TCM . When a TO Change is checked in the Requirements Block, the DE

will enter the respective ES/TCM’s Name, Signature, Office Symbol, Phone, e-Mail

address, and indicate the date if ES/TCM coordination.

2.4.5. IM. If Condemn Box is checked in the Disposition Block, the IM will enter their

name, signature, office symbol, phone e-Mail address, and indicate the date signed.

2.4.6. LSE/CE/EAA. Enter the Name, Signature, Office Symbol, Phone, e-Mail

address, and Date of the LSE/CE/EAA approving the disposition, or repair instructions.

2.5. Part C – Maintenance Coordination/Approval . Under the Coordination/Approval

block, the names, signatures, signature dates, e-Mail addresses, and phone numbers of the

IET Planner and the Maintenance Supervisor (MS) will be required as stated in the following

paragraphs.

2.5.1. IET/Planner . Enter the Name, Signature, Office Symbol, Phone, e-Mail address,

and Date of the IET/Planner.

2.5.2. MS . Enter the Name, Signature, Office Symbol, Phone, e-Mail address, and Date

of the MS.

3. ETARs Responsibilities The following subparagraphs identify the responsibilities

associated with the ETAR Process.

3.1. Headquarters (HQ) AFMC/A4 Responsibilities. HQ AFMC/A4 shall be responsible

for the following:

3.1.1. ETAR Policy. Issuing and sustaining AFMC ETAR process and policy including

supporting changes to AFMC Form 202.

3.1.2. ETAR Process Policy Waivers . Requests for waivers to processes or policy

within this publication must be prepared on an AF Form 679, Air Force Publication


Compliance Item Waiver Request/Approval. HQ AFMC/A4F will evaluate waiver

requests IAW AFI 33-360. (T-2).

3.1.3. Recommending Changes to ETAR Process and Policy. All recommendations

for change to ETAR process, policy and/or corresponding AFMC Form 202 will be

submitted by any AF user using AF Form 847, Recommendation for Change of

Publication. HQ AFMC/A4F will evaluate all recommendations for change to this

publication and the AFMC Form 202. All changes to this publication will be vetted with

the using community before publication. (T-2).

3.2. ETAR Functional Responsibilities. The following paragraphs identify the

responsibilities of engineers and depot maintenance process Supervisor, Planner, Functional

within the AF ETAR process.

3.2.1. Director of Engineering Responsibilities.

3.2.1.1. Ensures all AFMC engineering entities (i.e., AFNWC, AFSC, AFLCMC,

AFRL, AFTC) implement AFMC Form 202 process controls to ensure an accurate

and efficient process.

3.2.1.2. Develops, implements, and maintains SE policies, processes, metrics, tools

and training to enable the life cycle management of technologically-superior weapon

systems that are operationally safe, suitable, and effective.

3.2.1.3. Ensures implementation of standard LSE and OSS&E related procedures

with tailoring/waivers as authorized and appropriate.

3.2.2. PO/Complex Engineering Office Responsibilities.

3.2.2.1. Ensures internal reviews of completed ETARs to identify duplicate/similar

failures and repair trends IAW internal processes.

3.2.2.2. Ensures compliance with AFI 63-101/20-1 and AFMCI 63-1201.

3.2.2.3. Ensures AFMC Forms 202 are processed.

3.2.2.4. Ensures standard LSE and OSS&E related procedures are implemented

across PO/Complex programs and projects, with delegation, tailoring and waivers as

authorized and appropriate.

3.2.2.5. Ensures best practices appropriate to the nature of Center programs are

implemented.

3.2.2.6. Develops and implements LSE and OSS&E policy consistent with DoD, AF,

and AFMC policies.

3.2.3. DE. Serves as the DE authority as delegated by the LSE/CE to evaluate the

submitted ETAR and to develop ETAR corrective action, step-by-step instructions, and

complete the ETAR Part B. A DE signature in the ETAR Part B attests that engineering

analysis was completed IAW AFMCI 63-1201. DE authority may not be delegated to an

ES/TCM.

3.2.3.1. Ensures authorities are executed within the scope of the DEA letter from the

CE. The DE will collaborate with other engineers/ES in the PO as needed to develop

complete ETAR Part B Instructions.


3.2.3.2. Develop agreements with maintenance office supported counterparts in

defining how they will interact with the development of AFMC Form 202 issues.

3.2.3.3. Review ETAR Part A Problem Description and attachments to ensure

problem is clearly described and that pertinent technical data references, pictures,

etc., are provided.

3.2.3.4. When necessary, to review the problem, if you have access to the weapon

system asset, first action is to view the actual item and if necessary converse with the

maintenance personnel to ensure visibility of the solution.

3.2.3.5. Utilize all available technical data, information, and resources to analyze

reported problems, establish solution, and assess related risks to establish appropriate

ETAR Instructions.

3.2.3.6. When there is a need to correct or update formal technical data (TOs, Process

Orders, ENG DWGs, etc.) document the specific problem, recommended resolution

as required for the type of technical data, and notify the responsible activity.

3.2.3.7. When the DE determines that a permanent update is required to a TO in

order to correct a reported ETAR Problem, the DE shall notify the responsible

ES/TCM of the need for the change. Ensure TO change(s) directed by an ETAR are

processed as separate action parallel to the AFMC Form 202 process.

3.2.3.7.1. Coordinate and document the word-for-word change(s) required to be

documented on the AFTO Form 252. Mark the AFTO Form 252 as a SH 252 and

attach to the ETAR Instruction. Specify the verification method to be used IAW

TO 00-5-3 in the ETAR Instructions.

3.2.3.7.2. The ES/TCM will provide a copy of the SH 252 to the responsible

TOMA who will prepare an IOS cover sheet necessary to update the affected TO

IAW TO 00-5-3. Ensure the ETAR control number is annotated on the SH 252.

3.2.3.7.3. Document in the ETAR Instructions the manner or method that will be

used to verify new and/or revised maintenance operation or TO procedures. The

new or revised TO Procedures are verified as required IAW TO 00-5-3.

3.2.3.7.4. If the Safety Office and/or BEE office must review ETAR Instructions,

the ETAR will be forwarded to the appropriate Safety Office and/or BEE. A

qualified -018 or -803 series safety office representative will review ETAR Part B

Instruction for safety impacts and date and sign the ETAR. NOTE: The Safety

Office shall notify engineering of the Estimated Completion Date for reviewing

AFMC Form 202 submittals when a response cannot be provided within the

allowable timeframe. (T-2).

3.2.3.7.5. Certain categories of ETAR Instructions will require PO Subject Matter

Expert (SME) coordination. As specified below, the DE will coordinate

developed ETAR Instructions with appropriate PO SMEs prior to submitting the

ETAR to the EAA.

3.2.3.7.6. The DE will contact the Aircraft Structural Integrity PM when

replacement of fatigue critical structure must be addressed with PO.


3.2.3.7.7. NDI required in the ETAR instructions shall be conducted IAW

published AF NDI TO guidance. All revised, new, or prototyped NDI related

procedures that are not included in existing published TO guidance, shall be

reviewed and approved by certified Level 3 NDI personnel prior to approval by

delegated EAA as required by AFI 21-101, Aircraft and Equipment Maintenance

Management. (T-2).

3.2.3.7.8. Work-arounds, complicated structural repairs, efforts to save structure,

or repair/replacement that requires analysis to ensure the integrity of the

disposition approach will require coordination with PO LSE/CE. If required, the

LSE/CE will arrange for Original Equipment Manufacturer support in the DE’s

development of the ETAR Instruction.

3.2.3.7.9. The DE will coordinate with the PM to assess life cycle impacts when

the ETAR Instruction defers repairs, establishes interim repairs, or specifies

substitution of alternate parts.

3.2.3.7.10. The DE shall coordinate with the responsible ES/TCM if new or

alternate parts are specified to be used in the ETAR Instructions. The ES/TCM

will initiate action to stock list the part(s), update the D043 system, Master Item

Identification Control System, and update the affected IPB TO as required to

preclude future AFMC Form 202 reissue. The ES/TCM will collaborate and

coordinate with the respective IM for parts forecasting to ensure availability for

maintenance activities. (T-2).

3.2.4. LSE/CE . The LSE/CE is the overall Engineering/Technical Authority for

programs and systems.

3.2.4.1. Delegate engineering authority for completion of AFMC/Forms 202. Such

delegations shall be documented in writing in a DEA letter with a written or

electronic signature. Delegations may include EAA and DE authority for the review,

analysis, disposition and approval of ETARs.

3.2.4.1.1. Ensure DEA letters are reviewed annually.

3.2.4.2. Periodically review completed ETAR(s) to ensure appropriate changes are

identified, and take appropriate action to update technical data (Process Orders, TOs,

and ENG DWGs). Ensure OSS&E is maintained through robust and thorough

engineering analysis and solutions.

3.2.4.3. Ensure adequate engineering analysis training, tools, and facilities are

available to maintain OSS&E.

3.2.4.4. Assist the PM to develop and track metrics necessary to gauge key Technical

Performance Measures and state of OSS&E baseline characteristics. Collect ETAR

usage and response data, and track the number of repeat AFMC Forms 202 that drive

permanent change to TOs IAW Paragraph 5, Metrics.

3.2.4.5. Ensure organizational processes are in place to address contractual

agreements for depot assistance requests to/from contractor based maintenance or

engineering functions to include incorporation of this supplement where appropriate.


3.2.4.6. An automated ETAR system may support implementation of some or all of

administrative tasks, which consist of the following:

3.2.4.6.1. Receive and record AFMC Form 202 sent from maintenance activities.

3.2.4.6.2. Immediately notify the designated DE who will be responsible for

evaluating ETARs.

3.2.4.6.3. Verify that required/referenced attachments (ETAR Problem

Description and Instruction) are included and correctly marked and that required

coordination (e.g., Safety, Bio-Environmental, and TOMA etc.) has been

obtained.

3.2.4.6.4. Provide the IET/Planner a copy of the approved ETAR and

attachments.

3.2.4.6.5. Maintain a file copy of approved ETARs and attachments IAW AFI

33-360, Publications and Forms Management. Copies of completed ETARs shall

be stored for historical purposes with a preference for electronic media.

3.2.4.7. The EA designated by the LSE/CE reviews and approves ETAR Part B

Instructions and approves the ETAR (signs as EAA). The engineer delegated as EAA

shall not be the same engineer delegated as the DE who developed the ETAR

Instructions.

3.2.4.7.1. Ensure ETAR documented instructions are accurate, represent

engineering analysis, and are within the scope of the written DEA for the DE.

3.2.4.7.2. Ensures that the documented instruction considered cost, schedule, and

weapon system life cycle.

3.2.4.7.3. Ensures that required coordination is complete and annotated on the

ETAR.

3.2.4.7.4. Ensures Part B Instructions and information provided is adequate.

3.2.5. EAA. The LSE/CE EAA reviews and approves ETAR Part B Instructions and

approves the ETAR (signs as EAA). The engineer delegated as EAA shall not be the

same engineer delegated as the DE who developed the ETAR Instructions.

3.2.5.1. Ensures ETAR documented Instructions are accurate, represent engineering

analysis and are within the scope of the written DEA for the DE.

3.2.5.2. Ensures that the documented Instruction considered cost, schedule, available

resources and materials, and weapon system life cycle.

3.2.5.3. Ensures that required coordination is complete and annotated on the ETAR.

3.2.5.4. Ensures Part B instructions and information provided is adequate.

3.2.5.5. In conjunction with the DE, ensure that ETAR Instruction steps provide

available published AFTO numbers and paragraphs to govern maintenance action.

Ensure all revised, or modified NDI procedures developed to support ETAR

Instructions have been reviewed and approved by certified for level 3 NDI personnel.


3.2.6. Air Logistics Complex Maintenance Office Responsibilities. The Air Logistics

Complex Maintenance Directorates shall be responsible for the following:

3.2.6.1. Setting local policy and establishing a focal point for the collection of

monthly ETAR usage data from maintenance sections to ensure TO health metrics are

generated and forwarded to the Center Engineering Offices IAW AFMCI 63-1201.

3.2.6.2. The depot Maintenance Process Engineer (MPE) will coordinate with the

IET/Planner office to validate PDM process requirements as part of the LSE/CE

engineering requirements review process IAW AFMAN 63-143, AF CAM Process.

Review all pertinent technical data currently governing the maintenance process;

accomplish a business case analysis to determine the viability of a maintenance

process change, evaluate process capability control, and support the LSE/CE

Engineering Requirements Review Manager to identify engineering maintenance

requirements impact of governing depot maintenance technical data and maintenance

process operations.

3.2.7. ETAR Initiator/Submitter Responsibilities. The ETAR Initiator/Submitter

shall be responsible for the preparation and completeness of the AFMC Form 202 ETAR

Part A information.

3.2.7.1. Ensure initiated ETAR complies with established local quality control

criteria at all locations.

3.2.7.2. Notify first level supervisor of the affected maintenance operation problem -

unworkable item, damage, or other discrepancy that require engineering assistance

and complete an AFMC Form 202. Review the Problem Description with the

Supervisor/IET/Planner and if valid, direct that the ETAR be submitted. NOTE: If

the problem was organically caused, the supervisor will coordinate with Maintenance

QA Office who will sign and date the ETAR Part A.

3.2.7.3. Include a detailed description of the problem, the maintenance operation

requirement and attach photographs and/or sketches necessary to clarify the location

and extent of the problem. Any attachments to the ETAR referenced in Part A must

be annotated with the ETAR Control Number and be marked with the appropriate

Distribution Statement IAW AFI 61-201.

3.2.7.4. Submit the complete and validated Part A to the ETAR administrator

designated by the LSE/CE within two hours of signature for work stoppage requests

and within five business/work days for non-work stoppage ETAR. Submit using

automated system if available.

3.2.7.5. Include details concerning recommendations for a solution to the problem, or

limitations which would impact the ability to perform a particular repair.

3.2.8. ES/TCM Responsibilities . The ES/TCM responsibilities consist of executing the

TO change process per TO 00-5-3, ensuring procedure verification, obtaining required

coordination, ensuring that use of warnings and cautions are representative of MIL-STD

38784, Standard Practice for Manuals, Technical: General Style and Format

Requirements and working closely with the applicable IM to ensure the required parts are

forecasted and available for maintenance activities.


3.2.8.1. The ES/TCM should follow-up with the IET/Planner to ensure verification of

new TO procedures was accomplished per ETAR Instructions (desktop analysis,

simulation, or performance verification IAW TO 00-5-15, AF Time Compliance

Technical Order (TCTO) System).

3.2.9. Maintenance QA Activity Responsibilities . The QA Activity shall be

responsible for the following:

3.2.9.1. A QA representative shall be present at maintenance operation problem

review meetings between maintenance personnel and the DE developing ETAR

Instructions for a validated problem.

3.2.9.2. A QA representative shall participate in required ETAR procedure/SH 252

verification of new or revised procedures.

3.2.9.3. As established within local policy, periodically inspects nonstandard repairs

and maintenance procedures.

3.2.9.4. Each local maintenance quality organization shall jointly review the ETAR

process with its Process Engineering PO on a quarterly basis and make

recommendations to improve the process as required.

3.2.10. IET/Planner. The IET/Planner shall verify if current technical data (ENG

DWGs, TOs, Process Orders, etc.) already exists to address the maintenance operation

problem. If technical data does not exist, they will ensure that the problem description is

accurate and clearly documented in Part A of the ETAR. The IET/Planner shall be

responsible for the following. (T-2).

3.2.10.1. Reviews Forms 202 to ensure Part A is complete and correct, and the

conditions cited are valid. Assigns control numbers to track valid requests, if not

assigned by an automated system. Returns invalid requests (e.g., those for which

existing technical data is adequate) to the initiating activity and assist them with

problem resolution.

3.2.10.2. Ensures the MPE is involved in the initial problem resolution. Coordinates

with the MPE to ensure production functions have the necessary tools, and machines

to meet TO requirements. The IET/Planner will coordinate directly with the DE to

resolve any questions or problems with implementation of ETAR Instructions.

3.2.10.3. Once the ETAR Instruction is approved by an EAA and provided to

maintenance, the IET/Maintenance Planner shall ensure that new or changed

maintenance operation procedures are verified as specified in the ETAR Instructions

by the DE or ES/TCM for SH 252. Plan the verification of SH 252 TO procedures

and notify the responsible ES/TCM of completion of the SH 252 procedure

verification including needed changes, if any. Verificaton on the procedure(s) will be

documented on the AFTO Form 27, Preliminary Technical Order (PTO) Publication

Change Request (PCR)/TO Verification Record/Approval. NOTE: An SH 252

requires an IOS coversheet that will be posted to the TO by the responsible

organization Technical Order Management Agency.

3.2.10.4. Sign the ETAR Part C within two days of completion of Part B Instructions.

Ensure the MS has also signed in Part C within two days of AFMC Form 202 Part B


completion. Copies of the completed and signed ETAR shall be provided to the MS,

and (if required) to QA activities.

3.2.10.5. Review all ETAR Instruction for the need to recommend permanent

technical data updates. Initiate an AFTO Form 22 IAW TO 00-5-1 when governing

TOs specified in Depot Maintenance Work Specification must be corrected or

improved. When applicable, note the TO recommended change Local Control

Numbers on the AFMC Form 202.

3.2.10.6. Forward all copies of AFMC Form 202 procedures to affected TOMAs for

TO posting.

3.2.10.7. Maintain a file of the completed AFMC Forms 202 with the master WCD

file or in a planning file.

3.2.10.8. Forward AFMC Form 202 monthly usage data to designated Center

Engineering Office focal points IAW local policy. This data shall include, as a

minimum, the number of AFMC Forms 202 pending, the number approved and the

number associated with work stoppages.

3.2.11. MS Responsibilities.

3.2.11.1. The MS shall be responsible for the following:

3.2.11.2. Review AFMC Form 202s initiated by assigned personnel and forward to

the IET/Planner for a technical review.

3.2.11.3. When the AFMC Form 202 is intended to alleviate parts or material

shortages, attach a completed logistics parts supportability checklist to the AFMC

Form 202 by either electronic or paper media. This checklist should provide detail on

all logistics/material supportability efforts conducted to engineering partners.

Organizations may choose to use a tailored version of the example provided or

develop their own based on unique requirements.

3.2.11.4. Notifying maintenance QA when a nonstandard deficient condition is

organically caused by maintenance procedures or malpractice.

3.2.11.5. Review disposition instructions and/or procedures provided on AFMC

Forms 202 and SH 252s for any compliance problems, support equipment shortfalls,

or personnel training issues. Sign to indicate concurrence with implementing the

proposed procedures.

3.2.11.6. Ensure technicians annotate applicable DoD Forms 1574, Serviceable Tag –

Materiel, with comments required by AFMC Form 202 and forward the data to the

records section for annotation on equipment historical documents (Air Force TO

(AFTO) Form 95, Significant Historical Data, or AFTO Form 781-series aircraft

forms). (T-2).

3.2.11.7. Notify the IET/planner five days before the rescission event/date of any

AFMC Forms 202 for which a requirement still exists.

3.2.11.8. Inform the IET/Planner or QA of any issues encountered during

accomplishment of the instructions.


3.2.12. TOMA Responsibilities.

3.2.12.1. The TOMA shall be responsible for the following:

3.2.12.1.1. Ensure each SH 252 is worked as a priority and incorporated into the

affected TO, not to exceed 120 days from the date the SH AFTO Form 252 is

received by the TOMA. An IOS shall be issued if the TO cannot be incorporated

into the affected TO within the 120 day timeframe. If an AFMC Form 202 is

attached to the SH 252, the TOMA shall ensure that the Requirements block is

marked TO change and sign.

3.2.12.2. The TOMA that receives copies of extended use AFMC Forms 202s shall

annotate the project/control numbers in the ETIMS records for affected TOs. If the

TO is maintained in a paper library, reproduce enough copies of the forms to file with

each affected TO copy. The AFMC Form 202 project/control number shall be written

on the title page and the AFMC Form 202 shall be filed in the back of the TO. If the

TO is digital, the AFMC Form 202 project/control number shall be made a public

annotation on the title page of the TO and shall be linked to the AFMC Form 202

filed in a supplement folder on the master. The TOMA will remove AFMC Forms

202 once they are either rescinded or completed.

3.2.12.3. In conjunction with CE, ensure proper use of Warnings and Cautions IAW

MIL-STD 38784 when failure to comply with instructions could result in injury to

personnel or damage to equipment.

3.2.13. Workscope Meetings . Workscope meetings are encouraged to discuss and plan

resources for accomplishment of ETARs. These meetings shall be attended by

Engineering, and Process Engineering; ES/TCM; Records personnel; QA; and

representatives of both Planning and Scheduling. Other functionals may also be required

to attend dependent upon the particular workscope. Workscope meetings shall be

documented using the Workscope Meeting Minutes Sheet depicted in Figure 3. The

Workscope Meeting Minutes Sheet serves as an enterprise record for meeting

documentation, and shall not be used in lieu of critical official forms such as the AFMC

Form 202.


Figure 3. Workscope Meeting Minutes Sheet.


4. Special Handling 252 (SH 252) for Requesting Engineering Assistance for

Nonconforming Maintenance Technical Problems Beyond Published Authority

4.1. ETAR. Requests for engineering technical assistance may be executed in one of two

ways, either by the submittal of an AFMC Form 202, ETAR as discussed in Chapter 1, or by

the submittal of an AFTO Form 252.

4.2. Special Handling 252 (SH 252). An AFTO Form 252, fully-coordinated and approved

IAW TO 00-5-3, may be issued to provide the corrected or newly developed data necessary

to resolve an actual or anticipated work stoppage when the applicable TO is in error or

inadequate. The SH 252 may be issued to expedite a permanent change. The following

statement shall be either Stamped or typed on the top of each AFTO Form 252 authorized for

implementation, “Special Handling” and if applicable, all attachments. An alternative method

is to enter “AUTHORIZED FOR SPECIAL HANDLING” in the Instructions block of the

form.

4.2.1. Formal TO Change. TO changes need to be documented after the AFMC Form

202 is complete and initiated by the IET/Planner. An IOS Cover Sheet with an SH 252

attached may be used to incorporate a change into the affected TO. An example of the

IOS cover sheet may be found in TO 00-5-3.

4.3. Engineer or ES . The responsible Engineer or ES shall ensure the SH 252 is routed to

the applicable TOMA for processing.

5. Metrics

5.1. Performance Metrics.

5.1.1. AFMC Form 202, ETAR Metrics . Emphasis is placed on the AFMC Form 202,

receipt and completion process. This metric is based upon a Work Stoppage request

which must be resolved within 5 business/work days, and anticipated Work Stoppage

which must be resolved within 15 business/work days. Requests for engineering

assistance categorized as immediate priority must be resolved within 1 day after

prioritization. Immediate priority ETARs may be extended by a MOA between the

submitting and performing engineering organizations with the approval of the CE. The

following AFMC Forms 202 metrics will be provided once per quarter to AFLCMC,

AFSC, and AFNWC, and aggregately, to AFMC/A4 leadership:

5.1.1.1. Total number of open AFMC Form 202s, percent on-time and average flow

times by work stoppage vs. non-work stoppage by MDS and PO.


5.1.1.2. Number or percent of instances that AFMC Form 202s exceed predefined

threshold limits (one day for Immediate, five days for work stoppage, and 15 days for

non-work stoppage).

5.1.1.3. Average total time and percent on time by MDS and PO.

5.1.1.4. Trailing 12 month history of each of the above.

5.1.2. Annual Disposition Metrics. The LSE/CE or their staff should meet (either in-

person or by telecon) annually with the delegated Engineering Authority engineers (DEs

and EAAs) to assess the AFMC Form 202 disposition response time and the rationale for

resources (if any) that were required from the PO.

5.1.3. MOA. Depending on the needs of the PO and the maintenance organization, it

may be necessary to document organizational level agreements to facilitate delegated

engineering authority. A tailorable MOA template is provided in AFMCI 63-1201.

5.2. DLA Metrics . Metrics pertaining to DLA Form 339, Request for Engineering Support

will be performed and documented IAW the Performance Based Agreement (PBA) between

the AF and DLA.

6. AFMC Engineering Support Provided to the DLA 339 Process

6.1. Purpose. The purpose of this chapter is to establish policy, assign responsibility, and

define the process for engineering support provided by AFMC Engineering to the DLA IAW

DoDD Instruction 4140.69, Engineering Support Instructions for Items Supplied by Defense

Logistics Agency, and the AF/DLA PBA, Annex 5, Engineering Support, Version 3. DoDI

4140.69 provides guidance for the process whereby DLA requests engineering support for

NSNs which are items managed by DLA, and for which AFMC is the Engineering Support

Activity (ESA).

6.1.1. AFMC Engineering Support to DLA. AFMC Engineering, as an extension of

the AF, provides engineering support to the DLA. Engineering Technical Assistance shall

be provided to DLA using the DLA Form 339, Request for Engineering Support.

Engineering support provided shall encompass First Article Test (FAT), Critical Safety

Items (CSIs) assistance, developing, validating and approving Technical Data Packages

(TDPs), developing and engineering criteria, representing the military service

engineering interests, and providing technical guidance and decisions required in the

management and procurement of an item for its entire life cycle. As an agent of

AFMC/A4, AFLCMC is responsible for assigning focal points that act as the entry and

exit points for requests for engineering support within the AF.

6.1.1.1. Examples of CSIs include safety of flight, parts/repairs with catastrophic

failure consequences, major structural repairs, nuclear certified items, deferred

repairs, interface changes, deviation to work specifications, new manufacturing

processes, low observable critical processes, disposition of Product Quality

Deficiency Report material substitution, new repairs and/or repair processes, changes

with the potential to degrade reliability or performance, changing of test

limits/requirements, changing of calibration requirements on weapons system support

equipment, Hardness Critical Items/Hardness Critical Processes, corrosion prevention


and control requirements, changes that affect PO contract or warranty, and

dispositions that require contracted expertise.

6.1.1.2. Examples of TDP include applicable technical data such as models,

drawings, associated lists, specifications, standards, patterns, performance

requirements, QA provisions, software documentation and packaging details.

6.1.2. AFMC ESA Responsibilities.

6.1.2.1. Receive and perform quality checks of DLA Form 339 submittals for

completeness, accuracy, and adequacy of the requested engineering support.

6.1.2.2. Assign DLA Form 339 submittals to an engineer.

6.1.2.3. Identify/Verify CSIs IAW established procedures.

6.1.2.4. Provide timely engineering support to DLA requests IAW response times

defined in established engineering PBA.

6.1.2.5. Respond to DLA Form 339 requests for engineering support requests

pertaining to Extended Engineering Effort (EEE), as necessary.

6.1.2.5.1. Negotiate an EEE request with DLA IAW established engineering

PBA.

6.1.2.5.2. All such notifications shall be coordinated through Focal Point offices

at the applicable Complex.

6.1.2.5.3. All EEE information provided to DLA shall include all of the following

that apply: Technical Scope, Temporary Duty Requirement, and Itemized

estimated cost.

6.1.2.6. Provide comments for topics of discussion prepare for and attend AF/DLA

crosstalk meetings, as required.

6.1.2.7. Coordinate with appropriate personnel in POs that have an interest in the

item. The service ESAs are to ensure a single coordinated ESA response provided to

DLA.

6.1.2.8. Review and determine the validity of Engineering Data List (EDL),

Engineering Notes and Screening Analysis Worksheet (SAW) provided and populate,

as applicable. This is accomplished using the AF Purchase Request Process System.

6.1.2.9. The screening technician shall review the SAW for completeness, review all

available ENG DWGs, engineering notes and specifications and prepares an EDL and

recommends Acquisition Method Code/Acquisition Method Suffix Code

(AMC/AMSC) based on what the data supports.

6.1.2.10. The engineer must validate the AMC/AMSC code recommendation and

ensure that all required documentation for the TDP IAW the PBA is provided to

DLA, when required.

6.1.2.11. Request cataloging actions, as necessary, to include, but not limited to

updating of Material Management Aggregation Code, ES Code, AF IM code, and

Major Organizational Entity Rule.


6.1.2.12. Request/initiate with appropriate personnel to ensure updates occur to all

TOs, technical and engineering data, as applicable.

6.1.2.13. Provide engineering technical assistance in the analysis and

process/procedures of FAT. The engineer provides a complete test requirements at the

time the FAT is imposed. NOTE: These requirements will be included in the

solicitation as required by Federal Acquisition Regulation Part 9.

6.1.2.14. Serve as the focal point for OSS&E for technical descriptions created via

the DLA Form 339 process when selected as the service supporting an item.

6.1.2.15. Ensure compliance with the DoDI 4140.69 and associated PBA for items

managed by DLA.

6.1.2.16. Provide spares and screening support. When reviewing/supporting a

Consumable Item Transfer, update the TDP as applicable.

6.1.2.16.1. Ensure that all applicable sections of Part III of the Form 339 (blocks

18 through 24) are complete and executable.

6.1.2.16.2. Verify criticality of the item, correct configuration, need for the NSN

and part number and, validity of the support request.

6.1.2.16.3. Ensure all supporting man-hours for the engineering support request

are captured on the DLA Form 339.

7. Depot Control of Nonconforming Engine Parts.

7.1. Nonconforming Parts. Nonconforming engine hardware review is conducted in large

numbers that necessitate streamlined procedures. This unique need necessitates a high-flow,

low-complexity Nonconforming Material Review (NCMR) in a dedicated pool area of the

maintenance shops. This paragraph applies only to resolution of single component

nonconformity. A separate request will be initiated through the Electronic Non-conforming

Material Review, eNCMR, system (https://engines/eNCMR.) A separate material review

request will be initiated for each multiple or numerous components of the same

nonconformities for tracking purposes in the eNCMR database.

7.1.1. Informal Requests. Informal requests for technical assistance are NOT

authorized. Requests for instructions pertaining to nonconforming engine hardware must

be submitted via the eNCMR system.

7.1.2. Key Definitions Pertaining to Nonconforming Product.

7.1.2.1. Repair. An action taken on a nonconforming product so that it will fulfill

the intended usage requirements although it may not conform to the originally

specified requirements.

7.1.2.2. Rework. Action taken on a nonconforming product so that it will fulfill the

specified requirements.

7.1.2.3. Records. When an eNCMR Request and the authorization memorandum

are initiated, they become records. Any supporting documentation can be attached as

reference material to a repair or inspection action of an engine part.

https://engines/eNCMR


7.1.2.4. Nonconforming Parts. “Nonconforming” parts are engine components

worn, cracked or damaged beyond or not covered by TO authority requiring special

engineering disposition.

7.1.2.5. Condemned Parts. Parts determined not repairable are considered to be

condemned, supply condition code “H.” Condemned parts will be identified and

segregated at all times. When a determination has been made that a part is no longer

repairable, the part is identified by the shop personnel plainly marking in red with a

water-proof marker, paint, dye, ink or similar material (known as “painting red”). A

DoD Form 1577, Unserviceable (Condemned) Tag Materiel, will be completed and

attached (known as “red tagging”). Ensure the tag is filled out precisely as to why the

part was condemned. Give specific details as to what was wrong with the part to

cause the condemnation. The part will be annotated with a condemned code in the

G337 system, Inventory Tracking System (ITS), if applicable, and subsequently

segregated and sent back to the shop for condemnation credit and finally, shipped to

the appropriate Defense Distribution processing area.

7.1.2.5.1. Parts valued $10,000 or above must be sent to the NCMR Pool and

have an eNCMR Request submitted for engineering evaluation prior to

condemnation actions being taken.

7.1.2.5.2. Parts valued less than $10,000 may be condemned by shop personnel if

appropriate instructions are stated in the Tech Order or under written instruction

by the cognizant engineer.

7.1.2.5.3. Parts valued less than $10,000 must be sent to the NCMR Pool and

have an eNCMR Request submitted for engineering evaluation when identified as

supportably constraint. The appropriate supply organization will maintain a “Save

List” for shop personnel to review to determine what parts to be sent to NCMR. A

Link to “Save List” located in eNCMR.

7.1.2.5.4. Parts costing $10,000 or above may be condemned by shop and not

require NCMR action if the part has an insufficient number of cycles remaining to

meet the minimum build requirement as specified in the Tech data. All

condemned Comprehensive Engine Management System (CEMS) traced

components should be reported to the Engine Records office prior to turn in.

7.1.2.5.5. Parts identified in the Mutilation Listing, are considered to be a high-

risk type of condemned parts. Mutilation is required upon condemnation for this

(these) item(s). Parts requiring mutilation will be painted red, red tagged,

condemned in ITS, if applicable, mutilated and subsequently shipped to the

appropriate Defense Distribution processing area for processing.

7.1.3. Dispositions. Instructions provided in the DISPOSITION-Section of an eNCMR

must be strictly adhered to and must be verifiable upon completion of assigned work.

Dispositions cannot be altered. Additional dispositions can be given when subsequent

instructions are required. The applicable Disposition Engineer shall evaluate the

deficiencies noted in the DISCREPENCY Section of the eNCMR and provide disposition

instructions detailed in 7.4.5.1.


7.1.4. Technical Data. Use the eNCMR Request to furnish technical data for

conditions or procedures beyond published authority for nonconforming engine and

engine parts under work stoppage and non-work stoppage conditions. It is also used when

technical data does not exist and must be developed, approved, and provided to

maintenance technicians. The eNCMR Report will be issued to provide procedures and

engineering authorization for restoration of damaged or worn parts and components.

These procedures will bring the parts into serviceable condition through repair or

overhaul covered by applicable TOs, drawings, or other technical data. Engineering

determinations of a "use-as-is" or "satisfactory-as-is" condition will be provided. Items

determined to be beyond safe, and cost effective repair, shall be condemned.

7.1.5. Limitations. NCMR decisions must not degrade reliability, performance, form,

fit or function beyond the acceptable limits or tolerances as determined by the CE (or

their designee). eNCMR will NOT be used:

7.1.5.1. As interim TOs pending receipt of formal TOs

7.1.5.2. As changes to the intent of TCTOs or to extend rescission dates or reinstate

rescinded TCTOs.

7.1.5.3. To change nuclear certified equipment, systems or technical data.

7.1.5.4. To change TMDE requirements specified in TOs 00-20-14, AF Metrology

and Calibration, and 33K-1-100, Calibration Procedure for Maintenance Data

Collection.

7.2. Organizational Responsibilities.

7.2.1. The Complex shall provide an NCMR pool manager, and an alternate pool

manager in his/her absence.

7.2.2. The Complex shall provide: dedicated floor space; material handling equipment (

hoists etc.); sufficient Local Area Network-connected computers to permit access to ITS,

Interactive Electronic Technical Manuals System, Joint Engineering Data Management

Information and Control System, HAYSTACK, etc., for no fewer than three people at

once (an experienced planner, NCMR authorized subject matter expert, Multiple

expeditor (number establish by owning organization) and an administrative clerk).

7.2.3. The Complex will ensure the NCMR Pool Manager, NCMR planner,

administrative clerk and expeditor perform their responsibilities. Any deviations or issues

to these responsibilities will be brought to the attention of the NCMR Pool Manager for

their initial research, coordination and resolution.

7.2.4. AFLCMC shall provide sufficient propulsion engineers to conduct review of their

engine parts within the time constraints as well as ensuring that the ES, Item Manager

and Engineers perform their responsibilities.

7.3. Process Responsibilities.

7.3.1. The NCMR Pool Manager will:

7.3.1.1. Review the eNCMR Requests for completeness. Inputs changes in ITS to

read M-Code.


7.3.1.2. Provide To/From sheets on parts to be shipped out of pool back to shops.

7.3.1.3. Oversee the management of the eNCMR database for the eNCMR Request.

Ensure record-keeping maintenance is IAW AFRIMS User’s Guide.

7.3.1.4. Responsible for the entire process of all engine parts with a disposition code

“X.” This will include access to D043, Item Management Control System, G337, ITS

systems, and the NCMR database for research, updates and inputs as required. In

addition, responsible for the coordination and follow-up actions with the ES, IM,

leads/supervisors and/or the appropriate engineers.

7.3.2. The NCMR Planner will:

7.3.2.1. Review the eNCMR Request information for completeness.

7.3.2.2. Prepare supplemental WCDs, when appropriate sub-ops are known. Or,

communicate with appropriate TMS planner for the appropriate sub-ops to prepare

the supplemental WCDs.

7.3.2.3. Communicate with the appropriate TMS Planner to create an AFMC Form

959, Work Control Document, for the work authorized by the cognizant engineer on

the eNCMR Request. Print and attach to the part upon receipt of the 959 to the files

tab of the eNCMR, or hand delivered, from the TMS Planner.

7.3.2.4. If necessary, close WCD utilizing appropriate closing action. Identify

condemned components.

7.3.3. Maintenance Administrative Clerk. The Maintenance Administrative Clerk

(assigned to NCMR Area) will:

7.3.3.1. Provide clerical and administrative support to NCMR Section.

7.3.3.2. Upon receipt, and input data to G337

7.3.3.3. Notify responsible RCCs of pending ‘X’ account action.

7.3.3.4. Serves as office custodian for office records and administration, including

other duties associated with NCMR operations.

7.3.3.5. Ensure stock of NCMR tags are available for use by shop personnel.

7.3.4. Maintenance Expeditor. The Maintenance Expeditor (Assigned to Work the

NCMR Pool) will:

7.3.4.1. Contact responsible RCC if eNCMR Hold Sheet, WCDs or NCMR tags are

missing or engine parts are misrouted. Ships parts back to responsible RCC as

necessary.

7.3.4.2. Contact the NCMR pool manager when the storage area for a TMS is full.

7.3.4.3. Place date stamp on upper right hand corner of the eNCMR for all incoming

engine parts into the NCMR pool. Move all engine parts to their respective engine

lines for review/disposition.

7.3.4.4. Move engine parts to out-going lines after TO/FROM routing sheets have

been completed. Notifies the NCMR pool manager when parts have been

dispositioned and are pending shipment from the pool.


7.3.4.5. Make input into ITS for destination of in-coming and out-going engine parts.

7.3.5. Disposition Engineer. The Disposition Engineer will:

7.3.5.1. Take action to review deficiencies annotated in eNCMR.

7.3.5.2. Review/research problems with maintenance if required.

7.3.5.3. Develop repair and/or corrective actions, provide step by step instructions,

and engineering justification as required and annotate in the DISPOSITIONS Section

of the eNCMR.

7.3.6. PO EAA. The PO EAA will:

7.3.6.1. If necessary, delegate PO EAA in writing for specific areas of responsibility

to one or more individuals. The PM EAA cannot be delegated to the same engineer

that develops procedures or makes a disposition.

7.3.6.2. If necessary, delegate in writing authority to engineers to provide

engineering disposition instructions at locations not co-located with the responsible

engineering activity.

7.3.6.3. Verify and approve instructions developed in engineering disposition and

sign engineering approval block.

7.3.6.4. Coordinate (no delegation) on all NCMR Request and Reply forms that could

affect the OSS&E of the system or equipment.

7.3.7. ES. The responsible ES will:

7.3.7.1. Assist the engineer as required.

7.3.7.2. Prepare and process a Recommended Change, RC, TO PCR, when indicated

by a mark in Description of Discrepancy section of the eNCMR Report.

7.3.7.3. Have AFSC ES coordinate on X-Condition memoranda or provides

appropriate disposition instructions. Pool Manager provides X-Condition memoranda

to the AFSC ES for concur/non-concur and disposition of asset. Disposition will be

accomplished within ten working days.

7.3.7.4. Assist in initiation of AFMC Form 206 for over and above work including

price estimate and automation system entries. Use pre-agreed to menu pricing

estimates for standard type repairs to hasten AFMC Form 206 initiation rather than

seek formal price estimates one at a time. This is usually good enough as actual

pricing will occur at the time of rework and this is only an estimate.

7.3.8. Responsible Item Manager (IM). The responsible IM will:

7.3.8.1. Coordinate on X-Condition memoranda and provide appropriate disposition

instructions forwarded for concur/non-concur from ES.

7.3.8.2. When the IM non-concur with the ES automated approval of an X-Condition

item, the IM needs to consult with the ES/Engineer for a resolution. Should the

ES/IM decide to place the item in other than X-Condition, the IM/ES must coordinate

with pool manager to make the appropriate change in the NCMR database.

7.4. Procedures.


7.4.1. Initiation of an NCMR Action. Any mechanic, welder, machinist, inspector,

etc., who recognizes or identifies a nonconforming part requiring NCMR activity will

notify their respective work lead or supervisor. The work lead or supervisor will initiate

an eNCMR Request and provide a clear explanation of the deficiency, problem or

condition including TO reference. If necessary Ensure the tag is filled out precisely as to

why the part was condemned. Give specific details as to what was wrong with the part to

cause the condemnation.

7.4.2. Parts Requiring Engineering Disposition.

7.4.2.1. Parts requiring engineering disposition will immediately be segregated by

placing in a clearly designated area marked "Parts Awaiting NCMR." The top of the

first page of the WCD, will be stamped with a transparent red ink containing the

letters NCMR. The eNCMR will be completed and the part readied for shipment to

the NCMR pool. Parts at the responsible engineers’ discretion, on-site disposition will

be allowed.

7.4.2.2. Parts requiring engineering disposition are considered as nonconforming and

will be clearly identified by attaching a NCMR tag to the part in a manner that will

allow easy visibility. The tag will remain attached to the part until released from the

NCMR area. The tag may be removed for processes that cannot be accomplished with

a tag attached but must be reattached at the first opportunity.

7.4.2.3. eNCMR Request will be initiated by the responsible RCC After disposition

by engineering, the WCD will be returned to the NCMR pool for release regardless

of disposition, e.g., condemnations.

7.4.3. Receipt of Part in NCMR Pool.

7.4.3.1. The NCMR part expeditor receives the nonconforming part, at the NCMR

pool, date stamps in the upper right portion of the form and moves the parts to its

segregated TMS specific storage area for easy access and identification by engineers.

7.4.3.2. On-site NCMR transactions are permitted for whole up assemblies or

engines or parts physically located in a building other than B3001.

7.4.3.3. Parts repaired in lots or batches will have the Inventory Tracking Number

(ITN) “split” if applicable, when a portion of the lot or batch is determined to be

nonconforming. In instances where parts are repaired in designated containers

(usually in lots or batches), the nonconforming parts will immediately be moved to

another container with a tag attached, as above. The tag will remain attached to the

container until the parts within are no longer nonconforming at which time it is

removed. Parts repaired in lots or batches will never have nonconformity types mixed

in the same container unless a positive identification method is used. An example

would be to number each part with a marker and referencing the nonconformity by

the NCMR Control Number.

7.4.4. Analytical Condition Inspection Nonconforming Parts. Analytical Condition

Inspection, ACI, parts will not be sent to the NCMR pool. Engineers will make an on-site

disposition to these types of parts. The WCD will then be immediately hand-carried to


the NCMR pool manager/NCMR planner, Release Stamp and input in the NCMR

database for tracking purposes.

7.4.5. AFLCMC/LP Review.

7.4.5.1. The appropriate Disposition Engineer will take action to complete the

DISPOSITION Section on parts Awaiting Disposition.

7.4.5.1.1. The Disposition Engineer will select a Disposition Type from the

Disposition Drop-down. eNCMRs that have been initiated with incorrect and

missing data will be dispositioned as ‘Insufficient Data/Resubmit.’

7.4.5.1.2. The eNCMR system automatically selects a radio-button option of

Return to NCMR or Continue Processing based upon the selection in the

Disposition Drop-down. Items requiring subsequent engineering review should be

marked Return to NCMR.’ Items not requiring further review should be marked

Continue Process. The Disposition Engineer will confirm or change this selection.

7.4.5.1.3. When damage to the part is evidently attributed to the current repair

cycle, the Disposition Engineer will check the ‘Shop Damage’ check-box.

7.4.5.1.4. The Instructions Text Box will be used to provide technical

instructions, including references to TOs or WCD line references as well as

engineering justification if required. Longer instructions and diagrams should be

attached to the FILES Section. If no special instructions are needed, the

Disposition Engineer may state the Disposition Drop-down selection in the text

box, i.e. ‘Condemn.

7.4.5.1.5. If the discrepancy is related to a process issue and requires review by

Process Engineering, the Disposition Engineer will check the ‘Requires Process

Review’ box and supply relevant details in the text box.

7.4.5.2. For a procedure that is repeatedly required, the engineer should consider

requesting a Recommended Change, RC or an AFTO Form 22, Technical Manual

(TM) Change Recommendation and Reply, through the appropriate ES.

7.4.5.3. If a part is dispositioned ‘Deficiency Acceptable’ or ‘Repair Deficiency’ and

the discrepancy is readily apparent to field organizations or if discrepancies are

beyond field TO limits, instructions must be included for documenting the repairs on

the AFTO Form 95, Significant Historical Data.

7.4.5.4. eNCMRs with a Disposition Type allowing a part to re-enter supply and

marked Continue Process will automatically require approval by a designated

Disposition Engineer and will route to the Awaiting Approval Tab for Approval or

Disapproval.

7.4.5.5. If a completed eNCMR Report does not require additional review of the

nonconforming part at the NCMR pool or on-site review, the engineer will fill name

in the “Given By” block and “On” block in the eNCMR report.

7.4.5.6. When the nonconforming product is generated and damage is evidently

attributed to the current repair cycle or handling, shop damaged block will be checked

on the eNCMR report.


7.4.5.7. The Disposition engineer contacts the ES to initiate an AFMC Form 206

action for over and above repair work.

7.4.6. Placement of Parts in X-Condition.

7.4.6.1. The NCMR pool manager/planner initiates an email to the appropriate AFSC

ES for approval/disapproval. Coordination is required from the ES, IM and IM

lead/supervisor or the ES and IM must agree to provide different appropriate

disposition instructions for non-concurrence. Coordination for an authorized

memorandum will be returned to the NCMR pool manager/planner within 10 working

days. X-Condition items will be monitored daily by the NCMR pool

manager/planner, and affected parties will be notified after the 10 business/working

days in order to find lost, delayed or misrouted coordination. After AFSC ES, IM and

IM lead/supervisor have coordinated and approved the authorized memorandum or

the “X” disposition code has been changed by the ES, it will be sent to the NCMR

pool manager/planner. The NCMR pool manager/planner will print each authorized

memorandum. Each authorized memorandum will be date stamped & signed by the

NCMR pool manager/planner. The authorized memorandum will be used to update

the NCMR database. Two copies of the eNCMR Report and either the authorized

memorandum or email notification will be provided to the appropriate organization

for turn-in processing. Note: The “M” code, verifying the part is in NCMR, will need

to be changed in G337 to the correct status and condition codes by the NCMR pool

manager/planner when the ES or engineer changes the “X” disposition code to a

different code in the ITN block of the eNCMR Report.

7.4.6.2. When the engine part in X-Condition is being re-dispositioned due to a repair

or for excess storage parts, the ES or the engineer will coordinate with the NCMR

pool manager/planner for the correct disposition process and documentation for the

office files. For condemned parts, G337 will be updated with the correct condemned

status and condition codes and the NCMR database will be updated by the NCMR

pool manager/planner.

7.4.6.3. If maintenance loses the capability due to no activity, tooling or machinery

changes, MRB clerk to validate with appropriate Repair Development (RD) planner if

previous RD prototype has been accomplished. If so a 2nd RD effort will not be

accomplished and maintenance will engage with process engineering for assistance to

re-establish capability. If no RD has been done then RD Prototype procedures must

be accomplished.

7.4.7. Release of Parts to Maintenance Shops.

7.4.7.1. When parts are received at the NCMR Pool, the NCMR pool

manager/planner will enter status code “M” (NCMR) in the ITS QN2097 status

screen. This will place the item on “HOLD” status until the engineers make their final

disposition on the eNCMR Report. When the part is released, the administrative clerk

will then change the “M’ code in the ITS to the new status and/or condition codes, as

applicable. Note: The “M’ code in G337 can be temporarily removed for a

supplemental or recycle WCD to be pulled at the shop location and will immediately

be re-coded “M” when completed with prior coordination with the NCMR pool

manager/planner.


7.4.7.2. Parts having a transparent green Released Stamp placed across the NCMR

stamp on the front page of the WCD as applicable, will no longer be considered as

nonconforming. The next RCC to handle the released NCMR item will remove the

NCMR tag. Access to the green Released Stamp is for use by only authorized NCMR

pool manager/planner. Repaired parts will not be made serviceable until a green

Released Stamp has been placed over the red NCMR stamp on the top of the WCD.

Parts with the front page of the WCD that have been stamped with the red NCMR

stamp by mistake, will have the WCD hand-carried to the NCMR office to have the

green “Stamped by Mistake” placed over the red NCMR stamp on the first page of

the WCD. The ITS screen QN2097 will be reviewed to ensure that an "M" status

(NCMR code) does not remain prior to scanning the part as serviceable. Parts not

having a green “released” stamp across the NCMR stamp and/or having an "M" code

status remaining on the QN2097 screen will be returned to the NCMR area for

investigation and will not be put in a serviceable status in ITS.

7.4.8. Follow-on Shop Actions.

7.4.8.1. The appropriate maintenance shop(s) will accomplish the repairs, re-

inspections, condemnations, etc., as indicated on the eNCMR Report. Repaired or

reworked nonconforming products will be re-inspected per the applicable TO and

signed off by certified Complex personnel. In these cases, the mechanics inspection

stamp applied to the applicable step of the WCD is the evidence of TO compliance.

7.4.8.2. An AFMC Form 206 for funding will be requested for any disposition given

by engineering on eNCMR Report that is determined to be over and above work.

7.4.9. Nonconforming parts that require work/rework as result of engineering disposition

will be returned to the NCMR pool or shop location as instructed by the engineer on the

eNCMR Report.

7.4.10. Rescission and Removal. This applies only to actions taken on AFMC Forms

202. eNCMR is for single-instance use only on each part.

7.4.11. Standardizing Procedures. When responses to a particular problem with an

engine part are repeated, the cognizant engineer or ES should determine whether TO

changes are preferable to additional NCMR activity.

7.5. eNCMR Request Completion Instructions.

7.5.1. Initiation. The eNCMR Request will be initiated per eNCMR User Guide on the

eNCMR web site.

7.5.2. All boxes on the eNCMR Request must be completed or annotated with "NA" (not

applicable) if information is not available by the initiator.

7.5.3. The initiator will ensure a WCD and NCMR tag is attached to the nonconforming

part going to the NCMR pool or on-site review

7.5.4. Part B, Management.

7.5.4.1. Instructions. Enter specific instructions pertaining to special re-inspection,

rework instructions, or other dispositions. When known, enter the applicable supply

point where part is to be routed if no special instructions are required and disposition.


If part is to be returned to NCMR pool or to the on-site location for further action

after the initial instruction is met, the assigned engineer will sign the form in Part C

coordination block.

7.5.4.2. Disposition. Enter the dispositions for the nonconformity

7.5.5. Part C, Maintenance/Supply/Requirements.

7.5.5.1. Maintenance. Check the boxes that are applicable to the nonconformity.

7.5.5.2. Supply Action. Check applicable box if part will be routed for a supply

action.

7.5.5.3. Requirements. Mark the applicable requirements to be accomplished.

7.5.6. Part C, Coordination/Approval.

7.5.6.1. Engineer Signature. Enter the assigned engineers name, office symbol, and

phone number. The assigned engineer shall enter their electronic signature and date to

signify completion of the discrepancy and recommended instructions for remedy.

7.5.7. Part D, Engineering Branch/Section Coordination/Approval.

7.5.7.1. Interim Engineering Branch/Section. If applicable, enter the name of the

interim engineer, office symbol, and phone number of the assigned engineering

branch/section. The engineering supervisor and/or designee will initial the block if

further repair or inspection will be required. If so, the part will be returned to the

NCMR pool shop location for an on-site review.

7.5.7.2. Final Engineering Branch/Section. Upon completion of required engineering

activity, the nonconforming item instructions will be signed by the Final Engineering

Branch/Section to signify completion of instructions for the part. The engineering

signatory for this final block will include the individual’s office symbol and phone

number.

7.6. Records Management.

7.6.1. Official Records. The eNCMR Report are official records IAW the AFRIMS User

Guide. The active copies will be maintained in numerical order and retained at the

NCMR office until last entry, after which they will be put in inactive file for a period of 1

year then destroyed (AFRIMS T21-05R1200).

7.6.2. The NCMR files are input using an EIM database system to summarize each

eNCMR Report and provide data from the form via a computer spreadsheet. The database

is available through the engineering EIM and can be accessed by engineers, ESs, pool

managers, NCMR planners and pool admin clerks.

7.6.3. The eNCMR Report are evidence of actions taken and, as such, will be maintained

in the NCMR area file plan.

7.7. Use of Forms.

7.7.1. High Flow Engine NCMR Environment. The eNCMR Request is the preferred

method for the high flow engine NCMR environment. It has been tailored to provide

more space for description of problems, deficiencies, instructions, responses or


resolutions. This is important because of the cyclic nature of the NCMR repair activity,

wherein parts might return to the dedicated NCMR pool or shop location (on site) for

engineer examination following a second or subsequent inspections or repairs. The

eNCMR Request also contains information not reflected on AFMC Form 202 that is

peculiar to the NCMR database that maintains engine component information. The

database itself is important to engineers for hardware trend recognition and to TCMs for

quarterly spares computations. It is also used to gather statistical data for various

Complex organizations. This version of the eNCMR Report requires the same signatures

as the AFMC Form 202. The eNCMR Report signature requirements have been

simplified for the following reasons: (a) ground safety is not an issue in engine NCMR

because only maintenance procedures already planned and in use may be invoked by the

engineers and product engineers (nuclear hardness engineers) are not involved as the

parts subject to this instruction are not nuclear hardened; (b) the shop supervisor approval

signature is not required. Thus, only three (3) signatures remain: engineer, TOMA (as

applicable) and engineering branch, unit or designee.

7.7.2. Repetitive NCMR Assessments. A Recommended Change, RC, may be initiated

by the TCM if NCMR assessments become repetitive and warrant inclusion in TOs to

alleviate unnecessary traffic of parts into the NCMR pool or on site reviews at various

shop locations.

HEATHER J. MOORE, NH-04

Division Chief A4/10-EN, Directorate of Logistics,

Civil Engineering,

Force Protection, and Nuclear Integration


Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

DoDD 5230.24, Distribution Statements on Technical Documents

DoDI 4140.69, Engineering Support Instructions for Items Supplied By Defense Logistics

Agency (DLA)

AFI 21-101, Aircraft and Equipment Maintenance Management

AFI 21-202V2, Cruise Missile Maintenance Management

AFI 33-360, Publications and Forms Management

AFI 63-101/20-101, Integrated Life Cycle Management

AFMAN 33-363, Management of Records

AFMCI 21-301, AFMC TO System Implementing Policies

AFMCI 63-1201, Implementing Operational Safety, Suitability and Effectiveness (OSS&E) and

Life Cycle Systems Engineering (LCSE)

AF Pamphlet 63-128, Integrated Life Cycle Management

MIL-STD 882, DoD Standard Practice: System Safety

TOs cited in this AFMC Manual may be accessed via ETIMS at

https://www.my.af.mil/etims/ETIMS/index.jsp. An ETIMS account is required. If you have an

essential requirement for an ETIMS account, contact the AFTO Field Support Team at DSN

872-9300, Commercial 850-882-9300 or email [email protected].

TO 00-5-1, AFTO System

TO 00-5-3, AFTO Life Cycle Management

TO 00-5-15, AF TCTO Process

TO 00-20-1, Aerospace Equipment Maintenance Inspection, Documentation, Policies and

Procedures

TO 00-20-2, Maintenance Data Documentation

TO 00-25-107, Maintenance Assistance

TO 00-20-14, AF Metrology and Calibration Program

TO 33K-1-100, Calibration Procedure for Maintenance Data Collection

Adopted Forms

AF Form 3925, Engineering Order

AF Form 847, Recommendation for Change of Publication

AFMC Form 959, WCD

AFMC Form 202, Nonconforming Technical Assistance Request and Reply

https://www.my.af.mil/etims/ETIMS/index.jsp

mailto:[email protected]


AFMC Form 206, Temporary Work Request

AFTO Form 22, Recommended Change Request

AFTO Form 95, Significant Historical Data

AFTO Form 840, NCMR (NCMR)

AFTO Forms 781(A-P), Maintenance Data Documentation Series

DLA Form 339, Request for Engineering Support

DLA Form 1912, Defense Logistics Agency Local Purchase – Technical Support Request

DoD Form 1574, Serviceable Tag – Materiel

Terms

AF Materiel Management Aggregation Code—A two-position alphabetic code authorized to

identify specific items (NSNs) to be managed by a specific manager. Materiel Management

Aggregation Codes apply to systems, programs, aggregation to related equipment, and selected

Federal Supply Class.

AFMC Form 202—ETAR. The document and process used within a depot-level maintenance

activity to request the responsible engineer and ES develop technical data or determine

serviceability when published data is in error or not adequate to complete the task at hand (work

stoppage or anticipated work stoppage) and provide the response to the maintenance technicians.

The AFMC Form 202 process is also used to alleviate critical parts or material shortages by

authorizing substitutes determined suitable by the responsible engineer Purpose is to provide

EAA engineering determination and authorization to resolve: (1) Procedures for restoration of

damaged or worn parts and components to serviceable condition through repair or overhaul

procedures or processes not covered by applicable TOs, drawings or other technical data.(2) A

serviceability condition of "Use-as-is" or "Satisfactory-as-is" (3) A one-time substitution of

parts, components or materials determined to be suitable replacements for specified items.(4) A

one-time substitution of support equipment, special tools, test equipment, fixtures or ground

handling equipment determined to be suitable replacements for specified items.

Alternate Source—An offeror (Government or Contractor) other than the Prime Contractor or

Original Equipment Manufacturer to provide the identical part numbered item.

Approved Source—Any supplier who has been approved by the cognizant engineering

organization(s) to supply parts manufactured to the original specifications of the item.

Authority—The legitimate right or power of an individual to make determinations or direct

actions within the scope of the position to achieve specific objectives. Assigned persons are

responsible to exercise their authority to accomplish the assigned task(s).

Chief Engineer (or Designee—The CE for any system is the individual designated as the CE

per AFMCI 63-1201 and has ultimate cognizant technical authority responsibility for that

system. The CE may designate an individual(s) to assist with the approval of ETAR requests.

This (these) designee(s) shall be designated by name in writing annually.


Critical Application Item—An item that is essential to weapon system performance or

operation, or the preservation of life or safety of operating personnel, as determined by the

engineering activity(s).

Critical Safety Item—CSIs are categorized as either Aviation CSIs or Ship CSIs. For the

purpose of this instruction, any reference to CSI includes both Aviation CSIs. A part, assembly,

installation equipment, launch equipment, recovery equipment, or support equipment for an

aircraft or aviation weapons system that contains a characteristic for which any failure,

malfunction, or absence could cause a catastrophic or critical failure resulting in the loss or

serious damage to the aircraft or weapons system; an unacceptable risk of personal injury or loss

of life; or an uncommanded engine shutdown that jeopardizes safety.

Disposition Engineer—Maintenance engineer with delegated authority to develop the AFMC

Form 202 engineering disposition.

Distribution Statement—A statement used in marking a technical document, regardless of

publication media or form, to denote the extent of its availability for distribution, release, and

disclosure without additional approvals and authorizations from the controlling DoDD office.

DLA Form 339—Form used to obtain engineering support for standardization for DLA

managed items supplied to the services/agencies. Categories of engineering support supplied and

Decision Support Center/service/agency responsibilities are defined in General Services

Administration Revision Control System DoD-DLA (A) 259(s)) and DLA Regulation 4140.69,

Engineering Support Instructions for Items Supplied by DLA.

Engineering Change—A change to the current approved configuration documentation of a

configuration item. Any alteration to a product or its released configuration documentation.

Effecting an engineering change may involve modification of the product, product information,

and associated interfacing products.

Emergency Maintenance Support—Maintenance assistance required by AF activities to satisfy

urgent unprogrammed requirements for depot level maintenance or Organizational and

intermediate O&I level maintenance which is beyond the capability of the maintaining

command.

Engineering Support—Engineering and technical assistance, including, but not limited to:

developing, validating and approving TDPs; developing and reviewing engineering criteria;

representing the military service engineering interests; and providing technical guidance and

decisions required in the management and procurement of an item for its entire life cycle.

Engineering Support Activity—The organization/individual designated to provide engineering

or technical assistance, including the development of technical data and engineering criteria,

engineering representation, guidance, and decisions.

Engineering Support Activity Focal Point—Entry and exit point(s) for requests for

engineering support within each service.

Extended Engineering Effort—A request for engineering support that requires the use of

dedicated resources to work a defined requirement, has a clearly specified end product, and

incurs a one-time negotiated charge.

Item Unique Identification—DoD program that that enables easy access to information about

DoDD possessions that make acquisition, repair, and deployment of items faster and more


efficient to track. It is a permanent marking method used to give equipment a unique

identification. Marking is essential for all equipment with an acquisition cost of over $5,000,

equipment which is mission essential, controlled inventory, serially-controlled, or consumable.

Item Unique Identification-marking is a set of data for assets that is globally unique and

unambiguous. Tangible items are distinguished from one another by the assignment of a unique

identifier in the form of a unique data string and encoded in a bar code placed on the item. An

item unique identifier is only assigned to a single item and is never reused. Once assigned to an

item, the Item Unique Identification is never changed even if the item is modified or re-

engineered.

Life Support Item—All equipment and components designed to protect, sustain, or save human

lives as designated by the engineering activity.

Maintenance Engineering—For the purposes of this AFMC Manual maintenance engineering

is referred to as logistics support for depot maintenance repair facilities and provides plant

facilities, equipment engineering, calibration, and installation support as required.

Operational Safety—The level of safety risk to the system, the environment, and the

occupational health caused by a system or end item when employed in an operational

environment. The PM shall utilize the established system safety process to assure operational

safety.

Planner—Persons (typically GS0895, IETs) responsible for development, preparation, revision,

coordination and accuracy of technical content of WCDs. Reviews/updates/maintains files of

WCD change requests, and maintain documentation for AFMC.

Program Manager—The PM is the senior individual responsible and accountable for

management of a weapon system or sub-systems. PM refers to Product Group Manager which

has engineering and programmatic responsibility for the discrepant item.

Reverse Engineering—The process of examining an item to determine its function, material

composition, construction, and its electrical, physical, and environmental requirements for the

development of a TDP adequate for procurement. The output of the reverse engineering project

will be a TDP for an item that has the same form, fit, and function of the original item.

Scientific and Technical Information—Information relating to research, development,

engineering, testing, evaluation, production, operation, use, and maintenance for military

products, services, and equipment for military systems. This includes production, engineering,

and logistics information.

Systems Engineering—Comprises the scientific, technical, and managerial efforts needed to

define/refine requirements, develop, test, verify, deploy, support, sustain and dispose of a

product, platform, system, or integrated System-of-Systems/Family-of-Systems capability to

meet user needs. SE may be referred to as a discipline, a methodology, an approach, a practice, a

process, a set of processes and sub-processes, or various other terms; however, its fundamental

elements – systematic technical and managerial processes and measurements – remain the same

regardless of the collective nomenclature.

Technical Content Manager—The individual, usually an ES or Engineer, responsible for

maintaining the accuracy, adequacy, modification, classification, review, and currency of the

technical content of TOs and TCTOs supporting assigned systems, commodities or processes.


Technical Data—Recorded information, regardless of form or method of recording, of a

scientific or technical nature. Information that can be used, or adapted for use, to design,

develop, assemble, engineer, produce, manufacture, modify, operate, repair, test, overhaul,

maintain, or reproduce equipment and related technology.

Technical Data Package—A technical description of an item adequate for supporting an

acquisition strategy, production, engineering, and logistics support. The description defines the

required design configuration or performance requirements, and procedures required to ensure

adequacy of item performance. It consists of all applicable technical data such as models,

drawings, associated lists, specifications, standards, patterns, performance requirements, QA

provisions, software documentation and packaging details.

Test, Measurement, and Diagnostic Equipment—Devices used to maintain, evaluate,

measure, calibrate, test, inspect, diagnose, or otherwise examine materials, supplies, equipment,

and systems to identify or isolate any actual or potential malfunction, or decide if they meet

operational specifications established in technical documents.

Work Control Document—The official record for (depot) work including control,

identification, certification, and routing of items. It is an instruction document summarizing

sequenced steps and the TO references for processing the item. WCDs are developed by

authorized planner/IET IAW approved technical data. The WCD is the record documenting that

the task was performed by certified technicians IAW authorized technical data.


Attachment 2

SAMPLE DLA FORM 339

Figure A2.1. DLA Form 339, Request For Engineering Support.












Table A2.1. DLA Form 339, Request for Engineering Support Completion Instructions.

DLA FORM 339, REQUEST FOR ENGINEERING SUPPORT COMPLETION

INSTRUCTIONS

PART I HEADER INFORMATION (To be completed by DLA Initiator)

BLOCK

NO.

TITLE INSTRUCTION

1.a. CASE NUMBER Enter the Defense Supply Center case number in the

space provided.

1.b. REVISION LETTER Enter the Revision Number if required, if not, leave

blank.

2.a. DATE Enter the date of the Request for Engineering Support

in the space provided.

2.b. REVISION DATE If a Revision Letter Number was entered in 1.b.,

enter the date in the space provided, if not leave

blank.

3 TO: Check the applicable box(s) from the following

choices: (ARMY; NAVY; United States AF; AZ;

HD; SE; BD; HX; SU; BF; KE; SX; CL; TG; GT;

United States Marine Corps; OTHER; PA

4 FROM: Enter the information requested in blocks 4.a.through

4.g.(3).

4.a. REQUESTING OFFICE Enter the Office Symbol of the office requesting

assistance.

4.b. POINT of CONTACT

(POC)

Enter the name, and title of the requesting office

Point of Contact.

4.c. ADDRESS of

REQUESTING OFFICE

Enter the address of the requesting office Point of

Contact.

4.d. PHONE NUMBER Enter the DSN and commercial phone numbers of the

requesting office Point of Contact.

4.e. Facsimile NUMBER Enter both the DSN and commercial Facsimile phone

numbers of the requesting office Point of Contact.

4.f. e-MAIL ADDRESS Enter the e-Mail address of the requesting office

Point of Contact.

4.g.(1). DSC

ENGINEER/TECHNICI

AN REVIEW NAME

Enter the name of the Defense Supply Center

engineer or technician performing the review.

4.g.(2). DSC

ENGINEER/TECHNICI

AN REVIEW TITLE

Enter the title of the Defense Supply Center engineer

or technician performing the review.

4.g.(3). DSC

ENGINEER/TECHNICI

AN REVIEW PHONE

Enter both the DSN and commercial phone numbers

of the Defense Supply Center engineer or technician

performing the review.

5 ESA RESPONSE TIME

REQUIRED

Complete the appropriate Engineering Support

Activity response time required.

5.a. NEGOTIATED If Negotiated is checked, enter the number of days.


EMERGENCY

RESPONSE TIME

5.b. RESPONSE TIME

PRIORITY GROUP I

If a priority group I Purchase Request, Contract

Waiver, or Reverse Engineering project, check the 30

day box.

5.c. RESPONSE TIME

RESPONSE TIME

PRIORITY GROUP II

If a priority group II Purchase Request, check the 40

day box.

5.d. RESPONSE TIME

RESPONSE TIME

PRIORITY GROUP III

If a priority group III Purchase Request, Procurement

pending, or Out of Stock, check the 60 day box.

5.e. STOCK ON HAND Check the 90 day box.

5.f. NEGOTIATED

EXTENDED

ENGINEERING

EFFORT RESPONSE

TIME

If a time has been negotiated involving an Extended

Engineering Effort, check box 5.f., and enter the

number of days negotiated for the response.

6 NOMENCLATURE Enter the nomenclature of the part for which

engineering assistance is needed.

7 NSN Enter the NSN of the part for which engineering

assistance is needed.

8 CAGE Enter the Commercial and Government Entity

number of the Original Equipment Manufacturer of

the part for which engineering assistance is needed.

9

PART NUMBER(s) Enter the part number(s) of the part or parts for which

engineering assistance is required.

10.a. MMAC Enter the Materiel Management Aggregation Code of

the part(s) requiring engineering assistance.

10.b. SMIC Enter the Special Material Identification Code of the

part(s) requiring engineering assistance.

10.c. MCC Enter the Material Control Code of the part(s)

requiring engineering assistance.

11.a. End Item Application Enter the weapon system or equipment end item

application for which the part requiring engineering

assistance is applied.

11.b. Next Higher Assembly Enter the weapon system or equipment end item

NHA for which the part requiring engineering

assistance is applied.

12 CRITICALITY OF

RECORD CURRENTLY

SHOWS

Check either the “YES” box or the “NO” box.

13 AMC/AMSC Enter the Acquisition Method Code/Acquisition

Method Suffix Code Acquisition Method

Code/Acquisition Method Suffix Code code.

14 IS THIS A CIT ITEM If the item is a Consumable Item Transfer check


either the “NO” box or the “YES” box. Enter the

Losing Inventory Manager and the Effective Transfer

Date.

PART II ENGINEERING SUPPORT REQUEST (To be completed by DLA

Initiator)(Explanation of Categories on Page 4)

15 REQUEST FOR

ENGINEERING

SUPPORT

Enter the information requested in blocks

15.a.through 15.k.

15.a. ALTERNATE METHOD

of SUPPORT

If this block is checked, check all that apply in the

following sub-blocks: Contractor advises Item

Obsolete Without Replacement; Contractor Out of

Business, or Moved Without Replacement; Product

Line Discontinued; Technical Data Required for

Open Competition.

15.a.(1).

Thru

15.a.(4).

ALTERNATE

METHODS of

SUPPORT

Select all that apply from the following: Contractor

Advises Item Obsolete Without Replacement;

Contractor Out Of Business, Or Moved Without

Replacement; Product Line Discontinued; Technical

Data Required for Open Competition.

15.a.(5). ALTERNATE

METHODS of

SUPPORT

ADMINISTRATIVE

INFORMATION

Enter the Commercial and Government Entity, Part

Number, NSN, of Recommended Replacement.

15.b.(1)

Thru

15.b.(4).

ALTERNATE METHOD

CATEGORY

Check box 15.b.if alternate source is required. Enter

the Alternate Offeror, the Manufacturer, and the

Point of Contact. Check the applicable box from the

following: Category 1, Same Item; Category 2,

Similar Item, Same Item; or Category 3, New Item.

15.b.(1)

Thru

15.b.(4).

ALTERNATE METHOD

CATEGORY

Check box 15.b.if alternate source is required. Enter

the Alternate Offeror, the Manufacturer, and the

Point of Contact. Check the applicable box from the

following: Category 1, Same Item; Category 2,

Similar Item, Same Item; or Category 3, New Item.

15.b.(5). ALTERNATE

METHODS of

SUPPORT

ADMINISTRATIVE

INFORMATION

Enter the Commercial and Government Entity, Part

Number, NSN, Of Recommended Replacement.

15.c. ENGINEERING

CHANGE PROPOSAL

(ECP)/REQUEST for

WAIVER OR

DEVIATION

If Engineering Change Proposal is checked, provide a

description of the need in Block 16.

15.d. REQUEST TECHNICAL

DATA PACKAGE

If Technical Data Package is checked, provide a

description of the Technical Data Package in Block


DEVELOPMENT or

VALIDATION

16.

15.e. REVERSE

ENGINEERING

CANDIDATE

APPROVAL (Initial

Phase)

If item is selected as a candidate for reverse

engineering, details must be entered in Block 16

(Describe in Block 16)

15.e.(1). TECHNICAL DATA

PROVIDED (Encl:)

When the Technical Data Package is attached as an

enclosure check Technical Data Provided box and

enter the enclosure number/title.

15.e.(2). POTENTIAL

SAVINGS/IMPROVED

DELIVERY

When a potential financial or delivery time

improvement is anticipated, check box 15.e.(2).and

enter the savings.

15.f. REVERSE

ENGINEERING

(APPROVAL)

Check Block 15.f.if reverse engineering is approved

for the item.

15.g. CONTRACT

DELIVERABLES

Describe contract deliverables in Block 16.

15.h. MISCELLANIOUS

TECHNICAL

REQUIREMENTS

Describe miscellaneous technical requirements in

Block 16.

15.i. CRITICAL

APPLICATION

If critical application box is checked, describe reason

in Block 16.

15.j. EVALUATION OF

SURPLUS OFFER

Describe in Block 16.

15.k. EXTENDED

ENGINEERING

CHANGE PROPOSAL

(ECP)/REQUEST FOR

WAIVER OR

DEVIATION

Describe rationale for extended engineering need in

Block 16.

16 SUPPLEMENTAL

INFORMATION/COM

MENTS

Enter the supplemental information from blocks

15.c.through 15.e.and 15.g.through 15.k.

17 ENCLOSURES Identify enclosures from above by number and

electronically attach them or if paper identify them

by number, stamp or type the number onto the paper

attachment and append the copy(s) to this form.

PART

III

EVALUATION (To be completed by ESA)

18 ADDITIONAL

INFORMATION

REQUIRED FROM

INITIATOR

(See Block 22 for details)

20.a. ENGINEERING

SUPPORT

Check all applicable blocks in section 20.


EVALUATION

20.a.(1). ALTERNATE METHOD

of SUPPORT FOR

SUBJECT NSN

IDENTIFICATION

Identify the replacement item NSN and/or part

number, and manufacturer Commercial and

Government Entity number.

20.a.(2). ALTERNATE METHOD

of SUPPORT FOR

SUBJECT NSN

IDENTIFICATION

If the Alternate Source Replacement Item/Technical

Data cannot be identified check block 20.a.(2) to

authorize NSN cancellation.

20.a.3.a. SUPPLY by NEXT

HIGHER

ASSEMBLY/KIT, NSN

Enter the NHA/kit NSN.

20.a.3.b. FABRICATE/ASSEMBL

E

List the NSNs, units of issue and, quantities of the

items that the assembly is to be fabricated/assembled

from.

20.c. ALTERNATE

OFFEROR

If the Alternate Offeror has been approved, check the

“APPROVED” box. If the Alternate Offeror has been

disapproved, check the “DISAPPROVED” box and

refer to Block 22 for details. If the Alternate Offeror

has been Conditionally Approved, check the

“Conditionally Approved” box and refer to Block 22

for details.

20.d. TDP

DEVELOPMENT/VALI

DATION STATUS

Indicate whether development/validation Technical

Data Package is enclosed or not available by

checking either the “Enclosed” box or the “Technical

Data Not Available” box.

20.e. REVERSE

ENGINEERING

PROJECT INITIATION

Check the applicable boxes to indicate whether

reverse engineering project initiation has been

approved or disapproved. Enter the number of

prototypes if approved, and the estimated cost of

performing test and evaluation. Check the applicable

box to indicate the method of accomplishing testing:

ESA or Outside Source. (Describe tests to be

performed in block 22).

20.f. REVERSE

ENGINEERING

If reverse engineering has been approved, check the

“APPROVED” box. If the reverse engineering has

not been approved, check the “DISAPPROVED” box

and refer to Block 22 for details.

20.g. CONTRACT

DELIVERABLES

If contract deliverables have been approved, check

the “APPROVED” box. If the contract deliverables

have not been approved, check the

“DISAPPROVED” box and refer to Block 22 for

details.

20.h. MISCELLANIOUS

TECHNICAL

REQUIREMENTS

Refer to block 22 for Miscellaneous Technical

Requirements details.


20.i. CRITICAL

APPLICATION

DECISION

Critical Application Decision refers to block 19 and

add description in block 22.

20.j. SURPLUS OFFER If The Surplus Offer has been approved check the

“APPROVED” box. If the Surplus Offer has not been

approved, check the “DISAPPROVED” box and

refer to block 22 for details.

20.k. EXTENDED

ENGINEERING

Refer to block 22 for Extended Engineering details.

21 ENGINEERING

SUPPORT BILLING

CHARGE

Complete blocks 21.a through c.

21.a SCHEDULED RATE Enter the scheduled rate.

21.b. ACTUAL HOURS Enter the actual hours expended.

21.c. COST

ESTIMATE(Completed

by ESA For Extended

Engineering Efforts

Only) $

Enter the Cost Estimate completed by ESA for EEEs.

22 SUPPLEMENTAL

INFORMATION/COM

MENTS

Enter Supplemental Information/Comments from

blocks indicated above.

23 ENCLOSURES Enter enclosures applicable to blocks above as

indicated. Ensure that all enclosures are clearly

identified and that any enclosures that are attached in

paper media have the number and title clearly marked

at the top of each page of the enclosure.

24.a. RESPONSIBLE ESA

OFFICE

Enter the office symbol of the responsible ESA

24.b. DATE Enter the

24.c. POINT OF CONTACT Enter the name, and title of the requesting office

Point of Contact.

24.d. ADDRESS Enter the address of the requesting Point of Contact.

24.e. PHONE Enter the DSN and commercial phone numbers of the

requesting office Point of Contact.

24.f. Facsimile:

COMM

Enter both the DSN and commercial Facsimile phone

numbers of the Point of Contact.

24.g. e-Mail Address Enter the e-Mail address of the requesting Point of

Contact.

24.h. Reviewer Enter Reviewer Name