SSP_50489-Rev_G.docx

ISS Mission Integration Template

International Space Station Program

Revision G

June 2017

This document may be used only in the International Space Station (ISS) program to fulfill responsibilities of a Cooperating Agency of an ISS Partner in furtherance of the ISS Intergovernmental Agreement. Re-transfer or disclosure to, or use by, any persons other than citizens of ISS Program International Partner countries, or use for any other purpose, requires prior Governments authorization of all ISS Program Partners who approve this document.

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract Number: NNJ12GA46C

SSP 50489

Revision G

REVISION AND HISTORY PAGE

DCN 001 (Reference per SSCD 007451, EFF. 04-14-03;

SSCD 007451R1, EFF. 05-15-03)

DCN 001 (Reference per SSCD 009876, EFF. 06-14-07)

(DCN 002 was intentionally omitted due to the DCN numbering policy prior to the MIC Contract)

DCN 003 (Reference per SSCD 010360, EFF. 11-29-07)

DCN 004 (Reference per SSCD 011280, EFF. 06-11-09)

DCN 005 (reference per SSCD 011894, EFF. 04-15-10)

REVISION AND HISTORY PAGE

PREFACE

iss mission integration template The purpose of this document is to define the templates used to develop schedules for the mission integration of United States (U.S.), International Partner (IP), and Visiting Vehicle Provider (VVP) launched hardware and cargo to the International Space Station (ISS). These schedules track products (such as data deliveries and analyses) and major milestones (such as Program-level reviews) and are used to ensure that the mission integration process is completed successfully and in a timely manner.

Need dates for schedule activities are initially calculated based on the templates. The templates identify the activities that will be included on the schedule and when they must occur based on their relation to each other and to the projected launch date, increment, or Increment Definition and Requirements Document (IDRD) period. The generic schedules for all Visiting Vehicle (VV) flights are included in this document.

This document is under the control of the Multilateral Mission Integration and Operations Control Board (MMIOCB).

iii

INTERNATIONAL SPACE STATION PROGRAM

iss mission integration template

CONCURRENCE

june 2017

See Directive Approval

Ryan L. Prouty Manager, Mission Integration and Operations National Aeronautics and Space Administration

Sergey Khumonin Head of Safery, Reliability and Verification Department Rocket Space Corporation - Energia

Date

Date

Bernardo Patti ESA ISS Program Manager European Space Agency

Ken Podwalski Program Manager Canadian Space Station Program

Date

Date

Koichi Wakata ISS Program Manager Japan Aerospace Exploration Agency

Date

INTERNATIONAL SPACE STATION PROGRAM

iss mission integration template

CONCURRENCE

june 2017

TABLE OF CONTENTS

APPENDIX

TABLE

FIGURE

1-1 introduction purpose scope The purpose of SSP 50489, ISS Mission Integration Template, is to define the template that is used to develop the hardware and cargo integration schedules for United States (U.S.) and International Partner (IP) provided hardware and cargo for both utilization and logistics which is to be launched for use on the International Space Station (ISS) or brought to orbit for ISS science.

This document defines the schedule templates for the ISS hardware missions. These templates include ISS Mission Integration and Launch Vehicle Integration milestones.

precedence This document is a planning guide. Actual implementation schedules may deviate from the template, if new constraints or requirements develop. In instances of new generic updates to the template schedule, a CR shall be submitted for review and disposition in order to update SSP 50489.

delegation of authority This document is approved by the Multilateral Mission Integration and Operations Control Board (MMIOCB).

milestone explanation A symbol designating the milestone level will be displayed to the left of the milestone in the Mission Integration Template schedules. The Milestone Levels are defined as follows:

table 1.5-1 milestone explanation table

documents applicable documents The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The documents listed in this paragraph are applicable to the extent specified herein. Inclusion of applicable documents herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of this document.

reference documents The following documents contain supplemental information to guide the user in the application of this document. These reference documents may or may not be specifically cited within the text of this document.

Volume 1: Station Program Management Plan

Volume 2: Program Planning and Manifesting

Volume 4: Payload Engineering Integration

SSP 50200-05

Part 1 Station Program Implementation Plan, Volume 5: Logistics and Maintenance, Part 1: Maintenance

SSP 50200-05

Part 2 Station Program Implementation Plan, Volume 5: Logistics and Maintenance Part 2: Logistics

Volume 7: Training

Volume 8: Increment Execution Preparation

Volume 9: Real-Time Operations

Volume 10: Sustaining Engineering

Volume 11: ISS Cargo Integration Processes

2-3

Soyuz Missions Launched on a Soyuz Launcher Generic schedulE ISS Mission Integration Template – Soyuz (Figure 3.1-1) details Soyuz missions launched on a Soyuz launcher. This figure details at a high-level a Mission Integration Schedule Template for a Soyuz vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for Soyuz Missions to the ISS relative to flights and increments. Specific Level I and Level II flight schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for Soyuz missions to the ISS that are launched on a Soyuz Launcher. Flight-specific schedules are obtained by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar dates for each applicable milestone is determined by the appropriate task owners and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term hardware (HW) will be used to identify space bound items that the HW providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown, the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: National Aeronautics and Space Administration [NASA].

Landing occurs dependent on post-undock and/or deorbit burn targeting.

3-1

Figure 3.1-1 iss mission integration template – soyuz (6 pages)

3-7

Progress missions Launched on a Soyuz Launcher Generic ScheDUle ISS Mission Integration Template – Progress (Figure 4.1-1) details Progress missions launched on a Soyuz launcher. This figure details at a high-level a Mission Integration Schedule Template for a Progress vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for Progress Missions to the ISS relative to flights and increments. Specific Level I and Level II flight schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for Progress missions to the ISS that are launched on a Soyuz Launcher. Flight-specific schedules are obtained by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar dates for each applicable milestone is determined by the appropriate task owners and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term HW will be used to identify space bound items that the H/W providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: [NASA].

4-1 figure 4.1-1 iss mission integration template – Progress (7 pages) figure 4.1-1 iss mission integration template – progress (7 pages) figure 4.1-1 iss mission integration template – Progress (7 pages)

4-3

DCN XXX

DCN XXX

DCN XXX

HTV Missions launched on AN h-iib rocket generic schedule ISS Mission Integration Template – HTV (Figure 5.1-1) details HTV missions launched on an H-IIB rocket. This figure details at a high-level a Mission Integration Schedule Template for an HTV vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for HTV Missions to the ISS relative to flights and increments. Specific Level I and Level II flight specific schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for HTV missions to the ISS that are launched on the H-IIB Rocket. Flight-specific schedules are obtained by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar date for each applicable milestone is determined by the appropriate task owner and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term HW will be used to identify space bound items that the HW providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: [NASA].

5-1 figure 5.1-1 iss mission integration template – htv (7 pages) figure 5.1-1 iss mission integration template – HTV (7 pages) figure 5.1-1 iss mission integration template - HTV (7 pages) 5-8

Spacex CARGO Dragon Missions launched on A Falcon Rocket generic schedule ISS Mission Integration Template – SpaceX Cargo Dragon (Figure 6.1-1) details SpaceX (SpX) Cargo Dragon missions launched on a Falcon rocket. This figure details at a high-level a Mission Integration Schedule Template for the SpX Cargo Dragon vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for SpX Cargo Dragon Missions to the ISS relative to flights and increments. Specific Level I and Level II flight specific schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for SpX Cargo Dragon missions to the ISS that are launched on a Falcon Rocket. Flight-specific schedules are obtained by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar date for each applicable milestone is determined by the appropriate task owner and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term HW will be used to identify space bound items that the HW providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: [NASA].

Landing occurs dependent on post-unberth and/or deorbit burn targeting.

6-1 figure 6.1-1 iss mission integration template – spacex cargo dragon (6 pages) figure 6.1-1 iss mission integration template- spacex cargo dragon (6 pages)

6-7 orbital ATK Cygnus Missions launched on AN antares Launcher or atlas v rocket generic schedule ISS Mission Integration Template – Orbital ATK Cygnus (Figure 7.1-1) details Orbital ATK (OA) Cygnus missions launched on either an Antares launcher or an Atlas V rocket. This figure details at a high-level a Mission Integration Schedule Template for the OA Cygnus vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for Orbital ATK Missions to the ISS relative to flights and increments. Specific Level I and Level II flight specific schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for OA Cygnus missions to the ISS that are launched on either an Antares Launcher or Atlas V Rocket. Flight-specific schedules are obtained first by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar date for each applicable milestone is determined by the appropriate task owner and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term HW will be used to identify space bound items that the HW providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: [NASA].

7-1 figure 7.1-1 iss misssion integration template – orbital ATK (5 pages) figure 7.1-1 iss mission integration template – orbital ATK (5 pages)

7-6

SpaceX Crew Dragon Missions Launched On A Falcon Rocket generic schedule ISS Mission Integration Template – SpaceX Crew Dragon (Figure 8.1-1) details SpaceX (SpX) Crew Dragon missions launched on a Falcon rocket. This figure details at a high-level a Mission Integration Schedule Template for the SpX Crew Dragon vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for SpX Crew Dragon to the ISS relative to flights and increments. Specific Level I and Level II flight specific schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for SpX Crew Dragon missions to the ISS that are launched on a Falcon Rocket. Flight-specific schedules are obtained by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar date for each applicable milestone is determined by the appropriate task owner and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term HW will be used to identify space bound items that the HW providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: [NASA]. Landing occurs dependent on post-undock and/or deorbit burn targeting.

10-1 figure 8.1-1 iss mission integration template – spacex crew dragon (6 pages) figure 8.1-1 iss mission integration template – space crew dragon (6 pages)

Figure 8.1-1 ISS Mission Integration Template – Spacex Crew-dragon (6 pages)

Boeing Commercial Crew Transportation (CST)-100 Missions launched on AN ATlas V Rocket generic schedule ISS Mission Integration Template – Boeing CST-100 (Figure 9.1-1) details Boeing CST-100 missions launched on an Atlas rocket. This figure details at a high-level a Mission Integration Schedule Template for the Boeing CST-100 vehicle. The schedule template is for planning purposes and is the starting point for creating the specific Mission Integration Schedules for Boeing CST-100 Missions to the ISS relative to flights and increments. Specific Level I and Level II flight specific schedule milestones and dates are coordinated by the applicable Visiting Vehicle Leads and Increment Managers and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to build the ISS flightspecific mission integration schedules for Boeing CST-100 missions to the ISS that are launched on an Atlas V Rocket. Flight-specific schedules are obtained by generating a generic template schedule based on the generic template milestones that are applicable for the particular mission. The true calendar date for each applicable milestone is determined by the appropriate task owner and associated teams and approved by the task owners, associated teams, Visiting Vehicle Leads and Increment Managers.

For the purpose of this document, the term HW will be used to identify space bound items that the HW providers send to a U.S. packing facility for processing, packing and/or shipping prior to being loaded onto the vehicle. Once the HW has left the packing facility, it becomes cargo.

Also, for clarity, when two dates are shown the first one is the anchor date and the other date is the corresponding Launch minus reference date. The task owner will be shown in brackets; e.g.: [NASA]. Landing occurs dependent on post-undock and/or deorbit burn targeting.

figure 9.1-1 iss mission integration template – boeing cst-100 (5 pages) increment schedules generic schedule ISS Mission Integration Template – Increment (Figure 10.1-1) details the high-level Mission Integration Schedule Template for a two-increment Increment Definition and Requirements Document (IDRD) period as defined by the IDRD. The schedule template is for planning purposes and is the starting point for creating specific Mission Integration Increment Schedules. Specific schedule milestones and dates are coordinated by the applicable Increment Manager and will be approved and baselined by the appropriate ISS panels and control boards.

The schedule template contains the functional sections required to facilitate tracking of planned launches to and departures from the ISS, major milestones, and Change Request (CR) development applicable to ISS Flight Plan, the IDRD and its Annexes 1-5. Increment milestones are obtained by generating a generic template schedule based on the generic template milestones and submitting to the Increment Manager and appropriate task owners where true calendar dates for each applicable milestone are established.

INCREMENTS

An increment is a specific time period on the ISS which combines different operations such as, scientific research, maintenance, and other ISS system and utilization operations. The duration of an increment is the time period from the undocking of a Soyuz to the undocking of the next Soyuz and can support one or more stages. A stage is a designated period during an Increment delineated by a vehicle docking or undocking and is further defined by the number of crew aboard (for example 3, 6, or 7 persons). Specific stage definitions for each Increment are documented for requirement documentation and planning purposes in the Increment IDRD and updated Post-Stage Operations Readiness Review (SORR) in the Current Stage Requirement Document (CSRD).

figure 10.1-1 iss mission integration template – increment (10 pages)

Figure 10.1-1 ISS Mission Integration Template – increment (10 pages)

10-11

Combined milestone definitions table Milestone definitions This section contains the definitions of the milestones in the Mission Integration Template Schedules. The description of each milestone is explained in Table 11.1-1, Combined Milestones Definitions. To the extent possible the milestones in the table are ordered alphabetically by Template Section. Included in the table are the following fields.

VEHICLE or Increment A Visiting Vehicle is defined as a vehicle that docks or berths to the ISS. Currently there are seven (7) Visiting Vehicles. They are Soyuz, Progress, HTV, SpaceX Cargo Dragon, Orbital ATK Cygnus, SpaceX Crew Dragon, and Boeing CST-100. The Soyuz, Progress, SpaceX Crew Dragon, and Boeing CST-100 vehicles dock and undock with the ISS. The HTV, SpaceX Cargo Dragon, and Orbital ATK Cygnus vehicles berth and unberth with the ISS.

An increment is defined as a specific time period on the ISS which combines different operations such as scientific research, maintenance, and other ISS system and utilization operations. The duration of an increment is the time period from the undocking of Soyuz to the undocking of the next Soyuz and can support one or more stages. Specific stage definition for each increment are documented in the increment IDRD and CSRD for requirement documentation and planning purposes.

milestone This is the name of the milestone. These milestones are associated with a schedule template date which is shown in relation to milestones such as On-Dock (O/D)/Increment (I) /Launch (L) /Undock (UD)/ Unberth (UB), Return (R) to name a few. These are schedule template dates in month (m), week (w), day (d) or hours (h) time increments.

Description Defines the “who, what, where and why” of a milestone.

Template section Identifies the section in the Mission Integration Schedule Template where the milestone can be found.

Controller/Facilitator(s) One or more organizations may be included in the Controller/Facilitator(s) column. The first is the organization responsible for, or in control of, the requirements met by the product, review, etc. The second and subsequent organizations are responsible for implementing the requirements or facilitating the review. If only one organization is included in the column, then that organization is both the Controller and the Facilitator.

Predecessor A milestone which occurs prior to, and provides information or products to, the milestone being defined.

Successor A milestone which occurs after the milestone being defined that receives information or products from that milestone.

Waste Management Sections In interest of identifying and describing the Waste Management (WM) milestones in Table 11.1-1, Combined Milestone Definition Table, a letter designation of WM- has been placed before each milestone. Doing so also allows for the Waste Management milestones to remain together when the table is sorted.

11-2

Table 11.1-1 combined milestone definitions (28 pages)

Table 11.1-1 combined milestone definitions (28 pages)

Table 11.1-1 combined milestone definitions (28 pages)

Table 11.1-1 combined milestone definitions (28 pages)

Table 11.1-1 combined milestone definitions (28 pages)

11-30

Appendix a - Acronyms and abbreviations

B-1

APPENDIX b - GLOSSARY <Reserved>

Appendix c - open work Table C-1 lists the specific To Be Determined (TBD) items in the document that are not yet known. The TBD is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBD item is numbered based on the section where the first occurrence of the item is located as the first digit and a consecutive number as the second digit (i.e., <TBD 4-1> is the first undetermined item assigned in Section 4 of the document). As each TBD is solved, the updated text is inserted in each place that the TBD appears in the document and the item is removed from this table. As new TBD items are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBDs will not be renumbered.

Table C-1 to be determined items

Table C-2 lists the specific To Be Resolved (TBR) issues in the document that are not yet known. The TBR is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBR issue is numbered based on the section where the first occurrence of the issue is located as the first digit and a consecutive number as the second digit (i.e., <TBR 4-1> is the first unresolved issue assigned in Section 4 of the document). As each TBR is resolved, the updated text is inserted in each place that the TBR appears in the document and the issue is removed from this table. As new TBR issues are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBRs will not be renumbered.

table C-2 TO BE RESOLVED ISSUES

C-1 image3.png

Row Title

72 Nominal Load (NL)

75 NASA Provided Supplies

78 Late Load (LL)

83 Imagery

85 Operations

89 MIDAS Inventory Tracking Report (MITR)

PRR [CMC] (HW OD at Packing Facility (NL)-2w)

Release Layouts (Baseline) [CMC] (PRR+1w)

Deliver MPR to NASA [CMC] (L-6w-2d)

HW OD at Packing Facility [CMC] (Cargo Ships to NLI (NL)-5w)

Cargo Ships to NLI [CMC] (Cargo TO to NLI (NL)-1w)

Cargo TO to NLI [CMC] (L-14d)

NASA Provided Supplies OD at Packing Facility [CMC] (NASA Provided Supplies Ships to NLI-5w)

NASA Provided Supplies Ships to NLI [CMC] (NASA Provided Supplies TO to NLI-1w)

NASA Provided Supplies TO to NLI [CMC] (L-3w)

HW OD at Packing Facility [CMC] (Cargo Ships to NLI (LL)-24d)

Cargo Ships to NLI [CMC] (Cargo TO to NLI (Unpowered) (LL)-2d)

Cargo TO to NLI (Unpowered) [CMC] (L-9h)

Cargo TO to NLI (Cold Bags) [Cold Stowage] (L-9h)

Cargo TO to NLI (Powered) [HWP] (L-9h)

Submit Pre-Flight HW Imagery [HWP] (L-2w)

Submittal through MFT for Posting on IO [NASA] (L+2w) Operations

Flight Rules (Basic) [FOD/SpaceX] (L-6m)

Flight Rules (Rev A) [FOD/SpaceX] (L-4m)

Flight Rules (Final) [FOD/SpaceX] (L-7w) MIDAS Inventory Tracking Report (MITR)

Deliver TCL and WMR to FOD and TWIG [CMC] (Cargo Ships to NLI (NL)+1w)

Deliver MITR to FOD (Interim) [CMC] (L-14d)

Legend: Progress Bar Level 1 Milestone - Level 2 Milestone -

Level 3 Milestone - Launch Milestone -

SpaceX Crew Dragon

(SSP 50489)

As of Mon 6/26/17 image42.emf

95 Cargo Return

111 Post Landing/Recovery

Deliver TCL and WMR to FOD and TWIG [CMC] (L-1d)

Deliver MITR to FOD (Final) [CMC] (L-5d)

Deliver MITR to FOD [CMC] (L+36h) Cargo Return

Request FOD to Review Return Complement and Provide Inputs [CMC] (LD-19w)

CMC Receives Inputs for Return Layouts [FOD] (Request FOD to Review Return Complement and Provide Inputs+3w)

Return PRR [CMC] (LD-14w)

Final Return Layouts Review [NASA/FOD/CMC] (LD-6.5w)

Deliver RMDP (Draft #1) [CMC] (LD-3m)

Deliver RMDP (Draft #2) [CMC] (LD-2m)

Deliver RMDP (Draft #3) [CMC] (LD-1m) (If Required)

Deliver RMDP (Draft Updates) [CMC] (UD) (If Required)

Present Prioritization of Early and Priority Items Destow at IPT [CMC] (LD-4w)

Present Prioritization of Early and Priority Items Destow at MIOCB [CMC] (LD-2w)

Export Request Approved by NASA ECR/EST for HW Returning to IPs [NASA] (LD-2w)

Deliver RMDP (Baseline Release) [CMC] (LD)

RMDP Status to MIOCB (Early) [CMC] (LD+2w) (If Required)

RMDP Status to MIOCB (Nominal) [CMC] (LD+10w) (If Required)

Deliver RMDP (As-Flown) [CMC] (LD+13w) Post Landing/Recovery

Ambient Early Destow Operations Review with HW Providers [CMC] (Early Destow HW TO to CMC-3w)

Early Destow Hardware TO to CMC [SpaceX] (LD+3h)

Early Destow Return Hardware TO to HW Providers [CMC] (LD+1d - LD+14d) image43.emf

Nominal Destow HW TO to CMC [SpaceX] (LD+3h)

Return Cargo Packing and Shipping to CMC [SpaceX] (LD+1d)

Return HW TO to HW Providers [CMC] (LD+2d) image44.emf

1 Major Milestones

21 Safety

Major Milestones

IOR [NASA] (IX-4m)

VBR [CST-100] (L-18m)

MIR [CST-100] (L-13m)

Crew Complement Definition [FOD] (L-11m)

FOR [FOD] (L-5m) (If Required)

MCR [NASA/CST-100] (L-4m)

CIR [CST-100] (L-4m)

ISS PQR [NASA/ON] (L-6w)

SORR [NASA] (L-3.5w)

IP FRR [CST-100] (L-7d)

FRR [NASA] (L-7d)

LRR [CST-100] (L-2d)

Launch (L-0)

Dock (L+1d)

Undock (L+180d)

Landing (UD+4h)

SORR (for Return) [NASA] (UD-2.5w)

FRR (for Return) [NASA] (UD-1w)

Lesson Learned [OP] (UD+90d) Safety

Deliver IBLHA to NASA (Baseline Launch) [CMC] (L-3m-1d)

Deliver IBLHA to NASA (Rev. A Launch) [CMC] (L-6w-1d)

Boeing CST-100 image45.emf

26 Time-Critical Ground Handling Requirements

31 Mission Integration (Reference Increment Template)

38 Cargo Mission Milestones

Deliver IBLHA to NASA (Baseline Return) [CMC] (L-6w-1d)

Deliver IBLHA to NASA (Rev. A Return) [CMC] (L-1.5w) Time-Critical Ground Handling Requirements (TGHR)

Present Draft TGHR at CIR [NASA] (L-4m)

Update TGHR [NASA] (L-4m to L-2m)

TGHR Review at MIOCB [NASA] (L-2.25m) (If Required)

Baseline TGHR [NASA] (L-2m) Mission Integration (Reference Increment Template)

IDRD Main Volume

IDRD Annex 1 (Manifest)

IDRD Annex 2 (On-Orbit Maintenance Plan and Operations Support)

IDRD Annex 3 (Imagery Requirements)

IDRD Annex 4 (Medical Operations)

IDRD Annex 5 (Payloads Tactical Plan)

Cargo Mission Milestones

Pressurized Cargo Complement (Preliminary) [NASA] (L-13m)

MRAD (Initial) [CST-100] (L-10m)

Pressurized Cargo Complement (Update) [NASA] (L-5m)

MRAD (Update) [CST-100] (L-3m)

Pressurized Cargo Complement (Final) [NASA] (L-6w)

MRAD (Final) [CST-100] (L-4w)

Cargo Map from NASA to CMC [NASA] (L-2w) image46.emf image4.png

46 Cargo Processing

Documentation 47 Nominal Load (NL)

49 Late Load (LL)

51 Return Cargo

55 Cargo Processing

64 Nominal Load (NL)

67 NASA Provided Supplies

Cargo Processing Documentation eLabel Request Approved [HWP] (HW OD at Packing Facility (NL)-5w) eLRODS Approved (Launch) [HWP/CMC] (HW OD at Packing Facility (NL)-4w) eLabel Request Approved [HWP] (HW OD at Packing Facility (LL)-5w) eLRODS Approved (Launch) [HWP/CMC] (HW OD at Packing Facility (LL)-4w)

Return Packing Data [HWP] (L-11w)

Return Export Submitted [HWP] (L-2w) eLRODS Approved (Return) [HWP/CMC] (LD-10w)

Return Export Approved [HWP/NASA] (LD-2w) Cargo Processing

Deliver MPR to NASA [CMC] (L-5m-2d)

Deliver HAMR [CMC] (HW OD at Packing Facility (NL)-7w)

Hardware Audit [CMC] (HW OD at Packing Facility (NL)-6w)

Release Layouts [CMC] (HW OD at Packing Facility (NL)-5w)

Release Layouts (Baseline) [CMC] (HW OD at Packing Facility (NL)-3w)

PRR [CMC] (HW OD at Packing Facility (NL)-2w)

Release Layouts [CMC] (PRR+1w)

Deliver MPR to NASA [CMC] (L-6w-2d)

HW OD at Packing Facility [CMC] (Cargo Ships to NLI (NL)-5w)

Cargo Ships to NLI [CMC] (Cargo TO to NLI (NL)-1w)

Cargo TO to NLI [CMC] (L-8w)

NASA Provided Supplies OD at Packing Facility [CMC] (NASA Provided Supplies Ships to NLI-5w)

NASA Provided Supplies Ships to NLI [CMC] (NASA Provided Supplies TO to NLI-1w) image47.emf

70 Late Load (LL)

73 Time Critical (TC)

78 Imagery

80 Operations

84 MIDAS Inventory Tracking Report

(MITR)

90 Cargo Return

NASA Provided Supplies TO to NLI [CMC] (L-3w)

HW OD at Packing Facility [CMC] (Cargo Ships to NLI (LL)-24d)

Cargo Ships to NLI [CMC] (Cargo TO to NLI (LL)-1w)

Cargo TO to NLI [CMC] (L-11d)

HW OD at Packing Facility [CMC] (Cargo Ships to NLI (TC)-2w)

Cargo Ships to NLI [CMC] (Cargo TO to NLI (Unpowered) (TC)-2d)

Cargo TO to NLI (Unpowered) [CMC] (L-17h)

Cargo TO to NLI (Cold Bags) [Cold Stowage] (L-17h)

Cargo TO to NLI (Powered) [HWP] (L-17h)

Flight Rules (Basic) [FOD/CST-100] (L-6m)

Flight Rules (Rev A) [FOD/CST-100] (L-4m)

Flight Rules (Final) [FOD/CST-100] (L-7w)

Deliver TCL and WMR to FOD and TWIG [CMC] (Cargo Ship to NLI (NL)+1w)

Deliver MITR to FOD (Interim) [CMC] (L-30d)

Deliver TCL and WMR to FOD and TWIG [CMC] (L-1d)

Deliver MITR to FOD [CMC] (L+36h) Cargo Return

Request FOD to Review Return Complement and Provide Inputs [CMC] (LD-19w) image48.emf

106 Post Landing/Recovery

CMC Receives Inputs for Return Layouts [FOD] (Request FOD to Review Return Complement and Provide Inputst+3w)

Return PRR [CMC] (LD-14w)

Final Return Layouts Review [NASA/FOD/CMC] (LD-6.5w)

Deliver RMDP (Draft Updates) [CMC] (Launch to Undock) (If Required)

Present Prioritization of Early and Priority Items Destow at IPT [CMC] (LD-4w)

Present Prioritization of Early and Priority Items Destow at MIOCB [CMC] (LD-2w)

Export Request Approved by NASA ECR/EST for HW Returning to Ips [NASA] (LD-2w)

Deliver RMDP (Baseline Release) [CMC] (LD)

RMDP Status to MIOCB (Early) [CMC] (LD+2w) (If Required)

RMDP Status to MIOCB (Nominal) [CMC] (LD+10w) (If Required)

Deliver RMDP (As-Flown) [CMC] (LD+13w)

Ambient Early Destow Operations Review with HW Providers [CMC] (Early Destow HW TO to CMC-3w)

Early Destow HW TO to CMC [CST-100] (LD+3h)

Early Destow Return HW TO to HW Providers [CMC] (LD+1d - LD+14d)

Nominal Destow HW TO to CMC [CST-100] (LD+3h)

Return Cargo Packing & Shipping to CMC [CST-100] (LD+1d)

Return HW TO to HW Providers [CMC] (LD+2d) image49.emf

1 IDRD Period

4 Launch/Depart

5 ISS Flight Program Sequence

11 Extra Vehicular Activity

(EVA)

14 Major Milestones

15 Major Milestones- Increment Specific

IDRD Period

Increment X (IX)

Increment Y (IY) Launch/Depart

ISS Flight Program Sequence

Launch

Dock

Berth

Undock

Unberth Extra Vehicular Activity (EVA)

Russian EVA #

USOS EVA #

Increment Specific

IOR [NASA] ( IX-4m)

Program Direction Letter for Preliminary OOS Development (Published) [OC] (IX-18w)

OOS (Preliminary Planning TIM) [FOD/POI/IP] (IX-16w)

OOS (Preliminary Published) [FOD/POI/IP] (IX-14w)

Program Direction Letter for Final OOS Development (Published) [OC] (IX-8w)

OOS (Final Planning TIM) [FOD/POI/IP] (IX-6w)

OOS (Final Published) [FOD/POI/IP] (IX-4w)

Increment image50.emf

27 Major Milestones - Flight Specific

37 PIER

40 ISS Flight Plan

44 Mission Integration

Program Direction Letter for OOS Update Development (Published) [OC] (IX+4w)

OOS (Update Planning Telecons) [FOD/POI/IP] (IX+6w to IX+7w)

OOS (Update Published) [FOD/POI/IP] (IX+7w)

Lessons Learned (Russian‐If needed) [OP] (Soyuz UD+60d) Flight Specific

FOR [FOD] (L-4m) (If Required)

GDR [RSC-E] - Soyuz (L-21d)

GDR [RSC-E] - Progress (L-21d) (If Required)

FRR [NASA] (L-7d) (If Required)

State Commission Review #1 [Roscosmos] (L-2w)

State Commission Review #2 [Roscosmos] (L-6h)

PIER

IX and IY PIER CR Release [NASA] (IY Comp.+4.5m)

IX and IY PIER CR at MIOCB for Approval [NASA] (IY Comp.+6m) ISS Flight Plan

MIPD CR Release (CRXXXXX) (IX-67w)

MIPD CR to MIOCB for Approval (CRXXXXX) (IX-62w)

MIPD CR to SSPCB for Approval (CRXXXXX) (IX-61w) Mission Integration image51.emf image5.wmf

45 Program Authorization

Letter

48 IDRD Main Volume

55 IDRD Annex 1 (Manifest)

56 IDRD Annex 1 (Manifest)

- Soyuz

Program Authorization Letter

PAL Call for Inputs [OP] (IX-52w) (If Required)

PAL Release [OP] (IX-43w) (If Required)

Baseline Call for Inputs [OP] (IX-43w)

CR Release (CRXXXXX) [OP] (IX-39w)

MIOCB for Approval (CRXXXXX) [OP] (IX-30w)

Rev A Call for Inputs [OP] (IX-19w)

CR Release (CRXXXXX) [OP] (IX-13w)

MIOCB to Support SORR (CRXXXXX) [OP] (IX-4.5w)

IDRD Annex 1 (Manifest) - Soyuz

Present L-4.5m U.S. Cargo List at MIOCB for Approval [OP/NASA] (L-4.5m)

Send L-4.5m U.S. Cargo List Request to RSC-E [OP] (L-4.5m)

Present L-2m U.S. Cargo List at MIOCB for Status [OP] (L-2.25m)

Present L-2m U.S. Cargo List at MIOCB for Approval [OP/NASA] (L-2m)

Send L-2m U.S. Cargo List to RSC-E [OP] (L-2m)

Rec. RSC-E Input [OP] (L-1.5m)

Release IDRD Annex 1 BL Manifest [OP] (L-2m)

IDRD Annex 1 Haz/Tox Codes [OP] (L-2m)

IDRD Annex 1 BL Approval at MIOCB [OP/NASA] (L-1m)

Rec. RSC-E As Launch Manifest Inputs [OP] (L+2w) image52.emf

81 IDRD Annex 1 (Manifest)

- Progress

Release IDRD Annex 1 As Launch Manifest [OP] (L+4w)

IDRD Annex 1 As Launch Manifest Approval at MIOCB [OP/NASA] (L+2m)

Present UD-3.5m Return U.S. Cargo List at MIOCB for Approval [OP/NASA] (UD-3.5m)

Send UD-3.5m Return U.S. Cargo List to RSC-E [OP] (UD-3.5m)

Present UD-2m Return U.S. Cargo List at MIOCB for Status [OP] (UD-2.25m)

Present UD-2m Return U.S. Cargo List at MIOCB for Approval [OP] (UD-2m)

Send UD-2m Return U.S. Cargo List to RSC-E [OP] (UD-2m)

Release IDRD Annex 1 Return Manifest [OP] (UD-2m)

Rec RSC-E Return Manifest Input [OP] (UD-40d)

IDRD Annex 1 Return Manifest Technical Concurrence at MIOCB [OP/NASA] (UD-1m)

Rec. RSC-E Post Flight Manifest Inputs [OP] (UD+3w)

Post Flight IDRD Annex 1 CR Release [OP] (UD+2.5m)

Post Flight IDRD Annex 1 CR Package to OC2 [OP] (UD+3.5m)

Post Flight IDRD Annex 1 CR Package to MIOCB OSB [OP] (UD+4m) IDRD Annex 1 (Manifest) - Progress

Present L-4.5m U.S. Cargo List at MIOCB for Approval [OP/NASA] (L-4.5m)

Send L-4.5m U.S. Cargo List Request to RSC-E [OP] (L-4.5m)

Rec. RSC-E Input [OP] (L-3m)

Present L-2m U.S. Cargo List at MIOCB for Status [OP] (L-2.25m)

Present L-2m U.S. Cargo List at MIOCB for Approval [OP/NASA] (L-2m)

Send L-2m U.S. Cargo List to RSC-E [OP] (L-2m)

Release IDRD Annex 1 BL Manifest [OP] (L-2m) image53.emf

98 IDRD Annex 1 (Manifest)

- SpaceX Cargo

109 IDRD Annex 1 (Manifest)

- Orbital ATK

IDRD Annex 1 Haz/Tox Codes [OP] (L-2m)

IDRD Annex 1 BL Approval at MIOCB [OP/NASA] (L-1m)

Rec. RSC-E As Launch Manifest Inputs [OP] (L+2w)

Release IDRD Annex 1 As Launch Manifest [OP] (L+4w)

IDRD Annex 1 As Launch Manifest Approval at MIOCB [OP/NASA] (L+2m)

Rec. RSC-E Post Flight Manifest Inputs [OP] (UD+3w)

Post Flight IDRD Annex 1 CR Release [OP] (UD+2.5m)

Post Flight IDRD Annex 1 CR Package to OC2 [OP] (UD+3.5m)

Post Flight IDRD Annex 1 CR Package to MIOCB OSB [OP] (UD+4m) IDRD Annex 1 (Manifest) - SpaceX Cargo

L-3m Working Manifest to Distribution [OP] (L-3.5m)

L-3m Stowage Assessment and Working Manifest to MIOCB for Approval [OP/NASA] (L-3m)

Release IDRD Annex 1 Manifest L-6w CR [OP] (L-10w)

IDRD Annex 1 Haz/Tox Codes [OP] (L-10w)

IDRD Annex 1 Approval at MIOCB [OP/NASA] (L-6w)

L-2w Working Manifest to Distribution [OP] (L-4w)

L-2w Working Manifest to MIOCB for Approval [OP/NASA] (L-2w)

Post Flight IDRD Annex 1 CR Release [OP] (LD+3m)

Post Flight IDRD Annex 1 CR Package to OC2 [OP] (LD+4m)

Post Flight IDRD Annex 1 CR Package to MIOCB OSB [OP] (LD+4.5m) IDRD Annex 1 (Manifest) -…