Attachment 1 - Basic Contract PWS.pdf

Performance Work Statement (PWS) Atmospheric Early Warning System (AEWS) Long Range Radome Replacement Program

Prepared By:

AFLCMC/HBDIA

Program Management Office (PMO) Hill AFB, Utah

Version: 1.0

Last Updated: 29 July 2025

Table 1 - Post Award Changes Initiator Rev# Date Change Summary

Contents

1.0 Overview

1.1 Background

1.2 Scope

1.3 Contractor Responsibilities

1.4 Type of Contract

1.5 Item Description

1.6 Technical Orders (T.O)

1.7 Guidance Documents

2.0 General Requirements

2.1 Small Business Subcontracting Plan:

2.2 Security Requirements

2.2.1 Non-Disclosure Agreements (NDA)

2.2.2 Protection of Information

2.2.3 Reporting Requirements

2.2.4 Security Incidents and Violations

2.2.5 Security of Contractor Systems

2.2.6 Confidentiality of Information

2.2.7 Foreign Disclosure

2.2.8 Counterfeit Prevention Plan

2.3 Environmental Protection, Labor, Health and Safety Requirements

2.3.1 Environmental, Safety, And Occupational Health (ESOH)

2.3.2 Canadian Occupational Health, Safety, and Labor

2.3.3 United States-Mexico-Canada Agreement (USMCA)

2.3.4 Voluntary Protection Program (VPP)

2.4 Manpower Reporting

2.4.1 Sub-Contractor Management

2.4.2 DOD SAFE

2.4.3 CONUS and OCONUS Travel:

2.5 Theater Operations and Support

2.5.1 Equipment and Preparation

2.5.2 Alaska Theater (ARS)

2.5.2.1 Site Arrival Requests (Alaska)

2.5.3 Canadian Theater (NWS)

2.5.3.1 Canadian Theater Transportation

2.5.4 Mount Koke’e Hawaii Theater

2.6 CDRL Approval Process

2.6.1 Definition of Accepted, Approved and Rejected

2.6.2 Government CDRL review process

2.6.3 Discrepancies

2.7 Corrective Actions

3.0 Work Performance Requirements

3.1 Radome Manufacturing, Installation, Technical Data, and Training

3.1.1 Program Management

3.1.1.1 Meetings 13

3.1.1.1.1 Kick-off Meeting

3.1.1.1.2 Status Meeting (Monthly)

3.1.1.1.3 Impromptu Meetings

3.1.1.2 Program Studies and Reports

3.1.1.2.5; Contract Funds Status Report

3.1.1.2.2 Integrated Master Schedule (IMS)

3.1.1.2.3 Monthly Status Report (MSR)

3.1.1.2.4 Requirements Traceability Verification Matrix (RTVM)

3.1.1.2.5 Radar Protection Plan

3.1.1.2.6 Site Survey Report

3.1.1.2.7 Engineering Change Proposal (ECP)

3.1.2 Spare Materials

3.1.3 Storage

3.1.3.1 Disposition:

3.1.3.1.1 Retention for Future Projects:

3.1.3.1.2 Transfer to Theater Locations

3.1.4 Radome Assembly and Accessory Production and Shipping

3.1.4.1 Factory Acceptance Test and Report

3.1.4.2 End Item Acceptance Test and Checkout Report

3.1.4.3 Radome Assembly Packaging

3.1.4.3.1 Radome Packaging Requirements

3.1.4.3.2 International Standards for Phytosanitary Measures (ISPM NO. 15) Requirements

3.1.4.3.3 Nameplates and Product Markings

3.1.4.3.4 IUID Submittal

3.1.4.3.5 Spares Hazardous Materials (When Applicable)

3.1.4.4 Technical Data Package

3.1.4.4.1 Commercial Engineering Design Data and Associated Lists

3.1.4.4.2 Special Inspection Equipment (SIE)

3.1.4.4.3 Special Tooling

3.1.4.4.4 Commercial Item Description (CID)

3.1.4.4.5 Special Packaging Instructions (SPI) Engineering Design Data and Associated Lists

3.1.4.4.6 Quality Assurance Provisions (QAPs)

3.1.4.4.7 Technical Data Package Lists (TDPL)

3.1.4.4.8 Engineering Drawing Tree

3.1.4.5 Commercial Off The Shelf Manuals

3.1.4.5.1 Technical Order Guidance Conference (TOGC)

3.1.4.6 Training and Training Materials

3.1.5 Radome Shipping, Handling, Transportation, and Disposal

3.1.5.1 Transportation Mode Selection

3.1.5.2 Safety And Security Requirements

3.1.5.3 Coordination With Government Agencies

3.1.5.4 Canadian Shipments

3.1.5.4.1 Canadian Documents and Markings

3.1.6 Storage Requirements

3.2 Radome Disassembly and Assembly

3.2.1 Material Receiving Inspection

3.2.2 Radar and Facility Protection

3.2.3 Legacy Radome Disassembly

3.2.3.1 Damage Inspection

3.2.4 Composite Radome and Accessories Installation

3.2.5 Composite Radome Acceptance Test

3.2.5.1 Contractor Test

3.2.5.2 Site Acceptance and Site Acceptance Test Report

3.2.6 Contractor Warranty and Liability

3.2.6.1 Government Testing And Verification

3.2.6.2 Correction Of Defects

3.2.6.3 Notification And Correction Process

3.2.7 Legacy Radome Material Disposal and Removal

3.2.7.1 Removal from Canada

3.2.7.2 Disposal Requirements

3.2.7.3 Scrapping and Disposal

3.2.7.4 Storage and Transportation

3.2.7.5 Proposal and Approval

3.2.7.6 Payment Withholding

3.3 Over and Above

3.3.1 Over and Above Work Request

4.0 Data Deliverables

4.1.1 OPSEC Plan, CDRL-A001, TO-YRXXX, Rev XXX

4.1.2 Counterfeit Prevention Plan (CPP), CDRL-A002, Task Order XXXX

4.1.3 Contract Funds Status Report (CFSR), CDRL-A003, TO-YRXXX, Rev XXX

4.1.4 Radar Protection Plan (RPP), CDRL-A004, TO-YRXXX, Rev XXX

4.1.5 Presentation Material, CDRL-A005, TO-YRXXX, Rev XXX

4.1.6 Meeting Agenda, CDRL-A006, TO-YRXXX, Rev XXX

4.1.7 Meeting Minutes, CDRL-A007, TO-YRXXX, Rev XXX

4.1.8 Requirements Traceability Verification Matrix (RTVM), CDRL-A008, TO-YRXXX, Rev XXX

4.1.9 Integrated Master Schedule (IMS), CDRL-A009, TO-YRXXX, Rev XXX

4.1.10 Monthly Status Report (MSR), CDRL-A010, TO-YRXXX, Rev XXX

4.1.11 Accident/Incident Report, CDRL-A011, TO-YRXXX, Rev XXX

4.2 Site Survey Report, CDRL-A012, TO-YRXXX, Rev XXX

4.3 Engineering Change Proposal (ECP), CDRL-013, TO-YRXXX, Rev XXX

4.4 Technical Data Package (TDP), CDRL-A014, TO-YRXXX, Rev XXX

4.5 Commercial Off The Shelf Manuals, CDRL-A015, TO-YRXXX, Rev XXX

4.6 Acceptance Test and Checkout Report, CDRL-A016, TO-YRXXX, Rev XXX

4.7 Safety Data Sheet (SDS) Report, CDRL-A017, TO-YRXXX, Rev XXX

4.8 Training Materials, CDRL-A018, TO-YRXXX, Rev XXX

4.9 Non-Disclosure Statements, CDRL-A019, TO-YRXXX, Rev XXX

5.0 Service Summary

6.0 Appendices

6.1 Attachments

6.1.1 Long Range Site Locations and Addresses

6.1.2 Comments Resolution Matrix (PWS 2.7)

6.1.3 Memorandum For Alaska Radar System Support

6.1.4 Pacific Regional Site Access Request (SAR)

6.1.5 Customer Support Request – Third Party Request

6.1.6 Notional Schedule

6.2 Appendix B – ARS Alaska Site Map

6.3 Appendix C – North Warning System (Canada) Map and Legend

6.4 Appendix D – Acronyms

LIST OF TABLES

TABLE 1 - POST AWARD CHANGES 2

TABLE 2 – GOVERNMENT SUPPLIED TECHNICAL ORDERS 7

TABLE 3 - KICK-OFF MEETING 14

TABLE 4 - MONTHLY STATUS REPORT 16

TABLE 5 - SITE SURVEY REPORT 17

TABLE 6 - DATA DELIVERABLES 27

1.0 Overview

This is a supply and services contract that outlines the processes, tasks and duties required of the Contractor on behalf of the United States Air Force Atmospheric Early Warning System (AEWS) Program Management Office

(PMO)

1.1 Background

The Alaska Radar System (ARS) spans throughout the state of Alaska, and the North Warning System (NWS) consists of a sequence of radar sites operating across the northern and eastern coasts of Canada; from the Yukon in the west to the southern Labrador coast in the east. Each site houses an FPS-117 Radar System Antenna. Each antenna is protected by multiple configurations of radomes and towers. Most radomes have an expected life cycle of 20 years. However, many of the USAF radomes are approaching 30 years of installed life and are experiencing serious panel decay. The decay will eventually impact operational availability of the FPS-117 radar, and by extension the entire site if the antenna is damaged due to exposure to the elements.

1.2 Scope

The Contractor shall furnish all facilities, parts, materials, equipment and services, necessary to manufacture, transport, remove, install and dispose of 27 Long-Range Radomes, fifteen (15) in Alaska United States, ten (10) in Canada, one (1) in Utah, and one (1) in Hawaii. Work performed under this contract shall be indefinite for the period of 7 years and 6 month option

1.3 Contractor Responsibilities

The Contractor shall exercise management, operational control, and retain full responsibilities for performance requirements set forth in this PWS, applicable paragraphs, and applicable clauses in the contract and specific requirements defined in accepted Task Orders.

1.4 Type of Contract

This contract consists of Firm Fixed Price (FFP) Contract Line-Item Number (CLINs) for material purchases, Cost Reimbursable No Fee (CRNF) for Travel CLIN, and Cost-Plus Fixed Fee (CPFF) for Over & Above (O&A) CLINs.

1.5 Item Description

A structural, weatherproof enclosure that protects a radar antenna. The composite radome is constructed of composite material transparent to radio waves electromagnetic signals. Composite designs to be utilized to withstand severe weather conditions withstanding snow loads, salt spray, and extreme temperatures.

1.6 Technical Orders (T.O)

Government supplied Technical Orders and Technical Manuals, reference Table 2

Table 2 – Government Supplied Technical Orders

T.O. Title 31P1-2GPS-14 Illustrated Parts Breakdown, Radome CW-396A/GPS 31P1-2GPS-15 Installation Instructions, Rigid Radome, CW-396A/GPS, CW- 396B/GPS 31P3-2FPS6-232-7 Installation Instructions, Tower, AB-259/FPS-6 31P6-2FPS3-375 Installation Instructions, Arctic Tower, AB-199A/FPS-3 (Koke’e Only) TM 87-13 (COTS) ESSCO Model M55-70-9100 Radome

1.7 Guidance Documents

• Engineering Specification for the AN/FPS-117 Radar Radome (Document No.: 20250725 CAGE: 98747)

• AB-199 Drawings

• AB-259 Drawings

Arctic Tower Drawings

• TM ESSCO Shell Radome Type S27-82

• S-7078-2 Base Mounting Ring Layout (55’ Radome)

2.0 General Requirements

The Contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS for the duration of the period of performance. The Contractor shall achieve a complete, effective, structured preventative maintenance program for the AN/FPS-117 Radar System and Subsystems. The Contractor shall comply with all country, federal, state, local, industry, installation, and national codes.

With the exception of any government furnished property identified elsewhere within this PWS, the Contractor shall provide everything needed to accomplish PWS requirements (e.g - office and lab space, office equipment [desks, chairs, etc.] and supplies, computer equipment/software [desktop and/or laptop], telephones and telephone services [including the DSN service], internet services, and reproduction facilities (except those required for producing specific training manuals or materials). All materials purchased by the Contractor for the use or ownership of the Federal Government, becomes the property of the Federal Government. The transfer of materials shall be documented by the Contractor in the Monthly Status Report. The Contractor must furnish the COR copies of such documents monthly, through E-mail (CDRL A010, DI-MGMT-80368)

2.1 Small Business Subcontracting Plan:

If the awardee is a large business, the Contractor shall submit a small business subcontracting plan

2.2 Security Requirements

The Contractor shall comply with the contract security requirements identified in the following subparagraphs. The Contractor shall pass down tailored security requirements, as stated in the contract, to all Subcontractors. The Contractor shall comply with the requirements outlined in the Visitors Group Security Agreement and industrial security tenets as outlined in DoDM 5220.22V2_AFMAN 16-1406V2, National Industrial Security Program:

Industrial Security Procedures for Government Activities.

The Contractors performing duties associated with this contract must adhere to all the standards for protecting classified information as specified in DoDM 5200.01-AFMAN 16-1404, Vol 1-3, Air Force Information Security Program, and all applicable supplements and operating instructions.

2.2.1 Non-Disclosure Agreements (NDA)

IAW FAR 9.505-4(b) the Contractor is responsible for obtaining all Non-Disclosure Agreements (NDAs) with all applicable Government, corporate, supplier, and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted, e.g., non-foreign disclosure due to public law, data that will be used or accessed during the execution of this contract. Note: This is to be completed prior to contract performance for all applicable locations and if the Contractor is required to interact with foreign partners of the United States on programs, the Contractor shall comply with all regulations pertaining to that interaction to include filing for appropriate export licenses or exemptions. The Contractor shall use the Government approved NDA form and provide to the COR two (2) calendar days prior to the initial Kick-Off Meeting. (CDRL A019, DI-MGMT-82241)

2.2.2 Protection of Information

Controlled Unclassified Information (CUI) is any information that law, regulation, or Government wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

The National Archives and Records Administration Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.

The Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information, AFI 16-1404 Air Force Information Security Program, and Air Force Guidance Memorandum 2020-16-01, Air Force Guidance Memorandum for CUI, 23 July 2020. The Contractor will consult the applicable security classification guide to monitor CUI aggregation for potentially generating classified information by compilation.

The Contractor shall comply with DoDM 5400.7/Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program, requirements.

https://static.e-publishing.af.mil/production/1/saf_aa/publication/dodm5220.22v2_afman16-1406v2/dodm5220.22v2_afman16-1406v2.pdf http://www.archives.gov/cui/registry/category-list.html http://www.archives.gov/cui/registry/category-list.html

Protection of CUI and unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems must be protected using the guidelines set forth in NIST Special Publication 800-171, Operations Security (OPSEC)

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. Critical information is defined as information about USAF missions or activities the adversary needs to achieve their goals. The Contractor shall ensure compliance with DoDD 5205.02E, DoDM 5205.02-M, AFI 10-701 and/or other applicable Government security regulations including procedures to protect classified and/or CUI, Government projects and/or programs. The Contractor shall ensure Contractor personnel who perform work in geographically separated locations, or another Government facility comply with the OPSEC procedures of the facility. The Contractor shall implement security requirements as listed in the unit’s OPSEC Plan, which will be provided as Government furnished information. Contractors will also receive a local threat briefing from the sponsoring organization as required. (CDRL A001, DI-MGMT-80934)

2.2.3 Reporting Requirements

The Contractor shall immediately report to an appropriate Government authority any information or circumstances of which they are aware of that may pose a threat to the safety and/or security of DoD personnel, Contractor personnel, resources and classified or controlled unclassified information.

The Contractor shall immediately notify the Government security manager, and Contracting Officer of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified and/or CUI or arrests.

All unclassified/classified security infractions/incidents will be reported to the assigned Division Security Office, to include any adjudicated reported offenses within the Insider Threat Program covered under DODMAN-AFMAN

5200.02 16-1405 Air Force Personnel Security Program, AFI 16-1402, Insider Threat Program Management and Security Executive Agent Directive (SEAD)-4, National Adjudicative Guidelines.

2.2.4 Security Incidents and Violations

The Contractor shall notify the CO and the AEWS Program Management Office (PMO) Security Manager within twenty-four (24) hours of any incident involving the actual or suspected compromise/loss of United States Government (USG) classified information, security violations, security incidents, or of any indication of a potential unauthorized disclosure to enable the USG to conduct immediate assessments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.204-7012. The Contractor shall use the appropriate Information System to send reports for security incidents.

2.2.5 Security of Contractor Systems

The Contractor shall ensure the security of automated information systems at The Contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified and/or controlled unclassified information.

2.2.6 Confidentiality of Information

Unless otherwise specified, all financial, statistical, personnel, and/or technical data furnished, produced, or made available to the Contractor during the performance of this contract is considered confidential business information and shall not be used for purposes other than performance of work under this contract.

2.2.7 Foreign Disclosure

Export of technical information to Canadian personnel shall be governed by Secretary of the Air Force (SAF)/International Affairs Policy Division (IAPD) issued Delegation of Disclosure Letter (DDL). Export to foreign persons must be in compliance with the International Traffic in Arms Regulations (ITAR), and will typically be secured by obtaining United States (US) State Department authorization (export license or agreement) or meeting the conditions of ITAR exemptions such as 22 Code of Federal Regulations (CFR) 125.4(b)(3) or 22 CFR

126.6(c)(7), allowing release based on services required in performance of a DoD contract in support of sales made in accordance with a Foreign Military Sales (FMS) case LOA.

2.2.8 Counterfeit Prevention Plan

Contractors that supply systems, equipment, spares, repair, and replacement parts for High Reliability systems to the Department of Defense (DOD) shall establish policies and procedures to avoid, detect, mitigate and dispose of counterfeit parts to prevent such parts from entering the USAF/DoD. These policies and procedures shall be documented in a Counterfeit Prevention Plan (CPP) for submission and approval in accordance with (CDRL A002, 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 SAE AS5553, Aerospace Standard, Counterfeit Electronics Parts;

Avoidance, Detection, Mitigation, and Disposition shall apply.

2.3 Environmental Protection, Labor, Health and Safety Requirements Work performed by the contractor shall comply with all applicable federal, state, providence, territory, jurisdiction, and local regulations regarding occupational safety and health.

2.3.1 Environmental, Safety, And Occupational Health (ESOH)

The Contractor responsible for compliance with all federal, state and local laws. The Contractor shall comply with Public Law 91-596 Occupational Safety and Health Act (OSHA) and the DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH). These requirements shall be incorporated into the Contractors safety and health program. Additionally, The Contractor is responsible for the safety and health of all sub-contractor's employees during the performance of this contract.

2.3.2 Canadian Occupational Health, Safety, and Labor

The Contractor is responsible for compliance with all Canadian Jurisdictions; federal, province and local laws.

Contractor shall comply with Occupational Health and Safety Act, R.S.O. 1990, c. O.1 and Canada Labour Code (R.S.C., 1985, c. L-2). These requirements shall be incorporated into the Contractors safety and health program.

Additionally, The Contractor is responsible for the safety and health of all sub-contractor's employees during the performance of this contract.

2.3.3 United States-Mexico-Canada Agreement (USMCA)

The Contractor will be engaged in work that requires entry into Canada. Employers accessing the sites from the United States or other foreign locations will be required to obtain Temporary Work Permits IAW the USMCA.

Additionally, all labor, rights, exports, imports, goods and services are subject to provisions, taxes, and tariffs IAW the USMCA https://ustr.gov/trade-agreements/free-trade-agreements/united-states-mexico-canada-agreement/agreement-between

2.3.4 Voluntary Protection Program (VPP)

The Air Force is part of OSHA’s VPP. All Contractors are required to familiarize themselves with the requirements of VPP. Information on VPP can be accessed at http://www.osha.gov. The intent of the Air Force Safety Program is to prevent injuries and to communicate our safety expectations with potential offers as well as those Contractors awarded a government contract. The Air Force’s interest is to protect personnel working in or around Contractor operations, and to protect Air Force equipment/property.

2.4 Manpower Reporting

The Contractor shall perform administrative, technical, financial management, and Contractor Manpower Reporting Application (CMRA) reporting (IAW Title 10, USC, Section 235 and 2330a) functions during the performance period of this contract and shall maintain a status of effort towards achieving the objectives, including all technical activities, problems/deficiencies, impacts, and recommended solutions. The Contractor shall report all Contractor labor hours (including sub-contractor labor hours) required for performance of services provided under this contract for the United States Air Force via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: https://sam.gov/content/home. Reporting inputs will be for the labor executed during the period of performance during each Government Fiscal Year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013.

https://ustr.gov/trade-agreements/free-trade-agreements/united-states-mexico-canada-agreement/agreement-between https://ustr.gov/trade-agreements/free-trade-agreements/united-states-mexico-canada-agreement/agreement-between

2.4.1 Sub-Contractor Management

The Contractor may subcontract with other companies to establish a strong technical capability to meet diverse contract requirements. However, the prime Contractor shall be responsible for all aspects of the contract performance (i.e., the technical/administrative data approval), oversight, and the flow of all the requirements to all the sub-contractors, Service Agreements and Work Agreements.

2.4.2 DOD SAFE

In the event where necessary, to safely Encrypt and transmit CUI, PII, or PHI files, the Department of Defense (DoD) Secure Access File Exchange (SAFE) may be utilized by Government and Contractor. https://safe.apps.mil/

2.4.3 CONUS and OCONUS Travel:

CONUS and OCONUS location travel costs shall be IAW the Federal Acquisition Regulation (FAR) 31.205-46. No profit or fee will be paid in support of this CLIN. Travel expenses may include the following: Air Fare is Coach, and Rental Car is Economy. Airfare for travel and Per Diem shall be billed IAW Federal Acquisition Regulations (FAR) (available at https://www.acquisition.gov/browse/index/far). Per Diem rates can be found at http://www.defensetravel.dod.mil/site/perdiemCalc.cfm. The Contractor is responsible for making all necessary travel arrangements. The Contractor shall minimize Government expense by consolidating services at sites located in the same geographic area, whenever possible. Contractor shall annotate travel costs for each travel effort within the Contractor Funds Status Report (CFSR) reporting all travel hours and expenses to include, at minimum, airfare, rental cars, any additional transportation costs, taxes, fees, and lodging incurred (while traveling). (A003, DI-

MGMT-81468)

2.5 Theater Operations and Support

The locations of sites are very remote and have very extreme climates. Work performed at these locations require support and coordination with the PMO, Pacific Regional Support Center (PRSC) Alaska, Canadian Department of National Defence, and Operations and Maintenance (O&M) Contractors within their respective theaters. For Alaska, the contractor may choose to subcontract with the O&M contractors, coordinate Memorandum of Understanding (MOU) or submit for BOS contractor support. In Canada, Third Party Requests are necessary to perform work as defined within the Canadian Theater.

Prior to work at each site, the contractor must coordinate an O&M Escort who will bear responsibility to secure and monitor manpower during any labor period at each required site. Additionally, an O&M Electronic Maintenance Technicians (EMT) will need to be coordinated prior to shutting down and restoring each radar and communication system. The contractor shall ensure safety, wildlife monitor, transportation, communications personnel as well as lodging and meals are carefully coordinated and planned for prior to commencement of work within the respective theater.

2.5.1 Equipment and Preparation

Due to the uniqueness of each geographical radar site and operational theater requirements, GFE may be located within reason at each site, however it is the responsibility of the Contractor to verify that GFE is available to support all efforts defined within this PWS prior to work. The contractor shall be responsible to validate the necessary scaffolding, ground transportation, manlifts, and electrical outlets necessary to complete installation efforts at each site, to include validation of electrical load, phase, wattage, hertz and outlet position for each site. The contractor shall provide advanced notice of at least ninety days for tools and equipment needs for each site as well as bear responsibility to pre-position the equipment at each site prior to commencement of work. The contractor shall be responsible for pre-positioning of cook camps, meals, tools, and the logistics of install team movement. The contractor shall supply all tools as specified in the contractor's installation manual to complete the installations. The contractor shall coordinate with the O&M contractor for GFE helicopter or fixed wing support required (if available) to support pre-positioning (scaffolding, camp, tools, etc.), team mobilization/demobilization, and sustainment during installations.

2.5.2 Alaska Theater (ARS)

For tasks in the Alaska theater, the Contractor must coordinate with the Operations & maintenance Contractor, currently “Arctec Alaska”, with coordination with the Base Operations Support (BOS). Coordination shall be made with Mr. Mitch Rohloff, Mitch.Rohloff@arctecalaska.com, 907-552-2162, of ARCTEC Alaska prior to arrival.

https://safe.apps.mil/ https://www.acquisition.gov/browse/index/far http://www.defensetravel.dod.mil/site/perdiemCalc.cfm

ARCTEC may establish a direct purchase order to provide support for services. See Appendix 5.1.2 attachment “Memorandum For Alaska Radar System Support” for more information.

2.5.2.1 Site Arrival Requests (Alaska)

Visitors shall be processed through a Site Arrival Request (SAR). All visiting personnel are required to be favorably vetted by the PRSC Security Team prior to arrival at the site, without exception. See Appendix D attachments “PACAF Regional Support Center Site Arrival Request (SAR)” Attachment 5.1.3

2.5.3 Canadian Theater (NWS)

For tasks in the Canadian theater, the Contractor must coordinate with the Department of National Defence and Operations & maintenance Contractor, currently “Nasittuq Corporation”. For theater/site support the contractor shall submit a “Third Party Support Request Form” Attachment 5.1.4.

2.5.3.1 Canadian Theater Transportation

The contractor shall be responsible for all non-GFE logistics associated with the transportation of the radomes from the manufacturing facility to sites and disposal locations. This includes, but is not limited to storage, scheduling, sea lift, and ground support. GFE helicopter and/or fixed winged transport, if necessary, will require coordination by submitting a Third-Party Request to the Canadian Department of National Defence and Nasittuq.

2.5.4 Mount Koke’e Hawaii Theater

For site support within the Mount Koke’e Hawaii Theater contact the PMO for coordination. The “PACAF Regional Support Center Site Arrival Request (SAR)” Attachment D, applies for Mount Koke’e site entry.

2.6 CDRL Approval Process

Each CDRL required specifies when the delivery is due. The Contractor shall comply with all defined delivery timelines. The Contractor shall ensure all CDRL deliveries comply with the CDRLs associated Data Item Description (DID). In some instances, this PWS requires extra data/details associated with a CDRL delivery and The Contractor shall incorporate the extra data/details as defined by this PWS or the Task Order PWS. If a CDRL is rejected by the government, The Contractor shall have ten (10) business days to correct or adjudicate the comments and re-deliver the CDRL. If The Contractor determines that if the complexity of the deliverable or number of comments require more than ten (10) business days, then the Contractor shall request an extension providing detailed reasons as to why an extension is needed and a proposed completion date to the PMO PM for consideration and approval. The Contractor shall make that request within five (5) business days of receiving the rejected deliverable.

2.6.1 Definition of Accepted, Approved and Rejected

CDRL deliverables can quickly hinder a programs ability to progress from one milestone to the next and it is imperative that the government and Contractor use the same terminology to understand the status of a CDRL delivery.

• Accepted – The meaning of accepted is the CDRL met the DID and PWS requirements only. The format is accepted only.

• Approved – The meaning of approved is the CDRL met the DID and PWS requirements and the content of the

CDRL in its current version is approved for format and content by the government.

• Approved Final – The meaning of approved final is the CDRL has met the DID and PWS requirements and the content of the CDRL is sufficient in its current version to be considered a final approved CDRL by the government and does not require any further updates.

• Rejected – The CDRL deliverable is not approved. A Rejected CDRL will be returned to The Contractor with a standardized government comment resolution matrix form and/or red line mark ups/comments within the document that require corrections/adjudication from The Contractor.

If something within the program changes that requires the approved final CDRL to be updated, then The Contractor shall inform the government. The Contractor and the government will discuss and agree to an approved re-delivery timeline for review and the CDRL will require another Approved Final prior to considering the CDRL successfully met.

2.6.2 Government CDRL review process

The government shall have thirty (30) calendar days or twenty (20) business days whichever is greater to review and provide comments or a decision to The Contractor using terminology previously defined. Most CDRLs will have an initial, subsequent, and final delivery.

A CDRL on Initial delivery will first be reviewed to ensure they meet the DID and PWS requirements and if they do the CDRL will be identified as Accepted. If the CDRL is not acceptable, then it shall be rejected for corrections as previously defined.

A CDRL on subsequent delivery will be reviewed for content only if it has already been identified as accepted. If the content is considered sufficient based on the timing of the program it will be identified as accepted or accepted final.

If the CDRL is not acceptable, then it shall be rejected for corrections as previously defined.

A CDRL on final delivery will be reviewed for content only if it has already been identified as accepted. If the content is considered sufficient then the CDRL can be identified as accepted final. If the CDRL is not sufficient then the CDRL will be identified as rejected for corrections as previously defined.

2.6.3 Discrepancies

In case of conflict between this document and any referenced document, contact ACO & PCO for resolution of discrepancy.

2.7 Corrective Actions

In the event Contractor is determined not to perform to the scope of this contract and/or task order, the Government may submit a Comments Resolution Matrix (CRM) to the contractor describing Administrative, Substantive, or Critical issues for non-conformance of tasks the contractor may be responsible or culpable for. An example CRM can be found under Attachments 5.1.2. Upon investigation, the Government may submit a Corrective Action Request (CAR) Non-Conformance Report to the Contractor describing the details, objective evidence, and corrective actions required. The contractor shall submit a Corrective Action Plan in response to the CRM or CAR no later than fifteen

(15) calendar days after receipt.

3.0 Work Performance Requirements

3.1 Radome Manufacturing, Installation, Technical Data, and Training Contractor shall perform all work performance requirements as outlined to complete the removal of legacy radomes and the manufacturing and installation of new Radomes.

3.1.1 Program Management

The Contractor shall designate a prime and alternate Program Manager through the period of this contract. The Program Manager shall be responsible for the daily operations of the contract. The Program Manager or alternate shall be available during administrative duty hours. A PM is responsible for overseeing and leading a group of related projects, typically within the context of a program. The contractor designated Program Manager will be responsible for overseeing the development and execution of program plans and strategies, coordinating resources, schedules, and budgets across multiple projects, monitoring and reporting on program progress to the government and stakeholders, while managing risks and issues across the program, facilitating communication and collaboration between different project teams and stakeholders. The PM shall ensure that program milestones and deliverables are met, managing program budgets and costs, and ensure compliance with relevant regulations and standards. The Program Manager will be responsible for generating various documents and artifacts, such as program plans, program or project progress reports, status reports, program risk and issue logs, program schedules, and program budgets. These documents and artifacts are used to communicate the status, progress and performance of the program to government stakeholders, as well as to manage and coordinate resources, schedules, and budgets pertaining to the Radome replacement program.

3.1.1.1 Meetings

The Contractor shall support and respond to all meetings defined within this PWS. Where practical, meetings between the Contractor and Government teams shall be combined to minimize number of meetings. For all meetings, the contractor shall take meeting minutes (CDRL A007, DI-ADMN-81250)

3.1.1.1.1 Kick-off Meeting

Program Kick-off meetings are essential as they signify that the project/program has formally started. This provides the opportunity for all parties to get to know each other, build trust and promote mutual understanding. The kick-off meeting will provide the opportunity for The Contractor to address aspects of the program as an overview to ensure a thorough understanding of the program and associated risks. The Contractor shall convene a Kick-off meeting no later than (NLT) thirty (30) calendar Days After Contract Award (DACA) at a mutually agreed upon location. The Contractor shall meet minimum entrance and exit criteria for the Kick-off Meeting as defined in the individual Task Order. Table 3- Kick Off Meeting provides a simplified template that may be expanded or reduced if mutually agreed upon by the Contractor and Government.

Table 3 - Kick-off Meeting

Kick-off Meeting CDRL CDRL Name POP A005 Presentation Material (DI-ADMN-81373 NOT 2) As defined in Task Order A006 Meeting Agenda (DI-ADMN-81249C) As defined in Task Order A008 Requirements Traceability Verification Matrix (DI-MGMT-

82133 NOT 1)

As defined in Task Order

• Kick-off Meeting shall cover the following:

• Program Overview o Purpose of the Kick-off Meeting o Contract Overview o Program Milestones o CDRLs o Program Risk Management.

• System Requirements Review

• Contractors’ system requirements are traced to all contractual government system requirements.

• All Contractor’s system requirements and performance requirements are defined, verifiable, and derived from government system requirements and are consistent with the preferred system solution as well as available technologies.

• System performance, cost (program budget) schedule, risk, and other system constraints are within scope and understood.

• System technical risks are identified, documented, understood, and manageable for development and system risks and/or mitigation plans are acceptable to the government.

• Approved Contractor’s system performance requirements and specification.

• Adequate process and metrics in place for program success.

• Program schedule is executable.

• Program is properly organized and staffed.

• Program is executable within the existing budget.

• Technical Overview of:

o Assembly/Disassembly Protection Plan o Requirements Traceability Verification Matrix (RTVM) o Radar Protection Plan o Site Survey and Installation Plan o Technical Milestones o Schedule (IMS) o Conceptual Designs o Technical Manuals o Manufacturing o Transportation o Installation Process o Shipping, Handling, Transportation, and Disposal

3.1.1.1.2 Status Meeting (Monthly)

The Contractor shall host one (1) Status Meeting monthly via Microsoft Teams, phone, or in person on a mutually agreed upon date. A Status Meeting may take the place of an Impromptu meeting if agreed to by Government PM or COR. Topics for the Status Meeting shall cover no less than the Integrated Master Schedule (IMS), items within the Monthly Status Report (MSR) and CDRL/ Deliverables. The following deliverables shall be supplied to the government as defined within. (CDRL-A005 DI-ADMIN-81373), (CDRL-A006 DI-81249), (CDRL-A007 DI-

ADMN-81250C)

3.1.1.1.3 Impromptu Meetings

The Contractor shall support impromptu meetings requested by the Government. Impromptu meeting(s) shall occur within three (3) business days of the request unless mutually agreed upon by the Government and Contractor.

(CDRL-A007 DI-ADMN-81250C)

3.1.1.2 Program Studies and Reports

Upon receipt of Order, Contractor shall perform all technical studies for work performance requirements

3.1.1.2.1 Contract Funds Status Report

The Contractor shall prepare and submit a monthly Contract Funds Status Report (CFSR) for each task order, outlining the current status of funding for each task. The Contractor shall submit the monthly CFSR no later than the 10th calendar day of each month, for the previous month's activity. The Contractor shall submit the monthly CFSR in an Excel spreadsheet format, with each task order listed in a separate tab within the spreadsheet and ensure that the information provided is accurate, complete, and up to date. (CDRL A003 DI-MGMT-81468)

3.1.1.2.2 Integrated Master Schedule (IMS)

The Contract Program Manager shall create an independent Integrated Master Schedule (IMS) associated with each Task Order that includes all milestones defined within. The IMS must be reviewed during all Integrated Product Team (IPT) meetings and attached to the monthly status report. The format must be in Microsoft Excel and delivered in Adobe Acrobat PDF. The Contractor shall ensure that all milestones for both the Contractor and Government are incorporated within the IMS. Within the first 60 days of contract award, the Contractor must conduct a comprehensive review of the IMS with Government Program Manager (PMs) and/or COR. This review provides an opportunity for the Government to understand the IMS developed for the program and suggest any corrections or additional milestones. Once the initial review is completed, the Contractor shall support IMS reviews for each Task Order as requested by the Government. (CDRL A009, DI-MGMT-80368) o Manpower Safety o Site Acceptance Test Plan/Procedure o Program Risks and Issues

• Following Critical Program Milestone entrance criteria

• Action Item Review

Exit Criteria CDRL CDRL Name A007 Meeting Minutes (DI-ADMN-81250C) Kick-off Meeting Exit Criteria shall address the following:

Expected course of the program, discussed and agreed upon.

Sufficient review of technical, schedule, and performance requirements Risks and issues identified with plans to address following the event Action items specified with POC and expected completion date.

3.1.1.2.3 Monthly Status Report (MSR)

The Contractor shall submit a MSR no later than day ten (10) of each month throughout the contract period reporting the performance objectives of each task order. The MSR shall contain all items defined in the Data Item Description (DID) and may be altered if mutually agreed upon. Table 4-Monthly Status Report provides a simplified template that may be expanded or reduced if mutually agreed upon by the Contractor and Government: (CDRL A010, DI-MGMT- 80368)

Table 4 - Monthly Status Report

3.1.1.2.4 Requirements Traceability Verification Matrix (RTVM) To ensure compliance with the technical requirements of the FPS-117 Radar system, the Contractor shall develop a comprehensive Requirements Traceability Verification Matrix (RTVM) upon receipt of order, as applicable to newly incorporated Task Order requirements. This RTVM shall address the requirement list within the Radome Engineering Specification (Document No: 20250725 CAGE: 98747) section 4.1 Verification Index. This RTVM shall supplement documentation delivered during the proposal process, which identified the verification status of the radome design against requirements, to include additional information and details. The RTVM shall provide existing data or evidence that verifies that the Contractor’s radome design meets each requirement listed within the Air Force radome specification. For requirements that have not been previously verified, the Contractor shall provide a testing plan for the validation of the remaining requirements, in accordance with section 4 of the specification. Initial Delivery, Subsequent Deliveries and Final Delivery shall be defined in the Task Order PWS. (A008 DI-MGMT-82133)

Monthly Status Report (MSR) Monthly Status Report (MSR) shall include no less than:

Schedule of:

• Radome and Accessory Manufacturing

• Shipments of Radomes and Accessories

• Radome and Accessory manufacturing completion dates

• Radome and Accessories on hand (Not yet installed)

• Radome and Accessories in transit, and location shipped to

• Quantity of Shipments within month (Radomes and Accessories)

• Installation status for each site in work

• Schedule slips

Technical Issues

• Diminishing Manufacturing Shortage Material Shortages (DMSMS)

• Material Receiving Inspection

• Identify long lead items or efforts identified.

• Acceptance test status

• Constraints – identify all constraints impacting or may impact manufacturing, transport, installation, de-installation of Radomes Assemblies and components. Solutions with get-well schedule be identified for each constraint.

• Over and Above work Other

• Action Items

• Itemized man-Hours and costs incurred during the period.

• Contract Deliverable Status

• Total Completed

• Total Incomplete

Exit Criteria CDRL CDRL Name A010 Status Report (DI-MGMT-80368A)

3.1.1.2.5 Radar Protection Plan

To ensure the integrity of the radar system and equipment, the Contractor shall develop and submit a comprehensive Radar Protection Plan that outlines the methods and procedures for protecting the Radar Weapon System, array floor, and surrounding area from potential hazards during the removal and installation of radomes, including:

• Shearing of bolts

• Grinding

• Electrical current through the pedestal

• Other potential damage or interference

The Radar Protection Plan shall be tailored to address the unique requirements of all sites and shall be submitted to the Government for approval no later than 90 days after receipt of the task order. If the Contractor is unable to develop a unified protection plan that applies to all sites, the plan shall be revised and resubmitted for approval.

The approved Radar Protection Plan shall be adhered to during all phases of the contract, including assembly, disassembly, testing, and installation of Radome Assemblies and Accessories. The Contractor shall ensure that all personnel involved in the contract are trained on the Radar Protection Plan and that the plan is strictly followed to prevent damage to the AN/FPS-117 Radar Weapon System and surrounding facilities.

In the event that the Government does not approve the initial Radar Protection Plan, the Contractor shall revise and resubmit the plan within 30 days of notice. The revised plan shall address all comments and concerns raised by the Government, and the Contractor shall ensure that the revised plan is implemented and followed throughout the remainder of the contract. (CDRL A004, DI-MISC-80508B)

3.1.1.2.5.1 Accident/Incident Notification and Report

The Contractor shall notify the Contracting Officer (CO) within eight (8) hours of any incident resulting in personnel injury or damage to Government property, and within 3 (three) workdays submit an Accident/Incident Report.

The contents of Accident/Incident Notifications and Accident/Incident Reports shall be defined by the CDRL. If requested by the designated CO, The Contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the Procuring Safety Office.

The Contractor will provide copies of contractor data related to accidents/incidents, such as contractor analyses, test reports, summaries of investigations, etc. as necessary to support the Government investigation. (CDRL A011, DI-

MGMT-82188)

3.1.1.2.6 Site Survey Report

To understand and prioritize the work requirements for each site, the contractor shall submit a Site Survey Report conveying the necessary, equipment, manpower, GFE, and necessary planning elements as required to successfully perform the de-installation, installation, test, and disposal of each radome per long range site. To ensure the most efficient use of cost and time, the method of performing the survey is recommended to include a questionnaire submitted to the PMO and O&M Contractor to gather information on the Contractors behalf. This may include photos, measurements, or other technical information. If deemed necessary, travel to the sites shall be performed IAW the travel CLIN of this contract. The Sites to be surveyed are listed in Attachment “Long Range Site Locations and Addresses”. The Site Survey technical report shall cover items within Table 5 be submitted NLT 90 days after receipt of order. (A012, DI-MISC-82104)

Table 5 - Site Survey Report

Site Survey and Installation Report

• Site name and location

• Radome P/N or configuration

• Tower P/N or configuration

• Anticipated Engineering changes or deviations from configuration

• Anticipated Shipping Method

• Shipments and Broker Requirements

• On hand Government Furnished Equipment (GFE)

• Needed Government Furnished Equipment (GFE) (manlift, scaffolding etc)

• Transportation Support (Ground/Air/Sea)

• Local/site support requirements

• Recommended installation method

• Installation start date and installation completion date

• On site container storage method.

• Disposal location

• Disposal schedule

• Expected deviation from Radome Baseline Configuration (Engineering Changes)

• Quantity of manpower/installers needed

• The Contractor shall provide information not included in the above list if deemed relevant.

CDRL CDRL Name

A012 Site Survey Report (DI-MISC-82104)

3.1.1.2.7 Engineering Change Proposal (ECP)

Upon identifying an engineering change to the government approved baseline configuration of the radome, in pre-existing tower, or radome-attachment infrastructure that is required to meet the technical requirements of the radome or facilitate installation, the Contractor shall submit Engineering Change Proposal (ECP) that is applicable to the suggested design change. The Contractor shall also submit an ECP for any proposed subcomponent substitutions.

Initial Delivery, Subsequent Deliveries and Final Delivery shall be defined in the Task Order PWS. (A013, DI-

SESS-80639E)

3.1.2 Spare Materials

The Contractor shall provide a comprehensive plan for managing spare materials required for the radome replacement. This plan shall address material identification, justification, long term protection/storage requirements, storage, and disposition of spare materials. The Government anticipates that the Contractor's expertise will be crucial in determining the appropriate types and quantities of spare materials necessary to prevent work stoppage and ensure timely project completion. The Contractor shall propose a detailed list of spare materials required for the radome replacement. This list should include, but is not limited to, items such as:

Radome panels (specify potential…