ALE-47_SOW-3_1_14-30059.pdf_-__-_06-27-2014.pdf

SOW 3.1 Revision – 3 Jun 2014

Statement Of Work

For

AN/ALE-47 Countermeasures Dispenser System

Production-3.1

Prepared By:

SOF, Chaff/Flare, and EO/IR Engineering Element

AFLCMC/WNYEAB

Approved By: Air Force Life Cycle Management Center

EW/Avionics Engineering Branch

Robins AFB, GA 31098–1813

SIGNATURE: __________________________________

Enrique Leon, Deputy

EW/Avionics Engineering Branch

Electronic Warfare & Avionics Division

DISTRIBUTION STATEMENT A: Approved for Public Release.

File No. FD2060-14-30059 Page 1 of 49

SOW 3.1 Revision - 3 Jun 2014

Revision Page

The following revisions have been made to this document:

# Revision Affected Pages

File No. FD2060-14-30059 Page 2 of 49

Table Of Contents

1. Background

1.1 Objectives

1.2 Scope

2. Requirements

2.1 Pre-Production Requirements (Reserved)

2.2 Production Requirements

2.2.1 Environmental Stress Screening (ESS)

2.2.2 Production Acceptance Test

2.2.2.1 Production LRU ATPs

2.2.2.2 Production SRU ATPs

2.2.3 Production Interchangeability Test

2.3 System Software Loading

2.3.1 Control Display Unit (CDU)

2.3.2 Programmer

2.3.3 Sequencer

2.4 Lead-Free Control Plan

2.5 Program Management

2.5.1 Post Award Conference

2.5.2 Program Management Reviews (PMRs)

2.5.3 Technical Interchange Meetings (TIMs)

2.5.4 Production Surveillance and Reporting System

2.6 Communications

2.7 Data Management

2.7.1 Data Accession List (DAL)/Internal Data

2.7.2 GFE Detail Transaction Status Data Report

2.7.3 Rights In Data

2.8 Configuration Management

2.8.1 ECPs, NORs, And Deviations

2.8.2 Programmable Devices

2.8.3 Parts Management

2.8.4 Counterfeti Prevention Plan

2.8.4.1 Risk Assessment

2.8.4.2 Counterfeit Notificatoina and Reporting

2.8.4.3 Detection and Avoidance Responsabilities

2.8.4.4 Counterfeit Prevention Training

2.8.5 Engineering Data

2.8.5.1 Engineering Data Guidance Conference

2.8.5.2 In-Process Review (IPR) of the TDP

2.8.5.3 Relationship of Contractor with Subcontractors/Vendors

2.8.5.4 Engineering Data Updates and Revisions

2.8.6 Technical Manuals

2.9 Safety

File No. FD2060-14-30059 Page 3 of 49

2.10 Green Procurement Program

2.11 Security Requirements

2.11.1 Government Security Regulations

2.11.2 Security Regulations

2.11.3 Operations Security (OPSEC)

2.11.4 Security Clearance

2.11.5 Security Incident or Violation

2.11.6 Security of Contractor Systems(s)

2.11.7 Access to Government Facility

2.11.8 Access to Robins AFB

2.11.8.1 Background Check

2.11.8.2 Entry to Robins AFB

2.11.8.3 Identification of Contractor Personnel Requiring Access

2.11.8.4 Defense Biometric Identification System (DBIDS) Identification (ID) Card ..30

2.11.9 Labeling Of Classified Hardware

2.12 Warranty

2.13 Warranty Returns of Classified Hardware

3. Government Furnished Property and Services

3.1 Government Furnished Equipment (GFE)

3.2 Reporting Loss Of Government Property

3.3 Government Furnished Software (GFS)

4. General Information

4.1 Cautions

4.1.1 Obsolete Parts

4.1.2 Code For Programmable Parts

4.1.3 PCB Apertures

4.1.4 Gerber File Format

4.1.5 TRDs In The TDP

4.1.6 Integrated System Performance Test

4.1.7 Programmer Discrete I/O CCA ATP

4.1.8 Sequencer Poll Source Circuit

4.1.9 Missing Drawings

4.2 Applicable Documents and Order of Precedence

4.2.1 Military Standards

4.2.2 Other Documents

4.3 Definitions

Attachment 1. LRU Listing

Attachment 2. SRU Listing

Attachment 3. MIL–STD–882E Extracted Requirements

File No. FD2060-14-30059 Page 4 of 49

1. Background

The AN/ALE-47(V) Countermeasures Dispenser System (CMDS) is an integrated, threat-adaptive, reprogrammable, computer-controlled airborne defensive system. The AN/ALE-47 dispenses countermeasure decoys (Chaff, Flare and others) against radar and infrared homing threats to enhance aircraft survivability.

The AN/ALE-47 CMDS procurable under this Statement Of Work consists of the Line

Replaceable Units (LRUs) listed in Attachment 1. Each LRU consist of one or more lower assemblies called Shop Replaceable Units (SRUs). See Attachment 2 for a list of SRUs. The individual aircraft determines the system configuration and the number of LRUs.

The Air Force and Army support the AN/ALE-47 with two-level maintenance concept. The

