Enclosure_BB_-_RTOs_-_12.13.18.pdf

ENCLOSURE BB

REPRESENTATIVE TASK ORDER

RFP 80GSFC18R0032

TO BE PROPOSED

CONTRACT - TBD

RTO 1 - New Lunar Mission

Task: New Lunar Mission

Task Order: 1

Task Modification: 0

I. Summary of Work

This task is designed to provide Flight Dynamics support to the New Lunar Mission (NLM) program. This is a Class C Mission. The work described herein will cover both pre-launch analysis and ground system development for NLM. The NLM is the next step in the return to the Moon and will continue to build on our knowledge of the Moon by mapping resources, investigating possible landing sites for future human exploration, and understanding the history of the Moon.

II. Period of Performance

The period of performance for this task will be from 01/01/2020 through 12/31/2020.

III. Task Description

The Flight Dynamics support for NLM will cover Phase C of the mission. Current planning assumes an NLM launch date of March 1, 2023.

The current schedule for planning purposes is below.

• PDR: will have already been held on October 15, 2019

• CDR: October 15, 2020

The task support includes, but is not limited to, the following.

Meeting Support

• Technical meetings of the NLM Flight Dynamics Team will be biweekly

• The Task will provide a written monthly report assessing technical, staffing, and budget statuses

• Participate in Working Group meetings with Project and Science team members as directed by the task monitor

• Task personnel will participate in meetings related to operations planning and execution of mission rehearsals.

• The task will also help to coordinate support from the Flight Dynamics Facility (FDF).

• Provide support for Project reviews (e.g. SRR, MDR, PDR, CDR, MOR, ORR, FOR) as needed.

Documentation Support

Support will be required for development and review of key mission documents. These include but are not limited to the following.

• Critical Design Review (CDR) Package – development and review

• Flight Dynamics System (FDS) Requirements - development

• Interface Control Document (ICD) between the Project and the FDS – development and review

• Operations Procedures document – development

Analysis Support

The following lists of analyses will be required from the list below:

• Orbit Determination Error Analysis – Analysis will be performed to determine the amount of tracking data required to meet mission requirements for the different phases of the mission (e.g. cruise to lunar orbit capture, mission orbit, etc.).

• DeltaV Budget Analysis – Analysis will be performed to support in developing the DeltaV budget for the entire mission. This includes computing the deterministic and statistical maneuvers needed from separation through capture into lunar orbit. Also included will be an assessment of the stationkeeping DeltaV required for the 2- year lifetime. All of maneuver analysis will be wrapped up to determine the DeltaV margin for the mission which can inform on the potential for an extended mission phase for

NLM.

FDS Development

A Flight Dynamics System (FDS) will be developed to perform the duties necessary for operations with requirements collected in the FDS Requirements Document. The major functions of the FDS will include maneuver planning (for all phases), maneuver validation, maneuver calibration, orbit prediction, and orbit product generation. Additionally, the FDS will need to perform sub-tasks necessary to perform the main tasks. For example, it will need to be able to process maneuver telemetry in order to perform maneuver calibration. Prior to implementation, the main software for the FDS will need to be determined … candidate packages include GMAT, STK, and FreeFlyer. The selection will be made based on cost of maintenance and suitability. Additionally, Matlab or Python scripting may be needed to augment the main package and provide for automation of some tasks.

Additionally, for FDS development the task shall

• Develop FDS to be compatible with TBD operating system to be used in the Mission

Ops Center (MOC)

• Support installations of the FDS in the MOC

• Document test plans and results for all updates.

• Maintain FDS system under configuration control

• Follow a CMMI Level 2 compliant process for any software development efforts

Simulation Support

• Provide internal training prior to project level reviews

• Provide planning products to support project mission rehearsals (MR)

IV. Deliverable Items and Schedules

At a minimum, the contractor shall deliver the items specified below.

Deliverable Due Date

FDS Requirements Document Draft: CDR – 2 months

Final: CDR

CDR Package Draft: CDR – 5 months

Final: CDR – 2 weeks

OD Error Analysis Report CDR – 6 months

DeltaV Budget Report CDR – 6 months

V. Management Approach

Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.

Configuration Management

Flight Dynamics Systems and documents will be reviewed and signed-off by NLM Project Management.

Facilities

Appropriate IT devices to support the analyses, testing, 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 install any required tools and utilities on the contractor’s equipment.

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.

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.

VI. Work Location

This work shall be performed at the contractor’s facility and at TBD Mission Operations Center located at GSFC.

VII. Reporting Requirements

The contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of testing activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies.

The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the GSFC NMDB online library, as directed by the TM.

RTO 2 - LST Flight Dynamics

Task: LST Flight Dynamics

Task Order: 2

Task Modification: 0

I.Summary of Work

This task is designed to provide Flight Dynamics support to the Large Space Telescope (LST) program. LST is a telescope which will orbit at Sun-Earth Libration Point 2 and perform science imaging. The work described herein will cover both pre-launch analysis and ground system development for LST. This task shall support NMDB in the areas of LST orbit determination (OD) analysis, incorporation of advanced navigation techniques, model and system development, trajectory and mission analysis, maneuver planning, analysis tools and ground system development, and pre-launch operations activities. Prelaunch support includes supporting internal and Project-level simulations, rehearsals and testing, and preparation of launch products.

II.Period of Performance

The period of performance for this task will be from 01/01/2020 through 12/31/2020.

III.Task Description

LST is planned to be launched in early 2023. LST orbit determination will be provided by the GSFC FDF for the duration of the mission. The contractor shall support the TM as needed including trade space analysis, requirements analysis, tools and techniques development (including development of advanced navigation techniques), reporting to other project groups, as well as provide documentation for analyses performed (including mathematical models), and procedure/process and results. The contractor is expected to work in close coordination with government flight dynamics staff assigned to the mission.

For each Subtask area, the contractor shall develop and maintain an online repository which includes current and past documentation, an action item ticket system, as well as software code and scripts.

LST Flight Dynamics Support

Ground System Development and Testing: The term ‘ground system’ encompasses all flight dynamics software used to support prelaunch analysis, testing and mission rehearsals, trending and trade analyses, and mission operations support. Analysis software packages, such as launch window analysis tools, can be maintained separately from the flight dynamics ground system, but are considered to be part of the overall ground system support for LST.

The contractor shall develop, maintain and update the LST flight dynamics ground system. This support includes developing requirements and specifications, defining interfaces, performing trade analyses, prototyping, and performing detailed design and specifications as necessary for the LST flight dynamics ground system. The flight dynamics ground system shall support LST during spacecraft testing, communications network and subsystems testing, mission rehearsals and eventually launch and mission operations.

The contractor shall maintain and update flight dynamics software and system components for a planned LST Project-level Ground Segment Freeze Date of L- 6 months. Multiple releases are expected, up to one per year. Maintenance shall begin immediately after each release. The final release before launch shall include all functionality for launch, early orbit and the science mission support, shall meet all Project Level requirements, shall generate all products as required in the FDF to LST Project ICD, and shall be completely integrated into the FDF and with FDF systems interfaces. Development shall be coordinated through an online Configuration-managed repository or similar technology, and via action and work item tracking. Work items shall be mapped to use cases, requirements, design specifications and operations procedures developed during mission rehearsals and simulations. Work items shall be documented as needed via work item tickets, sections in larger documents, or individual documents. These materials shall then form the core of operations and system documentation.

The contractor shall continue execution of a build/test/release plan (with associated schedule) for the flight dynamics ground system software, and update the plan at least every month. The contractor shall generate and maintain the requirements and functional specifications for the LST flight dynamics ground system software and operations support. Verification and validation methods shall be included as part of the requirements development process, and shall be developed in conjunction with Project ground segment teams. The contractor shall lead a broad-based review of all Project-level requirements to fully establish which requirements the analysis, software and operations support must comply with and to allow for traceability to those Project-level requirements from FDGS requirements.

Mission Analysis: The contractor shall perform mission analysis. Analysis efforts shall include performing launch vehicle trade analysis, launch window analysis, evaluating launch vehicle manufacturer-provided mission analysis documentation, taking into account LV constraints and limitations. The contractor shall analyze launch vehicle and LST collision avoidance options.

Analysis encompasses optimizing mid-course correction (MCC) and L2 orbit injection delta-V allocations to meet mission constraints, creating both impulsive and finite burn propulsion system model, generating tracking network contact predictions based on LST attitude and onboard antenna capabilities, performing orbit determination analysis for launch and early orbit; mission science orbit; and MCC, injection and stationkeeping (SK) maneuver planning, reconstruction and calibration with various tracking scenarios. Analysis shall be fully documented as a technical memorandum. Informal presentations of analysis results shall be made to the TM; more formal Project-level presentations may be required. The contractor shall prototype and perform trade analyses as necessary. Analysis shall be planned and tracked in a task plan and the schedule updated at least monthly.

Meeting and Review Support: The contractor shall participate in meetings as required. These meetings may include ground segment planning and support; spacecraft and mission design reviews; technical meetings both internal and with subsystems, spacecraft and science payload manufacturers; launch vehicle interface meetings, operations planning, including simulations and rehearsal meetings; and command authorization meetings.

The contractor shall support, at a minimum, a weekly flight dynamics support meeting with the TM, a monthly status meeting with the TM and branch management, and a monthly Project status meeting.

The contractor shall participate in and record minutes for all meetings supported.

The contractor shall participate in reviews as required. These reviews may include Project-level ground segment and spacecraft subsystems requirements reviews; software test readiness reviews, spacecraft and mission design reviews; mission and subsystem operations readiness reviews, as well as other subsystems’ peer reviews. The contractor shall provide documentation and presentation support for flight dynamics aspects of these reviews as required.

The contractor shall participate in flight dynamics peer reviews, in the areas of analysis, software and operations planning. Analysis peer reviews may include trade analysis evaluation, trajectory design, delta-v budget, and orbit determination; software peer reviews may include requirements, development, design and test readiness reviews; operations planning peer reviews may include orbit determination, maneuver support, internal and external interfaces.

The contractor shall produce documentation and present at these peer reviews as required by the TM.

Documentation for each review shall be delivered 2 weeks prior to the review. The contractor shall support in the resolution of review Requests for Action (RFAs) within 3 months or the next review, whichever is earlier unless otherwise directed by the TM.

Document Review: The contractor shall review and provide comments on relevant Project documents, including attitude, propulsion, thermal, communications, flight software and telemetry subsystem documents, tracking network interface agreements, ground segment requirements, mission operations plans, operating procedures, launch vehicle interface documents, and other relevant documentation as required.

CCSDS Standards Implementation: The task shall work closely with NMDB CCSDS government and contractor personnel to promote usability of current standards in review and standards in development for LST mission operations.

Pre-Launch Operations Support: The contractor shall support Spacecraft/Mission data flows, rehearsals, simulations and tests as required, including product generation and in-person realtime and offline support as approved by the TM. Rehearsal, simulation and test support shall be provided from the FDF via the CIL and other operational interfaces, and may involve the backup FDF facilities and procedures. The contractor shall create an internal test plan, complete with test documentation, ‘truth’ test data to train flight dynamics personnel and to ensure local operating procedures (LOPs) and software can support the nominal mission, as well as the most likely contingencies. The contractor shall generate post-test reports for internal and Project-level simulations. The contractor shall create and maintain a training test plan and matrix for flight dynamics personnel, assessing the team’s abilities to support nominal and contingency mission operations. The contractor shall work closely with the TM, NMDB and FDSS III management to ensure the LST flight dynamics team and the FDF is ready to support mission operations. The contractor may be required to provide trained flight dynamics liaisons in the mission operations center in support of Project rehearsals, simulations, in preparation for launch and early orbit mission operations.

Operations Integration and Coordination: The contractor shall coordinate across the entire flight dynamics team and with operations facility personnel to ensure all designs, operational agreements, and interfaces are within the capabilities of the FDF operations facility. The contractor shall coordinate LST support with other FDF technical and management to enable integration of flight dynamics ground system and other software needed to support pre-launch support for rehearsals and simulations and preparation for launch and for actual launch operations.

IV.Deliverable Items and Schedules

• Spacecraft CDR will be 7/20/2020

• Ground System CDR will be 10/20/2020

• At a minimum, the contractor shall deliver the items specified below.

Deliverable Due Date (No later than)

Monthly Detailed work items Schedule/Plan update Monthly, or as negotiated with TM

Monthly Status Report input for NMDB and Project Monthly Status Reports, including a high level version of the Schedule/Plan

Monthly, or as negotiated with TM

Peer Review 4 weeks before Spacecraft CDR

Materials for Spacecraft CDR 2 weeks before Spacecraft CDR

Ops Con Document – Baseline 2 weeks before Spacecraft CDR

Trajectory Design Plan – Baseline 2 weeks before Spacecraft CDR

Materials for Ground System CDR 2 weeks before Ground Sys CDR

FDF-MOC ICD – Baseline (contains all the expected product deliverables, cadence, and format)

2 weeks before Ground Sys CDR

Navigation Plan – Baseline (describes how OD will be done) 2 weeks before Ground Sys CDR

SLA or PSLA – Baseline (services agreement between the project and all the Networks)

2 weeks before Ground Sys CDR

V.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.

b. Configuration Management

Systems and documents shall be covered under the Configuration Management (CM) Plan.

Configuration management for the flight dynamics ground system and other support tools shall be documented in the CM Plan, which shall be updated as necessary. The contractor shall configuration control and maintain a database containing LST data, the flight dynamics system and the supporting tools. Raw tracking data measurements, telemetry, and products sent and received shall be archived for no less than end of mission plus 5 years.

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 on-site and off-site facilities as required, and to install any required tools and utilities on the contractor’s equipment

The contractor shall explore options for storage and high performance computing including cloud services.

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 shall provide accounts and passwords to government-furnished workstations where existing versions of various relevant software packages shall be maintained.

VI. Work Location

This work shall be performed at the contractor’s facility and the Goddard Space Flight Center, primarily in the Flight Dynamics Facility (FDF).

VII. 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, and action item status. The contractor shall provide all reports at least one day in advance of the monthly branch status meeting or LST Project meetings via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies.

The contractor shall report technical and management status including Risk, Schedule and Staffing at a weekly management/leadership meeting. The schedule/plan shall be reviewed and updated at least every month.

Within 28 calendar days of award of this task, the contractor shall submit to the TM a candidate schedule/plan structure to serve as the LST flight dynamics schedule of record.

An updated schedule/plan shall be submitted to the TM illustrating the project lifecycle through L+6 months at the components and system feature-level. The schedule/plan shall include all work activities updated with proper status (%complete, dependencies, relevance to critical path). This schedule/plan shall be included in the FDSS-III Monthly report.

Monthly, an updated schedule/plan shall be submitted to the TM in MS Project Format showing detailed activities required to support analysis, internal and external tests/simulations/rehearsals, flight dynamics ground system documentation, development, quality review, testing, and integration of components into appropriate systems illustrating the current week and the next two calendar months.

The contractor shall comply with any and all additional requests for status meetings and reports.

The contractor shall deliver all documents as directed by the TM.

RTO 3

Flight Dynamics Facility (FDF) Mission Development and Operations

I. Summary of Work

This task order statement of work (SOW) describes hypothetical support requirements for missions new to the FDF. The purpose of including an RTO for FDF operations support is to allow the contractor to illustrate the range of experience, skills, and innovative processes that it would apply to the development of the capabilities needed to support these missions.

The support required by this statement of work covers two areas, described in detail in Section V of the SOW below:

A. Ground System Development and Launch Support for the Achilles Launch Vehicle

(ALV)

B. Launch and Early Orbit Support to the Three Blind Mice (TBM) Mission

The contractor shall expect to work closely with the Government’s Task Monitor (TM) for this task, and to work with NASA and contractor personnel as well as NASA’s partners in other Government agencies, industry, and academia when needed to accomplish the technical objectives of the task.

Details of the work by subtask are provided below. This work will generally require the contractor to utilize a mix of GSFC in-house and commercial-off-the-shelf orbit determination and mission planning software in performance of the work items. The contractor may, in some situations, propose the use of their own proprietary software. The technical and cost advantage to the Government should be clearly justified.

II. Period of Performance

The period of performance for this task will be from 01/01/2020 through 12/31/2020.

III. Work Location

All (100%) of this work is expected to occur at the FDF at Goddard Space Flight Center (GSFC).

IV. Government Property

The Government will provide the facility and facility services for mission support functions performed onsite at GSFC. Within these onsite facilities, the Government will provide office and workstation furniture that are required to manage and operate the spacecraft and its ground support elements.

A summary of other Government-furnished equipment that may be applicable to this task is available in the FDSS Bidder’s Library.

V. Specific Tasks The contractor shall perform the following specific tasks during the period specified in Section II.

A. Ground System Development and Launch Support for the Achilles Launch Vehicle

(ALV)

The ALV is a new launch vehicle being developed by NASA to deliver large payloads to low earth orbit. The organization at Kennedy Space Center (KSC) that is responsible for building the vehicle has just entered into an agreement with the Space Network (SN) and the Near Earth Network (NEN) to provide vehicle command and telemetry capabilities to the operations center at KSC for the maiden flight on November 15, 2020. The SN and the NEN have just required the FDF to provide the acquisition data for the vehicle. Nothing else is currently known about the

ALV.

The contractor shall perform the following activities:

• Develop an assessment of infrastructure (hardware, software, interfaces, etc.)

requirements needed to support the vehicle’s maiden flight.

• Develop the capabilities (including proposing and performing relevant tests) needed for this support, as identified in the above assessment.

• Support prelaunch preparations, including testing, simulations, training, documentation, reviews, and analysis as needed.

• Launch day support, including relevant product deliveries.

• Post launch analysis, assuming support to future ALVs.

B. Launch and Early Orbit Support to the Three Blind Mice (TBM) Mission

The TBM mission consists of three university-built cubesats being deployed from the ALV during its maiden launch on November 15, 2020. The university has been planning to use Joint Space Operations Center (JSpOC) Two Line Elements (TLEs) for navigation. The university has recently been told that these TLEs may not meet their navigation requirements and has reached out to the FDF for support.

The contractor shall perform the following activities:

• Provide a report of recommendations to the TM by February 28, 2020 addressing options for meeting the mission’s navigation requirements.

VI. Deliverable Items and Schedules

All deliverables are specified in Section V.

VII. Reporting Requirements The contractor shall report status to the TM and the FDF Operations Director on a daily basis.

The contractor shall propose the process by which these Government representatives are apprised of the status of the activities on this task and the process by which open actions and concerns are tracked to closure. The contractor shall support the preparation of materials for technical discussions and presentations when needed. The contractor shall compile the results of technical analyses into technical reports for archival purposes and when appropriate, into conference-quality papers for external audiences.

VIII. Risk Management Requirements The contractor shall perform risk management according to all applicable NASA policy directives, including, but not limited to, the applicable versions of NPR 8000.4 and/or NPR 7120.5.