RFS SOW - DRAFT - 20241212.docx

CUI

UPGRADED EARLY WARNING RADAR (UEWR)

RADIO FREQUENCY SWITCH (RFS) PROCUREMENT AND DEPLOYMENT (P&D)

STATEMENT OF WORK (SOW)

Revision Number: 1.0

12 December 2024

Space Systems Command (SSC) Battlespace Awareness Acquisition Delta (SSC/SZBQ)Controlled By: USSF, SSC/SZB Category: OPSEC, PROCURE Dissemination: D POC: Maj James Dossett

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and U.S. DoD contractors only, for Administrative or Operational Use, 10 September 2024. Other requests for this document shall be referred to SSC/SZB.

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 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any means that will prevent disclosure of contents or reconstruction of the document.

TABLE OF CONTENTS

INTRODUCTION

Scope. This Statement of Work (SOW) defines the effort to procure, build, test, deliver, and install/test 70 Radio Frequency Switch (RFS) units plus 11 spare units for the Upgraded Early Warning Radar (UEWR) weapon system and 1 qualification unit. The RFS units are already a fully qualified design.

1.2 Background. There will be 81 total RFS units across the five radar sites (Royal Air Force (RAF) Fylingdales, UK; Cape Cod Space Force Station (SFS), MA; Beale Air Force Base (AFB), CA; Clear SFS, AK; and Pituffik Space Base (SB), Greenland). These RFS will be installed on top of a cabinet inside the radar. They provide a failsafe connection to the legacy analog beamforming path while allowing for future modernization efforts without interrupting legacy operations. The breakout by site is provided in Table 1: RFS Production Requirements by UEWR Site.

Table 1: RFS Production Requirements by UEWR Site

1.2.1 A notional diagram of the RFS installed on the cabinets is below in Figure 1: RFS Installation.

Figure 1: RFS Installation

1.2.2 The RFS design was fully qualified and operationally accepted in fiscal year 2024. The Level III Technical Data Package (TDP) will be utilized for procurement, construction, and unit test.

0. REQUIREMENTS

2.1 General

2.1.1 Procure the parts and material to build 81 RFS units in accordance with (IAW) the FY24 RFS TDP.

2.1.2 Build, ship, and deploy 81 procured RFS units and spares to five UEWR sites. Quantities by location are listed in the associated RFI CUI Appendix.

2.1.3 Initial/Final Qualification testing will be required on the first unit.

2.1.4 Deliver RFS units and spares as follows.

2.1.5 Deliver the Continental United States (CONUS) RFS units and spares directly to Cape Cod SFS, Massachusetts; Beale AFB, California; and Clear SFS, Alaska.

2.1.6 Deliver RAF Fylingdales units and spares to RAF Mildenhall, UK for surface shipment to destination.

2.1.7 Deliver Pituffik SB systems and spares to Joint Base McGuire-Dix-Lakehurst, New Jersey, for air channel cargo shipment to destination.

2.1.8 Plan and perform required site modifications (power/cable trays/other) necessary prior to RFS installation.

2.1.9 Deploy RFS units through Operational Acceptance (OA) at each site.

2.2 Security Considerations

2.2.1 This contract will likely require access to the following types of information/data:

1. Secret information

2. Restricted Data (RD)

3. Formerly Restricted Data (FRD)

4. North Atlantic Treaty Organization (NATO) information

5. Controlled Unclassified Information (CUI).

2.2.2 Information Security: The contractor performing duties associated with contract must adhere to all the standards for protecting classified information as specified in DODM 5200.01 v1-v3_AFMAN 5200.01 v1-3, Information Security Program and all applicable supplements and operating instructions.

2.2.3 Physical Security. Contractor employees shall comply with base Operations Plans/instructions for FPCON procedures, Random Antiterrorism Measures (RAMS) and Operation Security (OPSEC), Emergency Management (EM) and local search/identification requirements. The contractor shall safeguard all government property including controlled forms provided for contractor use. At the close of each work period, government training equipment, facilities, support equipment, and other valuable materials shall be secured.

2.2.4 The contractor will adhere to all Space Force and/or Air Force activity Operating Instructions (OI) for internal circulation control, protection of resources and to regulate entry into Space Force/Air Force controlled areas during normal, simulated and actual emergency operations to include local written OIs.

2.2.5 For those contractor and subcontractor employees requiring access to federal installations, the company’s facility security officer (FSO) or the contractor's contract manager (or alternate) shall complete a Visit Authorization Request (VAR). For contractor personnel expected to perform classified work, submit the var, via the Defense Information System for Security (DISS) to the Government security manager or, for contractors working on other military installations coordinate with the Government security office.

2.2.6 Contractor personnel requiring credentials shall comply with and meet the credentialing standards, IAW Homeland Security Presidential Directive 12 (HSPD 12) and DoDI 5200.02, which requires at a minimum a favorably adjudicated Tier 1 investigation with fingerprinting to obtain access to AF information systems, sensitive information, and receive credentials.

2.2.7 As prescribed by Department of Air Force Federal Acquisition Regulation Supplement (DAFFARS) 5352.242-9000, Contractor Access to Air Force Installations, DAFFARS 5352.242-9001, Common Access Cards (CAC) for Contractor Personnel, and Federal Acquisition Regulation (FAR) 52.204-9, Personal Identity Verification of Contractor Personnel the contractor must comply with the requirements set forth in this guidance.

2.2.8 The contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site.

2.2.9 The contractor shall complete a request for identification credential or CAC for each employee requiring access federal property. The request shall be submitted to the Government security manager who will notify the contractor of the current procedure for obtaining a CAC and the governing regulations and policies. For the CAC application, a company sponsored e-mail address must be provided for each contractor employee.

2.2.10 This contract requires contractor employees to obtain a CAC. Contractors shall provide a listing of personnel who require a CAC to the contracting officer. The Government will provide the contractor instruction on how to complete the trusted associate sponsorship (TASS) application and then notify the contractor when approved contractor personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation system (RAPIDS) issuing facility (typically the local Military Personnel Flight (MPF).

While visiting or performing work on installation(s)/location(s), contractor personnel shall wear or prominently display the CAC, as required by the governing local policy.

2.2.11 Defense Biometric Identification Systems (DBIDS) card/pass (AF Form 75 may be used only if DBIDS is inoperable).

2.2.12 All Government issued identification upon completion of contract, termination of contract or service, resignation/termination of employees, or expiration of the identification shall be returned to the Government.

2.2.13 The contractor shall comply with all applicable regulations, policies, and local base procedures for entry to Air Force controlled or restricted areas for escorted access and/or unescorted access for all personnel.

2.3 Program Management

2.3.1 The Contractor shall plan, organize, coordinate, integrate and execute all requirements outlined in this document.

2.3.2 The Contractor shall plan, host, and conduct a Kickoff meeting with the Government within 30 calendar days upon contract award. The objectives of the Kickoff meeting are the contractor’s plan for supporting these tasks, fabrication set-up time, key supplier relationships, shipping/delivery plan, invoicing plan, strategic schedule up to production qualification testing, deployment planning, general site maintenance/modification requirements, site survey requirements, identification of key stakeholders, opportunities/capture plans, and risks/mitigation plans. The contractor and/or the Government may include other topics as conditions warrant. Post slides NLT 3 business days prior to the event.

2.3.3 The Contractor shall prepare and coordinate approval of Kickoff meeting minutes from which include attendees, key discussions, and action items NLT 3 business days after the meeting. [DAL Kickoff Meeting Minutes]

2.3.4 The Contractor shall plan, host, and conduct a quarterly Government stakeholder Program Management Review (PMR) of funding, history, outstanding actions, and status if significant interest items.

2.3.5 The Contractor shall provide PMR agenda and applicable draft briefing/discussion material to all Government participants a minim of 7 business days begore the planned PMR. [DAL PMR Minutes]

2.3.6 The Contractor shall prepare and coordinate Government approval of PMR minutes that include annotated briefing materials to document participants, summary of discussions, decisions, and follow-on actions NLT than 3 business days after the meeting. [DAL PMR Minutes]

2.3.7 The Contractor shall provide Fabrication Status Report data as part of the PMRs after Production Qualification Test (PQT) through the end of all procurement activities.

2.3.8 The Contractor shall plan, host, and conduct regular Integrated Product Team (IPT) meetings with the Government to review the status of the effort. The meetings shall consist of project status, review of key milestones, logistics, contract deliverables, risks, concerns, actions items, status of action items, and any other relevant discussion topics. The Contractor shall prepare and coordinate government approval of minutes of IPT meetings NLT 3 business days after the meeting. [DAL IPT Meeting Minutes]

2.3.9 The Contractor shall report any problems during fabrication via telephone/electronic notification the day of the incident/occurrence followed by a Report of Production or Delivery Problems within 5 business days of occurrence. [DAL Report of Production]

2.3.10 The Contractor shall develop, maintain, update, and execute an overarching Integrated Master Schedule that integrates all, vertically and horizontally, RFS P&D activities for a baseline. The IMS shall include, but not limited to, production tasks, deployment tasks, government dependencies, external dependencies, milestones, resource loaded tasks, critical paths, and predecessor/successor relationships. The schedule shall provide sufficient detail to determine critical path.

2.3.11 The Contractor shall prepare and coordinate Government approval of the IMS at the within 3 business days of the Kickoff and provide updates by the 20th of each subsequent month through final deployment, or as directed by the Government. [DAL IMS]

2.3.12 The Contractor shall prepare and deliver a monthly Funds and Man Hour Expenditure Report. [CDRL A00X]

2.4 System Engineering

2.4.1 The Contractor shall plan, organize, coordinate, integrate, execute, and manage al system engineering efforts, all site work, documentation, installation, and any other related site activities.

2.4.2 The Contractor shall develop and deliver a Manufacturing Plan. [CDRL A00X]

2.5 Fabrication/Production Qualification

2.5.1 The Contractor shall conduct required reviews as standard in production and deployment efforts (such as, but not limited to, Production Readiness Review (PRR), Manufacturing Readiness Assessment (MRA), Initial/Final Test Readiness Reviews (TRRs)) with the Government.

2.5.2 The Contractor shall develop a System Test Plan (STP) for PQT, Production Acceptance Test and Evaluation (PAT&E) at the first procurement site, and Formal Contractor Testing (FCT) at subsequent procurement/deployment sites for the RFS units. At the end of all RFS site deployments, the STP for FCT shall be updated such that it covers the SIL and all five sites. [CDRL A00X]

2.5.3 The Contractor shall build a minimum of one RFS unit for PQT and deploy the finalized products at the first UEWR procurement site as listed in Table 1: RFS Production Requirements by UEWR Site.

2.5.4 The Contractor shall develop, validate and deliver PQT descriptions/procedures prior to PQT in-plant testing. [CDRL A00X]

2.5.5 The Contractor shall conduct Initial and Final Test Readiness Reviews (TRRs) for site coupling installations and RFS system deployments.

2.5.6 The Contractor shall conduct PQT in-plant with the Government present. While the Government may not be present for the entire fabrication of the initial articles, it is the Government’s intent to observe key aspects of fabrication, acceptance testing, and crating as part of PQT.

2.5.7 The Contractor shall perform Correction of Deficiencies (COD) following the PQT, if required.

2.5.8 The Contractor shall conduct a Delta PRR after a PQT COD, if required by the Government. The Delta PRR shall use the PRR format focused on changes resulting from the COD.

2.5.9 The Contractor shall provide a PQT Report. [CDRL A00X]

2.6 Full Rate Production

2.6.1 The Contractor shall develop, validate, and deliver Production Acceptance Test and Evaluation (PAT&E) descriptions/procedures 30 calendar days prior to PAT&E of the initial procurement articles. [CDRL A00X]

2.6.2 The Contractor shall update the Technical Data Package (TDP) and associated documentation for changes due to material substitution due to obsolescence, changes in the fabrication process, or minor design changes. [CDRL A00X).

2.6.3 The Contractor shall fabricate and deliver RFS units as indicated in Table 1: RFS Production Requirements by UEWR Site.

2.7 Deployment

2.7.1 The Contractor shall travel to deploy RFS units and spares to the sites.

2.7.2 The Contractor shall coordinate with the UEWR Product Division for site surveys, site access, and site lodging as outlined below. Final approval to travel occurs at the final TRR or Site Deployment Readiness Review (SDRR), as appropriate.

2.7.3 Peterson SFB, Beale AFB, and Clear SFS personnel should be identified with Defense Information System for Security (DISS) inputs no later than (NLT) two weeks prior to travel. The Contractor shall coordinate directly with Clear SFS services; however, on-site lodging cannot be guaranteed.

2.7.4 RAF Fylingdales travel and personnel must be identified NLT 45 calendar days prior for United Kingdom “Request For Visit (RFV)” processing. Substitutions should be only due to emergencies; however, additional names may be added as risk mitigation for such substitutions.

2.7.5 Pituffik SB travel to include Air Mobility Command passenger reservations and lodging shall be coordinated with the UEWR PD NLT 60 days prior to travel.

2.7.6 The Contractor shall develop and deliver a Site Preparation Requirements Installation Plan (SPRIP), also known as (AKA) Work Plan, that covers all aspects of the site modification and deployment activities. This plan needs to be developed in draft format prior to the first site deployment activity to support the Government’s Risk Management Readiness Review process. The SPRIP should be continuously refined until the final SDRR or TRR as appropriate. Post the draft SPRIP NLT 7 calendar days prior to the initial SDRRs/TRRs and final SPRIP NLT 7 calendar days prior to the final SDRRs/TRR(s). [DAL Site Preparation Requirements Installation Plan]

2.7.7 Deficiency Reporting. The Contractor shall support Government Deficiency Reporting (DR) systems and processes. These processes include providing data for entry into the Joint Deficiency Reporting System (JDRS) and supporting Deficiency Review Boards (DRBs).

2.7.8 The Contractor shall conduct SDRRs for non-test events at site. Plan to accomplish SDRRs virtually.

2.7.8.1 The Contractor shall develop briefing slides for the SDRRs. Post slides NLT 7 business days prior to the event. [DAL]

2.7.8.2 The Contractor shall record and post SDRR minutes. Post minutes NLT 3 business days after the meeting. [DAL]

2.7.9 System Test Descriptions (STDs). The Contractor shall update STDs for site deployments to support FCT, Developmental Test (DT), and Operational Test and Evaluation (OT&E). This should equate to site specific changes to PAT&E procedures and initial Cape Cod site testing procedures. Updates should reflect sequential site activity such that the final STDs cover the SIL and five sites. [CDRL A00X]

2.7.10 Test Readiness Reviews (TRRs). The Contractor shall conduct Initial and Final TRRs for coupling installations and site RFS system deployments. Plan to conduct the first TRR at the Contractor’s site and the subsequent TRRs virtually.

2.7.10.1 The Contractor shall develop briefing slides using the Government template as guidance for all deployment related TRRs. Post slides NLT 3 business days prior to the event. [DAL]

2.7.10.2 The Contractor shall provide minutes from all deployment related TRRs. Post minutes NLT 3 business days after the meeting. [DAL]

2.7.11 Integrated Test Teams (ITTs). The Contractor shall support Government ITTs as directed. Plan on ITT support for each site.

2.7.12 The Contractor shall develop and brief Site Commander In/Out Briefs Post slides NLT 7 business days prior to the event. [DAL]

2.7.12.1 Site In-briefs should cover as a minimum:

1. The scope of planned work (installation/testing)

2. Team size/composition

3. General schedule of site activity

4. Site support requirements

5. Risks/hazards

2.7.12.2 Daily Site Activity Reporting. The Contractor shall provide daily reporting via NIPRNet to the UEWR Chief of Test and the Program Manager (PM). This should be at the Controlled Unclassified Information (CUI) level and include key accomplishments, challenges, and other key information as required. [CDRL A00X]

2.7.12.3 Site Out-briefs need only report on the results of the overall activity and may use the same slide deck as used for the In-Brief.

2.7.13 Quick Look Brief. The Contractor shall deliver a Quick Look Brief within 10 days of the conclusion of FCT. The brief shall cover preliminary results of testing.

2.7.14 The Contractor shall deliver a System Test Report (STR) for each procurement site deployment. [CDRL A00X]

2.7.15 The Contractor shall include trip reports for any contract related travel during the reporting period and as requested by the Government. Post trip reports NLT 7 calendar days after returning from the trip. [CDRL A00X]

2.8 Risk Management

2.8.1 The Contractor shall develop a Risk Mitigation Plan that includes how the contractor intends to track and resolve risks, to include likelihood (probability), consequence (impact), and associated rationale.

2.8.2 The Contractor shall continuously identify and categorize risks through various risk identification methodologies.

2.8.3 The Contractor shall provide the Government updates no less than at every PMR.

2.9 Configuration Management (CM)

2.9.1 The Contractor shall identify errors in pre-existing documentation and provide corrections/updates to the Government for review.

2.9.2 When a Notification of Revision (NOR) is approved by the government, the Contractor shall conduct a Physical Configuration Audit (PCA), with Government oversight, comparing the TDP (as documented) to the as-built configuration as part of the first lot Quality Control (QC) inspection, test, and verification action at the manufacturing facility.

2.9.3 The Contractor shall support PCAs as RFS units are deployed to remaining sites.

2.9.4 The Contractor shall provide a PCA Summary Report and Certification. [DAL] Post the report NLT 14 days after completion of the PCA.

2.10 Data Management (DM)

2.10.1 The Contractor shall provide meeting minutes after all formal reviews. Post minutes NLT 3 calendar days after the reviews. [DAL Meeting Minutes]

2.10.2 The Contractor shall deliver all data, documents, and CDRLs (drafts for review and final copies) IAW the requirements of this SOW and the relevant CDRL. All data products will be delivered in electronic format wherever possible. Deliveries will be made to the UEWR PD Points of Contact (POC) listed on the relevant CDRL.

2.10.3 The Contractor shall maintain a current and accurate DAL. The Contractor shall include all internally generated documents and data used by the Contractor to support and manage this effort in the DAL. The Contractor shall provide Government personnel free and unlimited access to items included in the DAL. [CDRL A00X].

2.11 Sustainment Engineering

2.11.1 Contractor shall plan and execute technical tasks, engineering and logistics investigations and analyses to ensure continued operation and maintenance of the system being developed. This includes:

2.11.1.1 Collection and triage of all service use and maintenance data. Post data and updates NLT 7 calendar days after data is obtained. [DAL]

2.11.1.2 Analysis of safety hazards, failure causes and effects, reliability and maintainability trends, and operational usage profiles changes. Post analysis NLT 7 calendar days after completion. [DAL]

2.11.1.3 Root cause analysis of in-service problems (including operational hazards, deficiency reports, parts obsolescence, corrosion effects, and reliability degradation). Post analysis NLT 7 calendar days after completion. [DAL]

2.11.1.4 The development of required design changes to resolve operational issues.

2.11.1.5 Other activities necessary to ensure cost-effective support to achieve readiness and performance requirements over a system's life cycle.

2.11.1.6 The Contractor shall recommend engineering changes which would improve technical performance, improve reliability and maintainability, or reduce operating costs for Obsolescence.

2.12 Maintenance Planning and Management

2.12.1 Any Contractor modifications to the approved design shall not deviate from the approved maintenance concept.

2.12.2 The Contractor shall continue to perform Failure Modes, Effect, and Criticality Analysis (FMECA) no later than prior to deployment to first site. Post analysis NLT 7 calendar days after completion. [DAL]

2.12.3 The Contractor shall conduct a Level of Repair Analysis (LORA) IAW MIL-HDBK-1390, Level of Repair Analysis and SAE AS 1390, Level of Repair Analysis.

2.12.4 The Contractor's LORA shall be consistent with the maintenance concept.

2.12.5 The Contractor shall consider items to be included in LORA, (e.g. Training Systems, SE/Test Measurement Diagnostic Equipment (TMDE), SIL, etc.)

2.12.6 The Contractor shall focus the LORA on optimizing the system maintenance concept to LORA goals, e.g., minimizing life cycle costs, meeting sustainment key performance parameters, etc.

2.12.7 The Contractor shall maintain an electronic LORA database, available to and accessible by the Government.

2.12.8 The Contractor shall develop and deliver the maintenance plan for any Contractor designed system(s) and any affected system(s)/sub-system(s) describing how the maintenance concept will be implemented, actions for each significant maintenance task, explains technical requirements to conduct maintenance, lists resource requirements, consumables and lists for each repairable item the supply, maintenance, and recoverability requirements/sources.

2.12.9 The Contractor shall perform Contracted Logistical Support (CLS) services for three months (90 calendar days) per site following each site’s Operational Acceptance to allow time for the Ground Based Radars Maintenance and Sustainment Services (GMASS) contractor to assume full sustainment responsibility. This includes the ability to initiate RFS related technical and engineering assistance for hardware, firmware and software, conduct root cause analysis and, if directed, correct deficiencies at site in case a failure requires an urgent or emergency correction.

2.13 Packaging, Handling, Storage and Transportation (PHS&T)

2.13.1 The Contractor shall identify, plan, resource, and acquire packaging/PHS&T requirements to maximize availability and usability of material to include support items whenever they are needed for mission success.

2.13.2 The Contractor shall utilize original manufacturer packaging and/or reusable “fast packs” when possible, for packaging, storing, and transporting LRUs, parts, and materials.

2.13.3 The Contractor shall utilize approved Special Packaging Instruction (SPI) IAW DD Form 2169, Special Packaging Instructions and MIL-STD-2073-1E, Standard Practice for Military Packaging, for those items with unique packaging, handling, and transportation requirements (dimensions, weight, dunnage, special markings, special handling, etc.) The Contractor may use ASTM D3951-15 as additional guidance.

2.13.4 For any packaging changes throughout fabrication and deployment, the Contractor shall update Preservation and Packing Data. [CDRL A00X].

2.14 Technical Data

2.14.1 The Contractor shall identify, plan, validate, resource and implement management actions to develop and acquire information to:

2.14.1.1 Operate, maintain, and train on the equipment to maximize its effectiveness and availability.

2.14.1.2 Define the configuration baseline of the system (hardware and software) to effectively support the Warfighter at the time it is needed.

2.14.2 The Contractor shall provide any required updates to the existing Level 3 Technical Data Package (TDP) IAW MIL-STD-31000B, Technical Data Packages and the TDP Option Worksheet which will support, production, engineering, and logistics support.

2.14.2.1 The TDP shall define the design configuration or performance requirements and procedures required to ensure the adequacy of item performance.

2.14.2.2 The TDP shall consist of applicable technical data such as models, drawings, drawing tree, trade studies, associated lists, specifications, standards, performance requirements, quality assurance requirements, test equipment, software documentation, software or binary code embedded on memory chips, interface control documents (ICDs), and packaging details.

2.14.2.3 Drawings shall be developed/updated IAW ASME Y14.24, Y14.34, Y14.35M, Y14.41, Y14.5, and Y14.100 standards.

2.15 Technical Data – Manuals

2.15.1 The Contractor shall implement the Air Force Technical Manual Contract Requirements (TMCR) specified TMCR TM-86-01R. [CDRL A00X]

2.15.2 The contractor shall submit recommended additional, contractor-identified TM/TO, TMCR TM-86-01R, as a TM Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, accompanied with a numbered contractor contracts letter to the Government CO requesting review and approval of the recommended requirement prior to developing additional data.

2.15.3 The contractor shall notify the Government Program Office of location, dates and times of all TO Certification activities.

2.15.4 The contractor shall obtain a Technical Order Distribution Account (TODA) in Enhanced Technical Information Management System (ETIMS), as described in Technical Order (TO) 00-5-1, to obtain baseline TOs for the UEWR-related Contract-covered systems.

2.16 Data Rights

2.16.1 The Contractor shall deliver all documents/material produced under this contract with Government Purpose Rights or Unlimited Data Rights.

2.16.2 At or before the conclusion of the period of performance of this contract, the Government will acquire all RFS technical data, Model-Based Systems Engineering (MBSE) models, deliverables, databases, tools, computer software, and computer software documentation delivered, produced or otherwise provided to the Government during the performance of this contract in an editable format and accessible in the Government environment.

2.16.3 All documents and materials, to include the source codes of any software, produced under this contract, permit the Government to use, modify and disclose in any manner for any purpose without restriction.

2.16.4 These documents and materials may not be used or sold by the Contractor without written permission from the Contracting Officer.

2.16.5 All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

2.17 Training and Training Support

2.17.1 The Contractor shall plan, resource, and implement a cohesive integrated strategy to train personnel to operate and maintain the equipment throughout the equipment lifecycle.

2.17.2 The Contractor’s integrated training strategy shall effectively utilize, as required:

1. On-the-Job Training (OJT)

2. Proficiency Training

3. Formal and Informal Classroom Instruction

4. Sustainment Training

5. Train-the-Trainer

2.17.3 The Contractor shall ensure all applicable maintenance and operations personnel are trained and proficiency qualified on at a minimum:

1. Theory of Operation

2. Troubleshooting/Fault Isolation

3. Remove and Replace (LRUs)

4. Power Up/Power Down - Component

5. Power Down - as a system

6. Reparable/Non-repairable (LRUs)

7. Interconnects

8. Calibration

9. Equipment Operation

2.17.4 The Contractor shall update RFS site training materials for each deployment site as required. Post updated training materials NLT 30 calendar days prior to SDRRs/TRRs as required. [DAL]

2.17.5 The Contractor shall conduct site training as required for maintainers and operators using training materials in the current first site RFS project as modified for the unique aspects of each follow-on site.

3 GOVERNMENT FURNISHED PROPERTY (GFP). Government Furnished Property (GFP) is the property in possession of the, or directly acquired by, the Government, and subsequently furnished to the contractor for performance of a contract. GFP includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. GFP also includes contractor acquired property (CAP) if the CAP is a deliverable under a cost contract when accepted by the government for continued use under the contract. If required, the Government will provide GFP via the GFP Module within the Procurement Integrated Enterprise Environment (PIEE).

3.1 PIEE GFP Module.

3.1.1 If GFP is required, the contractor will be provided a listing of all GFP identifying all serial and non-serial GFP transferring under the contract.

3.1.2 The Contractor shall establish GFP Module roles of Contractor Property Receiver and Contract property Shipper. These roles will allow the contractor to receive property transfer notifications, acknowledge receipt of GFP in compliance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7007 and AFI 23-119, send GFP property transfers and provide the contractor access to fully approved GFP attachment(s) in the Electronic Document Access (EDA) and GFP Module. The GFP Module may be accessed via the following link:

https://safe.menlosecurity.com/doc/docview/viewer/docNDA86D34A50CB1461f11ba735906e351692d45894c27fdaf59dbbd5eca253c469b88e726325f0

3.1.3 After the contractor physically receives GFP under this SOW, the contractor shall:

3.1.3.1 Acknowledge receipt of GFP in the PIEE GFP Module IAW DFARS 252.211-7007

3.1.3.2 Identify any shipping discrepancies in an MFR: send to the Government and retain as Key Supporting Documentation (KSD)

3.1.3.3 Record the information necessary to meet the record requirements of FAR 52.245-1(f) (1) (iii) (A) (1) through (10).

3.1.3.4 Identify GFP as Government owned in a manner appropriate to the type of property (e.g., stamp, tag, mark, or other identification).

3.2 Government furnished information (GFI). GFI may be required during performance of this requirement. Examples of GFI to be provided may include previous Government analyses and studies, USAF/USSF policy and guidance, DoD Security Classification Guides (SCGs), operational plans, and other references and sources that may be necessary to effectively perform analyses or other tasks. When required, contractor shall request GFI via the Contracting Officer Representative (COR) or designee and shall protect such information according to any applicable restrictions. Specific examples include existing RFS Level III TDP and Operational Acceptance Report, facility access, etc.

APPENDIX A – Terms and Definitions Business Day. Unless specified otherwise for specific sites, a Business Day is Monday through Friday, except for Federal Holidays. The following Federal Holidays observed under this contract.

*If date falls on weekend, the holiday is observed on the day the Government observes the holiday Contracting Officer (CO). Designated by the Department of Air Force (DAF) to direct/redirect the efforts of the Contractor or modify any of the Items of the contract.

Contracting Officer Representative (COR). Appointed Government representative responsible for monitoring, evaluating, and reporting Contractor performance of the contract. The COR interfaces with the customer, contractor, and SPO.

Contractor’s Program Manager. Serves as the focal point between the SPM and the company’s management regarding all issues and discrepancies. Ensures full compliance with the terms and conditions of the contract and has primary responsibility for the performance of this requirement. Identifies the focal point responsible for day-to-day communication with the COR.

Core Hours. Business days between 7:30 A.M. through 4:30 P.M. Mountain Standard Time.

Government System Program Manager(SPM). Provides primary program oversight and management of the requirement.

Integrated Product Team (IPT). Team is composed of representatives from appropriate stakeholders, organizations, and functional disciplines working together to seek opportunities for improvements, identify and resolve issues, and make sound and timely recommendations to facilitate decision making.

Stakeholder. Any individual, group, or organization who may affect, be affected by, or perceives itself to be affected by the contract. This includes people who are users, providers, influencer, funders, or governance of the systems.

Systems Program Office (SPO). Supports the SPM in execution of the requirement.

APPENDIX B – Acronyms & Definitions

image1.png image2.png