PWS.pdf

Performance Work Statement (PWS)

For

Legacy AN/ALQ-184 System/Software

Sustainment and

AN/ALQ-131 Hardware Sustaining Engineering

Purchase Request: FD2060-21-30025

Prepared By:

External Electronic Attack Pods & Towed Decoy

System Engineering Office

(AFLCMC/WNYEAA)

Date: 27 October 2020

Warner Robins Air Logistics Complex

AFLCMC / WNY

280 Byron St., Bldg. 229

Robins AFB, GA 31098-1607

DISTRIBUTION STATEMENT D: Distribution authorized to U.S. Government Agencies and their contractors (Critical Technical) (4MAY2020). Other requests for this document shall be referred to AFLCMC/WNYEAA, Robins AFB, GA 31098-5365. Questions concerning the technical content should be directed to

AFLCMC/WNYEAA.

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-21-30025 PWS REV0.0

27 Oct 2020 ii

(This page intentionally left blank.)

iii

Table of Contents

Chapter 1: Description of Services

1.1 Objective(s)

1.2 Benefits to United States Air Force (USAF)

1.3 Background

Chapter 2: Services Summary

Chapter 3: Government Property and Services

3.1 Contractor Responsibility

3.2 Government Property to be Provided

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property

3.3.2 Reporting Loss of Government Property

3.4 Return or Retention of Government Property

3.5 Government Systems

Chapter 4: Requirements

4.1 Technical Requirements

4.1.1 AN/ALQ-184 Engineering Services Requirements

4.1.2 AN/ALQ-131 Hardware Sustaining Engineering Requirements

4.2 Period and Place of Performance

4.2.1 Place of Performance

4.2.2 Period of Performance

4.3 General Requirements

4.3.1 Technical & Management Work Plan

4.3.2 Master Schedule

4.3.3 Monthly Status Report

4.3.4 Program Management Reviews & Technical Interchange Meetings (TIMs)

4.3.5 Agenda

4.3.6 Minutes

4.3.7 Kickoff Meeting

4.3.8 Design Reviews

4.3.9 Quality of CDRL Deliverable ....................................... Error! Bookmark not defined.

4.3.10 Receipt of CDRL Deliverable ...................................... Error! Bookmark not defined.

iv

4.3.11 Timely Notification of Problems

4.4 Data Requirements

4.5 Other Requirements

4.5.1 Restrictions on use of Proprietary Material

4.5.2 Supplies

4.5.3 Parts De-rating and Application

4.5.4 System Safety

4.5.5 Configuration Management

4.5.6 Subcontract Management

4.5.7 Holiday and Facility Closings

4.5.8 Travel

Chapter 5: General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Definition of Mission-Essential Services

5.1.2 Designation of Services as Mission-Essential

5.2 Security Requirements

5.2.1 Classified / Controlled Unclassified Information (CUI)

5.2.2 Government Security Regulations

5.2.3 Operation Security (OPSEC)

5.2.4 Communication Security (COMSEC)

5.2.5 Security Clearances

5.2.6 Security of Contractor System(s)

5.2.7 Access to Government System(s)

5.2.8 Access to Government Facility

5.2.9 Access to Robins Air Force Base (AFB)

5.3 Environmental Management System (EMS)

5.3.1 Executive Order Compliance

5.3.2 Secretary of the Air Force Policy Compliance

5.3.3 Training

5.3.4 Subcontract

5.4 Green Procurement Program (GPP) .................................. Error! Bookmark not defined.

5.5 Safety Requirements

5.5.1 Contractor Compliance

v

5.5.2 Voluntary Protection Program (VPP)

5.5.3 Mishap Notification

5.5.4 Safety & Health Plan

5.5.5 Subcontract Management

5.6 Inspection of Services

5.7 Trafficking in Person

5.8 Contract Manpower Reporting

5.8.1 SAF/AQ Directive

5.8.2 OSD Directives

5.8.3 Contractor Manpower Reporting

5.9 Quality Management System

5.10 Invoicing/Payment and Receipt/Acceptance

5.10.1 Submission of Payment Requests and Receiving Reports

5.10.2 Service Acceptance

Appendix A: References........................................................................................................ A-1 vi

(This page intentionally left blank.)

05 May 2020

Chapter 1: Description of Services

