STARCOM PWS STAR FO-DRAFT.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

STAR Follow On

27 August 2025

Delta 11

Template AO: HQ STARCOM/ES

STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD Contractors only;

administrative/operational use; 13 August 2021. Other requests for this document shall be referred to HQ STARCOM

Business Operations.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title22, USC, Sec 2751, et. seq.) or the Export Administration Act of1979, as amended, Title50,USC., App. 2401,et.seq.

Violations of these export laws are subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

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

Commented [MH1]: Will be updated.

ii

CHANGE CONTROL SUMMARY

Revision (Rev). A revision should be used to consolidate all changes into a new basic document with a new basic date. It should be used to clean up the document when it begins to become confusing with too many changes. It is the Data Managers (DM) decision when to revise the document. Number the revision and include a summary of the revisions in the change table. DM will remove all change bars when the document is revised since the revised document takes all previous changes into account. Do not remove changes from the change table when the document is revised since they may lend important historical value.

Version (Ver). A change that is administrative in nature does not require the document to be re-staffed.

Changes that remove or add items periodically assessed or affect items assessed in frequency of assessment or thresholds must be re-staffed for approval. Consolidate changes when possible. Include a summary of the changes incorporated in the change table. Ensure change bars have been inserted after initial release.

Rev./Ver. Eff. Date Description

A dd Apr 24 Final RFP Release.

Commented [MH2]: Will be updated once first draft is complete iii

Table of Contents

1 Introduction/Background

1.1 Mission Overview

1.2 Scope

2 General Requirements

2.1 Non-Personal Services

2.2 Contractor Management

2.3 Contractor Personnel, Disciplines, and Specialties

2.4 Location and Hours of Work

2.5 Travel / Temporary Duty (TDY)

2.6 Security and Safety

2.7 Manpower Reporting

2.8 Documentation

2.9 Performance Evaluation

2.10 Government Furnished

3 Performance Requirements

3.1 Space Aggressor EW Support

3.2 Space Aggressor OW Support

3.3 Space Cyber Range Support

3.4 Transition

3.5 Associate Contractor Agreements (ACA)

3.6 STARCOM Directed Meetings/Events

4 Applicable Publications

5 Deliverables

6 Services Summary

Appendix A: Mission System Inventory Descriptions

Attachment 1 – Government Furnished Property

Attachment 2 – Government Furnished Material

STAR FO PWS

Performance Work Statement (PWS)

1 Introduction/Background This Performance Work Statement (PWS) outlines the requirements for providing comprehensive support to the 527th Space Aggressor Squadron (527 SAS), the 57th Space Aggressor Squadron (57 SAS) and the 33rd Range Squadron (33 RGS) in their respective missions to prepare Joint Forces and Coalition Partners for operations in contested space environments. As key components of the United States Space Force's (USSF) mission qualification and professional adversary force, these units require robust support to effectively execute their missions and enhance their ability of replicating the threat, ultimately ensuring allied victory in the space domain. This PWS defines the specific tasks and deliverables required to enable all three units to achieve these objectives.

1.1 Mission Overview

To prepare Joint Forces and Coalition Partners for operations in contested space environments by providing realistic, relevant, and integrated space threat replication and support to the 527 SAS, 57 SAS and 33 RGS.

1.2 Scope

This contract will provide non-personal services through subject matter experts in the following areas:

SATCOM, EA, GPS EA, Offensive Cyber Operations (OCO), intelligence product generation, and OW.

This includes support to mission planning, system support, development, testing, maintenance, education, mission qualification, and training of Space Aggressors.

Support includes programs identified as Sensitive Compartmented Information (SCI) and Special Access Required (SAR) administered under the enhanced security guidelines & procedures authorized by Department of Defense DODI 5200.01 (DoD Information Security Program and Protection of Sensitive Compartmented Information) and AFI 16-1404 (Air Force Information Security Program).

Future work options are included to provide flexibility in adapting to evolving mission requirements driven by the anticipated growth of supported units. These options encompass potential future tasks, services, and capabilities that may become necessary to maintain optimal support and performance as the operational environment expands. Exercise of these options will be subject to mutual agreement, incorporating factors such as evolving mission needs, technological advancements, and available resources. This mechanism allows for proactive and agile adaptation of the contract to ensure continued effective support to the growing user base and to seamlessly integrate emerging requirements without the need for extensive renegotiation.

Identify if this requirement includes any Mission Essential Services, submission of ME plan IAW

DFARS 252.237-7023

2 General Requirements This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

The Period of Performance is as follows:

Base Year: Contract start – 31 Oct 2027 OY1: 01 Nov 2027 – 31 Oct 2028 Optional Extension up to 6 Mos: 1 Nov 2028 – 30 Apr 2029 (only for emergencies)

2.1 Non-Personal Services

The government will not supervise contactor employees or control the specific methods by which the contractor performs the required tasks. The government will not assign tasks to individual contractor employees or prepare their work schedules. However, to ensure clarity, facilitate effective communication, and align efforts with mission objectives, the government may provide amplifying guidance and intent related to specific project, tasks, or sections within the 527 SAS, 57 SAS, and 33rd RGS. This guidance will primarily be directed at contactor management and task leads. However, government personnel may engage directly with contractor employees involved in specific projects to discuss technical matters, clarify requirements, and provide feedback on work in progress. These interactions are intended to enhance understanding and collaboration and should not be construed as direct supervision or task assignment. The contractor remains responsible for managing its employees, assigning tasks, and determining the appropriate methods to achieve the required outcomes.

The contractor shall ensure its employees understand the prohibitions imposed on the government regarding personal services contracts. The contractor shall manage its employees and 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, the contractor shall notify the Procuring Contracting Officer (PCO) immediately

2.2 Contractor Management

The Contractor shall integrate and coordinate all activity needed to satisfy the requirement. The Contractor shall manage the timeliness, completeness, and quality of problem identification, and resolution, as applicable. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all Contractor personnel. If the Contractor has any proposed revisions to this PWS or any other contract attachment, for the purpose of making the documents more accurate (regulatory changes) or complete (for clarity), the Contractor shall submit suggested revisions as word document with tracked changes and a change request to the COR and CO for consideration.

The Contractor shall provide a Monthly Status Report (MSR) covering activities of the preceding month.

Deliverable AA01 – Monthly Status Report (MSR)

2.2.1 Contract Administration

The Contractor shall ensure its personnel do not perform inherently Governmental activities, as defined in FAR 7.5. The Contractor shall ensure its personnel do not attempt to represent the Government of the United States (US) to any other person or entity, US, or foreign, except for delivering a Government-approved message or position. All briefings, policies, plans and other formal products the Contractor develops, reviews, and creates, will be reviewed and approved by the Government.

2.2.2 Contractor POC

The Contractor shall have a single point of contact between the Government and Contractor personnel assigned to support this contract. This lead shall coordinate with the Contracting Officer’s Representative (COR) to obtain and clarify contract requirements and shall be responsible for the daily control and supervision of the Contractor’s employees.

2.2.3 Personnel Administration

The Contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements. The Contractor shall obtain approval from Government prior to attending Government-provided training classes. Provided there is no cost to the Government, the Contractor may be eligible to attend Government-sponsored and Government-provided training to maintain proficiency in software, administrative procedures or other areas. Additionally, provided there is no cost to the Government, the Contractor may be eligible to attend third-party-provided off-site seminars and classes.

To enhance performance and support the 527th SAS mission, the contractor may request approval for its employees to attend government sponsored, or government provided training session focused on software, administrative procedures, or other directly relevant areas. The contractor may also request approval for employees to attend third party provided off site seminars and classes that directly contribute to the contractor’s ability to fulfill the requirements of this PWS. All requests for training attendance must be submitted to the 527th SAS leadership (or their designee) for review and approval at least 140 business days prior to the scheduled event. Approval will be granted only if the training demonstrably enhances the Contractor’s ability to support the 527th SAS mission, is offered at no cost to the government (unless otherwise approved in writing by the Contracting Officer or Contracting Officer Representative), and aligns with the overall training objectives of the 527th SAS. The contractor bears the responsibility for any costs associated with unapproved training.

2.2.4 Contractor Identification

Contractor employees shall clearly identify themselves as “Contractors” at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other Contractor personnel, or with the public. Contractor personnel shall wear a readily visible badge that clearly identifies them as Contractor employees.

Deliverable AA02 – Contractor Personnel Roster

2.3 Contractor Personnel, Disciplines, and Specialties

The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The Contractor shall ensure the labor categories, labor rates, and man-hours utilized in the performance of each Task Order (PWS line item) issued hereunder will be the minimum necessary to accomplish the task. The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract. The contractor shall provide three task leads to oversee, support, and assisting in EW/OW and Cyber services working as teammates.

2.3.1 Personnel Turnover

The Contractor shall ensure continuity of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal. Once the Contractor knows an employee will no longer support the requirement, the Contractor shall provide written documentation to the CO and COR within three (3) business days. In this notification, the Contractor shall include the date and time the position will be vacant, anticipated fill date, and what management actions the Contractor will take to ensure uninterrupted performance.

Position vacancies shall not exceed 14 calendar days unless approved in writing or otherwise directed in advance by the CO (e.g. a grace period associated with new awards and PWS modifications, increasing the number of personnel on a task order).

2.3.2 Removal of Personnel at Government Request.

The Government may request removal (permanent or temporary) of personnel for security, safety, or health reasons, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person. Additionally, the Government reserves the right to request the removal and replacement of any Contractor personnel whose performance, attendance, or lack of responsiveness demonstrably hinders the 527th SAS mission. This includes, but is not limited to, instances of: (a) documented and repeated unavailability during scheduled work hours; (b) failure to provide timely and accurate information regarding project status or whereabouts upon request; (c) repeated failure to meet agreed-upon deadlines; or (d) any other behavior that negatively impacts the Government’s ability to effectively execute its mission. In such cases, the Government will provide written notification to the Contractor, outlining the specific concerns. The Contractor shall provide a replacement within 14 business days of the notification. The Government's decision regarding removal and replacement is final and not subject to protracted legal challenges, provided the removal is based on a good-faith assessment of the Contractor’s personnel's impact on mission effectiveness.

2.4 Location and Hours of Work

The primary work location under this PWS is anticipated to be at Bldg. 815 and 24 on Schriever SFB, and at various Contractor and Government facilities. However, the Government reserves the right to designate alternate work locations, including other Government facilities or approved Contractor sites, as necessary to support mission requirements. The Contractor shall comply with all Government directives regarding work location. The Government will provide reasonable notice to the Contractor of any changes to the primary work location, except in cases of urgent operational needs, where shorter notice may be required. The Contractor shall generally support a normal work week of 40 hours per week. Normal workdays are eight (8) hours per day, Monday through Friday, except US Federal Holidays. Mission requirements may be dictated other than Monday through Friday. The units may need to take basing actions, for example the 57 SAS is schedule to work from Kirtland AFB, NM starting in CY27.

2.4.1 Building Access

The Government will provide Contractor personnel unescorted access to Bldg 24 consistent with task requirements. Access to Government facilities, documents and systems will be in accordance with the DD Form 254 and paragraph 2.6.

2.4.2 Morale Events

There may also be occasions when Contractors are invited to participate in morale and recreational activities (e.g., holiday parties, golf outings, sports day and other various social events). Under these circumstances, Contractor employees shall comply with individual company policy in accordance with company compensation system. Because the Government does not have an employer/employee relationship with Contractor employees, it is not authorized to grant administrative leave or expend Government resources to compensate Contractor employees for hours expended on activities not included in the PWS.

2.4.3 Closures

For closures affecting the availability of the Government site (e.g., weather closures, a National Day of Mourning, etc.), the Government will notify the Contractor through normal means such as the Snow Call Line and local news outlets, or via email from the COR or CO. During such closures, Contractor personnel may telework if they have a COR-approved telework request in place and coordinate with the assigned section.

2.4.4 Teleworking Commented [MH3]: Need to look at this when

compared to the old PWS

Telecommuting/telework is defined as authorization for an employee that works at the United States Government (USG) location, to work at an alternate location, i.e., at the employee’s home or Contractor location, either routinely or situationally. Contractor-designated location is defined as a contractor-identified place of performance for specific employees, i.e., not at the USG location. There are two types of telecommuting/telework; 1) routine telework in which telework occurs as part of an ongoing, regular schedule within the designated installation operating location area, and 2) situational telework that is approved on a case-by-case basis, where the hours worked were not part of a previously approved, ongoing and regular telework schedule, to include pandemic situations and remote telework (teleworking outside the operating location area), and other non-routine telework situations.

Either telework option will be concurred by Government requirements owners and submitted to the COR. Routine telecommuting/telework will be approved by the COR or the location specific alternate COR. Situational telecommuting/telework requests will be approved by the CO. To obtain approval for teleworking, the Contractor shall submit a teleworking request with appropriate rationale in writing. This request shall include the Contractor’s [“lead’s”, “Project Manager’s”, “Task Lead’s”, etc.] approval, as well the primary Government customer’s approval, if different than the COR, when the request is submitted to the COR for approval.

Telecommuting/telework is generally customer-specific, and all telework approved equipment must be authorized by the Government for use. Regardless of work location, the Contractor shall maintain availability during core hours via e-mail, Government approved video conferencing, and phone. The Government will not assume operating costs associated with the Contractor using an alternate worksite; all telecommuting/ telework expenses for Internet, telephone connectivity, and other equipment services shall be borne by the Contractor. Any costs related to maintenance required for remote telework Government Furnished Equipment not due to negligence, to include shipping costs (if required), will be paid by the Government. The Contractor shall provide a written request with appropriate rationale for COR or alternate COR approval prior to any telecommuting.

Teleworking is not authorized for classified work. Authorized telework locations do not abrogate the Contractor’s requirement for complying with the protection of information IAW DoD, USAF, and USSF regulations, Security and Protection of Information sections of this PWS, contract clauses or the DD Form 254.

2.5 Travel / Temporary Duty (TDY)

Travel may be required inside the Continental United States (CONUS) and Outside the Continental

United States (OCONUS) on a temporary basis to accomplish the mission. All travel will be at the direction of the Government and reimbursed/accounted for as part of the FFP NTE travel Contract Line-

Item Number (CLIN). Approximately 100 days of travel is required per year.

Any travel required to fulfill the tasks within this PWS shall be performed IAW the Joint Travel

Regulation (JTR) is not subject to profit and must be initially coordinated with the COR prior to approval. The Contractor shall submit requests and obtain Government approvals for all travel prior to purchasing refundable tickets. Travel will be for purposes such as exercise and mission support and indicated in paragraph 3 of the PWS. The Contractor shall include estimates for all allowed travel costs.

If some authorized costs are not included in the request, the Contractor shall state the reasons why the costs are not included in the estimate and invoice. The Contractor shall provide receipts for all expenses incurred and shall follow the JTR. Local area travel is not reimbursable. Local area is a 150-mile radius of Schriever AFB. Any remaining funds will be de-obligated to the buying activity.

Commented [MH4]: This needs to be compared to the old PWS

Deliverable:

AA03 Travel Report For all trips, the Contractor shall provide a trip report within ten (10) business days of the return date from travel. Extensions may be granted by the COR on a case-by-case basis. As a minimum, trip reports will include the objectives and outcomes of the trip. Trip reports do not have a specific format and may range from an email to a formal presentation depending on the type of trip.

2.6 Security and Safety

2.6.1 Facility Clearance

The contractor shall possess or obtain a facility clearance at the classification levels specified in the workload data.

The contractor shall apply for personnel security clearances within five days after receipt of the facility clearance or within 30 days after award of the contract if the contractor possesses a facility clearance.

The contractor shall comply with all Schriever Space Force Base (SSFB) and USSF security requirements. SSFB contains a restricted area and Bldg. 24 is a controlled area. In both areas special security procedures are used to deter espionage, sabotage, and theft of USAF/USSF resources. The contractor shall be responsible for security of their work areas in cooperation with applicable base agencies.

The contractor shall be advised that vehicles entering or leaving SSFB are subject to search by the

50th Security Forces Squadron (50 SFS) at their discretion. Drugs, firearms, or other weapons are strictly prohibited and not allowed on SSFB. If found, the individual may be barred from future entry, impacting the contractor ability to meet requirements.

The contractor shall be responsible for all costs incurred by the contractor associated with security requirements including submission of necessary security investigation paperwork, routine entry/exit delays, and operational delays due to contingencies or exercises, are to be anticipated by the contractor.

The contractor shall initiate unescorted entry authorization requests no later than 7 calendar days after their start date, if access to restricted/controlled areas is required IOT perform the tasks described in this PWS, The contractor shall, always, display restricted/controlled area badges on their outer garments above the waist when inside the restricted/controlled area, Contractor personnel shall remove and secure the restricted/controlled area badge immediately upon departure from the restricted/controlled area to prevent loss. Incidents of a person not properly displaying badges or violating escort procedures (e.g., working out of view of escort) shall be treated as a breach of security and that person shall be susceptible to apprehension, search and detainment. Any person inside a restricted/controlled area without a restricted/controlled area badge will be detained or apprehended, searched, removed, and turned over to appropriate authorities for disposition.

Commented [MH5]: Keep, but clean up

Commented [MH6]: This section needs to be checked with the old PWS

If the contractor is not issued a Restricted Area Badge (RAB) they shall be issued a visitor badge and will be under direct surveillance, at all times, of a USG/Contractor employee possessing a restricted/controlled area badge with escort authority if the contractors require escorted entry.

The contractor shall comply with all applicable security regulations including the restricted/controlled area badge which shall only be valid for the contractor’s term of employment or for the duration of the contract, whichever is shorter. Upon contractor termination, the contractor shall surrender the CAC and restricted/controlled area badge to 527 SAS Security Manager within one business day. The contractor shall immediately report the occurrence of any lost badge to the 527 SAS Security Manager and COR within one workday of loss. If 527 SAS Security personnel are not available, the contractor shall report the loss directly to 50 SFS within one workday of loss. The contractor shall not be issued a replacement badge until reporting procedures are satisfactorily completed.

The contractor shall be advised that delays can be anticipated at the entry control point each time an individual enters the restricted/controlled area. These delays are a routine matter when the 50 SFS and/or USAF/USSF search vehicles, hand carried items, check badges, and credentials.

The contractor shall be responsible for protection of USG information, property, equipment and resources that are generated, issued, or supplied under the terms of this contract IAW DoDM

5220.32V2 _AFMAN16-1406V2, National Industrial Security Program: Industrial Security Procedures for Government Activities, and AFMAN 16-1404 V1-3, Air Force Information Security Program.

The contractor shall enter into a security agreement with the SAFB installation commander. This agreement shall be directive on the contractor. The contractor shall coordinate security matters with the 527 SAS Security Manager and P-S GAR/IP (Schriever). Each eligible contractor employee shall personally report to the 527 SAS Security Manager for completion of the AF Form 2586, Unescorted Entry Authorization Certificate. Contractor employees shall not be allowed unescorted entry to SSFB secured area/buildings until these procedures have been completed. Site activities shall operate with notification of WG/IP and adherence to all guidance

2.6.1 DD Form 254

The contractor shall be provided access to applicable USG facilities. The contractor will be allowed non-escorted access to Government buildings on Schriever SFB, and other sites consistent with task requirements. Access to Government facilities, documents, and systems shall be in accordance with (IAW) the approved Department of Defense (DD) Form 254 – Contract Security Classification Specification, Department of Defense. Employees are subject to all regulations and directives governing the activities of personnel on Government installations, as well as all health and safety directives imposed.

The contractor security manager shall coordinate with the 527 SAS security manager to obtain access and badge information.

The contractor shall coordinate with the Contracting Officer’s Representative (COR) to ensure there is no interference with current operations during the transition period and until facility access is granted.

The contractor shall fully participate in all PS-G or Higher Head Quarters (HHQ) directed exercises/inspections to the level dictated by the scenarios in progress. The contractor shall fully participate in all host base exercises and inspections, except as determined by the PS-G commander.

This support will be required on a non-mission interference basis during normal contractor duty hours.

The contractor shall not increase manpower or man-hours during exercise participation unless specifically stated in this PWS or authorized by the CO.

2.6.2 Security and Training

The contractor shall identify an individual to perform the duties of Security Manager who shall obtain appropriate personnel security clearances for employees. The Security Manager shall coordinate with

527 SAS Security Manager on all security related issues.

The contractor shall possess a facility clearance at the classification level of “TS” IAW the DD254 at the time of contract award.

All contractor personnel shall have all the clearances as required in DD254. Contractor employees whose duties require access to restricted areas or classified information shall possess a minimum of

Secret security clearance unless otherwise noted. The maximum-security level is TS/SCI. 527 SAS will provide additional security clearance information as required.

The Contractor shall comply with the DD Form 254 security requirements. See the DD Form 254 for

OPSEC, COMSEC and NATO requirements and guidance.

At a minimum, the contractor shall complete the following courses via the MyLearning on-line access, or classroom attendance within 30 days after contract award. The contractor shall also comply with all required 527 SAS security procedures training. Other training may be required at the direction of the

COR.

Course Frequenc y

Method

a. OSI/Counterintelligence (INTEL) Brief Annual Classroom

b. DoD IAA Cyber Awareness Challenge Annual MyLearning

c. Restricted Area Escort Training Annual CBT

d. Derivative Classification Annual CBT

e. Insider Threat Awareness Annual CBT

f. Unauthorized Disclosure of Classified Information and CUI Annual CBT

Contractor must comply with foreign travel training required by location as stated in the DoD foreign travel guide (https://www.fcg.pentagon.mil/fcg.cfm)

Contractors may request Antiterrorism Level I training from a 50 SW certified Anti- Terrorism Officer

(ATO). Should the contractor choose to complete this training, they must make their request to the 527

SAS COR and the 527 SAS COR will coordinate training locations and times with the installation

Antiterrorism Program Manager. Regardless of training, contractors will report suspicious activity to

Security Forces (567-6464) or the AF Office of Special Investigations (554-2822).

https://www.fcg.pentagon.mil/fcg.cfm

After contract award, if any of the Government-provided mission support systems change, or new systems are added, the Government will provide initial training upon approval of the COR and direction of the CO. The contractor shall attend training as approved by the COR and directed by the CO. After initial training is completed, the contractor shall be responsible for re- training and training new contractor employees.

The contractor shall attend other training for support provided. This other training includes mission support, geographical-specific, security policy, new equipment, etc. Other training includes 527 SAS provided Mission Qualification Training (MQT), Crew Chief Upgrade Training and instructor qualification. This training will start at phase-in and will be completed within 45 days after contract award.

The contractor shall ensure their employees stay current and proficient in their areas of responsibility.

The contractor shall ensure personnel accessing information systems in the performance of this contract have proper and current cybersecurity certifications to perform support functions IAW DoD

8570.01-M, Information Assurance Workforce Improvement Program and AFMAN 17-1303, Cybersecurity Workforce Improvement Program. The contractor shall authorize certification release for all applicable personnel, whenever a certification is issued or renewed, to DoD/DMDC via https://www.dmdc.osd.mil/milconnect.

2.6.3 Controlled Unclassified Information (CUI)

The Contractor shall safeguard all information provided and marked as CUI via this contract IAW DoD Instruction (DoDI) 5200.48, Controlled Unclassified Information (CUI). If the Contractor generates any CUI information, it shall protect and disseminate that information per the controls required by DoDI

5200.48. The Contractor shall monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. The Contractor shall immediately report the potential classification of aggregated or compiled CUI to the CO and the COR. The Contractor shall safeguard unclassified nonpublic information by applying specified network security requirements, as defined in DoD Instruction 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information, which includes identified CUI and Federal Contract Information that resides in or transits contractor unclassified information systems.

2.6.4 Special Access Programs (SAP)

Access to special access programs (SAPs) and Alternative Compensatory Control Measures (ACCMs) is required. The Contractor’s assigned personnel shall have been granted a final TOP SECRET security clearance with eligibility for access to Sensitive Compartmented Information (SCI) and have previous experience working Special Access Programs (SAPs). All personnel are required to submit a SAP Pre-Screening Questionnaire (PSQ) in accordance with DoDM 5205.07 V2 to the Government Program Office and follow procedures outlined in DODM 5200.01 Volume 3. Personnel will be required to consent to and successfully complete a Government Counterintelligence Scope Polygraph. Requests for waivers of SAP experience must be submitted in writing; the Contracting Officer will provide a decision on the request within six (6) working days. Government security officers will determine whether prospective personnel meet the personnel security requirements for any task.

2.6.5 Personnel Security Program

Commented [JT7]: Title 32 of the Code of Federal Regulations (CFR) § 2002 describes requirements for adequate safeguarding that, in the context of Defense contracts, are implemented through Defense Federal Acquisition Regulation Supplement (DF ARS) clause 252.204-7012, Safeguarding Covered Defense Information and C)iber Incident Reporting. This clause applies to contracts that require the processing, storing, or transmitting of CUI on contractor-owned information systems.

Upon publication of the final Title 48 CFR DFARS rule, 20 I 9-D04 I, Program Managers and requiring activities shall include the need for Cybersecurity Maturity Model Certification assessments in procurement request and requirement documents in accordance with phase-in timelines described in Title 32 CFR § 170.3. (See embedded doc at the end of the template)

Commented [JT8]: Add ref to Department of Defense Manual (DODM) 5200.01 vol 3 in para 4.

http://www.dmdc.osd.mil/milconnect

The Contractor shall establish and maintain a personnel security program to support the contract. The Contractor’s assigned personnel shall establish and maintain eligibility for access to TOP SECRET Sensitive Compartment Information (SCI) and participate in the Government Counterintelligence Scope Polygraph Program. Government security officers will determine whether the Contractor’s personnel meet the personnel security requirements for the tasks under this contract; no costs will be reimbursed related to providing personnel who fail to meet the security requirements.

2.6.6 Non-Disclosure Agreements (NDA)

The Contractor’s assigned personnel shall complete and sign Non-Disclosure Agreement(s) (SF-312) regarding protection of sensitive Government and third-party Contractor information.

Deliverable:

AA04 – Non-Disclosure Agreement

2.6.7 Communications Security (COMSEC) Monitoring

Telecommunications networks are continually subject to interception by unfriendly intelligence organizations. All communications within DoD organizations are subject to Communications Security (COMSEC) review. The Government may conduct COMSEC monitoring and recording of electronic or voice communications originating from or terminating at DoD organizations at any time. The Contractor shall ensure all assigned personnel are aware that any time they communicate to or from a Government facility, they are subject to COMSEC procedures. The Contractor shall ensure wide and frequent dissemination of the above information to all employees dealing with Government information.

2.6.7 Counterintelligence Cooperation

Attend mandated CI briefs/events.

2.7 Manpower Reporting

In accordance with FAR 52.204-14 Service Contract Reporting Requirements, the Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor shall fill in all required data fields at the data collection site. Use the following web address: www.sam.gov.

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, the Contractor shall report all data no later than October 31 of each calendar year. Contractors may direct questions to the System for Award Management (SAM) help desk.

2.8 Documentation

The Contractor shall make all information and documentation generated or maintained (to include Government-furnished documents) by this contract available for Government review upon request for the duration of the contract. The Contractor shall generate and maintain all such documentation in an electronic, editable (where appropriate) format. Contractor-generated format is acceptable, unless otherwise noted by this PWS.

The Contractor shall provide responses to requests for information. These requests are in addition to Deliverable submissions and other documentation that is available for review by request. Requests may cover the range of activities under this PWS.

2.8.1 Documentation Rights

http://www.sam.gov/

The Government has unlimited rights to data for all deliverables developed under this PWS. The Contractor shall not use any materials pertaining to this contract for business development or any other Contractor purposes; however, the Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements.

All products developed and produced by the Contractor in the performance of this PWS are the property of the Government, and this could include software, electronic files, hard copy documents, etc.

Rights to all documentation are governed by Defense FAR Supplement (DFARS) 252.227-7032, Rights in Technical Data and Computer Software.

2.8.2 Government Data

The Contractor shall request Government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract. The Government will provide the Contractor access to information required to accomplish assigned tasks commensurate with security clearance and on a need-to-know basis. The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the Contracting Officer.

2.9 Performance Evaluation.

Contractor performance is subject to Government surveillance to ensure PWS compliance. The Contractor shall comply with the following:

Access. The Contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The Contractor shall provide support, and not interfere with the CO, Contracting Officer’s Representatives (CORs), state, federal, and other designated personnel in the performance of their official duties. The Contractor shall provide access as soon as possible, but not to exceed one (1) workday after the request.

Non-conformance. The Contractor shall identify root causes of non-conformances and shall control them through analysis, corrective actions, and preventive actions. The Contractor shall focus on eliminating the cause to prevent reoccurrence. The Contractor shall maintain records of non-conformities and actions taken. The Contractor shall correct and provide responses to all Government-identified non-conformances in accordance with (IAW) time frames specified by the CO. There are two types of non-conformances: Minor and Major.

Minor Non-conformance. A Minor Non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Minor Non-conformance does not normally increase risk to the Government.

Minor Non-conformances are typically low risk and are communicated through a Corrective Action Request (CAR) notice. First notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time.

Upon receipt of a non-conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan may not be required for minor CAR notices.

Major Non-conformance. A Major Non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Major Non-conformance may also be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures or actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs.

The CO will communicate Major Non-conformances using the CAR notice and will include a suspense date for the Contractor’s Corrective Action Plan. As a minimum, the Contractor’s Corrective Action Plan shall address:

• Actions taken to fix the immediate problem

• Root cause analysis of the problem to determine cause

• Corrective action on the cause of the problem

• Actions taken to prevent recurrence

2.10 Government Furnished

The Government will make available the materials, office space, communications capability and information for use by the Contractor in the performance of this contract.

2.10.1 Government Furnished Property (GFP).

The Government will not provide any GFP for Contractor use on this contract.

2.10.2 Government Furnished Resources.

The Government will furnish up to workspaces in the MSF, Bldg 24, Bldg 815, & Bldg 442 associated desks, chairs, computers connected to internet, use of telephones, copier and fax machines. Any equipment is considered incidental to performance location.

2.10.3 Government Furnished Information (GFI)

Government staff personnel will be available for technical exchanges with the Contractor. Government personnel will provide technical input, answer questions, review and approve completed work, and provide feedback regarding Contractor efforts. The COR is the primary source of technical guidance for this PWS.

3 Performance Requirements The following section specifies the Performance Objectives and Performance Elements for the contract.

Acceptable Quality Level (AQL) is a tolerable variation in the execution of a PWS Standard.

3.1 Space Aggressor EW Support

3.1.1 Intel

Research and network system subject matter on intelligence community Information Systems (IS), (i.e.

Joint Worldwide Intelligence Communications System (JWICS)) to create and present briefings and white papers to Air, Space, and Cyberspace operations professionals.

Create and present weekly classified intelligence briefs focused on space and space control activities conducted by U.S. adversaries over the period of interest. The briefings shall include a technical analysis of the tactics, system, and operator proficiency demonstrated by the adversary during the observed operation. 527 SAS will provide slide format to be utilized for content.

Provide intelligence briefings, instruction, and advisory support to various training for SAS operators and external customers. This shall include specific threat briefings that are tailored to a specific training audience and their system.

Commented [MH9]: This needs to be updated

Commented [MH10]: We will need to review the verbiage after the initial draft to either avoid A&AS or put that into it’s own CLIN for review.

Commented [MH11]: Created w/AI. Needs thorough review.

Support exercise planning for Master Scenario Event List builds for threats to be injected into training with modeling and simulation. Travel may be required and will be conducted in accordance with PWS para 2.5.

Maintain a database of observed adversary TTPs, and mission systems to support creation and validation of Space Aggressor tactics. SIPR and/or JWICS will be utilized as the repository for this database. These TTPs shall be updated in the Space Aggressor Adversary Threat Replication Guide

(ATRG) and space threats brief quarterly.

Support the evaluation of new military systems and commercially available technologies for the potential threat(s) they may present to U.S./Allied forces. Travel may be required and will be conducted in accordance with PWS para 2.5.

Support threat intelligence community conferences, cross-talks, and Weapons School (Delta 1) syllabus reviews.

Develop/recommend implementation plans for applying intelligence information and procedures to SAS projects to support military training and exercises.

Attend conferences for exercise planning as requested by the Government. Examples include:

Deconfliction Conferences, Combined Force Space Component Command, J2 (Intelligence) conferences, NRO Threat Conferences, Space Control Working Group, etc.). Notify the Government

COR of scheduling conflicts for personnel to support missions/exercises/training as needed.

Performance Standards

a) Standard: The Current Intelligence Briefings shall include a technical analysis of the tactics, system, and operator proficiency demonstrated by the adversary during the observed operation IAW unit requirements and Intel Flight SOI.

b) Standard: Weekly CIB created and presented 90% of the time.

Deliverable

A001: Weekly Classified Intelligence Briefings on Adversary Space Activities

A002: Tailored Threat Assessments for Specific Training Audiences

3.1.2 Mission Planning

Support the planning and scheduling of exercises that contain SATCOM, ASN, Orbital Warfare, and

GPS EA. Note this list may not be all inclusive

Coordinate with training audiences identified by the Government to provide support request forms.

Process received support request forms and identify 527 SAS support requirements with training audiences (such as via teleconference). Provide Government with exercise details to enable 527 SAS to adjudicate exercise and event support and its extent; provide recommendation on 527 SAS support based upon personnel and equipment availability, prioritization based on higher headquarter guidance, and feasibility.

Schedule and notify 527 SAS members for exercises and events based on their availability and certification

Update Government documents and trackers with information on upcoming exercises and events, both approved and pending; synchronize and inform 527 SAS members with updated information on upcoming exercises and events, both approved and pending.

Create and support the drafting/staffing/tracking of exercise approval packages. Government review and approval is required before submission to external agencies. Note: staffing packages typically require a long lead time to ensure approvals are received prior to mission need date.

Support drafting/staffing/tracking of GPS EA requests. Produce GPS RPM interference contours and

GIANT Jammer to Signal ratio (J/S) contour plots. Utilize Government provided hardware/software to complete this task. Upon Government review and approval, submit packages in accordance with

CJCSM 3212.03E (Performing Electronic Attack in the United States and Canada for Tests, Training, and Exercises).

Support drafting/staffing/tracking Counterspace Activity Approval Packages (CAAPs). Upon

Government review and approval, submit in accordance with Office of the Deputy Secretary of Defense

Policy 070640-19 (Testing, Training, and Exercising of Space Control Electronic Warfare), Chairman of the Joint Chiefs of Staff Instruction 3320.01D (Joint Electromagnetic Spectrum Operations), and

AFSPCI 10-211 (Counterspace Activity Approval Package) Chapter 4.

Support drafting/staffing/tracking Ultra-High Frequency (UHF) SATCOM EA requests, Satellite Access

Requests, Deconfliction Support Request (DSR), and other planning products deemed necessary by the Government. Government review and approval is required for release to any external agencies.

SATCOM EA requires close coordination with the 25th Space Range Squadron and with other agencies dependent upon the exercise requirements.

Draft and submit Range Request Forms (RRF) and Operations Requests (OR) to 25 SRS or appropriate range organization after Government review and approval.

Review the 25 SRS published Operations Directives (OD) to ensure Space Aggressor exercise requirements are met. Advise SAP and the Aggressor Mission Commander of any discrepancies, errors, and potential conflicts with Aggressor requirements and resources.

Coordinate with Regional SATCOM Support Centers (RSSC), satellite owner/operators, Space Delta 5

(DEL 5) Radio Frequency Deconfliction, Combined Forces Space Component Command (CFSCC), and other external agencies as required to ensure requests are received and processed. Notify the

Government of any issues that may impact timeliness or performance.

Performance Standards

a) Standard: The contractor shall ensure that approval packages or operations requests (to include but not limited to CAAP, EA Request, DSR, and Satellite Access Request) are submitted and accepted prior to the deadlines set by the Government to enable mission requirements set by the Government.

b) Standard: The contractor shall inform the Government if any approval packages or operations requests (to include but not limited to CAAP, EA Request, DSR, and Satellite Access Request) are delayed or at risk of being delayed no later than 10 days prior to deadline.

c) Standard: The contractor…