Attachment_1_PWS.pdf

PR: FD2060-19-31779 PWS REVISION: 0 1

Distribution Statement: C

Performance Work Statement

For

Redesign of the AN/ALM-99B Test Set Programmer

Purchase Request: FD2060-19-31779

Date QAPC signs QASP.

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government Agencies and their Contractors (Critical Technical) (01 MAY 97). Other requests for this document shall be referred to AFSC/PZABB-R, Robins AFB, GA 31098-5365. Questions concerning technical content should be directed to 408 SCMS/GULB.

WARNING - This document contains technical data whose export is restricted by the Arms

Export Control Act (Title 22, U.S.C., Sec. 2751 et seq.) or the Export Administration Act 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violators of these export laws are subject to severe criminal penalties.

HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

PR: FD2060-19-31779 PWS REVISION: 0 2

1.0 Description of Services. This Performance Based Work Statement (PWS) describes the engineering services required to design a replacement for the AN/ALM-99B Programmer Test

Set. Per the revised Configuration Item Development Specification (CIDS, 094-008327) for Test

Set, Programmer AN/ALM-99B, the hardware design will utilize COTS that meets or exceeds the requirements of MIL-PRF-28800F for Class 3 equipment. Per MIL-PRF-28800F, Paragraph

1.2.1 C, “Class 3 equipment is designed for operational environments where conditions are routinely encountered in a diverse, controlled climate. Examples include test equipment for bench-top, rack mount and occasional portable use in diverse, environmentally controlled locations.” Class 3 equipment is the designation for intermediate-level support equipment typically used in a back shop environment. The goal is an item with a high level of Reliability and Maintainability (R&M), is producible, supportable, and achieves a high level of operational availability.

1.1 Objectives: The objective of this effort is to award a contract which results in the timely delivery of one engineering prototype and two prototype AN/ALM-99C replacements. The

Contractor shall provide Test Requirement Documents (TRDs). Accurate technical monthly status reports addressing schedule and cost status shall be provided. The Contractor shall provide accurate Technical Order (T.O.) changes. The AN/ALM-99C shall pass prototype testing requirements. In addition, a technical data package will be acquired as part of this redesign effort, which will allow for competition on future acquisitions.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by increasing the reliability and maintainability of the AN/ALM-99B, as well as, sustaining the electronic warfare suite for the B-52H strategic bombers until retirement currently planned for

2050.

1.3 Background: The AN/ALM-99B Programmer Test Set (001-006682-001) is currently used to test the AN/ALM-155, Control-Indicator-Programmers (CIPs). It is primarily used to perform tests on the C-10130/ALQ-155 (V) CIP. The AN/ALM-99B provides test, alignment and troubleshooting for the C-10130 CIP. The original test set design dates back to the 1970’s has numerous obsolescence issues, utilizes extremely dated technology which adds complexity, requires extensive support, and makes the tester more challenging to maintain and troubleshoot.

The test set includes numerous obsolete circuit card assemblies (CCAs), located in both the test set and the associated Adapter, Test Set, Programmer, and A8 (hereafter referred to as the adapter).

2.0 Services Summary.

Performance Objective PWS

Reference Performance Threshold

Deliver a Technical Data

Package (TDP) that accurately depicts the final product

4.12.2 Final versions shall be free of technical errors

and require no major re-work, as determined by the Government.

PR: FD2060-19-31779 PWS REVISION: 0 3

Provide Test Requirement

Documents (TRDs)

4.10.1, 4.10.2

TRDs shall contain no more than one technical error and no more than five typographical errors per submittal and comply with submission dates as prescribed in the Government approved

Integrated Master Schedule.

Provide accurate technical monthly status addressing schedule and cost status

4.14.4 Monthly status reports that shall be technically

accurate and complete with no more than one technical error and no more than five typographical errors. Errors shall be corrected and the report shall be resubmitted to the COR and engineer NLT 15 working days after receipt of Government comments.