The Electronic Warfare and Avionics Division (AFLCMC/WNY), the Product Group Manager (PGM) for the AN/ALQ-184 and AN/ALQ-131 system, requires varying levels of support for sustainment of managed products. The Electronic Attack Pods and Towed Decoy Systems Engineering Section, AFLCMC/WNYEAA, is the overall system technical authority and has Operational Safety, Suitability, and Effectiveness (OSS&E) responsibility. These electronic combat systems are experiencing problems with discontinued Original Equipment Manufacturer (OEM) hardware and software components, incompatibilities with advanced state of the art hardware and software component functionality, and age-related operational performance deficiencies. These systems’ service lives have been extended well beyond their anticipated design life. The scope of this effort includes software sustainment (test) through Independent Verification and Validation (IV&V), of the AN/ALQ-184(V) Electronic Attack (EA) pod Operational Flight Program (OFP) software to include all test tools and documentation.

1.1 Objective(s)

The first objective of this Performance-based Work Statement (PWS) is to acquire Contractor sustaining engineering support for the AN/ALQ-184 Electronic Counter Measure Pod. This effort is intended to provide Independent Verification and Validation (IV&V), of the AN/ALQ-184(V) Electronic Attack (EA) pod Operational Flight Program (OFP) software, updating of existing verification and validation tools, updating of existing verification and validation tool documentation, and reviewing/updating of software documentation. This support applies to all parts of the AN/ALQ-184(V) OFP including the RePLACE® and IO1553 code modules.

The second objective of this PWS is to acquire Contractor sustaining engineering support for the AN/ALQ 131 Electronic Counter Measure Pod. This effort is intended to continue the focus on system-level operational and technology-obsolescence deficiencies. As such, it will generate studies, analysis and model/prototype solution sets at the Line Replaceable Unit (LRU), Shop Replaceable Unit (SRU) or component level. In addition, this effort requires continued support of sustaining engineering and the recurring maintenance of test capability at the Electronic Warfare Avionics Integration Support Facility (EWAISF).

1.2 Benefits to United States Air Force (USAF)

This acquisition will benefit the USAF by ensuring combat capability is maintained and is current with today’s emerging threat environment through critical Sustaining Engineering activities. The AN/ALQ-184 and AN/ALQ-131 protects U.S. and Allied aircraft from terminal threats in a variety of complex and dense environments through threat detection and electronic attack.

1.3 Background

The primary mission of the AN/ALQ-184(V) Electronic Attack (EA) pod is to identify and counter increasingly complex, diverse enemy air defensive systems. The pods consist of a multitude of receiver, transmitter and signal processing sub-systems, data and support equipment. The systems were first designed, developed, assembled and deployed in the mid-1970s with incremental hardware and software upgrades since then. Since the early 1990s, the AN/ALQ- 184 and the ALQ-131, have been the primary defensive system for the F-16 and A-10 combat aircraft. Due to the rapid and continuous evolution of the electronic battlefield arena, the AN/ALQ-184 and ALQ-131 has been outpaced by technological developments in threat systems thus creating an array of serious operational deficiencies which must be resolved. Additionally, documented AN/ALQ-184 OFP software deficiencies require correction in the currently fielded software. These corrections to the OFP require IV&V prior to final release of software.

Chapter 2: Services Summary

Performance Objective PWS Reference Performance Threshold Submit timely notification of problems in program management that impact cost, delivery or schedule

4.3.10 Contractor shall notify the Government

within two (2) business days of problems in program management that impact cost, delivery or schedule by greater than 10% in any one of these areas.

Notification within two (2) business days from the time the contractor is aware of the problem if in relation to a routine or urgent IV&V effort. Notification within four (4) hours from the time the contractor is aware of the problem if in relation to an emergency IV&V effort.

Notification shall be supplied via telecom and via e-mail, to be followed up with a written statement in the Monthly Status Report.

Perform testing 4.1.1 4.1.2

100% of all formal tests conducted IAW the approved test procedures shall be documented in a formal test report submitted per Contract Data Requirements List (CDRL) for Government review and comment. For formal tests, sufficient engineering shall have already been done to ensure less than 10% of the critical test objectives are not met. Contractor shall execute the tasking with no more than 10% deviation in cost or schedule.

Submit a report to document the results of the technical inquiry or deficiency analysis/Investigation and IV&V documentation

4.1.1 4.1.2 4.3.9

Generate technically accurate reports with no more than one (1) technical error per report. 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. Following receipt of all comments, reports shall require no more than one (1) revision per report after the initial submittal.

Performance Objective PWS Reference Performance Threshold Comply with Air Force wide and local security procedures

5.2 Zero (0) reportable security violations per

contract year, as determined by the ALQ- 184 and ALQ-131 Security Classification Guide (SCG) s and organizational procedures.

Conduct acceptable Contractor safety program

5.5 No more than two (2) Class C mishaps per

contract year. Zero (0) Class A or B mishaps per contract year.

Quality of CDRL deliverable

4.3.9 All with required

CDRLs

There shall be no more than one (1) rejection of any single deliverable. There shall be no more than a total of 10 (ten) rejection(s) of deliverables per contract year. The Government will reject a deliverable if two (2) or more technical errors or five (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 defined as a typographical or grammatical error.

Chapter 3: Government Property and Services

3.1 Contractor Responsibility

The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property.

The FAR and applicable supplements can be accessed at https://www.acquisition.gov/content/regulations.

3.2 Government Property to be Provided

The Contractor shall determine any requirements for Government Furnished Property (GFP) that may be necessary for execution of this task. The Contractor shall submit a written request for any such GFP not later than 30 days prior to the Contractor’s expected need date. GFP is provided on an as-available basis. The contractor should inform the government of program risks if GFP is not available.

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property

In accordance with DFARS 252.245-7002, Reporting 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, theft, loss due to lack of security, 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.3.2 Reporting Loss of Government Property

The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools LTDD of Government Property toolset can be accessed from the DCMA home page External Web Access Management application at http://www.dcma.mil/WBT/propertyloss/.

3.4 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 upon completion of the contract/order. All Government property shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), and deliverables become the property of the Government upon receipt. Any GFP that is modified as part of a tasking under this contract shall be returned in the condition/configuration prescribed in the individual tasking.

3.5 Government Systems

The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

Chapter 4: Requirements

4.1 Technical Requirements

4.1.1 AN/ALQ-184 Engineering Services Requirements

The contractor shall perform work efforts and program activities required by this PWS. This effort is required to continue the performance and support of IV&V of the AN/ALQ-184(V) EA pod OFP. The contractor shall provide IV&V of the OFP prior to final release for urgent and emergency reprogramming efforts, as determined by the user, within the agreed-upon schedule. Software updates upon which the contractor shall perform IV&V consist of changes to the OFP due to incorporation of user Operational Change Requests (OCRs) and corrections of deficiencies detected in the field and by previous IV&V efforts. Included in this PWS is the requirement to review open Software Problem Reports (SPRs) and OCRs to determine validity and suitability of software maintenance candidates, review software documentation describing the code changes associated with each OFP update, and update all verification and validation tools to accommodate the OFP update. The work required to support this effort includes reviewing data items, supporting design reviews and technical coordination meetings, testing OFP integrity, verifying supporting documentation, validating verification and validation tool modifications, generating test plans, test procedures, and test reports, and other AN/ALQ-184 related engineering work as defined by the Government.

4.1.1.1 AN/ALQ-184 SPR/OCR/Code and Documentation Reviews

The contractor shall review the Government’s analysis of open SPRs for validity and suitability as version release candidates. The contractor shall make these determinations based on a comparison of the open SPRs and OCRs against the latest OFP version release. For software changes, this review shall be conducted in less than sixty (60) days, and for emergency reprogramming candidates, the review shall be conducted within eight (8) hours. The contractor shall document the results of the review by entering revisions to the SPRs into the System Problem and Metrics Manager (SPAMM). [DI-MGMT-81232T System Problem Report].

Upon receipt of a version release from the Government, the contractor shall perform a code walkthrough. As part of the code walkthrough, the contractor shall, as a minimum, verify that:

a) All OFP changes can be attributed to corrections for only the SPRs or OCRs accepted as version release candidates

b) “in line” software comments are adequate to allow an independent programmer to understand and modify existing software

c) Code logic and implementation is valid and complies with MIL-STD-1679A, DoD-STD- 2167A, or IEEE/EIA 12207.0, IEEE/EIA 12207.1 and IEEE/EIA 12207.2 requirements

The contractor, when tasked by WNYEAA, shall review documentation changes and updates which relate to the AN/ALQ-184(V) OFP. Documents shall be reviewed for completeness and accuracy, and to verify that the version release requirements are accurately documented and match the code implementation. Findings shall be documented in a technical report.

[DI-MISC-80508B, Analysis and Study Report].

4.1.1.2 AN/ALQ-184 IV&V Testing

