Request for Information (RFI) For Earth Venture Mission-3 (EVM-3) Multi-mission Access to Space (ATS) Concepts (Launch Services)

September 3, 2019
1.0 INTRODUCTION / SCOPE

This Request for Information (RFI) is in response to the planned NASA Announcement of Opportunity (AO) for the 2019 Earth Venture Mission-3 (EVM-3) Program. NASA's Goddard Space Flight Center (GSFC) is supporting multiple proposal teams (EVM3-M1, -M2 & -M3). GSFC is interested in identifying commercial access to space (ATS) options that enable these mission concepts to meet the orbital requirements necessary to achieve the science objectives.

These three missions are currently in the proposal phase. This phase ends when the proposal is submitted, approximately three months after the EVM-3 AO is released. If the proposal is selected, the EVM-3 mission will proceed to Phase A, per NASA Procedural Requirement (NPR) 7120.5E (available at http://nodis3.gsfc.nasa.gov/main_lib.html). The following schedule should be used as a basis for responses to this request for information:
RFI released September 3, 2019
Responses due September 30, 2019
EVM-3 AO Released September 2019
Proposal submittal in response to 2016 SMEX AO December 2019
Selections Announced (target) Spring 2020
Launch Readiness date NET December 2024
NLT October 2025

The no later than (NLT) date is set by the AO.
If a GSFC EVM-3 proposal is selected, the project will be managed by GSFC. The spacecraft buses (or space vehicle, SV) will be provided by one of the GSFC industry partners (selected in a previous POD). The selected EVM-3 mission will work with NASA's Science Mission Directorate (SMD), the ESSP Program, and LSP to identify and procure the access to space option that best meets the mission's science, technical, and programmatic requirements. The RFI responses will be used in our EVM-3 proposals to NASA/SMD.
As always, this market survey/Request for Information (RFI) does not obligate the US government to a future procurement. The US Government will protect all proprietary information. Distribution will be based on a strict need-to-know basis.

1.1 DESIRED MISSION SERVICES
GSFC is interested in information regarding the feasibility, risks, and cost of non-NASA provided ATS including: pre-launch mission planning, mission design, integration to launch vehicle, post-integration aliveness testing, and launch support for one or more of the three mission concepts: EVM3-M1, EVM3-M2, and EVM3-M3. The ATS options include dedicated commercial launch vehicle(s), a commercial rideshare, or some combination of the two.
All interested parties are requested to respond to this RFI in accordance with Section 4.
 
2.0 EVM-3 MISSION OVERVIEW
EVM-3 missions will be managed under the leadership of a Principal Investigator in collaboration with the mission partners. The missions are planned to be in accordance with a NPR 7120.5 Category 3 mission with Class D spacecraft and payloads (per NPR 8705.4). The rideshare spacecraft follow the USAF Rideshare Users Guide (RUG), are compliant with the USAF Do-No-Harm (DNH) requirements, and are compatible with multiple rideshare and small launch vehicle opportunities.
Potential Mission Mission Description
EVM3-M1 Small Spacecraft Constellation - Low Earth Orbit, Mid-inclination
EVM3-M2 Small Spacecraft Constellation - Sun-synchronous Low Earth Orbit
EVM3-M3 12U CubeSat Constellation - Sun-Synchronous Low Earth Orbit

2.1 EVM3-M1 MISSION OVERVIEW
NASA's GSFC EVM3-M1 mission concept is a constellation of two spacecraft that will operate in mid-latitude (425 km x 425 km) at a desired inclination of 51.8 degrees (+/- 5 degrees). The second spacecraft is in the same orbit plane, but 180 degrees from the first spacecraft (delayed 45 minutes). It will pass over the same location on Earth as the first spacecraft but approximately 12 hours later. Both spacecraft are based on an ESPA Grande-class bus. The two EVM3-M1 spacecraft are released in a nominal nadir-pointing, three axis stabilized orientation. The EVM3-M1 spacecraft has on-board propulsion to raise and lower the spacecraft (as needed) to support the ATS options listed in Table 2.1-1. See Appendix A-1 for the EVM3-M1 mission accommodation details.
To provide launch service flexibility and depending on a potential rideshare provider's unique capabilities, we are allowing vendors to provide multiple access to space (ATS) options (see Table 2.1-1). Describe the pros and cons (and ROM cost) for each option you can support. In addition, provide any additional ATS options we may have overlooked (see Appendix C).

Table 2.1-1: EVM3-M1 Potential Access to Space Option
No. Access to Space Option
O1: 425x425km, 53°, O2: O1 45m delayed L/V #1 L/V #2 RS #1 RS #2 Time Required
1 Two Small L/V:
LV#1 drops off S/C at orbit #1
LV#2 drops off S/C at orbit #2 x x <3 months
2 Two Rideshare Launches:
RS#1 drops S/C-1 off at orbit #1
RS#2 drops S/C-2 off at orbit #2 x x <3 months
3 One Rideshare Launch:
S/C-1 & S/C-2 dropped off at orbit #1
S/C-2 raises/lowers altitude to orbit #2 x <3 months
4 One Medium L/V: (ie. two S/C on one L/V)
LV drops off S/C-1 & S/C-2 at orbit #1
S/C-2 raises/lowers altitude to orbit #2 x <3 months

2.2 EVM3-M2 MISSION OVERVIEW
NASA's GSFC EVM3-M2 mission concept is a constellation of a two spacecraft that will operate in a polar sun-synchronous orbit (705 km x 705 km) at a desired inclination of 98.20 degrees at two separate local times of the descending node (LTDN) of 10:00 and 13:17. The two EVM3-M2 spacecraft are released in a nominal nadir-pointing, three axis stabilized orientation. Each spacecraft is based on an ESPA Grande-class bus. See Appendix A-2 for the EVM3-M2 mission accommodation details.
The EVM3-M2 spacecraft can be deployed with two launch vehicles, but a single launch (rideshare) is a challenge. A single launch vehicle (rideshare) requires a tug (either another spacecraft or a propulsive ESPA) to deploy the second spacecraft. If one of your ATS options requires a tug, describe the technical and programmatic details of the tug (including a ROM cost). You must do the analysis, but we estimate the tug requires 450 m/s delta-V to go from 705km SSO 1000 LTAN to 1317 LTAN, and it takes ~6.6 months. We also estimate that with 1,000 m/s delta-v, it can be done in 3.5 months. Table 2.2-1 lists the ATS options, both with and without a tug.
To provide launch service flexibility and depending on your unique capabilities, we are allowing vendors to provide multiple access to space (ATS) options (see Table 2.2-1). Describe the pros and cons (and ROM cost) for each option you can support. In addition, provide any additional access to space options we may have overlooked (see Appendix C).
Table 2.2-1: EVM3-M2 Potential Access to Space Option
No. 700 SSO, Access to Space Option
(O1: 1000 LTDN, O2: 1317 LTDN) L/V #1 L/V #2 RS #1 RS #2 Tug Time Required
1 Two Small L/V: ~700km SSO
LV#1 drops off S/C-1 at orbit #1
LV#2 drops off S/C-2 at orbit #2 x x <6 months
2 Two Small L/V: ~550km SSO
LV#1 drops off S/C & tug raises orbit #1
LV#2 drops off S/C & tug raises orbit #2 x x x <6 months
3 Two Rideshare Launches: ~700km SSO
RS#1 drops S/C-1 off at orbit #1
RS#2 drops S/C-2 off at orbit #2 x x <6 months
4 Two Rideshare Launches: ~550km SSO
RS#1 drops off S/C & tug raises orbit #1
RS#2 drops off S/C & tug raises orbit #2 x x x <6 months
5 One Rideshare Launch: ~700km SSO
S/C-1 dropped off at orbit #1
S/C-2 dropped off by tug at orbit #2 x x <6 months
6 One Rideshare Launch: ~550km SSO
Tug raises S/C-1 to orbit #1
Tug drops off S/C-2 at orbit #2 x x ~6 months
7 One Medium L/V: ~700km SSO
LV drops off S/C-1 at orbit #1
Tug drops off S/C-2 at orbit #2 x x ~6 months
8 One Medium L/V: ~550km SSO
Tug raises S/C-1 to orbit #1
Tug drops off S/C-2 at orbit #2 x x ~6 months

2.3 EVM3-M3 MISSION OVERVIEW
GSFC's EVM3-M3 mission concept consists of a fifteen (15) 12U-CubeSats (requiring three launches of five spacecraft each) that will operate in a polar sun-synchronous orbit (705 km x 705 km) at a desired inclination of 98.2 degrees at three separate local times of the descending node (LTDN) of 16:00, 10:30 and 18:00. The M3 constellation is required to be in-place in less than four months after the first launch. See Appendix A-3 for EVM3-M3 spacecraft accommodation details.
The EVM3-M3 mission utilizes five (5) spacecraft-provided, Tyvak 12U Dispensers (ref. www.tyvak.com/launchservices Tyvak 12U Dispenser User's Guide for Payloads and Launch Vehicles TK-12UDUG dated March-2018) to deploy spacecraft to the specific orbit plane. The expected mass of the spacecraft and its deployer is 35 kg. Each spacecraft is released in a nominal nadir-pointing, three axis stabilized orientation, and makes use of a standard T-0 gaseous nitrogen purge during ground processing.
To provide launch service flexibility and depending on a potential rideshare provider's unique capabilities, instead of direct insertion into our desired mission orbit, we are allowing the launch service the option to deploy our mission to a lower insertion orbit. Each insertion altitude has a minimum launch mass capability to support the existing mission concept, and a maximum predicted value (MPV) mass that can be used as an upper not-to-exceed limit on the EVM3-M3 launch mass.
Table 3.1-1: Potential Launch Insertion Orbits Under Consideration
(Bold Current Mission Baseline)
Insertion Type Insertion Orbit
(98.20° Inclination) Minimum
Launch Mass
(Dedicated Ride) Maximum
Launch Mass (MPV)
(Ride Share)
Higher Injection
Orbit Insertion ** 825 km x 825 km 180 kg 225 kg
Desired Target Injection Orbit 675 km x 675 km
Lower Injection
Orbit Insertion ** 525 km x 525 km
** Note: While the higher circular injection orbit of 675 km is preferred, M3 could achieve mission orbit from circular orbits as high as 825 km and low as 525 km. Respondents that offer these alternative injection altitudes will be assessed against the impact to the mission lifetime from the higher/lower injection orbit.

Depending on your unique capabilities, we are allowing vendors to provide multiple access to space (ATS) options. Responses may include alternate rideshare insertion orbit options in addition to those detailed above that may or may not be further evaluated in Phase A. Describe your options to deploy the constellation (including ROM costs). Provide any additional access to space options we may have overlooked (see Appendix C).
NOTE: If your proposed solution is to launch all three orbit planes at the same time, with the orbit change being performed by the launch system, present an assessment on how long it will take to establish the desired constellation formation and start to return science. The EVM3-M3 constellation is required to be operational in less than four months after launch. Explain how you will meet this requirement.
2.4 STANDARD SERVICE REQUIREMENTS
2.4.1 EVM3-M1 and EVM3-M2 (RIDESHARE) STANDARD SERVICE REQUIREMENTS
A list of services required by the ESPA Grande-class EVM-3 missions is provided below. It is expected that these missions require no particularly difficult or unusual services; however, identify any services that cannot be provided, or are particularly costly.

a) Mechanical Interface - 24" bolt circle adapter required
b) Electrical Interface - Four 15-pin In-Flight Disconnect (IFD) separation connectors used for Payload operation on the pad, LV-monitored separation breakwire loops, and open/close command to battery relays.
c) Battery charging - Battery trickle charging on the pad.
d) LV Purge - GN2 Purge on pad
e) Power to S/C after Integrated Payload Stack (IPS) Integration - Power on pad. Launch unpowered.
f) Payload access on LV - No access is required for the Payload after integration to the LV.
g) Separation System - Separation system provided by the Payload provider, standard 24 inch light-band.
h) Telemetry - Telemetry to support powered operation and LV separation confirmation.
i) Command - LV to provide battery relay open and close commands. LV provides two separate commands to deploy each spacecraft.
j) S/C to LV Integration - Payload requests to accomplish integration of Payload or to be present during integration.

2.4.2 EVM3-M3 STANDARD SERVICE REQUIREMENTS
A list of services required by the EVM3-M3 mission is provided below. It is expected that these missions require no particularly difficult or unusual services; however, identify any services that cannot be provided, or are particularly costly.

a) Mechanical Interface - 5 Separate Tyvak 12U Deployer *
b) Electrical Interface - 5 Separate Tyvak 12U Deployers.*
c) Battery charging - Battery trickle charging on the pad.
d) LV Purge - GN2 Purge on pad
e) Power to S/C after Integrated Payload Stack (IPS) Integration - Power on pad. Launch unpowered.
f) Payload access on LV - No access is required for the Payload after LV integration.
g) Separation System - Standard Tyvak 12U deployer.
h) Telemetry - Telemetry to support powered operation and LV separation confirmation.
i) Command - LV provides two separate commands to deploy each spacecraft.
j) S/C to LV Integration - Payload requests to accomplish integration of Payload or to be present during integration.

* (ref. www.tyvak.com/launchservices Tyvak 12U Dispenser User's Guide for Payloads and Launch Vehicles TK-12UDUG dated March-2018)

2.5 LAUNCH VEHICLE

Describe your low-risk ATS approach(s). Provide the historic (if available) and predicted ROM cost for each ATS approach. Describe the launch and related launch services. The respondent should show heritage and previous launch experience for the ATS option suggested. If the launch vehicle has not been certified by NASA, describe your plans for certification.

Provide the integration flow and launch environmental test levels (e.g. launch loads and acoustic levels). Provided the ICDs or users guides that describe the mechanical, electrical, and thermal interfaces between the ATS method and the spacecraft. The launch vehicle proposed shall be consistent with the AO requirements.

2.6 LAUNCH MANIFEST

The RFI response must include a letter of support for each EVM-3 mission supported. The letter must confirm you can manifest the mission commensurate with the requirements included in this RFI for the spacecraft access to space requirements (see Appendix B for a sample letter). The EVM-3 AO will define the launch requirements, but we assume the EVM-3 missions will be required to be launched no later than (NLT) October 2025. The vendor should also include separately costs associated with month-to-month delays in a launch date for up to 9 months, if a rideshare with another Primary payload is proposed.

 
3.0 EVM AO REQUIREMENT

3.1 GENERAL
The access-to-space (ATS) offered shall be compatible and appropriate for the mission described in EVM-3 AO Rideshare requirements. The EVM-3 missions will be in accordance with NPR 7120.5 Category 3 mission and with NPR 8705.4 Class D spacecraft and payloads.

The following text reflects the requirements that each of EVM proposal must address (provided for your information). NASA's Science Mission Directorate (SMD) released these ATS guidelines for the EVM-2 AO and we expect similar requirements for the EVM-3 AO, although, there could be changes once the EVM-3 AO is released. The details of the RFI response are captured in Section 4.0 and Appendix C.

3.2 ATS REQUIREMENTS FROM THE EVM-2 AO (for your reference information)
Although NASA-provided launch services continue to be offered, alternative access to space, rather than the use of NASA-provided launch services, may be proposed or considered under this AO. Alternative access to space may include the provision of non-NASA launch services as primary, secondary, or co-manifested payloads on a U.S. or foreign-manufactured launch vehicle. Under this AO, purchased launch services must be obtained on a U.S.-manufactured launch vehicle only.

The National Space Transportation Policy (Section IV) prescribes the use of U.S.-manufactured launch vehicles for the launch of U.S. Government sponsored payloads. Proposed alternative access to space must be consistent with the National Space Transportation Policy and with any policies or requirements specified in this AO. National Space Transportation Policy URL: https://obamawhitehouse.archives.gov/sites/default/files/microsites/ostp/national_space_transportation_policy_11212013.pdf

For proposals submitted in response to this AO, NASA will accept a Launch Vehicle Risk
Category 1 (per NPD 8610.7D, NASA Launch Services Risk Mitigation Policy for NASA-Owned and/or NASA Sponsored Payloads/Missions) for non-NASA provided access to space. Non-NASA launch services and hosted payloads will be handled by NASA consistent with existing policy and regulations. The demonstrated reliability and the resultant probability of mission success for non-NASA launch services and hosted payloads will be evaluated by NASA consistent with National Space Transportation Policy (National Space Transportation Policy, Section IV) and NASA's Launch Services Risk Mitigation Policy (NPD 8610.7D, NASA Launch
Services Risk Mitigation Policy for NASA-Owned and/or NASA-Sponsored Payloads/Missions).
The proposed launch service will be assessed in conjunction with NASA stakeholders as part of the selection process. The functions, operating structure, and policies of the NASA Launch Services Program (LSP) with regards to defining and executing advisory services or consulting for Government or commercial entities are defined in the Launch Services Program (LSP) Advisory Services Plan that can be found in the Program Library. The NASA Flight Planning Board will approve final mission assignments, assuring consistency with Agency risk strategy. Information on the reliability of ELVs may be obtained from the point of contact listed in the AO ELV Launch Services Program Information Summary document.

Alternative access to space options involves several complex issues at this stage of project maturity. It is in the proposer's best interest to clearly support the maturity of their plan and access to space possibilities. The minimum expectations for access to space arrangements must be included in the proposal to the level of detail outlined in Requirement 90 (iv). Any additional evidence of maturity or commitment provided will be used to support risk posture.

Requirement 90. Proposals that include non-NASA launch services (purchased or contributed) obtained from a U.S. or non-U.S. partner shall meet the following requirements:
i. The proposer must demonstrate a commitment from the organization(s) that will provide the launch services.
ii. The proposer must demonstrate a commitment from the launch services provider when flying as a primary.
iii. The proposer must demonstrate a commitment for the proposed co-manifested mission organization(s) or, when flying as a secondary, of the primary mission organization(s) utilizing the launch services; these commitments must be documented in a Letter from the appropriate organization(s).
iv. The proposal must identify the launch opportunity and must provide evidence in the proposal that the launch service provider agrees to manifest the mission should the proposal be selected and confirmed for flight by NASA. This evidence must include a Letter from the launch service provider containing, at a minimum, the following information:
a. Evidence that the launch service provider will provide the services described in the proposal under the conditions (cost, schedule) described in the proposal;
b. A description of the opportunity (or opportunities, if more than one under consideration) that the launch service provider can offer for consideration by the PI; and
c. A description of the process that the launch service provider will use in order to commit to the PI to provide specific launch services for the proposed investigation, should NASA select the proposed investigation; this process description must include a notional schedule for identifying the specific launch opportunity and definitizing the cost.
v. The proposal must describe the launch services, demonstrate compatibility with the proposed launch vehicle, and show how the provider will fulfill the mission requirements.
vi. The proposal must describe the approach for the proposer and for the launch service provider to work with NASA to enable NASA's insight for launch services, and the proposal budget must include a $2.0M charge for NASA launch vehicle monitoring functions and advisory services. [an RFI response not required to this item] 
4.0 RFI RESPONSE INSTRUCTIONS, FORMAT, AND SELECTION CRITERIA

4.1 INSTRUCTIONS
Provide separate responses for each mission - EVM3-M1, EVM3-M2, and EVM3-M3. Different mission teams will review each response. Provide duplicate material so that each response is stand-alone.
The RFI response has three sections: 1) a letter of support; 2) supporting material; and 3) backup material (ICDs, Users Guide, etc.). We understand the RFI is asking for a lot of information. The draft letter of support is required. We'll work with you on the final version for our proposals. The supporting material section includes question we'll need address in our proposal. This is a market survey, so respond to the applicable questions and provide a summary level of detail. We'll contact you if we have specific questions on your response. You may provide the same supporting material section for all three RFI responses.
4.2 FORMAT
The document(s) shall be formatted as a Portable Document Format (PDF) file delivered to the E-mail address in section 5.0. Appendix C includes a suggest format for the RFI response.

5.0 POINT OF CONTACT:

Questions about this RFI should be directed to Robert Caffrey (Email: [email protected], Phone: 301-286-0846).

6.0 FINAL DUE DATE OF RFI RESPONSE

The response to the RFI is due no later than 5 p.m. ET on September 30, 2019. The electronic PDF document shall be sent to Robert Caffrey (Email: [email protected]).
It is the responsibility of potential respondents to monitor the FBO.gov for further information concerning this RFI:
http://fbo.gov

7.0 WHAT'S NEXT?
Based on your RFI response, we may ask that you to present your RFI response to our team (either in-person or via telecom). We will contact you with the details of the presentation.

 
8.0 ACRONYMS
AO Announcement of Opportunity
ATS Access To Space
CBE Current Best Estimate
CSR Concept Study Report
DC Direct Current
DNH Do No Harm
ELV Expendable Launch Vehicle
FY Fiscal Year
GSFC Goddard Space Flight Center
HPL Hosted Payload
I & T Integration & Test
ICD Interface Control Document
LTDN Local Times of the Descending Node
LV Launch Vehicle
MLI Multi-Layer Insulation
MPV Maximum Predicated Value
NASA National Aeronautics and Space Administration
NLT No Later Than
NPD NASA Procedural Document
NPR NASA Procedural Requirement
NTE Not To Exceed
PDF Portable Document Format
PI Principal Investigator
PDF Portable Document Format
POC Point of Contact
POD Partnership Opportunity Document
ROM Rough Order of Magnitude
RS Rideshare
RPL Rideshare Payload
RUG Rideshare Users Guide
RY Real Year
SAA South Atlantic Anomaly
S/C Spacecraft
SMEX-2 Small Explorer #2
SOW Statement of Work
SV Space Vehicle
TBD To Be Determined
U.S.A. United States of America

 
Appendix A-1: EVM3-M1 ATS Payload Request Form
Number Item Value Comment
1 Mission (S/C or HPL) EVM3-M1 (S/C) ESPA Grande bus
2 Mass to Orbit (kg) 422 kg (total) 2 S/C @ 211 kg ea = 422 kg
3 Orbit
(LEO, SSO, GEO, etc.) LEO
4 Apogee x Perigee (km) 425 x 425 400 to 450 km
5 Apogee Accuracy (+/-) 10
6 Perigee Accuracy (+/-) 10
7 Inclination (Deg) 53
8 Inc Accuracy (+/- Deg) 5
9 Argument of Perigee 0
10 AOP Accuracy (+/- Deg) ---
11 RAAN (Deg) ---
12 RAAN Accuracy (+/- Deg) ---
13 S/C Dimensions 42 in x 46 in x 56 in. ESPA Grande
14 S/C Disposition controlled re-entry
15 Launch Compatibility ESPA Grande, Pegasus - XL, RovketLab
16 Quantity/ Frequency 2 S/C
17 I&T Funding Source NASA Mission
18 Desired Launch Date 12/2024
19 Earliest / Latest Availability 12/1/2024 earliest
6/1/2025 latest
20 Special Requirements May use a tug (propulsive ESPA, etc.)
21 Handling Requirements ISO 14644-1 Class 8 (Class 100,000) cleanroom environment

 
Appendix A-2: EVM3-M2 ATS Payload Request Form
Number Item Value Comment
1 Mission (S/C or HPL) EVM3-M2 S/C ESPA Grande bus
2 Mass to Orbit 374 kg 2 S/C, 187 kg each
3 Orbit LEO, Circular
4 Apogee x Perigee (km) 705 x 705
5 Apogee Accuracy (+/-) 5km
6 Perigee Accuracy (+/-) 5km
7 Inclination (Deg) 98.2 Sun sync
8 Inc Accuracy (+/ - Deg)
9 Argument of Perigee
10 AOP Accuracy (+/ - Deg)
11 LTAN 1000 and 1317orbit crossing time
12 LTAN Accuracy (+/- Deg)
13 S/C Dimensions 71 x 68 x 94 cm
14 S/C Disposition S/C lowers perigee at end of mission for passive reentry
15 Launch Compatibility ESPA or Venture Class
16 Quantity/ Frequency 2 spacecraft Launched together or within 6 months of each other
17 I&T Funding Source NASA
18 Desired Launch Date 12/1/2024
19 Earliest/ Latest Availability 12/1/2024 earliest
6/1/2025 latest
20 Special Requirements May use a tug (propulsive ESPA, etc.)
21 Handling Requirements

 
Appendix A-3: EVM3-M3 ATS Payload Request Form
Number Item Value Comment
1 Mission (S/C or HPL) EVM3-M3 12U S/C 5 12U Cubesats per Orbit Plane
2 Mass to Orbit (kg) ~170-190 kg 5 x 25 kg (12U Cubesats )
5 x 7 kg (12U Dispensers)
10-30 kg (Support Structure / Misc)
3 Orbit
(LEO, SSO, GEO, etc.) LEO 705 km SSO Mission Orbit
4 Apogee x Perigee (km) 675 km x 675 km
525 km x 525 km Desired Insertion Orbit
Lowest L/V Insertion Orbit
5 Apogee Accuracy (+/-) 10 km Standard Accuracy
6 Perigee Accuracy (+/-) 10 km Standard Accuracy
7 Inclination (Deg) 98.21 (SSO at 705 km)
8 Inc Accuracy (+/- Deg) 0.1 deg Standard Accuracy
9 Argument of Perigee n/a
10 AOP Accuracy (+/- Deg) n/a
11 LTAN (Deg) C#1: 16:00
C#2: 10:30
C#3: 18:00 3 Orbit Planes: 5 S/C per plane
12 LTAN Accuracy (+/- Deg) +/- 15 minutes
13 S/C Dimensions 12U 20 cm x 20 cm x 30 cm (12U)
Plus dispensers/support structure
14 S/C Disposition Pre-Phase A
15 Launch Compatibility Need 5 12U Dispensers
16 Quantity/ Frequency 3 Separate Launches
45-60 day centers
17 I&T Funding Source NASA GSFC
18 Desired Launch Date Vendor Specified
NLT June 30, 2025
19 Earliest/ Latest Availability Vendor Specified
NLT November, 2024 Critical Path is Instrument - Working Development Schedule
20 Special Requirements None
21 Handling Requirements None
22 Mission Owner NASA GSFC

 
Appendix B: Sample Vendor Letter of Support (modify as required)

Date: TBD
<M1 PI Name>
NASA/GSFC/610
8800 Greenbelt Road
Greenbelt, MD 20771

SUBJECT: Letter of Support for the EVM-3 Mission

Dear Dr. <PI Name>,

TBD Vendor is pleased to support EVM3-Mn Mission as a candidate for NASA's Science Mission Directorate (SMD) Earth Venture Mission (EVM).

TBD Vendor has experience launching and deploying small spacecraft such as XXX mission. This includes mission planning and analysis, manifesting payloads, payload integration, and deployment/separation system management. If EVM3-Mn is selected, TBD Vendor will provide the launch services, including providing reasonable cooperation to enable NASA's required insight under the NASA Launch Services Program. We will meet the EVM3nn requirements:

• Launch December 2024 to October 2025
• EVM3-Mn consists of ESPA-Grande/12U-CubeSat class spacecraft
• The required orbit is LEO, TBD km altitude, and inclination of TBD
• EVM3nn requires no non-standard services

We are proposing to manifest EVM3-Mn on mission YYY, launching in 2024/2025. The backup opportunity is mission ZZZ, launching in 2024/2025. The ROM cost of the EVM3-Mn launch services is $TBD.

We look forward to partnering with GSFC.

Sincerely,

TBD Vendor

 
Appendix C: EVM3 ATS RFI Response Format:
Each RFI response will have three sections: 1) letter of support; 2) supporting material; and 3) backup material (ICDs, Users Guide, etc). Provide a separate response for each EVM-3 mission.
1. Letter of Support - provide a draft letter of support, addressing the elements in Requirement 90 items i, ii, and iii (a sample letter is in Appendix B). We'll work with you to finalize the letter so it can be included in our EVM-3 proposals.
i. Rideshare provider - demonstrate a commitment to provide the rideshare / launch services for the EVM3 payloads.
ii. Launch services provider - demonstrate a commitment to flying the EVM3 payloads as a primary (in order to meet orbit and launch date requirements).
iii. Secondary/co-manifested mission provider - demonstrate a commitment from the lead organization(s) utilizing the launch services; these commitments must be documented in a Letter from the appropriate organization(s)
The letter of support will include the following information:
a. Evidence that the rideshare/launch service provider will provide the services described in this RFI, including a ROM cost and launch dates;
b. Describe of the opportunity (or opportunities, if more than one under consideration) that the rideshare/launch service provider is offering; and
c. Describe the process to commit to the PI to provide specific services for the proposed investigation; this process description must include a notional schedule for identifying the specific rideshare/launch opportunity and definitizing the cost.

2. Supporting Material - In your response, briefly describe the following:
1) Previous experience - describe your experience that is similar to the missions in the RFI.
2) Cost ROM - provide a cost ROM for all the activities including mission design, integration and testing, and launch services. Separately, provide the costs associated with month-to-month delays in a launch for up to 9 months, if the rideshare is with a primary payload.
3) Launch and/or rideshare approach - describe your approach, including 1) schedule (with key milestones defined); 2) documentation requirements; 3) analysis requirements; 4) hardware requirements; 5) testing requirements; 6) integration requirements; 7) safety & mission assurance requirements; 8) budget phasing requirements; 9) procurement approach (existing contracts, GSA, new RFP, etc.), and any other additional details.
4) Technical maturity/qualification - identify maturity/qualification of the proposed ATS opportunity. If the launch opportunity approach has not already been certified by NASA, the respondent should describe how these items will be demonstrated, including a timeline for this demonstration, before it is required for this mission.
5) Rideshare/Launch Opportunities - summarize the opportunities between 2020 - 2026
6) NASA's insight for launch services - if a launch service is being provided, describe your approach to support NASA launch vehicle monitoring functions and advisory services.
7) ATS Tables - Complete tables C-1, C-2, and C3 for missions M1, M2, and M3.

3. Backup Material - In your response, include ICDs, Users Guides, etc. (no page limit)
Table C-1: EVM3-M1 Potential ATS Option: 2 ESPA Grande S/C
No. ATS Option
O1: 425x425km, 51.8°, O2: O1 45m delayed L/V #1 L/V #2 RS #1 RS #2 Time Required ROM Cost
Pros and Cons of ATS Options
1 Two Small L/V:
LV#1 drops off S/C at orbit #1
LV#2 drops off S/C at orbit #2 x x <3 months
2 Two Rideshare Launches:
RS#1 drops S/C-1 off at orbit #1
RS#2 drops S/C-2 off at orbit #2 x x <3 months
3 One Rideshare Launch:
S/C-1 & S/C-2 dropped off at orbit #1
S/C-2 raises/lowers altitude to orbit #2 x <3 months
4 One Medium L/V: (ie. two S/C on L/V)
LV drops off S/C-1 & S/C-2 at orbit #1
S/C-2 raises/lowers altitude to orbit #2 x <3 months
5

 
Table C-2: EVM3-M2 Potential ATS Option: 2 ESPA Grande S/C
No. 700 SSO, ATS Option
(O1: 1000 LTDN, O2: 1317 LTDN) L/V #1 L/V #2 RS #1 RS #2 Tug Time Required ROM
Cost
Pros and Cons of ATS Options
1 Two Small L/V: ~700km SSO
LV#1 drops off S/C-1 at orbit #1
LV#2 drops off S/C-2 at orbit #2 x x <6 months
2 Two Small L/V: ~550km SSO
LV#1 drops off S/C & tug raises orbit #1
LV#2 drops off S/C & tug raises orbit #2 x x x <6 months
3 Two Rideshare Launches: ~700km SSO
RS#1 drops S/C-1 off at orbit #1
RS#2 drops S/C-2 off at orbit #2 x x <6 months
4 Two Rideshare Launches: ~550km SSO
RS#1 drops off S/C & tug raises orbit #1
RS#2 drops off S/C & tug raises orbit #2 x x x <6 months
5 One Rideshare Launch: ~700km SSO
S/C-1 dropped off at orbit #1
S/C-2 dropped off by tug at orbit #2 x x <6 months
6 One Rideshare Launch: ~550km SSO
Tug raises S/C-1 to orbit #1
Tug drops off S/C-2 at orbit #2 x x ~6 months
7 One Medium L/V: ~700km SSO
LV drops off S/C-1 at orbit #1
Tug drops off S/C-2 at orbit #2 x x ~6 months
8 One Medium L/V: ~550km SSO
Tug raises S/C-1 to orbit #1
Tug drops off S/C-2 at orbit #2 x x ~6 months
9

Table C-3: EVM3-M3 Potential ATS Option: 3 Orbit Planes: 5 S/C per plane, 35kg per 12U w/Dispenser
No. 705 km SSO, ATS Option
(O1-3: 10:30, 16:00, & 18:00, LTDN) L/V #1 L/V #2 L/V #3 RS #1 RS #2 RS #3 Tug Time Required ROM
Cost
Pros and Cons of ATS Options
1 Three Small L/V: x x x <4 months
2 Three Rideshare Launches: x x <4 months
3
4