Provide accurate

Operator Instructions

(T.O.) changes

4.5 Final versions shall be free of technical errors

and require no major re-work, as determined by

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be Provided: Government property to be provided are referenced in the attached Scheduled Government Furnished Property (SGFP)

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government-Furnished Property (GFP) in the Item Unique Identification (IUID)

Registry.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of

Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of

Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property: The Contractor shall report loss of

Government property using Defense Contract Management Agency (DCMA) / Access To eTools.

PR: FD2060-19-31779 PWS REVISION: 0 4

3.5 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All

Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order is 18 months after receipt of order (ARO).

4.1.2 Place of Performance: These services will be performed at the Contractor’s facility, 293

Highway 247, Warner Robins, GA and at the WNY Engineering Lab at RAFB.

4.2 Contract Data Requirements List(s) (CDRL)

Document

Identifier

DID Title PWS Reference(s)

A001 DI-MGMT-81650 Integrated Master Schedule 4.3, 4.6, 4.14.2

A002 DI-ADMN-81249B Conference Agenda 4.4.1, 4.6.1, 4.7.1, 4.9, 4.11, 4.12.2.1, 4.12.3

A003 DI-ADMN-81250B Conference Minutes 4.4.1, 4.6.1, 4.7.1, 4.9, 4.11, 4.12.2.1, 4.12.3

A004 DI-ADMN-81373 Presentation Material 4.4.1, 4.6.1, 4.7.1, 4.9

A005 DI-SAFT-80102B Safety Assessment Report (SAR) ?

A006 DI-MGMT-

81453A81453B

Data Accession List (DAL) 4.12.9

A007 DI-MGMT-80368A Status Report 4.14.4

A008 DI-NDTI-80603A Acceptance Test Procedure 4.10.1

A009 DI-MISC-80711A Acceptance Test Report 4.10.1

A010 DI-NDTI-80603A Qualification Test Procedure 4.10.2

A011 DI-MISC-80711A Qualification Test Report 4.10.2

A012 DI-IPSC-81431A System/Subsystem Specification 4.4

A013 DI-MGMT-80004A Management Plan 4.14.1

A014 DI-CMAN-

81022DC

Configuration Audit Summary Report 4.11

A015 DI-MISC-81832 Counterfeit Prevention Plan 4.15

A016 DI-MISC-80711A Final Report 4.13

A018 DI-SESS-81000E/T Product Drawings/Models and Associated

Lists

4.12.2

A019 DI-DRPR-81961 Engineering Drawing Tree 4.12.2

A020 TM-86-01 N Technical Manual Contract Requirements 4.5

PR: FD2060-19-31779 PWS REVISION: 0 5

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than 1 total rejection(s) of deliverables per quarter. The

Government will reject a deliverable if 1 or more technical errors or 5 or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Wide Area

WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) or be submitted directly to the MFT member identified on the CDRL. There shall be no more than

1late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to

4.3 General Technical Requirements. The Contractor shall provide engineering services to design a replacement for the AN/ALM-99B. These services include a test set redesign, prototype fabrication, and test and delivery effort by redesigning the AN/ALM-99B Test Programmer Set to meet legacy specification performance requirements. The prototypes shall exhibit improved system availability and system performance at least equivalent to the existing AN/ALM-99B.

The Contractor shall consider and include current state-of-the-art technology wherever possible.

The Contractor shall ensure there is an acceptable industry base for the components being recommended in the redesign. The Contractor shall identify and document any required modifications to Test Program Sets (TPSs), with respect to both hardware and software. All PWS activity shall be planned and scheduled using a detailed integrated master schedule (IMS).

(CDRL A001, IMS, DI-MGMT-81650)

4.4 Requirements Definition. The Contractor shall accomplish system analyses to define and develop system technical requirements that address all identified requirements. Exit criteria for this phase is a successful Systems Requirements Review (SRR). (CDRL A012, System/Subsystem Specification, DI-IPSC-81431A)

