TAP-M DRAFT_PWS_ 6.27.21.pdf

FA251821R0018

Performance Work Statement (PWS)

For

Transitional Approach for Protected MILSATCOM

(TAPM)

24 June 2021

Section 1- Description of Services

PARA DESCRIPTION PAGE

Section 1 Description of Services 3

1.0 Contract Scope 3

1.1 Place of Performance 3

1.2 Mission Essential Services 3

1.3 Protected MILSATCOM SUPPORT 5

1.4 Projected In-Scope Changes and Issues Affecting the

Contract

Section 2 Government Furnished Facilities and Services 14

2.0 Facilities and Service 14

2.1 Government Furnished Facilities 14

2.2 Government Furnished Data 14

2.3 Government Furnished Services 14

Section 3 Performance and Responsibilities 15

3.0 General Information 15

3.1 Contractor Program Management 15

3.2 Contract Information Management 19

3.3 Operational Exercises 19

3.4 Base Access Delays 20

3.5 Travel and Materials 19

3.6 Safety 21

3.7 Environmental 22

3.8 Recycling 23

3.9 Federal, State, and Local Laws 23

3.10 Interfaces with Participating Associate Contractors 24

3.11 Quality Performance Program Requirements 24

3.12 Contractor Quality Program 25

3.13 Ancillary Training Requirements 25

3.14 Anti-terrorism 26

3.15 Service Contract Reporting 26

Section 4 Services Summary 27

Appendix A Acronyms 29

Appendix B Publications List 32

Appendix C Possible Travel Locations 34

Appendix D Workload Estimates 35

Exhibits A

Contract Document Requirements List (CDRL)/Data Item

Descriptions (DIDs) List

1.0 Contract Scope

The contract provides mission support services to the Protected Band Military Satellite

Communications (MILSATCOM) missions for the 4th Space Operations Squadron (4 SOPS), Space Delta 8 (DEL 8), hereafter referred to asTAPM. Due to the upcoming delivery of Mission

Planning Subsytem (MPSS) Increment version 8.4, some of the requirements outlined in this

PWS will be significantly reduced throughout the life of this contract. Requirements impacted by the software release are listed in Appendix XX.

1.1 Place of Performance

The TAPM services identified in this section shall be provided primarily at Schriever Air Force

Base (SAFB) and Peterson Air Force Base (PAFB) Colorado, MacDill Air Force Base (MAFB)

Florida, Wheeler Army Airfield (WAAF) Hawaii, Patch Barracks (PB) Germany, and will require travel to locations worldwide. Temporary duty locations, purposes, and number of trips are identified in Appendix C of this PWS. This is a tentative list of travel locations and may be modified during the course of the contract as required.

1.1.1 Core Hours and Federal Holidays

Provide support for core hours identified as normal office hours 0730 to 1630, though the nature of the short notice taskings may require the Contractor to adjust to meet the requirement.

Protected Band Watch Officers will staff a 24 hours, 7 Days a Week (24/7) shift schedule.

The US Federal holidays are listed below. Any foreign locations are subject to any local workforce holiday schedules.

Holiday

New Year’s Day

Birthday of Martin Luther King, Jr.

Washington’s Birthday

Memorial Day

Juneteenth

Independence Day

Labor Day

Columbus Day

Veterans Day

Thanksgiving Day

Christmas Day

1.2 Mission Essential Services

Unless otherwise directed by the Contracting Officer (CO), the contractor shall ensure continued support at SAFB, as well as other locations identified in this PWS, during crises as required by

Defense Federal Acquisition Regulation Supplement (DFARS) 252.237-7023 Continuation of

Essential Contractor Services. In a crisis, if the Government deems necessary, the Contractor shall provide all Mission Essential Services (defined in Table 1) necessary to ensure mission accomplishment. On occasion, services may be required to support an activation, or exercise of contingency plans outside normal duty hours. Excessive or sustained support would be subject to

DFARS 252.237-7023(f) contained in the contract.

The contractor shall provide a Mission Essential Plan for providing reasonable assurance of continuation of mission essential services during crises conditions, (CDRL A024) within 30 calendar days after contract award. At a minimum, the plan shall address the elements identified in DFARS 252.237-7024. The plan shall also designate mission essential personnel and include their name, address, and telephone number. The contractor is required to maintain updates to this plan as necessary and ensure that coverage is provided during real-world and exercise scenarios.

Table 1: Mission-Essential Contractor Services

PWS Paragraph Mission Essential Service

1.3.1.1.1.1 Current MILSATCOM Operations Support – Daily Reports

1.3.1.1.2 -.5 Current MILSATCOM Operations Support – Troubleshooting

PWS Paragraph Mission Essential Service

1.3.1.2.4 Terminal Image Products

1.3.1.2.5 Milstar/AEHF Ephemeris Files

1.3.1.2.6 MPE Help Desk Support

1.3.1.3.4 RSSC System Administration Duties

1.3.1.3.5 RSSC Configuration Management

1.3.1.4.1 C-SSE Technical Assessment and Advice

1.3.1.4.2 C-SSE User/Manager Technical Assistance

1.3.1.4.9 User Message Support

1.3.1.5 PWBO Support

1.3.2.1 Cryptographic Planning Support

1.3.2.2 Cryptographic Operations Support

1.3.3 Payload Planning Support

These paragraphs are also denoted by an asterisk (*) throughout this document

1.3 Protected Band MILSATCOM SUPPORT

Provide Protected Band MILSATCOM operations and management support including current operations support, planning/monitoring tool and helpdesk support (at 4 SOPS and regional satellite communications (SATCOM) Support Center (RSSC) locations), protected band

Consolidated SATCOM Systems Expert (C-SSE) support, Protected Band Watch Officer

(PBWO) support to worldwide protected MILSATCOM users, cryptographic/COMSEC planning and operations support, payload planning support, training, and additional and quick response services. These system support activities shall include, at a minimum, the elements identified in paragraphs 1.3.1 through 1.3.6 below.

1.3.1 Protected MILSATCOM Operational Communications Support Services

1.3.1.1 Current Operations Support

1.3.1.1.1 Collect and monitor networks and payload data for systemic issues at the planning, payload, and terminal level. Identify to the 4 SOPS/Communications Directorate any undocumented limitations or other systemic problems.

1.3.1.1.1.1 * Create a daily advisory report during the normal work week that identifies system level activities with the Milstar and Advanced Extremely High Frequency (AEHF) system, and electronically distribute to the respective RSSCs, Unified Combatant Commands and various other users/managers. (CDRL A001 – System Advisory Report)

1.3.1.1.2* Troubleshoot strategic and tactical networks, as well as terminal related issues, during scheduled and unscheduled system outages, as well as during day-to-day operations.

1.3.1.1.3* Maintain technical knowledge and competency; be able to properly extract necessary data from technical documentation (i.e. Interface Control Documents, System Requirements

Documentation, Technical Manuals and Orders, Etc.) in order to support troubleshooting efforts.

1.3.1.1.4* Participate in Situation Assessment Recovery Team meetings to assist in resolution of system level anomalies.

1.3.1.1.5* Provide on-call user support for communications services issue resolution during non-regular duty hours. Respond to SAFB as soon as possible (ASAP) but no later than 3 hours from the time of Government request if the issue cannot be resolved via telecom.

1.3.1.1.6 Support 4 SOPS/DEL 8 during operational test events of system functionalities to include the communications planning tools (e.g. Mission Planning Element (MPE)) and on orbit testing for new assets.

1.3.1.1.7 Manage and provide system administration support to the 4 SOPS Communication data repository functions and any associated operating software on the server. Operational problems with these functions (databases, spreadsheets, etc.) shall be corrected within 72 hours of identification. Any government induced delay to this timeframe needs to be identified to the

Contracting Officer Representative (COR) immediately.

1.3.1.1.7.1 Ensure the repository functions are updated with the latest data, and shall archive replaced functions. Necessary baseline updates shall be applied as future protected systems are fielded. A quarterly status report will be submitted to track activity and any modifications of these functionalities. (CDRL – A002 Database Status Report)

1.3.1.1.7.2 A database, or similar function, shall at a minimum encompass the ability to provide a functional Master Station Log, Satellite Access Authorization parser and tracking functionality and the capability to connect between the communications support shops (Ops, Plans, Crypto, Help Desk) for compare and consistency purposes.

1.3.1.2 Planning/Monitoring Tool Operations and Help Desk Support

1.3.1.2.1 Provide configuration management for the 4 SOPS AEHF MPE resource monitoring

(RM) databases and produce useable archives for this data to be used by the squadron and other system users as requested.

1.3.1.2.2 Provide support to operations of the RM distribution through organic MPE function of

Communications Asset Monitoring (CAM) Distribution (CAM-D), as well as by other contingency means if necessary.

1.3.1.2.3 Provide Structured Query Language (SQL) database queries for report generation and other data gathering functions.

1.3.1.2.4 * Plan and deliver terminal image products for the squadron’s non-command and control terminals (For example (e.g.) Advanced Secure Mobile Anti-Jam Reliable Tactical

Terminal (ASMART-T)) to ensure normal operations, test events, and training evolutions are accomplished successfully.

1.3.1.2.5 * Provide Milstar and AEHF ephemeris files to the system users in the appropriate formats for planning and terminal operations on a weekly basis (during normal operations) and as needed when circumstance dictate off nominal distribution. These files shall be posted to an appropriate Secure Internet Protocol Router (SIPR) website and emailed as needed to user who will be maintained on a distribution list. (CDRL A003 - Ephemeris Distribution Report)

1.3.1.2.6 * Provide dedicated centralized MPE Help Desk (MHD) support to users across all fielded Mission Planning Subsystem (MPSS) software increments and hardware platforms which requires Security Plus (+) certification. The MHD shall be staffed Monday through Friday at

Schriever AFB during normal business hours (Mountain Time zone), with recall response during non-duty hours. For issues reported outside duty hours, recall time to SAFB will be 3 hours.

Provide a monthly report of all/any workarounds or best practices discovered or devised during the month. (CDRL A005– Workaround/Best Practices Tracker)

1.3.1.2.6.1 Provide, using a government database/system, a searchable repository of user call trouble tickets that can be used to analyze trends, research past issues encountered, and proactively develop products to better support the communications planning community.

Coordinate issues discovered across different users and theaters to ensure appropriate dissemination of information to all users. Provide a monthly report for all trouble calls received, displaying the current status for each call. (CDRL A004 – Help Desk Trouble Ticket Status

Report)

1.3.1.2.6.2# Provide systems engineering support for MPSS anomalies by assisting with

Discrepancy Report (DR) creation In Accordance With (IAW) Technical Order (T.O.) 00-35D-

54), prioritization and analysis, to include the generation and distribution of detailed operationally acceptable workarounds for MPSS software issues. Participate in the DR assessment, prioritization and delivery scheduling process to ensure that required fixes are delivered in a manner suitable to operations.

1.3.1.2.6.3 Provide close coordination with software developer to ensure the MHD, and 4 SOPS

Communications Directorate, stays abreast of pre-fielded versions of software and upcoming DR fixes.

1.3.1.3# Help Desk Forward Support: Due to upcoming delivery of MPSS 8.4 and efficiencies gained, the support listed in this section is expected to be completely de-scoped in a phased approach during the course of this contract.

1.3.1.3.1# Provide on-site support at RSSCs for Mission Planning Element (will require Top

Secret (TS)/Sensitive Compartmentalized Information (SCI) clearance at RSSC West located at

PAFB).

1.3.1.3.1.1# Provide level 1 maintenance and associated preventive maintenance for the

AN/TSCA 154 AEHF Secure Mobile Anti-jam Reliable Tactical Terminal (ASMART-T) at

RSSC Europe in accordance with Technical Manual 11-5895- 1881-10

1.3.1.3.2# Provide operational support with troubleshooting issues RSSC Planners have while using MPE software. Assist in resolving mission requirement and communication plan issues when present due to complex satellite access requests.

1.3.1.3.3# Interface with RSSCs as they field MPE related questions and problems from field users. Assist with the operational use of the MPE software by users worldwide. Feed this information back on a monthly basis to the central MHD for dissemination. (CDRL A006 –

RSSC Help Desk Trouble Ticket Report)

1.3.1.3.4# * Provide system administration (sysadmin) duties at the RSSC, which requires

Security Plus (+) certification. This includes user logon management, resetting accounts, changing passwords, hardware and log monitoring/management, installation of Commercial off the Shelf software and virus protection updates as distributed through Enhanced Technical

Information Management System. Support provided for RSSC West at Peterson AFB includes sysadmin duties for the PBWO located on the same base

1.3.1.3.4.1# Perform level one maintenance and necessary preventive maintenance inspection on

MPSS: tripwire security inspections, external hardware cleaning, optical drive cleaning, and internal hardware cleaning.

1.3.1.3.4.2# Coordinate the delivery of new equipment and disposition of legacy equipment.

Properly record these actions in Integrated Maintenance Data System.

1.3.1.3.4.3# Provide appropriate Database Administer functions to include clearing out Oracle logs to ensure proper operations. Create Oracle accounts, provides Database Management

System Status monitoring, performs Database update/roll-back, and Data backup/restore using

Recover Manager.

1.3.1.3.4.4# Perform necessary virtual private network updates and maintenance, coordinate with vendor and the local communications squadron concerning connection issues.

1.3.1.3.5*# Provide configuration management for the local RSSC MPE RM databases and support operations of the RM distribution through organic MPE function of CAM CAM-D and

Mission Operations Data Capture, as well as by other contingency means if necessary.

1.3.1.3.6# Support RSSC personnel in MPE related meetings, i.e. Deficiency Review Boards, MPE Working Group, etc.

1.3.1.4 C-SSE Operations Support

1.3.1.4.1* Provide Protected Band C-SSE technical assessment and advice to the 4 SOPS/DEL 8 leadership regarding user interests in reconfiguring both the Milstar and AEHF constellations, as well as with other executive decisions with impacts to user operations.

1.3.1.4.2* Provide C-SSE level technical assistance to system users and managers during the development of their contingency or exercise communications plans to help ensure the most efficient use of the Milstar and AEHF constellation. This support may occasionally include deployments to contiguous United States (CONUS) and outside contiguous United States

(OCONUS) locations.

1.3.1.4.3 Provide technical assistance from a payload and system level to the RSSCs to ensure a viable conduit for support and information flow between the organizations.

1.3.1.4.4 Provide support through 4 SOPS Communications Directorate to the squadron’s

Weapons and Tactics section for the development of advanced tactics with an emphasis on user communication support (will require TS/SCI clearance).

1.3.1.4.5 Trend constellation resources using the MPE, or other available tools, once monthly, once quarterly, and once yearly for the various products in order to identify unexpected systemic issues as well as to provide data for future payload configuration for both the Milstar and AEHF.

This needs to be provided to the community of interest in an easily readable format. (CDRL

A007 – Trending Report)

1.3.1.4.5.1 Perform and provide system trending and performance analysis on an as needed basis for emergent situations to include ‘what if’ scenarios and post anomaly investigations as they relate to operations. This will be directed by 4 SOPS Communications Directorate COR and needs to be provided to the community of interest in an easily readable format. Historically this report is required on average five times per year. (CDRL A008 – Observation Analysis Report)

1.3.1.4.6 Gather and synthesize information to mitigate limitations or deficiencies observed in operations. Examples can include observed training issues, as well as trends extracted from

Satellite Access Authorization and SATCOM Event Messages (SEM). This will be delivered in a quarterly report to 4 SOPS Communications Directorate. (CDRL A009 – Quarterly Operational

Events Trending Report)

1.3.1.4.7 Provide support for future Protected Band systems and terminals with technical assessments and C-SSE recommendations.

1.3.1.4.8 Draft, review, and coordinate on documents pertaining to payload operations and mission planning, as well as with the execution for current and developing Protected Band

SATCOM systems.

1.3.1.4.9* Coordinate with necessary organizations, draft, and prepare for delivery, user message correspondence for the Protected Band MILSATCOM systems. . Historically messages will be required on average 15-20 times per month. Provide monthly roll up of all messages transmitted over the past month. (CDRL A010 – User Message Distribution Report)

1.3.1.4.10 Research and outline periods of non-availability for mission impacting events conducted by 4 SOPS/DEL 8. Provide this in a concise format for 4 SOPS to distribute to the necessary organizations within the community of interest. The report will be required on a semi-annual basis, but operations may dictate additional submissions not to exceed four per year total.

(CDRL A011 – Ops Non-Availability Tracker)

1.3.1.4.11 Conduct authorized administrative functions on the Protected Band C-SSE Secure

Internet Protocol Router Network (SIPRNet) Share Point website in support of special operation command operations. Ensure a SIPRNet distribution list is kept up-to-date, to be used in the absence of product distribution via website.

1.3.1.4.12 Provide technical meeting and conference support services, including technical support to the Government during conferences, seminars, technical and operational meetings and reviews (e.g. EHF Users Forum, Material Improvement Process Review Board, Configuration

Control Board (CCB), Key Management Architecture Working Group, etc.). This includes providing minutes produced by the meeting host, or providing a synopsis of the meeting or conference to include any concerns affecting 4 SOPS/DEL 8. Trip reports shall be written for conferences attended outside of the local area. (CDRL A012 - Meeting Minutes/Trip Report)

1.3.3.2.2 1.3.1.4.13 Provide and maintain network tracking capabilities for significant cutover events. This product will be made available for delivery upon request of the Government. At least 15 business days’ notice will be given to the contractor to prepare of delivery. The

Government anticipates no more than 2 requested deliveries per year, but operational changes my dictate higher or lower volume. (CDRL A019 – Network Tracking Tool)

1.3.1.4.12.1 Meeting and conference support may require the Contractor to develop, present, and defend a presentation. This more in-depth support should only be expected four or five time per year.

1.3.1.5 PBWO Support *

1.3.1.5.1 Provide personnel for 24/7 protected watch stander at the SATCOM Integrated

Operations Division located at PAFB (will require TS/SCI clearance). Provide continuity binder for shift changeovers.

1.3.1.5.2 Assist users in resolving system related Electromagnetic Interference (EMI) issues

(IAW) Joint Spectrum Interference Resolution Procedures (CJCS-M 3320.02F), Satellite

Communications Electromagnetic Interference Resolution Procedures (Operating Instruction

(OI) 714-4), and Satellite Communications (SPI 3250.01A) Enclosure E EMI Resolution.

1.3.1.5.3 Maintain continuous global situational awareness for Milstar, AEHF, Ultra high frequency (UHF) Follow-On Extremely High Frequency (EHF), UHF follow-on/EHF (UFO/E), UHF follow-on EHF Enhanced (UFO/EE), Interim Polar System (IPS), Enhanced Polar System

(EPS), and follow on protected band constellations to facilitate immediate ops impact response to satellite anomalies. Be prepared to produce graphical depictions of this data (i.e. numbers of impacted users, beam and satellite footprint laydowns, etc.) for submissions as requested.

1.3.1.5.4 Gather and consolidate constellation RM data from CAM data, Joint Integrated

SATCOM Tool, Joint SATCOM Management and Planning System, RSSC trending reports and other available tools.

1.3.1.5.5 In coordination with 4 SOPS engineering and communications support functions, perform assessment to determine global operational impacts of satellite anomalies. This includes, understanding available root cause and the conditions of satellite during anomalies, recovery actions for accurate up channel reporting and potential user impacts. Examples of anomalies include problems with payload, satellite bus, crosslinks, crypto distribution, command

& control, etc.

1.3.1.5.6 Up channel Immediate Chat or Voice Reporting to Consolidated Space Operations

Center (CSpOC) in accordance with applicable directives and reporting criteria.

1.3.1.5.7 Generate/release SEM to approved classified venue in accordance with applicable directives and reporting criteria’s. Report monthly on SEM activity. (CDRL A013 – Monthly

SEM status report)

1.3.1.5.7.1 Maintain situational awareness and trending for non-SEM reportable issues and outages (i.e. NC3 terminal outages/ASIs). Be prepared to report this status as requested by

Protected Band C-SSE.

1.3.1.5.8 Provide operations interface, technical expertise, and system status while acting in support role to the single, central focal point for all Protected SATCOM operations, ready to brief the Protected Band operations global SA picture to Command Staff at any time.

1.3.2 Protected MILSATCOM Cryptographic and COMSEC Operations Support Services

1.3.2.1* Cryptographic Planning Support

1.3.2.1.1 Upon authorization, Build/Deliver/Archive Cryptographic Key Authorization Table

(CKAT) and Fill Group Commands to the Key Translation Element. The CKAT ensures all users have the correct Transmission Security and COMSEC keys to support Milstar/AEHF communications, and the Fill Group Command provides delivery data for AEHF Local Key

Management stations. Typical operations will dictate one delivery per month, but operational need may require additional delivery. Historically this has been a monthly product, but at times operations may dictate a more frequent delivery, on more than 15 in a calendar year estimated.

(CDRL A014 - CKAT)

1.3.2.1.1.1 Extract and deliver, to the EPS Control and Planning Segment operator, relevant data necessary for successful operations on the EPS/EPS-R system. Historically this has been a monthly product, but at times operations may dictate a more frequent delivery, on more than 15 in a calendar year estimated. (CDRL A015 – EPS CKAT Data)

1.3.2.1.2 Provide COMSEC planning for Cryptographic services on Milstar and AEHF in coordination with Directed Network Planners.

1.3.2.1.3 Provide joint cryptographic planning for all users of the UFO/E, UFO/EE, EPS, and emergent Protected SATCOM Systems.

1.3.2.2* Cryptographic Operations Support

1.3.2.2.1 Provide joint cryptographic troubleshooting and support for all users of the Milstar and

AEHF systems.

1.3.2.2.2 Provide updates to the AEHF Satellite Mission Control Subsystem Over the Air Rekey and End Cryptographic User (ECU) tables as new terminals are fielded.

1.3.2.2.3 Support the Protected Satellite Operations Center KTE, Radiant Mercury Boundary

Protection Device (BPD), and Central AEHF Key Management Station. Perform operational support for all aspects mentioned in this paragraph.

1.3.2.2.3.1 Execute system administration functions for the BPD, which requires Security Plus

(+) certification. Normal operations on the BPD do not require Security + certification.

1.3.2.2.3.2 Upon receipt of required data from the government, produce and deliver a monthly consolidated ECU status report. (CDRL A016 - ECU Status Report)

1.3.2.2.4 Provide technical assistance to the Controlling Authority and Space Operations

Command on all Milstar/AEHF cryptographic issues.

1.3.2.2.5 Provide MPE support for cryptographic planning functionalities that may include the use of SQL.

1.3.3* Protected MILSATCOM Payload Planning Support; : Due to the upcoming delivery of MPSS 8.4 as a final release of (NEED GOOD TERM FOR THIS) software, portions of this section is expected to be de-scoped during the course of this contract

1.3.3.1# Provide MPSS and strategic communications planning expertise to enable the customer to successfully deliver all operational MPSS Global Scenarios. This support may occasionally include deployments to CONUS and OCONUS locations.

1.3.3.2 Provide engineering support to facilitate satellite payload coordination and configuration, payload table creation, as well as execution of payload table validation activities for Global

Scenario development and implementation. Provide a monthly report encompassing all activity from the past month. (CDRL A017 - Global Scenario Database Delta Report)

1.3.3.2.1# Run Global Scenario delta compare to ensure a viable database. Provide a monthly report to the Government for each operational scenario (average three to four per month) with differences that need to be addressed. Work center OIs and Standard Operating Procedures

(SOPs) will address work center specific direction, policy, and procedures. All OIs, and SOPs once accepted by the government, will become property of the government and will be incorporated into the contract. (CDRL A018 - Global Scenario Delivery Clean Up Document)

1.3.3.3 Engineer, train, and execute advanced workarounds using engineering tools such as

SQL, Beyond Compare, Bit level comparisons, and data parsers for development and validation of global scenarios and other required MPE products.

1.3.3.4# Support configuration control across multiple fielded database increments through participation in 4SOPS Configuration Control Board, execution of data integrity checks, and focus on process discipline. Provide monthly status on all CCB activity. (CDRL A020 – Monthly

CCB Minutes/Change Report)

1.3.3.5 Support the Terminal Data Node (TDN) personnel to meet their strategic mission objectives (Terminal/image verification/troubleshooting, TDN specific training topics, exercise data collection scripts etc.).

1.3.3.5.1# Develop, validate, and prepare for delivery, image products for command and control

(C2) terminals including fixed and mobile locations. This will also include mission data for the

Advanced EHF Satellite Mission Control Subsystem. This product will be made available for delivery upon request of the Government. At least 2 months’ notice will be given to the contractor to prepare for delivery. The Government anticipates no more than two requested deliveries per year, but operational changes my dictate higher or lower volume of no more than four deliveries per year. (CDRL A021 – C2 Terminal Image Products)

1.3.4 Training Support

1.3.4.1 Provide communications systems proficiency training. Training includes informal training sessions that would last no more than one duty day in local areas.

1.3.4.2 Train 4 SOPS/DEL 8, Unified Combatant Commands (CCMD) personnel (see travel list in Appendix C), and other entities deemed beneficial to the Protected SATCOM Community of

Interest by the Government (e.g. Terminal Program Offices, System Program Offices, etc.) on system level technical theory, communications planning, and communications planning tool usage of AEHF MPE.

1.3.4.2.1 Conduct MPSS User Support Visits once per year, at each RSSC in order to help meet mission requirements using MPE capabilities. These visits are conducted to demonstrate the capabilities of the MPSS product, assist RSSC personnel with operational issues, and to provide system familiarization to efficiency of MPSS operations.

1.3.4.3 Train 4 SOPS personnel on AEHF Secure Mobile Anti-jam Reliable Tactical Terminal operations in local areas as required. Estimated number of occurrences is approximately 2-4 times a year.

1.3.4.4 Provide continuing training for PBWO to ensure proficiency in local areas as required.

Estimated number of occurrences is approximately 2-4 times a year.

1.3.4.5 Provide cryptographic training and education to 4 SOPS personnel and Milstar/AEHF system users and managers in local areas as required. Estimated number of occurrences is approximately 2-4 times a year.

1.3.4.6 Provide in depth Milstar/AEHF/MPSS System instruction for advanced engineering topics particular to the communications payload planning areas of responsibility in local areas as required. These areas include strategic network and terminal configurations, AEHF payload configuration methodologies, Extended Data Rate (XDR) signal structure, and transition to strategic use of XDR. This occurs monthly.

1.3.4.7 Provide logistical support for all training, to include a secure location for the local

Milstar and AEHF System Level Course. Develop training materials and procedures including the appropriate markings, which take into consideration the evolution of the entire protected system (changes to Milstar and AEHF as well as UFO E/EE, IPS, EPS) and encompass lessons learned through operations. Prior to each class course materials shall be reviewed and updated as needed. Average occurrence: 11 times per year, 5 local and 6 TDY locations. (CDRL A022 –

Training Documents)

1.3.4.7.1 Ensure all Government furnished property is fully functional and ready to perform training and students are provided course materials.

1.3.4.7.2 Local training shall require storage of classified equipment and material IAW the

Department of Defense (DD) Form 254 block 11d. The government will not be responsible for providing a location for local training.

1.3.4.8 Training and Education Costs: The Government will provide training and materials as new or modified systems come online. Specialized government provided training (e.g., not commercially available) may be required as directed. The Government will not reimburse or pay for contractors to receive any other training such as certifications.

1.3.5 Additional and Quick Response Services

The nature of the services may require the contractor to provide quick response deliverables and respond to additional or quick response tasking’s to meet the needs of the Government. This may require short notice report production or document reviews and the preparation of technical, procedural, conceptual, and information papers with minimal notice. It is understood that work in support of quick response tasking’s may conflict with work already scheduled and shall be identified and assigned by the COR.

1.4 Projected In Scope Contract Changes and Issues Affecting the Contract

DEL 8 anticipates requirements growth (mission and equipment) and contract requirement fluctuations to occur throughout the TAPM period of performance. Additionally, DEL 8 anticipates that existing systems (e.g., mission, communications, and mission support) will be replaced with new systems during the TAPM period of performance. These systems may require support to a level yet to be determined. This support may include additional terminal users, e.g.

International Partners (United Kingdom, Canada, Netherlands, and Australia). The following requirements represent potential changes to the contract, and are considered to be within the scope of the contract. As these requirements represent certain unknowns, the Offeror is not required to propose against these efforts. These efforts may include additional labor and travel.

The Government will negotiate any in scope changes directly with the Contractor at the time any such requirement can be defined.

1.4.1.1 Potential transition from legacy to advanced waveforms

During the course of this contract, the government anticipates migrating/transitioning from legacy waveforms to those provided by the AEHF platform. This will also accompany a draw down for the legacy systems. Increases to the contract may occur during the period of performance due to activities associated with this.

1.4.1.2 Potential Protected Anti-Jam Tactical System (PATS) Build Up

During the course of this contract, the government anticipates the PATS moves forward into operations. Increases to the contract may occur during the period of performance due to activities associated with the PATS system.

1.4.1.3 Potential Future Strategic SATCOM systems Build Up

The Government anticipates future strategic SATCOM systems build up during the course of this contract. Increases to the contract may occur during the period of performance due to activities associated with these systems.

1.4.1.4 Potential Enhanced Polar System Recapitalization (EPS-R)

The Government anticipates EPS-R build up during the course of this contract. Increases to the contract may occur during the period of performance due to activities associated with the EPS-R system.

1.4.1.5 Future Crypto Planning

Provide joint cryptographic planning for users of emergent EPS-R and future Protected system requirements.

1.4.1.6 Operational Test Events

There is a possibility 4 SOPS/DEL 8 will require future support for operational test events of communications planning tools to include the full scope of functionalities within the tool.

1.4.1.7 Cryptographic Voice KGV-11 De-scope

During the period of performance of this contract tasks associated with KGV-11 networks may be de-scoped.

Section 2 – Government Furnished Facilities and Services

2.0 Facilities and Services

2.1 Government Furnished Facilities

The Government will provide sufficient workspace at all locations to meet requirement needs.

The Government will provide access to Secure Telephone set with commercial and Defense

Switched Network (DSN) access. The Government will provide access to a SCI approved shredder, a classified Secret color laser printer, an unclassified black and white laser printer, and classified storage space within a U.S. General Services Administration (GSA) approved safe.

The Government will provide access to classified computers connected to SIPRNET, unclassified computers connected to Non-Secure Internet Protocol Router, and classified MPSS computers connected to an internal classified processing network equipped with productivity software.

2.1.1 Any utilities currently used to support analysis, production and dissemination will be provided by the Government.

2.1.2 All government provided facilities and equipment, to include floor space allocations, are subject to adjustment or relocation during the period of performance of this contract.

2.1.3 Sign a hand receipt for laptops provided by the Government for the performance of required training. Identify any laptops not in working order and notify the COR in writing.

2.1.3.1 The Contractor and the Government CORs shall jointly determine the working order and condition of all laptops provided.

2.1.3.2 In the event of a disagreement between the Contractor and the Government COR on the working order and condition of the laptops, the disagreement shall be treated as a dispute under the contract clause entitled "Disputes" located in the contract.

2.2 Government Furnished Data

Operate equipment IAW applicable technical orders to include current changes and supplements.

If technical orders are not available, the Contractor shall follow commercial manuals or industry standards. For a list of current procedures/manuals/technical orders, see Appendix B.

2.3 Government Furnished Services

The Government will provide on-base postal/parcel distribution services, basic custodial service, security and fire protection, emergency medical services, classified destruction, local area off-base, and long distance telephone service including DSN service for official government phone calls in performance of this contract.

The Government will provide government only sourced training.

Section 3 – Performance and Responsibilities

3.0 General Information

This section of the PWS outlines the conditions and constraints the Contractor must perform within the contract and does not contain any description of services to be performed. Refer only to Section 1 – Description of Services for identification of the services to be performed by this contract. The following conditions and constraints pertain to the entire contract and is arranged logically, not associated with any particular service or paragraph in Section 1– Description of

Services.

3.1 Contractor Program Management

Provide program management to ensure efficient and effective accomplishment of all work required. The Contractor shall provide qualified personnel, equipment, tools, materials, supervision, and services necessary to perform the services described within this PWS.

3.1.1 Contractor Program Manager

3.1.1.1 Identify in writing to the Government Contracting Officer the individual assigned to act as the Contractor Program Manager (CPM) and any authorized Deputy Contractor Program

Manager (DCPM).

3.1.1.2 The CPM or DCPM shall have full authority to act on behalf of the company in all matters relating to contract performance.

3.1.1.3 The CPM and DCPM shall read, write, speak, and understand the English language.

3.1.1.4 The CPM or DCPM shall be made available to the Government Contracting Officer

(GCO) and the Government Program Manager (GPM) during normal duty hours within thirty

(30) minutes of notification, and within two (2) hours of notification after normal duty hours.

The CPM or DCPM shall provide management information only to the GCO.

3.1.2 Contractor Security Manager

Identify to the GCO and the GPM the security point of contact responsible to obtain the appropriate security clearances for employees working this contract and who will be responsible for all contractor security responsibilities associated with this contract within 10 calendar days after contract award.

3.1.3 Employee Management

3.1.3.1 Contractor personnel shall be under the direction and control of the Contractor.

3.1.3.2 Contractor personnel shall be subject to rules and policies governing the activities of personnel on government installations.

3.1.3.3 The Contractor shall not employ persons for work on this contract if such employees are identified as potential threats to the health, safety, security, general well-being or operational mission of the installation and its population.

3.1.3.4 The GCO will notify the Contractor in writing, to remove any employee from the installation when retention of such employee endangers life, property, security, or where such an employee violates reasonable and necessary base regulations.

3.1.3.5 The Contractor shall not employ any person who is an employee of the United States

Government if employing that person would create a conflict of interest.

3.1.3.6 All Contractor personnel shall be able to read, write, speak, and understand the English language.

3.1.3.7 Ensure mission essential work center coverage while minimizing potential harm to

Contractor employees.

3.1.3.8 All Contractor employees are required to identify themselves by introducing themselves or being introduced as Contractor personnel and by displaying distinguishing badges or other visible identification for meetings with Government personnel, and shall also identify themselves during telephone conversations and in formal and informal written correspondence.

3.1.3.9 Retrieve and return to host unit, all identification media, including common access card and restricted area badges from contract employees that depart for any reason before the contract expires or upon termination of the contract.

3.1.3.10 Notify the Government within 24-hours when unable to retrieve identification media from contract employees.

3.1.4 Contract Performance Management

Advise the GCO immediately of any problems that affect the Contractor’s performance or impact mission accomplishment.

3.1.4.1 All questions concerning interpretation of the contract or PWS will be directed to the

GCO.

3.1.4.2 Meetings and coordination efforts must be held at frequencies commensurate with the complexity and status of the effort required to support the work and meet the identified requirements.

3.1.5 Contract Transition

Transition into and out of this contract without degradation of service. The Government will oversee the contract transition period. The GPM and the GCO will schedule a transition “kick-off” meeting at the start of the transition period to be attended by the incumbent contractor and the successor contractor. The transition assistance required by the successor contractor shall not interfere with the incumbent contractor’s ability to perform the services of this contract.

3.1.5.1 Phase-In

Establish, and deliver to Government 10 calendar days after contract award, procedures to ensure a successful transition of all services identified in this PWS and assume all responsibilities without any degradation in service. (CDRL A025 Phase-In Plan) The Contractor shall begin initial phase-in operations during the period identified in the contract and have a complete workforce trained and available in each work center no later than the start date of the contract.

Phase-in activities will include appropriate interface with the requiring activity and incumbent contractor to observe and become familiar with current operations to facilitate assumption of total contract performance on contract start date. All required equipment inventories and inspections with the Government will occur during the Phase-in period. The Contractor shall contact the GPM to coordinate Phase-In activities that include government personnel.

3.1.5.1.1 Status Briefings and Readiness

During Phase-In, the Contractor shall provide weekly briefings to the TAPM GPM and the

TAPM Multi-Functional Team. These briefings will discuss readiness status, problems encountered in accomplishing the phase-in, categorized as minor, major, or showstoppers, progress-to-date with schedule updates to reflect the actual progress, any variances from efforts, any work-around plans being implemented to resolve problems, and any support required from the Government for phase-in.

3.1.5.2 Phase-out

Support and cooperate fully with the successor to ensure a smooth transition of all services identified in their PWS. The Contractor shall ensure all responsibilities are transferred with no degradation in service and maintain overall contract responsibility until the completion of the contract period of performance and the transition to the successor is complete. The Contractor shall provide a Phase-Out Plan within 30 days of government request. (CDRL A026 Phase-Out

Plan)

3.1.6 Authorized Technical Direction

3.1.6.1 MFT Post Award Lines of communication. IAW AFI 63-138, members of the MFT after contract award should ensure the only formal or directive line of communication between the Government and the Contractor is from the GCO. However, all other members of the MFT can communicate informally with the contractor. Examples of informal communication are clarification of delivery schedules or communication of COR inspection results.

3.1.6.2 All questions concerning interpretation of the contract or PWS shall be directed to the

GCO.

3.1.6.3 The GCO is the only individual authorized to provide contract clarification and/or modify, in any way, the terms of the contract. Such changes of terms shall be accompanied by issuance of a modification to the contract signed by the GCO.

3.1.6.4 The GCO shall be notified immediately upon receipt of unauthorized technical direction from unauthorized government personnel for potential resolution.

3.1.7 Deliverables

3.1.7.1 Data delivered in the normal course of the TAPM contract performance shall be accomplished IAW the format, frequency, and distribution identified in the CDRLs contained in each DD Form 1423 under Exhibit A of this contract.

3.1.7.2 The use of a Receiving Report (DD Form 250) for each CDRL is not required for inspection and acceptance of the deliverables; however, an informal review will be accomplished by the COR.

3.1.7.3 Changes and/or updates to data deliverables will be communicated to the contractor by the GCO.

3.1.7.4 The GCO or COR shall perform final inspection and acceptance of deliverables.

3.1.7.5 The preferred method of delivery for data identified in the PWS is via electronic media, and must be compatible with SAFB Local Area Network electronic media requirements.

3.1.8 Program Management Review (PMR)

3.1.8.1 Provide a PMR to the government semi-annually in August and February.

3.1.8.2 Emphasis shall be on overall performance (to include contractual and technical concerns) and process improvement.

3.1.8.3 These PMRs will be held in the Colorado Springs area and will be coordinated with the

COR/GPM. This meeting can be in person or conducted virtually. Present PMRs within first 21 days of August and February. (CDRL A027 – PMR).

3.1.8.4 Contractor’s Progress, Status and Management Report will be required monthly on the

10th business day (CDRL A028 – Contractor’s Progress and Status Report). This report also requires summaries of CDRLS A001, A003, A007, A010, A013, A014, A015, A016, A017, A018, and A021 as noted in each CDRL.

3.1.9 Security Requirements

3.1.9.1 Ensure personnel are adequately cleared to the required security clearance levels (up to and including TS/SCI) prior to contract start (see the TAPM DD Form 254).

3.1.9.2 Have the capability to respond to short notice taskings. The facility clearance and level of safeguarding required has been determined to be TS/SCI.

3.1.9.3 The Contractor must possess or obtain TS security clearances, with the ability to hold an

SCI billet, prior to contract start date. A specific number of SCI billets will be allocated to the contract and will be assigned to all, or a subset, of the contract personnel. This will be done by the COR as deemed necessary for mission accomplishment.

3.1.9.4 Not every contract member will necessarily hold a TS/SCI billet.

3.1.9.5 The Contractor shall be required to access the items identified on the DD Form 254.

3.1.9.6 Performance of the requirements will allow the Contractor to have access to the items identified on the DD Form 254.

3.1.9.7 Provide personnel with the necessary TS/SCI security clearances and shall maintain appropriate personnel security clearances for employees per Department of Defense (DoD)

5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

3.1.9.8 Enter into a Visitor Group Security Agreement (VGSA). The Peterson-Schriever

Garrison (P-S GAR) Information Protection Office is the point of contact for completing a

VGSA.

3.1.9.9 The VGSA is an agreement between the installation commander and the Contractor that describes the conditions that must be met to gain access to the installation and sensitive information.

3.1.9.10 The Government will provide initial and follow-up security procedures training to

Contractor personnel who work in controlled and restricted areas.

3.1.9.11 Ensure security complies with the NISPOM DoD 5220.22-M, the Air Force Guidance

Memorandum, AFI 16-1404, Air Force Information Security Program, the Industrial Security

Program Air Force Instruction (AFI) 16-1406, the contract’s DD Form 254, and the applicable base contractor integrated VGSA document.

3.1.9.12 Perform duties within restricted areas IAW with the provisions of the Air Force and

Space Force.

Integrated Defense (AFI 31-101 and applicable supplements), and the 50 SW Installation

Security Instruction (50 SW IDP 31-1).

3.1.9.13 Provide sufficient personnel authorized to serve as restricted area escorts for its employees. Failure of the Government to grant a clearance, revocation of a clearance, or revocation of base access privileges for any individual employed by the contractor shall not serve as justification for failure to perform. (Both documents referenced in this paragraph will be delivered upon contract award for operational security reasons)

3.1.9.14 Control access to all areas of contractor responsibility IAW DoD Information Security

Department of Defense Manual 5200.01.

3.2 Contract Information Management

3.2.1 Data Management

All data, regardless of media, produced in the performance of this contract shall be the property of the Government and shall be made available on the SAFB local area network and/or hard copy. The Contractor shall provide management related information directly to the government program manager.

3.2.2 Contract Publications

3.2.2.1 Applicable paragraphs within each listed publication are identified in Appendix B and are listed as either directive or as guidance.

3.2.2.2 Comply with all documentation defined as directive and comply with the intent of documentation defined as guidance.

3.2.3 Technical Order Management

Maintain applicable Technical Order (AFTO) in accordance with AFTO 00-5-1.

3.2.4 Directive Publications Review

Review new or revised directive publications (draft and final versions) and notify the GCO within 30 calendar days of receipt if the directive poses any cost or performance risk to the contract.

3.2.5 Freedom of Information Act and Privacy Act

3.2.5.1 Ensure personal privacy data is protected to prevent unauthorized disclosure and ensure proper disposal.

3.2.5.2 Forward Freedom of Information Act and Privacy Act requests to the Government IAW

AFI 33-332, Air Force Privacy Act Program, not later than the first duty day after receipt of request.

3.3 Operational Exercises

Participate in all operational exercises and inspections to the fullest level possible without negatively impacting real-world…