2017_11_16_MAIA_Hosting_Strategy_Synopsis.pdf

This is a modification to synopsis MAIAHPS2017 entitled “Multi-Angle Imager for Aerosols (MAIA) Hosted Payload Services” which was posted on July 31, 2017 (Attached for reference ONLY). The purpose of this notice is to provide potential Offerors updated information regarding the procurement strategy and identify/revise key upcoming milestones.

THIS INFORMATION IS FOR PLANNING PURPOSES ONLY AND IS SUBJECT TO CHANGE.

The following is a summary of key procurement strategy elements:

a. The title for the procurement has been renamed to “Multi-Angle Imager for Aerosols (MAIA) Hosting

Services” (vice “hosted services”) to clarify that there is no assumption or requirement that the MAIA Instrument be a dedicated (single) spacecraft payload or one of several spacecraft payloads. Rather, the Government will consider a variety of Offeror-proposed solutions for hosting services. NOTE: The original synopsis number and title, noted above, will no longer be utilized for any future postings. All future postings will be contained under number 80LARC18R0004 with this renamed title.

b. The scope includes the procurement of services for hosting the MAIA Instrument including: Integration Planning; Contractor Ground System Design, Integration, Testing, and Readiness; MAIA Instrument- Spacecraft Integration, Test, and Pre-Launch Processing; Spacecraft and launch vehicle; Launch and MAIA In-orbit Checkout; On-Orbit Spacecraft Operations to enable Instrument Operations, including Extended Operations (if any, options); and Support to MAIA Instrument End-of-Life Operations and Decommissioning.

c. The procurement will be conducted as a full and open competition under NAICS code 541715, Research and Development in the Physical, Engineering, and Life Sciences (Except Nanotechnology and Biotechnology), 1,000 employee size standard, and as a commercial service utilizing Federal Acquisition Regulation (FAR) Part 12 terms and conditions.

d. The potential period of performance (POP) will be ~9 years, consisting of a ~6-year base period and three, 1-year options. The exact POP will be dependent on Offeror solutions; however the preferred launch date is no later than June 2022 based on a planned MAIA Instrument delivery of December 2019 to June 2020.

Operations are planned for 3 years following launch and the 90 calendar day In-orbit checkout period.

Option periods will be utilized for any extended mission operations.

e. The contract will be Firm-Fixed-Price (FFP) with milestone payments.

f. The following are ESTIMATED key milestone dates (NOTE: These are estimated dates only and may change at any time. Any changes will be posted to www.fbo.gov.):

Milestone Date

Draft RFP Issuance January 2018 Pre-solicitation Conference February 2018 Industry Comments Due March 2018 RFP Issuance March 2018 Proposals Due April 2018 Award October 2018

No solicitation is currently available; therefore, do not request a copy of the solicitation. If a solicitation is released it will be synopsized in FedBizOpps. It is the potential Offeror’s responsibility to monitor this site for the release of any solicitation or synopsis.

Please check FedBizOpps regularly for updates. We look forward to your comments and feedback. If you have questions or comments, please contact Karen Dempster (Karen.C.Dempster@nasa.gov) with a copy to Michael Kaszyca (Michael.Kaszyca@nasa.gov).

http://www.fbo.gov/ mailto:Karen.C.Dempster@nasa.gov mailto:Michael.Kaszyca@nasa.gov

Request for Information and Sources Sought Notice Multi-Angle Imager for Aerosols (MAIA) Hosted Payload Services

The National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) is hereby soliciting information regarding potential sources for a new procurement for MAIA Hosted Payload Services. NASA LaRC is also seeking industry input regarding potential procurement strategies.

I. Background

As part of the Earth Venture Program managed by the Earth System Science Pathfinder Program Office (ESSPPO) located at NASA LaRC, NASA’s Earth Science Division (ESD) is developing Earth Science Instruments to be flown as hosted payloads.

MAIA is a selected payload as part of the Earth Venture Instrument-3 (EVI-3) program and is a cost-capped mission. The hosted payload services are outside the scope of the cost-capped instrument development; thus the hosted payload procurement is being conducted separately. The MAIA investigation aims to benefit society by assessing linkages between different types of particulate matter and adverse human health outcomes, including cardiovascular and respiratory disease, low birth weights, and premature deaths. Breathing particulate air pollution is a well-known cause of many health problems, but the toxicity of specific particle sizes and compositions is less understood. To improve our understanding, MAIA will derive the concentrations of fine, coarse, sulfate, nitrate, organic carbon, black carbon, and mineral dust particles on a 1-km grid in selected major urban areas around the world.

The MAIA instrument contains two pushbroom spectropolarimetric cameras on a two-axis gimbal.

Rotation of the gimbal in the along-track (scan) direction provides multi-angle viewing of Earth targets, either in a “step-and-stare” observing mode in which the gimbal steps to a set of discrete view angles and acquires science data after settling at each angle, or in a “sweep” mode as the gimbal rotates continuously over the along-track field of regard. Rotation of the gimbal in the cross-track (pan) direction enables access to Earth targets that are not directly on the spacecraft ground track, and is also used during observations of the instrument’s solar-illuminated on-board calibrator.

The MAIA instrument contains 14 spectral bands in the ultraviolet (UV), visible/near-infrared (VNIR), and shortwave infrared (SWIR), and the spectral bandpasses encompass the range from 340 nm to 2190

nm. To limit the impact of detector dark current, the camera focal planes are passively cooled to a nominal temperature of 225K, requiring a cold space view on the spacecraft anti-sun side to radiate heat.

A nadir-viewing radiator is also included to dissipate heat from the instrument’s electronics subsystems.

The MAIA instrument does not collect data continuously; rather it collects data during approximately 10% of each spacecraft orbit. The remainder of the orbit period is used for on-board data processing and buffering of instrument data to the host spacecraft.

MAIA will operate in Low Earth Orbit (LEO) and is a Category 3 mission (per NPR 7120.5E, NASA Space Flight Program and Project Management Requirements) with a Class C payload (per NPR 8705.4, Risk Classification for NASA Payloads). NOTE: The export control classification for the MAIA instrument has not yet been determined. Documents pertaining to the MAIA shortwave infrared focal plane detector assembly and associated Read-Out Integrated Circuit (ROIC), other than general systems description and basic marketing information on function and purpose, are controlled under the International Traffic in Arms Regulations (ITAR), 22CFR 120-130. All other technical data about the MAIA instrument is controlled under the Export Administration Regulations with an ECCN of 9E515.

Attachment (REFERENCE ONLY)

The MAIA instrument collects data using multi-angle views as shown in Figure 1. The along-track scan gimbal provides step-and-stare multi-angle imagery. The cross-track pan gimbal provides access to targets off the sub-satellite track.

Figure 1. Example MAIA Step-and-Stare Sequence

In the figures below, the MAIA instrument configuration is shown for a spacecraft in a sun synchronous ascending orbit with equator crossing time occurring in the morning. Figure 2 shows an overview of the MAIA instrument and defines directions and sides for this configuration.

Figure 2. Conceptual Configuration of the MAIA Instrument

The stowed dimensions of the MAIA instrument are 0.7 m in length in the along-track direction, 0.9 m in width in the cross-track direction, and 0.5 m in height in the direction from the spacecraft/MAIA interface plane toward nadir. When deployed, the instrument height increases to 0.55 m.

Keep Out Zones are shown in Figure 3. The Camera field-of regard Keep Out Zone (KOZ) for science observations is described further in Table 2, L2-H1.

Nadir direction

Anti-sun side

Sun side

Trailing side

Trailing side

Nadir direction

Sun side

Other KOZs are for calibration and heat rejection. The On-Board Calibration (OBC) target (shown on the trailing side in Figure 3) must have an unobstructed sun view for at least three minutes as the spacecraft passes over the orbit’s highest latitudes, as described further in Table 2, L2-H12. The trailing face is the preferred location of the OBC, but depending on the equator-crossing time, ascending or descending node availability, and other potential accommodation constraints, the OBC may be located on the leading face if necessary.

The anti-sun facing radiator shown in Figure 3 must have an unobstructed (2π steradians) view of cold space for the entire duration of each orbit.

Figure 3. MAIA Keep-Out Zones

The major planned MAIA mission milestones are as follows:

Table 1. MAIA Mission Milestones

Activity Date System Requirements Review and Instrument Definition Review (SRR/IDR) March 2017 (Complete)

Preliminary Design Review (PDR) January 2018 Critical Design Review (CDR) September 2018

Instrument Delivery Planned: December 2019 NLT: June 2020

Launch Earliest: June 2020

NLT: TBD

II. Hosted Payload Procurement Requirements and Schedule

The general scope for the MAIA Hosted Payload procurement includes the host spacecraft, integration and test, access to space (launch vehicle and launch), command uplink from the host Mission Operations Center, downlink of MAIA engineering and science data to the host Ground Data System, delivery of

Flight direction

Along-track direction

±65°

Nadir direction

±50°

Camera Field-of-Regard Keep

Out Zone Nadir direction

Cross-track directionAnti-sun side radiator

Anti-sun side

Trailing side

OBC

OBC

Spacecraft interface error-checked MAIA data to the MAIA Ground System (consisting of the Instrument Operations Center and Science Operations Center at JPL and the Atmospheric Science Data Center (ASDC) at NASA LaRC), and all related tasks and support needed for the successful hosting of the MAIA Instrument during its planned mission (e.g., pre-launch planning, launch support, in-orbit check-out and operations).

The current MAIA mission and resource requirements are as follows:

Table 2. MAIA Mission and Resource Requirements

MAIA

Req. ID Description Requirement

L2-H10 Mission Duration 36-month baseline mission following MAIA In-Orbit Checkout

L1- M3 MAIA In-Orbit Checkout Period 90 days

L2-H17 Orbit Altitude (acceptable range)

Orbit semi-major axis between 6978 km and 7228 km, i.e., between 600 km and 850 km above the Earth equatorial radius of 6378 km. There is enhanced science value for orbit altitudes towards the higher end of this range.

L2-H15 Orbit Inclination Sun synchronous. Ascending node on the orbit dayside is preferred, but descending node on the orbit dayside is acceptable.

L2-H15 Sun-Sync Equatorial Crossing Time

Mean Local Time (MLT) of dayside equator crossing between 9:00 am and 3:00 pm, excluding 11:30 am -12:30

pm. Preferred MLT is between 10:30 am and 11:30 am or between 12:30 pm and 1:30 pm. Note: Slow drift in MLT (up to 1 hour over mission life) is acceptable, as long as MLT remains earlier than 11:30 am or later than 12:30 pm throughout the mission.

L2-H5 Satellite Stabilization 3-axis stabilized

L2-H6 Pointing Control during MAIA observations 0.1 degrees (360 arcsec) (3σ)

L2-H7 Pointing Knowledge during MAIA observations 0.06 degrees (216 arcsec) (3σ)

L2-H8 Pointing Jitter during MAIA observations

10 arcsec (3σ) over 0.5 s, 100 arcsec (3σ) over 30 s

D-98479 Launch Environment Compatible with Intermediate Class Launch Vehicle loads and environments to LEO

L2-H20 MAIA Instrument Mass (maximum expected value, MEV) 80 kg

L2-H21 Dimensions (l x w x h) 0.7 m (along-track) x 0.9 m (cross-track) x 0.5 m (height)

L2-H21 Footprint on Spacecraft/MAIA Interface Plane (nadir-facing) 0.7 m (along-track) x 0.9 m (cross-track)

L2-H13 Orbit Average Power (MEV) during operations 85 W

L2-H14 Peak Power (MEV) during operations 100 W RFI-1 Survival Power (non-operating) 50 W worst case L2-H3 Orbit Average Data Rate (MEV) 10 Mbps RFI-2 Peak Data Rate (MEV) 100 Mbps RFI-3 Science Data Interface SpaceWire

RFI-4 Command and Telemetry Data Interface SpaceWire or 1553B

L2-H2 L2-H29 Commands and Files

Uplinks to be supported on a daily basis during nominal operations and up to 3x daily during MAIA In-Orbit Checkout.

L2-H4 Time Stamp Provide MAIA instrument with a monotonically increasing spacecraft time, updated every 1 sec ± 1 msec.

L2-H1 Camera Keep Out Zone ±65 degrees along-track ±50 degrees cross-track as shown in Figure 3

RFI-5

Thermal Flux requirements from host spacecraft and non-MAIA hosted payload surfaces

Nadir surface: incident radiative heat flux ≤0.1 W/m2 orbit average and ≤0.13 W/m2 peak

Anti-sun side surface: incident radiative heat flux ≤0.1 W/m2 orbit average and ≤0.13 W/m2 peak

Sun-side surface: incident radiative heat flux ≤38.1 W/m2 orbit average and ≤49.5 W/m2 peak

L2-H23 Unique Constraints Placed on Host Disturbance torques of up to 0.3 N-m will occur during MAIA operations.

L2-H12 Illumination of On-Board Calibrator

(OBC)

Provide unobstructed solar illumination of the onboard calibrator side of MAIA for at least three minutes every orbit when the spacecraft is near its highest orbit latitude with the sun illuminating that surface.

L2-H26 Field-of-Regard (FOR) Free of specular reflections

Provide the MAIA Instrument with a FOR that is free of specular reflections from spacecraft and neighboring payload structures.

L2-H27 Thruster Plume Impingement Provide the MAIA Instrument Operations Center with at least 72 hours advance notice of planned thruster operations and spacecraft maneuvers.

L2-H22 On-board Fault Response Execute pre-defined autonomous anomaly responses to command MAIA into a safe configuration in response to pre-defined on-board faults.

RFI-6 Ground-based Fault Response Execute pre-defined anomaly responses in response to pre-defined faults indicated in MAIA real-time engineering telemetry monitored by the Host.

L2-H25 Temp Sensors to Flight Systems

Relay data from up to six MAIA temperature sensors reporting directly to the flight system to the MAIA Instrument Operations Center.

L2-H32 Notification of Anomalies Notify the MAIA Project in less than an hour of any anomaly that compromises nominal operations of either the spacecraft or the MAIA instrument.

L2-H35 System Current Reporting Report the MAIA instrument current draw at a sampling rate of 1 Hz or 100 Hz (TBC), selectable by command.

L2-H24 Real-Time Data Relay real-time engineering telemetry to the MAIA Instrument Operations Center during spacecraft downlink or real-time passes.

L2-H28 Deliver Data Packets Deliver ≥ 98% of MAIA data packets delivered to the spacecraft to the MAIA Ground System in accordance with the Flight to Ground System ICD.

L2-H30 Deliver Received Data Within Two Days

Deliver all MAIA data to the MAIA Ground System within two days of receipt by the spacecraft during nominal operations and within 12 hours during MAIA In-Orbit Checkout.

L2-H31 Weekly Update to Orbit and Ephemeris

Deliver a weekly update of predicted spacecraft orbit, ephemeris information and operations plans covering at least four weeks to the MAIA Instrument Operations Center.

L2-H33 Time History of Spacecraft Attitude Provide a time history of spacecraft attitude to the MAIA Ground System with latency less than or equal to science data delivery latency.

The TENTATIVE procurement schedule is as follows:

Milestone Date Draft RFP Issuance November 2017 Pre-solicitation Conference (if held) December 2017 RFP Issuance February 2018 Proposals Due March 2018 Award August 2018

III. Capability Statements

One of the primary goals of this synopsis is to assist LaRC in determining whether a Small Business Set-aside is a suitable strategy for this procurement. If a full and open competition is ultimately pursued, responses to this synopsis will be used to aid in establishing small business subcontracting goals. Since no decision regarding a set-aside has yet been made, all qualified firms are encouraged to respond.

The anticipated North American Industry Classification System (NAICS) Code for this procurement is anticipated to be 541712, Research and Development in the Physical, Engineering, and Life Sciences (Except Biotechnology), and the size standard under this code is 1,000 employees.

NASA LaRC is seeking capability statements from all interested parties, including Small, Small Disadvantaged (SDB), SBA Certified 8(a), Woman-owned (WOSB), Veteran Owned (VOSB), Service Disabled Veteran Owned (SDVOSB), and Historically Underutilized Business Zone (HUBZone) businesses for the purposes of determining the appropriate level of competition and/or small business subcontracting goals for the procurement. The following information is requested:

1. Section 1 - Company Information: Provide responses to the following business information by completing the below table (Limited to 1 page.):

Category Response Company Name and Address Company Cage Code and DUNS POC (Name, Email, Phone) Business Size under NAICS 541712. Indicate Large, Small, SDB, 8(a), WOSB, VOSB, SDVOSB, HUBZone.

Number of Employees and Average Annual Receipts (3-year average)

Affiliate information: Provide information on parent company, joint venture partners, potential teaming partners, prime contractor (if potential subcontractor), or subcontractors (if potential prime contractor) Does your firm intend to submit an Offer as a Prime Contractor? Subcontractor?

If planning on proposing as a small business prime contractor, note your ability to comply with FAR 52.219-14, Limitations on Subcontracting

(JAN 2017).

2. Section 2 – Ability to Perform: Submit a capability statement that includes the following (Limited to 10 pages.):

a. Details on ability to perform all or any aspects of the effort described above and specifically identifying any requirements that can’t be met and why, along with a quantitative indication of how closely the affected requirements can bet met.

b. A draft schedule highlighting the following:

1. Major milestones from contract award through launch and operations (e.g., needed contract award date; spacecraft selection timeframe; instrument delivery date required relative to launch date).

2. In regards to augmenting the Integration and Test (I&T) schedule to include the MAIA Instrument, how much time is allocated for the specific MAIA activities? Does this include schedule reserve to address unexpected challenges?

3. List of information and deliverables that Contractor will need to receive from the MAIA Program.

4. Schedule for information and deliverables to be received from the MAIA Program.

c. A description of preferred concept of operations for science data collection and downlink (e.g., periodic high rate vs. longer duration low rate transfer of instrument data to spacecraft for storage and later downlink; downlink compression; anticipated frequency and duration of science data downlink).

d. Description of any impact of a request for expedited delivery of science data for high-priority targets of opportunity (TOOs). Any planning for including TOOs would occur during daily uplinks and TOOs data acquisition would be normal; however, delivery of the TOOs data is desired sooner than 2-day latency as noted in requirementL2-H30, above. Examples of TOOs are industrial accidents, major wildfires, and volcanic eruptions.

e. Description of whether an increase in stowed MAIA cross-track instrument width from 0.9 m to

1.0 m, along-track length from 0.7 m to 0.75 m and/or height from 0.5 m to 0.55 m (deployed height from 0.55 m to 0.6 m) will impact accommodating the MAIA payload.

f. Description of any impact of specifying am (morning) or pm (afternoon) dayside equator crossing and ascending or descending node.

g. Description of your ability to support molecular and particulate contamination control measures during integration and on-orbit operations to prevent contamination of UV sensitive camera optics.

h. Description of your ability to support single use pyrotechnic and/or non-explosive initiator activation to facilitate MAIA launch lock release.

i. Description, duration, and expected frequency of any anticipated maneuvers that would result in violating the MAIA KOZs, FOV, thermal, or pointing performance requirements (e.g., thruster firing, attitudes required to accommodate host or other payload(s) needs).

j. Description of your ability to provide a spacecraft simulator to validate interfaces and when it could be provided to the MAIA Program.

k. Rough Order of Magnitude price estimate to meet these requirements, including a separate breakout for (1) Integration, Test, and Launch and (2) Operations. The response shall include a brief discussion of the basis of estimate and any uncertainty in the cost estimate.

l. Identification of the technical maturity/qualification of the proposed access to space 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.

m. Mission Assurance protocol related to hardware and software for payload integration, testing, and mission operations.

n. Hosted payload opportunities for the period of 2020-2024 with associated mission parameters including, but not limited to:

1. Mission Name

2. Launch Date

3. Host Provider / Partnership

4. Payload Environment

i. Temperature Range

ii. Quasi-static loads

iii. Minimum resonant frequency

iv. Random vibration and acoustic loads

v. Shock environment

vi. Disturbance torque

vii. RF Field EMI/EMC/In-Space Charging

5. Launch Vehicle

6. Logistical considerations and constraints for operating the MAIA instrument.

7. Orbit altitude and eccentricity.

8. Daylight equator-crossing time and whether the crossing occurs on the ascending or descending node.

9. Expected mission life and reliability

10. Documentation supporting reliable access to space and mission duration, including heritage.

3. Section 3 - Performance/Experience: Provide a list of up to three (3) customers covering work performed within the past three (3) years by providing the following (Limited to 1 page per customer reference.):

Category Response Customer Company Name and Address Customer POC (Name, Email, Phone) Contract Number Contract Value (including all options) Contract Title/Short Description Contract Period of Performance (start and end dates, including all options)

NAICS Code Relevant Work Performed (including experience with integration and operation of science instruments):

4. Section 4 – Procurement Strategy Input: Based on your past experience and the above requirements, provide information regarding potential procurement strategies to maximize the effectiveness of the anticipated solicitation and resulting contract. Specifically, input on the following is desired (Limited to 2 pages)

a. Contract type (Firm-Fixed-Price vs Cost-Reimbursement).

b. It is anticipated that this requirement will be considered a commercial service as defined in FAR

2.101. As such, please provide feedback on this approach, including any exceptions/additions to the FAR Part 12 terms and conditions (e.g., typical milestone payments/financing provisions;

payload liability and indemnification).

c. Evaluation approach (e.g., Full trade-off between Mission Suitability, Past Performance, and Cost/Price; Lowest Price Technically Acceptable (LPTA); Price Performance Tradeoff (PPTO)) and factors (i.e., key discriminators in selecting a Contractor).

d. Key factors/parameters that affect pricing (e.g., rate per kilogram).

e. Factors the Government ought to consider (risks/benefits/impacts) if choosing an owner-operator as Prime Contractor. Similarly, factors the Government ought to consider (risks/benefits/impacts) if choosing a manufacturer as Prime Contractor.

IV. Submission Requirements and Other Information

Technical questions shall be directed to: Barbara Hilton (Barbara.B.Hilton@NASA.gov) with “MAIA Hosted Payload RFI Question” annotated in the subject. General or Procurement related questions shall be directed to: Karen Dempster (Karen.C.Dempster@NASA.gov) with “MAIA Hosted Payload RFI Question” annotated in the subject.

All responses shall be in 12 point Times New Roman font and submitted via email only to Karen Dempster (Karen.C.Dempster@NASA.gov) with a copy to Michael Kaszyca (Michael.Kaszyca@nasa.gov) no later than 3:00 PM EDT on August 14, 2017. Please reference “MAIA Hosted Payload RFI Response” in any response.

This synopsis is for information and planning purposes and is not to be construed as a commitment by the Government nor will the Government pay for information solicited. Respondents will not be notified of the results of the review. Responses to this synopsis will be reviewed by both civil servants and support service contractors.

No solicitation exists; therefore, do not request a copy of the solicitation. If a solicitation is released it will be synopsized in FedBizOpps. It is the potential Offeror’s responsibility to monitor these sites for the release of any solicitation or synopsis.

NOTE: It is anticipated that any procurement resulting from this request for information will consider domestic sources only as Public Law 105303, 51 U.S.C 50131, et. seq., states that the Federal Government shall acquire space transportation services from United States commercial providers whenever such services are required in the course of its activities. The launch service provider will be responsible for obtaining a Federal Aviation Administration (FAA) license as a commercial procurement is anticipated, as well as securing any necessary range assets and approvals for the launch.

mailto:Barbara.B.Hilton@NASA.gov mailto:Karen.C.Dempster@NASA.gov mailto:Karen.C.Dempster@NASA.gov mailto:Michael.Kaszyca@nasa.gov