4.4.1 Systems Requirement Review (SRR). The Contractor shall conduct a multi-functional technical SRR to ensure that all subsystem system and performance requirements are defined in sufficient detail to enable system functional definition and functional decomposition; and are consistent with program cost, schedule, risk, and other system constraints. The SRR shall demonstrate consistency between the subsystem requirements, and system/subsystem specification tree. SRR approval is required prior to proceeding to the preliminary design phase. The Contractor shall prepare an SRR agenda and submit final briefing charts three days prior to the review. The Contractor shall develop and deliver SRR minutes IAW the IMS.

(CDRL A002, Conference Agenda, DI-ADMN-81249B) (CDRL A003, Conference Minutes, DI-

ADMN-81250B) (CDRL A004, Presentation Material, DI-ADMN-81373)

PR: FD2060-19-31779 PWS REVISION: 0 6

4.5 Technical Order Updates. The contractor shall provide updates to Air Force technical orders in accordance with attached TM-86-01N, Technical Manual Contract Requirement. (CDRL A020, TM-86-01N, Technical Manual Contract Requirements).

4.6 Preliminary Design. The AN/ALM-99B Programmer Test Set is currently used to test the

AN/ALM-155, Control-Indicator-Programmers (CIPs). It is primarily used to perform tests on the C-10130/ALQ-155 (V) CIP. The AN/ALM-99C replacement will provide test and troubleshooting for the C-10130 CIP. The exit criteria for this phase shall be: trade-off analysis results; program objectives and execution plan (including processes and metrics); program constraints; cost and critical path drivers; program risk assessment; updates to the top-level functional architecture design; system specification updates; subsystem specifications;

requirements allocation to hardware development specifications for all configuration items; test method for verification of requirements; CI configuration management plan; and successful

Preliminary Design Review (PDR) that establishes the allocated baseline. The Contractor shall document all the work effort in a preliminary design engineering report IAW the IMS. (CDRL

A001, IMS, DI-MGMT-81650)

4.6.1 Preliminary Design Review (PDR). The contractor shall conduct a PDR to ensure that the allocated hardware and software requirements are completely captured in performance specifications for each configuration item of the preliminary design. PDR approval is required prior to proceeding to detailed design. The Contractor shall prepare a PDR agenda and submit final briefing charts three days prior to the review. The Contractor shall develop and deliver PDR minutes IAW the IMS. Minutes shall include all briefing materials as an attachment. (CDRL

A002, Conference Agenda, DI-ADMN-81249B) (CDRL A003, Conference Minutes, DI-

ADMN-81250B, CDRL A004, Presentation Material, DI-ADMN-81373)

4.7 Critical Design. The Contractor shall follow a structured engineering process to accomplish

AN/ALM-99C detailed design. The Contractor shall accomplish detailed design of all hardware and any software/firmware components, each with an associated set of performance and design requirements addressing identified requirements. The detailed design shall demonstrate that the allocated baseline is satisfied by the design. The Contractor shall develop drawings and other documentation required. The Contractor shall accomplish testing and validation of the

AN/ALM-99C. The exit criteria for this phase shall be: trade-off analysis results; program objectives and execution plan (including processes and metrics); program constraints; cost and critical path drivers; program risk assessment; updates to the top-level functional architecture design; function and sub-function development specifications update; interface specifications

(physical and functional) update; hardware and any software/firmware development specifications update for all configuration items; critical CI test results; updated test methodology (performance, qualification, environmental, etc.); AN/ALM-99C engineering prototype and successful Critical Design Review (CDR) that establishes the product baseline

(built-to).

4.7.1 Critical Design Review (CDR). The Contractor shall conduct a multi-disciplined technical

CDR to ensure that: the detailed design correctly and completely implements all requirements allocated to the subsystem; each hardware and any software/firmware product in the product baseline has been captured in the detailed design documentation to enable hardware fabrication

PR: FD2060-19-31779 PWS REVISION: 0 7

and software coding of configuration items; upward and downward traceability of final subsystem requirements to final system detailed design; the system under review can proceed into system fabrication and test; and the detailed design is consistent with program cost, schedule, risk, and other system constraints. CDR approval is required prior to proceeding to fabrication and test. The Contractor shall prepare a CDR agenda and submit final briefing charts one week prior to the review. The Contractor shall develop and deliver CDR minutes IAW the

IMS. Minutes shall include all briefing materials as an attachment. . (CDRL A002, Conference

Agenda, DI-ADMN-81249B) (CDRL A003, Conference Minutes, DI-ADMN-81250B) (CDRL

A004, Presentation Material, DI-ADMN-81373)

4.8 Prototype Fabrication. The Contractor shall fabricate, assemble, and deliver two fully functional, operational, compatible AN/ALM-99C prototypes. The Contractor shall maintain configuration control of the product baseline build-to documentation to accurately reflect final prototype configuration. The Contractor shall screen all components selected in the redesign of the AN/ALM-99C to eliminate any premature Diminishing Manufacturing Sources and Material

Shortages (DMSMS).

4.8.1 Prototype Delivery. The Contractor shall deliver one (1) fully functional, operational, and compatible AN/ALM-99C engineering test unit and two (2) prototypes to the Government IAW the IMS. The Contractor shall deliver all units, test fixtures and special test equipment developed, fabricated and tested under this work effort to AFLCMC/WNYEBA.

4.9 Test Readiness Review (TRR). The Contractor shall conduct a multi-disciplined technical

TRR to ensure that: planned tests are traceable to program requirements; all planned preliminary, informal, functional, unit level, and qualification tests have been conducted; the test objectives, test methods and procedures, scope of tests, and safety issues have been properly identified and documented; required test resources have been properly identified and coordinated to support planned tests; the AN/ALM-99C articles are ready to proceed into formal test; and the fabricated prototypes are consistent with program cost, schedule, risk, and other system constraints. TRR approval is required prior to proceeding to formal test. The contractor shall prepare a TRR agenda and submit final briefing charts three days prior to the review. The

Contractor shall develop and deliver TRR minutes IAW the IMS. Minutes shall include all briefing materials as an attachment. The Contractor shall provide TRDs. The AN/ALM-99C shall pass prototype testing requirements. . (CDRL A002, Conference Agenda, DI-ADMN-

81249B) (CDRL A003, Conference Minutes, DI-ADMN-81250B) (CDRL A004, Presentation

Material, DI-ADMN-81373)

4.10 Prototype Test. The Contractor shall utilize existing test equipment to test the AN/ALM-

99C prototypes in accordance with the approved test methodology to verify and validate that operational performance MTBD requirements are met. The prototypes shall successfully pass subsystem testing requirements.

4.10.1 Acceptance Testing. The Contractor shall develop a detailed acceptance test procedure

(ATP) for the AN/ALM-99C and submit the acceptance test procedure for Government approval.

The Contractor shall conduct acceptance test on each prototype AN/ALM-99C in accordance with the approved ATP testing and submit a test report for each prototype AN/ALM-99C for

PR: FD2060-19-31779 PWS REVISION: 0 8

Government approval following testing. The Contractor shall deliver the engineering test unit and prototype AN/ALM-99C test sets, following successful acceptance test, for formal Air Force test IAW the IMS. Prototypes shall successfully pass prototype testing requirements with no more than two retests at the next higher assembly. . (CDRL A008, DI-NDTI-80603A, Acceptance Test Procedure) (CDRL A009, DI-NDTI-80809B Acceptance Test Report)

4.10.2 Qualification Testing. The Contractor shall develop a qualification test procedure (QTP) to qualify the AN/ALM-99C and submit the QTP for Government approval. The Contractor shall conduct qualification tests on the AN/ALM-99C in accordance with the Government approved

QTP and document the results in a qualification test report. Qualification-by-similarity shall be considered where applicable. The Government reserves the right to witness all testing performed by the Contractor. The Contractor shall submit a test report for government approval following testing IAW the IMS. Prototypes shall successfully pass prototype testing requirements with no more than two retests at the next higher assembly. (CDRL A010, DI- NDTI-80603A, Qualification Test Procedure) (CDRL A011, DI-NDTI-80809B Qualification Test Report)

4.10.3 Government Testing. The prototypes of the redesigned AN/ALM-99C configuration will be tested at Robins AFB depot and ground tested on the ALQ-155 CIP at a main operating base to ensure full system level interoperability and operational performance compliance IAW the

IMS. The Contractor shall provide technical support for Government testing efforts. Government testing of the prototypes will be performed using existing and/or new/modified procedures and new technical orders. Prototypes shall successfully pass testing requirements with no more than two retests at the next higher assembly.

4.11 Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA). The

Contractor shall conduct a multi-disciplined FCA/PCA of the final Government tested, redesigned prototype the AN/ALM-99C test sets within two months after delivery of prototypes to ensure that: the actual performance meets the functional specification requirements (derived from the requirements specifications) documented in the Functional, Allocated, and Product

Baselines; the configuration controlled product baseline (build-to) documentation reflects the physical item tested; and the system functional design is consistent with program cost, schedule, risk, and other system constraints. The Contractor shall update, as required, the technical data package to reflect any changes that occur during test. The Contractor shall prepare a FCA/ PCA agenda and submit final presentation material three days prior to the review. The Contractor shall develop and deliver a FCA/PCA report that documents audit findings IAW the IMS. (CDRL

A002, DI-ADMN-81249A, Conference Agenda) (CDRL A003, DI-ADMN- 81250A, Conference Minutes) (CDRL A014, DI-CMAN-81022C, Configuration Audit Summary Report)

4.12 Data.

4.12.1 Users Manuals. The Contractor shall develop all necessary users’ manuals so a competent depot level technician can reasonably use the equipment as needed to test a UUT. All submissions will be IAW the IMS.

4.12.2 Engineering Data: The contractor shall develop/produce/maintain and deliver a

Technical Data Package (TDP) that accurately depicts the final product. TDP data includes, but

PR: FD2060-19-31779 PWS REVISION: 0 9

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. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems and/or components. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created IAW the following American Society of Mechanical Engineers (ASME) standards:

ASME Y14.100-2013, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for this task to create and deliver Product Drawings

Models and Associated Lists (Engineering Data) under this contract.

Data set classification code marking IAW Appendix F of ASME Y14.100-2013 is required.

CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL-STD-130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for

Electrical and Avionics Items shall be IAW document 9579777 Revision B (CAGE 98752) The

TDP shall be delivered in accordance with Air Force Product Data Specification drawing

9579776 Revision N (CAGE 98752), reference attached DD Form 1423 Block 16. (A018, DI-

SESS-81000E/T, Product Drawings/Models and Associated Lists) The contractor shall submit an engineering drawing tree identifying all system, subsystem and equipment drawings as part of the drawing package prior to CDR. (A019, DI-DRPR-81961, Engineering Drawing Tree)

4.12.2.1 Engineering Data Guidance Conference: The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM 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:

(CDRL A002, Conference Agenda, DI-ADMN-81249B) (CDRL A003, Conference

Minutes, DI-ADMN-81250B)

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

PR: FD2060-19-31779 PWS REVISION: 0 10

and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

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

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.

4.12.3 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).

Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), These shall consist of the Native, Neutral, Word Searchable PDF, HPGL, Metadata Spreadsheet, BOM, Gerber Data, and Software/memory Device Data.

The contractor shall notify AFLCMC/LZPEM 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.

PR: FD2060-19-31779 PWS REVISION: 0 11

(CDRL A002, Conference Agenda, DI-ADMN-81249B) (CDRL A003, Conference Minutes, DI-

ADMN-81250B)

4.12.4 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.

4.12.5 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 and funded 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 data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable data prior to delivery of final media.

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

4.12.6 Restrictions on Use of Proprietary or Sole Source. The Contractor shall not recommend proprietary or sole source components unless there is no alternative available. Any proprietary or sole source components recommended shall be explicitly identified at status and design reviews. The Contractor must obtain written permission from the Government contracting officer prior to incorporation of proprietary data/components, etc. and submitted under the proper

DFARS clause (DFARS 252.227-7).

4.12.7 Data Products. The Contractor shall not develop any proprietary data product in the performance of the actions required by the contract. Any data owned by the Government and

PR: FD2060-19-31779 PWS REVISION: 0 12

provided by the Government to the Contractor shall remain the property of the Government after modification by the Contractor.

4.12.8 Government Data Rights. The Contractor shall provide the Government unlimited or unrestricted rights to all technical data, drawings and software developed exclusively with

Government funding for this contract. For items which are outsourced as the result of a

Contractor make/buy decision, the Contractor will identify to the Government program team and contracting officer any subcontractor/supplier claim of proprietary data asserted with other than unlimited rights. The Contractor shall identify any proprietary hardware, drawings or data referring or relating to Government logistics support that has been developed at private expense.

The Contractor shall provide the Government purpose license rights for logistical support if any proprietary hardware or drawings or data developed at private expense is used. Any software licensed or developed internally for this contract shall be delivered to the Government with

Government purpose license rights or unrestricted rights by the completion/termination of the contract. An index of all drawings and data developed under the contract shall be maintained and shall be made available to the procuring agency upon request.

4.12.9 Data Accession List (DAL). All data developed under this task shall become property of the Government. The Contractor shall provide a DAL listing all data, hardware, and software/firmware developed by the Contractor in accomplishment of this task. The contractor shall provide a DAL quarterly and with a final submission at the end of the period of performance. The Contractor shall provide the Government access to any of this data or software/firmware at the request of the Government. The Contractor shall provide the

Government access to the data contained in the DAL and software developed under this task.

(CDRL A006, DI-MGMT-81453A, Data Accession List)

4.13 Final Project Report. The Contractor shall deliver a final report summarizing all technical problems/issues encountered and corrective actions. The Contractor shall report on predicted reliability improvements as related to the predicted reliability of the current unmodified SRU. A preliminary copy of this final report shall be submitted to the Government 30 calendar days after prototype delivery. The Contractor shall submit the final report 30 calendar days prior to the end of the contract. In addition to the final report, the Contractor shall provide a presentation summarizing the results and conclusions of this work effort. The report shall include all briefing materials as an attachment. (CDRL A016, DI-MISC-80711A, Scientific and Technical Reports)

4.14 Program Management.

4.14.1 Program Management Plan (PMP). The Contractor shall develop a PMP that describes how the program shall be accomplished to meet the goals of the program. The plan shall identify as a minimum: all applicable tasks, reviews, status reports, data deliveries and milestones. The purpose of this plan is to provide the management oversight into the program. (CDRL A013, DI-

MGMT-80004A, Management Plan)

4.14.2 Schedule. The Contractor shall develop a detailed integrated master schedule (IMS) that is compliant with the contract line item delivery schedule. This detailed IMS is considered a prime PMP element and shall support all other elements of the PMP to include all milestones

PR: FD2060-19-31779 PWS REVISION: 0 13

and contract deliverables. It requires Government approval for implementation and any proposed changes. (CDRL A001, IMS, DI-MGMT-81650)

4.14.3 Technical Status Reviews. The Contractor shall brief the program’s status, with respect to technical issues, schedules/milestones, etc. on at least a monthly basis. Significant information from the technical status reviews will be included in the MSR as directed by the Government.

4.14.4 Monthly Status Reports (MSR). The Contractor shall report technical, schedule, and cost status on a monthly basis. The report shall identify accomplishments for the month and any difficulties encountered. The Contractor shall present a detailed summary of planned work versus actual work performed, cost variance/schedule variance (CV/SV), technical anomalies encountered, and recommendations. The MSR report will be used by the Government to monitor and evaluate Contractor performance. The MSR are expected to be complete and accurate. Errors shall be corrected and the report shall be resubmitted to the COR and engineer NLT 15 working days after receipt of any Government comments. (CDRL A007, DI-MGMT-80368A, Status

Report)

4.14.5 Technical Interchange Meetings (TIM). The Contractor shall plan, organize, and manage the program efforts to ensure internal control and timely compliance with the program schedule. The Contractor shall support and participate in technical interchange meetings (TIMs) at the Contractor’s facility to present findings of each sub-task. TIMs may be held via telecom at the discretion of the Government. Either the Contractor or the Government can request a special technical interchange meeting if required. Attendees shall consist of, as a minimum, a

Government representative and the Contractor. Significant information from TIM shall be included in the MSR as directed by the Government.

4.14.6 Travel Requirements. The Contractor shall travel in support of the meeting and testing requirements of this PWS as required by AFLCMC/WNYC.

4.15 Counterfeit Prevention Plan (CPP). Contractors that supply electronic parts or systems that contain electronic parts shall establish policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the USAF/DoD supply chain. These policies and procedures shall be documented in a Counterfeit Prevention

Plan (CPP) for submission and approval in accordance with Data Item Description (DID) DI-

MISC-81832 and accomplished for all specified contract items. DI-MISC-81832 is applicable to

Parts, Material and Processes Selection (PMPS) associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies. The requirements of the recently DoD-adopted SAE 5553, Aerospace Standard, Counterfeit

Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply. (CDRL

A015, DI-MISC-81832, Counterfeit Prevention Plan)

4.16 Item Unique Identification (IUID)

4.16.1 Authority. In accordance with DFARS 252-211.7003(a), Item Identification and

Valuation/Definitions, “‘DoD unique item identification’ means a system of marking items

PR: FD2060-19-31779 PWS REVISION: 0 14

delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items.” Unique item identification is required for all items that meet the criteria established by DFARS 211.274-2, Policy for unique item identification.

4.16.2 IUID Marking Plan and Verification Report. The Contractor shall mark items in accordance with DFARS 211.274-2, DFARS 252-211.7003, and Military Standard (MIL-STD)-

130N, Department of Defense Standard Practice/Identification Marking of U.S. Military

Property.

4.16.3 DoD IUID Registry. In accordance with the Department of Defense Guide to Uniquely

Identifying Items Assuring Valuation, Accountability and Control of Government Property, the

Government user will add item(s) to the Department of Defense (DoD) IUID Registry. The

Government user or Contractor representative responsible for causing “life cycle events” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update the item record(s) in the DoD IUID Registry.

4.17 Quality System. As a minimum, the Contractor’s quality system shall be established and maintained in accordance with ISO9001:2000, Quality System Model for Quality Assurance in

Design, Development, Production, Installation, and Servicing (or equivalent). This system shall be developed and available for cognizant Government Quality Assurance Representative (QAR) review prior to beginning production.

4.18 Packaging. The Contractor shall package and mark material in accordance with the contract

Air Force Materiel Command (AFMC) Form 158.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements CONSULT SECURITY OFFICE for your Organization

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: 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.

PR: FD2060-19-31779 PWS REVISION: 0 15

5.2.2 Security Management: The Contractor shall comply with the security requirements specified in the Contractor’s DD Form 254, Contract Security Classification Specification. The

Contractor shall flow down the security requirements to subcontractors as applicable.

5.2.2 3 Operations Security (OPSEC): The contractor shall ensure OPSEC is incorporated into the appropriate area of the contract IAW DoD Directive 5205.02E, DoD Operations Security

(OPSEC) Program and AFI 10-701 Air Force OPSEC Program. The Contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.) Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22-

M. Applicable equipment shall be safeguarded, maintained and operated in accordance with

DoD 5220.22-M.

5.2.4 Security Clearance: The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the SECRET level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the

Department of Defense (DD) Form 254, Department of Defense Contract Security Classification

Specification.

5.2.5 Security Incident or Violation: The Contractor shall notify the Government Contracting

Activity and the Government Security Manager within 48 hours of any incident involving the actual or suspected compromise/loss of classified information to enable the Government to conduct immediate assessments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW DFARS Clause

252.204-7012

The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.6 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The

Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National

Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the

PR: FD2060-19-31779 PWS REVISION: 0 16

contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.7 Access to Government Facility or Military Installation: The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.8 Security Classification Guide (SCG): The contractor shall follow the AN/ALQ-155

Power Management System Including AN/ALT-28 (V) Transmitting Set, AN/ALT 13 (V)

Transmitting Set Security Classification Guide (SCG) dated 2 November 2011 and all security classification guides of systems/information associated with the program for derivative classification, identification of the level and duration of classification for specific information elements, and public release requirements.

5.3 Environmental Management System (EMS): These services shall not be performed at a

Government facility; therefore, the EMS requirement does not apply.

5.4 Agency Affirmative Procurement Programs: This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States

Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements:

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and

Health regulations including, Public Law 91-596 as amended by Public Law 101-552

[Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

5.5.2 Mishap Notification/Investigation: The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations. The Contractor shall provide notification to AFLCMC Safety office telephonically at

(937) 904-3386 during duty hours and (937) 510-1184, the Installation Safety Office telephonically at (478)-926-6271 during duty hours and (478)-327-2612 after hours, as well as notifying the program office at (478) 926-7327 within four business hours after initial notification of all mishaps or incidents for damage to DoD property. The Contractor shall cooperate with Government safety investigations.

5.5.4 Voluntary Protection Program (VPP): Contractor personnel performing work on a

USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

http://www.osha.gov/dcsp/vpp/index.html

PR: FD2060-19-31779 PWS REVISION: 0 17

5.6 Inspection of Services: In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via iRAPT.

5.8 Quality Control Plan/Quality Management System (QMS): The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a

Quality Control Plan (QCP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required. (CDRL XXXX)

A QCP is generally required for the repair and manufacturing of parts; please check with your

QAPC if the MFT has determined a QCP is not required.

Suggested DID Authorities; research based on your individual requirement.

Review DLA’s ASSIST website to research the appropriate DID authority for your requirement (http://quicksearch.dla.mil/qsSearch.aspx). Examples include:

DI-QCIC-81187 Quality Assessment Report

DI-QCIC-81722 Quality Program Plan

DI-QCIC-81794 Quality Assurance Program Plan

5.9 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about

Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and

Combat Trafficking in Persons. http://www.state.gov/j/tip http://quicksearch.dla.mil/qsSearch.aspx http://www.state.gov/j/tip

PR: FD2060-19-31779 PWS REVISION: 0 18

6.0 Appendices

6.1 Appendix A, Reference(s)

Publication Title of Publication Date of

Publication

Sections(s) that Apply

DoD

5220.22-M

National Industrial Security Program Operating

Manual (NISPOM).

February 28, 2006

Change 1 - March

28, 2013

DoDD

4715.1E

Environment, Safety, and Occupational Health

(ESOH)

March 19, 2005

DoDD)

5205.02E

DoD Operations Security (OPSEC) Program June 20, 2012

DoD

Manual

5205.02-M

DoD Operations Security (OPSEC) Program

Manual

November 3, Public

Law 91-

596 as amended by Public

Law 101-

Occupational Safety and Health Act of 1970 December 29, as amended through January

1, 2004