SOW 123 eLib.pdf

Statement of Work Task: NASA Conjunction Assessment Risk

Analysis (CARA) Task Order: 123 Task Modification: 5

I. Summary of Changes in this Task Modification

This modification extends the period of performance through October 31, 2024.

II. Summary of Work The NASA Conjunction Assessment Risk Analysis (CARA) program provides support to mission customers to analyze collision threats to their assets and to develop processes for reacting to those threats. The CARA team serves as the primary technical interface between the 18th Space Defense Squadron (18 SDS) and the flight project for the conjunction assessment effort.

Interface with other outside organizations may also be required, as defined by the Task Monitor

(TM).

III. Period of Performance The period during which the work for this task shall be performed is between November 1, 2019 and October 31, 2024.

IV. Task Description The majority of the CARA work is funded by the mission programs through the annual Planning, Programming, and Budget Execution (PPBE) process managed by the Science Mission Directorate (SMD) at NASA Headquarters. Funding for the task that is outside of this process will be placed on separate subtasks, however any work covered by the PPBE funding will be performed under Subtask 1 and its functional subtasks as noted below.

a. Subtask 1: Basic CARA - Provide CARA services for missions covered by funding approved for CARA through the NASA PPBE funding process.

i. Perform Functional Subtask 1: Operations

ii. Perform Functional Subtask 2: Ground System Support

iii. Perform Functional Subtask 3: Analysis

iv. Perform Functional Subtask 4: Training

v. Perform Functional Subtask 5: Task Management

vi. Perform Functional Subtask 6: NASA-DOD Liaison Services

b. Subtask 2: Miscellaneous – Provide CARA services for reimbursable missions or provide individually-funded special analysis projects to missions. For estimation purposes, assume 3 1-staff-week analysis efforts.

Functional Subtask Descriptions

1. Functional Subtask 1: Operations

i. Provide monthly reports on conjunction screening history and close approaches as requested by customer missions and approved by TM.

ii. Provide daily summary reports of screening results to mission customers.

iii. Serve as liaison between the screening data provider and missions being screened to offer expertise regarding interpreting screening data and to ensure the timely delivery of data to the screening data provider and missions.

iv. Communicate with stakeholders regarding events of concern, including email notifications of event status and definition of High Interest Events (HIE).

Provide HIE briefing packages and, when requested, attend meetings to brief this material. Provide evaluation of conjunction assessment results to TM.

v. Provide detailed assessment of conjunction risk during CA conjunction events.

vi. Support Flight Projects in developing risk mitigation maneuver strategies that meet mission orbit requirements.

vii. Perform database trending & reporting as specified by the TM.

viii. Interface with screening data provider to develop support schedules for events requiring additional screenings and tasking.

ix. Provide evaluation of conjunction assessment screening results as received from the screening data provider. For those results that will be delivered to the mission, provide the screening results to the mission by the milestone, or time, agreed upon with the mission.

x. Interface with the Combined Space Operations Center (CSpOC) and/or the 18th Space Defense Squadron to assess and improve the products and services being provided to NASA.

xi. Interface with screening alternate/backup providers as specified by the TM to assess and improve the services being provided to NASA (e.g. 19th Space Defense Squadron (19 SDS)).

xii. Assist new missions in setting up a CA process and associated interfaces, including reviewing requirements and modifying software and databases to handle the new missions as well as drafting an interface document.

xiii. Develop and maintain operational procedures, job aides, and operational guidelines for routine CARA operations support. Identify operational efficiencies using automation and other process improvements and implement them as approved by the TM.

xiv. Routinely produce CA metrics as defined with the Task Monitor. Work with the CARA Analysis team to provide metrics that can be presented in the Metrics IPT forum sponsored by DOD and which will help provide a better understanding of the CA process and the orbit regimes in which CA is performed.

xv. Provide 24x7 “on-call” support through the use of smartphone and remote laptop access. The phone service plan will be charged as an ODC to the task.

xvi. Perform post-event analysis and conduct post-event debriefs for events as prioritized by the TM. Maintain an archive of post-event analyses for knowledge capture.

xvii. Perform ASW Synthesized Covariance Analysis and Database Updates quarterly.

xviii. Perform semi-annual needs-assessment analysis and report to TM via the semi-annual task planning meeting.

xix. Maintain proficiency with, and engage as operationally appropriate, third-party tools or data sources for CA conduct as specified by the TM (e.g., SDA, JAC).

xx. Support NASA/DoD CA Interagency Working Group, NRO COLA cons, CA TAC, and other meetings as assigned by the TM.

xxi. Perform operations evaluations and CONOPS updates as needed, including changes related to any fielded prototypes. Ensure related documentation be included in training packages.

xxii. Maintain the CARA Operations team training program material, including incorporation of any new CAS features and offline tools as well as any changes to the Operations Concept. Work with the CARA Analysis Team and ground system personnel to incorporate changes resulting from new capabilities.

xxiii. Assist TM with updates to devolution-related activities, including preparation of CA Standard and CA Handbook, drafting Devolution Pilot materials, and supporting related meetings.

xxiv. Conduct the CARA Users Forum meeting at least quarterly or on dates as agreed with the TM. Prior to completing development for any software modifications that directly impact the missions, conduct a User’s Forum meeting to describe software changes that affect users and collect feedback.

xxv. Support development of back-up CA Ops capabilities using Dahlgren/19 SDS.

This includes, but is not limited to:

a. Develop and maintain console procedures for utilizing 19 SDS as a backup in the event of a VSFB outage

b. Conduct semi-annual exercise of backup capability to ensure continued feasibility and familiarity of personnel with procedures.

c. Gain and maintain required training to utilize 19 SDS systems to provide back-up CARA OSA support as needed as specified by the

TM.

xxvi. Develop and maintain procedures for supporting devolved missions.

xxvii. Create and maintain console procedures for use of CARA backup system on the Goddard-provisioned Amazon Web Services (AWS) Commercial Cloud.

xxviii. Conduct semi-annual exercise of CARA backup system on the Goddard-provisioned AWS Commercial Cloud.

xxix. Review large constellation and commercial operations concepts upon request to determine their effect on CARA’s supported missions. Develop and maintain related documentation to be included in Operations and mission training packages.

xxx. Perform transition of operational support to AWS cloud environment

a. Update processes and procedures, and training materials for cloud

b. Conduct cloud Operations staff training and certification

xxxi. Staff operations shifts as specified by the TM. Currently 2 shifts spanning 8 am-10 pm local..

xxxii. Create and maintain a mission list of CARA assets that require support; Include launch date, KDP dates, maneuverabilty, altitude, inclination, and timelines for preparing CAOIA and OCAP documentation preparation and scheduling.

Documentation development shall be as prioritized by the TM.

xxxiii. Provide monthly CARA Operations effort and participate in monthly tag-ups with CARA TM or designee.

xxxiv.

2. Functional Subtask 2: Ground Systems Support

i. Perform semi-annual needs-assessment analysis and report to TM via the semi-annual task planning meeting

ii. Prioritize discrepancy/enhancement tickets and maintain delivery schedule.

iii. Develop suggested software development and deployment contents for approval of TM such that there is no lag between completion of one deployment and the commencement of work on the next one.

iv. Develop and deploy software deployments to the Conjunction Assessment System (CAS) and, if required, operational off-line tools, that include new capabilities or architectural improvements as specified by the TM.

v. Develop software delivery & maintenance plan. Provide weekly status of progress.

vi. Maintain the Conjunction Assessment System (CAS) documentation on a configuration managed repository, to include relevant requirements and architecture documentation, math specifications, and training updates.

vii. Develop and maintain the CARA Configuration Management Plan and Software Development Plan, and observe and adhere to CM processes and practices as described in those plans, including conducting Software Design Reviews and Software Change Boards as required. Updates to CARA CM plan or other process changes only as agreed with TM.

viii. Provide CAS Ground System Maintenance & Operations. Perform technology trade studies and provide recommendations on value-added hardware and software technologies and implementations as specified by the TM.

ix. Coordinate required cloud system administration support with the cloud administration team/staff to develop requirements and execute plans for accomplishing those items.

x. Provide maintenance of CARA system including upgrades, as specified by the TM, to the cloud architecture and software. This support includes hardware and software procurements needed to support the mission.

xi. Support the CARA Devolution pilots as specified by the TM.

xii. Produce distribution versions of CARA tools to be forwarded to NASA missions, as directed by the TM.

xiii. Produce software development kits (SDKs) to distribute the source code and accompanying test cases for key CA algorithms, as directed by the TM.

xiv. Support development and exploration of MCP (Mission Cloud Platform) Cloud capability as well as reviewing the SLA document and other agreements, as specified by the TM.

xv. Perform both ground systems architecture and software development functions.

The Ground Systems Lead is responsible for system engineering to include developing an accurate and complete requirements specification for software releases, acceptance test planning, and software review briefings. Execute effective communications strategies between the ground systems lead and the development lead to ensure developer understanding of requirement intent, including tag-ups, code reviews, and detailed ticketing.

xvi. Work with MCP Cloud team to set up required environment(s) on AWS (Amazon Web Services) Cloud.

xvii. Track direct cloud costs by different expenditure category and present such data, including estimates at completion, to the TM at the weekly task meeting.

xviii. Develop and maintain written procedures in conjunction with CARA Ops and Analysis teams for accessing cloud and initiating instances.

xix. Conduct training for all CARA Ops personnel and any other personnel specified by the TM as needed for system and tool updates and enhancements.

xx. Generate and maintain training materials to train devolved operators or other non-CARA users on CARA software and tools, as required.

xxi. Conduct feasibility studies for new systems engineering approaches, such as automated regression testing, requirements tracking, and workflows.

xxii. Perform trade studies and implement modern practices for both software and hardware development life-cycles as approved by TM to ensure that Ground System updates and development practices remain relevant to current industry standards.

xxiii. Develop and write test plans and procedures that identify gaps in the test coverage and validates overall ground system operations.

xxiv. Develop verification and validation techniques for the different types of ground systems requirements and implement as approved by TM.

xxv. Develop and maintain a bi-directional traceability matrix between requirements and test plans

3. Subtask 3: Analysis

i. Interface with the 18th Space Defense Squadron to assess and improve the services and products being provided to NASA.

ii. Interface with screening alternate/backup providers as appropriate (e.g., 19

SDS, National Space Defense Center).

iii. Perform analysis as approved by TM to investigate and implement needed capabilities, which may include:

a. Classified access

b. 9 digit implementation and testing

c. Non-traditional data implementation and testing

d. Space Fence catalogue evaluation and screening/HIE loading experiments

iv. Evaluate new missions before they are added to CARA support to determine whether there are any mission-unique trajectory or operations aspects that will have an impact on existing CARA processes and procedures.

v. Develop tools and perform CA-related mission design analyses in cooperation with new missions, such as satellite colocation analyses, serious conjunction density analyses, mission trackability analyses, and ephemeris accuracy and covariance realism analyses.

vi. Maintain 3rd party tool evaluation materials (test plans, benchmark cases, etc.) as prioritized by the TM.

vii. Work with TM to prioritize analysis items and perform semi-annual needs-assessment analysis and report to TM via the semi-annual task planning meeting.

viii. Analyze concepts and new algorithms to improve the CARA capabilities.

ix. Provide analysis from within the Secure Compartmented Information Facility (SCIF) at Peterson SFB, the 18th Space Defense Squadron facility at Vandenberg SFB, the 19th Space Defense Squadron at Dahlgren Naval Air Station, and/or at NASA Goddard Space Flight Center as requested by the TM and as approved by facility management.

x. Perform requirements analysis for new capabilities and new customers.

xi. Write and present technical paper(s) at conferences as assigned by TM.

All papers must be pre-approved by the TM prior to submission and must follow the NMDB approval process for abstract and paper submissions.

xii. Perform conjunction analysis for end-of-life/deorbit/orbit change scenarios as requested by flight projects with TM approval.

xiii. Perform FAA/FCC/DoC license request evaluation analysis for NASA HQ as requested by the TM.

xiv. Perform regime characterization analyses for flight projects to determine the number of conjunctions that can be expected for a given mission.

xv. Develop prototypes to rapidly field new techniques to the CARA Operations team for ops evaluations.

xvi. Develop training materials for CA prototypes and provide to CARA Ops Team.

xvii. Support CARA team training as requested by Ops team.

xviii. Perform recurring analyses needed for updates to key CARA parameter files, such as screening volume sizes, covariance synthesis factors, CONOPS threshold values, and any other parameters that require routine update.

xix. Support periodic internal task Engineering Review Boards (ERB) of any long-term analyses and research domains as requested by the Chief Engineer.

xx. If directed, conduct analysis efforts in evaluation of Space Fence sensor performance.

xxi. Evaluate emerging CA industry toolsets and practices, as well as pay-per-use CA data sources, for relevance and possible incorporation into CARA operations and processes.

xxii. Support development of comprehensive standards and guidelines for the Agency’s non-HSF CA activities, including conducting enabling analyses.

xxiii. Interact with the CA community to assist NASA with shaping the vision for the NASA CARA activity.

xxiv. Support CA community meetings as assigned.

xxv. Support interactions with outside organizations (contractor and government personnel) to exchange data pertinent to conjunction assessment analysis for all CARA –supported assets.

xxvi. Provide assistance to TM in developing conjunction assessment and space situational awareness policies, procedures, and practices.

xxvii. Provide technical review of Releasability Matrix, Non-Disclosure Agreements, Operating Instructions, training materials, procedures, Operations Agreements, ICDs (Interface Control Document) or CAOIAs (Conjunction Assessment Operations Implementation Agreement), and other CARA documentation.

xxviii. Perform operations evaluations and CARA CONOPS updates as needed, including changes related to any fielded prototypes.

xxix. Support the CARA Users Forum meeting as requested.

xxx. Support long-term (five-year outlook) task planning in conjunction with the TM and Chief Engineer

xxxi. Ensure proper QA and review of products before delivery of draft versions to customer.

xxxii. Assist TM with updates to required documentation, including preparation of CA Standard, CA Handbook, etc.

xxxiii. Perform Orbital Collision Avoidance Plan (OCAP) analyses required for new missions in a priority order defined by the TM, document analysis findings and evaluate missions’ preliminary analysis results for OCAP documentation.

xxxiv. Archive all CARA peer-reviewed conference publications by main categories of research foci as approved by TM, for customer accessibility using Microsoft TEAMS.

xxxv.

4. Functional Subtask 4: Training

i. Perform initial and recurring training as necessary to ensure fully certified ops team to execute CARA mission requirements.

ii. Conduct operations training for all CARA Ops personnel and any other personnel specified by the TM as needed.

iii. Create and maintain a staff certification process for new operations team members including a certification examination.

iv. Identify and train new part-time personnel yearly or as specified by the TM.

v. Maintain and document internal CARA training products. Review CARA training materials and procedures annually and as necessary for new activities to ensure CA best practices and CARA standards and requirements are maintained.

vi. Maintain and document CARA training products for external/devolved users.

Review training materials and procedures annually and as necessary for new activities to ensure CA best practices and CARA standards and requirements are maintained.

vii. Provide support to OSAs from CARA and contractor staff as necessary.

viii. Complete AWS Trainings and Certifications as necessary and approved by TM to maintain proficiency for developing in CARA’s Cloud environments

5. Functional Subtask 5: Task Management

i. Report routinely on program activities, schedules, issues, risks, and costs, through the forums listed in this SOW and upon request

ii. Coordinate between task personnel and with the TM to develop a task plan that meets the needs of the task. The plan shall be maintained using an integrated electronic scheduling and ticketing package as specified by TM. Schedule slips and blockers/risks to progress should be reported weekly during task tag-ups.

iii. Coordinate activities in multiple, geographically separate locations efficiently, aided by the use of appropriate enterprise management tools. Assemble and conduct semi-annual Task Planning Workshops at which task requirements, including software needs, will be prioritized for the coming six months.

iv. Support long-term (five-year outlook) task planning in conjunction with the TM and Chief Engineer/Analysis team.

v. Monthly financial management reporting by subtask

vi. Monthly hours reporting by functional subtask

vii. Monthly manifest of the prime and subcontracting employees, by name, supporting the different project subtasks and their nominal levels of allocation.

viii. Assess and communicate annual staffing and resource needs with a projected 5-year outlook.

ix. Provide technical review of CARA documentation as specified by the TM.

x. Ensure deliverables are produced and documented in accordance with SOW requirements.

xi. Conduct weekly coordination tag-ups with CARA and OSA Task lead or designees.

xii. Review and develop a CARA landing page that defines the general main subtasks and expected deliverables.

xiii. Develop and maintain an active page that captures ongoing work summarized after each Task Planning event for monthly reviews.

xiv. Develop and maintain a roles and responsibilities document (RASCI matrix) for approval by TM and perform periodic reviews as specified by TM.

xv.

6. Functional Subtask 6: Perform NASA-DOD Liaison functions as specified by the TM

i. Assist missions and Flight Projects with the development and submission of any Orbital Data Requests within 7 days of initial request

ii. Maintain listserv for requests and communication to/from NASA-DOD Liaison

iii. Maintain ODR tracking list

iv. Ensure that analysis/briefing packages submitted by mission for redistribution

ODRs are evaluated by the appropriate team member and the ODR written if needed within 2 weeks of mission request.

7. Deliverable Items and Schedules

3.1 Prototype tool documentation (requirements

updates, training, spec updates)

Accompanies each prototype update

3.2 Engineering Review Boards (ERB) schedule

and proceedings

As needed

3.3 Source code for all prototype software

deliverables

With software delivery

3.4 Papers/reports/presentations describing

results of assigned analyses

As directed

3.5 Conference papers As directed

4.1 CARA Ops Team Training Material Updates Annual updates and internal updates resulting from new capabilities

4.2 External User Training Material Updates

with voice track

Annual updates or as negotiated with TM

5.1 Task Planning Workshops Semi-annually

5.2 Financial Program Management Review Monthly, or as specified by the TM

8. Management Approach

a. Staff Allocation, Expertise, and Skill Mix The contractor shall staff this work item with the appropriate skill mix and staffing level for the work. The contractor lead position who oversees the execution of this task shall be dedicated full time to CA-related tasks and experienced in managing a large (e.g., 10 or more people) team in performing operations work. Task organizational structure and roles and responsibilities of team members shall be as agreed with the Task Monitor.

b. Configuration Management Documents will be covered under the Flight Project Configuration Management Plan or the ETD Configuration Management Plan as specified by the customer. CA software will be covered under the CARA CM and Software Acquisition Management Plan (SAMP) documents.

c. Facilities Appropriate IT devices to support the analyses, specification development, and report development are required. It shall be the contractor’s responsibility to provide and set up local workstations and network connections at the contractor’s off-site facilities as required, and to provide and install any required tools and utilities on the contractor’s equipment.

d. 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 compliance of the TM.

e. 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 GSFC required security-related training courses. NASA shall provide space for the CA System in the FDF and the FDF backup facility as well as office space in the FDF for CA operations personnel.

9. Travel Non-local travel will be required for this task and shall be as negotiated with and pre-approved by the TM. The total number and location of trips are subject to change with Task Monitor approval. For planning purposes, please assume the trips described below. Unless otherwise directed, travel costs should be charged to Subtask 1.

2 trips to CONUS for the A-train MOWG

2 trips to Washington DC for technical and/or task planning meetings

1 trip to Denver, CO for CA Operators’ Workshop May, 2024

1 trip to Denver, CO for the 2024 Astrodynamics Specialist Conference

1 trip to Austin, TX for the 2024 Space Flight Mechanics Meeting

1 trip to Colorado Springs for technical/planning meeting

1 trip to VSFB for OSA training/tool integration

1 trip for the Nov 2024 AWS RE:Invent Conference, Las Vegas, NV

1 trip to VSFB for the NASA/DoD CA IWG

10. Work Location This work shall be performed primarily at the Goddard Space Flight Center. The contractor will be required to perform some work at the contractor’s facilities, Peterson SFB, Dahlgren NAS, and at Vandenberg SFB.

11. Reporting Requirements The contractor shall report status in person or via teleconference to the TM or designated alternates on a weekly basis, or as specified by the TM. Reports shall include informal presentation of interim results, status of software development activities, action item status, schedule milestone progress, and summary of activities performed by each sub-task. The contractor shall provide on a monthly basis, or as specified by the TM, 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 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, as specified by the TM. 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. Final deliveries of all documents shall be posted to a NASA server, as specified by the TM. Budget estimate input will be prepared yearly and updated as necessary. Costs shall be tracked at the subtask level and reported monthly. The contractor shall provide a monthly summary of the hours charged to the functional subtasks by each individual contractor upon request of the TM.

12. Security Requirements This task shall comply with IT security requirements as documented in the FDF IT security plan for all systems located in the FDF on IONet. Systems not covered on the FDF security plan shall be covered under the Code 590 security plan and supported by the Code 590 sustaining engineering support, or the Code 700 Mission Cloud Platform (MCP) security plan for systems on the cloud, or the contractor sustaining engineering support depending on system location.

13. Rights REQUIRED: The Contractor shall adhere to the FAR 52.227-17 RIGHTS IN DATA – Special Works (2007).

1. References None