SOW 148 eLib.pdf

Monthly status reports Monthly Results of work done will be documented in a monthly report and submitted via the FDSS-III contract process.

Preliminary results for

JAXA

11/13 Provide preliminary results for both the snake maneuver and following a repeating ground track as options for formation flying. This should include an idea of how many burns are necessary and total delta-v for a year in low and high drag environment. For the snake maneuvers, the time between burns should be assessed to show how much or little flexibility exists. This should be done as a PowerPoint presentation for the MDWG on 11/13 which will feed a presentation to JAXA on 11/16.

FDS Requirements for AOS-Storm defined

12/1/23 Document all AOS-Storm FDS requirements: formation flying, OD etc

Tech Memo completed for Initial AOS-Storm Orbit Design

12/15/23 Write a tech memo documenting the analysis performed to determine the AOS-Storm orbit and Force Model used.

Repeating Ground Track Formation Flying Strategy Analysis

12/22/23 Power point of a high-level summary of analysis to date. This should include a summary of the maneuver strategy, the delta-V range for DMUs and any phasing burns if required, approximate maneuver cadence with associated flux levels, and whether these options meet or do not meet the requirements.

Snake Maneuver Formation Flying Strategy Analysis

12/22/23 Power point of a high-level summary of analysis to date. This should include a summary of the maneuver strategy, the delta-V range for DMUs and any phasing burns if required, approximate maneuver cadence with associated flux levels, and whether these options meet or do not meet the requirements.

Preliminary OD Study 1/26/24

1/19/24

Document initial navigation requirements/conops for performing OD

Initial analysis complete for RMM conops

1/26/24 Create a presentation for scenarios considered which describe RMM conops for AOS-Storm. How do RMMs affect the conops for each type of stationkeeping strategy? How much time might the team have if the leader/follower performs an RMM in low/high drag for typical RMM sizes of 1-10cm/s? This analysis would be in the form of a PowerPoint presentation.

Tech Memo completed for AOS- Storm Initial Ascent Planning

2/16/24 Perform preliminary analysis for an AOS-Storm only (no PMM) ascent planning to assist with spacecraft requirements definition prior to the draft RFP deadline.

Tech Memo completed for AOS- Storm Initial Deorbit Planning

2/16/24 Perform preliminary analysis for an AOS-Storm only (no PMM) deorbit planning to assist with spacecraft requirements definition prior to the draft RFP deadline.

Tech Memo completed for snake maneuver analysis as an option for formation flying

3/15/24 Write a tech memo documenting the analysis performed and results of using the snake maneuver in order to maintain formation flying between AOS-Storm and PMM.

Tech Memo completed for a ground track box analysis as an option for formation flying

3/15/24 Write a tech memo documenting the analysis performed and results of using a repeating ground track to maintain formation flying between AOS-Storm and PMM.

Mission SRR Draft Slides

SRR- 30

days

Prepare charts on AOS-Storm orbit, formation flying concept, and anything else the project deems necessary for SRR

Mission SRR Support SRR Present charts for mission SRR

Preliminary orbit design for AOS-Sky

1/31/24

6/7/24

Start looking at the requirements for the polar orbit to develop an initial set of orbital parameters to provide feedback to the spacecraft vendor studies. This should be done in a PowerPoint presentation

Tech Memo for AOS- Storm Ascent Planning

6/30/24 Perform analysis to develop a preliminary ascent plan for both the AOS-Storm and PMM spacecraft.

Mission SRR Cleanup 6/30/24 Provide results of analysis for any questions which come out of SRR as necessary.

VI. 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 government recognizes that the schedule and deliverables in section V are subject to change based on factors outside the government’s control (e.g., international collaborations). As a result, the primary focus for managing this task should be on providing a consistent level of effort with any redirections or changes in deliverables and schedules being tracked via the weekly status reports.

b. Configuration Management

All work product, including documents, presentations, scripts (e.g., GMAT, FreeFlyer) and code will be managed with an appropriate version control system determined in consultation with the TM and will be made available to the government.

c. Facilities

No government facilities are required.

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

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

1. The Government will provide remote access to various pre-existing AOS repositories containing mission context information, records of historical analysis, and any other germane items identified in discussions with the TM.

VII. Travel There is no travel anticipated for this task.

VIII. Work Location

The contractor is expected to perform these analysis activities in their own facility.

IX. Reporting Requirements The contractor shall report status on a weekly basis or as designated by the TM (through meetings and/or email). Reports shall include interim results, status of development activities, current and projected issues, and other action items.

X. Security Requirements This task shall comply with IT security requirements as laid out in the FDSS III contract.

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

Works (2007).

XIII. References None