The contractor shall utilize the Government furnished verification (Zilog Z8 and Z8002 diagnostic emulators and TMS320C3x In-Circuit Emulator (TICE), etc.) and validation (IECS3 real time processor activity and data recording, replay, analysis system, etc.) tools to the maximum extent feasible for this portion of the effort. The software testing specified in this PWS shall meet or exceed the requirements for the software quality tests as specified in MIL- STD-1679A, DoD-STD-2167A, or IEEE/EIA 12207.0, IEEE/EIA 12207.1 and IEEE/EIA 12207.2, as applicable to each software product. The testing shall demonstrate that the software is, or is not, reasonably free of serious errors and meets the requirements of the version release candidate SPRs and OCRs. The software is to be stressed to, and beyond, the limits of its design capabilities in order to ensure that degradation at the point of saturation is not catastrophic. Testing requirements shall be documented in Software Test Description and as a minimum shall provide for module, subprogram, program performance, and full system integration testing. The Software Test Description shall also define the schedule and necessary inputs from the development contractor or the Government to perform the required testing. The contractor shall examine test results and identify deficiencies in the system. In the event that a deficiency is discovered, the contractor shall document the conditions under which the deficiency was discovered. The contractor shall report all deficiencies discovered in the system to AFLCMC/WNYEAA by entering problem reports into SPAMM. The SPRs shall be submitted within two (2) weeks from when the software deficiency is first verified. If the deficiency is sufficient to preclude further routine testing or is found during an urgent or emergency reprogramming effort, the contractor shall immediately report the deficiency to AFLCMC/WNYEAA. The contractor shall diagnose errors and recommend changes in the system where the source of the problem is evident from the test results. The contractor shall prepare a test report summarizing testing accomplished on each IV&V effort at the conclusion of the IV&V testing period. The contractor shall annotate in the report all deficiencies and recommended mission data programming restrictions that are associated with the OFP version release tested. The contractor shall deliver to the Government, as part of the software project Test Report, a statement certifying their recommendation to the Government to accept or reject the software product. [DI-IPSC- 81439A/T Software Test Description, DI-MGMT-81232T System Problem Report, DI-IPSC- 81440A/T Software Test Report]

4.1.1.3 AN/ALQ-184 Test Tool Update

The contractor shall modify the verification and validation tools, which are written in FORTRAN, C/C++, TCL, and Visual Basic to ensure compatibility and interface-ability with the OFP version to be tested. This includes tools needed for: verifying and validating the RePLACE® and IO1553 modules, testing the 1553 bus, or loading the updated software into the AN/ALQ-184(V) EA pod. The contractor shall present details of the required modifications to the present verification and validation tools to accommodate the OFP software updates at project team meetings. The contractor shall present at a Project Team meeting details and associated cost and schedule of the required modifications to the present verification and validation tools.

The contractor shall ensure all efforts on this task are managed as one integrated systems engineering effort. The contractor shall update the following software documents for tools modified under this effort: Software Design Description, Software User’s Manual, Interface

Design Description, and developmental design drawings. [DI-IPSC-81435A/T Software Design Description, DI-IPSC-81436A/T Interface Design Description, DI-IPSC-81443A/T Software User Manual, and DI-SESS-81002E/T Developmental Design Drawings]

4.1.1.4 Skill Level of AN/ALQ-184 IV&V Personnel

The Contract team performing IV&V work under the terms of this effort shall have the following skills or shall be approved by the Government to work on this program:

a) BS/MS in computer science/engineering, electrical/electronic engineering, or equivalent degree per DoD hiring practices, and/or 15 plus years on the job experience, with two

(2) years’ experience to include: software, documentation, and IV&V experience. Years of experience, as determined by the Government, may be substituted for the required degree.

b) Programming experience with any of these computer languages: FORTRAN, Ada, PASCAL, Visual Basic, Java, TCL, PERL, C, C++, Zilog Z8 and Z8002 assembly or other assembly languages.

c) Experience necessary to perform the following tasks:

1. Perform verification and validation in all phases of software implementation, integration, and review

2. Perform verification and validation of documentation for completeness and accuracy

3. Verify that “in-line” software comments are adequate to allow an independent programmer to understand and modify existing software

4. Participate in software reviews

5. Generate standards and guidelines for tests being performed

d) Two years of AN/ALQ-184(V) OFP software experience in the following areas:

1. Pod System Processor Program (PSPP)

2. Technique Generator Program (TGP)

3. Radar Warning Receiver Interface Processor Program (RWRIPP)

4. Low Band Processor Program (LBPP)

5. OFP Computer Software Component (CSC) to CSC and OFP to Computer Software

Configuration Item (CSCI) to peripheral CSCI interfacing

6. OFP, built-in-test, and mission data memory utilization

7. RePLACE® software and tools

e) Two years of AN/ALQ-184(V) system knowledge in the following areas:

1. Digital architecture which includes, as a minimum, Central Processing Units

(CPU’s) operation, bus interfaces between CPUs, and component control interfaces

2. RF architecture which includes, as a minimum, component utilization for performance of automatic gain optimization, voltage controlled oscillator tuning, propeller beam, and modulation

3. Creation of mission data matrices using the Mission Data Generator Program.

4. Performance of AN/ALQ-184 HATCHECK using the support equipment computer program

5. RePLACE® system

6. VxWorks RTOS

The contractor shall provide, as part of the Technical & Management Work Plan, a resume for each technical employee assigned to accomplish the efforts defined by this PWS. As part of the Technical & Management Work Plan and within 30 days after assignment of any new personnel to this effort, the contractor shall also provide certification that not less than 70% of the personnel assigned to this effort meet the experience requirements stipulated in the paragraph above.

4.1.2 AN/ALQ-131 Hardware Sustaining Engineering Requirements

4.1.2.1 General Engineering Support/Technical Inquiries

The Contractor shall provide technical expertise to respond to day-to-day tasks and minor engineering inquiries related to the AN/ALQ-131 system, sub-system and support equipment operational deficiencies, field inquiries or general hardware supportability issues. Activities include but are not limited to: design verification testing, support equipment deficiency solution, Obsolescence & DMS deficiency identification/analysis/resolution, integration of solutions into the overall system, drawing reconciliation, First Article & Qualification Testing, environmental testing and response to field supportability inquiries. (DI-MISC-80508B, Analysis and Study Report; DI-NDTI-80603A, Test Procedure; DI-NDTI-80809B, Test/Inspection Report; DI-ADMN-80925, Revision to Existing Govt Documents)

4.1.2.2 Deficiency Analysis/Investigations

The Contractor shall identify and evaluate system-level deficiencies revealed from operational use, DMS, and obsolete technology as defined by AFLCMC/WNY task request. Activities include but are not limited to: document, design, prototype, and test changes in an effort to characterize the critical paths of an identified problem; develop prototype solution sets, demonstrate and perform testing to evaluate the prototype for operational performance;

conduct in depth system analysis resulting in formal report of results.

Testing shall be done both on an individual solution and on integrated combinations of solution sets as required by the task description. Formal tests shall be conducted in accordance with the approved test procedures. For formal tests, sufficient engineering shall have already been done to ensure more than 90% of the critical test objectives are met. The Contractor shall ensure that the system baseline performance is retained, that design improvements satisfy the minimum performance requirements and that risk is sufficiently reduced to warrant fielding of the solution. The Contractor shall work with the assigned Government engineering staff throughout the execution of each task, and deliver a final report at the conclusion of the effort which details the entire effort including the test results and recommended implementation approaches. (DI-ADMN-80925, Revision to Existing Govt Documents; DI-MISC-80508B, Analysis and Study Report; DI-NDTI-80603A, Test Procedure, DI-NDTI-80809B, Test/Inspection Report)

On tasks requiring new design, the contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. 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.

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 delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision L (CAGE 98752), reference attached DD Form 1423 Block 16. (DI-SESS-81000E/T, Product Drawings and Associated Lists)

The Contractor shall update (and where necessary create) component, assembly, and next-higher-assembly specifications to account for any changes/impacts due to this effort. (DI- ADMN-80925, Revision to Existing Govt Documents)

4.2 Period and Place of Performance

4.2.1 Place of Performance

The place of performance for this contract will be a combination of U.S. Government and non U.S. Government installations. Specifically, Robins AFB, GA, the Contractor’s facility, off-site temporary duty (TDY) to other USAF Command facilities, other DoD facilities, and private industry facilities.

4.2.2 Period of Performance

The period of performance for the contract/order is 10 years. This includes one (12) twelve month basic and nine (9) 12 month option periods.

4.3 General Requirements

4.3.1 Technical & Management Work Plan

The contractor shall develop a Technical & Management Work Plan (Project Plan). The Plan developed by the contractor program manager for ALQ-184 and ALQ-131 activities, shall contain, as a minimum, the Contractor’s approach to implementing the provisions of this PWS.

The plan shall reflect the requirements as delineated throughout this document. [DI-MGMT- 81117, Technical & Mgmt Work Plan]

4.3.2 Master Schedule

The Contractor shall define and maintain a Master Schedule throughout the entire effort. The schedule shall depict the program milestones and activities utilizing Microsoft Project and shall contain event-driven program elements that are of sufficient detail as to be commensurate with and facilitate the reporting of, work versus cost. The schedule shall be coordinated with the Government for any changes. The schedule shall be included as part of the Monthly Status Report.

4.3.3 Monthly Status Report

