OOES_PWS_FY22_FY26_IPS.pdf

NAVAL SAELLITE OPERATIONS CENTER

PERFORMANCE WORK

STATEMENT

FLTSAT AND UFO ON ORBIT ENGINEERING SERVICES

(OOES) CONTRACT

FY2022 – FY2026

PERFORMANCE WORK STATEMENT

ON ORBIT ENGINEERING SERVICES (OOES) CONTRACT

INTRODUCTION:

The Naval Satellite Operations Center (NAVSOC) was the first United States commissioned military space command and has been operating spacecraft since 1962. NAVSOC is responsible for operating, managing and maintaining satellite systems, providing reliable, uninterrupted satellite services to the warfighter. NAVSOC is continuously looking to innovate and automate all areas of its mission in order to improve efficiency and be cost effective.

The NAVSOC is responsible for operating, managing and maintaining assigned Department of Defense (DoD) satellites and network systems. NAVSOC reports to the Combined Force Space Component Commander (CFSCC) and the Commander Fleet Cyber Command (FLTCYBERCOM). NAVSOC’s primary mission is to provide reliable communication services to the joint warfighter.

The purpose of this contract is to provide qualified and specialized technical services to ensure satellite mission capability 24 hours a day 7 days a week including holidays. Figure-1 shows NAVSOC echelon structure and reporting chain of command.

Figure-1: NAVSOC Echelon Structure

Services under this contract include on-orbit satellite engineering, Trend analysis, Anomaly Resolution, Mission

Planning, Technical Studies, Satellite Specific Training and Command and Control procedures automation, test and evaluation. NAVSOC HQ and Detachment Delta are the locations to be supported under this contract.

Background Information:

The NAVSOC Telemetry, Tracking & Commanding (TT&C) operations are conducted from two Satellite Operations

Centers (SOCs) located within the continental United States (CONUS). The primary SOC is located at the NAVSOC

Headquarters Facility (HQ) in Point Mugu, CA. An alternate SOC is located at NAVSOC Detachment Delta (Det D) in Schriever Air Force Base, Colorado Springs, CO. Both SOCs are supported by three remote Telemetry and

Commanding (T&C) facilities; an unmanned T&C facility at Laguna Peak (LP) in Point Mugu, CA, NAVSOC

Detachments Alfa (Det A) in Prospect Harbor, ME and Detachment Charlie (Det C) in Finegayan, Guam.

Organizational Structure:

The NAVSOC staff is a mix of military, government civilian, and contract personnel working together and collaborating as an integrated team to meet common mission requirements and accomplish strategic command goals.

The contractor will be a critical part of the NAVSOC team, working to meet NAVSOC's common command objectives. Thus, the contractor is expected to provide recommendations to improve processes, procedures, and operational readiness, as well as to increase efficiency and reduce operating costs. The NAVSOC organizational structure is shown in figure-2.

Figure-2: NAVSOC Organizational Structure

Service Locations and Business Hours:

The work shall be performed at NAVSOC HQ located in Naval Base Ventura County (NBVC), Point Mugu, California and NAVSOC Detachment Delta (Det D) located in Schriever Air Force Base, Colorado Springs, Colorado.

Location Business Hours (Local) SOC Hours After Hours Recall

HQ 0730 – 1630 (M-F) 24/7, 365 Within 1 hr

Det D 0730 – 1930 (M-F) 16/5 Within 1 hr

Table-1: Working hours by site.

Security Classification Requirements

An approved and executed Security Classification Form DD-254 will be provided at the time of award. The contractor shall comply with all federal and local security statutes, regulations, and requirements. The contractor shall become acquainted with and comply with all Government regulations as posted, or as requested by the KO when required to enter and/or work in a Government site. The contractor shall ensure that all security clearances are obtained and maintained current to work to continue without interruption.

The contractor shall obtain all required corporate and personnel Security Clearances prior to commencement of work.

The contractor shall ensure that a list of all personnel with Security Clearances is maintained current, including clearances that are pending. Contractor is required to obtain and maintain personnel clearances for all contractor personnel at the appropriate level at the expense of the contractor.

The contractor shall maintain and provide a current listing of all employees at any NAVSOC locations. The list shall be updated continuously and include such information as employee’s full name, social security number, level of security clearance, date of security clearance and agency granting the clearance.

All contractor employees shall obtain the required employee passes. The Government will issue Identification (ID) cards/passes/access cards without charge. Each employee shall wear the Government issued ID card/pass over the front of the outer clothing above the waist. When an employee leaves the contractor’s service, the employee’s pass, ID card, and/or access card shall be returned on the last day.

