NUWC_Drawing_50225-0026MN.pdf

50225-00266MN

26 January 2015

Configuration Management

Engineering Change Document Manual

Department of the Navy

Naval Undersea Warfare Center

Division Newport

1176 Howell Street

Newport, Rhode Island 02841

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only; Critical Technology 20141215. Other U.S. requests shall be referred to the Naval

Undersea Warfare Center Division, Newport, RI.

CHANGE/REVISION RECORD

CHANGE

NO.

DATE

APPROVED

DESCRIPTION APPROVER

1815NE013 26 January Initial Release E. A. McLaughlin

TABLE OF CONTENTS

Section Title Page

1 INTRODUCTION

1.1 Purpose

2 CONFIGURATION CHANGE CONTROL DOCUMENTATION

2.1 Engineering Change Documentation (ECD)

2.1.1 Engineering Change Proposal (ECP)

2.1.2 Request for Deviation (RFD)

3 ECD FORMS AND INSTRUCTIONS

3.1 Engineering Change Proposal (ECP) Form Instructions

3.2 Request for Deviation (RFD) Form Instructions

3.3 ECD Checklist

1 INTRODUCTION

1.1 Purpose

This Configuration Management Engineering Change Document (ECD) Manual provides guidance for preparing Engineering Change Proposals (ECPs) and Requests for Deviation (RFDs).

2 CONFIGURATION CHANGE CONTROL DOCUMENTATION

2.1 Engineering Change Documentation (ECD)

Changes to the approved Functional and Product Baselines of Configuration Items (CIs) must be properly documented and approved by the Configuration Review Board (CRB). Engineering Change

Documentation can be submitted by any activity that desires a proposed change or deviation from an approved baseline.

2.1.1 Engineering Change Proposal (ECP)

An ECP is a specific written request to make a change to a CI’s current approved Functional Baseline

(Critical Item Performance Specification, CIPS) or Product Baseline (drawing package, DWGs). ECPs provide information to define the change description, the technical impact, and cost data (if applicable).

Also provided are preliminary test data and analyses to support the technical feasibility of the submittal.

2.1.2 Request for Deviation (RFD)

An RFD is a specific written request to depart from a particular requirement of a CI’s current approved

Functional and Product Baselines for a specific period of time. Approval of a deviation does not change a baseline; it only provides authorization to deviate from it. An RFD is requested prior to manufacture, during manufacture, or after an item has been submitted for government inspection and acceptance. Submittal of recurring departures is discouraged and should be avoided when possible.

Consideration should be given to development of an ECP to propose a permanent change to the baseline.

3 ECD FORMS AND INSTRUCTIONS

The appended instructions and forms shall be used to prepare ECDs for submittal consideration.

Section 3.1 contains ECP instructions and forms. Section 3.2 contains RFD instructions and forms.

Section 3.3 contains the ECD Checklist. If there are any questions about the information found herein, please direct them to the Government Configuration Manager for resolution. Editable forms are available upon request.

3.1 Engineering Change Proposal (ECP) Instructions and Form

Distribution Statement D

Insert date ECP generated (for example 26Jan2015).

Block 1. Date

Contractor: The date shall be the date on which the ECP is submitted to the Government.

NUWC: Date corresponds to the date that the Government Number (Box 3) is assigned.

Block 2. Title

The title shall begin with the Model of the CI, and consist of keywords that identify the proposed revision(s). A CI is an item with an NSN. It is a lowest replaceable unit (LRU), for example: a hydrophone, projector, OBE, cable, window, or dome. Example titles: TR-338C, Housing Dimension

Discrepancy, or DT-705A CIPS, Test Requirement Revision and New Noise Limit Table, or DT-102

Cable, Add Additional Length, or DT-100 CCA Telemetry Card, Replace Obsolete Capacitor.

Block 3. Government No

The Government Number is assigned upon receipt of the ECP from the Contractor. The Originator No., Box 9d, will be appended.

Block 4. Department of Defense Activity Address Code (DoDAAC)

Enter the DoDAAC of the procuring activity. The DoDAAC is a six position code that uniquely identifies a unit, activity, or organization that has the authority to requisition and/or receive material.

The first position designates the particular Service/Agency element of ownership.

NUWCDIVNPT is N66604, NAVSEA is N00024.

Blocks 5a, b, c, and d. Originator

Contractor: Enter the name (point of contact), phone number, mailing address and e-mail address of the submitting activity.

NUWC: Use CM Manager.

Block 6. Class of ECP

In general, enter “I” if the change affects the “form, fit, or function” of the CI, and enter “II” if the change does NOT affect the “form, fit, or function”.

Class I: the requested change involves health, performance, interchangeability, reliability, survivability, or maintainability of the item or its repair parts, use of operation, weight, or appearance.

Class II: the requested change does not involve any of the factors listed for Class I.

Block 7. Justification code

Enter the justification code, which is applicable to the proposed engineering change.

A – Administrative (Government Use Only) – this is for record only. This applies to, for example, the initial release of drawings/documents into the configuration management system.

B - Interface - shall be assigned to eliminate incompatibility between CI’s.

C -Compatibility - modifies/corrects a condition found during and/or after manufacture and is in the scope of the contract. There is no increase in price.

D - Deficiency – this cannot be safety, interface, or compatibility related.

O - Operational or logistics support – this makes a change in operational capabilities of logistic support.

P - Production stoppage – is required to prevent slippage in an approved production schedule. This code applies when production to the current configuration documentation either is impractical or cannot be accomplished without delay.

R - Cost Reduction- this reduces life cycle costs but is not a Value Engineering ECP.

S - Safety – if this code is used a system hazard analysis must be included. Refer to MIL-STD-882.

V - Value engineering ECP. When the contract contains a value engineering clause, each value engineering ECP shall be identified both by the "V" in Block 7 and by the entry of the following notation in Block 2: "VALUE ENGINEERING CHANGE PURSUANT TO CONTRACT CLAUSE."

Block 8. Priority.

A priority shall be recommend, enter an "E", "U", or "R" (Emergency-48 hours, Urgent-30 days, or

Routine-90 days).

Block 9. ECP Designation.

Block 9a. Model/Type.

Enter model or type designation of the CI for which this proposal is being filled out. If there is more than one, then separate by commas (TR-233D, TR-232C).

Block 9b. CAGE code.

Enter the CAGE code for the activity originating the ECP.

(NUWC: 50225)

Block 9c. N/A.

Block 9d. Originator’s No.

Contractor: Number shall be limited to 7 characters. The number shall be retained for any subsequent resubmissions. This number will be integrated into the government assigned number in Block 3.

NUWC: same as Box 3.

Block 9e. Type.

Enter either a "P" for preliminary, or "F" for formal.

Block 9f. Revision.

If an ECP is being revised after being signed, attach a new top sheet which contains all the content of the original, excluding any signatures, with the following modifications and additions:

Block 1 shall be the submission date of the revision.

Block 2 shall also include a line that summarizes the information that differs from the original submission (for example, R1: Typo on part number).

Block 3, “R1” or applicable revision number shall be appended to the government number.

Block 9f, “R1”. Further revisions shall be identified as “R2”, “R3”, etc.

Applicable blocks shall be annotated with the information preceded by “R1: ..”

Block 17, (add for example) “R1: corrects …”.

Block 10. Baseline Affected.

“Functional” for the Functional Baseline (CIPS) of the CI is affected. “Product” if the Product Baseline

(DWG PKG) is affected.

Block 11. Other System/Configuration Items Affected.

Enter "yes" or "no", as applicable, to indicate whether there is an effect on other systems or CI’s.

Review the Check List.

Block 12. Specifications Affected.

If the Functional Baseline is affected by the ECP, identify it by CAGE code (normally 53711), document number, revision letter, and the SCN number (if applicable). Normally this will be in line c.

Note that the existing revision letter of the drawing is recorded, not the proposed revision letter. If the

ECP is for the Initial Release of any drawing, record the CAGE Code, drawing number + “(initial release)”, and leave the revision letter box empty.

Block 13. Drawings Affected.

If the Product Baseline or another related drawing is affected by the ECP, it shall be identified by its

CAGE code (normally 53711), drawing number, and revision letter. Note that the existing revision letter of the drawing is recorded, not the proposed revision letter. If more than six drawings are affected, enter

“Enclosure 1” on the first line. Attach the list of affected drawings. If the drawing is an initial release, record the CAGE Code, drawing number + “(initial release)”, and leave the revision letter box empty.

Block 14. Contract Number, CLIN, and Delivery Order Number.

Enter the number of the active contract, CLIN, and Delivery or Task Order Number affected. Or enter

“N/A” if no contract is in effect. More than one set may be listed.

Block 15. Name of Lowest Part/Assembly Affected

Enter the part or assembly that the ECP affects, for example, Ceramic Ring, or Ceramic Stack

Assembly.

Block 16. In Production.

Indicate “yes” if deliveries have not been completed on the contract(s), indicate "no" if the deliveries have been completed, or N/A if there is no contract.

Block 17. Description of change

The description of the proposed change shall be given in sufficient detail to adequately describe what is to be accomplished. Supplemental sketches and data shall be provided to the extent necessary to clearly portray the proposed change(s). If additional space is needed, use Enclosure pages for details but provide an overview in this block. Typically, for a CIPS, an enclosure consisting of a table (xlsx) is used that contains columns labeled Page, Paragraph, From, To, and Justification. For a drawing, an enclosure consisting of a document (docx) is used that contains text with the following information: Drawing

Number, Zone, Add, Revise (From, To) or Delete, and Justification.

Block 18. Need for change.

Enter an explanation of the need (or justification) for the change to include specific information identifying the benefit of the change. Why or what happened to initiate the change. If using a From/To

Enclosure (see Block 17 instructions), indicate the reason(s) in the Justification column and provide an overview in this block.

Block 19. Effectivity by serial number

If block 16 is “no”, then enter “N/A”. If block 16 is “yes”, then enter the production effectivity serial number(s). Examples: “A015, A017”, “A015 and up”, “All production” (if production has not started), All Future Production…

Block 20. Effect on delivery schedule

State the estimated delivery schedule of items incorporating the change, either in terms of days after contractual approval, or by specific dates contingent upon contractual approval by a specified date. State

“N/A” if there will be no effect on the delivery schedule.

Block 21. Submitting Activity

Contractor: An authorized official of the activity entered in Block 5 shall fill in and sign Block 21. This indicates the ECP has the official sanction of the submitting activity.

NUWC: Typically the TDA.

Block 22. Concur/Do Not Concur and Approval/Disapproval

These blocks are for Government use.

The first line is for the lead systems engineer (LSE) to concur or not concur with the classification and with the proposal.

Class II ECP: The following lines are for the Acquisition Manager (ACQ), the Integrated Logistics

Support person (ILS), the TDA, and any other consultants (shipyard, SUBMEPP, …) as required, to concur or not concur with the proposal. Page 2 contains extra lines which can be used, if required. The bottom line of page 1 is for the CM Manager to approve or disapprove of the proposal.

Class I ECP: Is the same as Class II with the following differences: the Chief Engineer and a Systems consultant are added and the Approver becomes NAVSEA PEOSUB PMS4013T.

4. DODAAC

66604

3. GOVERNMENT NO.

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only; Critical Technology (26Jan2015). Other U.S. requests shall be referred to the Naval Undersea Warfare Center Division, Newport, RI.

17. DESCRIPTION OF CHANGE

15. NAME OF LOWEST PART/ASSEMBLY AFFECTED 16. IN PRODUCTION

No

11. OTHER SYS./CONFIG. ITEMS AFFECTED

No

10. BASELINE AFFECTED

1. Date

1/26/2015

a. TYPED NAME

Elizabeth A. McLaughlin

c. ADDRESS

1176 Howell St., Newport, RI 02841

6. CLASS OF ECP

II

b. PHONE NUMBER

401-832-5103

d. E-MAIL ADDRESS elizabeth.mclaughlin@navy.mil

a. MODEL/TYPE

[Unknown]

d. ORIGINATOR NO. e. TYPE

F

f. REV

2. TITLE OF CHANGE

18. NEED FOR CHANGE

19. EFFECTIVITY BY SERIAL NUMBER 20. EFFECT ON DELIVERY SCHEDULE

None

NUWCDIVNPT, Code 1535, ACQ

Form Approved

NAVSEA NEWPORT

CM-ECP OCT 2014

(MM/DD/YYYY)

5. ORIGINATOR (First, Middle Initial, Last) (Street, City, State, Zip Code)

9. ECP DESIGNATION

12. SPECIFICATIONS AFFECTED 13. DRAWINGS AFFECTED

CAGE Code Specification/Document No. REV. SCN

a. SYSTEM

b. DEVELOPMENT

c. PRODUCTION

CAGE Code NUMBER REV.

21. SUBMITTING ACTIVITY

22. APPROVAL/DISAPPROVAL

ENGINEERING CHANGE PROPOSAL (ECP)

CM-ECP OCTOBER 2014 PREVIOUS EDITIONS ARE OBSOLETE PAGE 1

7. JUST. CODE

Compatibility

8. PRIORITY

Routine

b. CAGE CODE

50225

14. Contract NO.

APPROVAL

Concur Do Not Concur

NUWCDIVNPT, Code 1535, LSEYes No

TYPED NAME

Ronald J. Rego

Gerald J. Roche

SIGNATURE DATE SIGNED

ACTIVITYAPPROVAL TYPED NAME SIGNATURE DATE SIGNED

NUWCDIVNPT, Code 1535, TDAConcur Do Not Concur

Concur Do Not Concur

GOVERNMENT ACTIVITY

Concur Do Not Concur

NUWCDIVNPT, Code 1535, CMApproved Disapproved Elizabeth A. McLaughlin

Concur w/ Classification

23. APPROVAL/DISAPPROVAL CONTINUED

ENGINEERING CHANGE PROPOSAL (ECP), PAGE 2 Form Approved

NAVSEA NEWPORT

CM-ECP OCT 2014

GOVERNMENT NO.

APPROVAL

Concur Do Not Concur

a. TYPED NAME SIGNATURE DATE SIGNEDGOVERNMENT ACTIVITY

Concur Do Not Concur

Concur Do Not Concur

3.2 Request for Deviation (RFD) Instructions and Form

Distribution Statement D

Insert date RFD generated (for example 26Jan2015).

Block 1. Date

Contractor: The date shall be the date on which the ECP is submitted to the Government.

NUWC: Date corresponds to the date that the Government Number (Box 3) is assigned.

Block 2. Title

The title shall begin with the Model of the configuration item (CI), and consist of keywords that identify the proposed deviation(s). A CI is an item with an NSN. It is a lowest replaceable unit (LRU), for example: a hydrophone, projector, OBE, cable, window, or dome. Example titles: TR-338C, Housing

Dimension, or DT-705A, Test Requirement for Noise, DT-102 Cable, Length.

Block 3. Government No

The Government Number is assigned upon receipt of the RFD from the Contractor. The Originator No., Box 9d, will be appended.

Block 4. Department of Defense Activity Address Code (DoDAAC)

Enter the DoDAAC of the procuring activity. The DoDAAC is a six position code that uniquely identifies a unit, activity, or organization that has the authority to requisition and/or receive material.

The first position designates the particular Service/Agency element of ownership. NUWCDIVNPT is

N66604, NAVSEA is N00024.

Block 5a, b, c, and d. Originator.

Contractor: Enter the name (point of contact), phone number, mailing address and e-mail address of the submitting activity.

NUWC: Use CM Manager.

Block 6. Classification of RFD

In general, enter “Major” if the deviation affects the “form, fit, or function” of the CI, and enter “Minor” if the change does NOT affect the “form, fit, or function”.

Major: the nonconformance involves: health, performance, interchangeability, reliability, survivability, or maintainability of the item or its repair parts, use of operation, weight, appearance, or safety.

Minor: the nonconformance does not involve any of the factors listed for Major.

Block 7. Block 7. Justification code

Enter the justification code, which is applicable to the proposed engineering change.

A – Administrative (Government Use Only) – this is for record only. This applies to, for example, the initial release of drawings/documents into the configuration management system.

D - Deficiency – this cannot be safety, interface, or compatibility related.

P - Production stoppage – is required to prevent slippage in an approved production schedule. This code applies when production to the current configuration documentation either is impractical or cannot be accomplished without delay.

S - Safety – if this code is used a system hazard analysis must be included. Refer to MIL-STD-882.

Block 8. Priority

A priority shall be recommend, enter an "E", "U", or "R" (Emergency-48 hours, Urgent-30 days, or

Routine-90 days).

Block 9. RFD Designation.

Block 9a. Model/Type.

Enter model or type designation of the CI for which this request is being filled out. If there is more than one, then separate by commas (TR-233D, TR-232C).

Block 9b. CAGE code.

Enter the CAGE code for the activity originating the ECP.

(NUWC: 50225)

Block 9c. N/A.

Block 9d. Originator’s Number.

Contractor: Number shall be limited to 7 characters. The number shall be retained for all subsequent resubmissions, if any. This number will be integrated into the government assigned number in Block 3.

NUWC: same as Box 3.

Block 9e. Type

Enter either a "P" for preliminary, or "F" for formal.

Block 9f. Revision

If an RFD is being revised after being signed, attach a new top sheet which contains all the content of the original, excluding any signatures, with the following modifications and additions:

Block 1 shall be the submission date of the revision.

Block 2 shall also include a line that summarizes the information that differs from the original submission (for example, R1: Typo on part number).

Block 3, “R1” or applicable revision number shall be appended to the government number.

Block 9f, “R1”. Further revisions shall be identified by “R2”, “R3”, etc.

Applicable blocks shall be annotated with the information preceded by “R1: ..”

Block 17, (add for example) “R1: corrects …”.

Block 10. Baseline Affected.

“Functional” for the Functional Baseline (Critical Item Performance Specification) of the CI is affected.

“Product” if the Product Baseline (drawing package) is affected.

Block 11. Other System/Configuration Items Affected.

Enter "yes" or "no", as applicable, to indicate whether there is an effect on other systems or CI’s.

Review the Check List.

Block 12. Specifications Affected

If the Functional Baseline is affected by the RFD, identify it by CAGE code (normally 53711), document number, revision letter, and the SCN number (if applicable). Normally this will be in line c.

Block 13. Drawings Affected

If the Product Baseline or another related drawing is affected by the RFD, it shall be identified by its

CAGE code (normally 53711), document number, and revision letter. If more than six drawings are affected, enter “Enclosure 1” on the first line. Attach the list of affected drawings.

Block 14. Contract Number

Enter the number of the active contract, CLIN, and Delivery or Task Order Number affected. Or enter

“N/A” if no contract is in effect. More than one set may be listed.

Block 15. Name of Lowest Part/Assembly Affected

Enter the part or assembly that the ECP affects, for example, Ceramic Ring, or Ceramic Stack

Assembly.

Block 16. Recurring

Enter “yes” or “no”. This block identifies whether or not the deviation has been requested and approved previously. If “yes” then reference the previous deviation in Block 17, also provide rationale why the recurrence was not prevented by previous corrective action and/or accomplished design change.

Block 17. Description of Deviation

Include the purpose and give sufficient detail to adequately describe what is affected by the RFD. Cite the CIPS paragraph(s) and/or DWG description(s) and values that are not being met. Supplemental material shall be provided to the extent necessary to clearly define the RFD. If additional space is needed, use Enclosure pages for details but provide an overview in this block.

Block 18. Need for Deviation

Explain why it is impossible or unreasonable to comply with the configuration documentation within the specified delivery schedule. Also explain why the deviation is proposed in lieu of a permanent design change.

Block 19. Corrective Action

Describe action being taken to correct non-conformance to prevent future recurrence.

Block 20. Effectivity

Identify the items affected. Enter as applicable, the serial numbers of the items affected, or the lot number(s) applicable to the lot(s) affected by the deviation being requested. (Note delivery/task order is in Block 14.)

Block 21. Effect on Delivery Schedule.

State the effects on the contract delivery schedule that will result from both approval and disapproval of the request.

Block 22. Submitting Activity

Contractor: An authorized official of the activity entered in Block 5 shall fill in and sign Block 21. This indicates the RFD has the official sanction of the submitting activity.

NUWC: Typically the TDA.

Block 23 Concur/Do Not Concur and Approval/Disapproval.

These blocks are for Government use.

The first line is for the lead systems engineer (LSE) to concur or not concur with the classification and with the proposal.

Minor RFD: The following lines are for the Acquisition Manager (ACQ), the Integrated Logistics

Support person (ILS), the TDA, and any other consultants (shipyard, SUBMEPP, …) as required, to concur or not concur with the proposal. Page 2 contains extra lines which can be used if required. The bottom line of page 1 is for the CM Manager to approve or disapprove of the proposal.

Major RFD: Is the same as Class II with the following differences: the Chief Engineer and a Systems consultant are added and the Approver becomes NAVSEA PEOSUB PMS4013T.

4. DODAAC

66604

3. GOVERNMENT NO.

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only; Critical Technology (26Jan2015). Other U.S. requests shall be referred to the Naval Undersea Warfare Center Division, Newport, RI.

17. DESCRIPTION OF DEVIATION

15. NAME OF LOWEST PART/ASSEMBLY AFFECTED 16. RECURRING

No

11. OTHER SYS./CONFIG. ITEMS AFFECTED

No

10. BASELINE AFFECTED

1. Date

1/26/2015

a. TYPED NAME

Elizabeth A. McLaughlin

c. ADDRESS

1176 Howell St., Newport, RI 02841

b. PHONE NUMBER

401-832-5103

d. E-MAIL ADDRESS elizabeth.mclaughlin@navy.mil

a. MODEL/TYPE

[Unknown]

d. ORIGINATOR NO. e. TYPE

F

f. REV

2. TITLE OF DEVIATION

18. NEED FOR DEVIATION

20. EFFECTIVITY BY SERIAL NUMBER 21. EFFECT ON DELIVERY SCHEDULE

None

NUWCDIVNPT, Code 1535, ACQ

Form Approved

NAVSEA NEWPORT

CM-RFD DEC 2014

(MM/DD/YYYY)

5. ORIGINATOR (First, Middle Initial, Last) (Street, City, State, Zip Code)

9. RFD DESIGNATION

12. SPECIFICATIONS AFFECTED 13. DRAWINGS AFFECTED

CAGE Code Specification/Document No. REV. SCN

a. SYSTEM

b. DEVELOPMENT

c. PRODUCTION

CAGE Code NUMBER REV.

22. SUBMITTING ACTIVITY

23. APPROVAL/DISAPPROVAL

REQUEST FOR DEVIATION (RFD)

CM-RFD DEC 2014 PREVIOUS EDITIONS ARE OBSOLETE PAGE 1

7. JUST. CODE

Compatibility

8. PRIORITY

Routine

b. CAGE CODE

50225

14. Contract NO.

APPROVAL

Concur Do Not Concur

NUWCDIVNPT, Code 1535, LSEYes No

TYPED NAME

Ronald J. Rego

Gerald J. Roche

SIGNATURE DATE SIGNED

ACTIVITYAPPROVAL TYPED NAME SIGNATURE DATE SIGNED

NUWCDIVNPT, Code 1535, TDAConcur Do Not Concur

Concur Do Not Concur

GOVERNMENT ACTIVITY

Concur Do Not Concur

NUWCDIVNPT, Code 1535, CMApproved Disapproved Elizabeth A. McLaughlin

Concur w/ Classification

6. CLASS OF RFD

Minor

19. CORRECTIVE ACTION TAKEN

24. APPROVAL/DISAPPROVAL CONTINUED

REQUEST FOR DEVIATION (RFD), PAGE 2 Form Approved

NAVSEA NEWPORT

CM-RFD DEC 2014

GOVERNMENT NO.

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only; Critical Technology (26Jan2015). Other U.S. requests shall be referred to the Naval Undersea Warfare Center Division, Newport, RI.

APPROVAL

Concur Do Not Concur

a. TYPED NAME SIGNATURE DATE SIGNEDGOVERNMENT ACTIVITY

Concur Do Not Concur

Concur Do Not Concur

3.3 ECD Checklist

(See next page.)

CM_CHECKLIST FORM 26Jan2015

ECD Checklist Title and/or Short Description: ______________________________________________________

ECD Number: _____________________________ Date: __________________

Potential Impact YES NO POC RESULTS

Other systems / equipments impacted?

If yes, then what?

Technical Documentation Impacted:

Technical Manual

CIPS (including Restoration Requirements)

Maintenance Requirement Cards (MRCs)

Installation Control Drawings (ICDs)

Test Procedures (CSTP, etc.)

Technical Repair Standard (TRS)

Allowance Parts List (APLs)

Baseline Drawings

Training

Special Purpose Tools & Test Equipment (SPT&TE)

Packaging, Handling, Shipping & Transportation (PHS&T)

Safety

Reliability

Cost change? (short term and/or long term)

Existing Production (Back-fit required)

Hull, Mechanical & Electrical (HM&E)

NSN (form, fit, and/or function changed?)

Distribution – informational copies to: ______________________________________________

Additional signatures? ___________________________________________________________

TDA (print name) Signature Date blank: