Attachment 01_IDIQ PWS.pdf

Page | 1 of 68

Contract Number:

Missile Warning, Space & Ground Control Team

Page | 2 of 26

TABLE OF CONTENTS

SECTION TITLE PAGE #

1 Scope of Work 3-4

2 Contractual Requirements 5-9

3 General Requirements 10-14

4 Performance Requirements 15-16

5 Contract Transition 17-18

6 Services Summary 19-20

7 Contract Administration 21-22

8 Acronyms 23-26

Page | 3 of 26

RADAR SERVICES REQUIREMENTS

SECTION 1

SCOPE OF WORK

1.0. BACKGROUND. This Indefinite Delivery/Indefinite Quantity (ID/IQ) contract is a

United States Space Force (USSF) radar, computer, and communications support effort for missile warning (MW), missile defense (MD), and space domain awareness (SDA) worldwide. The mission owners are the USSF and Space Operations Command (SpOC). The objective of this contract is to provide non-personal operations, maintenance, and support

(OM&S) services for the USSF and SpOC radar missions.

1.1. MISSION. SpOC’s MW, MD & SDA radar missions continue to evolve to meet the

USSF objectives for commonality, interoperability, survivability, capacity, and responsiveness for missile detection, defense, discrimination, and homeland defense systems in accordance with (IAW) USSF policy. The radar mission is of vital interest to the nation and requires continuous support. The effort put forth under this contract by the contractor should always reflect the relationship between the radar mission and the safety and security of the United

States (US) and its Allies. Additional integrally related missions and projects may be added in the future and will be negotiated separately.

1.1.1. Mission Contingencies. Based on mission needs, the Government anticipates upward and downward adjustments of its requirements throughout the lifetime of the contract.

Examples include:

Space Systems Command (SSC) Receiver/Transmitter (R/T). The SSC R/T may be added in the future. The scope of work required has not been determined.

Digital Early Warning Radar (DEWR) Mission System Equipment. DEWR

Mission System is projected to be added in the future to supplement (run parallel to) the current UEWR Mission System for a short period of time until the DEWR Mission

System replaces the UEWR Mission System. The scope of work required has not been determined.

Project PHARUS. Project PHARUS will replace legacy hardware subsystems with

Government-owned, COTs-based hardware subsystems and modern, modular software architecture supporting rapid mode-insertion. It will increase capabilities for the warfighter and reduce future sustainment requirements. The scope of work required has not been determined.

Clear SFS Security Forces Support. Security Forces support at Clear SFS may be added in the future if the proper exception to 10 U.S.C. 2465 is received. The scope of work required has not been determined.

Page | 4 of 26

1.2. CONTRACT SCOPE. Provide all mission essential non-personal services, administrative, financial, and managerial resources necessary on a continuous twenty-four hours-a-day/seven days-a-week (24/7) basis to support USSF and SpOC radar systems. The following types of missions and services areas may be provided: radar operations support, system upgrades and modifications, radar maintenance, mission computer maintenance, technical assistance, site/installation physical security, exercises and testing support, simulation trainers, training development and support, military satellite communications, communications-electronics, electronic system management, supply, fuels, Non-Classified Internet Protocol

Router Network (NIPRNet), Secret Internet Protocol Router Network (SIPRNet), Joint World-

Wide Intelligence Communications System (JWICS), environmental, occupational health, medical and public health, civil engineering, vehicle and traffic management, services (food and morale/welfare activities), lodging management, custodial, industrial, physical and operational security, information management, and transition (phase-in/out) activities. Includes security classification up to Top Secret (TS)/Sensitive Compartmented Information (SCI) level in support of site Sensitive Compartmentalized Information Facility (SCIF) and communications requirements. The Government reserves the right to add additional missions or services which are determined integral to the MW, MD, and SDA mission of this contract.

1.3. MISSION PARTNER ASSETS. The Government reserves the right to remove and add other assets, mission partner assets, or performance requirements at any of the six (6) GSUs based on future needs. The types of missions and service areas shown above may not be all inclusive and could change based upon the determination by the USSF, SpOC, and their mission partners’ needs.

Page | 5 of 26

SECTION 2

CONTRACTUAL REQUIREMENTS

2.0. GENERAL. Unless otherwise identified, the Federal Acquisition Regulation (FAR) definition for the words ‘shall’ or ‘will’ reside over the entirety of the contractor’s performance in meeting the contract’s and its issued task orders’ PWS requirements. Therefore, whether these words are cited for each requirement or not, the Government’s expectation is that the contractor ‘shall’ fulfill all requirements as provided in the respective PWS.

2.1. CONTRACTOR PM. The contractor shall provide an overarching PM who shall be the single point of contact for the Government for all contract administration and performance in direct support of USSF and SpOC. The Contractor PM shall plan, integrate, execute, manage, monitor, and control the contract. If the assigned overarching PM for the contract is not the same PM for an issued task order, then the contractor shall identify this in its respective task order proposal. The contractor’s PM shall have sufficient authority to direct the day-to-day contractor activities of the resources assigned to this contract.

2.2. AVAILABILITY. The contractor shall be responsive to Government requests and meet required contractual timelines. Task Orders may provide other or further availability requirements. The contractor shall respond to emergencies immediately. The contractor PM or designated representative shall be available to respond to non-emergency Government requests within twenty-four (24) hours.

2.3. CONTRACTOR ADMINISTRATION. The contractor shall provide an overarching contract administrator for the contract who shall establish processes and assign appropriate resources to effectively administer the entire requirement. The contractor shall respond to

Government requests for contractual actions within a reasonable amount of time or otherwise directed by the CO. If the assigned overarching contractor administrator for the contract is not the same for an issued task order, then the contractor shall identify this in its respective task order proposal.

2.3.1. Proposal Submission Process. Submit a proposal for every Request for Task Order

Proposal under this contract. A requirements document with supporting details will be provided to the contractor as attachment(s) to the RFP. The contractor’s proposal shall be submitted to the ordering CO by the time and date specified in the RFP letter. Pricing on task order proposals shall be valid for ninety (90) calendar days after the required submission date.

2.4. CONTRACTOR PERSONNEL, DISCIPLINES, AND SPECIALTIES. Provide the necessary resources and infrastructure to manage, perform, and administer the contract.

Employ and utilize qualified personnel with appropriate combinations of education, training, clearances, and experience. All contract employees who interface with the Government, either electronically or in person, shall be able to read, write, speak, and understand English.

Contractor personnel will be under the direction and control of the contractor’s PM. They shall be subject to regulations and directives governing the activities of personnel on government

Page | 6 of 26 installations.

2.5. CONTRACTOR EMPLOYEE RESTRICTIONS AND IDENTIFICATION.

Contractor shall not employ any person for work on this contract if the employee is identified by the contractor or CO as a potential threat to the health, safety, security, general wellbeing or operational event of the installation and its population. When on a Government installation, each contracted employee shall be identified with easily readable identification worn and displayed on the employee’s forward facing mid to upper torso garment(s). Worn and displayed identification will include the employee’s name and contractor’s name. Identification shall always be worn when a contractor employee is working in support of the contract. All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as contractor employees.

2.6. CONTRACTOR CONDUCT. If a contractor employee endangers life, property, security, or such an employee violates base regulations; the Installation/Site Commander/

United States Space Force Liaison Officer (USSFLO) may direct removal of any employee from the installation. While on duty, contractor personnel must be actively performing mission related activities. The Government reserves the right to require immediate removal of an individual from the Installation/Site at its discretion. In cases where the Installation/Site

Commander/USSFLO has directed removal, the CO will follow-up with written notification to the contractor.

2.7. INSTALLATION/SITE REMOVAL. The Installation/Site Commander/USSFLO may direct the contractor in writing to remove any employee from the Installation/Site when presence of such employee endangers life, property, or security, or where such employee violates reasonable and necessary regulations or lawful order of the Installation/Site

Commander/USSFLO. Categories of violations or misconduct, which may cause employees to be removed from the Installation/Site include, but are not limited to:

• Security violations

• Inappropriate use of Government Computers, Government-Furnished Property (GFP), and Government-Furnished Equipment (GFE)

• Negligence, willful damage to, or destruction of property

• Injuries inflicted upon other personnel

• Alcohol or drug abuse

• Engagement in unauthorized private business transactions

2.8. WITHDRAWAL OF PRIVILEGES. The Government retains the right to withdraw privileges authorized herein that are subject to abuse by contractor employees or their dependents. Upon investigation of facts and circumstances of any incident, services or privileges may be withdrawn on a permanent or temporary basis, at the sole discretion of the

Installation/Site Commander/USSFLO and Government CO.

2.9. CONFLICT OF INTEREST. The contractor shall not employ any individual who is an employee of the United States Government if the employment of that individual would create a conflict of interest, nor shall the contractor employ any person who is an employee of the DAF

Page | 7 of 26 or USSF, either military or civilian, unless such person seeks and receives approval of the employment in accordance with DODD 5500-7. In addition, the contractor shall not employ any person who is an employee of the AF if the employment would be contrary to the policies contained in AFI 64-106.

2.10. TERMINATIONS. Report any employee terminations to the CO within 24 hours of occurrence. The CO may request the contractor remove any employee performing work on the contract when retention endangers life, property, national security, and the integrity and standards of the program. The CO may also request the contractor remove any employee from performance of duties who does not meet the minimum education and experience qualifications established in the contractor’s Management Plan.

2.11. RECALL OF CONTRACTOR PERSONNEL. The Installation/Site

Commander/USSFLO will determine the level of contractor participation for any given exercise, inspection, or real-world event, including recall of contractor personnel back to the

Installation/Site. Surge support requests are submitted through the Installation/Site

Commander/USSFLO for review and coordinated prior to submitting recommendations for surge support to the CO for approval. Emergency requests that risk life, limb, or mission failure shall be approved by the COR.

2.12. ASSOCIATE CONTRACTOR AGREEMENTS (ACAs). The contractor shall negotiate with associate contractors to develop appropriate ACAs towards the integrated support, cooperation, exchange, and sharing of information essential to successful performance of the individual efforts. Submit completed ACAs to the CO no later than 30 days after award.

These agreements shall not restrict the Government’s rights established pursuant to this or any other contract. The contractor shall not duplicate contracted functions intended by the AF or

USSF to be provided by an associate contractor pursuant to the terms of their contract. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the contract which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

2.13. THIRD-PARTY SUPPORT. The contractor shall provide technical information and logistical support for other contractors, subcontractors, or Government agencies in support of upgrades, projects, and other efforts impacting PWS requirements and Installation/Site operations. It is permissible for the contractor to separately contract with third-parties under the following conditions: (a) the services are performed on a non-interference basis with the contractual services performed under this contract, (b) no Government property provided under this contract is used in performance of third-party services without written approval of the CO, and (c) the Government PM and CO are informed of third-party contracts prior to final agreement.

2.14. CONTINUANCE OF PERFORMANCE/MISSION ESSENTIAL SERVICES. In a time of crisis, other services to increase security and well-being may be required on a 24/7 basis as determined by the Installation/Site Commanders/USSFLO and directed by the CO. In the event of a crisis or pandemic declared by the US President and/or the Secretary of Defense, Page | 8 of 26 continue performing all PWS requirements. Continue services through all Force Protection and

Defense Conditions without interruption. Make written notification to the Installation/Site

Commander/USSFLO, the Government PM and CO of any cost impact resulting from declared crises and states of emergencies within 30 days of CO direction to continue work.

2.15. CONTINGENCY PLANNING. The contractor shall develop a contingency plan as defined in each ID/IQ task order. The plan shall provide for continued operations and timely return of systems to operational status in the event of a declared crisis, catastrophic and non-catastrophic events, and work stoppages for each site location. The plan shall contain the following information at a minimum: continue support during contingency actions, emergency work requests, natural disasters, labor strike/personnel walk-off, contingency mobilization, and mobilization recall commitments.

2.16. KEY POINTS OF CONTACT. The contractor shall provide the names, mobile phone numbers, and duty phone numbers of points of contact for the Contractor PM and Program

Contracts Administrator.

2.17. Contractor Program Integration. Maintain continuity and oversight of the support operations at the six Radar Installations/Sites and the contractor’s Program Management Office

(PMO). Communicate and coordinate activities seamlessly, sharing information across

Installations/Sites when such information is beneficial to the program overall and to prevent the same issues being worked independently at multiple sites. Maintain current comprehensive schedules of Installation/Site projects and activities. Conduct joint Government/contractor

PMRs.

2.18. CONTRACTOR TRAVEL. The contractor is responsible for the cost of travel required to perform the contract tasks unless specifically identified as reimbursable travel by the Government. Costs for travel shall be IAW the regulatory implementation of Public Law

99-234 and FAR Subpart 31.205-46 - Travel Costs (subject to local policy and procedures).

The contractor shall ensure that personnel traveling overseas in support of the contract have appropriate passports, other travel documents (e.g., travel visas) and proper country clearance required for the destination country or countries. The contractor shall adequately plan travel coordination to ensure minimal impact on the mission. Additional travel requirements and any reimbursement requirements may be defined further in each ID/IQ task order.

2.18.1. Travel Arrangements. Contractor is responsible for arranging all travel required to fulfill the contract’s requirements. Letters of Identification (LOI) are required for Air Force

Material Command (AFMC) flights and/or shipment of household goods and must include the contractor’s billing address and contract number. The contractor shall receive a written signature from the CO on all LOIs. Country clearances should be processed at a minimum of sixty (60) calendar days prior to arrival. For OCONUS travel, the contractor shall arrange for

Air Mobility Command (AMC) travel through the supporting Traffic Management Office

(TMO) or through the AMC passenger reservation center (24-hour telephone service at 1-800-

851-3144). The contractor shall arrange all unaccompanied baggage shipments to Installation/

Site locations, with the nearest TMO. The Government will pay for costs up to the allowable limits, IAW FAR Subpart 31.205-46. Any additional costs will be paid for by the contractor.

Page | 9 of 26

2.19. CONTRACTOR COMMON ACCESS CARDS (CACs). A CAC is required for contractor personnel requiring on-going access to an USSF Installation/Site, or who require

USAF network access in performance of PWS requirements (to include myLearning web-based training completion). A favorable background investigation (Tier 1) is required for NIPRNet access. Coordinate with the appointed Mission Partner Affiliation Sponsor (MPAS)/Mission

Partner Affiliation Sponsor Manager (MPASM) to acquire a CAC. Notify MPAS or MPASM when contractor personnel are no longer affiliated with the contract or no longer meet eligibility requirements and return CACs of personnel affected within 30 days of those conditions.

2.20. CONTRACTOR DOCUMENTATION OF CONTRACT PERFORMANCE. Make

all information and documentation generated in performance of PWS requirements or maintained (to include Government-furnished documents) by the contractor in performance of

PWS requirements, available in editable electronic format for Government review upon request for the duration of the contract. Contractor-generated format is acceptable, unless otherwise noted in the PWS.

2.21. CONTRACTOR TRAINING. The contractor’s training program shall ensure a properly trained and qualified workforce is in place prior to performing assigned duties and throughout the life of the contract. The contractor shall fund all contractor personnel training unless otherwise stated. Government-unique training courses will be made available to contractor personnel and travel will be reimbursed by the Government. The contractor shall pay for training expenses when employee turnover causes the need for repetition of

Government-provided training within one (1) year of course completion. The contractor shall create, update, and conduct a formal position certification/qualification training program to ensure only certified/qualified contractor personnel are assigned to perform operations, maintenance and testing in positions identified as requiring certification/qualification. The certification/qualification program must be contractor self-contained, requiring no technical or materiel support from the Government and is subject to Government observation and review.

Maintain training records for personnel and grant the Government access to those records upon request, to determine compliance with Certification/Training Plan. Trainees will not perform operations, testing, or maintenance unless under the direct supervision of a certified/qualified technician. Training requirements include operations, testing, and maintenance (as appropriate). Disseminate knowledge gained by contractor personnel at Government training courses and conferences to other contractor personnel requiring the same information. Other training requirements may be detailed at the task order level.

2.22. Contractor Knowledge Management (KM). Create, implement, and maintain a KM

Plan for a sustainable radar and communication system workforce qualified in meeting PWS requirements.

Page | 10 of 26

SECTION 3

GENERAL REQUIREMENTS

3.0. GENERAL REQUIREMENTS. Services may take the form of assistance, administration, management, execution, and/or operation of auxiliary functions which are required to support this contract. The contractor shall successfully integrate and coordinate all activities needed to execute requirements; manage the timeliness, completeness, and quality of problem identification; provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors; seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel; demonstrate sound teamwork practices with the Government as well as with other contractors as required;

and present new ideas, identify possible efficiencies, opportunities for streamlining, and discuss possible solutions in the performance of this contract.

3.1. NON-PERSONAL SERVICES. The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees outside the scope of this contract. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the CO immediately.

3.2. LIMITED HEALTH SERVICES FOR CLEAR SFS AND PITUFFIK SB. Contract performance in support of the Geographically-Separated Units (GSUs) at Clear SFS and

Pituffik SB requires work in a remote environment. Except as otherwise provided in the contract, the contractor accepts the risks associated with required contract performance at these

GSUs. Emergency medical and dental care is provided if US contract employees are injured while living on location supporting the radars’ performance. Medical care beyond this standard may be provided on a space available basis for general health concerns (illness).

3.2.1. Medical Evacuations for Clear SFS and Pituffik SB. If medical evacuation off Clear

SFS is required for contractor personnel, the contractor is responsible for all transportation and associated costs. If medical evacuation out of Pituffik SB is required for US contractor personnel, the contractor will be required to charter a flight/transportation at their own expense or reimburse the US Government for all costs associated to medically evacuate US contractor personnel out of Pituffik SB (to include airlift support and associated costs).

3.3. SPECIAL CONSIDERATIONS FOR PITUFFIK SB. Comply with all applicable international agreements, customs, and theater clearance requirements between the US

Government and Kingdom of Denmark.

3.4. SPECIAL CONSIDERATIONS FOR RAF FYLINGDALES. Comply with all applicable international agreements, tax and labor laws, customs, and theater clearance

Page | 11 of 26 requirements between the US Government and the United Kingdom (UK).

3.5. REPORTING REQUIREMENTS. All deliverables identified in a task order shall be accurate, complete, and submitted on time.

3.6. SITE AWARENESS AND NOTIFICATION. Inform, educate, and/or make available to the Installation/Site Government personnel (military and civilian) the rules, regulations, and procedures for personnel compliance in the interest of safety, security, and mission accomplishment. Report any violations to the Installation/Site Commander/USSFLO.

3.7. PWS and SOW Organization. PWS and SOW requirements have been organized in a manner that facilitates clear and concise description. The grouping of requirements is not intended to imply a preferred organizational structure to meet requirements. A requirement, once stated in the PWS or SOW, applies regardless of its location in the PWS. The contractor is expected to understand the interrelationship between requirements and to organize and perform accordingly. The Installation/Site Commander/USSFLO when stated throughout the PWS means the Installation/Site Commander/USSFLO or his/her designated representative. Site applicability is listed under each paragraph of the PWS to indicate the Installation/Site the requirements within the paragraph applies to.

3.8. WORKLOAD DATA. The workload data is only needed at the TO level.

3.9. LOCATION AND HOURS OF WORK. The primary location of the Government program office is:

SpOC SAIO/PMO

135 Dover Street, Building 350

Peterson SFB, CO 80914

3.9.1. SpOC Locations: The SpOC locations for contract performance are listed below.

• 6 SWS, Cape Cod SFS, MA

• 7 SWS, SOC-B Beale AFB, CA

• 7 SWS, SOC-CM Cheyenne Mountain SFS (CMSFS), CO

• 12 SWS, Pituffik SB, Greenland

• 13 SWS, Clear SFS, AK

• RAF Fylingdales, United Kingdom

3.9.2. Work Schedule. For contractor tasks that are required during normal duty hours (0730-

1630 Monday – Friday), the contractor shall adopt a work schedule that mirrors the

Government’s federal work/holiday schedule. Radar operations are performed 24/7 unless specifically exempted or otherwise stated. Adjustments to working hours may be required depending on local conditions and mission requirements.

3.10. PROCESSING, HANDLING AND STORAGE OF CLASSIFIED INFORMATION

AND EQUIPMENT. Performance may require the contractor to process, handle and store

Page | 12 of 26 information and equipment. Certain items may be classified up to TS/SCI. Contractor employees whose duties require access to classified information shall possess a minimum of an interim Secret security clearance unless otherwise noted. The contractor must possess a facility security clearance at the classification level of Top Secret, IAW DoD 32 CFR Part 117

National Industrial Security Program Operational Manual (NISPOM), prior to contract work.

The contractor shall have SIPRNet access for classified communication with the Government and follow all applicable security guidance.

3.11. MISSION EQUIPMENT. Mission Equipment by Installation/Site location and the required on-site support will be defined at the task order level.

3.12. CONTRACTOR PROVIDED MATERIALS, SUPPLIES, VEHICLES, AND

EQUIPMENT. The contractor shall provide all the materials, supplies, vehicles, and equipment required to perform the contract tasks unless specifically identified as local purchase in the ID/IQ task order. The contractor is responsible for shipment of vehicles.

3.13. Contractor Vehicle Licensing, Training, and Operation. Personnel operating general-purpose motor vehicles and special-purpose vehicles/equipment will be licensed in accordance with (IAW) the applicable US, UK, or Greenlandic standards and will be trained and/or certified.

3.14. GFP, GFE, Government-Furnished Material (GFM), and Contractor Acquired

Property (CAP). Includes all property owned or leased by the Government. Government property includes both Government-furnished and CAP for which the Government purchases/pays. Government property includes material, equipment, special tooling, special test equipment, and real property. Government property does not include intellectual property and software. Supplies for, repair, and replacement of these items will be at the contractor’s expense and will not be reimbursed by the Government. The Contractor may utilize this

Government property until economically unrepairable as determined by the COR. If the property is replaced and paid for with the contractor’s own funds, it becomes contractor property and shall be marked accordingly to distinguish it from Government-marked property.

The Contractor shall use the GFP module of the Procurement Integrated Enterprise

Environment (PIEE) to report receipt of GFP; report transfer of GFP to another DoD contract;

report the shipment to the Government or to a contractor (the GFP module generates the electronic equivalent of the DD Form 1149, DD Form 1348-1, or other required shipping documents); report when serially-managed items of the GFP are incorporated into a higher-level component, assembly, or end item; and report the loss of Government property in accordance with FAR 52.245-1, paragraph (f)(1)(vii) of this contract.

3.15. PLANS, POLICIES, AND PROCEDURES. Contractor shall comply with plans, policies, and procedures.

3.16. EXISTING RECORDS. Contractor shall maintain all Government records in the format provided or current formatting.

3.17. GENERATED DOCUMENTATION. The contractor shall maintain all records and

Page | 13 of 26 reports generated in performance of the contract and issued task order requirements in editable electronic format; make available for Government review and retention, upon request.

Contractor format is acceptable unless specified otherwise. Contractor name and logos may not be used except when a contractor signatory is required for a specified document, record, report, or deliverable.

3.18. SUPPORT AGREEMENTS. The contractor shall comply with Host-Tenant requirements indicated by “the receiver will” and IAW Support Agreements. Advise the

Installation/Site Commander/USSFLO, Government PM, and CO in writing, of any required support not reflected in support agreements.

3.19. EQUIPMENT MAINTENANCE. Contractor shall maintain all assigned equipment in performance of the contract and issued task orders or commercial manuals when Government policy is not available.

3.20. QUALITY PROGRAM. Contractor shall develop, implement, and maintain a Quality

Program that meets or exceeds all performance requirements in the contract and its issued task orders. All PWS requirements shall be reviewed at least annually.

3.20.1. Quality Program Plan (QPP). The contractor shall implement the QPP that provides insight into the following quality processes: internal audits including procedures and oversight of each PWS requirement, identification of deficiencies, prevention of nonconforming services, and corrective measures if performance requirements are not attained.

3.20.2. Quality Status Report (QSR). The contractor shall generate and distribute a QSR as determined in each task order.

3.21. OUTSIDE AGENCY SUPPORT. Contractor shall provide technical assistance and advice to all other contractors or Government agencies to support design, development, and installation of new facilities, systems, or equipment within the scope of any issued task order.

3.22. SCIF. SCIF facility, equipment, and maintenance requirements shall be defined at the task order level.

3.23. BRIEFINGS, MEETINGS, TOURS, AND ESCORT SUPPORT. The contractor shall provide support for briefings, meetings, tours, and escort support on a non-interference basis to mission operations. Maintain workload data on briefings, meetings, tours, and escort support per issued task orders. Specific requirements may be detailed further at the task order level.

3.24. BUDGET INFORMATION. The contractor shall participate in developing budget information including projected costs for unfunded requirements with justification and impact statements. Additional budget information requirements may be detailed in each task order.

3.24.1. Resource Utilization. Document the use of Government funding detailing annual CR

CLIN projections and expenditures for each option year (OY). Develop budget information

Page | 14 of 26 including projected costs and unfunded requirements with justification and impact statements as required for continued performance.

Page | 15 of 26

SECTION 4

PERFORMANCE REQUIREMENTS

4.0. PERFORMANCE REQUIREMENTS. The Government reserves the right to remove and add other radar, mission partner assets, or performance requirements at any of the GSUs based on future requirements. Changes to existing requirements shall be negotiated through a bilateral modification. Services required may include, but are not limited to, operations, maintenance, logistics support, information technology, communications, training, administrative, Communications Security (COMSEC), base facilities support, base operating support services, security support and any other service determined in support of this contract.

4.1. PROJECTS. Each project may be awarded as an individual task order for work within scope of the contract. The Government anticipates using FFP or CR CLINs for these projects, but other CLIN structures could be used. Projects’ final CLIN structure will be determined by the CO on a case-by-case basis depending on the nature of the work. Project proposal requirements will be specified at the task order level.

4.2. INSTALLATION AND HIGHER HEADQUARTERS-DIRECTED EXERCISES.

The contractor may be required to participate in installation- or higher headquarters-directed exercises and inspection teams. Specific requirements will be detailed at the task order level.

4.3. FACILITIES PLANS AND STANDARDS. Comply with Government-furnished Plans and Standards at each GSU and ensure all maintenance, repair, and construction work is accomplished within established guidelines and standards. Specific requirements may be detailed at the task order level.

4.4. OPERATING INSTRUCTIONS (OIs)/CHECKLISTS/MANUALS. Develop and maintain COR approved standardized OIs and checklists for all radar contractor operated systems; procedures unique to a particular Installation/Site may be captured as annotation on the standardized OI or by a local procedure checklist. Include startup, transfer, and shutdown instructions as well as any specific instruction necessary to safely operate all equipment and systems. Maintain current schematic diagrams for all main electrical and mechanical systems.

These schematics shall be readily available to assist troubleshooting utility systems. Maintain a current and complete set of Original Equipment Manufacturers (OEM) operation manuals on all RP and RPIE which the contractor operates and maintains. Additional Operating

Instruction/Checklist/Manual services or requirements may be detailed at the task order level.

4.5. CIVIL ENGINEERING (CE) FACILITY SUPPORT. Manage all CE Facility

Support. This may include any CE related work/functions, work requests/service calls, minor construction (MC) work requests, CE sustainment projects, management of real property (RP) and real property installed equipment (RPIE), fire prevention and protection services, custodial services, grounds maintenance and snow mitigation support, refuse management, and emergency management. Additional Facility Support to CE services or requirements may be detailed at the task order level.

Page | 16 of 26

4.6. ENVIRONMENTAL COMPLIANCE. Comply with all environmental programs IAW all applicable laws, regulations, policies, standards, directives, executive orders, treaties, agreements, and host base OIs and plans at all GSUs. Comply with environmental programs and participate in meetings at the direction of the Installation/Site

Commander/USSFLO. Additional Environmental Compliance and service requirements may be detailed at the task order level.

4.7. SAFETY PROCEDURES, GUIDANCE, AND ADDITIONAL SAFETY

REQUIREMENTS. Provide site/ installation security comply with all local and international safety standards and comply with the program that is most stringent unless otherwise directed by the Government. The contractor shall provide Safety Support as defined and IAW the

ID/IQ task order. Additional Safety Procedures, Guidance, and Safety Requirement services or requirements shall be detailed in the ID/IQ task order.

4.8. SECURITY. Provide industrial, physical, and operational security, and resource protection. In addition, immediately report any information or circumstances that may pose a threat to the security of DoD personnel, contractor personnel, resources and classified or unclassified defense information. All incidents and violations will be reported to the unit security manager. Additional Security Procedures, Guidance, Clearance Requirements, and associated requirements shall be detailed at the task order level.

Page | 17 of 26

SECTION 5

CONTRACT TRANSITION

5.0. CONTRACT TRANSITIION. Contractor will implement and manage an orderly transition with all parties to include the successor contractor, the incumbent contractor, and the

Space Force Transition Team (SFTT). Jointly develop and prepare required reports (if any) during the last 30 days of transition prior to the assumption of maintenance and support responsibilities by the successor. Transfer all property, equipment, materials, supplies, and data no later than three days prior to new contract performance start. NOTE: All time periods in this section refer to calendar days elapsed from start of Transition Phase-In CLIN.

5.1. PHASE-IN PERIOD. Execute all Phase-In tasks as may be further specified within an issued Task Order (TO). Furthermore:

• The Government will provide existing radar data to the contractor. The contractor shall store and protect data and make this data available to authorized contractor/government users.

• Incumbent contractor(s) shall remain fully responsible and accountable for existing contractual requirements. The Government may award additional TOs after start of

Transition Phase-in, at which time the contractor shall assume full responsibility and accountability for all PWS tasks.

5.2. TRANSITION PHASE-IN PLAN. Develop, deliver, and execute a Transition Phase-in

Plan within thirty (30) calendar days of contract award. Identify any issues during transition to the CO and the SpOC Transition Team.

5.2.2. Phase-in Staffing. The contractor shall have a complete, certified, qualified, trained, and cleared workforce available in each work center (without any degradation in service) no later than the end of the ninety (90) calendar day transition period.

5.3. TRANSITION COORDINATION. The contractor shall coordinate all transition efforts with the SFTT prior to transitioning. Include Incumbent at start of transition efforts. Identify any conflicts to the CO.

5.4. KEY POINTS OF CONTACT. The contractor shall provide in writing the names and contact phone numbers of key points of contact to the Installation/Site Commanders/USSFLO, Government PM, and CO.

5.5. JOINT INVENTORY. Complete a joint inventory in conjunction with the incumbent contractor and the SFTT, documenting property, serviceability, and any discrepancies in each

ID/IQ task order functional area. The contractor shall document and assist in resolving all discrepancies. The contractor shall obtain and maintain equipment accountability of all GFP.

Upload all applicable GFP data into Defense Property Accountability System (DPAS) IAW

DoDI 5000.64 Accountability and Management of DoD Equipment and Other Accountable

Property, FAR Part 45 and DAFFARS Part 245. Notify the Government of any excess equipment for disposition and/or any equipment received in an inoperable condition within 180 calendar days. Obtain and maintain responsibility for licenses, maintenance agreements, Page | 18 of 26 service contracts and warranties. The contractor is accountable for all GFP.

5.6. PHASE-OUT. The contractor shall submit a Phase-Out (Transition) Plan 6 months prior to contract expiration that addresses all actions necessary to ensure a seamless transition, including joint inventories, account transfers, and turnover actions. Coordinate with the SFTT before any transition efforts begin. Identify any conflicts to the CO and PM. The incumbent shall complete all activities necessary to ensure a successful transition of all functional areas while ensuring continued service. The incumbent shall allow the successor contractor access to any system for over-the shoulder observation and hands-on training during transition. Upon direction of the Government, initiate a ninety (90) calendar day contract phase-out period.

5.6.1. Joint Inventory. The contractor shall prepare GFP inventories IAW FAR Part 45 and

DAFFARS Part 245 (PGI 245.201-71) and participate in a formal transfer of all GFP to the successor that fully accounts for all assets. Participate in a joint walk-through inventory with the successor to confirm GFP inventory.

5.6.2. Transition Travel. The contractor shall Accomplish all travel required to support the sixty (60) calendar day transition out period, IAW FAR 31.205-46. NOTE: The Phase-In /

Phase-out requirements listed above can change and be updated based on current needs and determined appropriate by the Government.

5.6.3. Additional Transitional Requirements. The Government reserves the right to remove and add other performance requirements for transitions at any installation/locations based on future requirements that shall be negotiated through a bilateral modification and in support of the DoD.

Page | 19 of 26

SECTION 6

SERVICES SUMMARY

6.0. SERVICES SUMMARY (SS). The SS identifies critical success factors for the contract.

The SS performance objective or assessment items may be included with each task order. The

SS is a list of performance objectives and performance thresholds that Government personnel verify IAW the QASP and could result in a major finding if the performance threshold is not met. Each performance objective represents a significant task as identified in the PWS by the

Government at the time of contract award. The performance threshold represents the minimum acceptable level of performance. The performance objectives and performance thresholds represent the most significant tasks of this contract.

6.1. PURPOSE. The SS lists performance objectives for the required services the Government will surveil. The absence of any contract requirement from the SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract including the clauses entitled “Inspection of Services” and “Default.”

6.2. COMPONENTS. The SS states the performance objective (required service), and threshold (performance standard, accept and reject points (if applicable) in either a qualitative or quantitative fashion) for each critical success factor.

6.3. QASP. The SS will be used as the baseline to develop a Government QASP. The QASP will identify the audit methods and procedures the Government will use to evaluate the

Contractor's performance.

6.4. RIGHT TO SURVEIL. The Government reserves the right to surveil all services and requirements called for in this PWS and those issued with task orders to determine whether the contractor is meeting performance objectives and goals.

6.5. MEASUREMENT, ANALYSIS, AND IMPROVEMENT (MA&I).

6.5.1. Quality Assurance. According to the Inspection of Services clauses, the Government will evaluate the contractor’s performance under this contract. The Government will use compliance and management audits to verify and validate contractor performance to the PWS.

The primary compliance audit surveillance tool is the COR and Contractor Performance

Assessment Team (CPAT) audit. The Government may decrease or increase the scope and frequency of contract performance evaluations based on the contractor’s past performance, risk assessment, and level of confidence provided by contract performance.

6.5.2. Evaluations. Government audits will be performed on a periodic basis. At contract start the Government will schedule/perform audits. If contractor performance to specified requirements is exceptional and provides sound confidence and a “low” risk level, then

Government contract evaluations may be reduced in scope and frequency. If contractor performance of specified requirements significantly reduces confidence and raises risk to the

“high” level, then the Government may initiate a more in-depth systems audit on the contract

Page | 20 of 26 requirement that is in violation of specified requirements.

6.5.3. Major Non-Conformance. A non-conformance that adversely impacts (or has the potential to) mission, safety of personnel and/or equipment, environment, performance

(quality), schedule (delivery), and/or cost. The CO will communicate major non-conformances to the contractor using a Corrective Action Request (CAR) form with a suspense date for the contractor’s corrective action plan.

As a minimum, the contractor’s action plan will address:

(1) Action taken to fix the problem (correction)

(2) Root cause analysis of the problem

(3) Corrective action on the cause of the problem

(4) Actions taken to prevent recurrence to include the follow-up plan (how and when)

(5) Action(s) required by the Contractor’s Quality Plan

(6) All supporting evidence to support actions taken such as updated manuals, instructions, procedures, etc. Embed supporting evidence in this section to maintain a single point document unless size is restrictive of security policies prevent embedding.

In these cases, provide location of the documents.

6.5.4. Minor Non-Conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance

(quality), schedule (delivery), or cost. Minor non-conformances are communicated through

Notices; First Notices are issued for any identified minor nonconformance, Second Notices are issued for repeat minor non-conformances or failing to correct minor non-conformances within a reasonable amount of time. A formal corrective action plan is not required for Notices.

6.6. PERFORMANCE OBJECTIVES/THRESHOLDS. Performance objectives may be added or deleted, and performance thresholds raised or lowered during the course of this contract. For example, repeated contractor performance deficiencies in non-critical areas may force the related requirement to become a performance objective in the SS. Conversely, changes in technology or mission requirements may eliminate SS objectives. Performance

Objective Thresholds may be defined in each task order.

Page | 21 of 26

SECTION 7

CONTRACT ADMINISTRATION

7.1 GENERAL

This section provides contract administration requirements, and where applicable for each task order placed under this Master ID/IQ. Costs associated with these administration requirements shall not be billed as a direct cost to the Government. Future task orders will be negotiated separately and proposals will be provided based on COs direction.

Additional contract administration requirements may be specified in each task order.

7.1 AUTHORIZED AGENCIES

The Master ID/IQ is available for use by the Space Administration and Integration Officer

(SAIO) only.

SAIO Address:

SpOC SAIO/PMO

135 Dover Street, Building 350

Peterson SFB, CO 80914

7.3. ROLES AND RESPONSIBILITIES

7.3.1. GOVERNMENT PROGRAM MANAGEMENT (PM) AND CONTRACT

MANAGEMENT. The SpOC Space Acquisition and Integration Office (SAIO) provides program, contract, and quality management execution of the contract. The USSF and SpOC set the requirements and the Department of the Air Force (DAF) Program Executive Office (PEO) is the Services Acquisition Decision Authority (SADA) as defined in AFI 63-138, Acquisition of Services. Contracting officer representatives (CORs) are located at each site and are responsible for all contractual technical issues. The CORs and the Contracting Officer (CO) are the primary interface to the contractor. The CO is the only individual with the express authority to obligate the Government and negotiate contract changes. The assigned CORs, with Subject Matter Experts (SMEs), are responsible for surveillance of the contractor using the criteria outlined in the PWS and the Government Quality Assurance Surveillance Plan

(QASP).

7.3.2. MULTI-FUNCTION TEAM (MFT). A team of stakeholders responsible for a service acquisition. The MFT is a customer-focused team instituted under the authority of senior leadership and responsible for assessing contractor performance and managing the requirement over the life of the contract. The goal is to develop, implement and execute a performance management assessment program that satisfies mission requirements, fosters innovation, and includes defined metrics.

Page | 22 of 26

7.3.3. MFT Objective. The objective of the MFT is to define the requirement in performance-based terms, ensure contractor compliance with contract requirements and ensure the contract as written continues to meet the overall mission needs. The role entails planning, programming, and budgeting for adequate funds, ensuring program execution within the approved funding and to ensure the contract supports mission requirements within the approved scheduled baseline.

7.3.4. MFT Members. Core MFT members for this contract are the PM, CO, Contracting

Specialist (CS) and Quality Assurance Manager (QAM). The full MFT consists of Core MFT members, Functional Commanders (FC), COR, the contractor and SMEs from various functional areas covering all program service requirements as needed. Membership may also include Legal, Small Business, Labor Relations, management and leadership of various organizations or any other functional experts such as Mobile Contracting Officer’s

Representative (MCOR), for whom the MFT has a need. Member participation is contingent upon contract issues requiring a particular MFT member’s participation. Contractors are part of the MFT and will be required to attend scheduled MFT meetings.

Page | 23 of 26

ACRONYMS

ACRONYM DESCRIPTION

24/7 24 hours a day, 7 days a week

ACA Associate Contractor Agreement

AFB Air Force Base

AFI Air Force Instruction

AFMC Air Force Materiel Command

AK Alaska

AMC Air Mobility Command

AQ…