The Contractor shall report technical, schedule, and cost status on a monthly basis. A Final Report shall be delivered that contains a summary of all previously submitted Status Report data. As a minimum, the Contractor report shall include: [DI-MGMT-80368A, Status Report] Summary of work performed and findings during the month Proposed changes to the Schedule If official travel was performed during the reporting period, a trip report shall be included as part of the status report Identification of technical problems / anomalies encountered Notification of problems in program management Identification of areas where the contractor’s performance or deliverables are not projected to meet the requirements of the contract, i.e., problems encountered and potential solutions

Recommendations for improvements in the test activities or other integrated team activities in addition to those documented in the Engineering Report

Summary of planned work during the next month CDRL status Status of Action Items from reviews and meetings

4.3.4 Program Management Reviews & Technical Interchange Meetings (TIMs)

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 program review and technical interchange meetings (TIMs). TIMs may be held via telecon at the discretion of the Government. The program review and technical interchange meetings shall be held monthly. Either the contractor or the Government can request a special program review and technical interchange meeting if required. Attendees shall consist of, as a minimum, a Government representative and the contractor. Only special review/conference meetings as identified by the Government will require deliverable special presentation materials. [DI- ADMN-81373, Presentation Material]

4.3.5 Agenda

The Contractor shall prepare and submit an agenda for each review and TIM. Only special review/conference meetings as identified by the Government will require a deliverable agenda.

The agenda will be submitted for Government approval not later than fifteen (15) working days prior to the review. [DI-ADMN-81249A, Conference Agenda]

4.3.6 Minutes

The Contractor shall produce minutes for any meetings or reviews applicable to this task. Only special review/conference meetings as identified by the Government will require deliverable minutes. The minutes will be submitted for Government approval fifteen (15) workdays after the end of the meeting in which they are produced. [DI-ADMN-81250A, Conference Minutes]

4.3.7 Kickoff Meeting

The Contractor’s program manager shall host a Kickoff meeting to be held not later than 60 days after award of the contract. The Contractor shall brief his/her understanding of the requirements, and shall submit a draft Technical & Management Work Plan and Master Schedule for review at this meeting. The Contractor shall present/discuss his/her approach to the entire effort within the known resource constraints. The Contractor shall brief any known impediments or issues that may already be known as well as brief risk mitigation plans for anticipating and responding to technical, logistic and other delays. The Kickoff meeting shall take place in building 229S at Robins AFB or at the Contractor’s Warner Robins facility.

4.3.8 Design Reviews

The Contractor shall conduct system design reviews (PDRs and CDRs) for the purpose of reviewing electrical design, mechanical design, and test requirements for solutions pursuant to PWS section 4.12. Multiple solution designs may be covered at each review. The Contractor shall prepare an agenda for each scheduled review and submit briefing charts and appropriate data prior to each review as required by the Government. Meeting minutes shall be prepared by the contractor and submitted to the Government for review & comment or approval. (DI- ADMN-81249A, Conference Agenda, DI-ADMN-81250A, Conference Minutes, DI-ADMN- 81373, Presentation Material)

4.3.9

4.3.9 Contract Data Requirement List (CDRL)

4.3.9.1 Quality of CDRL Deliverable

There shall be no more than one (1) rejection of any single deliverable. There shall be no more than a total of 10 (ten) rejection(s) of deliverables per contract year.

The Government will reject a deliverable if two (2) or more technical errors or five (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.

A rejected deliverable shall require no more than one (1) revision. The rejected deliverable shall be corrected and resubmitted within 15 calendar days of notification of Government rejection.

4.3.9.2 Submission of CDRL Deliverable

CDRL deliverables may be submitted via Wide Area Workflow (WAWF) and/or be submitted directly to the MFT member identified on the CDRL. The CDRL will determine submittal requirements.

4.3.9.3 Receipt of CDRL Deliverable

There shall be no more than two (2) late receipt(s) of deliverables per contract year. 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 the Government.

4.3.10 Timely Notification of Problems

The Contractor shall notify the Government PCO or Contracting Officer Representative (COR) of problems in program management that impact cost, delivery or schedule within two (2) business days from the time the contractor is aware of the problem.

4.4 Data Requirements

The Contractor shall deliver the data items listed throughout this document as part of this tasking. Documents shall be prepared and delivered in accordance with the corresponding DD Forms 1423 in the contract.

Document Identifier

DID Title PWS Reference(s)

A001 DI-MGMT-81232T System Problem Reports 4.1.1 A002 DI-MISC-80508B Technical Report-Study Services 4.1.1, 4.1.2 A003 DI-IPSC-81439A/T Software Test Description 4.1.1 A004 DI-IPSC-81440A/T Software Test Report 4.1.1 A005 DI-IPSC-81435A/T Software Design Description 4.1.1 A006 DI-IPSC-81436A/T Interface Design Description 4.1.1

A007 DI-IPSC-81443A/T Software Users Manual 4.1.1 A008 DI-SESS-81002E/T Developmental Design Drawings 4.1.1 A009 DI-NDTI-80603A Test Procedures 4.1.2 A00A DI-NDTI-80809B Test Inspection Report 4.1.2 A00B DI-ADMN-80925 Revision to Existing Government Documents 4.1.2 A00C DI-MGMT-81117 Technical Management Work Plan 4.3.1 A00D DI-MGMT-80368A Status Report 4.3.3 A00E DI-ADMN-81373 Presentation Materials 4.3.4, 4.3.8 A00F DI-ADMN-81249A Conference Agenda 4.3.5, 4.3.8 A00G DI-ADMN-81250A Conference Minutes 4.3.6, 4.3.8 A00H DI-SESS-81000E/T Product Drawings and Associated Lists 4.1.2 A00I DI-SAFT-80102C System Safety Report (SAR) 4.5.4 A00J DI-ENVR-81375 Environmental and Heath Safety Plan (HSP) 5.5.4

4.5 Other Requirements

4.5.1 Restrictions on use of Proprietary Material

Rights in software and data developed and delivered under the contract shall be governed by Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013, 7014, etc. In the event that it is necessary for the contractor to use contractor-developed and/or proprietary hardware and/or software to fulfill its obligations under the contract, the Government shall be notified, and any requirement for delivery of such proprietary material shall be with Limited or Restricted Rights, as the case may be. In the event it is necessary for the contractor to purchase licenses to third party software using contract funds in order to fulfill its obligations under the contract, those licenses shall be delivered to the Government; and the Government's rights in such software will be determined by the provisions of those license agreements.

4.5.2 Supplies

The Contractor shall be able to purchase "Other Direct Cost" (ODC) items such as: consumables, supplies, equipment, and specialized engineering services, as required to meet contractual requirements. The Contractor shall provide a written request for ODC approval to the Government PCO and obtain written approval from the Government PCO in advance, for any ODC purchase with a unit price of $5,000 or more.

4.5.3 Parts De-rating and Application

The Contractor shall establish a uniform policy regarding the de-rating of parts/components used on custom designed hardware assemblies developed as a part of this effort. Commercial-off-the-Shelf (COTS) items are excluded from this requirement but shall be subject to the requirement that they meet MIL-STD or prescribed environmental/functional test and operational criteria of the ALQ-131 system.

4.5.4 System Safety

The Contractor shall conduct a system safety program in accordance with MIL-STD-882E (when appropriate based on assigned sustaining engineering tasks), with the Government technical point of contact as the risk acceptance authority. The Contractor shall assess Prime Mission Equipment hardware as well as software contributions to system risk 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. The Contractor shall document the Government's risk acceptance levels and the accepted risk in a Safety Assessment Report (MIL- STD-882E Task 301). 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. [DI-SAFT-80102C, Safety Assessment Report]

4.5.5 Configuration Management

The Contractor is required to implement a configuration management program for all engineering products generated or processed as a result of this program. References to appropriate Configuration Management procedures shall be based on the contractor’s configuration management policies and procedures.

4.5.6 Subcontract Management

The Contractor shall ensure sub-contractor compliance with all applicable requirements of this contract.

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 with the exception of commercial off-the-shelf (COTS) items. The Contractor shall develop associate contractor agreements with appropriate vendors to ensure a smooth flow of information in a secure business environment.

4.5.7 Holiday and Facility Closings

Contractor personnel shall observe the ten federal holidays and facility closings, e.g., energy down days, authorized by the Government in accordance with AFMC MP5337.1, Service Contracts - General. Contractor personnel will only be permitted access to Government facilities when Government personnel are present.

4.5.8 Travel

Travel requests for Contractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of five (5) business days in advance of departure. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs.

Chapter 5: General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Definition of Mission-Essential Services

In accordance with DFARS 252.237-7023(a)(1), Continuation of Essential Contractor Services, “ ‘Essential contractor service’ means a service provided by a firm or individual under contract to DoD to support mission-essential functions, such as support of vital systems, … associated support activities, … and similar services provided to foreign military sales customers under the Security Assistance Program. Services are essential if the effectiveness of defense systems or operations has the potential to be seriously impaired by the interruption of these services, as determined by the appropriate functional commander or civilian equivalent.”

5.1.2 Designation of Services as Mission-Essential

In accordance with DFARS 237.7602(a), The Continuation of Essential Contractor Services / Policy, DFARS 252.237-7023(a)(2), and Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2, the Functional Commander (FC) 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

5.2.1 Classified / Controlled Unclassified Information (CUI)

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

5.2.2 Government Security Regulations

The Contractor shall ensure personnel, information, system, property, 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.

5.2.3 Operation Security (OPSEC)

The purpose of OPSEC is to reduce the vulnerability of 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 on a Government facility comply with the OPSEC procedures of the facility.

5.2.4 Communication Security (COMSEC)

The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or 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.5 Security Clearances

The Contractor shall ensure applicable Contractor personnel have security clearances at the Secret level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified information and/or CUI.

5.2.6 Security of Contractor System(s)

The Contractor shall ensure the security of Automated Information System(s) (AIS) at the Contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified information and/or CUI.

5.2.7 Access to Government System(s)

The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure Contractor personnel who require access to an unclassified or classified Government AIS have the appropriate background check or security investigation conducted. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

5.2.8 Access to Government Facility

The Contractor shall ensure Contractor personnel who require access to a Government facility comply with the security requirements of the facility.

5.2.9 Access to Robins Air Force Base (AFB)

5.2.9.1 Background Check

In accordance with AFI 31-113, Installation Perimeter Access Control, all non-DoD personnel requiring frequent or recurring access to Robins AFB must have a background check completed by the 78th Security Forces Squadron (78 SFS)/S5P Visitor Control Center (VCC) or Base Defense Operations Center (BDOC) before they will be granted qualified base access.

5.2.9.2 Entry to Robins AFB

In accordance with RAFB IDP 31-101, Contractor personnel granted qualified base access may receive installation entry and circulation privileges under limited circumstances or conditions.

They do not have the authority to sponsor anyone for access to Robins AFB or vouch for anyone to enter Robins AFB.

5.2.9.3 Identification of Contractor Personnel Requiring Access In accordance with RAFB IDP 31-101, a Contractor awarded a contract/order that requires services to be performed on Robins AFB shall provide the badging agent and PCO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.

5.2.9.4 Defense Biometric Identification System (DBIDS) Identification (ID) Card In accordance with RAFB IDP 31-101, Contractor personnel requiring access to Robins AFB, but not LAN (Local Area Network) access, shall complete the Robins AFB Access Affidavit to obtain a DBIDS ID card and return it to the badging agent. After verification by the badging agent, Contractor personnel shall come to the VCC to claim their DBIDS ID card.

5.2.9.5 Common Access Card (CAC)

In accordance with RAFB IDP 31-101, Contractor personnel requiring access to Robins AFB and LAN access will be entered in the Contractor Verification System (CVS) by the Trusted Agent (TA). The TA will email their user ID/password and instructions on accessing the Robins AFB public website to the Contractor personnel. Contractor personnel shall access the website and complete all applicable forms as directed. After this process is completed, Contractor personnel shall make an appointment with the 78th Mission Support Group (MSG) via the CAC Web Scheduler to claim their CAC.

5.2.9.6 Loss of Card

In accordance with RAFB IDP 31-101, if Contractor personnel lose their DBIDS ID card or CAC, they shall notify the badging agent immediately.

5.2.9.7 Retrieval of Card(s)

In accordance with RAFB IDP 31-101, the Contractor shall notify the badging agent immediately upon Contractor personnel being transferred/terminated. The Contractor is responsible for retrieving contractor/subcontractor CAC(s) and/or DBIDS ID card(s) (including restricted/controlled area badges) upon transfer/termination of Contractor personnel or completion/termination of the contract/order. The Contractor shall return all retrieved CAC(s) and/or DBIDS ID card(s) to 78 SFS/S5P.

5.3 Environmental Management System (EMS)

Contractor/subcontractor personnel who perform work on any Government facility shall comply with the EMS requirements established by the facility. Contractor/subcontractor personnel may be required to complete EMS training prior to beginning work

5.3.1 Executive Order Compliance

Executive Order (E.O.) 13423, Strengthening Federal Environmental, Energy, and Transportation Management, and E.O. 13514, Federal Leadership in Environment, Energy, and Economic Performance, establish the requirement for an EMS.

5.3.2 Secretary of the Air Force Policy Compliance

In accordance with the Assistant Secretary of the Air Force (SAF) Policy Letter, Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations, dated 11 Dec 06, and the Air Force Materiel Command/Vice Commander (AFMC/CV) Policy Letter, Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air…