SOW 122 eLib.pdf

Statement of Work Task: Orbital Safety Analysis Task Order: 122 Task Modification: 6

I. Summary of Changes in this Task Modification

This modification adds scope to provide OSA support to Department of Commerce (DOC) Office of Space Commerce (OSC).

Summary of Work The Orbital Safety Analysis (OSA) task provides support to the NASA Conjunction Assessment Risk Analysis (CARA) program by identifying, refining, and reporting close approaches between CARA-supported assets and the Department of Defense high accuracy catalog. The OSA work and team are resident at Vandenberg Space Force Base, CA (VSFB) and the 19th SDS, Dahlgren Naval Air Station, VA . The OSAs collaborate with their counterparts in the 18th Space Control Squadron and the Commercial Integration Cell in support of NASA interests.

II. Period of Performance The period of performance of this task is from 1 November, 2019 through 31 October, 2024.

III. Task Description The task is divided into subtasks and functional subtasks as listed below. Specific functions performed on the functional subtasks include the detailed functions listed in this section for each Subtask. Additionally, functions outlined in each subtask may differ from that documented in the United States Strategic Command and Goddard Space Flight Center (GSFC) Interagency Operating Instruction (IOI), as this SOW reflects the most current operational requirements. The TM will provide a list of satellites that belong to each subtask group below.

a. Subtask 1: Basic CARA OSA Services – Provide OSA services for missions covered by the PPBE funding process.

i. Perform Functional Subtask 1: Routine OSA Support

ii. Perform Functional Subtask 2: Training Support

b. Subtask 2: Miscellaneous – Includes reimbursable missions (e.g., Maxar). Provide OSA services for other missions that may request support. For estimation purposes, assume Maxar.

i. Perform Functional Subtask 1: Routine OSA Support

ii. Perform Functional Subtask 2: Training Support

c. Subtask 3: DOC OSC Services –Provide OSA services for DOC OSC. For estimation purposes, assume Maxar.

i. Perform duties listed in Functional Subtask 3: DOC OSC Support

Functional Subtask Descriptions

a. Functional Subtask 1: Routine OSA Support

i. Maintain a staffing plan with on-console support of 24 hours, daily (7 days per week). OSAs must be reachable (on-call) during non-duty designated holidays.

ii. Personnel will be trained on all applicable USSF/Del2/18 SDS/19 SDS mission systems required to perform OSA duties, including future mission systems (e.g., CONDOR). May be subject to CARA training as deemed necessary by TM.

iii. Maintain task documentation, including certification and training records.

iv. Develop, maintain and use on-console procedures for performing all routine and contingency OSA tasks. Deviations resulting in operational incidents shall be reported to CARA and the TM.

v. Perform routine screenings of CARA assets using the Astrodynamics Support Workstation (ASW) (and/or other available DoD-produced) solution and O/O-provided ephemeris when available.

vi. Perform manual orbit determination evaluation and differential correction updates including modeling updates for all OSA-identified as well as CARA-identified secondary objects in the priority order specified on the work list.

vii. Perform special maneuver ephemeris screenings as requested by the CARA team.

viii. Maintain a record of which work list items have been examined and addressed each time a work list is produced and report status using HIE tool or as designated by TM.

ix. Perform tasking level evaluation and make tasking increase requests for all OSA-identified as well as CARA-identified secondary objects as needed.

x. Generate and deliver close approach products in accordance with CARA-defined reporting criteria and delivery methods.

xi. Provide 1v1 updates as requested by the CARA operations team or their officially designated mission representative. TM will provide a list of approved designees.

xii. Maintain a log of all contacts from mission designees including who called, when, nature of request, and resolution. Any unanticipated requests should be reported to the TM.

xiii. Ensure that the CARA team is notified of breakups and other operational exigencies in a timely fashion per procedures agreed-upon with CARA Operations lead.

xiv. Identify, troubleshoot, and report any system or script anomalies that impact CA processes or deliveries in accordance with procedures. Notify and escalate to CARA operations and/or TM as required.

xv. Perform script modifications as necessary to support the CARA mission.

Troubleshoot/repair scripts as needed.

xvi. Incorporate CARA-provided tools into OSA process as requested.

xvii. Maintain on-console log and report operations metrics, such as number of manual DCs, tasking level adjudications performed, errors identified, and anomalies that affected operations all at the unclassified level within the monthly report or other mediums as designated by the TM

xviii. Provide 18SDS/19SDS CA status updates, to include plans, requirements, script development efforts, coordination status with other cells, and ops procedure changes to CARA within weekly and monthly status reports or upon request.

xix. Post products to Space-Track.org as requested by the TM or designated CARA mission representative.

xx. Enter information provided by the NASA Mission Resilience Protection Program (MRPP) regarding electromagnetic interference (EMI) events into the CSpOC Joint Spectrum Interference Resolution Office (JSIRO) database.

xxi. Attend local meetings to assist in implementing the initiative to integrate the Civil space enterprise with the 18 SDS.

xxii. Attend the CARA semi-annual task planning meeting and provide OSA status and anticipated future work items for prioritization by team.

xxiii. Coordinate regularly with Commercial Integration Cell to ensure that NASA is integrated with the same processes as commercial as appropriate.

xxiv. Participate in Operational readiness reviews for ASW software releases. Ensure forthcoming products are tested end-to-end through CARA system before deployment. Coordinate as necessary with 18 SDS and Omitron employees supporting ASW development.

xxv. Request SME reach back support from CARA and other Omitron staff as necessary.

xxvi. Conduct weekly tag-ups with CARA Engineering lead or designee.

xxvii. Perform testing of new ASW releases on MIE and send all relevant output back to CARA ops team for further testing.

xxviii. Produce and deliver to CARA at Goddard updates to the historically-observed maneuverable satellite list monthly and as specified by TM.

xxix. Support commercial SSA data evaluation by performing ensemble OD solutions (SSN data plus externally-sourced data), generating special CA products, or performing other specific actions or evaluations as specified by the TM.

xxx. Support planning and coordination for implementation of CARA OSA functions at 19th Space Defense Squadron (19 SDS)/Dahlgren.

xxxi. Deploy to 19 SDS for backup support as approved by TM.

xxxii. Support space surveillance data export activities, including additional and modified scripting to fulfill NOAA/OSC STM data requirements, as specified by the TM.

xxxiii. Fill analysis-related space surveillance data requests as specified by the TM.

xxxiv. Provide monthly OSA operations summary and status briefing and participate in monthly CARA Operations tag-ups with CARA TM or designee.

1.5 Monthly status report Monthly

1.6 Semi Annual Planning Briefing Twice yearly at date specified by

TM

1.7 Monthly OSA operations

summary and status briefing

Monthly

2.1 Technical memos and specialty

reporting

As negotiated

3.1 Unclassified catalog extract Every 4 hours a day

(24hrs/day x7days/week)

V. Management Approach

d. Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work. Staff will be trained in all required duty functions including but not limited to orbital analysis, CAVENET, and Astrodynamics Support Workstation (ASW) functions. The OSAs shall be certified to perform all required procedures. The OSAs may also be subject to military training and certification.

e. Configuration Management

Documents will be covered under the ETD Configuration Management Plan as directed by the Task Monitor. OSA procedures and software will be covered under appropriate CM plans at the

18 SPCS.

f. Facilities

NASA will coordinate with the USSF to provide all necessary resources for executing the CARA OSA functions within the 18 SDS and 19 SDS. This includes access to 18 SDS/Del2/19 SDS mission systems, NIPR workstations with static IP addresses, SIPR terminals, long distance phones, direct CARA SFTP access, OMEGA (JIRA) document repository, company websites for timekeeping and administrative actions, and access to NASA websites related to mission support.

Omitron shall coordinate with L3Harris Corp to ensure clearances are maintained via the MOSAIC contract. All OSAs should be submitted for NASA clearances (crossover from DoD) upon hiring (Omitron SSO to initiate request to TM).

g. Risk Management and Best Practices

The contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the concurrence of the TM.

h. Government Furnished Facilities, Equipment, Software and Other Resources

The Government will provide account and passwords to government-furnished workstations where existing versions of various relevant software packages shall be maintained. It shall be the contractor’s responsibility to complete any required security-related training courses. NASA shall coordinate with the USSF for any resources required at the 18 SDS for performing the CARA OSA functions.

VI. Travel Travel may be required for this task and shall be as negotiated with and pre-approved by the TM.

2 trips from VSFB to Goddard for CARA planning meetings

1 trip from VSFB to Goddard for Operations training

2 trips from VSFB to Dahlgren for training

VII. Work Location This work shall be performed primarily at the 18 SDS location in building 8401 at Vandenberg Space Force Base, CA, but may also be performed at the 19th SDS, Dahlgren Naval Air Station, VA.

VIII. Reporting Requirements The contractor shall report status in person or via teleconference to the TM or designated alternates on a weekly basis. Reports shall include informal presentation of interim results, status of development activities, action item status, and summary of activities performed by each task member. The contractor shall provide on a monthly basis a detailed presentation of project activities, project master schedule, status, issues, and risks; this presentation will also serve as the weekly status update for the week in which it is delivered. This monthly report shall also contain a government-only section containing cost accounting data and other financial reporting as directed. The contractor shall provide all reports in advance of the weekly and monthly meetings via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall maintain meeting minutes and action items. Detailed schedules shall be provided to the TMs as required. The contractor shall also support the TM in the preparation of status reviews for internal and external funding sources. The contractor shall comply with any and all additional requests for support of meetings and development of reports. Draft versions of all deliverables shall be provided to the TM for review in advance of the final delivery. The contractor shall deliver all documents in portable document format (PDF) electronic form to the CARA JIRA library and the GSFC NMDB online library or other NASA server, as directed by the TM.

Budget estimate input will be prepared yearly and updated as necessary. Spending will be tracked at the subtask level and reported monthly. The contractor shall provide a weekly summary of the hours charged to the task by each individual contractor.

IX. Security Requirements This task shall comply with all 18 SDS IT Security Plans.

X. Rights XI. REQUIRED: The Contractor shall adhere to the FAR 52.227-17 RIGHTS IN DATA – Special

Works (2007).

XII. References United States Strategic Command and Goddard Space Flight Center (GSFC) Interagency Operating Instruction (IOI) for Robotic Missions Support, dated 30 Sep 2011.