Navy supports the AN/ALE-47 with a three-level maintenance concept. Warner Robins Air

Logistics Complex (previously Warner Robins Air Logistics Center) is the organic depot for Air

Force, Army, and Navy AN/ALE-47 hardware and Operational Flight Program (OFP) software.

1.1 Objectives

This Statement Of Work identifies the objectives to fabricate, integrate components, test, and deliver production LRUs and SRUs in accordance with the Technical Data Package (TDP) and contract schedule. Other objectives include corrective action and maintenance of the TDP.

AN/ALE-47 production will support Air Force, Navy, Army and Foreign Military Sales (FMS) aircraft.

1.2 Scope

This Statement Of Work is applicable to Contractors that the Government has considered qualified on all LRUs listed in Attachment 1.

File No. FD2060-14-30059 Page 5 of 49

2. Requirements

2.1 Pre-Production Requirements (Reserved)

2.2 Production Requirements

The Contractor must obtain a delivery order from the Government Procuring Contracting Officer

(PCO) before commencement of production. The Contractor shall fabricate, integrate, test and deliver LRUs listed in Attachment 1 and SRUs listed in Attachment 2 in accordance with the quantities listed in each contract delivery order. The Contractor’s production articles shall conform to the contract, this Statement Of Work, and the TDP. The Contractor shall maintain current test equipment calibration in accordance with the requirements of ANSI/NCSL-Z540.3.

2.2.1 Environmental Stress Screening (ESS)

The Contractor shall prepare a Reliability Test Plan (subtitle Environmental Stress Screening

(ESS) Procedures) for each LRU listed in Attachment 1, excluding the Safety Switch and the

Dispenser. ESS Procedures prepared under a prior contract are not acceptable. ESS procedures shall be consistent with requirements specified by each LRU’s Critical Item Product Fabrication

Specification (CIPFS). The ESS procedures shall use the number of thermal cycles specified by the Sequencer CIPFS when an LRU's CIPFS does not specify the number of cycles. The

Contractor may cover multiple LRUs in an ESS Procedures document. ESS Procedures shall include:

• LRU(s) covered and the LRU(s) part number(s),

• Types of failures classified as nonrelevant,

• Step by step procedures,

• Pass criteria,

• Data to be recorded,

• Sample data sheets,

• Identification of computer software to be used, if applicable,

• Computer software to be used, if applicable (source and object code),

• Action to be taken if a reject decision is reached,

• List of test equipment, File No. FD2060-14-30059 Page 6 of 49

• Test equipment calibration requirements,

• Test set-up including interconnecting cable diagrams and cable labels, and

• Requirements for root cause analysis and failure determination for failed items.

The Contractor shall obtain Government approval of ESS procedures before using the procedures for ESS. The Contractor shall conduct ESS on each production LRU. The Contractor shall conduct ESS on each SRU that the Contractor will sell to the Government as an individual SRU

(not part of an LRU). The Contractor shall conduct SRU ESS with the SRU installed in a

Contractor-furnished LRU. The Contractor-furnished LRU shall be externally marked for ESS and shall not be sold to the Government under a production delivery order. Each LRU and separately procured SRU must pass ESS before proceeding to the Contractor's final Acceptance

Test. The Contractor shall summarize and report ESS results, including failure determination data, in the Status Report.

(A001, DI-NDTI-81585A/T) (A002, DI-MGMT-80368A)

If an uncosted Engineering Change Proposal proposes to use a part that has a temperature range not meeting the temperature requirements of the target LRU, the Contractor shall first have conducted ESS using a prototype item with the proposed Engineering Change Proposal incorporated. If a costed Engineering Change Proposal proposes to use a part that has a temperature range not meeting the temperature requirements of the target LRU, the Contractor shall include ESS in the proposed Engineering Change Proposal. See paragraph 2.8.1 for other

Engineering Change Proposal requirements.

2.2.2 Production Acceptance Test

The Contractor shall conduct Acceptance Test on each production LRU. See Attachment 1 for a list of LRUs.

File No. FD2060-14-30059 Page 7 of 49

See Attachment 2 for a list of SRUs. The Contractor shall conduct Acceptance Test on each production SRU that is sold separately except as follows. The Contractor may not initially have

Government approved SRU Acceptance Test Procedures for all SRUs when the contract is awarded. Therefore, the following "grace period" Acceptance Test provisions apply to production SRUs that are sold separately. For up to 384 days After Receipt of Order for the first

SRU, the Contractor shall conduct Acceptance Test on each production SRU by placing the SRU in its LRU and then conducting LRU Acceptance Test.

The Contractor shall conduct Acceptance Test after passing ESS. The Contractor shall conduct

Acceptance Test using Government approved Acceptance Test Procedures (ATPs). The

Contractor shall document Acceptance Test results in a Test/Inspection Report, using

DI-NDTI-80809B as a guide. The Contractor shall store Test/Inspection Reports and make them available to the Government upon request for up to five years after contract end.

2.2.2.1 Production LRU ATPs

The Contractor may use Government approved LRU ATPs from a prior contract (i.e.

resubmission not required). A Contractor with qualified LRUs has Government approved ATPs for Attachment 1 LRUs. The Contractor remains responsible for the design, development, fabrication, and maintenance of test hardware and software to support its ATPs. Software needed to run or automate the ATP is part of the ATP by definition.

When a change to any Government approved ATP is needed due to a defect discovery or engineering change, the Contractor may submit an unsolicited ATP update for Government approval, or submit the ATP update as part of an Engineering Change Proposal, as applicable.

The Contractor shall submit a technical justification with the changed ATP. The Contractor shall obtain Government approval of each ATP before using the ATP for Acceptance Test.

2.2.2.2 Production SRU ATPs

The Contractor may use Government approved SRU ATPs from a prior contract (i.e.

resubmission not required). A Contractor with qualified LRUs may or may not have

Government approved ATPs for Attachment 2 SRUs. The requirements of this paragraph apply to a Contractor that does not have Government approved ATPs for Attachment 2 SRUs. The

Contractor shall prepare and submit for Government approval an ATP for each SRU listed in

File No. FD2060-14-30059 Page 8 of 49

Attachment 2. The Contractor shall obtain Government approval of each ATP before using the

ATP for Acceptance Test. The Contractor shall have performed dry-run Acceptance Test using its unapproved ATP before submitting it to the Government for approval. The Contractor shall design, develop, and fabricate test hardware and software for ATP use, making use of commercial equivalent test hardware/software where practical. The Contractor's ATP procedures may differ from the TDP's ATP procedures to accommodate different test hardware.

The Contractor's ATP shall identify commercial equivalents of Contractor-peculiar test hardware/software. Software needed to run or automate the ATP is part of the ATP by definition. The Contractor shall deliver ATP software with the ATP. ATPs included in the TDP are for reference only and may lack ATP software. ATPs included in the TDP are intended to provide a starting baseline for the Contractor's preparation of its ATP test cases and pass criteria.

ATPs included in the TDP may contain imperfect test cases and pass criteria, or may depend on software that is no longer available. See also paragraph 4.1.7 concerning an ATP that is missing from the TDP. The Contractor's ATP test cases and pass criteria may therefore deviate from the

ATPs contained in the TDP. When deviations from the TDP's ATP test cases or pass criteria are needed, the Contractor shall submit a technical justification for the deviations concurrent with the ATP submission. Acceptability of the deviations is at the sole discretion of Government engineering.

(Exhibit C, DI-NDTI-80603A)

When a change to any Government approved ATP is needed due to a defect discovery or engineering change, the Contractor may submit an unsolicited ATP update for Government approval, or submit the ATP update as part of an Engineering Change Proposal, as applicable.

The Contractor shall submit a technical justification with the changed ATP. The Contractor shall obtain Government approval of each ATP before using the ATP for Acceptance Test.

File No. FD2060-14-30059 Page 9 of 49

2.2.3 Production Interchangeability Test

The purpose of Production Interchangeability Test is to ensure standardization of the

Contractor's production items. In other words, to ensure that an Engineering Change Proposal implementation will not impact an individual LRU's or SRU's form, fit, and function. The

Contractor shall conduct Production Interchangeability Test before submitting uncosted

Engineering Change Proposals and report the test results in the Engineering Change Proposal.

The Contractor shall include a requirement for Interchangeability Test as part of a costed

Engineering Change Proposal submission. Production Interchangeability Test consist of:

• Conducting an SRU Acceptance Test with the proposed Engineering Change Proposal installed. (This requirement does not apply when the Contractor does not have a

Government approved ATP for the affected SRU.)

• Placing the SRU, with the proposed Engineering Change Proposal installed, into a

Contractor produced LRU and performing LRU Acceptance Test.

• Placing the SRU, with the proposed Engineering Change Proposal installed, into a

Government Furnished Tracor LRU and performing LRU Acceptance Test.

• Placing the SRU, with the proposed Engineering Change Proposal installed, into a

Government Furnished Symetrics LRU and performing LRU Acceptance Test.

See paragraph 3.1 for Government Furnished Equipment. See paragraph 2.8.1 for other

Engineering Change Proposal requirements. The Production Interchangeability Test requirement does not apply when an Engineering Change Proposal:

• affects the Safety Switch because it has no SRUs, or

• does not affect an item's technical requirements. For example, altering a drawing to change the suggested source of supply.

File No. FD2060-14-30059 Page 10 of 49

2.3 System Software Loading

The Contractor is responsible for fabricating or procuring all hardware, software (excluding

Government Furnished Software), and technical skills required to meet the requirements of

System Software Loading subparagraphs. The Government may render little or no System

Software Loading technical assistance to the Contractor.

2.3.1 Control Display Unit (CDU)

Before CDU sell-off, or, when sold separately, before Central Processing Unit (CPU) Circuit

Card Assembly (CCA) 1A3A1 sell-off, the Contractor shall load Firmware as indicated in paragraph 3.3, or as directed by the Procuring Contracting Officer (PCO).

2.3.2 Programmer

Before Programmer sell-off, the Contractor shall load firmware and software into the

Programmer, or, when sold separately, the CPU CCA 2A3 as indicated in paragraph 3.3, or as directed by the Procuring Contracting Officer (PCO).

2.3.3 Sequencer

Before Sequencer sell-off, the Contractor shall load firmware and software into the Sequencer, or when sold separately, the Control Logic CCA 8A2A2 as indicated in paragraph 3.3, or as directed by the Procuring Contracting Officer (PCO).

File No. FD2060-14-30059 Page 11 of 49

2.4 Lead-Free Control Plan

The Contractor shall develop a Lead-Free control plan to ensure that all equipment supplied by the Contractor shall meet the reliability and product life requirements of project specification(s) including the absence of, and prevention of Tin Whiskers and other deficiencies caused by the use of Lead-Free solder and components. The authorized soldering processes (SnPb, 1, 2, 3, or

4) identified in paragraph 6.2.3 and associated Table 1 of WR-ALC Lead-Free Control Plan assure meeting these reliability requirements. The use of non-Sn (e.g. gold, nickel palladium, nickel palladium gold) as a termination finish is permitted (process 1) and presents no Tin whisker risk. The use of hot solder dipping (process 2); pure Sn as a termination finish (process

3); and pure Sn as a termination and board finish (process 4) present reliability risks due to Tin whiskering, but are permitted provided Tin whisker mitigation per GEIA-STD-0005-2 has been utilized.

The Lead Free Control Plan shall implement all applicable provisions of WR-ALC Lead-Free

Control Plan and shall demonstrate how the Contractor shall be compliant with same. The

Contractor's Lead-Free Control Plan shall include provisions for testing, evaluation, and analysis to ensure that any hardware produced under this contract shall meet the expected reliability requirements of the TDP associated with this effort. The Contractor shall roll the testing requirements into any Qualification Test Plan/Procedures required under this contract.

(A003, DI-MISC-80508B)

2.5 Program Management

The Contractor shall perform program management tasks. Tasks include planning, budgeting, financial management, Production schedules, and directing and monitoring contract tasks. The

Contractor shall submit regular Status Reports and Integrated Master Schedules. The Status

Report shall contain information on warranty returns, repair information, and number of items delivered. Repair information is cumulative identification of the failed SRUs and associated components.

(A002, DI-MGMT-80368A) (A005, DI-MGMT-81650)

File No. FD2060-14-30059 Page 12 of 49 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A002 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A005

2.5.1 Post Award Conference

The Contractor shall attend a Post Award Conference at Robins Air Force Base within 60 days after contract award. The Contractor shall submit a conference agenda and conference minutes.

The Post Award Conference is intended to ensure that all parties understand the contract requirements and to identify and clarify the roles of Government personnel who will be involved in performance assessment and the contract administration. Below are topics that should be addressed at the Post Award Conference.

• Points of Contact and roles

• Contract Performance Assessment Report (CPAR)

• Statement Of Work review

• Deliverables and Acceptance Procedures

• Payment and Invoice Procedures

• Government Furnished Property

• Safety Requirements

• Security Procedures and Requirements

• Technical Manual Update Requirements

• Engineering Data Guidance Conference (See paragraph 2.8.5.1)

(A006, DI-ADMN-81249A) (A007, DI-ADMN-81250A)

2.5.2 Program Management Reviews (PMRs)

The Contractor shall schedule and conduct up to two annual PMRs per year. The Contractor shall host half of the PMRs at its facility, and travel to Robins Air Force Base for the other half.

At the Government's option, it may elect to replace travel with teleconference for any PMR. The

Contractor shall combine all conferences/meetings to fullest extent possible. The Contractor shall submit a conference agenda and conference minutes for each meeting.

(A006, DI-ADMN-81249A) (A007, DI-ADMN-81250A)

File No. FD2060-14-30059 Page 13 of 49 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A006 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A007 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A006

2.5.3 Technical Interchange Meetings (TIMs)

The Contractor shall host, conduct, and document up to five (5) TIMs for the life of the contract.

The Contractor shall submit a conference agenda and conference minutes for each meeting.

(A006, DI-ADMN-81249A) (A007, DI-ADMN-81250A)

2.5.4 Production Surveillance and Reporting System

The Contractor shall submit Production Status Reports documenting a surveillance system. The surveillance system shall document the progress toward meeting milestones and contractual delivery schedules. The system shall identify factors that may prevent hardware delivery in accordance with the schedule. The system shall reflect the time phasing of critical components from order release through final stocking. Critical components include in-house and major purchased/subcontract items.

(A004, DI-MGMT-81255)

2.6 Communications

The Contractor shall not divulge information related to this effort to any parties other than those called out in this Statement Of Work without written permission from the Government Procuring

Contracting Officer (PCO). The Contractor and the Government need to communicate effectively and in a timely manner with each other when issues/questions arise from the

Contractor’s investigation, analysis, or other efforts supported within this Statement Of Work.

Communications may be conducted in the form of telephone conversations, email, official letters, meetings or any other form that is needed.

2.7 Data Management

The Contractor shall implement and use a web site and email for communication and delivery of

CDRL items. Web site usage shall not require the Government to install Trust Certificate(s) on its computers as a condition of data access and data down-load. Performance of this Statement

Of Work requires the Contractor to have Microsoft Office Professional 2010 and Adobe Acrobat

X Professional or later versions thereof.

File No. FD2060-14-30059 Page 14 of 49 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A006 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A007 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A004

The Contractor shall establish, implement, and maintain a data management program process.

Data Management shall collect, control, and distribute documents in accordance with this

Statement Of Work and the CDRLs. The Contractor shall assure that subcontractor(s) data management procedures, programs, and data meet the requirements of this Statement Of Work.

The Contractor shall not make partial data deliveries.

The Contractor shall place the following on each and every page of data submitted under CDRL

Exhibits A and C: CAGE code (Contractor's CAGE for Exhibit A; CAGE 98752 for Exhibit C), document number, revision letter, and document date. Pages should be marked with the page number and the total number of pages. Some exceptions may apply, such as Engineering

Change Proposals and Notice Of Revisions, which have a predefined format and content.

2.7.1 Data Accession List (DAL)/Internal Data

The Contractor shall maintain and provide to the Government a complete listing of all internally generated data resulting from the contract. The Contractor shall deliver data listed on the DAL upon request from the Government.

(A008, DI-MGMT-81453)

2.7.2 GFE Detail Transaction Status Data Report

The Contractor shall not alter or repair Government Furnished Equipment (GFE). The

Contractor shall be responsible for repair cost incurred by the Government, when repair results from improper storage or abuse. See also paragraph 3.1. The Contractor shall report status of the Government Furnished Equipment (GFE) on the GFE Detail Transaction Status Data Report.

(A009, DI-MGMT-80377)

File No. FD2060-14-30059 Page 15 of 49 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A008 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A009

2.7.3 Rights In Data

The Government shall have unlimited non-exclusive rights in data, documentation, computer software, and computer software documentation deliverable under this Statement Of Work or associated Contract Data Requirements Lists. The Government shall have unlimited non-exclusive rights in data, documentation, computer software, and computer software documentation developed exclusively with government funds or developed with mixed funding.

The Contractor shall not mark briefings, reports, drawings, or other types of data with trade secrets markings, proprietary markings, or copyright markings. When the Contractor’s drawings reference design activity specifications / standards, the Contractor shall furnish the complete design requirements, including processes and materials for the item covered and shall deliver the documents without proprietary or copyright limits of any kind. Data produced directly or indirectly, using funds from this contract, becomes Government property.

2.8 Configuration Management

The product starting baseline is the TDP that the Government delivers to the Contractor. The

Contractor shall document and follow a systems engineering process for generating and incorporating new or modified drawings, Engineering Change Proposals, Notice Of Revisions, Engineering Change Orders, and Engineering Orders into the TDP. The Contractor shall incorporate new or modified drawings, Notice Of Revisions and Engineering Orders from the

Government or other manufacturers into the TDP when directed by the Government PCO. The

Contractor is responsible for having engineering capabilities (including systems engineering, reverse engineering, and software engineering) sufficient to resolve TDP defects, resolve diminishing manufacturing resources issues, resolve obsolete parts issues, use and interpret the

TDP, maintain the TDP, and produce modifications to the TDP. The Contractor shall be an accredited organization demonstrating a quality program meeting AS9100C (Quality

Management Systems - Requirements for Aviation, Space and Defense Organizations) requirements.

2.8.1 ECPs, NORs, And Deviations

The Contractor shall prepare and submit an Engineering Change Proposal (ECP) using

DD Form 1692 and Notice Of Revision (NOR) using DD Form 1695 for any proposed TDP File No. FD2060-14-30059 Page 16 of 49 change. MIL-HDBK-61A shall be used as a guide in classifying Class I and Class II

Engineering Change Proposals. The Contractor shall submit price basis information for costed

Engineering Change Proposals. The Contractor shall submit costed ECPs when the

Government's cost will be $15,000 or more. Otherwise ECPs shall be uncosted (i.e. no cost).

An uncosted Engineering Change Proposal shall report passage or failure of ESS (if applicable) and Interchangeability Test (if applicable). When the Engineering Change Proposal does not affect the Life Cycle Cost (LLC), the AN/ALE-47 system or support equipment, engineering, test, software, logistics, Technical Manuals, maintenance, or safety, the Engineering Change

Proposal shall so state. Otherwise, the Contractor's Engineering Change Proposal shall include the impacts to AN/ALE-47 system and support equipment, engineering, test, software, logistics, Technical Manuals, maintenance impacts, safety, and include a Life Cycle Cost (LCC) analysis.

Software includes test software, software used to program programmable devices, Computer

Software Configuration Items (e.g., OFPs), and Mission Data. Applicable Technical Manuals are 12P3-2ALE47-3 and 12P3-2ALE47-4. See paragraph 2.8.6 for other Technical Manual

Requirements. The Contractor shall initially categorize any hardware change that impacts software as a Class I change. With the exception of changes associated with costed Engineering

Change Proposals and Class I changes, the Contractor shall incorporate all Government approved Notice Of Revisions and Engineering Orders into the TDP. The Contractor shall incorporate changes associated with costed Engineering Change Proposals and Class I changes into the TDP only when the change is incorporated into the contract by contract modification, or when directed by the Government PCO. The Contractor shall incorporate Notice Of Revisions and Engineering Orders into the drawings when the Contractor is the current design activity. See paragraph 2.2.1 for ESS requirements and paragraph 2.2.3 for Interchangeability Test requirements related to Engineering Change Proposal submission.

The Contractor shall not consider any Request For Deviation to be effective until it is incorporated into the contract by contract modification, or until directed by the Government

PCO. The Contractor shall use DD Form 1694 to submit Request For Deviations. The scope of

Request For Deviations is the Contractor's ATPs and all TDP content excluding the TDP's ATPs.

The Contractor shall address safety in every Request For Deviation.

File No. FD2060-14-30059 Page 17 of 49

The AN/ALE-47 Air Force engineering office has the discretionary right to require any

Engineering Change Proposal to include Government Inspection And Test. Government

Inspection And Test may include dimensional verification, Interchangeability Test, LRU testing, and some software testing for LRUs containing software.

(A00A, DI-CMAN-80639C) (A00B, DI-CMAN-80642C) (A00C, DI-CMAN-80640C)

2.8.2 Programmable Devices

The Contractor shall have a capability to load firmware and software into components such as

Field Programmable Gate Arrays (FPGA), Programmable Array Logic (PAL), and Erasable

Programmable Read Only Memory (EPROM). The Government provided TDP may lack source code for programmable devices. The Government cannot and will not provide missing source code for programmable devices. The Contractor may need to reverse engineer programmable device object code to the extent needed to satisfy the requirements of this Statement Of Work.

As part of Engineering Change Proposal submission, Notice Of Revision submission, or TDP updates, the Contractor shall develop and deliver drawings (i.e. a software product specification), using DI-IPSC-81441A as a guide, for programmable devices that it replaces due to hardware changes. The drawings shall include source and object code. This software requirement does not apply to Operational Flight Programs (OFPs) and Mission Data Files

(MDFs).

(B001, DI-SESS-81000D/T)

2.8.3 Parts Management

The Contractor shall prepare and submit for Government approval a Parts Management Plan

(PMP). The Contractor may use MIL-STD-3018 as a guide in PMP preparation. The plan shall include a Parts List cross referenced to the TDP's Parts List Item Numbers. Parts identified in the TDP are the starting baseline for the Parts List. The PMP shall address the following:

File No. FD2060-14-30059 Page 18 of 49 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A00A https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A00B https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A00C https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/ALE-47_CDRL_1423_CDRL%202011-12.docx

• Government participation in parts selection,

• procedures for authorizing changes to the Parts List,

• obsolete parts management procedures,

• subcontractor management,

• parts quality, and

• parts documentation

The Contractor shall disclose point of contact information for the source of parts supply to the

Government when so requested. The Contractor shall accomplish 100% parts traceability from the purchase orders to the LRU part number and serial number (if applicable), SRU part number and serial number, contract delivery order, and shipped-to address.

The Contractor is responsible for having the engineering and reverse engineering capability necessary to accomplish parts replacement and redesign associated with diminishing manufacturing resources and parts obsolescence, including reverse engineering associated with

FPGAs and PAL components and associated software. The Contractor shall maintain a parts control program and use qualified parts per MIL-STD-965 when available. The Contractor shall use only new, not other-than-new parts in AN/ALE-47 LRU and SRU manufacture. The

Contractor shall notify the Government that a part is obsolete or will become obsolete within two months of the manufacturer's publication of a Last Time Buy Date. If the manufacturer did not publish a Last Time Buy Date, the Contractor shall notify the Government within two months of learning that a part is obsolete or will become obsolete. To resolve obsolete parts issues, the

Contractor shall follow and accomplish the below steps, in order, within six (6) months of a part becoming obsolete. A lifetime buy of an obsolete part does not meet the requirements of this

Statement Of Work.

a) Locate a second source. If unsuccessful then:

b) Locate a different MIL-qualified part that performs the same function without redesign.

Submit an Engineering Change Proposal and Notice Of Revision for the MIL-qualified part in accordance with paragraph 2.8.1. If unsuccessful then:

File No. FD2060-14-30059 Page 19 of 49

c) Locate a non-standard part that performs the same function without redesign. Submit an

Engineering Change Proposal and Notice Of Revision for the non-standard part in accordance with paragraph 2.8.1. (A separate non-standard parts request is not required.)

If unsuccessful then:

d) Submit an Engineering Change Proposal and Notice Of Revision for redesign in accordance with paragraph 2.8.1.

The Contractor shall use Engineering Change Proposals and Notice Of Revisions to overcome parts obsolescence or correct latent design deficiencies (i.e., correct errors found in the TDP).

No changes shall be permitted that affect the form, fit, or function of the individual LRU, SRU, the system’s functional allocation, or interface definition.

(A00D, DI-SDMP-81748/T)

File No. FD2060-14-30059 Page 20 of 49

2.8.4 Counterfeit Prevention Plan

The contractor shall prepare and submit for Government approval a Counterfeit Prevention Plan

(CPP) for counterfeit parts avoidance, detection and reporting. The Contractor shall base the plan on ASE AS 5553, Aerospace Standard for Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition. The Contractor shall identify all Business locations and programs to which the plan applies. The plan shall address materials, hardware, electronic parts, and procured assemblies. The plan shall identify the appropriate office(s), business units, functional organizations, and programs, who shall have responsibility for development, maintenance and implementation of the plan. The plan shall identify the specific roles and responsibility for each. The plan shall address purchase order requirements for independent distributors/brokers. The plan shall include requirements for part certificate of conformance.

The certificate of conformance must be traceable to the original equipment manufacturer. When a certificate of conformance is not available, the plan must require lot testing. The Contractor shall accomplish inspections on all components received (at the purchase order level) using a certified IDA-ICE-300 Counterfeit Component Auditor/Inspector. The Contractor shall identify and control the configurations of all systems, assemblies, subassemblies and parts, and enable mechanisms to provide traceability of parts. The Contractor shall report to the Government when control of the configurations of all systems, assemblies, subassemblies and parts, and mechanisms to provide traceability of parts are not possible. The Contractor shall identify the specific systems, assemblies, subassemblies and parts beyond the Contractors’ control. The

Contractor shall be responsible for detecting and avoiding the use or inclusion of counterfeit materials and parts, to include procured assemblies and subassemblies, in such products and shall be responsible for the rework or corrective action that may be required to resolve the use or inclusion of counterfeit materials and parts. The cost of counterfeit electronic parts and suspect counterfeit electronic parts and the cost of rework or corrective action that may be required to remedy the use or inclusion of such parts are not allowable costs under Department contracts, unless:

a) the contractor has established a counterfeit avoidance/detection system approved by the

DoD, File No. FD2060-14-30059 Page 21 of 49

b) the counterfeit parts were procured from a DoD-accredited trusted supplier or provided as government property, and

c) the contractor has provided timely notification to the government.

(A00F, DI-MISC-81832)

2.8.4.1 Risk Assessment

The contract shall address the risk of using unknown sources and or unauthorized suppliers in the plan. Application or technical risk assessments shall establish the effect that counterfeit parts may have on performance. Vendor or source of supply risk assessments shall establish the potential for obtaining counterfeit parts. Using any risk analysis tool acceptable to the

Government, the Contractor shall conduct a risk assessment based upon item characteristics and how likely it is that a counterfeit part will be received. The contractor shall identify and describe in the plan how parts are selected for assessment and what risk is acceptable based upon the parts design, construction, material and functional requirements. As a minimum, analysis shall be completed for flagging high risk items, such as items that are obsolete, discontinued, rare, etc.

The contractor shall require completion of a trade study, documented within the plan, that shall facilitate determining whether 100% testing of parts procured from after-market sources is more cost effective than qualification or requalification of a manufacturer. As a minimum, analysis shall be completed for flagging high risk items, such as items that are obsolete, discontinued, rare, etc.

2.8.4.2 Counterfeit Notification and Reporting

The Contractor shall obtain and maintain active membership in Government-Industry Data

Exchange Program (GIDEP). The Contractor shall report suspect counterfeit parts to government investigative authorities, PCO, GIDEP, and to the original equipment manufacturer of the genuine part. The Contractor shall maintain an internal list of counterfeit parts found and make the list and associated data available on the Data Accession List. The associated data shall include:

File No. FD2060-14-30059 Page 22 of 49

• the part's next higher assembly (SRU and/or LRU),

• the counterfeit part number,

• purchase order number,

• date purchased,

• number of pieces purchased,

• supplier name, address and CAGE,

• the original equipment manufacturer name for a genuine part

• date reported to GIDEP

• how the part was determined to be counterfeit,

• organization that made the counterfeit part determination,

• color photo of counterfeit part,

• color photo of genuine part.

2.8.4.3 Detection and Avoidance Responsibilities

The Contractor shall establish processes for the review and approval of contractor and applicable subcontractor systems for the detection and avoidance of counterfeit electronic parts and suspect counterfeit electronic parts, which processes shall be comparable to the processes established for contractor business systems under section 893 of the Ike Skelton National Defense Authorization

Act for Fiscal Year 2011 (Public Law 111–383; 124 Stat. 4311; 10 U.S.C. 2302 note). The

Contractor shall notify their subcontractors of all CPP requirements and processes per ODASD

Memo titled “Overarching DoD Counterfeit Prevention Guidance”.

2.8.4.4 Counterfeit Prevention Training

The Contractor shall provide appropriate training and shall require all personnel working procurement within their company, to include at a minimum their supply chain management specialists, receiving inspectors, and engineers, to complete said training. The plan shall describe and list the training provided by the contractor to their personnel.

File No. FD2060-13-30052 Page 23 of 49

2.8.5 Engineering Data

The primary scope of Engineering Data is that the contractor shall revise the TDP to correct errors and revise the TDP to overcome obsolete parts issues; furnishing back to the Government a TDP that can support a subsequent contractor's production of the AN/ALE-47. The Contractor shall develop/produce/maintain and deliver a revised Technical Data Package (TDP) that accurately depicts Government approved changes. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data created as a result of this contract shall be considered a part of the TDP. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776

(CAGE 98752), reference attached DD Form 1423 Block 16.

(B001, DI-SESS-81000D/T)

2.8.5.1 Engineering Data Guidance Conference

The Contractor shall support and co-chair a Guidance Conference with Air Force Life Cycle

Management Center Engineering Data Management Support Section, AFLCMC/EZGEM, for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the Contractor. The

Contractor shall prepare an agenda and record the minutes of the Guidance Conference. The

Contractor shall address, discuss, and provide status on the following:

(A006, DI-ADMN-81249A) (A007, DI-ADMN-81250A)

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats.

File No. FD2060-14-30059 Page 24 of 49

e. The Contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The Contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Note: Guidance Conference may be held in conjunction with other meetings or conferences.

2.8.5.2 In-Process Review (IPR) of the TDP

The Contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the Contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The

Contractor shall notify Air Force Life Cycle Management Center Engineering Data Management

Support Section, AFLCMC/EZGEM, a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the Contractor's progress in the preparation of the

TDP. The Contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The Contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility.

(A006, DI-ADMN-81249A) (A007, DI-ADMN-81250A)

2.8.5.3 Relationship of Contractor with Subcontractors/Vendors

The Contractor shall levy on sub-Contractors and sub-vendors the same requirements for

Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-Contractor/vendor levels associated with the program.

File No. FD2060-14-30059 Page 25 of 49

2.8.5.4 Engineering Data Updates and Revisions

The Contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/developed/modified/produced by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a) All engineering changes shall be incorporated into the applicable engineering data within

90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b) All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c) All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all Engineering Orders generated as a result of the preliminary data review.)

2.8.6 Technical Manuals

The scope of this paragraph is changes resulting from Class I Engineering Change Proposals

(ECPs). See also paragraph 2.8.1 for other Class I ECP requirements. The Contractor shall provide Time Compliance Technical Orders and red-line changes to Technical Manuals 12P3-

2ALE47-3 and 12P3-2ALE47-4 as specified by the Technical Manual Contract Requirements

CDRL. The Contractor shall provide support consisting of at least engineering and technical publications personnel available to resolve questions resulting from Technical Manual verification activities.

(D001, TM-86-01N).

File No. FD2060-14-30059 Page 26 of 49

2.9 Safety

The Contractor shall conduct a system safety program in accordance with MIL-STD-882E, with the Government technical point of contact as the risk acceptance authority. The Contractor's system safety approach shall meet the requirements listed in Attachment 3. In the context of system safety, fire control, Jettison, and Weight–On–Wheels (WOW) are safety critical control functions. The Contractor shall assess Prime Mission Equipment hardware and identify hazards.

For each hazard, the Contractor shall assess hazard severity, probability, and mishap risk. The

Contractor shall resolve or control mishap risk to acceptable levels. With reference to Table A–

III in Attachment 3, the Government's mishap risk acceptance levels are:

• 1–5 Unacceptable

• 6–9 Undesirable (Government decision required)

• 10–17 – Acceptable, but document the risk

• 18–20 – Acceptable, but do not document the risk

The Contractor shall document the Government's risk acceptance levels and the accepted risk in a Safety Assessment Report. This report shall provide a detailed discussion of risks that require

Government review/decision and if no reportable risks are identified, the report shall so state.

(A00E, DI-SAFT-80102B)

2.10 Green Procurement Program

This Statement Of Work has no steps or processes that require the use of Green Procurement

Program items.

2.11 Security Requirements

Knowledge and/or generation of classified information and/or Controlled Unclassified

Information (CUI) are required for performance of the contract/order. The Contractor shall ensure applicable Contractor personnel have security clearances at the Secret Level.

File No. FD2060-14-30059 Page 27 of 49 https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/Production-4/PR%20FD2060-10-21226/Atch%2002%20SOW/Referenced%20Documents/MIL-STD-882D.pdf https://org.eis.afmc.af.mil/UHD04/Jennifer.Smith.2/My%20Documents/Production%203.1/Atch%2003%20CDRLs/Exhibit%20A.doc%23A00E

2.11.1 Government Security Regulations

The Contractor shall ensure personnel, information, system, property, facility, and international security requirements are met. The Contractor shall comply with Government Security regulations including, DoD 5200.2-R, Personnel Security Program; DoD 5220.22-M, National

Industrial Security Program Operating Manual (NISPOM); DoDD 5205.02E, DoD Operations

Security (OPSEC) Program; DoD Manual 5205.02-M, DoD Operations Security (OPSEC)

Program Manual; and Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31-101.

2.11.2 Security Regulations

The Contractor shall ensure personnel, information, system, property and facility security requirements are met. The Contractor shall comply with Government security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security

Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM);

DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual

5205.02-M, DoD Operations Security (OPSEC) Program Manual; and Robins Air Force Base

Integrated Defense Plan (RAFB IDP) 31-101.

2.11.3 Operations Security (OPSEC)

The purpose of OPSEC is to reduce the vulnerability of United States Air Force (USAF) missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-M to protect U.S.

Government interests. The Contractor shall ensure Contractor personnel who perform work at a

Government facility comply with the OPSEC…