The contractor shall maintain internal physical security of designated areas in partnership with the Government. The physical security of exterior doors, windows, and any other portals shall be secured according to local security requirements. Table-2 provides a list of security classification required at each site.

Site Security Classification Required

HQ, Point Mugu, CA Secret

Det D, Schriever Air Force Base, Colorado Springs, CO Secret

Table-2: Security Classification Requirements

Ground Systems Overview:

NAVSOC's three remote earth stations at Det A, Det C and LP provide telemetry and commanding (T&C) capabilities via SGLS and EHF antennas.

Det A has one USC-38(V)3 antenna used to conduct EHF Broadcast services on Polar 2 and Polar 3 Interim Polar

Systems (IPS). Det A also has one USC-38(V)9 antenna used to conduct EHF Telemetry and Commanding (T&C) operations on both POLAR EHF and UFO, and a Space to Ground Link System (SGLS) antenna used to conduct

T&C operations on UFO and FLTSAT.

Det C has a USC-38(V)3 antenna used as a backup antenna to the USC-38(V)9, a USC-38(V)9 antenna used to conduct

EHF T&C operations on UFO, and a SGLS antenna used to conduct T&C operations on UFO and FLTSAT.

Laguna Peak has a SGLS antenna used to conduct T&C operations on UFO.

HQ has a USC-38(V)9 antenna used to conduct EHF T&C operations on POLAR EHF and UFO.

Dedicated leased lines links HQ and DET D to the U. S. Air Force Satellite Control Network (AFSCN) and are capable of conducting TT&C operations using Air Force Automated Remote Tracking Stations (ARTS) located around the world. Dedicated leased line are also used to connect All NAVSOC sites to provide a redundant and robust communication network system..

Satellite Constellations Overview:

The NAVSOC is responsible for operating, managing and maintaining the following satellite constellations: Fleet Satellite (FLTSAT) communication satellites, Ultra High Frequency (UHF) Follow On (UFO) communication satellites, and Mobile Users Objective System (MUOS) communication satellites. These constellations are the space segment of the Navy satellite communication (SATCOM) system; these constellations support DoD UHF, EHF, and GBS communications. The SATCOM system is configured to cover areas in the Atlantic, Pacific and Indian Oceans as well as well as within the CONUS. This system is currently comprised of one (1) FLTSAT, five (5) UFO, and five

(5) MUOS satellites operating in geosynchronous orbit providing 24/7 communication capabilities to the joint warfighter. Table-3 identifies the number of satellites in each constellation that are expected to be supported under this contract during each performance year through 2026. Projected number of satellites supported do not include end of life predictions, additional launches or new constellation.

Constellations 2022 2023 2024 2025 2026

FLTSAT 1 1 1 1 1

UFO 5 5 5 5 5

POLAR 2 2 2 2 2

MUOS 5 5 5 5 5

Table-3: Planned Satellite Support Requirements by Fiscal Year

Fleet Satellite (FLTSAT) Constellation

The FLTSAT constellation was designed and manufactured by TRW Inc. and was the initial constellation of operational military UHF communication satellites. There is currently one operational FLTSAT (FLTSAT 8) in geosynchronous orbit.

Ultra High Frequency Follow-On (UFO) Constellation

The UFO constellation was designed and manufactured by Boeing Space & Intelligence Systems (BSIS), formerly

Hughes Space Communication Company. UFO satellites were designed to replace the FLTSAT constellation.

Currently there are five (5) operational UFO satellites (UFO 2, 4, 8, 10, 11) in geosynchronous orbit. In addition to the UHF communication, UFO satellites provide users with EHF (UFO’s 4, 8, 10, 11 have EHF capability) and Global

Broadcasting Service (GBS) communication (UFO 8 and 10 have GBS capability) capabilities.

Mobile User Objective System (MUOS) Constellation

The MUOS is a Department of Defense (DoD) Ultra High Frequency (UHF) SATCOM system that provides the warfighter with modern worldwide mobile communication services. MUOS adapts a commercial third generation

(3G) Wideband Code Division Multiple Access (WCDMA) cellular phone architecture for use in a military UHF

SATCOM system using geosynchronous satellites in place of cell towers. The constellation of four WCDMA operational satellites will provide to the warfighter greater than 10 times the current legacy UHF capacity. In addition, there is one spare MUOS satellite flown via SGLS earth terminals for five MUOS satellites. The MUOS constellation is being designed and built by Lockheed-Martin Space Systems and is designed as the follow-on to the current

FLTSATCOM system (UFO and FLTSAT satellites).

NAVSOC conducts TT&C operations with the MUOS satellites primarily through Ka band antennas which reside at the MUOS Remote Access Facilities (RAFs). There are four (4) RAFs located around the world. RAFs are located at Wahiawa, HI, Geraldton, Australia, Northwest Virginia, and Niscemi, Sicily. In addition to the RAF sites, NAVSOC conduct TT&C operations with the MUOS satellites with AFSCN and CAS antennas during Launch and

Early Orbit, anomaly resolution, relocation, and spare satellite operations.

POLAR EHF (IPS)

The IPS is an EHF package, similar to the EHF payload on board the UFO satellite, is carried on board a classified

“Host” satellite in a Molniya orbit (period of 12 hr). IPS is deployed on two host satellites referred to as Polar 2 and

Polar 3 (P2 and P3). IPS provides EHF communications to fleet and DoD users in the regions above 65 degrees North latitude.

PERFORMANCE REQUIREMENTS:

Engineering services described in this PWS require Subject Matter Expertise (SME) and knowledge of satellite operations, satellite engineering and technical functional areas that include skill sets and experience that enable the organization’s need to comply with and respond to DoD, and NAVSOC requirements. Contractor will be responsible for FLTSAT, UFO, and POLAR EHF On-Orbit Satellite Engineering Support.

1. Contract Management and Quality Assurance

The contractor shall:

a) Provide the requisite Program Management and Quality Assurance (QA) to ensure services and products delivered at HQ and Detachments meet the timeliness and quality listed in the performance standards for each specification item in this PWS.

Performance Standards: Services and products are completed and delivered by due dates and in accordance with satellites support requirements documents (SRD) and NAVSOC approved instructions.

b) Attend operations related meetings (daily 08:00 – 08:30) and provide technical feedback and information related to satellite state of health or recent satellite related events and schedule. Attend technical interchange meetings (TIMs) or conferences as coordinated with N33. Average number of TIMs and conferences are two per year. The average length of each event is 2-4 days including travel.

Performance Standards: Contractor SME(s) are present at designated meetings and ready to participate in technical discussions related to this PWS.

c) Update personnel recall list of primary and backup SMEs for FLTSAT,UFO, and POLAR EHF constellations as required.

Performance Standards: Recall list updated within 1 working day of POC information change. Recall List submitted to the SOC within 1 working day of update. Recall List contains names and phone numbers for each SMEs.

d) Provide monthly status report of work completed, work in progress, projected work requirements, man-hours expended, monthly cost expenditures and cumulative expenditures by satellite constellation, training and automation effort . Contractor format is acceptable.

Performance Standards: Monthly Status Report delivered to the COR NLT the 15th of each month following the reporting period.

e) The contractor shall travel as required in support this task order. The contractor shall coordinate and seek travel approval from NAVSOC COR before commencing travel.

2. Satellites Command and Control

Some scheduled satellite contacts require on-console engineering expertise. Some contacts are time specific, require engineering support during off hours including weekends, and holidays. Contacts duration can vary from 15 minutes to 5 hours per support. The Support Requirements Document (SRD), Pass Plans or Perform

Files for each constellation outline support categories and the number of satellite engineers required.

a) Provide qualified personnel at NAVSOC Headquarters, Naval Base Ventura County, CA, and Detachment

DELTA, Schriever Air Force Base, CO.

Performance Standards: Contractor train and qualify their engineers before assigning them to Command and Control duties in the SOC. Qualified personnel are available to execute assigned duties during working hours.

b) Conduct pre-pass brief with assigned crew before start of Acquisition of Signal (AOS) for all support requiring satellite engineering on console expertise. Perform on-console engineering functions to include briefing the support crew before the pass, upload commands to the satellite, verify that the correct commands are sent to the satellite during the pass, verify that telemetry data are within nominal limits, execute contingency actions and safe the satellite if anomalies are encountered during the pass.

a) Performance Standards: Engineer(s) present in the SOC and ready to perform assigned commanding support NLT 10 min before Acquisition of Signal (AOS) time. Anomalous conditions encountered during the support are reported to the SWC within 5 minutes of anomaly recognition.

3. Satellite Health Trend Analysis, Risk Reduction and Mitigation:

The purpose of telemetry data trending and analysis is to assess each satellite state of health, identify trends related to performance, determine potential impact to overall satellite mission and assess payload capability to support the warfighter.

a) Analyze real-time and archived telemetry data collected during contacts and develop applicable graphs, and charts to trend satellite’s subsystem performance. Trend Analysis includes but not limited to Power Subsystem performance, Momentum Wheel Speed growth, Fuel consumption, Thermal subsystem performance and Attitude Control subsystem performance.

Performance Standards: Trend Analysis performed daily. N33 notified of any non-nominal trends that have the potential of impacting satellite bus health or payload outage or degradation within 4 hrs. of discovery.

b) Provide monthly report highlighting state of health (SOH) for each satellite subsystem and identify any trends that may have potential to degrade or influence the satellite ability to meet stated mission requirements.

Performance Standards: Monthly reports are submitted to N33 no later than 10 working days after the 1st of each month.

c) Develop and recommend to N33 any corrective action(s) required to maintain satellite system and subsystem state of health, and reduce operational risk to payload and any interruption to services to the warfighter.

Performance Standards: N33 is notified of recommended actions within 1 working day of finalizing the recommendations.

d) Implement government approved corrective action(s) in accordance with approved schedule.

Performance Standards: Corrective actions are implemented within approved schedule time frame.

e) Maintain and update trend analysis tools, macros, procedures, and recommended decision matrices to track, identify and project anomalous conditions for the satellite system, subsystem, and components.

Performance Standards: Changes and updates to trending tools are coordinated and approved IAW NAVSOC CM process.

f) Provide softcopy copies of the trend analysis tools and the users manuals or instructions via the established NAVSOC Configuration Management (CM) process.

Performance Standards: All softcopies are delivered to the CM manager within 1 week after implementation of the tools into operations.

g) Implement government approved updates to the Naval Satellite Verification Tables (NSVT) Values and procedures when trending and analysis indicate a change in satellite health has occurred.

Performance Standards: NSVT changes are implemented IAW NAVSOC NSVT instruction.

4. Anomaly Response, Analysis and Resolution:

Anomaly Classifications and Response:

Class I Anomaly: A routine spacecraft problem, usually seasonal in nature, that is well understood and easily corrected. Class I anomalies have no direct operational impact and are normally corrected by resetting or temporarily activating vehicle subsystem components.

Class II Anomaly: A non-routine spacecraft problem that has been anticipated or previously experienced.

Class II anomalies have a direct operational impact on either the satellite bus or the payload mission capability and are normally resolved by substituting a failed component with a redundant spare. Contingency command plans have been created and approved for use to deal with these problems. Use of the contingency plan should return the spacecraft to a nominal operating configuration. If a nominal configuration does not result, the anomaly is upgraded to a Class III anomaly.

Class III Anomaly: A non-routine spacecraft problem not anticipated and for which no contingency plan currently exists. These anomalies are not necessarily understood and are not common. Class III anomalies may or may not have a direct operational impact.

a) When recalled to the SOC by the SOC Watch Captain (SWC) to investigate an anomalous condition, perform real time, on-console support to configure the satellite to a safe state or to analyze and resolve anomalous condition and return the satellite to nominal operational conditions. Anomaly notification will be made via telephone and in accordance with contractor provided recall list.

Performance Standards: During normal working hours, respond to anomaly notification within five minutes, be present in the SOC and begin to take appropriate action within 15 minutes of the alarm notification. After working hours, including weekends and holidays, respond to anomaly notifications within five minutes, and be present in the SOC to take the appropriate action within one hour of the alarm notification. Verbal and/or written responses to anomaly notifications are accomplished IAW the classification guide of each constellation.

a) Evaluate satellite state of health, recommend and implement corrective action(s) to ensure satellite safety and resolve anomalies to restore satellite operations and payload availability as soon as possible.

Performance Standards: All corrective action(s) implemented in accordance with approved Pass Plans, Contingency Plans, or satellites On Orbit Handbook.

b) Develop, maintain and submit for Government approval contingency pass plans to allow the SOC to resolve and reconfigure satellite’s subsystems in the event a known anomaly that has an impact on mission performance.

Performance Standards: Contingency pass plans available in the SOC. Contingency pass plans are reviewed and updated as state of health, configuration of the satellite changes, at least once a year.

c) Recommend and implement long-term solutions to mitigate additional degradation in satellite performance due to anomalous conditions or normal aging.

Performance Standards: Contractor recommends viable solutions and implements government approved recommendations to mitigate satellite performance degradation IAW with approved government timelines.

d) Coordinate with N33 to request satellite Original Equipment Manufacturer (OEM) support or proprietary information in order to safely and expeditiously recover the satellite from an anomalous condition.

Provide trend data and reports to N33 in order to coordinate COAs with satellite OEM to resolve anomalies and provide proprietary OEM data. Obtain N33/N34 approval to implement actions recommended by the satellite OEM. It may take up to 48 hours for satellite OEM support to be available in the SOC.

Performance Standards: Contractor informs N33 of the need for OEM support or data as required. Trend data provided to N33 as required by the OEM for analysis.

e) Provide satellite health status to N33 during anomaly recovery processes describing the event and any recommended Courses of Action (COAs) necessary to protect, maintain, and restore satellite mission capability safely and efficiently. Contractor shall provide initial status update verbally or via SIPR email followed by written report within 48 hours detailing all information related to the anomaly and any associated technical charts and graphs.

Performance Standards: Verbal notification completed with 1 hour of anomaly recognition. Written report submitted with 48 of anomaly recovery completion.

f) Ensure Det-D engineering personnel trained and ready to support Trend Analysis, Risk Reduction and Mitigation functions in case of COOP.

Performance Standards: Contractor train and qualify DET-D contractor engineering personnel within 6 months of reporting to work to support trend analysis, anomaly identification, and anomaly resolution in the case of COOP.

5. Mission Planning and Scheduling

The Mission Planning process encompasses long-term planning process (2 weeks in advance) and real-time scheduling and resource conflict resolution process (36 hours, 24 hours and on shift). Timely, accurate, and efficient scheduling of ground resources via NSCN, AFSCN and MUOS RAF is essential in meeting NAVSOC mission requirements.

Engineers responsible for each constellation initiate the mission planning process as early as possible during the mission-planning week. Each constellation group develop and submit their weekly satellite contact requirements based on approved SRDs. Supports requirement for each constellation are stored in excel file format. Contractor engineers will consolidate the requirements file for all the constellations and submit it to the SOMS contractor in accordance with NAVSOC Mission Planning Standard Operating procedures (SOP).

a) Maintain Mission Planning capability and proficiency at HQ and Det D.

Performance Standards: Mission Planning process exercised once a month and all Mission planning tools and procedures are up to date at Det D.

b) Develop and submit a list of satellite contacts required for FLTSAT, UFO, and POLAR EHF in accordance with approved constellation SRD.

Performance Standards: Contact list for each constellation accurately reflect the SRD requirements and any associated special ops requirements.

c) Consolidate MUOS satellite contacts list with FLTSAT, UFO, and POLAR EHF schedules. Resolve any scheduling conflicts between contacts schedule competing for the same ground resources utilizing the provided Mission Planning tools. N33 engineers will provide MUOS contact list to the contractor for processing.

Performance Standards: Mission planning, is conducted in accordance with NAVSOC Instruction

03210.15A (Mission Planning Procedures).

d) Attend weekly mission planning coordination meeting to finalize the consolidated schedule, resolve conflicting schedule requirements and optimize resource usage. The SWC, Satellite Engineers, Orbital

Analysts, and Network Systems personnel will attend the meeting.

Performance Standards: Consolidated schedule presented and downtimes are clearly marked with impact to operations articulated to the group. All scheduling conflicts presented to the group and alternate resources recommended and assigned to resolve conflict. Accurate aggregate weekly schedule (AFSCN, NSCN and MUOS RAF) submitted to the SWC for review no later than 24 hours prior to the requested 22

SOPS submission date/time.

e) Update the mission planning Tools, macros and procedures as dictated by changes to the satellite state of health or addition of new ground sites and in accordance the SRD and Configuration Management Instruction (CMI).

Performance Standards: Updated mission planning tools will be tested and delivered to the Government within 14 days of changes made to SRDs. Real-time mission planning functions including processing approved SSCRs and AFSCN ESD schedule changes performed in accordance with NAVOSC approved mission-planning instructions, checklists and AFSCN regulations.

6. Mission Documentation:

a) Review On-Orbit Operations Handbook OOH revisions and provide recommendations regarding any impact or changes required to current concept of operations due to these revision.

Performance Standards: OOH revision reviews and recommendations are completed within 30 days of receiving any OOH revisions. Notify N33 of any additional time required to review OOH revisions.

b) Conduct annual review of applicable SRD(s) and provide recommended changes to keep the SRD(s) up to date.

Performance Standards: SRD reviews and recommendations are completed within 60 days of the beginning of each FY (1 October).

c) Develop, maintain, and deliver Pass Plans, Task Lists, Task List Templates, Contingency Plans, Operations Procedure Manuals (OPM), operations instructions, procedures, and other equivalent documents to ensure compatibility with satellite subsystems. Pass Plans and Task Lists are a set of commands and telemetry verifications sent to the spacecraft by the operator and/or engineer during a support. Contingency Plans are specific Pass Plans executed during a support to correct an anomalous condition on the satellite.

Performance Standards: Pass Plans and Contingency Plans are completed and delivered to N33 NLT 12:00PM PST every Friday. Non time sensitive Pass Plans are delivered to N33 NLT 6 hours before AOS of support. Real Time Pass Plans, Contingency Plans and Perform files are delivered to N33 NLT 1 hour before AOS of the support. Approved Perform Files are uploaded to the servers 24 Hours before AOS of the support. Task Lists Templates are delivered to N33 NLT 30 days after any update.

d) Update and deliver applicable Satellite User’s Guides, Mission Procedural Guides for each constellation under this PWS that explains in detail all procedures, processes, and operations performed by operators and engineers.

Performance Standards: Satellite User’s Guides, Mission Procedural Guides for each constellation are delivered to N33 NLT 30 days after any update.

e) Maintain and deliver a Cross Reference Databases for telemetry versus mnemonics, telemetry by sub-commutation, and telemetry by display.

Performance Standards: Cross Reference Databases for telemetry versus mnemonics, telemetry by sub-commutation, and telemetry by display are delivered to N6 NLT 30 days after any update.

f) Update satellite status binders (SSB) for each satellite. Status binders contain an up-to-date satellite bus and payload configuration and planned changes, expected alarms list, weekly telemetry snapshot, current satellite location, and satellite health overview, and level 1 alarms log. These binders will remain in the SOC and be readily accessible to the operators, SWCs, and NAVSOC mission operation personnel.

Performance Standards: SSBs are updated and available to the SOC NLT 24 hrs of any required changes.

For expected level 1 alarms list, updates are implemented within 1 hours of required change.

g) Provide a “quick look” anomaly assessment report within 48 hours of the anomaly occurrence followed by final report of best assessment of the root cause of the anomaly after the condition is corrected.

Performance Standards: Quick Look reports are delivered to N33 NLT 24 hrs. prior to the start of anomaly recovery process.

h) Maintain and deliver all records associated with an anomalous event including but not limited to executed pass plans, contingency plans, telemetry and technical data collected, and documentation related to the event to assist the Government in any anomaly or space mishap investigation.

Performance Standards: anomaly records are delivered to N33 NLT 24 hrs after N33 request for the records.

i) Provide meetings minutes and trip reports for meetings attended on behalf of NAVSOC and related to satellite operations.

Performance Standards: Meeting Minutes and Trip Reports are delivered to N33 NLT 5 working days after the meeting is adjourned or trip complete.

j) Provide recommended changes to NSVT values and implement N33 approved changes to the NSVT values, tools and procedures. NSVT is a set of telemetry alarms limits that must be uploaded into the ISCS.

Performance Standards: NSVT change requests are submitted to N33 within one working day of limit change. NSVT values are updated within one working day of N33 approving the change.

7. Training:

Training at NAVSOC encompasses the following areas and requirements for the contractor:

Mandatory Government training – Contractor personnel are required to attend mandatory all hands training sessions; those sessions include but not limited to at a minimum: safety stand down training, COOP/Emergency

Action Plan training, COMSEC, information assurance and EEO training.

Engineering Technician (ET) training – Only designated Government personnel will be trained as ETs. The contractor will be required to conduct FLTSAT and UFO training session as coordinated with N71. These training sessions are around eight weeks long. After 8 weeks of classroom and OJT, ETs are given 4-6 weeks to complete their PQS and be ready for their Qualification Board.

Satellite Engineering (SE) training – The contractor shall train their own personnel on FLTSAT, UFO and

POLAR EHF. The contractor shall develop and conduct its own SE PQS and SE Qualification Boards evaluation standards.

The contractor is highly encouraged to provide recommendation and feedback to N71 regarding the training material, training schedule and the effectiveness of the training provided.

a) Attend mandatory all hands training sessions as scheduled by the command training officer. Provide recommendations to N71 regarding training material, curriculum and the effectiveness of the training provided.

Performance Standards: contractor personnel attend and participate in all mandatory training as scheduled.

b) Update and submit for government approval lesson plans, course curriculum, test and evaluation criteria, and training material tailored to help designated personnel assigned to perform ET duties understand FLTSAT and

UFO system and subsystems characteristics and operations, satellite command and control, support scheduling, satellite alarms recognition, notification and troubleshooting.

Performance Standards: Lesson plans, course curriculum, test and evaluation criteria, and training material are delivered to N71 NLT 10 working days before start of classroom training or OJT. Course curriculum, test and evaluation criteria are coordinated and reviewed with N71 training personnel.

c) Provide FLTSAT and UFO refresher training and associated lesson plans to NAVSOC designated ET trainers. Training sessions may be scheduled two times per year or as changes to satellites standard operating procedures requires changes to SOC procedures. Each session shall not exceed four weeks duration unless approved by NAVSOC management.

Performance Standards: contractor shall provide proposed training schedule and associated materials to N71 four weeks prior to training.

d) Provide FLTSAT and UFO On-the-Job Training (OJT) to NAVSOC designated ET trainers on satellite constellations system and subsystems characteristics and operations, satellite command and control, support scheduling, satellite alarms recognition, notification and troubleshooting. Training classes may be scheduled two times per year and as coordinated with N71. The purpose of this training is to prepare the NAVSOC trainers to provide classroom training to new hires, evaluate trainees PQS and pass the ET qualification board.

Performance Standards: On-the-Job proposed training schedule and materials will be provide to N71 and N32 personnel four weeks prior to commencement of OJT. OJT covers supports discussed during the classroom.

e) Provide training feedback and recommendations to N71 regarding training material, curriculum and the effectiveness of the training provided.

Performance Standards: Feedback and recommendations provide to N71 with 30 days after each training session.

f) Update training materials required to conduct FLTSAT and UFO Recurring Training (RT) related to satellite operations. These training sessions are designed to provide a quick refresher to the SOC on seasonal satellite design characteristics, operations, anomaly resolution procedures and other topics related to satellite operation at NAVSOC. This training expected to occur every Monday and Wednesday during day shift and evening shift turnover.

Performance Standards: Training topics are coordinated and delivered to N71 NLT 5 working days before start of training sessions.

g) Update UFO and FLTSAT training materials, Performance Qualifications Standards (PQS), conduct SE classroom training, SE OJT, and conduct Qualification Board evaluations for new personnel.

Performance Standards: Conclude SE training within 6 months of hiring new personnel and qualify SEs within

8 months of hiring new personnel.

h) Update UFO and FLTSAT materials required for the Monthly SOC training as coordinated with N32 and

N71.

Performance Standards: Monthly training materials are provided to N32 and N71 for review NLT than 5 working days before the training sessions.

8. Emergency Action and Continuity of Operations

Procedures to respond to unplanned events that disrupt NAVSOC HQ ability to support and sustain mission requirements are addressed in the Emergency Action Plan (EAP) and Continuity of Operations (COOP) instructions (NAVSOCINST 5510.3). To ensure NAVSOC’s ability to maintain mission readiness and meet mission requirements at both SOCs during planned downtimes, a handover from HQ to Det D and vice versa will be scheduled to transfer operations before each downtime. In case of a planned downtime that will prevent either

SOC from meeting their mission requirements, a failover will be executed to transfer operations to the alternate

SOC. The COOP instruction provides detailed procedures to allow continuity of critical satellite operations until full recovery can be achieved. The COOP contains, at minimum, immediate and supplemental methods and resources necessary to react, deploy, and recover from planned handover or an emergency.

a) Review and recommend changes to EAP and COOP during tabletop reviews and operational rehearsals to validate the plan.

Performance Standards: Support of tabletop exercise and operational rehearsals encompass entire extent of required operational capabilities and demonstrate the ability to fully execute the COOP. Lessons

Learned and recommendations from contractor participation in tabletop reviews and operational drills are submitted to DGR within 10 working days.

b) Maintain a list of deployable personnel and be prepared to deploy contractor HQ operational resources and personnel to other detachments in support of extended COOP when approved by the Operations and

Training Department Head.

Performance Standards: A list of qualified SEs and other operational personnel recall information is updated and available in the SOC within 24 hours of any changes.

c) Provide qualified FLTSAT and UFO engineers to support COOP events at Det D. COOP events can last longer than few days. Provide 1 SE to support 2 COOP events for lasting 10 working days. During COOP, FLTSAT and UFO supports categorized as “OT” (1 SO and 1 ET) in the SRD may will be converted to

“EO” (1 SO and 1 SE) supports to allow 24/7 staffing of Det D SOC during the event.

Performance Standards: Qualified SE(s) are available and ready to support extended COOP event.

9. Technical Analysis and Studies:

a) Provide technical reports, point papers, white papers and oral presentations related to satellite systems and subsystem concept of operations. The purpose of these analysis and studies are to investigate and develop innovative Tactics, Techniques and Procedures (TTPs) that improve satellite performance, or to protect the satellite and mitigate the impact any natural or manmade threats that can harm the satellite.

Performance Standards: Technical Studies and reports delivered to N33 on the due dates mutually agreed on with N33.

b) Evaluate proposed new satellite system concept of operations and Tentative Operational Requirements

(TOR) and document evaluation results and recommendations.

Performance Standards: Documentation delivered to N33 on the due dates mutually agreed on with N33.

c) Provide ground systems engineering support to N6 to resolve ground system anomalies. Specifically, analyze ground system TT&C uplink and downlink anomalous performance. Analyze transmit and receive power performance on ground system antennas and assess overall impact on TT&C operations. The government estimates 2 occurrences per year/160 hours per occurrence. The contractor shall provide engineering analysis of ground system anomalies and provide written recommendations on anomaly resolution to N6 within 30 days of tasking.

Performance Standards: Provide engineering analysis of ground system anomalies and provide written recommendations on anomaly resolution to N6 within 30 days of tasking.

10. Automation, Testing and Maintenance:

10.1 Software Support

a) Provide software maintenance support to UFO and FLTSAT Legacy Pass Plan Automation (LPPA) system.

Software maintenance support shall encompass trouble shooting software deficiencies with the LPPA system, identifying corrections to LPPA system deficiencies, adding approved enhancements, and implementing and testing corrections to the LPPA system. Testing can be conducted on the Test and

Evaluation system and/or the Operational system. Software deficiencies shall be documented using the

NAVSOC Error and Enhancement Reporting System (EAERS). Contractor shall follow the processes and procedures documented in the NAVSOC Configuration Management Plan. Changes to LLPA that require a change to training material(s) require the contractor to modify the training material(s) and conduct delta training.

Performance Standards: Software corrections and testing of corrections will be completed no later than 14 days after initial reporting of deficiencies. Software corrections will be submitted into the NAVSOC version of build (VOB) no later than 21 days after initial reporting of deficiency. Software enhancements and corrections shall be incorporated into the NAVSOC VOB per the NAVSOC Configuration Management Plan.

b) Provide software maintenance support to the MUOS Pass Plan Automation (MPPA) system. Software maintenance support shall encompass trouble shooting software deficiencies with the MPPA system, identifying corrections to MPPA system deficiencies, adding improved enhancements, and implementing and testing corrections to the MPPA system. Software deficiencies shall be documented using the

NAVSOC Error and Enhancement Reporting System (EAERS). Contractor shall follow the processes and procedures documented in the NAVSOC Configuration Management Plan.

Performance Standards: Software corrections and testing of corrections shall be completed no later than

14 days after initial reporting of deficiencies. Software corrections shall be submitted into the NAVSOC version of build (VOB) no later than 21 days after initial reporting of deficiency. Software enhancements and corrections shall be incorporated into the NAVSOC VOB per the NAVSOC Configuration Management

Plan.

e) Develop training material for MPPA and LPPA for enhancements and any deficiency workarounds.

Conduct training of the MPPA and LPPA enhancements and workarounds: all Engineering Technicians

(ETs), Satellite Operators (SOs), MUOS Satellite Engineers (SEs), and Command Duty Officers located at

NAVSOC HQ and Detachment Delta.

Performance Standards: Training material shall be provided to the government no later than 14 days after completion of software enhancements or identification of deficiency in which a workaround is required.

Training of new software enhancements or workarounds shall be conducted no later than 21 days after completion of software enhancements or identification of deficiencies.

10.2 Integrated Satellite Control System (ISCS) Testing

The contractor shall provide ISCS test support to the N6 department. ISCS testing shall encompass Tracking, Telemetry, and Commanding (TT&C), Mission Planning System (MPS) and scheduling, and automation functions.

Developmental and operational testing shall be conducted. Test support shall encompass:

a) Redline existing UFO and FLTSAT test procedures/plans.

b) Provide on console test support.

c) Analyze test results.

d) Document deficiencies using the EAERS process.

e) Develop and provide test report(s) to N6.

f) Updates to LPPA source code shall be incorporated into the Version of the Build (VOB) per NAVSOC

Configuration Management process NLT 30 Sep 2023.

10.3 Deliverables:

a) Updates to LPPA documentation (training documentation, requirements, and design) shall be delivered to

N6 NLT 30 Sep 2023. Documentation updates can be provided in Microsoft (MS) Word or PowerPoint formats. The government shall have unlimited rights on all LPPA source code and documentation.

b) Updates to MPPA source code shall be incorporated into the Version of the Build (VOB) per NAVSOC

Configuration Management process NLT 30 Sep 2023.

c) Any updates to MPPA documentation (requirements and design documents) shall be delivered to N6 NLT

30 Sep 2023. Documentation updates shall be provided in MS Word format. The government shall have unlimited rights on all MPPA source code and documentation.

d) Training documentation will be delivered to N6 NLT 30 Aug 2023. Documentation updates can be provided in MS Word or PowerPoint formats.

e) Training to all required personnel shall be completed NLT 30 Sep 2023.

f) ISCS test plan and procedures shall be delivered to N6 NLT 30 Aug 2023.

g) ISCS testing shall be completed NLT 15 Sep 2023.

h) ISCS test report(s) shall be delivered to N6 NLT 30 Sep 2023. ISCS test report(s) shall be provided to N6 in MS Word format.

11. Enterprise-wide Contractor Manpower Reporting Application (ECMRA)

a) Report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the NAVSOC via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications

Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil."