1. Payload Launch Campaign Planning and Expectations Sponsoring Org/Office Code: OZ POIWG Date: July 2015 OZ/Brienne Shkedi SPX4/SPX5 Lead RIM 281-483-9858 brienne.shkedi@nasa.gov OZ/Yuri Guinart-Ramirez SpX6 OZ Flight Lead and LIS 281-244-8151 Yuri.guinart-ramirez-1@nasa.gov OZ/Andrew Clem SpX7 OZ Flight Lead and Tech Demo Office Engineer 281-483-0751 Andrew.l.clem@nasa.gov

2. The OZ Flight Leads performs the following functions: – Collects, analyzes, and coordinates payload unique constraints within the program for a single flight Resulting data is used to build a launch campaign that meets requirements, such as – Maximum time to activation – Minimum docked mission duration – Maximum docked mission duration – Maximum return to port time – Number of consecutive launch attempts that can be supported Help others understand when decision-making is needed to minimize impact to payload community – Presents the payload constraints at the Stage Operations Readiness Review (SORR) – Serves as the payload developer point of contact for mission updates, including launch and return opportunities and changes Provides regular statuses on the launch campaign with launch dates, time to reach station, return dates, time to reach port, etc. – Coordinates launch viewing passes, where applicable – Collects payload developer lessons learned for post-mission review – Other duties as assigned 2 What is the OZ Flight Lead? Need good data from PDs to make this part successful!

3. Goal is to launch on the day planned to. Reality is that real time issues with the vehicle, rocket, ISS, or weather may result in delays. The “Launch Campaign” is the primary launch plan, and the follow-on plan if that doesn’t work out. Distributed to PDs in a table of potential launch dates. Identifies known risks to any particular date. 3 What is a Launch Campaign? SpX7 Example  Depending on real-time events, it is possible that the vehicle provider will attempt launch on ANY day in the launch campaign.  Launch campaign days can be added/deleted as SpX analysis gets refined including latest ISS Trajectory data. Launch Campaign Payload Planning Constraints In the event of a scrub, recommend PDs be prepared to move to the next possible launch date.

4. Many variables affect a mission launch campaign and feasible launch dates – Other vehicle traffic and significant on-orbit activities (i.e. EVAs) – Range availability (ISSP flights don’t always get priority) – Beta constraints – Lighting and distance to port for various unberth opportunities – Payload operations requirements  SpX-4 was planned around 2 USOS EVAs, a RS EVA with jettison, Soyuz launch and docking, Progress exchange, capture with 3 crew, and unberthing in high beta; all while trying to ensure the exact right minimum berthed duration for Rodent Research and maximum berthed duration for Fruit Flies. Orb-3 had all that PLUS SpX4 in its way! Vehicle constraints may be relaxed as needed to enable more launch or landing opportunities. – Ex: may agree to extend return to port >48 hrs (SpX5 and SpX-6) It’s a really big deal to slip a flight! – Expect SpX/Orb decisions on launch dates as late as possible while issues are worked Cost, contract implications, and next customers all considered. Precise planning of these constraints starts ~L-4 months Focused attention on potential launch campaign after the preceding flight – However, the vehicle schedule can have us starting data collection for the next mission way before we finish the last one (SpX5 to SpX-6, SpX-6 to SpX-7) 4 Why are Launch Campaigns so Variable?

5. Differences between general assumptions on key planning parameters and reality  If your payload truly has a constraint in any of these areas, it will drive a launch or unberth decision. 5 How are Payload Constraints Factored into the Launch Campaign? Bad Assumption SpX RealityComments Rendezvous Time (“Launch to HA3”) 3 days1 to 5 days Rendezvous time is dictated by orbital mechanics (where is the ISS at time of launch) and arrival window for berthing during crew wake periods. Also protect for a 24 hr re-rendezvous contingency. Berthed Duration 30 days25 to 40 days Balance between total crew time needed, available landing opportunities, and other events (EVAs or other VV traffic). Return to Port Time 48 hours25 to 60+ hours 48 hours per contract, but routinely extended to enable more unberth opportunities. Add 3 hours for sample T/O to PD at airport. Max Mission Duration None40 to 45 days From pre-launch turnover to sample recovery post-flight. # Cargo Turnovers 3Continuous Vehicle Provider will move through the launch campaign as needed depending on real time conditions. Cargo Refresh Time Between Scrubs A while1 hour PD time with cargo with 48-hr scrub: Lockers: 5 hours (from/to KSC) Coldbags:1 hour (from/to cold stowage) CTBs: 1 hour (from/to CMC) In addition factor in the potential for launch slip(s)

6. Activation Timeline for SpX Missions How long could it be before my payload is activated? Refer to the following timeline and discussion of major events. Turnover to Launch – This is negotiable, but is typically Launch-24 hours. A launch slip could extend this by about 24 hours. Launch to HA3 – HA3 is the third height adjustment rendezvous burn. Rendezvous timelines are built such that this occurs at 07:00 UTC for SpX vehicles. This typically occurs between 20 and 70 hours from launch. This time is launch day dependent. If launch is delayed a day, time to HA3 could stay the same or increase or decrease by as much as 24 hours. HA3 to Berth – Berthing usually occurs about 8 hours after HA3. Berth to Activation – Hatch open usually takes place the day after berth. TurnoverLaunch Slip? Launch HA3 BerthActivation Standard cargo scrub capability Late load cargo can be swapped for a 48 hr scrub, but ISSP may assess back-to- back-to-back launch attempts For a 24 hr slip, only cargo on the hatch can be swapped; but it is considered a unique requirement and must be specifically requested via you PIM/RIM) as early as possible Eventually TGHR should reflect these requirements

7. Needed to support SORR at ~L-5 weeks (provide at least 2 weeks prior to SORR) PD data drives key decision points leading up to launch: – How long before a new launch date do we need to turn on work? If it’s in the Launch Campaign, assume that date is “turned on” – How close to a set launch date do we need to stop work (if we expect to slip) in order to preserve later launch opportunities? Need to know critical milestones during payload ground prep. Provided to OC/ON/SpaceX as decision points leading up to launch Data also collected to assess PD’s ability to meet scrub schedules – How many launch attempts can your resources support? – Do you intend to provide new hardware and samples for next launch attempt or re-use hardware previously delivered? – If re-using, how much time do you need with that hardware/sample to “refresh”? May drive minimum spacing between launch attempts Ground Operations Data Needed from PDs to Support Launch Campaign Launch Date T-Cell Stop Blood Draw JAXA Epigenetics T-Cell Isolation Start (18 hrs) (L-24 hr delivery) Micro 5 Biocell/BRIC 20 Sample Install T-Cell EC Fill (L-24 hr delivery) Flatworms Sample Cut UTCKSCL-3 daysL-30 hours 1/10 9:451/10 4:45 -- 1/7 4:451/8 7:001/8 13:301/8 14:001/8 22:45 1/13 8:341/13 3:341/8 21:001/10 3:341/11 6:001/11 12:001/11 13:001/11 21:34 1/14 8:121/14 3:121/9 23:001/11 3:121/12 13:001/12 12:001/12 18:001/12 21:12 SpX5 Example When something changes we need to know in order to understand the timing constraints & pass to ON & SpaceX !!

8. If your payload doesn’t meet “reality” on slide 5, ISSP wants to know by ~L- 4 months for initial planning. – Data solicited from OZ Flight Lead and FPM to support FPIP CRs and assessments and refined leading up to SORR Data collected to determine: – Payload constraints that might dictate specific launch or unberth date – Cargo in nominal load that might be impacted in case of significant delays No one else in NASA has this data yet (updated PTP Blank Book will eventually include for access via Orbit, ECD TBD) – Can be discerned from PPOs (if they’ve been provided by this timeframe) Rendezvous time requirements Min berthed duration – Not available anywhere Max mission duration Return to port requirements Limited life of items in nominal load Any other unique requirements – Ex: 2 USOS crew needed for RR1, RR2; operations/tasks constrained to very specific Flight Days like RR-2 dissection windows; sensitivity to changes in berthed duration/return dates if adjusted after launch (or a particular event) 8 Payload Launch & Unberth Constraints Driving Selection of Viable Dates

9. Currently roughly at ~ L-4 to 5 months will kick-off the questionnaire via FPM to PIM/RIM teams – Usually driven to support FPIP upcoming CR but could be driven by ISSP management awareness of payload constraints for upcoming vehicle milestones – Initial data gathering can have additional clarification requests as the constraints are fully understood – Once data collection is done via Orbit, this process may become a “check/update” these sections already in Orbit – As we get closer to launch, and as subsequent FPIP updates are worked through, the data will be refined and the “products” Draft Payload Constraints Summary produced to compile all the constraints at ~ L-3 months Initial Launch Campaign chart produced at ~ L-3 months – Payload Summary Constraints, FPIP constraints, SpX Launch Opportunity Memo are all inputs to it, plus an additional information available from VV – Distribution to PD teams dependent on fidelity of known FPIP constraints ~ L-2.5 months SORR presentation at ~ L-5 weeks should be a much more refined set of Payload Constraints including Ground Operations – KSC personnel will continue to verify Ground constraints after SORR (or as soon as teams arrive at KSC), as we understand unexpected things can happen and drive changes to decision need dates SPX5 Launch Campaign Payload Planning Constraints 9 Data Collection Timeline

10. OZ Flight Lead is your main source for information for launch status – Don’t listen to launch date rumors, listen to the OZ Flight Lead! Plan for reality – Anticipate the possibility of a rolling launch campaign. – Use realistic assumptions for your pre-flight and on-orbit ops planning. People want your data so they can help make you successful – It is really OK to have the Launch Campaign planned around your payload! If we can’t meet a constraint, then we won’t; but it is OK to ask – Tell us about critical milestones in your ground preparation so that decisions are made in time to meet your needs. – Inform ISSP when your payload has hard constraints in on-orbit ops or post- flight that need to be considered when selecting launch or unberth dates. – YOU know your payload constraints, and if a question doesn’t quite match a constraint concern you have - TELL US. We cannot provide the best protection for payload success if we don’t understand what matters to your payload most. SPX5 Launch Campaign Payload Planning Constraints 10 Summary

11. Back-Up SPX5 Launch Campaign Payload Planning Constraints 11

12. Ground Processing Information 12 Question#Detail or Explanation Once at the launch site, how long before launch do you need to begin sample preparation? L-__ days/hrs How many sample turnovers are you prepared to support? Is this limited by hardware availability, sample availability, or something else? # Time points for Irrecoverable work during ground prep. This is work which, if performed, will limit ability to support later launch attempts (i.e. activating samples when you have a limited number of samples available for the launch campaign). L-__ days/hrs Other critical factors or milestones in your ground operations which should be considered in determining the launch campaign after a scrub (i.e. time needed for ordering new samples)? L-__ days/hrs Standard cargo turn-around times with 48-hr scrub: Lockers: 5 hours for processing between receipt from KSC/UB and handover back to KSC/UB Coldbags:1 hour for processing between receipt from Cold Stowage Team after coldbag deintegration and handover back to Cold Stowage Team for packing for re-launch. CTBs: 1 hour for processing between receipt from KSC/UB and handover back to KSC/UB for re-launch. What is your scrub support plan (complete sample swap, or refresh of samples returning fro the vehicle)? Does it fit within the standard capability?

13. Payload Launch & Unberth Constraints 13 Question#Detail or Explanation For each launch opportunity, the time to berthing will vary with orbital mechanics of the two vehicles. Do your payload requirements dictate a specific launch to berth window? Expect this would be driven by life limit of samples or required start time from turnover or launch. Indicate constraint and explain limiting factors (ex. experiment must start by T/O + X hrs; biological samples die by T/O + X hrs, experiment is fine as long as temperatures are maintained, etc.). Cold stowage hold times do not need to specified. Payload Start by T/O + ___ hrs OR L + ___ hrs Minimum or maximum berthed duration constraint and limiting factors (ex. facility through-put, min/mix 0g exposure, life limit from last operation, etc.). ___ days It’s possible that we will launch with some variables still in work and the unberth date TBD. Does your payload have any impacts if berthed duration is changed after launch? Indicate constraint and explain the impact. Y/N For each unberth opportunity, the time for cargo to be returned will vary depending on distance from port at splashdown. Standard sample return times are based on an assumed return to port of R+ 48 hrs; however, in order to enable more launch/unberth opportunities, the ISSP may agree to let Dragon land farther out with delayed return. Do your payload requirements dictate a specific minimum return to port time? Expect this would be driven by life limit of samples in 1g. Indicate constraints and explain limiting factors. Return By R+ ___ hrs Standard sample handover times provided in word file.

14. SpX-6 SORR Example Payload Launch/Landing Constraints SpX6 Current Prime Launch and Unberth Plan Meet the Following Payload Constraints Launch to Berth Constraints: Payload start L1+3.75 days (Next Limiter L1+4.5 days) – NanoRacks Module-53 (The Hydrofuge) Module can sustain up to 5 days without power (T/O L1-30 hrs) For Back/up launch date 4/11 with no 24 hr late-load cargo swap, will likely exceed 5 days without power but will not request to constraint Launch Opportunities to preserve it – Cell Shape and Expression (Cytospace) and Nanoparticles & Osteoporosis (NATO) Experiments start by 108 hours after ground prep, needs Kubik 5 commissioning/check-out completed – Osteo-4 Tray 1 operations by L1+ 4.5 days to obtain early mG exposure data (at +8°C setpoint) Automated activation at L1+36 hr with 72 hr for Tray 1 ops on ISS – PCG-3 start by 5 to 7 days for science quality (preferred 5) Min Berthed Duration Constraints: 27 days (Next Limiter: 25 Days) – 27 Days: JAXA/Space Aging 27 days for sequenced operations and sample temperature conditioning for 24 hours in MELFI, and POLAR transfer to Dragon. – 25 Days: Rodent Research -2 (CASIS samples return) 25 days payload operations and return CASIS samples #1-#3 on SpX-6, including POLAR transfer to Dragon Max Mission Duration Constraints (T/O through sample handover back to PD at LGB in California): > 45 days (No other known next Limiter identified) – >45 days but < 60 days: PCG-3 Once experiment is deactivated after ops complete, and back to ambient temperatures the samples are more stable. Return Constraints: Sample H/O to PD at LGB ≤ 60 hrs – 58 hrs: BRIC-21 and JAXA/Space Aging & Nematode (or more time if samples maintained at their respective temperature requirements) – 70 hrs: PCG-3: Sample degradation from temperature excursions away from ambient temperature. In this case, G does not impact formed crystals. – All other payloads need earliest possible, or limited based on max mission duration.

15. SpX-6 SORR Example Payload Ground Preparation Decision Points for Launch Prep Start: How soon do we need to tell PDs to plan for a given launch date in order for them to be ready to support? LAUNCH L- 29 days (RR-2 animal acclimation) L-21 days (JAXA Space Aging & Nematode ground prep start; Refrigerated nematode culture start) L-2 wks (BRIC-21 only if additional growth medium req’s for launch scrubs) L-1 wk (Triplelux-A EC HM Interface filling; BRIC-21 sample prep; RR-2 TPK sample load) Decision Points for Launch Prep Stop: When do we need to tell PDs to stop prep in order to preserve later launch opportunities? LAUNCH L-1 wk L-4 days (JAXA/Decid e Samples to launch) L-3 days (RR-2 TPK sample load) L-6 daysL-5 daysL-4 daysL-3 days L-2 days L-1 day L-2 days (JAXA Space Aging & Nematode load samples into flight chambers) L-29 hrs (RR-2 Food bar install & Animal loading in Transporter)  Triplelux-A: No turnover planned for Cell samples & reagents; lifetime (in cold stowage) approx. 6 months  Bric-21: If more than 21 days from original launch date, complete sample swap  JAXA Space Aging: 7 times turn-overs are available (each turn-over covers 4 days continuous launch window.  JAXA Nematode Muscles: 20 times turn-overs available (each covers 2 days continuous launch window) L-5 days (BRIC- 21 sample prep)