PWS.docx

Performance Work Statement for AN/ALQ-172 Enhanced Maintenance Test Set (EMTS) Test Program Set (TPS) Maintenance & Support

Purchase Request: FD2060-24-00035 11 December, 2023

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD Contractors only, due to critical technology, date of determination: 15 July 2013. Other requests shall be referred to AFSC/PZABB 236 Byron St STE 19A; Robins AFB GA 31098- 670. Questions concerning technical content should be directed to 408 SCMS/GULB, 460 Richard Ray Blvd, STE 200, Robins AFB GA 31098-1813.

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 of 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 destroyby any method that will prevent disclosure of the contents or reconstruction of the document

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to to develop and sustain TPS, TPIH and other test support equipment. These services include TPS/TPIH/Support Equipment deficiency investigation/resolution, generation/consolidation of documentation for hardware and software test requirements definition; TPS/TPIH trade-off analysis; testing requirements analysis and implementation at operational, intermediate and Depot maintenance levels.

The contractor shall accomplish highly specialized engineering tasks that include AN/ALQ-172 systems test product engineering, Test Program Set (TPS)/Test Program Interface Hardware (TPIH) development, sustainment, testing and evaluation related to the ALQ-172 V(1), V(2) EMTS and component issues as well as associated technical documents and/or Technical Orders (TOs).

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by by increasing maintainability, repairability of the AN/ALQ-172 system as well as conducting corrective, perfective and adaptive maintenance actions in order to resolve system/subsystem-related test deficiencies.

1.3 Background: The contractor shall support 408 SCMS, the Supply Chain Management Manager for the AN/ALQ-172 system, by participating in all phases of TPS development and sustainment effort. The end goal is to provide cost-efficient, quality software and hardware solutions that can be fielded in a timely manner and support the United States Air Force (USAF) mission.

The AN/ALQ-172 Countermeasures System (CMS) is the primary Radio Frequency (RF) Electronic Warfare (EW) system installed on the Air Force Global Strike Command (AFGSC) B-52H and Air Force Special Operations Command (AFSOC) MC-130H Combat Talon II and AC-130U Gunship.

2.0 Services Summary

No Test Program Set (TPS) shall fail the required tests due to design flaws. Failure will be considered to be in non-compliance of this PWS unless corrected within the cost and schedule limits allowed by the original contract.

Provide red-lines of documentation changes via the DAL.

Ensure contracted project stays within agreed upon cost limits as documented in the approved WBSD.

3.0 Government Property: Applicable Government furnished equipment is already in contractor possession under existing repair contract FA8522-15-D-0002 and FA8422-15-D-0002 is available for use on a rent free non-interference basis. This equipment includes the ALQ-172(V) Enhanced Maintenance Test Set. There is only one located at the L3Harris facility and it is accountable to the repair contract. In addition, Government furnished equipment already at the contractors facility and accountable to contracts FA8540-14-D-0002, and FA8422-15-D-0002 is also available for use on a rent free non-interference basis. The Contractor shall report any type of loss of Government furnished property IAW all applicable Government property clauses provided in the contract.

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: No additional Government property will be provided.

3.3 Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

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 in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.4.3 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.0.1 ALQ-172 Test Program Set (TPS) Development and Sustainment: The contractor shall support the AN/ALQ-172(V) Test Program Set (TPS) development and sustainment cycle for Operational, Intermediate and Depot-level test equipment as directed by 408 SCMS/GULB. TPS Development and Support shall be defined as the EMTS UUT test software all components including any associated EMTS software/hardware required to support the UUT TPSs. . The contractor shall conduct all development activities in accordance with the Level 3 or higher requirements of CMU/SEI-2010-TR-033, Software Engineering Institute Capability Maturity Model for Development, Version 1.3. The contractor shall capture all data generated within the following subtasks in the Data Accession List (DAL) of Paragraph 4.0.1.12.1. The contractor shall report the status and the hours expended on each of the following subtasks and per TPS candidate, where appropriate, in the monthly status report. The contractor shall include a summary total of all candidates and hours expended (per candidate, where appropriate) for the entire contract in each monthly status report of Paragraph 4.0.1.12.2.

The contractor shall develop and/or resolve ALQ-172 TPS deficiency change request candidates for AFGSC and AFSOC, satisfying the technical and program requirements of the PWS including all affected Test Program Interface Hardware (TPIH) and/or Interface Test Hardware (ITA).

4.0.1.1 Project Planning: The contractor shall support development of a project plan that describes the software work plan, tasks and schedule for accomplishment. The project plan shall address the software development processes, software tools, documentation requirements, software coding standards, configuration management processes, technical milestone meetings and criteria, test methodology, and any other requirements for successful execution of this software effort. The plan shall address all tasks to be accomplished and the responsible entity for accomplishing each task.

· DI-IPSC-81427B, Software Development Plan, A001-D001

· DI-MGMT-81334D, Contract Work Breakdown Structure, A002-D002

· DI-MGMT-81861C, Integrated Program Management Report, A003-D003

4.0.1.2 TPS Requirements Definition: The contractor shall identify, analyze, and document the Unit Under Test (UUT) requirements including TPIH and ITA for TPS candidates to be resolved by the contractor. The contractor requirements definition shall include full definition of the required software and test equipment capabilities, identification of the software/hardware components required for the functionality, identification of interface requirements, and documentation of the requirements. The contractor shall deliver a Test Requirements Document (TRD) for TPS development efforts or a Software Requirements Specification (SRS) with red-lined modifications to the original specification as applicable.

The contractor shall support System, Software and Interface Requirements Reviews per Paragraph 4.0.1.13. The contractor shall not proceed to the design phase (Paragraph 4.0.1.3) until the Government technical POC acknowledges successful completion of the SRR.

· DI-ATTS-80041A, Test Requirements Document, A004-D004

· DI-IPSC-81434A, Interface Requirements Specification, A005-D005

· DI-IPSC-81433A, Software Requirements Specification, A006-D006

4.0.1.3 TPS Design Definition: The contractor shall allocate the documented hardware/software requirements into a detailed design, as applicable, for the software candidates to be resolved. The contractor shall logically organize requirements into objects, and top-level design issues shall be identified with planned mitigations. The contractor shall develop preliminary test plans. The contractor shall deliver design documents, with red-lined modifications to the original design documents as applicable data.

The contractor shall also develop and deliver system-level test descriptions to qualify the candidates.

· DI-IPSC-81435B, Software Design Description, A007-D007

· DI-IPSC-81436A, Interface Design Description, A008-D008

· DI-IPSC-81439A, Software Test Description, A009-D009

4.0.1.4 Code, Unit Test, Software, System Integration Test: The contractor shall generate source code for the software candidates to be resolved using the Government approved design from Paragraph 4.0.1.3. The contractor shall provide any recommended design changes to the Government technical POC. The contractor shall maintain the originally approved design unless the alternate recommendation is approved by 408 SCMS/GULB and AFLCMC/WNYEBA. The contractor shall code and document the source code files per the approved coding standards as defined in the approved Software Development Plan (SDP) of Paragraph 4.0.1.1.

To the maximum and practical extent possible, the contractor shall test modified source code files at the unit level per the SDP. The contractor shall test each unit independent of other units using tests that are automated and repeatable, where applicable. The contractor shall use unit-level test procedures that are documented and provide maximum comprehensive testing, where applicable. The contractor shall verify and report unit test results in the Integration Test Report.

The contractor shall design TPS hardware and software with a focus on software sustainment changes (e.g. changes within one software module to be tested with existing code from other modules, as appropriate), to the maximum extent practical. The contractor shall verify and report software integration test results in the Integration Test Report.

The contractor shall conduct System Integration Testing (SIT) using operational AN/ALQ-172 hardware and applicable TPIH and ITA. The contractor shall perform SIT at 408 SCMS/GULB designated facilities with the assistance of other contractor and government personnel. SIT is to be an engineering laboratory test of the integrated TPS hardware/software to evaluate the technical adequacy of the TPS and/or the resolution of the TPS deficiencies and to ensure the TPS hardware/software solution(s) have no negative impact to system test set performance. The contractor shall deliver as requested applicable data for this work effort. The contractor shall verify and report SIT results in the Integration Test Report. Successfully pass all testing requirements with no more than two retests. Following AFLCMC/WNYEBA acceptance of the System Integration/Design Verification Tests, no more than 5% of scheduled regression tests shall fail due to problems induced by the solutions.

No Test Program Set (TPS) shall fail the required tests due to design flaws. Failure will be considered to be in non-compliance of this PWS unless corrected within the cost and schedule limits allowed by the original contract.

The contractor shall follow the applicable formal hardware/software development process to document and place test procedures and test results under configuration control. The contractor shall document defects detected during this phase following the process defined in the SDP. The contractor shall deliver applicable data for this work effort.

The contractor shall record all software deficiencies discovered through test in an AFLCMC/WNYEBA approved form. The contractor shall incorporate all Engineering Problem Report (EPR) database updates.

The contractor shall support a Test Readiness Review (TRR) for system functional testing per Paragraph 4.0.1.13. The contractor shall not begin the qualification tests of Paragraph 4.0.1.5 until the AFLCMC/WNYEBA technical POC acknowledges successful completion of the TRR.

· DI-NDTI-80603A, Test Procedure, A010-D010

· DI-IPSC-81440A, Software Test Report, A011-D011

· DI-NDTI-80809B, Test/Inspection Report, A012-D011

4.0.1.5 Qualification/ Acceptance Test: The contractor shall perform a Qualification/Acceptance Test to demonstrate that the software and hardware products meet the system requirements and performs adequately for field use. The contractor shall perform testing at 408 SCMS/GULB designated facilities with the assistance of other contractor and government personnel. The contractor shall perform Software Functional Test (SFT) in a real-time environment with and without induced faults (as applicable). The contractor shall accomplish testing using digital and radio frequency (RF) simulations as appropriate. The contractor shall deliver applicable data for this work effort.

· DI-NDTI-80603A, Test Procedure, A010-D010

· DI-IPSC-81440A, Software Test Report, A011-D011

· DI-QCIC-81890, Qualification Test Report, A013-D013

4.0.1.6 Fielding Support: The contractor shall provide interim sustainment and maintenance support during and following completion of qualification and field testing. Interim support may be required during accomplishment of Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA) and subsequent fielding of the software product. The contractor shall update and deliver, when applicable, a Software Production Specification (SPS), Software Version Description (SVD), and Software User Manual (SUM). The contractor shall update and deliver the English Language Test Document (ELTD). Final version T.O. changes shall be free of technical errors and require no major re-work, as determined by the Government. The contractor shall update and deliver, when applicable, T.O. change packages and technical manual source per Paragraph 4.0.1.11. The contractor shall deliver applicable data for this work effort. No deliveries shall occur greater than 10% outside the established Schedule Performance Index (SPI) boundary for more than two consecutive reporting periods as defined in individual task orders. For any deviation greater than 5%, notification shall be given within 5 business days and also documented in the subsequent monthly status report of Paragraph 4.0.1.12.2, but are not cause for negative ratings. If the late delivery exceeds 10% for two consecutive reporting periods as defined in individual task orders, then the contractor shall be in non-compliance with the contract.

· DI-IPSC-81441A, Software Product Specification, A014-D014

· DI-IPSC-81442A, Software Version Description, A015-D015

· DI-IPSC-81443A, Software User Manual, A016-D016

· DI-MISC-81384, Service Engineering Report (SER), A017-D017

· DI-IPSC-81488, Computer Software Product, A018-D018

4.0.1.7 Final Design Review: The contractor shall conduct a final design review (FDR) when detail design is fully complete to present the details of the TPS, TPIH and ITA. The review shall illustrate that the detail design satisfies the operational and technical performance and sustainment support requirements of the UUT. The review shall assess producibility and risk (technical, cost, and schedule) as well as review of the final specifications and test results.

· DI-ADMN-81249C, Meeting Agenda, A019-D019

· DI-ADMN-81373, Presentation Material, A020-D020

· DI-ADMN-81250C, Meeting Minutes, A021-D021

4.0.1.8 Functional Configuration Audit/ Physical Configuration Audit

4.0.1.8.1 Functional Configuration Audit/ Physical Configuration Audit (PCA) Planning: The Contractor shall develop and deliver a FCA/PCA plan. The FCA/PCA is to serve as a formal audit of any hardware Configuration Items (CI) generated as part of this effort in support of TPS sustainment to verify the Product Baseline. The Contractor’s audit plan shall validate that the functional and allocated performance requirements are satisfied. The Contractor’s audit plan shall also verify that the technical documentation adequately represents the CI. The FCA is typically performed via test, and the PCA is performed by verifying that the data (specifications, plans, test reports, drawings, etc.) adequately represent the CI.

· DI-SESS-81646C, Configuration Audit Plan, A022-D022

4.0.1.8.2 FCA/PCA Audit: The Contractor shall execute the 408 SCMS/GULB-approved audit plan of Paragraph 4.0.1.8.1 and per the requirements of Paragraph 4.0.1.13. The Contractor shall conduct a multi-disciplined FCA/PCA of the Government approved configuration within two (2) months after FDR to ensure: that the actual performance meets the specification requirements documented in the Functional, Allocated, and Product Baselines; that the configuration controlled product baseline (build-to) documentation reflects the physical item approved; and that 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 one week prior to the review. The Contractor shall develop and deliver a FCA/PCA report that documents audit findings.

· DI-ADMN-81249C, Meeting Agenda, A019-D019

· DI-ADMN-81373, Presentation Material, A020-D020

· DI-CMAN-81022E, Configuration Audit Summary Report, A023-D023

4.0.1.9 Detailed Cost Analysis and Integrated Logistics Support: The Contractor shall deliver detailed cost analysis for both the non-recurring and recurring costs needed for TPIH, ITA and other test fixtures.

· DI-MISC-80711A, Scientific and Technical Reports, A024-D024

· DI-ILSS-80095, Integrated Logistics Support Plan, A025-D025

4.0.1.10 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 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-2017, 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-2017 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. The contractor shall submit an engineering drawing tree identifying all system, subsystem and equipment drawings as part of the drawing package prior to CDR.

· DI-SESS-81000F, Product Engineering Design Data and Associated Lists, A026-D026

4.0.1.10.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:

· Understanding of all CDRL requirements, applicable DIDs, specifications

· and standards.

· TDP review requirements and schedules.

· TDP delivery requirements and schedules.

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

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

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

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

· Digital Technical Data Package (TDP) deliverables.

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

· DI-ADMN-81249C, Meeting Agenda, A019-D019

· DI-ADMN-81250C, Meeting Minutes, A021-D021

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

· DI-ADMN-81249C, Meeting Agenda, A019-D019

· DI-ADMN-81250C, Meeting Minutes, A021-D021

4.0.1.10.3 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 engineering data prior to delivery of data for review.

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

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.0.1.10.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.0.1.11 Technical Orders: The contractor shall develop and deliver red-lined technical order changes generated by any TPS development and/or sustainment effort associated with the ALQ-172 UUT.

4.0.1.12 Program Management

4.0.1.12.1 Data Accession List (DAL): All data developed under this work effort shall become property of the Government and under data management control of the responsible Government office. The contractor shall provide a DAL that lists all data developed by the contractor in accomplishment of this task. The contractor shall provide access to any data developed under this or any previous government tasks at the request of 408 SCMS/GULB. Red-lined documents shall be technically accurate, and, following receipt of all comments shall require no more than one (1) revision after the initial submission.

· DI-MGMT-81453B, Data Accession List, A028-D028

4.0.1.12.2 Monthly Status Report: The contractor shall document the status of all activities performed in a monthly status report. As an attachment to the monthly status report, the contractor shall include copies of the invoices submitted for payment. Minimum items to be addressed in the report include:

· Identification of areas where the contractor’s performance/deliverables are not projected to meet the requirements of the contract

· Schedule of actual material and travel costs versus planned costs to date and projections to the end of contract

· Status of Action Items from reviews and meetings

· Summary of work performed during the month

· Summary of planned work during next month

· Identification of technical problems or anomalies encountered

· Metric reports required by the contract

· EPR matrix to keep track of EPRs generated, EPRs occurring post integration tests, RESETS due to coding errors, phase of test program and current status

· Rework matrix, identifying the rework products (Software work products, tests, etc.), rework hours and estimated rework costs

The contractor shall update and deliver the Integrated Master Schedule (IMS) with the status report. The contractor shall be allowed less than 15% schedule variance against project schedules for development, testing, investigations, and document support.

· DI-MGMT-80368A, Status Report, A029-D029

· DI FNCL 80331A, Funds and Man-Hour Expenditure Report, A030-D030

4.0.1.12.3 Post Award Conference: The contractor shall hold a Post Award Conference (PAC) approximately thirty (30) calendar days after each delivery-order award. The purpose of this meeting will be to discuss security, technical aspects of project execution, overall schedule, and other requirements. The contractor shall submit an agenda, presentation and minutes in accordance with the deliverables per Para. 4.0.1.13.

4.0.1.12.4 Techincal Interchange Meetings (TIMs): The contractor shall support, participate in, and as directed by the 408 SCMS/GULB and/or AFLCMC/WNYEBA, chair TIMs in support of this effort. The intent of these meetings is to ensure proper technical control and program management. No pre-submitted agenda is required unless specifically requested by 408 SCMS/GULB. The contractor shall record detailed minutes of each review and shall provide them as an attachment to the status report covering the calendar period during which the meeting took place. The meeting shall be held either virtually or at a government or contractor’s facility at the discretion of 408 SCMS/GULB.

4.0.1.12.5 Program Management Reviews (PMRs): The contractor shall host quarterly program management reviews with 408 SCMS/GULB representatives for the duration of the program. At each PMR the contractor shall include a presentation of project status showing all work accomplished and any problems encountered. These formal reviews may be held at another government installation or contractor facility if specified by the 408 SCMS/GULB. PMRs may also be scheduled on an "as requested" basis by either the Government or the contractor. The contractor shall conduct and document the meetings for the purpose of program control and review. The contractor shall submit an agenda, presentation and minutes in accordance with the deliverables of task 4.0.1.13.

4.0.1.12.6 Meetings: The contractor shall conduct or support meetings as required to accomplish the work efforts in this task. As requested by 408 SCMS/GULB, the contractor shall participate or conduct the following conferences:

Requirements Reviews per Para. 4.0.1.2 Test Readiness Reviews (TRR) per Para. 4.0.1.4 FDR per Para. 4.0.1.7 FCA/PCA per 4.0.1.8 Post Award Conference per Para. 4.0.1.12.3 Technical Interchange Meetings per Para. 4.0.1.12.4 Program Management Reviews per Para. 4.0.1.12.5

The contractor shall provide engineering and program expertise to support all aspects of the AN/ALQ-172 throughout the ALQ-172 community (e.g. Program Management Reviews, Working Groups and Technical Interchange Meetings) as requested by 408 SCMS/GULB.

The contractor shall submit agendas and minutes for each meeting conducted. The contractor shall accomplish the travel required to complete these work efforts and shall provide a trip report as an attachment to the status report covering the calendar period during which each trip was taken. The contractor shall submit travel requests to the 408 SCMS/GULB program manager prior to costs being incurred and a minimum of 5 business days prior to all routine travel. Travel requests shall include the names and applicable roles of travelers, travel dates, purpose of travel, duration of the trip, itinerary, current travel CLIN balance and estimated cost. The contractor shall not perform any travel until written permission is provided by 408 SCMS/GULB.

· DI-ADMN-81249C, Meeting Agenda, A019-D019

· DI-ADMN-81373, Presentation Material, A020-D020

· DIADMN81250C, Meeting Minutes, A021-D021

· DI-MISC-81384, Service Engineering Report, A031-D031

4.0.1.13 Equipment Maintenance: For the purposes of this work effort the entity referred to as the equipment shall be defined as:

· All TPIH, ITA, mockups and other test tools connected to the AN/ALQ-172 system

· Installed LRU cooling systems with their associated plumbing

· All associated interconnecting cables

The contractor shall maintain the equipment required to accomplish the defined in this PWS and perform the following, as a mimimum:

· Maintain the equipment in a safe and operational state

· Maintain and document configuration control of all equipment

· Document anomalies/failures and corrective action taken

· Troubleshoot anomalies/failures down to the Line Replaceable Unit (LRU) or Shop Replaceable Unit (SRU) level as applicable

· Support the government equipment custodian with meeting PMEL calibration requirements

· Perform scheduled maintenance on all equipment including daily, monthly and annual inspections

· Support Government Furnished Property (GFP) and Government Furnished Material (GFM) materiel handling services (including shipping, auditing, documenting utilization and consumption reporting)

· Purchase and provide consumable items and supplies as needed for TPS, TPIH and ITA operation and maintenance.

The contractor shall submit to the Government a list of all necessary EMTS UUT TPS hardware (i.e. EMTS cables and associated connectors) to support the Maintenance and Reliability System (MARS) LRU TPSs. This submittal shall include, but is not limited to, a Rough Order of Magnitude (ROM) identifying all costs associated with this procurement, a list of materials and/or end item components, and estimated build/delivery schedule. The Government will review and provide comments or concurrence. The Contractor shall provide a response to any Government comments within 15 calendar days. This procurment will be under its own future task order.

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend for basic year period and three option years FY24-27.

4.1.2 Place of Performance: These services will be performed by L3 Harris at Clifton, NJ and at the subcontractor’s facility

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier Base Year Option Year Option Year Option Year

4.0.1.10.1/4.0.1.10.2/ 4.0.1.12.6

4.0.1.12.6

4.0.1.10.2/4.0.1.12.6

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than one total rejection(s) of deliverables per quarter. The Government will reject a deliverable if one or more technical errors or five 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 in accordance with the respective CDRL.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than one late 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 the Government.

4.3 Engineering Services

4.3.1 Item Unique Identification

4.3.1.1 Marking Requirement: Unique Item Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.

4.3.1.1.1 IUID Marking Plan: The Contractor's IUID Marking Plan shall fully detail and document the strategy and scope to be used to meet MIL-STD-130, DoD Standard Practice Identification Marking of US Military Property. The plan must be approved by the system specific engineer prior to implementation. This applies only to items that are not already properly marked.

· DI-MGMT-81803A, IUID Marking Plan A032-D032

4.3.1.1.2 IUID Marking Activity and Verification Report: The Contractor shall provide an IUID Marking Activity and Verification Report. A key attribute for the report is the Verification column which indicates pass/fail for each item's Data Matrix Symbol Quality.

· DI-MGMT-81804A, IUID Marking Activity and Verification Report A033-D033

4.3.1.2 Reporting in 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.3.1.2.1 Transmission of Government property must be recorded in the IUID Registry. The Government is required to record the transfer of GFP to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government.

4.3.1.2.2 The Government or contractor/subcontractor personnel responsible for causing a “life cycle event” (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 in the IUID Registry.

4.3.2 Packaging: The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM). The Contractor shall package and mark material in accordance with other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns.

4.3.3 Counterfeit Electronic Parts: The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronic parts being installed in end items or otherwise entering the USAF/DoD inventory. These policies and procedures shall be documented in a 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.

· DI-MISC-81832, Counterfeit Prevention Plan, A034-D034

4.4 Supply Chain Risk Management: At a minimum evaluate the following critical supply chain risk areas: Continuity of Operations, Foreign Influence and Cyber Security for all contracts, additionally evaluate Counterfeit Prevention for contracts with FSG 59 items. These risk focus areas were chosen because they represent a high likelihood of serious disruptions to supply chain operations.

4.5 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as authorized for government personnel. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.6 Travel: Travel requests for contractor/subcontractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of 2 business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs.

4.6.1 The contractor shall travel in support of the meeting and testing requirements of this PWS as required by 408 SCMS.

4.6.2 Travel: Travel requests for contractor/subcontractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of 5 business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Designation of Services as Mission-Essential: The Functional Service Manager (FSM) has determined certain services under this contract/order are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

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: DoDM 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 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, sub contracts, and information used in the performance of duties in support of Air Force requirements/missions. The Contractor shall ensure Contractor personnel who perform work on (or in) a Government facility comply with the OPSEC procedures and training requirements of the facility as specified in AFI 10-701.

5.2.4 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer…