------------------------------------------ ----------------------------------------------------
  ISS Payload Integration Template           

  International Space Station Program        

  Revision C                                 

  Type 1 -- Approved by NASA                 

  September 2007                             

  This document contains information that    
  falls under the jurisdiction of the U.S.   
  Department of Commerce Export              
  Administration Regulations, 15 CFR         
  730-774, and is classified as EAR99. The   
  export, re-export or re-transmission of    
  this document or any of the data contained 
  therein in violation of the Export         
  Administration Regulations or other        
  applicable U.S. export control laws and    
  regulations is strictly prohibited.        
  (HSV-07-0126)                              

  National Aeronautics and Space             ![](media/image1.wmf){width="1.2493055555555554in"
  Administration\                            height="0.9854166666666667in"}
  International Space Station Program\       
  Johnson Space Center\                      
  Houston, Texas NAS15-10000 (F-MI-08)       
  ------------------------------------------ ----------------------------------------------------

REVISION AND HISTORY PAGE

  ------ ------------------------------------------------------- ----------
  Rev.   Description                                             Pub. Date

  \-     Initial Release (Reference per SSCD 002654, EFF.        10-26-00
         10-06-00)                                               

  A      Revision A (Reference per SSCD 006037, EFF. 09-11-02)   10-21-02

  B      Revision B (Reference per SSCD 007991, EFF. 10-01-03)   10-09-03

         This is the first release on IPIC.                      

  C      Revision C (Reference SSCD 010342, EFF. 09-25-07)       10-19-07

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 
  ------ ------------------------------------------------------- ----------

*ERU: /s/ Mary C. Nooney 10-19-07*

INTERNATIONAL SPACE STATION PROGRAM

iss payload integration template

PREFACE

This document is the program definition of program milestones, products,
and deliveries. The schedule template dates assure the payload
integration process is planned in a timely manner. The integration
template is defined and organized in terms of the following functional
areas: Payload Developer (PD), Research and Payload Mission Integration,
Payload Engineering Integration (PEI), Payload Software Integration,
Payload Operations Integration Function (POIF), and Kennedy Space Center
(KSC) Integration. The payload milestone chronologies contained in
Section 3 and the generic schedule templates contained in Appendix D are
each organized in accordance with these functional areas.

  ---------------- -- -------------------------------------- -- ------------
  APPROVED BY:        /s/ William R. Jones II                   9-25-07

                      William R. Jones II\                      Date
                      Manager, ISS Payload Office\              
                      National Aeronautics and Space            
                      Administration                            

                                                                
  ---------------- -- -------------------------------------- -- ------------

INTERNATIONAL SPACE STATION PROGRAM

iss payload integration template

CONCURRENCE

September 2007

  ----------------- ----------------------------------- --- --------------
  PREPARED BY:      M. Nagy                                 IPI MI

                    Payload Integration Template Book       ORGN
                    Manager                                 

                                                            

                    /s/ M. Nagy                             9/12/07

                    SIGNATURE                               DATE

                                                            

  CONCURRED BY:     G. Esquivel                             OZ2

                    Payload Mission Integration And         ORGN
                    Planning Manager                        

                                                            

                    /s/ A. Gerald Esquivel                  10/16/07

                    SIGNATURE                               DATE

                                                            

  Boeing DQA:       Annette Lehman                          Boeing/GCS

                    Document Quality Assurance              ORGN

                                                            

                    /s/ Annette Lehman                      9/12/07

                    SIGNATURE                               DATE
  ----------------- ----------------------------------- --- --------------

INTERNATIONAL SPACE STATION PROGRAM

iss payload integration template

LIST OF CHANGES

September 2007

All changes to paragraphs, tables, and figures in this document are
shown below:

  ------------------------------------------------------------------------
  SSCD              Entry Date         Change           Paragraph(s)
  ----------------- ------------------ ---------------- ------------------
  SSCD 002654       September 2000     Baseline         All

  SSCD 006037       October 2002       Revision A       All

  SSCD 007991       October 2003       Revision B       All

  SSCD 010342       September 2007     Revision C       All

                                                        
  ------------------------------------------------------------------------

TABLE OF CONTENTS

PARAGRAPH PAGE

[1.0 INTRODUCTION 1-1](#introduction)

[1.1 PURPOSE 1-1](#purpose)

[1.2 SCOPE 1-1](#scope)

[1.3 PRECEDENCE 1-1](#precedence)

[1.4 delegation of authority 1-2](#delegation-of-authority)

[2.0 documents 2-1](#documents)

[2.1 applicable documents 2-1](#applicable-documents)

[2.2 reference documents 2-2](#reference-documents)

[3.0 iss payload milestone definitions
3-1](#iss-payload-milestone-definitions)

[3.1 ISS PAYLOAD DEFINITIONS 3-1](#iss-payload-definitions)

[4.0 ISS PAYLOAD MILESTONE CHRONOLOGY
4-1](#iss-payload-milestone-chronology)

[5.0 INTERNATIONAL PARTNER LAUNCH VEHICLE UNIQUE MILESTONES
5-1](#international-partner-launch-vehicle-unique-milestones)

[5.1 Automated Transfer Vehicle (ATV) Launch Milestones
5-1](#automated-transfer-vehicle-atv-launch-milestones)

[5.2 RUSSIAN Vehicle (RV) Launch Milestones
5-3](#russian-vehicle-rv-launch-milestones)

[5.3 HII Transfer Vehicle (HTV) Launch Milestones
5-5](#hii-transfer-vehicle-htv-launch-milestones)

APPENDIces

A ACRONYMS AND ABBREVIATIONS A-1

B GLossary of terms B-1

C open work C-1

D SCHEDULE TEMPLATES D-1

TABLEs

TABLE PAGE

[3.1-1 Iss payload milestoneS AND definitions (16 pages)
3-2](#__RefHeading___Toc177265749)

[4.0-1A pAYLOAD DEVELOPER MILESTONE CHRONOLOGY payload\
development phase (3 PAGES) 4-3](#__RefHeading___Toc177265750)

[4.0-1B pAYLOAD DEVELOPER MILESTONE CHRONOLOGY iss mission\
integration phase (10 pages) 4-6](#__RefHeading___Toc177265751)

[4.0-2 PAYLOAD MISSION INTEGRATION MILESTONE CHRONOLOGY (7 pages)
4-16](#__RefHeading___Toc177265752)

[4.0-3 PAYLOAD ENGINEERING INTEGRATION MILESTONE CHRONOLOGY\
(3 pages) 4-23](#__RefHeading___Toc177265753)

[4.0-4 PAYLOAD SOFTWARE INTEGRATION MILESTONE CHRONOLOGY
4-26](#__RefHeading___Toc177265754)

[4.0-5 PAYLOAD OPERATIONS INTEGRATION FUNCTION MILESTONE\
CHRONOLOGY (3 pages) 4-27](#__RefHeading___Toc177265755)

[4.0-6 KENNEDY SPACE CENTER INTEGRATION MILESTONE CHRONOLOGY\
(2 pages) 4-30](#__RefHeading___Toc177265756)

[5.1-1 ATV Milestones (2 pages) 5-2](#__RefHeading___Toc177265757)

[5.2-1 RUSSIAN VEHICLE MILESTONES 5-4](#__RefHeading___Toc177265758)

[5.3-1 HII VEHICLE MILESTONES 5-5](#__RefHeading___Toc177265759)

# INTRODUCTION

## PURPOSE

The purpose of this document is to establish and define the generic
integration schedule templates that are used to produce payload-unique
integration schedules and payload flight complement integration
schedules.

This document provides the single authoritative source for all
International Space Station (ISS) payload integration milestone template
dates. This document serves as a reference source for ISS Payload
Program implementing organizations for their respective integration
product development schedules and corresponding processes. This document
also provides the Payload Developer (PD) community a reference source
for all integration submittals required by the ISS Payload Program.

Schedule templates in this document reflect integration data submittals
from the PDs, ISS Payload Program product deliveries, and major
milestones such as Program-level reviews. Schedule templates are used to
ensure that the payload integration process can be completed
successfully and in a timely manner. The Generic Payload Integration
Manager (PIM) Schedule Templates are established by payload class
(Pressurized, Small, Subrack, and Attached) and reflect detailed
activities that are relevant to managing the successful mission
integration of a given payload. The Generic Payload Mission Integration
Team (PMIT) Schedule Template reflects a high level rollup of milestones
that are relevant to managing the overall integration of the payload
flight complement.

## SCOPE

The templates and descriptive material contained in this document cover
all ISS payload integration activities performed by the NASA ISS Payload
Office for NASA sponsored or bartered payloads that are launched on the
Space Shuttle vehicle. Templates are applicable regardless of whether
the payload will operate in the United States Laboratory (US Lab) or in
an International Partner (IP) provided research module.

This document covers the integration template and products required for
integration of payloads when launched on Space Shuttle, Russian Vehicles
(Soyuz, Progress), European Space Agency (ESA) Automated Transfer
Vehicle (ATV), and Japan Aerospace Exploration Agency (JAXA) H-II
Transfer Vehicle (HTV).

## PRECEDENCE

Actual payload-specific or flight-specific implementation schedules may
deviate from the templates in this document. However, if there are
discrepancies between other documentation and SSP 57057, Revision C,
with regard to the schedule milestone template dates, the following
order of precedence shall be used:

A.  For ISS Program milestones, SSP 50489, ISS Mission Integration
    Template, shall take precedence.

B.  For Space Shuttle Program milestones, JSC 25187, Appendix A, Flight
    Production Generic Templates, Shuttle Templates, shall take
    precedence.

C.  \<**TBD** **1-1**\>, ATV schedule milestone reference

D.  \<**TBD** **1-2**\>, HTV schedule milestone reference

E.  SSP 57057, Revision C

## delegation of authority

This document is approved and controlled by the ISS Payload Control
Board (PCB).

# documents

## applicable documents

The documents listed in this section are applicable to the extent
specified herein. Inclusion of applicable documents does not supersede
the order of precedence identified in Paragraph 1.3 of this document.

  ------------------- ---------------------------------------------------
  document            title

  SSP 50489           ISS Mission Integration Template

  SSP-52000-IDD-ERP   Expedite the Processing of Experiments to Space
                      Station (EXPRESS) Rack Payloads Interface
                      Definition Document

  SSP 52000-PVP-ERP   Generic Payload Verification Plan, Expedite the
                      Processing of Experiments to Space Station
                      (EXPRESS) Rack Payloads

  SSP 52000-PIH-WRP,  Window Observational Research Facility (WORF) Rack
  Volume III          Interface Definition Document, PIH Volume III

  SSP 52000-PIH-WRP,  Window Observational Research Facility (WORF)
  Volume IV           Generic Payload Verification Plan, PIH Volume IV

  SSP 52000-PDS       Payload Data Sets Blank Book

  SSP 52054           ISS Program Payloads Certification of Flight
                      Readiness Implementation Plan, Generic

  SSP 5410X-ANX 1     Increment Definition and Requirements Document for
                      Planning Period X, Annex 1: Station Manifest
                      (Series of Flight-Specific Station Manifests)

  SSP 57001           Pressurized Payloads Hardware Interface Control
                      Document Template

  SSP 57002           Payload Software Interface Control Document
                      Template

  SSP 57004           Attached Payload Hardware Interface Control
                      Document Template

  SSP 57072           Standard Payload Integration Agreement for ISS
                      Payloads

  JSC 25187\          Flight Production Generic Templates, Shuttle
  Appendix A          Templates
  ------------------- ---------------------------------------------------

## 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.

  -----------------------------------------------------------------------
  document            title
  ------------------- ---------------------------------------------------
  SSP 50108           Certification of Flight Readiness Process Document

  SSP 50146\          NASA/RSA Bilaterial S&MA Process Requirements for
  Revision A          International Space Station

  SSP 50200-01        Station Program Implementation Plan, Volume 1:
                      Station Program Management Plan

  SSP 50200-02        Station Program Implementation Plan, Volume 2:
                      Program Planning and Manifesting

  SSP 50253           Operations Data File Standards

  SSP 50254           Operations Nomenclature

  SSP 50313           Display and Graphics Commonality Standard

  SSP 50431           Space Station Program Requirements for Payloads

  SSP 52000-PIH-WRP   Window Observational Research Facility (WORF) Rack
  Volume VI-A         Payload Configuration Data Set Definition,\
                      PIH Volume VI-A

  SSP 54504           Increment Definition and Requirements Document,
                      Annex 5: Payload Tactical Plan Blank Book

  SSP 57000           Pressurized Payloads Interface Requirements
                      Documents

  SSP 57003           Attached Payload Interface Requirements Documents

  SSP 57008           Unique Pressurized Payload Non-Rack Interface
                      Control Document Template

  SSP 57059           Standard Payload Integration Agreement for
                      Pressurized Payloads

  SSP 57061           Standard Payload Integration Agreement for Attached
                      Payloads

  SSP 57063           Standard Payload Integration Agreement for Small
                      Pressurized Payloads

  SSP 57064           Payload Integration Agreement Blank Book for Small
                      Pressurized Payloads

  SSP 57066           Standard Payload Integration Agreement for
                      EXPRESS/WORF Rack Payloads

  OPS-IDD-0-200       ATV Dry Cargo Integration Interface Definition
                      Document

  P32928-103\         Requirements for International Partner Cargoes
  (Russian Document)  Transported on Russian Progress and Soyuz Vehicles

  POIF-1004           Payload Operations Integration Center, Payload
                      Operations Handbook Volume 1: Pre-/Post-Increment
                      Operations

  POIF-2001           U.S. Payload Operations Data File Management Plan

  NSTS/ISS 13830      Payload Safety Review and Data Submittal
                      Requirements for Payloads Using the Space Shuttle
                      and International Space Station

  D683-35491-1        EXPRESS Rack Payload Configuration Data Set
                      Definition

  ESA-ATV-PR-13830\   ATV Pressurized Payload/Cargo Safety Certification
  July 2004           Process
  -----------------------------------------------------------------------

# iss payload milestone definitions

## ISS PAYLOAD DEFINITIONS

For the purposes of this document, the term "milestone" is used to
define the completion of a product, activity or process. A milestone may
identify the submittal of a data item, the delivery, or shipment of a
hardware item, the development of integration or operations product, or
the completion of a Program or payload review. Table 3.1-1, ISS Payload
Milestones and Definitions, defines each of the milestones used in the
ISS Payload Integration Templates and provides definitions for
clarification. The milestones acronyms are listed in alphabetical order
to facilitate search. Table 3.1-1 includes the following column headers:

Line Number: The line number is assigned to each milestone acronym and
is used to identify the milestone during documentation reviews, specific
schedule development, and internal coordination.

Milestone Acronym: The milestone acronym is the short-hand identifier
used in the generic payload integration templates and on the flight and
payload specific schedules.

Milestone Definition: The milestone definition provides a brief
description of the milestone acronym including reference to applicable
documentation that provides a more detailed description.

  -----------------------------------------------------------------------------------------------------
  []{#__RefHeading___Toc177265749                    
  .anchor}table 3.1-1 Iss payload                    
  milestoneS AND definitions (16                     
  pages)                                             
  --------------------------------- ---------------- --------------------------------------------------
  Line \#                           Milestone        Milestone Definition
                                    Acronym          

  1                                 Assembly &       Assembly & Installation (A&I) Drawings\
                                    Installation     Part of the Drawing Data Set, the Assembly and
                                    (A&I) Drawings   Installation Drawing shows the top assembly and
                                                     complete information necessary to install the
                                                     payload for launch. This drawing includes a
                                                     listing of items to be installed by part number
                                                     and nomenclature and quantity, locating dimensions
                                                     and associated tolerances, required torques, and
                                                     detail definition of any special requirements.
                                                     Payload Developers provide the payload Main Unit
                                                     Top Assembly drawing to PDL for use by KSC and PEI
                                                     in developing integrated rack launch assembly and
                                                     installation drawings, ECLs, or integrated rack
                                                     level on-orbit drawings. See SSP 52000-PDS.

  2                                 Acoustic Data    Acoustic Data (Middeck)\
                                    (Middeck)        Results from Acoustic Testing

  3                                 BR KSC           Bench Review Kennedy Space Center\
                                                     Members of the Astronaut Office (crew members or
                                                     designee) review cargo/stowage in its flight
                                                     configuration during Bench Reviews (BR). Bench
                                                     reviews are scheduled at KSC according to various
                                                     MPLM/Node integration milestones. Hardware
                                                     providers coordinate their shipments to KSC to
                                                     meet processing schedules for turnover for the
                                                     appropriate bench reviews based on rack
                                                     integration, stowage location, and/or time. In
                                                     addition, the ISS Program may also have pre-packed
                                                     BR for other modules (ATV/HTV) at KSC and then
                                                     ship payload and/or stowage items to final stowage
                                                     integration facility.

  4                                 BR JSC           Bench Review Johnson Space Center\
                                                     Members of the Astronaut Office (crew members or
                                                     designee) review cargo/stowage in its flight
                                                     configuration during BRs. All hardware on Russian
                                                     Flights and hardware stowed in the Middeck are
                                                     nominally conducted at JSC. In addition, the ISS
                                                     Program may also have pre-packed bench review for
                                                     other modules (MPLM/NODE/ATV/HTV) at JSC and then
                                                     shipped to final stowage integration facility.

  5                                 C&DH DS          Command and Data Handling Data Set\
                                                     C&DH DS is a segregation of PDL data that defines
                                                     the flight unique software interface requirements
                                                     between Integrated Payload Systems and ISS flight
                                                     data handling elements. See SSP 57002, Payload
                                                     Software Interface Control Document Template.

  6                                 CCCD             Crew Compartment Configuration Drawings\
                                                     This is a SSP product to identify the MDK layout
                                                     of all the hardware to review and support the
                                                     CCCR.

  7                                 CCCR             Crew Compartment Configuration Review\
                                                     This is a SSP review of the crew compartment
                                                     configuration at the Integrated Product Team
                                                     meeting.

  8                                 CCCR Freeze      Crew Compartment Configuration Review Freeze\
                                                     The Middeck manifest requirements will be frozen
                                                     to support preparation of the CCCR products which
                                                     include the video, data and electrical plug-in
                                                     plans in the Flight Requirements Document and
                                                     CCCD. After CCCR, manifest changes must be
                                                     approved by the SSP/ISS Program JPRCB if not
                                                     classified as a mission success requirement.

  9                                 CDR              Critical Design Review\
                                                     Most Payloads Projects as part of their hardware
                                                     development effort will conduct a CDR when their
                                                     hardware design reaches 90% maturity. The CDR
                                                     represents completion of the classical Project
                                                     Development Cycle Phase C. The CDR demonstrates a
                                                     "build-to" detailed design baseline to fabricate,
                                                     integrate and verify. The ISS Program provides a
                                                     draft Interface Control Document in support of a
                                                     CDR. The ISS Program also reviews the CDR data
                                                     package for implications to ISS payload
                                                     integration, and to provide verification guidance
                                                     to the PD.

  10                                CEIT             Crew Equipment Interface Test\
                                                     CEIT allows the astronauts to interface with the
                                                     flight hardware in its flight-like operational
                                                     configuration with cabling. This provides the crew
                                                     with the opportunity to check tools and the
                                                     payload interfaces and become familiar with the
                                                     hardware.

  11                                CIR Shuttle      Cargo Integration Review -- Shuttle\
                                                     This review is conducted by the SSP Office to
                                                     ensure that the ISS cargo elements manifested on a
                                                     given Shuttle mission can be accommodated within
                                                     the STS flight and ground capabilities. The
                                                     Shuttle CIR is the major cargo-related review at
                                                     which the ISS concurs with the integration and
                                                     implementation of their requirements at the
                                                     cargo/flight level.

  12                                CIR ATV          Cargo Integration Review -- ATV\
                                                     This review is conducted by the ESA to ensure that
                                                     the cargo elements manifested on a given ATV
                                                     mission can be accommodated within the ATV flight
                                                     and ground capabilities. The ATV CIR is the major
                                                     cargo-related review at which the ESA concurs with
                                                     the integration and implementation of their
                                                     requirements at the cargo/flight level.

  13                                CIRD Shuttle     Cargo Integration Review Dry Run -- Shuttle\
                                                     Conducted 3 weeks prior to CIR to identify any
                                                     last issues that will possibly need to be worked
                                                     at the CIR. Verify CIR electronic data package is
                                                     complete for distribution.

  14                                CoFR OZ2         OZ2 Certification of Flight Readiness
                                    Pre-Coord Review Pre-Coordination Review\
                                                     Primary objective is to review and concur with the
                                                     CoFR letter including the schedule and identify
                                                     CoFR responsibilities between IP/P and OZ

  15                                CoFR Bi-Lateral  OZ2 Bi-lateral CoFR Pre-Coordination Review\
                                    Pre-Coord Review Primary objectives is for OZ and IP/P to review
                                                     and concur with the CoFR letter including any
                                                     product exchanges/schedules and determine
                                                     participation requirements to support IP/P and OZ
                                                     CoFR meeting

  16                                CoFR Release OZ  Release OZ Certification of Flight Readiness
                                    Instruction      Instruction Letter\
                                    Letter           CoFR instruction letter defines CoFR endorsement
                                                     requirements and schedule for a given flight,
                                                     stage, or increment. Launch, on-orbit, and
                                                     return/disposal payloads are identified. Included
                                                     are PIRNs identifying ISS Program applicable
                                                     requirement changes.

  17                                CoFR OWTL and    Certification of Flight Readiness Open Work
                                    LPA Inputs Due   Tracking Log and Launch Package Assessment Inputs
                                                     Due\
                                                     OZ2 conducts a program-wide review of all CoFR
                                                     open work to focuses and identify any potential
                                                     issues/threats and CoFR exceptions. Emphasis is
                                                     made to prioritize work to close open endorsements
                                                     prior to OZ SORR CoFR.

  18                                CoFR OZ2 OWTL &  OZ2 Certification of Flight Readiness Open Work
                                    LPA Review       Tracking Log and Launch Package Assessment Review\
                                                     This review is only required if requested by the
                                                     OZ Manager or if there is significant
                                                     issues/threats to report to OZ management.

  19                                CoFR OZ OWTL and OZ Certification of Flight Readiness Open Work
                                    LPA Review       Tracking Log and Launch Package Assessment Review\
                                                     Certifying organizations specify open work
                                                     required to certify all sub-endorsements as
                                                     specified in SSP 52054. Identify any open items
                                                     that would constrain or prohibit cargo
                                                     integration/Shuttle rollout and provide a recovery
                                                     plan and go/no go recommendation to proceed.

  20                                CoFR (ISS        International Space Station Program Certification
                                    Program) LPA Dry of Flight Readiness Launch Package Assessment Dry
                                    Run and LPA      Run and Launch Package Assessment\
                                                     The Launch Package Management Team conducts the
                                                     LPA Dry Run to prepare for the ISS Program LPA at
                                                     the Space Shuttle Payload Control Board and for
                                                     flights with International Partner elements, the
                                                     LPA will be conducted at a joint Space Shuttle
                                                     Control Board/SSPCB.\
                                                     The LPA addresses remaining open work, issues and
                                                     constraints to ensure that there are no
                                                     anticipated problems within ISS that would
                                                     preclude the Scheduled delivery of payload to the
                                                     pad. Including each certifying organizations
                                                     providing a recommendation to proceed.\
                                                     The FPM is responsible for developing the
                                                     presentation using the initial OWTL and LPA inputs
                                                     data provided by the certifying organizations.

  21                                CoFR Endorsement OZ Certificate of Flight Readiness Endorsement
                                    Packages Due     Packages Due\
                                                     All OZ certifying organizations are required to
                                                     submit a CoFR package per requirements referenced
                                                     in SSP 52054.\
                                                     A nominal CoFR package includes a CoFR endorsement
                                                     checklist OWTL, exceptions, and certification
                                                     letter unless either the SSP 52054 or the OZ CoFR
                                                     instruction letter identifies a reduction of these
                                                     requirements.

  22                                CoFR IP/ IPM     Certificate of Flight Readiness IP/IPM Readiness
                                    Readiness Review Review\
                                                     Each IP/P conducts a CoFR review with their
                                                     management to assure their readiness to support
                                                     the ISS Program SORR.\
                                                     OZ participation is only required if there are
                                                     issues or open work associated with OZ activities
                                                     that would prevent an IP/P from satisfying any of
                                                     the endorsements codes.

  23                                CoFR (OZ)        OZ Certificate of Flight Readiness Multilateral
                                    Multilateral     Package Review\
                                    Package Review   OZ CoFR Review to approve the SORR charts
                                                     developed by the IPM and for all certifying
                                                     organizations to provide an OWTL statue in
                                                     preparations for the ISS Program SORR.

  24                                CoFR SORR        Certification of Flight Readiness Stage Operations
                                                     Readiness Review\
                                                     The SORR certifies that the Launch Package/Cargo
                                                     Element ground support facilities and personnel
                                                     are ready to support the flight stage, and/or
                                                     increment. Additionally, it certifies the
                                                     readiness of the on-orbit stage configuration to
                                                     accept the Launch Package/Cargo Element and
                                                     readiness for on-orbit increment operations.

  25                                Command &        Command and Telemetry Databases\
                                    Telemetry        Contain the definitions needed to decom system and
                                    Databases        payload data on the ground; and to allow users to
                                                     update and send commands. The payload portion is
                                                     built from the information provided in the C&DH
                                                     data Set. See SSP 57002.

  26                                Drawing DS       Drawing Data Set\
                                                     The Drawing Data Set controls the format and
                                                     content of selected Payload Engineering
                                                     Integration, and Configuration data required from
                                                     Payload Developers to develop complement-level
                                                     configuration drawings for the integrated
                                                     International Standard Payload Rack (ISPR) and
                                                     EXPRESS Rack. ISS Payload Engineering Integration
                                                     uses the On-Orbit Operational Configuration
                                                     Drawings to create Integrated Laboratory Module
                                                     Configuration Drawings for the ground control team
                                                     at Payload Operations and the Integration Facility
                                                     (POIF). The ground control team uses these
                                                     drawings to visualize what the planned payload
                                                     configurations are during real-time operations.
                                                     POIF uses the On-Orbit Operational Configuration
                                                     Drawings to assist in building Payload Crew
                                                     Procedures The configuration data is used to
                                                     configure the payload during all phases of flight,
                                                     including ascent, on-orbit, and return. See SSP
                                                     52000-PDS, Payload Data Sets Blank Book.

  27                                ECW              Export Control Worksheet,\
                                                     JSC Form 1724. Submitted to NASA, filed with USA
                                                     Commerce Department, requesting approval for the
                                                     Payload Developer (PD) to ship hardware out of the
                                                     USA and in to a specific country.

  28                                EIRR             EXPRESS Integration Readiness Review\
                                                     The purpose of the EIRR is to conduct an
                                                     assessment of all mission related systems of the
                                                     experiment launch package to determine the
                                                     readiness of the package to be integrated into the
                                                     EXPRESS carrier. The data presented will be
                                                     sufficient to validate the required certification
                                                     that proves the experiment systems are ready for
                                                     integration and on-orbit operations.

  29                                EMC Data         Electromagnetic Compatibility Data\
                                                     EMC RF Data is results from electromagnetic
                                                     interference and compatibility analysis.\
                                                     EMC Test Data is test results from electromagnetic
                                                     compatibility testing.

  30                                EMC Thermal      Electromagnetic Compatibility Thermal Blanket
                                    Blanket Data     (Cargo Bay Payload)\
                                    (Cargo Bay       Results from Electromagnetic compatibility testing
                                    Payload)         with the thermal blanket on the hardware item.

  31                                Engineering      Engineering Configuration List (ECL)\
                                    Configuration    Scoped payload hardware and drawing release
                                    List (ECL)       definition (as-designed configuration) derived
                                                     from the most current payload design drawings
                                                     uploaded to PDL and the PDL ECL Report. Payload
                                                     Developers provide hardware data and design
                                                     drawings to PDL for their manifested payload
                                                     hardware and embedded ORUs. PEI provides the
                                                     comprehensive ECL which incorporates the
                                                     as-designed configuration of all payloads for a
                                                     given flights. See SSP 52000-PDS.

  32                                Engineering      Element-Level Engineering Analysis Report\
                                    Stage Analysis   The Payload Element-Level Engineering Analysis
                                    Report           Report documents the stage-specific results of
                                                     payload complement compatibility analysis for the
                                                     specified element of the ISS, in response to the
                                                     verification requirements of the Payload
                                                     Verification Program Plan (PVPP).

  33                                EPAS             ETOV Payload Activity Summary\
                                                     The EPAS defines the ETOV Payload Planning
                                                     Requirements to the Shuttle FAOs for development
                                                     of the Flight Plan.

  34                                ETOV Payload     Earth-to-Orbit Vehicle Payload Procedures\
                                    Procedures       ETOV procedures are used for payload
                                                     operations/monitoring during Shuttle
                                                     ascent/descent and payload activities during
                                                     docked phase of operations including research
                                                     hardware transfer to/from ISS. The procedures
                                                     reside in U.S. SODF.

  35                                Export Control   Export Control Letter\
                                    Letter           Per ISS Payload Program Policy and the Standard
                                                     PIA requirements, an export control classification
                                                     letter for the payload is required of the Payload
                                                     Developer or sponsoring organization at the
                                                     beginning of the payload integration process. The
                                                     PIM will request this letter from the Payload
                                                     Developer soon after a PIM assignment is made, and
                                                     the delivery of this letter is independent of
                                                     flight manifesting. This letter is needed for
                                                     every new payload that the ISS Payload Office will
                                                     integrate. The export control letter will identify
                                                     to the ISS Program the export classification of
                                                     the payload hardware, software, technical data,
                                                     and payload project supporting documentation.

  36                                EXPRESS/ WORF    The EXPRESS/WORF Compatibility Analysis Report\
                                    Compatibility    The report is used to show compatibility of the
                                    Analysis Report  integrated EXPRESS/WORF racks/payloads with the
                                                     applicable requirements in SSP 57000, Pressurized
                                                     Payloads Interface Requirements Document, as
                                                     specified in the EXPRESS Interface Control
                                                     Documents. The report documents the rack-level
                                                     payload resource requirements for each stage and
                                                     provides input to the element-level Stage
                                                     Analysis.

  37                                FRD              Flight Requirements Document\
                                                     The document defines authorized requirements to be
                                                     implemented on specific flights.

  38                                FOR              Flight Operations Review\
                                                     This review is conducted by MOD for the SSP and
                                                     ISS Program Offices to ensure that the flight
                                                     products to be used during real-time operations
                                                     between the Space Shuttle and ISS meet ISS and SSP
                                                     requirements for accomplishment of the mission.

  39                                FPSR             Flight Planning and Stowage Review\
                                                     This review baselines crew activities, crew
                                                     compartment, and cargo bay stowage. It marks the
                                                     final opportunity/freeze point to add powered MDK
                                                     payloads or standard payload bay GAS payloads to
                                                     the flight.

  40                                FR Annex         Flight Rules Annex\
                                                     The FR Annex documents pre-planned responses
                                                     designed to minimize the need to develop real-time
                                                     decisions in response to off‑nominal situations
                                                     that occur during mission operations.\
                                                     The FR Annex also documents the authority and
                                                     responsibility of all organizations involved in
                                                     the conduct of mission operations, including the
                                                     IP mission control centers, POIC, engineering
                                                     support functions, and the Mission Management
                                                     Team. The FR Annex, Volume A contains the Space
                                                     Shuttle generic rules. The FR Annex, Volume B will
                                                     contain the generic ISS rules. The FR Annex,
                                                     Volume C will contain generic joint ISS and
                                                     Shuttle rules.\
                                                     Increment-specific flight rules will contain
                                                     flight rules specific to a given increment
                                                     activity or a joint ISS and Shuttle mission. A
                                                     single annex will contain increment-specific rules
                                                     for Volumes A, B, and C.\
                                                     The Increment-specific flight rules are submitted
                                                     by POIF to JSC MOD to support FOR.

  41                                FRR              Flight Readiness Review\
                                                     The purpose of the FRR is to conduct an assessment
                                                     of all mission-related flight and ground systems
                                                     to determine the readiness to support the upcoming
                                                     flight. NASA, NASA contractors, and IP
                                                     representatives will certify readiness in their
                                                     areas of responsibility. The data presented during
                                                     the review will be sufficient to validate, in
                                                     unambiguous terms, the required certification that
                                                     proves the systems are ready for flight and
                                                     on-orbit operations.

  42                                FSDP             Flight Safety Data Package\
                                                     Technical description of payload flight hardware
                                                     and its operation. The data package includes
                                                     definition of hazards, hazard controls, and
                                                     verification. The Payload Developer submits the
                                                     FSDP.

  43                                FSR              Flight Safety Review\
                                                     The flight safety review is conducted for all
                                                     payloads and includes hazard analyses to
                                                     systematically and objectively identify all
                                                     hazards and hazard causes inherent in the design
                                                     and flight operations, to evaluate controls, and
                                                     to assess methods used to verify hazard controls.
                                                     The integrated on-orbit safety encompasses both
                                                     crew and vehicle safety. There are three phases of
                                                     FSRs: Phase 0 /1, Phase II, and Phase III.

  44                                GCP Book         Ground Command Procedure Book\
                                                     The Ground Command Procedures Book contains
                                                     step-by-step instructions for the POIC Cadre to
                                                     control and monitor payloads and the ISS systems
                                                     supporting those payloads. The Ground Command
                                                     Procedures Book consists of multiple volumes. The
                                                     Ground Command Procedures Book Volume 3 is for
                                                     payloads and is updated as required due to changes
                                                     in the payload compliment onboard. The other
                                                     volumes are also updated as needed. The Ground
                                                     Command Procedures Book is controlled by the
                                                     U.S.PODFCB.

  45                                GL&C             Guidelines and Constraints\
                                                     The Payload Operations GL&C Report documents the
                                                     stage element-level (including EXPRESS/WORF)
                                                     operational restrictions for payloads located in
                                                     the specified element of the ISS. These are
                                                     derived from the Payload Element-Level Engineering
                                                     Analysis Report.

  46                                GPVP             Generic Payload Verification Plan (EXPRESS/WORF
                                                     Subracks only)\
                                                     The GPVP defines the complete set of payload
                                                     verification requirements and provides
                                                     instructions and guidelines for verifying
                                                     interface compatibility and safety of as-built
                                                     hardware and software for payloads to be placed on
                                                     board the ISS. The requirements associated with
                                                     the verification plan are identified in the
                                                     Interface Definition Document (IDD). The GPVP also
                                                     provides the required verification data and
                                                     template dates for those submittals.

  47                                GSDP             Ground Safety Data Package\
                                                     Technical description of Ground Support Equipment
                                                     (GSE) and its usage during ground processing. The
                                                     data package includes definition of hazards hazard
                                                     controls. The Payload Developer submits the GSDP.

  48                                GSR              Ground Safety Review\
                                                     The GSR process is conducted for the cargo
                                                     elements, IP cargo elements, experiments, and all
                                                     GSE/non-GSE planned for ground processing at KSC.
                                                     There are three phases of GSRs: Phase 0/I, Phase
                                                     II, and Phase III.

  49                                HFIT Hardware    Human Factors Integrated Test Hardware Evaluation\
                                    Evaluation       Evaluate the flight hardware requirement
                                                     applicability against SSP 57000, with respect to
                                                     Human Factors.\
                                                     The Human Factors Implementation Team (HFIT)
                                                     provides feedback to the PD on requirements that
                                                     have possible exceptions, list them in the
                                                     internal forms and provides recommended closure of
                                                     these requirements violations. Issues Certified of
                                                     Compliance (CoC) to complete Payload Engineering
                                                     Integration (PEI) requirement verifications.

  50                                HVR              Hardware Verification Review\
                                                     An internal ISS review coordinated by the Cargo
                                                     Coordination function to verify the completion of
                                                     cargo requirements (imagery, IMS bar code,
                                                     Operations Nomenclature, labeling, paperwork)
                                                     prior to the Bench Review.

  51                                H/W Audit        Hardware Audit\
                                                     A review conducted by the Launch Package
                                                     Management Team of the Hardware Accountability
                                                     Matrix Report (HAMR), to verify cargo requirements
                                                     completion, manifest data, and establishes on dock
                                                     delivery dates. The verified data is used to
                                                     support the development of stowage
                                                     drawings/engineering products such as SSCCD and
                                                     CCCDs.\
                                                     The Hardware Audit is typically scheduled 3 months
                                                     prior to the first bench review.

  52                                H/W ICD          Hardware Interface Control Document\
                                                     Defines the physical, functional, and
                                                     environmental interfaces of PD H/W and the ISS. At
                                                     CDR, a draft H/W ICD will be made available that
                                                     provides "design --to" interface data and
                                                     verification requirements applicability matrix. At
                                                     L-12 the H/W ICD is baselined which will contain
                                                     "mission-unique" configuration data. See SSP
                                                     57001, Pressurized Payloads Hardware Interface
                                                     Control Document Template, SSP 57004, Attached
                                                     Payload Hardware Interface Control Document
                                                     Template, SSP 57008, Unique Pressurized Payload
                                                     Non-Rack Interface Control Document Template, SSP
                                                     52000-PIH-WRP, Volume III, WORF Rack Interface
                                                     Definition Document, PIH Volume III, and SSP
                                                     52000-IDD-ERP.

  53                                ICA (MDK)        Interface Control Annex (Middeck/Orbiter Crew
                                                     Compartment)\
                                                     Interface control annex (ICA) defines payload
                                                     equipment stowed or installed in the Orbiter crew
                                                     compartment and requirements affecting interfaces,
                                                     stowage, installation, or flight crew use.

  54                                IDRD             Increment Definition and Requirements Document\
                                                     The baselined IDRD documents the assigned flight
                                                     dates; the resource and accommodation allocations
                                                     among assembly, system, and utilization; an
                                                     overview of the assembly, system, and utilization
                                                     flight and increment activities; and prioritized
                                                     requirements for execution planning of ISS Program
                                                     flight- and increment-specific objectives within
                                                     the planning period. See SSP 50489.

  55                                IDRD, Annex 1    Increment Definition and Requirements Document,
                                                     Annex 1\
                                                     The IDRD, Annex 1 includes the detailed cargo
                                                     manifest for all launch vehicles on a flight. The
                                                     baselined IDRD, Annex 1 includes cargo items,
                                                     newly manifested items, LON items, hazardous
                                                     cargo, etc. The update contains manifest data for
                                                     pre-packed items. See SSP 50489.

  56                                IDRD, Annex 5    Increment Definition and Requirements Document,
                                    PTP              Annex 5: Payload Tactical Plan\
                                                     This document provides the integrated
                                                     multi-lateral utilization input to the IDRD. The
                                                     Annex 5 PTP is an increment-specific multilateral
                                                     Payload Program plan including: research
                                                     objectives, crew training and baseline data
                                                     collection requirements, the ascent/descent
                                                     payload manifest for each flight in the increment,
                                                     the on-orbit payload complement resource
                                                     requirements, payload specific station and lab
                                                     support equipment requirements, Utilization rack
                                                     and subrack rack topologies, and inter-Partner
                                                     cross-segment resource requests. The IDRD, Annex
                                                     5: PTP provides Payload Program direction to the
                                                     Research Integration Offices, IPs, and
                                                     implementing field centers. See SSP 50489.

  57                                IDRP             Increment Definition Requirements Plan\
                                                     The IDRP contains the Planning Period overview,
                                                     major increment/flight specific objectives, and
                                                     increment resources and accommodations for
                                                     assembly, system, and utilization. OZ uses the
                                                     utilization allocations to initiate Annex 5 PTP
                                                     development. See SSP 50489.

  58                                IOR              Increment Operations Review\
                                                     The IOR is a major review between the ISS Program
                                                     and those organizational elements responsible for
                                                     executing operations planned for the increment.
                                                     The IOR will assess the preparation and status of
                                                     ISS mission operations. It will ensure that the
                                                     ground facilities and operational documentation
                                                     will be ready to support the final phase of
                                                     training for both flight and ground personnel, as
                                                     well as execute the real-time operations planned
                                                     for the increment. Those products that are
                                                     required to support crew training activities or
                                                     are required at the beginning of the increment
                                                     will be reviewed at the IOR.

  59                                IPLAT Label      The ISS Payload Label Approval Team (IPLAT)\
                                    Evaluation       IPLAT reviews and approves labels for compliance
                                                     with SSP 57000, Appendix C, for all payload
                                                     equipment that the crew will interface with during
                                                     nominal operations, planned maintenance, and
                                                     contingency operations.\
                                                     At the initial label evaluation phase, IPLAT
                                                     provides a checklist to PD documenting the
                                                     labeling requirements, which were violated as well
                                                     as recommended solutions.\
                                                     At the final label evaluation phase, IPLAT reviews
                                                     released engineering drawings/flight hardware
                                                     labeling to check that all recommended changes
                                                     were made and provides status for approval of the
                                                     label drawing. IPLAT issues JSC Form 732-ISS
                                                     Payload Label Final Disposition to complete label
                                                     verifications.

  60                                IRR              Increment Requirements Review\
                                                     Integrated review by the ISS community involving
                                                     Increment requirements, stage requirements, and
                                                     joint docked operations. This review looks at
                                                     allocations and preliminary feasibility of
                                                     implementation per each flight of the Increment.

  61                                JMST             Joint Multi-Segment Station Training\
                                                     JMST involves payload training for a crew with the
                                                     POIC (integrated simulations) and with all other
                                                     control centers (joint integrated simulations).

  62                                KSC SRDS         Kennedy Space Center Support Requirements Data
                                                     Set\
                                                     The SRDS documents the launch and landing site
                                                     advanced planning for ground processing support
                                                     requirements necessary to process a single ISS
                                                     payload through the following activities:
                                                     simulations preflight, in-flight, and post-flight
                                                     phases associated with launch and recovery on the
                                                     Space Shuttle system. This includes both hardware
                                                     and science items to be processed at the launch
                                                     and landing sites. See SSP 52000-PDS.

  63                                KSC TRDS         Kennedy Space Center Technical Requirements Data
                                                     Set\
                                                     The payload-unique technical requirement submits
                                                     are the detailed payload operations and
                                                     maintenance requirements that are to be levied on
                                                     KSC. These technical requirements are those that
                                                     KSC is to perform on a payload during prelaunch,
                                                     launch, recovery, and turnaround operations. See
                                                     SSP 52000-PDS.

  64                                Lessons Learned  Flight Lessons Learned\
                                    Flight and Stage The Flight Payload Manager (FPM) is responsible
                                                     for pulling together all ISS Payloads lessons
                                                     learned for the Increment Payload Manager (IPM) on
                                                     a particular flight. That includes hardware
                                                     integration prior to launch, during the joint
                                                     timeframe and landing.\
                                                     \
                                                     Stage Lessons Learned\
                                                     The Increment Payload Engineer (IPE) is
                                                     responsible for pulling together all ISS Payloads
                                                     lessons learned for the Increment Payload Manager
                                                     (IPM) on a particular stage.

  65                                Main Unit Top    Main Unit Top Assembly Drawing, Subrack Payload\
                                    Assy Drawing,    Part of the Drawing Data Set, the Top level
                                    Subrack Payload  drawing is provided by an EXPRESS or WORF Rack
                                                     subrack Payload Developer to PDL for use in
                                                     development of integrated rack drawing products.
                                                     The drawing includes all size dimensions,
                                                     interface information (including torque valves),
                                                     and special instructions required to integrate the
                                                     payload.

  66                                Manifest and     Manifest and Stowage Data Set\
                                    Stowage DS       The Payload Manifest and Stowage Dataset define
                                                     the flight-specific manifest items and their
                                                     characteristics, which specify manifest
                                                     requirements for payloads including subkit items
                                                     and Inventory Management System (IMS)/barcode
                                                     data. The Payload Manifest and Stowage Data are
                                                     required by ISS Program Manifest, ISS Program
                                                     Cargo Mission Contract (CMC), and the Flight Crew
                                                     Support Division (FCSD). The data collected for
                                                     the manifest will support the production of SSP
                                                     5410X-ANX 1, Increment Definition and Requirements
                                                     Document for Planning Period X, Annex 1: Station
                                                     Manifest (Series of Annexes of Flight-Specific
                                                     Station Manifests). ISS Program CMC requires data
                                                     in order to plan and design the launch, on-orbit,
                                                     and return stowage configuration of payload
                                                     stowage into on-orbit modules and logistic
                                                     carriers. Physical data describing each payload
                                                     manifest/stowage item to be packed and
                                                     delivered/returned shall be electronically entered
                                                     into PDL. FCSD requires data in order to plan and
                                                     design the launch/return stowage configuration of
                                                     the payload in the middeck locker(s). CMC also
                                                     requires data in order to plan and design the
                                                     launch/return stowage configuration of the payload
                                                     stowage item into trays or bags. See SSP
                                                     52000-PDS.

  67                                MIP              Mission Integration Plan (MIP)\
                                                     The MIP is the Program-to-Program agreement
                                                     between the ISS and the SSP for a specific Space
                                                     Shuttle flight. The MIP is a joint Shuttle/ISS
                                                     document that is mission-specific and covers
                                                     agreed-upon overview requirements, products, and
                                                     services. It also has annexes that contain
                                                     detailed data and/or requirements for that
                                                     particular mission. The Standard Integration Plan
                                                     is used as the starting document to develop the
                                                     mission-specific MIP and annexes.

  68                                MIP, Annex 1     Mission Integration Plan (MIP), Annex 1 (Payload
                                                     Data Package)\
                                                     MIP, Annex 1 provides information on weight and
                                                     center of gravity, plus Launch Package
                                                     configuration to determine compatibility of flight
                                                     hardware to facilities and KSC support equipment.
                                                     It consists of detailed data on the physical
                                                     as-built characteristics of the payload. It
                                                     includes a definition of the sequence mass
                                                     properties, payload constrained frequencies, modes
                                                     description, configuration drawings of all major
                                                     payload elements, radio frequency transmitter
                                                     characteristics, and functional data on the
                                                     payload. It is used in conjunction with the ICD by
                                                     systems and cargo engineering to develop
                                                     engineering flight products. These data are also
                                                     used by Mission Operations in the unique mission
                                                     operations development.

  69                                MIP, Annex 2,\   Mission Integration Plan (MIP), Annex 2, Part 1
                                    Part 1 (Flight   (Flight Planning)\
                                    Planning)        MIP, Annex 2, Part 1 comes from the VMDB Drop 1,
                                                     which contains electrical power, energy, and
                                                     cooling data.

  70                                MIP, Annex 4     Mission Integration Plan (MIP), Annex 4 (Command
                                                     and data)\
                                                     MIP, Annex 4 contains details of measurement and
                                                     command parameters to implement IVT for LP/CEs via
                                                     Orbiter resources. It consists of commands,
                                                     telemetry, and software required operating the
                                                     payload, measurements of the payload's status and
                                                     health, measurements necessary for accomplishing
                                                     payload objectives, and other data needed for
                                                     processing and interpreting data. It is used by
                                                     those entities involved in building the flight
                                                     software for each flight to understand parameter
                                                     characteristics, fault detection and annunciation,
                                                     scaling coefficients, digital and analog command
                                                     specification, decom data, payload recorder
                                                     requirements, channelization requirements, and the
                                                     definition of the high-rate data transmitted via
                                                     the Ku-Band. The ISS inputs to Annex 4 are
                                                     contained in the ISS standard out deliveries. The
                                                     ISS provided standard out data is the ISS launch
                                                     package/payload data in ISS format and is
                                                     integrated with the Shuttle Data Tape (SDT),
                                                     channelization requirements, parameter
                                                     characteristics, fault detection and annunciation,
                                                     scaling coefficients, digital and analog command
                                                     specification (Standard Out Data), decom data, and
                                                     payload recorder requirements. It contains the 80
                                                     percent standard out and 100 percent standard out.
                                                     It is baselined 6 months after 100 percent
                                                     standard out.

  71                                MIP, Annex 5     Mission Integration Plan (MIP), Annex 5
                                                     (MCC/Remote POCC Interface requirements)\
                                                     MIP, Annex 5 details interface agreement between
                                                     SSP and the customer for operations support.
                                                     Defines the format and content of the customer
                                                     data required for SSP to integrate customer
                                                     hardware into the flight and ground operations.
                                                     Defines routing and the remote customer control
                                                     center interface requirements and resources for a
                                                     flight.

  72                                MIP, Annex 8     Mission Integration Plan (MIP), Annex 8 (Launch
                                                     Site Support Plan Addendum)\
                                                     The MIP, Annex 8, LSSP Addendum, is developed by
                                                     KSC utilization to provide an overview of
                                                     utilization payload processing that will take
                                                     place at KSC. These plans are similar in content
                                                     to the Launch Processing LSSP and are developed
                                                     from the report capability of the PDL using the
                                                     SRDS. LSSP milestones shown in the Payload
                                                     Integration Flows reference LSSP Addenda.

  73                                OMRS             Operations and Maintenance Requirements and
                                                     Specifications\
                                                     The MIP OMRS replaces MIP, Annex 9. The Payload
                                                     Interface Verification Summary contains ISS Launch
                                                     Package-to-Space Shuttle integration requirements
                                                     at the launch site. It is used to develop and
                                                     document the ISS and Orbiter integration
                                                     requirements. ISS Payloads also use OMRS for KSC
                                                     technical requirements imposed on KSC. See SSP
                                                     52000-PDS.

  74                                On-Orbit         On-Orbit Configuration Drawing, Part of the
                                    Configuration    Drawing Data Set\
                                    Drawing          The drawing shows the on-orbit operational
                                                     configuration for a given payload including all
                                                     necessary hardware and the routing of cables and
                                                     hoses that support the payload. This drawing
                                                     includes a listing of items to be installed by
                                                     part number, nomenclature, and quantity; cable and
                                                     hose bend radius criteria; and detail definition
                                                     of any special requirements. Payload Developers
                                                     provide a payload level on-orbit drawing to PDL
                                                     for use by PEI in developing the integrated rack
                                                     level on-orbit drawing. See SSP 52000-PDS.

  75                                Ops              Operations Supportability Assessment\
                                    Supportability   Review of PD supportability to meet Ops assessment
                                    Assessment       objectives. Appeal may be made by the PD on
                                                     readiness for Ops assessment support taking into
                                                     consideration P/L complexity, early product
                                                     status, and cost implication to meet objectives. A
                                                     PD Appeal route is PCB.

  76                                Ops Assessment   Operations Assessment:\
                                                     A End-to-End demonstration of the integrated
                                                     payload crew interfaces including HFIT evaluation,
                                                     pre-cursors to draft procedures, preliminary
                                                     displays and OpNom, labeling plan, safety issues,
                                                     hazard identification and operations concept.
                                                     Attendees include the Payload Developer, Astronaut
                                                     Office, HFIT-IPLAT, POIF representative.

  77                                Ops TIM          Operations Technical Interchange Meeting\
                                                     Early technical exchange meeting with the PD and
                                                     POIF teams. Payload developers are introduced to
                                                     the POIF ops team, ops products, and product
                                                     timelines. Emphasis is placed on early definition
                                                     of the PD ops concept, crew related tasks, OpNom,
                                                     procedures and display development.

  78                                Passport         Passport\
                                                     An OC form includes additional data to support the
                                                     export control request.

  79                                PCS Displays     Portable Computer System Displays\
                                                     The PCS displays are P/L unique crew displays for
                                                     use on the P/L PCS that are built according to PD
                                                     requirements. Payload-specific PCS displays are
                                                     built (as needed) by PSIVF and delivered to the
                                                     ISS Program. The ISS Program integrates the
                                                     displays into a P/L PCS display load. See SSP
                                                     57002 (Software ICD).

  80                                PDR              Preliminary Design Review\
                                                     Most Payloads Projects as part of their hardware
                                                     development effort will conduct a PDR when their
                                                     hardware design reaches 30% maturity. The PDR is
                                                     the completion activity of the Classical Project
                                                     Development Cycle Phase B. The PDR demonstrates
                                                     and baselines a feasible and credible design that
                                                     will accomplish the stated goals within the
                                                     constraints imposed by the fiscal and operating
                                                     environment. The ISS Program provides preliminary
                                                     interface control documentation in support of a
                                                     PDR, reviews the PDR data package for implications
                                                     to ISS operations, and provides development
                                                     guidance to the PD.

  81                                PIA              Payload Integration Agreement\
                                                     The payload-unique PIA documents high-level
                                                     agreements made between the ISS Program and the PD
                                                     concerning ISS Station Support Equipment (SSE),
                                                     Program Furnished Equipment (PFE), Ground Data
                                                     Services (GDS) and unique agreements.

  82                                P/L Engineering  Payload Engineering Verification Memo\
                                    Verification     A report produced for each ISS Stage containing
                                    Memo             status of unique payload verification, element
                                                     level verification (including EXPRESS/WORF), ISS
                                                     level verification and Requirements Change
                                                     Assessment Report (RCAR) submittal.

  83                                P/L GDS BB       Payload Ground Data Services Blank Book
                                    Requirements     Requirements\
                                                     The P/L GDS DS documents the ground system and
                                                     communications requirements for supporting the
                                                     on-orbit operations of the payload. GDS are
                                                     provided by the ISS Program-furnished operations
                                                     support center (e.g., POIC, U.S. OC, and a TSC),
                                                     as well as by other operations facilities. See SSP
                                                     52000-PDS.

  84                                P/L GR&C         Payload Groundrules and Constraints\
                                                     Payload portion of the Increment-specific Execute
                                                     Planning GR&C.

  85                                P/L Hazard       Payload Hazard Control Matrix\
                                    Control Matrix   The PHCM is an operations product that documents
                                                     the completion of the Independent Safety
                                                     Verification Review (ISVR) process. This process
                                                     is lead by POIC Safety and independently verifies
                                                     that all applicable operational hazard controls,
                                                     defined in the payloads signed hazard reports,
                                                     have been implemented properly.

  86                                P/L MDM          Payload Multiplexer/Demultiplexer Configuration
                                    Configuration    Files\
                                    Files            P/L MDM Software functions and services are driven
                                                     by payload configuration files. P/L MDM
                                                     configuration files define current operational
                                                     data and settings. P/L MDM services such as
                                                     ancillary data services, file transfer, and health
                                                     and status collection are controlled by PCF
                                                     settings. See SSP 57002 (Software ICD).

  87                                P/L O/D          Payload On-Dock Relative to Launch Date\
                                                     KSC: Payload processing involves a variety of
                                                     customer offline and/or KSC integrated activities
                                                     and testing. Payload developers coordinate their
                                                     arrival at KSC based upon their processing
                                                     requirements and KSC turnover dates. Scheduled
                                                     integrated activities are based upon the types of
                                                     payloads.\
                                                     Attached payloads may require extensive final
                                                     offline assembly, checkout, and servicing, and
                                                     subsequent Shuttle and ISS integrated testing.
                                                     Other attached payloads arrive at KSC already
                                                     integrated on their carrier and have no planned
                                                     KSC activities. O/D dates are based on each
                                                     payload\'s unique processing schedule of
                                                     activities.\
                                                     JSC: Stowage HDW that supports the JSC MDK or MPLM
                                                     Bench Review will be delivered to JSC based on the
                                                     LPMT need date (Reference BR JSC).

  88                                P/L OOS          Payload Increment On-Orbit Operations Summary\
                                                     The P/L OOS is a high-level plan providing a
                                                     summary of payload activities for an entire
                                                     increment.

  89                                P/L Planning DS  Payload Planning Data Set\
                                                     The P/L Planning DS contains the detailed payload
                                                     operations and resource requirements
                                                     specifications used to develop mission planning
                                                     products. See SSP 52000-PDS.

  90                                P/L Regulations  Payload Regulations\
                                                     Payload regulations provide established priorities
                                                     for payload activities, preplanned responses to
                                                     off nominal situations, and unique information
                                                     that enhances POIC's ability to make real time
                                                     operations decisions. See SSP 52000-PDS.

  91                                P/L Simulator    Payload Simulator\
                                                     The PD shall be responsible for providing a P/L
                                                     Simulator to meet the training requirements for
                                                     the crew and Ground Support Personnel (GSP) on the
                                                     scientific and operational aspects of their
                                                     payload. The P/L simulator requirements are agreed
                                                     upon during the Training Strategy Team process and
                                                     documented in the P/L Training Data Set. See SSP
                                                     52000-PDS.

  92                                P/L Training.    Payload Training\
                                                     P/L training is provided to the ISS crew going up
                                                     on the first flight of the increment, regardless
                                                     of launch vehicle. Training includes procedures
                                                     training, increment-specific activities,
                                                     proficiency training on skills, systems
                                                     operations, and team training.\
                                                     Reflight - Reflight Training addresses payloads
                                                     that have flown on a previous increment.\
                                                     Facility - New P/L Facility Training addresses new
                                                     facility class payloads that have
                                                     [not]{.underline} flown on a previous increment.\
                                                     Subrack - New Payload Subrack Training addresses
                                                     new subrack payloads that have [not]{.underline}
                                                     flown on a previous increment.\
                                                     Complement Training - Complement Training involves
                                                     standalone training of the crew on the complement
                                                     of payloads to be operated during ISS on-orbit
                                                     activities.\
                                                     See SSP 52000-PDS.

  93                                Payload Transfer Payload Transfer Drawings/Requirement\
                                    Dwgs/Reqmts      Part of the Drawing Data Set, these drawings
                                                     conveys any special information needed to transfer
                                                     payload hardware from a launch vehicle to the ISS.

  94                                P/L T/O          Payload Turn-Over (Kennedy Space Center)\
                                                     KSC: KSC receives custodial responsibility for
                                                     payload hardware at turnover. Integrated racks
                                                     will be turned over by KSC utilization to support
                                                     MPLM install need dates. Hardware is turned over
                                                     to support KSC "online" integrated mission
                                                     processing activities as planned and required.
                                                     When processing involves integrated testing
                                                     activities, a thorough review of the flight
                                                     hardware and its related IDP is performed. An IDP
                                                     is not needed for flight-ready hardware, shipped
                                                     directly to KSC logistics for stowage, and
                                                     "turnover" is at hardware arrival, per shipping
                                                     documentation. However, typically, hardware
                                                     turnover follows a period of payload developer,
                                                     offline activities at KSC.\
                                                     JSC: Stowage HDW that supports the JSC MDK or MPLM
                                                     Bench Review will be turned over at JSC based on
                                                     the LPMT need date (Reference BR JSC).

  95                                P/L Training DS  Payload Training Data Set\
                                                     The P/L Training DS documents requirements for
                                                     user-provided and user/ISS Program-provided
                                                     payload training for the ISS crew and ISS Program
                                                     ground support personnel, and ISS Program
                                                     requirements for training of user personnel. See
                                                     SSP 52000-PDS.

  96                                P/L Verification Payload Verification Data\
                                    Data             Stage Analysis -- Unique, payload interface,
                                                     verification data required by PEI to complete ISS
                                                     element level verification for each stage; i.e.,
                                                     EMI, acoustics, thermal, protrusions, envelopes,
                                                     power draws.\
                                                     Certificate of Compliance - Unique payload
                                                     interface verification certification record that
                                                     indicates the payload is in compliance with
                                                     remaining applicable IRD requirements not utilized
                                                     for Stage Analysis.

  97                                PPD DS           Payload Procedures and Displays Data Set\
                                                     The PPD DS addresses the requirements to supply
                                                     United States (U.S.) Payload Operations Data File
                                                     (PODF) products. Operations concept and
                                                     analysis/flows, Payload displays, payload-unique
                                                     Operations Nomenclature, manual procedures and
                                                     support products, automated procedures, ground
                                                     command procedures, and payload messages are
                                                     included in this data set. See SSP 52000-PDS.

  98                                Proforma         Proforma\
                                                     A document, JSC Form 1735, must accompany the ECW.
                                                     Includes financial data for hardware requested for
                                                     export approval.

  99                                PRR              Payload Readiness Review\
                                                     The goal of the PRR is for the ISS Program, with
                                                     payload developer support, to provide a payload
                                                     readiness statement for launch, if there is a
                                                     direct payload interface with the Orbiter's
                                                     payload bay or as requested by the cargo bay
                                                     carrier integrator. This is applicable for large
                                                     attached payloads.

  100                               PSM              Payload System Manual\
                                                     The PSM provides the PRO with the operating and
                                                     reference data necessary to perform real-time
                                                     commanding and monitoring of the facilities and
                                                     payloads support systems. It also provides the
                                                     POIC with a reference of operational concepts and
                                                     technical data and schematics associated with
                                                     payload systems.

  101                               PTDR             Payload Training Dry Run\
                                                     Prior to crew training, a PTDR will be held for
                                                     each payload or experiment course, included
                                                     on-board training products, to prove the readiness
                                                     of the facilities, instructors, and training
                                                     equipment/products. The instructor that has been
                                                     designated to perform the training for the crew
                                                     prepares the Payload Training Lesson Plan and
                                                     courseware and then conducts the PTDR. Attendance
                                                     is required by the responsible Operations Lead and
                                                     crew representative in order to sign-off and
                                                     certify the lesson.

  102                               PTP Input Tables Payload Tactical Plan Input Tables\
                                                     PTP input tables are required of the Payload
                                                     Developer prior to flight manifesting. Payload
                                                     Developers -- RPO working in conjunction with
                                                     their PIM will fill out an investigation -- level
                                                     PTP input tables for each Increment which the
                                                     Payload/investigation is operated. The PTP input
                                                     tables are used as an initial source of payload
                                                     integration data to perform tactical planning, and
                                                     populate Increment-specific PTPs.

  103                               Rack Mass        Rack Mass Properties and Test Verified Model\
                                    Properties and   Consist of rack weight, center of gravity, moment
                                    Test Verified    of inertia and product of inertia.\
                                    Model            Rack test verified model is a model that has been
                                                     shown to behave in a manner acceptably close to
                                                     test results of the item the model represents. For
                                                     models intended to be used in coupled loads
                                                     analysis, such as the EXPRESS rack model, this is
                                                     usually done through comparison of normal modes
                                                     analysis results generated by the model with the
                                                     results of a modal survey performed on the
                                                     hardware. This assures that the model behaves in a
                                                     realistic fashion in terms of the dynamic behavior
                                                     of the hardware, within a limited frequency range.
                                                     Models intended for stress or displacement
                                                     analysis would be verified against stress or
                                                     displacement test results.

  104                               SDP              Safety Data Package\
                                                     A collection of safety and certification
                                                     documents, to be submitted to the PSRP (Payload
                                                     Safety Review Panel) by the hardware Payload
                                                     Developer, requesting approval for flight upon a
                                                     particular launch vehicle.

  105                               SSCCD/CMC Work   Space Station Configuration Control Drawings/Cargo
                                    Order            Mission Contract Work Order\
                                                     The Space Station Configuration Control Drawings
                                                     document the interior stowed configuration of the
                                                     U.S. logistics carrier (currently, the MPLM) as
                                                     required for launch and return. The top assembly
                                                     drawing provides the mission unique cargo carrier
                                                     configuration. Stowage rack level drawings provide
                                                     the stowage locations of the hardware packed
                                                     inside the racks. Bag/cushion level drawings
                                                     provide the packed configuration and unique
                                                     stowage instructions for the individual pieces of
                                                     hardware. SSCCD bag level drawings are also
                                                     provided for other launch vehicles such as the
                                                     Shuttle Middeck, Soyuz, Progress, HTV and ATV to
                                                     document JSC-packed Station hardware. Stowage
                                                     Integration develops SSCCDs for the crew, systems,
                                                     operational, logistics/maintenance hardware, and
                                                     payload stowage items stowed in standard stowage
                                                     racks. The results of all cargo layout planning
                                                     are documented by the SSCCD which provide the
                                                     physical installation requirements for the cargo
                                                     with the logistics carriers. For KSC packed
                                                     hardware the packing configuration can be
                                                     documented in either an SSCCD or CMC Work Order
                                                     which can be obtained from the assigned ISS
                                                     Stowage Integration Flight Lead.

  106                               Stage            Stage Configuration Drawings\
                                    Configuration    US Lab Level\
                                    Drawings         Stage Configuration Drawings document the overall
                                                     US Lab physical configuration of each payload rack
                                                     (EXPRESS and Facility) and each integrated payload
                                                     (subrack, deployed, and small payloads) that are
                                                     on-orbit during a given stage. See SSP 52000-PDS.

  107                               Stowage H/W      Stowage Hardware Drawings and Installed Payload
                                    Drawings and     Drawings\
                                    Installed P/L    Part of the Drawing Data Set, these drawings shows
                                    Drawings         the as-built or as delivered configuration of the
                                                     hardware being stowed for launch. Often the Main
                                                     Unit Top Assembly Drawing is the Stowage H/W
                                                     Drawing if a payload is being launched soft
                                                     stowed, but drawings are also required for kits,
                                                     sub-kits, or other hardware being launched
                                                     separate from the main unit to show how the
                                                     payload hardware should be configured for launch.

  108                               S/W ICD          Software Interface Control Document\
                                                     Documents requirements for command, data, and
                                                     payload support software accommodations for the
                                                     on-orbit and related ground-activity phases. See
                                                     SSP 57002.

  109                               TDS              Technical Data Sheet\
                                                     OC form includes technical descriptions, pictures
                                                     and drawings of hardware, to be sent to the
                                                     Russians, to gain permission to fly on a Russian
                                                     vehicle.

  110                               TGHR             Time-Critical Ground Handling Requirements\
                                                     MDK P/L time-critical Orbiter requirements are
                                                     documented in a mission-specific TGHR table. The
                                                     TGHR also includes time-critical requirements for
                                                     other non-payload crew compartment items. MDK
                                                     time-critical requirements include turnover,
                                                     launch delay, and early turnover requirements. MDK
                                                     orientation and power interrupt constraints are
                                                     also documented in the TGHR. MDK IVT and any other
                                                     requirements will be documented in OMRS File II,
                                                     Volume II. See SSP 52000-PDS

  111                               Transfer List    Transfer List\
                                                     Transfer list is the product distributed and
                                                     reviewed to support transfer cue card review
                                                     meeting, which verify all stowage
                                                     requirements/constraints are identified and
                                                     scheduled to accommodate mission objectives.

  112                               TST              Training Strategy Team\
                                                     A NASA payload TST process has been defined to aid
                                                     in the development of the payload training
                                                     requirements for each payload or experiment and
                                                     complements of payloads or experiments. Payload
                                                     training requirements and what will be needed to
                                                     fulfill those requirements, for both crewmembers
                                                     and GSP, are discussed, defined, and agreed upon
                                                     during this process. The official membership of
                                                     the TST consists of MSFC training personnel, JSC
                                                     training personnel, SSTF/PTC SME, PD
                                                     Representatives, Crew Representatives, and Program
                                                     Office personnel. See SSP 52000-PDS.

  113                               Usability Tests  Usability Tests\
                                                     The Usability Verification Event is a
                                                     test/evaluation, conducted with case-appropriate
                                                     rigor, to determine the readiness of payload
                                                     on-board displays and procedures for PTDR, crew
                                                     training and flight. It is performed to ensure
                                                     operability for payloads, regardless of the type
                                                     of Human Computer Interface (HCI). During the
                                                     event, the candidate flight displays are evaluated
                                                     for usability (per ISO 9241-11) and for
                                                     commonality across payloads (i.e., common look and
                                                     feel). Interoperability of the displays and
                                                     procedures is also assessed. If warranted, a
                                                     procedure only test/evaluation may be performed to
                                                     ensure operability. Evaluations can be formal
                                                     (i.e. conducted on flight representative hardware,
                                                     face-to-face with crew and PD representatives), or
                                                     informal (tabletop trial via telecon, with no
                                                     hardware present, in a work session format).

  114                               U.S. PODF        U.S. Payload Operations Data File\
                                                     The U.S. PODF is the collection of procedures,
                                                     displays and operations nomenclature necessary to
                                                     perform U.S. payload operations. The procedures
                                                     consist of manual, automated, and ground command
                                                     procedures. The U.S. PODF is controlled by the
                                                     U.S. PODFCB. See SSP 52000-PDS.
  -----------------------------------------------------------------------------------------------------

# ISS PAYLOAD MILESTONE CHRONOLOGY

The tables in this section provide a detailed listing and identify all
of the payload integration process milestones in chronological order.
The ISS payload integration milestones are grouped in this section
within functional areas. These functional groupings of integration
milestones are:

Table 4.0-1: Payload Developer Milestone Chronology. This table is
separated into two parts, Payload Development Phase (Table 4.0-1A) and
ISS Mission Integration Phase (Table 4.0-1B). The Payload Development
phase lists the typical payload project development activities that the
ISS Program monitors or supports. These activities normally occur prior
to the manifest assignment; therefore, the dates provided represent a
typical payload development template. Although the ISS Payload Program
does not require the activities and submittals identified in the Payload
Development phase, it is in the best interest of the PD to solicit early
ISS Payload Program guidance and support to avoid developmental cost and
schedule impacts further downstream in the ISS Mission Integration
phase. The specific dates for these activities if applicable will be
dependent upon the payload project's unique development schedule, not
the ISS payload integration process. The ISS Mission Integration table
lists the dates of all ISS Program "required" activities and submittals
due from the PD. These activities and submittals commence with the PD
delivery of the Questionnaire/PTP input tables followed by manifesting
of the payload via ISS Payload Program baseline of an Increment specific
Payload Tactical Plan.

Table 4.0-2: Payload Mission Integration Milestone Chronology. This
table lists ISS Payload Mission Integration (OZ2) submittals to the ISS
Program/SSP and other key Program milestones.

Table 4.0-3: Payload Engineering Integration Milestone Chronology. This
table lists ISS Payload Office Payload Engineering Integration (OZ3)
submittals to the ISS Program/SSP and other key Program milestones.

Table 4.0-4: Payload Software Integration Milestone Chronology. This
table lists ISS Payload Office Payload Software Integration (OZ5)
submittals to the ISS Program/SSP and other key Program milestones.

Table 4.0-5: Payload Operations Integration Function Milestone
Chronology. This table lists Payload Operations Integration submittals
to the ISS Program/SSP and other key Program milestones.

Table 4.0-6: Kennedy Space Center Integration Milestone Chronology. This
table lists Kennedy Space Center Utilization integration submittals to
the ISS Program/SSP and other key Program milestones.

Dates within these chronology tables are for planning guidance and
provide template data for the payload integration process generic
schedule templates contained in Appendix D. Actual payload-unique
schedules implementation may deviate from the templates. The chronology
tables include the following column headers:

LINE #: The line number is assigned to each milestone acronym and is
used to identify the milestone during documentation reviews, specific
schedule development, and internal coordination.

MILESTONE ACRONYM: The milestone acronym is a short-hand identifier used
in the generic payload integration templates and on the flight- and
payload-specific schedules.

DATE (MONTHS): Milestone date is referenced in relationship to start of
an ISS Planning Period (PP), Increment (I), or Launch (L). Some
milestone dates may reference Payload Project development activity such
as Preliminary Design Review (PDR), Critical Design Review (CDR) or
Hardware Readiness. The date is provided in months unless otherwise
identified. The milestone date indicated is the template date for the
completion of a given milestone.

PREDECESSORS AND SUCCESSORS: Identifies other milestones which typically
occur prior to (predecessors) the milestone indicated, as well as other
milestones that typically follow (successors) the milestone indicated.

F (Facility): An 'X' in this column indicates the milestone is
applicable to pressurized payloads and facility class payloads racks.
Payloads of this type typically have at least some amount of ISS
interfaces or resources, which preclude them from meeting the "Small"
payload criteria.

S (Small): An 'X' in this column indicates the milestone is applicable
to small payloads, including stowed/deployed. Payloads of this type have
minimal ISS interfaces and are very often passively stowed and
temporarily deployed or setup in the US Lab aisle way when active.
Criteria for defining a Small payload are found in SSP 57063.

Sub (Subrack): An 'X' in this column indicates the milestone is
applicable to EXPRESS and WORF subrack payloads only. Payloads of this
type have some unique integration submittals not required by other
payload types.

A (Attached): An 'X' in this column indicates the milestone is
applicable to attached (unpressurized) payloads. Payloads of this type
are attached externally to ISS for operations, but they can have some
internal pressurized components.

PMIT (Payload Mission Integration Team): An 'X' in this column indicates
the milestone is included PMIT Flight schedules.

ORG (ISS Payload Program Organization): This column header is only found
in the PD Milestone Chronology Tables 4.0-1A and 4.0-1B. This column is
used to identify the ISS Payload Program organization that is the owner
of the milestone with respect to this document. The five organization
choices for this column are: PMI (Payload Mission Integration), PEI
(Payload Engineering Integration), PSI (Payload Software Integration),
Payload Operations Integration Function (POIF), and KSC (Kennedy Space
Center Utilization integration).

The four payload classification columns identify which milestones are
applicable to each payload class listed above. If a unique date appears
in one of these columns instead of an 'X', this date supersedes the
milestone date for that payload class. If a milestone is applicable to a
payload classification, that milestone will appear on the Generic
Payload Integration Manager (PIM) Schedule Template for that payload
classification, and then used to develop unique payload schedules.

Some milestones within Table 4.0-2 will not have any payload
classification applicability identified since they are for reference
purposes only.

<table>
<colgroup>
<col style="width: 6%" />
<col style="width: 11%" />
<col style="width: 8%" />
<col style="width: 40%" />
<col style="width: 4%" />
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="10"><span id="__RefHeading___Toc177265750"
class="anchor"></span>table 4.0-1A pAYLOAD DEVELOPER MILESTONE
CHRONOLOGY<br />
payload development phase (3 PAGES)</th>
</tr>
<tr class="odd">
<th>Line #</th>
<th>Milestone Acronym</th>
<th>Date (Months)</th>
<th>Predecessors And Successors</th>
<th>F</th>
<th>S</th>
<th>Sub</th>
<th>A</th>
<th>PMIT</th>
<th>Org</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1</td>
<td>Export Control Letter</td>
<td>*</td>
<td><p>Export Control Letter</p>
<p>* Requested following new payload identification to the
Program.<br />
Highly desirable to have prior to PDR or any ISS Program support of PDR
or any PD development effort involving ISS Program personnel. Must have
prior to Drawing Data Set submittal.</p></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>2</td>
<td>PDR</td>
<td>*</td>
<td><p>Preliminary Design Review</p>
<p>* Typically would occur 3 years prior to launch.<br />
PD controls actual date of PDR.<br />
ISS Payload Program will support PDR.<br />
PDR may not be held by all PDs.</p></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>3</td>
<td>H/W ICD (P)</td>
<td>PDR</td>
<td>Hardware Interface Control Document (Preliminary)</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="even">
<td>4</td>
<td>OPS TIM</td>
<td>PDR</td>
<td><p>Operations Technical Interchange Meeting</p>
<blockquote>
<p>Payload Developers are introduced to Integration and Operations
product timeline and flow.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>5</td>
<td>PPD DS</td>
<td>PDR</td>
<td><p>Payload Procedures and Displays Data Set: Operations Concept;
Operations Analysis/Flows</p>
<blockquote>
<p>These are optional PD submittals.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>6</td>
<td>PPD DS</td>
<td>PDR</td>
<td>Payload Procedures and Displays Data Set: Operations Nomenclature
(Baseline Payload Name)</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>7</td>
<td>Phase 0/I FSDP</td>
<td>Ph 0/I FSR -45 days</td>
<td><p>Phase 0/I Payload Flight Safety Data Pack</p>
<blockquote>
<p>45 days before Phase 0/I FSR.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>8</td>
<td>Phase 0/I P/L FSR</td>
<td>PDR+2</td>
<td>Phase 0/I Payload Flight Safety Review</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>9</td>
<td>Phase 0/I GSDP</td>
<td>Ph 0/I GSR -45 days</td>
<td><p>Phase 0/I Payload Ground Safety Data Pack</p>
<blockquote>
<p>45 days before Phase 0/I GSR.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>10</td>
<td>Phase 0/I P/L GSR</td>
<td>PDR+3</td>
<td><p>Phase 0/I Payload Ground Safety Review</p>
<blockquote>
<p>Timing to support Phase II definition of hazard controls by CDR.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>11</td>
<td>CDR</td>
<td>*</td>
<td><p>Critical Design Review</p>
<p>* Typically would occur 2 years prior to launch.<br />
PD controls actual date of CDR.<br />
ISS Payload Program will support CDR.<br />
CDR may not be held by all PDs, i.e. reflight or serial
hardware.</p></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>12</td>
<td>Phase II FSDP</td>
<td>Ph II FSR -45 days</td>
<td><p>Phase II Payload Flight Safety Data Package</p>
<blockquote>
<p>45 days before Phase II P/L FSR</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>13</td>
<td>HW ICD (Draft)</td>
<td>CDR</td>
<td><p>Hardware ICD (Draft)</p>
<blockquote>
<p>After HW ICD Preliminary</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="even">
<td>14</td>
<td>Ops Assessment Supportability</td>
<td>CDR+2</td>
<td><p>Ops Assessment Supportability</p>
<blockquote>
<p>Two month before Ops Assessment.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>15</td>
<td>Phase II P/L FSR</td>
<td>CDR+2</td>
<td>Phase II Payload Flight Safety Review</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>16</td>
<td>Phase II GSDP</td>
<td>Ph II GSR -45 days</td>
<td><p>Phase II Payload Ground Safety Data Package</p>
<blockquote>
<p>45 days before Phase II P/L GSR.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>17</td>
<td>Phase II P/L GSR</td>
<td>CDR+2</td>
<td>Phase II Payload Ground Safety Review</td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>18</td>
<td>TST Process</td>
<td>CDR<br />
to CDR+4</td>
<td><p>Training Strategy Team Process Participation</p>
<blockquote>
<p>Starts at CDR and typically requires 4 months to complete.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>19</td>
<td>Drawing DS – Crew Interface Label Dwgs.</td>
<td>CDR+4</td>
<td><p>Drawing Data Set: Crew Interface Label Drawings
(Pre-released)</p>
<blockquote>
<p>Same time as Operations Nomenclature. (Abbreviations/Acronyms for
Hardware Panels).</p>
</blockquote></td>
<td>X</td>
<td>CDR+6</td>
<td>CDR+6</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="even">
<td>20</td>
<td>PPD DS</td>
<td>CDR+2</td>
<td><p>Payload Procedures and Displays Data Set: Operations Nomenclature
(Baseline Abbreviations/Acronyms for Hardware Panels, if needed);
Initial Crew Displays</p>
<blockquote>
<p>Same time as Crew Interface Label Drawings (Pre-released).<br />
Before Candidate Flight Crew Displays submittal.</p>
</blockquote></td>
<td>X</td>
<td>CDR+6</td>
<td>CDR+6</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>21</td>
<td>P/L Training DS</td>
<td>CDR+6</td>
<td><p>Payload Training Data Set</p>
<blockquote>
<p>No later than 2 months after TST process complete.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>22</td>
<td>PPD DS</td>
<td>CDR+7</td>
<td><p>Payload Procedures and Displays Data Set:</p>
<blockquote>
<p>Operations Nomenclature (Baseline Abbreviations/Acronyms for Hardware
Panels, if needed); Candidate Flight Crew Displays.<br />
After Crew Interface Label Drawings (Pre-released).</p>
</blockquote></td>
<td>X</td>
<td>I-15</td>
<td>I-15</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 6%" />
<col style="width: 11%" />
<col style="width: 8%" />
<col style="width: 40%" />
<col style="width: 4%" />
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="10"><span id="__RefHeading___Toc177265751"
class="anchor"></span>table 4.0-1B pAYLOAD DEVELOPER MILESTONE
CHRONOLOGY<br />
iss mission integration phase (10 pages)</th>
</tr>
<tr class="odd">
<th>Line #</th>
<th>Milestone Acronym</th>
<th>Date (Months)</th>
<th>Predecessors And Successors</th>
<th>F</th>
<th>S</th>
<th>Sub</th>
<th>A</th>
<th>PMIT</th>
<th>Org</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1</td>
<td>PTP Input Tables</td>
<td>I-17</td>
<td><p>Investigation Level Questionnaire for Payload Developer Increment
Specific Requirements</p>
<blockquote>
<p>7 months before IDRD Annex 5 PTP Baseline.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>2</td>
<td>PPD DS</td>
<td>I-16</td>
<td><p>Payload Procedures and Displays Data Set: Manual Procedures;
Procedure/Display Files List; Reference Data; Validation Record Report;
Log Files; IPV Links; Payload Messages</p>
<blockquote>
<p>6 months before Start New P/L Training.</p>
</blockquote></td>
<td>X</td>
<td>I-14</td>
<td>I-14</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>3</td>
<td>Reflight P/L Training</td>
<td>I-16</td>
<td><p>Training for “Reflight” Payloads</p>
<blockquote>
<p>PD participation only required if PD provides instructor.<br />
Reflight Pressurized facility (rack-level) payloads not requiring PD
training support could start earlier.<br />
12 months before Start Complement Training.</p>
</blockquote></td>
<td></td>
<td>I-16</td>
<td>I-16</td>
<td>I-16</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>4</td>
<td>PCS Display Requirements (P)</td>
<td>L-16</td>
<td><p>PCS Requirements for Program Built Displays (Preliminary)</p>
<blockquote>
<p>7 months before P/L MDM Configuration Files/PCS Displays (P).<br />
4 months before S/W ICD (P).</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td></td>
<td>PSI</td>
</tr>
<tr class="odd">
<td>5</td>
<td>C&amp;DH DS (P)</td>
<td>L-16</td>
<td><p>Command and Data Handling Data Set (Preliminary)<br />
(If Program is not to build displays)</p>
<blockquote>
<p>Initial L-12.<br />
Preliminary L-8.<br />
Final L-3.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td></td>
<td>PSI</td>
</tr>
<tr class="even">
<td>6</td>
<td>EXPRESS/<br />
WORF Laptop Payload SW Application and Displays (P)</td>
<td>L-16</td>
<td><p>EXPRESS/WORF Laptop Payload SW Application and Displays
(Preliminary)<br />
(If application is not the sole payload application to be integrated
onto the laptop)</p>
<blockquote>
<p>Demonstrate EXPRESS/WORF laptop integrated SW load is compatible.</p>
</blockquote></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>PSI</td>
</tr>
<tr class="odd">
<td>7</td>
<td>Manifest and Stowage DS (B/L)-<br />
Middeck</td>
<td>L-15 to<br />
L-14</td>
<td><p>Manifest and Stowage Data Set (Baseline) Middeck</p>
<blockquote>
<p>1.5 months before ISS Program Preliminary Manifest available at same
time as ISS Program.<br />
Call for manifest requests (MR cutoff date varies) for the Flight.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI/<br />
PEI</td>
</tr>
<tr class="even">
<td>8</td>
<td>H/W ICD – Draft Update</td>
<td>L-14</td>
<td>Hardware Interface Control Document draft update</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>9</td>
<td>P/L Trainer O/D at JSC</td>
<td>I-13</td>
<td><p>Payload Trainer hardware and software delivery to JSC training
facility</p>
<blockquote>
<p>3 months before New P/L Training.</p>
</blockquote></td>
<td>X</td>
<td>I-11</td>
<td>I-11</td>
<td>I-11</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>10</td>
<td>P/L GDS BB</td>
<td>I-13</td>
<td><p>Payload Ground Data Services Blank Book sent to PD Teams</p>
<blockquote>
<p>3 months before GDS Blank Book Requirements are Baselined.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>11</td>
<td>EMC RF Data (Cargo Bay Payload)</td>
<td>L-12.9</td>
<td><p>EMC Radio Frequency Data for Cargo Bay Payloads</p>
<blockquote>
<p>Prior to EMC Panel approval.<br />
4 months before CIR.<br />
8 months before ISS Program EMC Test Data to SSP.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>12</td>
<td>KSC TRDS ISS to P/L OMRS, File 10, Volume 2 (P) submittal</td>
<td>L-12.5</td>
<td><p>Kennedy Space Center Technical Requirements Data Set
International Space Station to Payload Operations and Maintenance
Requirements and Specifications, File 10, Volume 2 (Preliminary)
submittal</p>
<blockquote>
<p>0.5 month before KSC TRDS OMRS, File 10, Volume 2 (P).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td></td>
<td>KSC</td>
</tr>
<tr class="odd">
<td>13</td>
<td>KSC TRDS Bay to P/L OMRS, File 2, Volume 2 (P) submittal</td>
<td>L-12.5</td>
<td><p>Kennedy Space Center Technical Requirements Data Set Bay to
Payload Operations and Maintenance Requirements and Specifications,
File 2, Volume 2 (Preliminary) submittal</p>
<blockquote>
<p>0.5 month before KSC TRDS OMRS, File 2, Volume 2 (P).</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>14</td>
<td>Drawing DS - On-Orbit Configuration Drawings (B/L)</td>
<td>L-12</td>
<td>Drawing Data Set: On-Orbit Configuration Drawings (Baseline)</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>15</td>
<td>Drawing DS - Main Unit Top Assy Drawing (B/L)</td>
<td>L-12</td>
<td>Drawing Data Set: Main Unit Top Assembly Drawings Payload
(Baseline)</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="even">
<td>16</td>
<td>P/L Verification Data and COCs</td>
<td>L-12 to<br />
L-3(or turnover)</td>
<td><p>Payload Verification Data COCs, and RCARs</p>
<blockquote>
<p>Payload Verification Data (stage analysis related), Certificates of
Compliance (COCs), and Requirements Change Assessment Report (RCAR).
Dependent upon payload type, verification submittals are required across
a range of dates related to launch beginning at L-12 to L-3.<br />
Specific drop date are:<br />
L-12, L-11.5, L-11, L-10.5, L-10, L-9.5, L-9, L-7.5, L-7,L-6.5, L-5,
L-4.5, L-3.5, L-3 (or turnover)</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>17</td>
<td>EMC Thermal Blanket Data (Cargo Bay Payload)</td>
<td>L-11.9</td>
<td><p>EMC Thermal Blanket Data for Cargo Bay Payloads</p>
<blockquote>
<p>1.5 months before ISS Program/SSP Final EMC Report.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>18</td>
<td>PTDR</td>
<td>I-11</td>
<td><p>Payload Training Dry Run</p>
<blockquote>
<p>This milestone is applicable to new payloads or payloads with major
revisions in objectives or training products as determined by TST 1
month before Start New P/L Training.</p>
</blockquote></td>
<td>X</td>
<td>I-9</td>
<td>I-9</td>
<td>I-9</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>19</td>
<td>PCS Display Requirements (I)</td>
<td>L-11</td>
<td><p>PCS Requirements for Program Built Displays (Interim)</p>
<blockquote>
<p>These requirement updates will be used as the basis for baselining
the PL PCS SW Requirements Specification (SRS) 4 months before P/L MDM
Configuration Files/PCS Displays (I).</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td></td>
<td>PSI</td>
</tr>
<tr class="even">
<td>20</td>
<td>Drawing DS - Stowage H/W Dwgs and Installed P/L Dwgs (B/L)</td>
<td>L-11</td>
<td><p>Drawing Data Set: Stowage hardware drawings and installed P/L
drawings</p>
<blockquote>
<p>1 month before SSP need date for installed P/L drawings.<br />
2 month before ICA B/L.<br />
Before Hardware Audit (MPLM and Middeck).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI/ PEI</td>
</tr>
<tr class="odd">
<td>21</td>
<td>IDRD Annex 3</td>
<td>I-13</td>
<td><p>IDRD Annex 3 – Imagery Requirement</p>
<blockquote>
<p>Orbiter – Docked, Pre, Post<br />
EVA<br />
Transfer</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>22</td>
<td>New P/L Training</td>
<td>I-10</td>
<td><p>Training for “New” Payloads</p>
<blockquote>
<p>1 month after PTDR.<br />
2-4 months before Start Complement Training.</p>
</blockquote></td>
<td>X</td>
<td>I-8</td>
<td>I-8</td>
<td>I-8</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="odd">
<td>23</td>
<td>Rack Mass Properties and Test Verified Model</td>
<td>L-10.5 to L-9.5</td>
<td><p>Rack Mass Properties and Test Verified Model</p>
<blockquote>
<p>3.5 months before VADAR.<br />
3 months before submitting monthly mass properties.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td>PEI</td>
</tr>
<tr class="even">
<td>24</td>
<td>P/L Exception Submit</td>
<td>L-9.5</td>
<td>Payload Exception Submittal</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>25</td>
<td>P/L Verification Data</td>
<td>L-9.5 to L-7.5</td>
<td><p>Payload Verification Data (Stage Analysis Data)</p>
<blockquote>
<p>3 months before Final Stage Analysis Report.</p>
</blockquote></td>
<td>L-7.5</td>
<td>L-7.5</td>
<td>L-9.5</td>
<td>L-7.5</td>
<td>X</td>
<td>PEI</td>
</tr>
<tr class="even">
<td>26</td>
<td>C&amp;DH DS (I)</td>
<td>L-9</td>
<td><p>Command and Data Handling Data Set (Interim)</p>
<blockquote>
<p>2 months before P/L MDM Configuration Files/PCS Displays (I).<br />
1 month before S/W ICD (I).<br />
2 months before POIC Command &amp; Telemetry Database (I).</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td></td>
<td>PSI</td>
</tr>
<tr class="odd">
<td>27</td>
<td>EXPRESS/<br />
WORF Laptop Payload SW Application and Displays (I)</td>
<td>L-9</td>
<td><p>EXPRESS/WORF Laptop Payload SW Application and Displays
(Interim)<br />
(If application is not the sole payload application to be integrated
onto the laptop)</p>
<blockquote>
<p>Demonstrate EXPRESS/WORF laptop integrated SW load is compatible.</p>
</blockquote></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>PSI</td>
</tr>
<tr class="even">
<td>28</td>
<td>Drawing DS – Crew Interface Label Dwgs</td>
<td>I-8</td>
<td><p>Drawing Data Set: Crew Interface Label Drawings (Released)</p>
<blockquote>
<p>Before IPLAT grants approval for PD to produce/order labels.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>29</td>
<td>Manifest and Stowage DS (U/D) – MPLM/Node &amp; Middeck</td>
<td>L-6 to L-3</td>
<td><p>Manifest and Stowage Data Set (U/D) MPLM/Node &amp; Middeck –
Subkit Data</p>
<blockquote>
<p>L-2 months before Bench Review (L-6 for MPLM/Node and L-3 for
MDK).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI/ PEI</td>
</tr>
<tr class="even">
<td>30</td>
<td>PCS Display Requirements (F)</td>
<td>L-8</td>
<td><p>PCS Requirements for Program Built Displays (Final)<br />
These requirement updates will be used as the basis for updating the PL
SW Requirements Specification (SRS) to its final flight baseline
state</p>
<blockquote>
<p>4 months before P/L MDM Configuration Files/PCS Displays (F).</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td></td>
<td>PSI</td>
</tr>
<tr class="odd">
<td>31</td>
<td>P/L Planning DS Initial Submittal</td>
<td>I-8</td>
<td><p>Payload Planning Data Set Initial Submittal</p>
<blockquote>
<p>6 months before P/L OOS (F) and P/L GR&amp;C (F).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>POIF</td>
</tr>
<tr class="even">
<td>32</td>
<td>Drawing DS – On-Orbit Configuration Drawings (U/D)</td>
<td>L-7.5</td>
<td><p>Drawing Data Set: On-Orbit Configuration Drawings (Update)</p>
<blockquote>
<p>4.5 months after Baseline.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>33</td>
<td>Drawing DS – Main Unit Top Assy Drawing (U/D)</td>
<td>L-7.5</td>
<td><p>Drawing Data Set: Main Unit Top Assembly Drawings Payload
(Update)</p>
<blockquote>
<p>4, 5 months after Baseline.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PEI</td>
</tr>
<tr class="even">
<td>34</td>
<td>EXPRESS/<br />
WORF Laptop Payload SW Application and Displays (F)<br />
(Multiple P/L applications being integrated on laptop)</td>
<td>L-7</td>
<td><p>EXPRESS/WORF Laptop Payload SW Application and Displays
(Final)<br />
(Multiple P/L applications being integrated on laptop)</p>
<blockquote>
<p>CD with the P/L application will be provided to the PSIVF so that an
integrated laptop load can be developed.</p>
</blockquote></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>PSI</td>
</tr>
<tr class="odd">
<td>35</td>
<td>PPD DS</td>
<td>I-7 – I-5.5</td>
<td><p>Payload Procedures and Displays Data Set: ECR to Baseline Manual
Procedures; Procedure Hazard Control List</p>
<blockquote>
<p>After Tabletop, Usability Verification, Crew Training window from I-7
to I-5.5 months.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>36</td>
<td>Drawing DS – Stowage H/W Dwgs and Installed P/L Dwgs (U/D)</td>
<td>L-7</td>
<td><p>Drawing Data Set: Stowage hardware drawings and installed P/L
drawings (Update)</p>
<blockquote>
<p>1.5 months before HAMR B/L.<br />
2 months before SSCCD Released.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI/ PEI</td>
</tr>
<tr class="odd">
<td>37</td>
<td>Drawing DS – P/L Transfer Dwgs/Rqmts (B/L)</td>
<td>L-6</td>
<td>Drawing Data Set: Payload Transfer Drawings/Requirements
(Baseline)</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>PEI</td>
</tr>
<tr class="even">
<td>38</td>
<td>KSC O/D for Activity Testing</td>
<td>L-6</td>
<td><p>Kennedy Space Center On-Dock for Activity and Testing</p>
<blockquote>
<p>Arrival of Payload Hardware at KSC.<br />
PRCU Testing.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="odd">
<td>39</td>
<td>KSC Offline Activity</td>
<td>L-6 to L-4.5</td>
<td><p>Kennedy Space Center On-Dock for Offline Activity</p>
<blockquote>
<p>Arrival of Payload Hardware at KSC.<br />
PRCU Testing.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>40</td>
<td>KSC TRDS Orbiter MDK to P/L OMRS, File 2, Volume 2 (P)
submittal</td>
<td>L-6</td>
<td><p>Kennedy Space Center Technical Requirements Data Set Orbiter
Middeck to Payload Operations and Maintenance Requirements and
Specifications, File 2, Volume 2 (Nominal)(Preliminary submittal)</p>
<blockquote>
<p>1 month before OMRS, File 2, Volume 2 (P).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="odd">
<td>41</td>
<td>PPD DS</td>
<td>L-6</td>
<td><p>Payload Procedures and Displays Data Set: Final Ground Command
Procedures</p>
<blockquote>
<p>3 months before GCP Book (Final).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>42</td>
<td>C&amp;DH DS (F)</td>
<td>L-6</td>
<td><p>Command and Data Handling Data Set (Final)</p>
<blockquote>
<p>2 months before P/L MDM Configuration Files/PCS Displays (F).<br />
3 months before S/W ICD (F).<br />
2 months before POIC Command &amp; Telemetry<br />
Database (F).</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td></td>
<td>PSI</td>
</tr>
<tr class="odd">
<td>43</td>
<td>KSC SRDS (P)</td>
<td>H/W<br />
O/D-6</td>
<td><p>Kennedy Space Center Support Requirements Data Set
(Preliminary)</p>
<blockquote>
<p>6 months before payload hardware on dock at KSC.<br />
5 months before LSSP Addendum (B/L).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>44</td>
<td>Phase III GSDP</td>
<td>Ph III GSR -45 days</td>
<td><p>Phase III Ground Safety Data Pack</p>
<blockquote>
<p>45 days before Phase lll GSR.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>45</td>
<td>Phase III GSR</td>
<td>L-5.6</td>
<td><p>Phase III Ground Safety Review</p>
<blockquote>
<p>The phase III Safety Review must be completed 30 days prior to
delivery to the launch site. Actual Safety Review date is flexible, but
must consider the complexity of the hardware and operations, potential
safety issues, and whether the safety activities will be required to
support integrated assessments.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>46</td>
<td>Phase III FSDP</td>
<td>Ph III FSR -45 days</td>
<td><p>Phase III Flight Safety Data Pack</p>
<blockquote>
<p>45 days before Phase III FSR.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>47</td>
<td>Phase III FSR</td>
<td>L-5.6</td>
<td><p>Phase III Flight Safety Review</p>
<blockquote>
<p>The phase III Safety Review must be completed 30 days prior to
delivery to the launch site. Actual Safety Review date is flexible, but
must consider the complexity of the hardware and operations, potential
safety issues, and whether the safety activities will be required to
support integrated assessments.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>48</td>
<td>Manifest and Stowage DS (U/D) Bar Codes/IMS and S/N data
(MPLM/Node)</td>
<td>L-5</td>
<td><p>Manifest and Stowage Data Set (Update) – Bar Code/IMS and Serial
Number Data (MPLM/Node)</p>
<blockquote>
<p>L- 1 month from BR (L-5 MPLM/Node).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>49</td>
<td>MPLM/Node HDW O/D &amp; T/O #1 BR KSC</td>
<td>L-5 to L-4.5</td>
<td><p>MPLM/Node Hardware On-Dock and Turn-Over #1 Bench Review at
Kennedy Space Flight Center (dependent on processing requirements)</p>
<blockquote>
<p>2 weeks before the #1 Bench Review.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>50</td>
<td>EMC Test Data (Cargo Bay Payload)</td>
<td>L-5</td>
<td><p>EMC Test Data for Cargo Bay Payloads</p>
<blockquote>
<p>3.5 months before ISS Program/SSP Final EMC Report.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>51</td>
<td>KSC TRDS Orbiter MDK to P/L TGHR Table (P) submittal</td>
<td>L-4.5</td>
<td><p>Kennedy Space Center Technical Requirements Data Set Orbiter
Middeck to Payload Time-Critical Ground Handling Requirements Table
(Preliminary) submittal</p>
<blockquote>
<p>0.5 month before Orbiter MDK TGHR table (P).</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>52</td>
<td>MPLM/Node H/W O/D &amp; T/O #2 BR KSC</td>
<td>L-3</td>
<td><p>MPLM/Node Hardware On-Dock and Turn-Over #2 Bench Review at
Kennedy Space Flight Center</p>
<blockquote>
<p>2 weeks before the #2 Bench Review.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>53</td>
<td>KSC PRCU Testing</td>
<td>L-4.5 to L-3.5</td>
<td><p>Kennedy Space Center Payload Rack Computer Unit Testing</p>
<blockquote>
<p>2.5 months after Payload on-dock KSC.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>54</td>
<td>CoFR OWTL and LPA Inputs</td>
<td>L-3</td>
<td><p>Certificate of Flight Readiness Open Work Tracking Logs and
Launch Package Assessment Inputs</p>
<blockquote>
<p>Open Work Tracking Log (OWTL).<br />
Inputs.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>55</td>
<td>CoFR OZ2 OWTL and LPA Review</td>
<td>L-10 weeks</td>
<td><p>OZ2 Certification of Flight Readiness Open Work Tracking Log and
Launch Package Manager Review</p>
<blockquote>
<p>Potential threats, exceptions, open work.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>56</td>
<td>P/L COC</td>
<td>L-4.5 to L-3.5</td>
<td>Payload Verification Data (Certificates of Compliance)</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PEI</td>
</tr>
<tr class="odd">
<td>57</td>
<td>P/L Test Data for ICA</td>
<td>L-4 and L-2.5</td>
<td><p>Payload Test Data for Interface Control Annex</p>
<blockquote>
<p>Due at L-4 months<br />
Thermal<br />
Structures<br />
Due at L-2.5 months<br />
EMC<br />
Acoustic</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
<tr class="even">
<td>58</td>
<td>VAR</td>
<td>L-3.5</td>
<td><p>Verification Acceptance Review</p>
<blockquote>
<p>3.5 months after VADAR.</p>
</blockquote></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>59</td>
<td>Manifest and Stowage DS – (U/D) Middeck</td>
<td>L-2</td>
<td><p>Manifest and Stowage Data Set – (U/D) Middeck Bar Code/IMS and
Serial Number Data</p>
<blockquote>
<p>2 months before MDK Bench Review.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>60</td>
<td>CoFR OZ OWTL and LPA Review</td>
<td>L-9 weeks</td>
<td><p>OZ Certification of Flight Readiness Open Work Tracking Log and
Launch Package Managers Review</p>
<blockquote>
<p>Potential threats, exceptions, open work.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>61</td>
<td>PPD DS</td>
<td>L-2</td>
<td>Payload Procedures and Displays Data Set: Payload Automated
Procedures (Timeliner Files)</td>
<td>X</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>POIF</td>
</tr>
<tr class="even">
<td>62</td>
<td>CoFR Endorsement Packages Due</td>
<td>L-7 weeks</td>
<td><p>Certification of Flight Readiness Endorsement Packages Due</p>
<blockquote>
<p>-OWTL<br />
-Payload Developer’s Checklist<br />
-Exceptions<br />
-Certification Letter</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>63</td>
<td>CoFR OZ2 Endorsement Package Review</td>
<td>L-6 weeks</td>
<td><p>Certification of Flight Readiness Endorsement Package Review</p>
<blockquote>
<p>Updates to OWTL.<br />
Complete Endorsement Package.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="even">
<td>64</td>
<td>MDK BR H/W O/D JSC</td>
<td>L-1.5 months</td>
<td><p>Middeck Bench Review Hardware On-Dock at Johnson Space Center</p>
<blockquote>
<p>2 weeks before L-1 JSC MDK Bench Review.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>PMI</td>
</tr>
<tr class="odd">
<td>65</td>
<td>MDK HDW O/D KSC (Nominal Installation)</td>
<td>L-22 days to H/W T/O</td>
<td><p>Middeck Hardware On-Dock Kennedy Space Center (Nominal
Installation)</p>
<blockquote>
<p>Approximately 7 working days before MDK T/O KSC for launch.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>66</td>
<td>HDW MDK O/D KSC (Late Installation)</td>
<td>L-15 days to H/W T/O</td>
<td><p>Middeck Hardware On-Dock Kennedy Space Center (Late
Installation)</p>
<blockquote>
<p>Approximately 10 working days before MDK T/O KSC for launch.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="odd">
<td>67</td>
<td>MDK HDW T/O KSC (Nominal Installation)</td>
<td>L-8 days</td>
<td><p>Middeck Hardware Turn-Over Kennedy Space Center (Nominal
Installation)</p>
<blockquote>
<p>Approximately 7 working days after MDK O/D KSC.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="even">
<td>68</td>
<td>MDK HDW T/O KSC (Late Installation)</td>
<td>L-3 days to L-28 hours</td>
<td><p>Middeck Hardware Turn-Over Kennedy Space Center (Late
Installation)</p>
<blockquote>
<p>Approximately 10 working days after MDK O/D KSC.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>KSC</td>
</tr>
<tr class="odd">
<td>69</td>
<td>Lessons Learned Due</td>
<td>Landing + 2 months<br />
Stage + 2 months</td>
<td><p>Lessons Learned Due from the Payload Developer</p>
<blockquote>
<p>2 months after the Landing for Flight Lessons Learned.<br />
2 months after the Stage for Stage Lessons Learned.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td>PMI</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 11%" />
<col style="width: 8%" />
<col style="width: 47%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 5%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 0%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="9"><span id="__RefHeading___Toc177265752"
class="anchor"></span>table 4.0-2 PAYLOAD MISSION INTEGRATION MILESTONE
CHRONOLOGY (7 pages)</th>
<th></th>
</tr>
<tr class="odd">
<th>Line #</th>
<th>Milestone Acronym</th>
<th>Date (Months)</th>
<th>Predecessors And Successors</th>
<th>F</th>
<th>S</th>
<th>Sub</th>
<th>A</th>
<th colspan="2">PMIT</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1</td>
<td>ISS Payload Process Overview</td>
<td>*</td>
<td><p>ISS Payload Process Overview</p>
<p>* Initial PIM meeting with PD following PIM assignment to present the
ISS Payload process Overview (Roadshow). Also will cover optional
services the Program could provide to the PD such as HFIT evaluation,
procedures, displays and OpNom developmental guidance, and operations
concept support.</p></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>2</td>
<td>Export Control Letter Concurrence</td>
<td>*</td>
<td><p>ISS Program concurrence for Export Control Letter</p>
<p>* 1 month after receipt of Export Classification Letter from
PD.</p></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>3</td>
<td>PIA (PCB)</td>
<td>CDR+1</td>
<td>Payload Integration Agreement (Baseline)</td>
<td>X</td>
<td>L-11</td>
<td>X</td>
<td>X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>4</td>
<td>Ops Assessment</td>
<td>L-20</td>
<td><p>Operations Assessment</p>
<blockquote>
<p>2 months after the Ops Assessment Supportability.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>5</td>
<td>Inc Res Plan Kickoff</td>
<td>I-18</td>
<td>Increment Research Plan Kickoff<br />
The Increment Research Plan Kickoff results in the baseline of an
Increment Research Complement at I-15 and resulting PTP CR</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>6</td>
<td>MIP Cargo Bay P/L B/L Input</td>
<td>L-17</td>
<td><p>Mission Integration Plan Cargo Bay (Payload Baseline Input)</p>
<blockquote>
<p>Mission Integration Plan Cargo Bay Payload Baseline.<br />
PTP baseline, coordinate inputs with PIM for ISS payloads.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>7</td>
<td>Feasibility Checklist</td>
<td>I-16</td>
<td>Feasibility Checklist<br />
Completion by the PIMs drives the Feasibility Assessment (I-16 to I-15)
in support of the Increment Research Directive Baseline</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>8</td>
<td>MIP (B/L)</td>
<td>L-16</td>
<td><p>Mission Integration Plan (Baseline)</p>
<blockquote>
<p>7 months before CIR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>9</td>
<td>IDRD (BL)</td>
<td>I-16</td>
<td><p>Increment Definition and Requirements Document (Baseline)</p>
<blockquote>
<p>8 months after IDRP release.<br />
This is an ISS Program product.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>10</td>
<td>Feasibility Assessment</td>
<td>I-16 to I-15</td>
<td>Feasibility Assessment<br />
Feasibility Assessment supports the baseline of the Increment Research
Directive</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>11</td>
<td>IDRD P/L B/L Input</td>
<td>I-15</td>
<td><p>Increment Definition and Requirements Document (Payload Baseline
Input)</p>
<blockquote>
<p>In parallel with PTP development.<br />
2 to 3 months before IDRD Rev A(U/D).</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>12</td>
<td>PTP CR Release</td>
<td>I-15</td>
<td>Payload Tactical Plan Change Request Release<br />
The PTP CR is the resulting formal documentation of the data approved in
the Research Directive and will occur simultaneously with the Research
Directive baseline at the I-15 MPCB.</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>13</td>
<td>Inc Res Dir (B/L)</td>
<td>I-15</td>
<td><p>Increment Research Directive Baseline<br />
The Increment Research Directive baseline initiates the release of the
Increment PTP CR.</p>
<blockquote>
<p>Both occur simultaneously at the I-15 MPCB.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>14</td>
<td>IDRD Annex 1 P/L (B/L) Input -</td>
<td>L-15 to L-12.5</td>
<td><p>Increment Definition and Requirements Document Annex 1 Payload
Baseline Submit</p>
<blockquote>
<p>Post Manifest approval at PCB via Research Post PD Manifest and
Stowage submit.</p>
<p>Before MR cut-off for IDRD Annex 1 B/L.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>15</td>
<td>MIP Annex 1 P/L Input</td>
<td>L-14.5</td>
<td><p>Mission Integration Plan Annex 1 Payload Data Package (Payload
input)</p>
<blockquote>
<p>Input for Cargo Bay Payloads only.<br />
4.5 months before MIP Annex 1 B/L.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>16</td>
<td>MIP Annex 5 P/L Input</td>
<td>L-14.3</td>
<td><p>Mission Integration Plan Annex 5 Payload Operations Control
Center (Payload input)</p>
<blockquote>
<p>7 months before Baseline.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>17</td>
<td>FRD (B/L)</td>
<td>L-13.2</td>
<td><p>Flight Requirements Document (Baseline)</p>
<blockquote>
<p>2.8 months after MIP B/L.<br />
4.2 months before CIR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>18</td>
<td>IDRD Rev A (U/D)</td>
<td>I-12</td>
<td><p>Increment Definition and Requirements Document Revision A
(Update)</p>
<blockquote>
<p>4 months after IDRD (B/L).</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>19</td>
<td>IRR</td>
<td>I-12</td>
<td><p>Increment Requirements Review</p>
<blockquote>
<p>Use PTP latest revision.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>20</td>
<td>IDRD Annex 1<br />
L-12 (B/L)</td>
<td>L-12</td>
<td><p>Increment Definition and Requirements Document Annex 1 L-12
(Baseline)</p>
<blockquote>
<p>3 months before CIR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>21</td>
<td>MIP Annex 4 P/L Input</td>
<td>L-11.6</td>
<td><p>Mission Integration Plan Annex 4 Command and Data (Payload
Input)</p>
<blockquote>
<p>1.8 month minimum before MIP Annex 4 B/L.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>22</td>
<td>P/L ICA Submit Due Date</td>
<td>L-11.1</td>
<td><p>Payload Interface Control Annex Submit Due Date</p>
<blockquote>
<p>2 months weeks before after ICA B/L with the IDRD Annex 1 B/L
data.<br />
2 weeks before ICA B/L CR release.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>23</td>
<td>MIP –Appendix E Submit</td>
<td>L-11.1</td>
<td><p>Mission Integration Plan Appendix E Submit</p>
<blockquote>
<p>3 weeks after ISS Program IDRD Annex 1 manifest approved.<br />
2.1 months prior to CIR to support powered payload requirements and ICA
Baseline.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>24</td>
<td>MIP Annex 2 Part 1 P/L Input</td>
<td>L-11</td>
<td><p>Mission Integration Plan Annex 2 Part 1 Flight Planning (Payload
Input)</p>
<blockquote>
<p>5.1 months before MIP Annex 2, Part 1 B/L.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>25</td>
<td>IDRD Annex 5: PTP (B/L)</td>
<td>I-10</td>
<td>Increment Definition and Requirements Document Annex 5:
Payload Tactical Plan (Baseline)</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>26</td>
<td>IDRD P/L Rev A Input</td>
<td>I-10</td>
<td><p>Increment Definition and Requirements Document Revision A
(Payload Input)</p>
<blockquote>
<p>2 month before IDRD Rev B (U/D).</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>27</td>
<td>IDRD App I Sub to LPMT</td>
<td>L-10</td>
<td>Increment Definition and Requirements Document Appendix I (Transfer
Priorities) Submit due to Launch Package Management Team</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>28</td>
<td>MIP Annex 1 (B/L)</td>
<td>L-10</td>
<td><p>Mission Integration Plan Annex 1 Payload Data Package
(Baseline)</p>
<blockquote>
<p>1 month before CIR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>29</td>
<td>CIRD</td>
<td>L-9.8</td>
<td>Cargo Integration Review Dry Run</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>30</td>
<td>FPSR List</td>
<td>L-9.2</td>
<td>Flight Planning and Stowage Review List</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>31</td>
<td>IDRD P/L Rev B Input</td>
<td>I-9</td>
<td><p>Increment Definition and Requirements Document Revision B
(Payload Input)</p>
<blockquote>
<p>1 month before IDRD U/D to Rev B.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>32</td>
<td>IORR</td>
<td>I-9</td>
<td>Integrated Operation Readiness Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>33</td>
<td>CIR</td>
<td>L-9</td>
<td>Cargo Integration Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>34</td>
<td>ICA (B/L)</td>
<td>L-9</td>
<td>Interface Control Annex (Baseline)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>35</td>
<td>IDRD<br />
ANNEX 3</td>
<td>I-8</td>
<td><p>Increment Definition and Requirements Document Annex 3</p>
<blockquote>
<p>IDRD Annex 3 – Imagery Requirement:<br />
- Orbiter – Docked, Pre, Post<br />
- EVA<br />
- Transfer</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>36</td>
<td>HAMR Rel (MPLM/Node &amp; MDK)</td>
<td>L-8</td>
<td>HAMR Release (MPLM/Node &amp; MDK)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>37</td>
<td>IDRD App I Approval</td>
<td>L-8</td>
<td>Increment Definition and Requirements Document Appendix I (Transfer
Priorities) Approval</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>38</td>
<td>FPSR</td>
<td>L-7.7</td>
<td><p>Flight Planning and Stowage Review</p>
<blockquote>
<p>1.3 months after ICA B/L.<br />
2.3 months after released stowage dwgs and installed P/L dwgs.<br />
Freeze point for Middeck Powered Payload requirements.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>39</td>
<td>MPLM/Node &amp; MDK<br />
H/W Audit</td>
<td>L-7.5</td>
<td><p>MPLM/Node &amp; MDK Hardware Audit</p>
<blockquote>
<p>2 weeks after HAMR release.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>40</td>
<td>MIP Annex 5 (B/L)</td>
<td>L-7.3</td>
<td><p>Mission Integration Plan Annex 5 Payload Operations Control
Center (Baseline)</p>
<blockquote>
<p>4.3 months or greater before JMSTs.<br />
3.5 months before FOR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>41</td>
<td>MIP Annex 4 (B/L)</td>
<td>L-7.7</td>
<td><p>Mission Integration Plan Annex 4 Command and Data (Baseline)</p>
<blockquote>
<p>3 weeks before CIR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>42</td>
<td>VADAR</td>
<td>L-7</td>
<td>VADAR</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>43</td>
<td>MAPs B/L</td>
<td>L-7</td>
<td>MAPs Baselined (MPLM/Node)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>44</td>
<td>IDRD Annex 1 L-6 (U/D)</td>
<td>L-6</td>
<td><p>Increment Definition and Requirements Document Annex 1 L-6
(Update)</p>
<blockquote>
<p>2 months before FOR.<br />
1 month after IDRD Annex 1 (L-6) MR Cut-off.<br />
3 months after IDRD Annex 1 (L-9) Update.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>45</td>
<td>OZ2 CoFR Pre-Coord Rev</td>
<td>L-5</td>
<td>Certification of Flight Readiness Pre-Coordination Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>46</td>
<td>MIP Annex 2 Part 1 (B/L)</td>
<td>L-4.9</td>
<td>Mission Integration Plan Annex 2, Part 1 Flight Planning
(Baseline)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>47</td>
<td>OZ2 Bilateral CoFR Pre-Coord Rev</td>
<td>L-4.5</td>
<td>OZ2 Bilateral Certification of Flight Readiness Pre-Coordination
Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>48</td>
<td>HAMR MDK</td>
<td>L-4.5</td>
<td>HAMR Release (MDK Only)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>49</td>
<td>IOR</td>
<td>I-4</td>
<td><p>Increment Operations Review</p>
<blockquote>
<p>2.5 months after P/L OOS (B).<br />
2.5 months after P/L GR&amp;C (B).</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>50</td>
<td>Release CoFR OZ Instruction Letter</td>
<td>L-4</td>
<td>Release OZ Certification of Flight Readiness Instruction Letter</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>51</td>
<td>SSCCD (F)</td>
<td>L-4</td>
<td><p>Space Station Configuration Control Drawings (Final)</p>
<blockquote>
<p>2 weeks before Bench Review.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>52</td>
<td>MPLM/Node Phase III FSDP</td>
<td>L-4</td>
<td><p>MPLM/Node Phase III Flight Safety Data Package</p>
<blockquote>
<p>1.5 month before the MPLM/Node Phase III FSR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>53</td>
<td>MPLM/NODE BR #1 KSC</td>
<td>L-4</td>
<td>MPLM/NODE Bench Review #1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>54</td>
<td>MDK HDW Audit</td>
<td>L-4</td>
<td><p>Middeck Hardware Audit</p>
<blockquote>
<p>2 weeks after HAMR Release.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>55</td>
<td>HDW BR JSC</td>
<td>L-3.75</td>
<td>Hardware Bench Review JSC</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>56</td>
<td>FOR</td>
<td>L-3.7</td>
<td><p>Flight Operations Review</p>
<blockquote>
<p>3 weeks before the Start of JMST.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>57</td>
<td>CoFR OWTL &amp; LPA Inputs</td>
<td>L-3</td>
<td>Certification of Flight Readiness Open Work Tracking Log and Launch
Package Assessment Inputs Due</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>58</td>
<td>MPLM/NODE BR #2</td>
<td>L-3</td>
<td>MPLM/NODE Bench Review #2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>59</td>
<td>OFK Submit to SSP</td>
<td>L-3</td>
<td>Official Flight Kit (OFK) Submit to SSP due date</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>60</td>
<td>CCCR Freeze</td>
<td>L-3</td>
<td><p>CCCR Freeze</p>
<blockquote>
<p>1 months before CCCR.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>61</td>
<td>IDRD Annex 1 L-3 (U/D)</td>
<td>L-3</td>
<td><p>Increment Definition and Requirements Document Annex 1 L-3
(Update)</p>
<blockquote>
<p>CR to support CCCR Freeze.<br />
3 months after IDRD Annex 1 (L-6) Update.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>62</td>
<td>CCCD Release</td>
<td>L-2</td>
<td>Crew Configuration Compartment Drawings</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>63</td>
<td>OZ2 OWTL &amp; LPA Rev</td>
<td>L-10 weeks</td>
<td>OZ2 Open Work Tracking Log and Launch Package Assessment Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>64</td>
<td>OZ OWTL &amp; LPA Rev</td>
<td>L-9 weeks</td>
<td>OZ Open Work Tracking Log and Launch Package Assessment Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>65</td>
<td>MPLM/Node Phase III FSR</td>
<td>L-2.5</td>
<td>MPLM/Node Phase III Flight Safety Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>66</td>
<td>OFK Items Del</td>
<td>L-2</td>
<td>Official Flight Kit Items Delivered</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>67</td>
<td>CCCR</td>
<td>L-2</td>
<td><p>Crew Configuration Compartment Review</p>
<blockquote>
<p>1 month after CCCR Freeze.<br />
1 month after CCCD Released.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>68</td>
<td>ISS Program LPA</td>
<td>L-7 weeks</td>
<td>International Space Station Program Launch Package Assessment</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>69</td>
<td>CoFR Endorsement Pack Due</td>
<td>L-7 weeks</td>
<td>Certification of Flight Readiness Endorsement Packages Due</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>70</td>
<td>OZ2 CoFR Endorsement Pack Rev</td>
<td>L-6 weeks</td>
<td>OZ2 Certification of Flight Readiness Endorsement Package
Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>71</td>
<td>IP/P CoFR RR</td>
<td>L-5.5 weeks</td>
<td>IP/P Certification of Flight Readiness Readiness Review (OZ
participation, as required)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>72</td>
<td>IRR Kickoff</td>
<td>L-4 weeks from HDW Installation</td>
<td>Increment Requirements Review (IRR) Kick-Off (MPLM/Node Only
Flights)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>73</td>
<td>CSRD</td>
<td>L-3.5 weeks</td>
<td>CSRD</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>74</td>
<td>Transfer List</td>
<td>L3 weeks</td>
<td>Transfer List Reviews begin</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>75</td>
<td>IDRD Annex 1 L-6 weeks (U/D) and subsequent</td>
<td>L-6 weeks to L-2 weeks</td>
<td><p>Increment Definition and Requirements Document Annex 1 L-6 weeks
(Update)</p>
<blockquote>
<p>Weekly update as required.<br />
1 week after IDRD Annex 1 weekly MR Cut-off.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>76</td>
<td>CoFR OZ Multilateral Readiness Review</td>
<td>L-4.5 weeks</td>
<td><p>OZ Certification of Flight Readiness Multilateral Readiness
Review</p>
<blockquote>
<p>1 week before SORR.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>77</td>
<td>MPLM/Node HDW BR #1 KSC</td>
<td>L-4</td>
<td><p>Multi-Purpose Logistics Module/Node Hardware Bench Review #1
Kennedy Space Center</p>
<blockquote>
<p>MPLM HDW Bench Review #1 at Kennedy Space Center.<br />
1 month after H/W O/D.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>78</td>
<td>HDW VER REV</td>
<td>L-1 w from BR</td>
<td>Hardware Verification Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>79</td>
<td>IDRD Annex 2 B/L Flt Req</td>
<td>L-1.75</td>
<td>Increment Definition and Requirements Document Annex 3 Baseline
(Flight Requirements)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>80</td>
<td>ICA Res for L-10 Day BR sub</td>
<td>L-1.3</td>
<td>Interface Control Annex Reserve for L-10 days Bench Review
Submit</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>81</td>
<td>MDK HDW BR JSC</td>
<td>L-1</td>
<td><p>Middeck Hardware Bench Review at Johnson Space Center</p>
<blockquote>
<p>2 weeks after H/W O/D.</p>
</blockquote></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>82</td>
<td>ICA Res CR Approval for L-10 days BR Appr</td>
<td>L-28 days</td>
<td>Interface Control Annex Reserve Change Request for L-10 days Bench
Review Approval</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>83</td>
<td>SORR</td>
<td>L-3.5 weeks</td>
<td><p>Stage Operations Readiness Review</p>
<blockquote>
<p>2.5 weeks after CoFR submittal.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>84</td>
<td>CCCD Rel for L-10 days BR</td>
<td>L-18 days</td>
<td>CCCD Release for L-10 days Bench Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>85</td>
<td>FRR</td>
<td>L-2 weeks</td>
<td>Flight Readiness Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>86</td>
<td>HDW O/D L-10 days BR</td>
<td>L-2 weeks from BR</td>
<td>Hardware On-Dock L-10 days Bench Review</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>87</td>
<td>IRR Final</td>
<td>L-2 weeks from HDW Installation</td>
<td>Installation Readiness Review Final (MPLM/NODE Only Flights)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td>88</td>
<td>MDK L-10 Day BR (JSC)</td>
<td>L-10 days</td>
<td><p>L-10 day Middeck Bench Review at Johnson Space Center</p>
<blockquote>
<p>2 weeks after H/W O/D.</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>89</td>
<td>EIRR</td>
<td>Testing Start –<br />
4 weeks</td>
<td><p>EXPRESS Integration Readiness Review</p>
<blockquote>
<p>4 weeks before testing.</p>
</blockquote></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>90</td>
<td>RMDP Rel</td>
<td>L-2 days</td>
<td>RMDP Release</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td>91</td>
<td>RMDP B/L</td>
<td>Launch</td>
<td>RMDP Baseline</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2">X</td>
</tr>
</tbody>
</table>

+---+-------+----+---------------------------------+---+---+---+---+---+
| [ |       |    |                                 |   |   |   |   |   |
| ] |       |    |                                 |   |   |   |   |   |
| { |       |    |                                 |   |   |   |   |   |
| # |       |    |                                 |   |   |   |   |   |
| _ |       |    |                                 |   |   |   |   |   |
| _ |       |    |                                 |   |   |   |   |   |
| R |       |    |                                 |   |   |   |   |   |
| e |       |    |                                 |   |   |   |   |   |
| f |       |    |                                 |   |   |   |   |   |
| H |       |    |                                 |   |   |   |   |   |
| e |       |    |                                 |   |   |   |   |   |
| a |       |    |                                 |   |   |   |   |   |
| d |       |    |                                 |   |   |   |   |   |
| i |       |    |                                 |   |   |   |   |   |
| n |       |    |                                 |   |   |   |   |   |
| g |       |    |                                 |   |   |   |   |   |
| _ |       |    |                                 |   |   |   |   |   |
| _ |       |    |                                 |   |   |   |   |   |
| _ |       |    |                                 |   |   |   |   |   |
| T |       |    |                                 |   |   |   |   |   |
| o |       |    |                                 |   |   |   |   |   |
| c |       |    |                                 |   |   |   |   |   |
| 1 |       |    |                                 |   |   |   |   |   |
| 7 |       |    |                                 |   |   |   |   |   |
| 7 |       |    |                                 |   |   |   |   |   |
| 2 |       |    |                                 |   |   |   |   |   |
| 6 |       |    |                                 |   |   |   |   |   |
| 5 |       |    |                                 |   |   |   |   |   |
| 7 |       |    |                                 |   |   |   |   |   |
| 5 |       |    |                                 |   |   |   |   |   |
| 3 |       |    |                                 |   |   |   |   |   |
| . |       |    |                                 |   |   |   |   |   |
| a |       |    |                                 |   |   |   |   |   |
| n |       |    |                                 |   |   |   |   |   |
| c |       |    |                                 |   |   |   |   |   |
| h |       |    |                                 |   |   |   |   |   |
| o |       |    |                                 |   |   |   |   |   |
| r |       |    |                                 |   |   |   |   |   |
| } |       |    |                                 |   |   |   |   |   |
| t |       |    |                                 |   |   |   |   |   |
| a |       |    |                                 |   |   |   |   |   |
| b |       |    |                                 |   |   |   |   |   |
| l |       |    |                                 |   |   |   |   |   |
| e |       |    |                                 |   |   |   |   |   |
| 4 |       |    |                                 |   |   |   |   |   |
| . |       |    |                                 |   |   |   |   |   |
| 0 |       |    |                                 |   |   |   |   |   |
| - |       |    |                                 |   |   |   |   |   |
| 3 |       |    |                                 |   |   |   |   |   |
| P |       |    |                                 |   |   |   |   |   |
| A |       |    |                                 |   |   |   |   |   |
| Y |       |    |                                 |   |   |   |   |   |
| L |       |    |                                 |   |   |   |   |   |
| O |       |    |                                 |   |   |   |   |   |
| A |       |    |                                 |   |   |   |   |   |
| D |       |    |                                 |   |   |   |   |   |
| E |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| G |       |    |                                 |   |   |   |   |   |
| I |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| E |       |    |                                 |   |   |   |   |   |
| E |       |    |                                 |   |   |   |   |   |
| R |       |    |                                 |   |   |   |   |   |
| I |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| G |       |    |                                 |   |   |   |   |   |
| I |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| T |       |    |                                 |   |   |   |   |   |
| E |       |    |                                 |   |   |   |   |   |
| G |       |    |                                 |   |   |   |   |   |
| R |       |    |                                 |   |   |   |   |   |
| A |       |    |                                 |   |   |   |   |   |
| T |       |    |                                 |   |   |   |   |   |
| I |       |    |                                 |   |   |   |   |   |
| O |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| M |       |    |                                 |   |   |   |   |   |
| I |       |    |                                 |   |   |   |   |   |
| L |       |    |                                 |   |   |   |   |   |
| E |       |    |                                 |   |   |   |   |   |
| S |       |    |                                 |   |   |   |   |   |
| T |       |    |                                 |   |   |   |   |   |
| O |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| E |       |    |                                 |   |   |   |   |   |
| C |       |    |                                 |   |   |   |   |   |
| H |       |    |                                 |   |   |   |   |   |
| R |       |    |                                 |   |   |   |   |   |
| O |       |    |                                 |   |   |   |   |   |
| N |       |    |                                 |   |   |   |   |   |
| O |       |    |                                 |   |   |   |   |   |
| L |       |    |                                 |   |   |   |   |   |
| O |       |    |                                 |   |   |   |   |   |
| G |       |    |                                 |   |   |   |   |   |
| Y |       |    |                                 |   |   |   |   |   |
| ( |       |    |                                 |   |   |   |   |   |
| 3 |       |    |                                 |   |   |   |   |   |
| p |       |    |                                 |   |   |   |   |   |
| a |       |    |                                 |   |   |   |   |   |
| g |       |    |                                 |   |   |   |   |   |
| e |       |    |                                 |   |   |   |   |   |
| s |       |    |                                 |   |   |   |   |   |
| ) |       |    |                                 |   |   |   |   |   |
+===+=======+====+=================================+===+===+===+===+===+
| L | Mile  | Da | Predecessors And Successors     | F | S | S | A | P |
| i | stone | te |                                 |   |   | u |   | M |
| n | Ac    | (M |                                 |   |   | b |   | I |
| e | ronym | on |                                 |   |   |   |   | T |
| \ |       | th |                                 |   |   |   |   |   |
| # |       | s) |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | Dr    | C  | IPLAT Initial Label Evaluation  | X | C | C | X |   |
|   | awing | DR | of (Pre-released) Crew          |   | D | D |   |   |
|   | DS -  | +4 | Interface Label Drawings        |   | R | R |   |   |
|   | Crew  | .5 |                                 |   | + | + |   |   |
|   | I/F   |    | > 2 weeks after submittal of    |   | 6 | 6 |   |   |
|   | Label |    | > Crew Interface Label Drawings |   | . | . |   |   |
|   | Dwgs  |    | > (Pre-released).               |   | 5 | 5 |   |   |
|   | (     |    |                                 |   |   |   |   |   |
|   | IPLAT |    | IPLAT returns ISS Payload Label |   |   |   |   |   |
|   | Label |    | Verification checklist to PD    |   |   |   |   |   |
|   | E     |    | containing IPLAT concurrence or |   |   |   |   |   |
|   | valua |    | recommendations. The PD will    |   |   |   |   |   |
|   | tion) |    | make corrections to label       |   |   |   |   |   |
|   | (P)   |    | design if violations occur.     |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 2 | H/W   | C  | Hardware Interface Control      | X | X | X | X |   |
|   | ICD   | DR | Document (Draft) only contains  |   |   |   |   |   |
|   | (D    | +1 | "design-to" data and            |   |   |   |   |   |
|   | RAFT) |    | verification applicability      |   |   |   |   |   |
|   |       |    | matrix except for subrack       |   |   |   |   |   |
|   |       |    | payloads which will also have   |   |   |   |   |   |
|   |       |    | "mission-unique" data           |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 3 | H/W   | L- | Hardware Interface Control      | X | X | X | X | X |
|   | ICD   | 12 | Document (Baseline)             |   |   |   |   |   |
|   | (B/L) |    |                                 |   |   |   |   |   |
|   |       |    | > 2 months after PD submit of   |   |   |   |   |   |
|   |       |    | > mission unique data.          |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 4 | Dr    | L- | On-Orbit Configuration Drawing, | X |   |   |   |   |
|   | awing | 11 | EXPRESS/WORF (Preliminary)      |   |   |   |   |   |
|   | DS -  |    |                                 |   |   |   |   |   |
|   | On-   |    | > 5 months before B/L.\         |   |   |   |   |   |
|   | Orbit |    | > This milestone is applicable  |   |   |   |   |   |
|   | Con   |    | > at the integrated EXPRESS or  |   |   |   |   |   |
|   | figur |    | > integrated WORF rack level    |   |   |   |   |   |
|   | ation |    | > only. It does not apply to    |   |   |   |   |   |
|   | Dra   |    | > Subrack level payloads.       |   |   |   |   |   |
|   | wing, |    |                                 |   |   |   |   |   |
|   | EXPR  |    |                                 |   |   |   |   |   |
|   | ESS/\ |    |                                 |   |   |   |   |   |
|   | WORF  |    |                                 |   |   |   |   |   |
|   | (P)   |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 5 | Dr    | L- | Assembly and Installation       | X |   |   |   |   |
|   | awing | 11 | Drawings, EXPRESS/WORF          |   |   |   |   |   |
|   | DS -  |    | (Preliminary)                   |   |   |   |   |   |
|   | A&I   |    |                                 |   |   |   |   |   |
|   | Draw  |    | > 5 months before B/L.\         |   |   |   |   |   |
|   | ings, |    | > This milestone is applicable  |   |   |   |   |   |
|   | EX    |    | > at the integrated EXPRESS or  |   |   |   |   |   |
|   | PRESS |    | > integrated WORF rack level    |   |   |   |   |   |
|   | /WORF |    | > only. It does not apply to    |   |   |   |   |   |
|   | (P)   |    | > Subrack level payloads.       |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 6 | Pa    | L  | Payload Exceptions to the IDD   | X | X | X | X |   |
|   | yload | -9 |                                 |   |   |   |   |   |
|   | Excep | .5 |                                 |   |   |   |   |   |
|   | tions |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 7 | Dr    | I  | IPLAT Final Label Evaluation of | X | X | X | X |   |
|   | awing | -7 | (Released) Crew Interface Label |   |   |   |   |   |
|   | DS -- | .5 | Drawings                        |   |   |   |   |   |
|   | Crew  |    |                                 |   |   |   |   |   |
|   | I/F   |    | > 2 weeks after submittal of    |   |   |   |   |   |
|   | Label |    | > Crew Interface Label Drawings |   |   |   |   |   |
|   | Dwgs  |    | > (Released).\                  |   |   |   |   |   |
|   | (     |    | > Before Bench Review.          |   |   |   |   |   |
|   | IPLAT |    |                                 |   |   |   |   |   |
|   | Label |    | IPLAT will issue JSC Form 732   |   |   |   |   |   |
|   | E     |    | Label Approval.\                |   |   |   |   |   |
|   | valua |    | JSC Form 732 will be included   |   |   |   |   |   |
|   | tion) |    | into HFIT CoC and Form 883.     |   |   |   |   |   |
|   | (F)   |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 8 | Dr    | L  | On-Orbit Configuration Drawing, | X |   |   |   |   |
|   | awing | -6 | EXPRESS/WORF (Baseline)         |   |   |   |   |   |
|   | DS -  |    |                                 |   |   |   |   |   |
|   | On-   |    | > 5 months after Preliminary.\  |   |   |   |   |   |
|   | Orbit |    | > This milestone is applicable  |   |   |   |   |   |
|   | Con   |    | > at the integrated EXPRESS or  |   |   |   |   |   |
|   | figur |    | > integrated WORF rack level    |   |   |   |   |   |
|   | ation |    | > only. It does not apply to    |   |   |   |   |   |
|   | Dra   |    | > Subrack level payloads.       |   |   |   |   |   |
|   | wing, |    |                                 |   |   |   |   |   |
|   | EX    |    |                                 |   |   |   |   |   |
|   | PRESS |    |                                 |   |   |   |   |   |
|   | /WORF |    |                                 |   |   |   |   |   |
|   | (B/L) |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 9 | Dr    | L  | Assembly and Installation       | X |   |   |   |   |
|   | awing | -6 | Drawings, EXPRESS/WORF          |   |   |   |   |   |
|   | DS -  |    | (Baseline)                      |   |   |   |   |   |
|   | A&I   |    |                                 |   |   |   |   |   |
|   | Draw  |    | > 5 months after Preliminary.\  |   |   |   |   |   |
|   | ings, |    | > This milestone is applicable  |   |   |   |   |   |
|   | EX    |    | > at the integrated EXPRESS or  |   |   |   |   |   |
|   | PRESS |    | > integrated WORF rack level    |   |   |   |   |   |
|   | /WORF |    | > only. It does not apply to    |   |   |   |   |   |
|   | (B/L) |    | > Subrack level payloads.       |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | Dr    | L  | Stage Configuration Drawings    | X | X |   |   |   |
| 0 | awing | -6 | (Preliminary)                   |   |   |   |   |   |
|   | DS -- |    |                                 |   |   |   |   |   |
|   | Stage |    | > 3.5 months before B/L.        |   |   |   |   |   |
|   | Con   |    |                                 |   |   |   |   |   |
|   | figur |    |                                 |   |   |   |   |   |
|   | ation |    |                                 |   |   |   |   |   |
|   | Dr    |    |                                 |   |   |   |   |   |
|   | awing |    |                                 |   |   |   |   |   |
|   | (P)   |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | E     | L  | Drawing Data Set: Engineering   | X | X | X | X |   |
| 1 | ngine | -6 | Configuration List (ECL)        |   |   |   |   |   |
|   | ering |    | (Baseline)                      |   |   |   |   |   |
|   | Con   |    |                                 |   |   |   |   |   |
|   | figur |    | > Parts List only -- no drawing |   |   |   |   |   |
|   | ation |    | > sheets.                       |   |   |   |   |   |
|   | List  |    |                                 |   |   |   |   |   |
|   | (ECL) |    |                                 |   |   |   |   |   |
|   | (B/L) |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | EXPR  | L  | EXPRESS/WORF Compatibility      |   |   | X |   |   |
| 2 | ESS/\ | -6 | Analysis Report for Stage XX    |   |   |   |   |   |
|   | WORF  |    |                                 |   |   |   |   |   |
|   | Com   |    |                                 |   |   |   |   |   |
|   | patib |    |                                 |   |   |   |   |   |
|   | ility |    |                                 |   |   |   |   |   |
|   | Ana   |    |                                 |   |   |   |   |   |
|   | lysis |    |                                 |   |   |   |   |   |
|   | R     |    |                                 |   |   |   |   |   |
|   | eport |    |                                 |   |   |   |   |   |
|   | for   |    |                                 |   |   |   |   |   |
|   | Stage |    |                                 |   |   |   |   |   |
|   | XX    |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | HFIT  | L  | Issued CoC and Form 883 after   | X | X | X |   |   |
| 3 | Final | -4 | Form 882 is completely closed.  |   |   |   |   |   |
|   | Har   | .5 |                                 |   |   |   |   |   |
|   | dware |    |                                 |   |   |   |   |   |
|   | Evalu |    |                                 |   |   |   |   |   |
|   | ation |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | E     | L  | Payload Element Level           | X | X |   | X | X |
| 4 | ngine | -4 | Engineering Analysis Report     |   |   |   |   |   |
|   | ering | .5 |                                 |   |   |   |   |   |
|   | Stage |    | > 3 months after PD submittal   |   |   |   |   |   |
|   | Ana   |    | > of Stage Analysis             |   |   |   |   |   |
|   | lysis |    | > verification data.            |   |   |   |   |   |
|   | R     |    |                                 |   |   |   |   |   |
|   | eport |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | GL&C  | L  | Payload Operations Guidelines   | X | X | X | X | X |
| 5 |       | -4 | and Constraints Element-Level   |   |   |   |   |   |
|   |       |    | Report                          |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | Dr    | L  | Stage Configuration Drawings    | X | X |   |   |   |
| 6 | awing | -2 | (Baseline)                      |   |   |   |   |   |
|   | DS -  | .5 |                                 |   |   |   |   |   |
|   | Stage |    | > 3.5 months after Preliminary. |   |   |   |   |   |
|   | Con   |    |                                 |   |   |   |   |   |
|   | figur |    |                                 |   |   |   |   |   |
|   | ation |    |                                 |   |   |   |   |   |
|   | Dra   |    |                                 |   |   |   |   |   |
|   | wings |    |                                 |   |   |   |   |   |
|   | (B/L) |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | ISS   | L  | Payload Element Level Stage     | X | X | X | X | X |
| 7 | Level | -3 | Analysis Report                 |   |   |   |   |   |
|   | P/L   |    |                                 |   |   |   |   |   |
|   | Compl |    |                                 |   |   |   |   |   |
|   | ement |    |                                 |   |   |   |   |   |
|   | Ana   |    |                                 |   |   |   |   |   |
|   | lysis |    |                                 |   |   |   |   |   |
|   | r     |    |                                 |   |   |   |   |   |
|   | eport |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+
| 1 | P/L   | L  | Payload Engineering             | X | X | X | X | X |
| 8 | E     | -6 | Verification Memo -- Stage      |   |   |   |   |   |
|   | ngine | w  | Level                           |   |   |   |   |   |
|   | ering | ee |                                 |   |   |   |   |   |
|   | Ve    | ks | > Before SORR activity start.   |   |   |   |   |   |
|   | rific |    |                                 |   |   |   |   |   |
|   | ation |    |                                 |   |   |   |   |   |
|   | Memo  |    |                                 |   |   |   |   |   |
+---+-------+----+---------------------------------+---+---+---+---+---+

[]{#__RefHeading___Toc177265754 .anchor}table 4.0-4 PAYLOAD SOFTWARE
INTEGRATION MILESTONE CHRONOLOGY

+----+------+------+-------------------------------+---+---+---+---+---+
| Li | M    | Date | Predecessors And Successors   | F | S | S | A | P |
| ne | iles | (Mon |                               |   |   | u |   | M |
| \# | tone | ths) |                               |   |   | b |   | I |
|    | Acr  |      |                               |   |   |   |   | T |
|    | onym |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 1  | P/L  | L-14 | Payload MDM Configuration     | X |   | X | X |   |
|    | MDM  |      | Files/Portable Computer       |   |   |   |   |   |
|    | C    |      | System Displays (Preliminary) |   |   |   |   |   |
|    | onfi |      |                               |   |   |   |   |   |
|    | gura |      | > 2 months after Preliminary  |   |   |   |   |   |
|    | tion |      | > C&DH data set.\             |   |   |   |   |   |
|    | F    |      | > 2 months before Preliminary |   |   |   |   |   |
|    | iles |      | > S/W ICD.                    |   |   |   |   |   |
|    | /PCS |      |                               |   |   |   |   |   |
|    | Disp |      |                               |   |   |   |   |   |
|    | lays |      |                               |   |   |   |   |   |
|    | (P)  |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 2  | S/W  | L-12 | Software Interface Control    | X |   | X | X |   |
|    | ICD  |      | Document (Preliminary)        |   |   |   |   |   |
|    | (P)  |      |                               |   |   |   |   |   |
|    |      |      | > 4 months before S/W ICD     |   |   |   |   |   |
|    |      |      | > (I).                        |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 3  | S/W  | L-8  | Software Interface Control    | X |   | X | X |   |
|    | ICD  |      | Document (Interim)            |   |   |   |   |   |
|    | (I)  |      |                               |   |   |   |   |   |
|    |      |      | > 4 months after S/W ICD      |   |   |   |   |   |
|    |      |      | > (P).\                       |   |   |   |   |   |
|    |      |      | > 1 month before P/L MDM      |   |   |   |   |   |
|    |      |      | > Configuration Files/PCS     |   |   |   |   |   |
|    |      |      | > Displays (I).\              |   |   |   |   |   |
|    |      |      | > Submit to S/W ICD (F).      |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 4  | P/L  | L-7  | Payload MDM Configuration     | X |   | X | X |   |
|    | MDM  |      | Files/Portable Computer       |   |   |   |   |   |
|    | C    |      | System Displays (Interim)     |   |   |   |   |   |
|    | onfi |      |                               |   |   |   |   |   |
|    | gura |      | > 2 months after Interim C&DH |   |   |   |   |   |
|    | tion |      | > data set.\                  |   |   |   |   |   |
|    | F    |      | > 1 month after Interim S/W   |   |   |   |   |   |
|    | iles |      | > ICD.                        |   |   |   |   |   |
|    | /PCS |      |                               |   |   |   |   |   |
|    | Disp |      |                               |   |   |   |   |   |
|    | lays |      |                               |   |   |   |   |   |
|    | (I)  |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 5  | P/L  | L-4  | Payload MDM Configuration     | X |   | X | X |   |
|    | MDM  |      | Files/Portable Computer       |   |   |   |   |   |
|    | C    |      | System Displays (Final)       |   |   |   |   |   |
|    | onfi |      |                               |   |   |   |   |   |
|    | gura |      | > 2 months after Final C&DH   |   |   |   |   |   |
|    | tion |      | > data set.\                  |   |   |   |   |   |
|    | F    |      | > 1 month before Final S/W    |   |   |   |   |   |
|    | iles |      | > ICD.                        |   |   |   |   |   |
|    | /PCS |      |                               |   |   |   |   |   |
|    | Disp |      |                               |   |   |   |   |   |
|    | lays |      |                               |   |   |   |   |   |
|    | (F)  |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 6  | S/W  | L-3  | Software Interface Control    | X |   | X | X |   |
|    | ICD  |      | Document (Final)              |   |   |   |   |   |
|    | (F)  |      |                               |   |   |   |   |   |
|    |      |      | > 5 months after S/W ICD (I). |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+

+---+------+------+------------------------------+----+---+---+---+---+
| [ |      |      |                              |    |   |   |   |   |
| ] |      |      |                              |    |   |   |   |   |
| { |      |      |                              |    |   |   |   |   |
| # |      |      |                              |    |   |   |   |   |
| _ |      |      |                              |    |   |   |   |   |
| _ |      |      |                              |    |   |   |   |   |
| R |      |      |                              |    |   |   |   |   |
| e |      |      |                              |    |   |   |   |   |
| f |      |      |                              |    |   |   |   |   |
| H |      |      |                              |    |   |   |   |   |
| e |      |      |                              |    |   |   |   |   |
| a |      |      |                              |    |   |   |   |   |
| d |      |      |                              |    |   |   |   |   |
| i |      |      |                              |    |   |   |   |   |
| n |      |      |                              |    |   |   |   |   |
| g |      |      |                              |    |   |   |   |   |
| _ |      |      |                              |    |   |   |   |   |
| _ |      |      |                              |    |   |   |   |   |
| _ |      |      |                              |    |   |   |   |   |
| T |      |      |                              |    |   |   |   |   |
| o |      |      |                              |    |   |   |   |   |
| c |      |      |                              |    |   |   |   |   |
| 1 |      |      |                              |    |   |   |   |   |
| 7 |      |      |                              |    |   |   |   |   |
| 7 |      |      |                              |    |   |   |   |   |
| 2 |      |      |                              |    |   |   |   |   |
| 6 |      |      |                              |    |   |   |   |   |
| 5 |      |      |                              |    |   |   |   |   |
| 7 |      |      |                              |    |   |   |   |   |
| 5 |      |      |                              |    |   |   |   |   |
| 5 |      |      |                              |    |   |   |   |   |
| . |      |      |                              |    |   |   |   |   |
| a |      |      |                              |    |   |   |   |   |
| n |      |      |                              |    |   |   |   |   |
| c |      |      |                              |    |   |   |   |   |
| h |      |      |                              |    |   |   |   |   |
| o |      |      |                              |    |   |   |   |   |
| r |      |      |                              |    |   |   |   |   |
| } |      |      |                              |    |   |   |   |   |
| t |      |      |                              |    |   |   |   |   |
| a |      |      |                              |    |   |   |   |   |
| b |      |      |                              |    |   |   |   |   |
| l |      |      |                              |    |   |   |   |   |
| e |      |      |                              |    |   |   |   |   |
| 4 |      |      |                              |    |   |   |   |   |
| . |      |      |                              |    |   |   |   |   |
| 0 |      |      |                              |    |   |   |   |   |
| - |      |      |                              |    |   |   |   |   |
| 5 |      |      |                              |    |   |   |   |   |
| P |      |      |                              |    |   |   |   |   |
| A |      |      |                              |    |   |   |   |   |
| Y |      |      |                              |    |   |   |   |   |
| L |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| A |      |      |                              |    |   |   |   |   |
| D |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| P |      |      |                              |    |   |   |   |   |
| E |      |      |                              |    |   |   |   |   |
| R |      |      |                              |    |   |   |   |   |
| A |      |      |                              |    |   |   |   |   |
| T |      |      |                              |    |   |   |   |   |
| I |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| S |      |      |                              |    |   |   |   |   |
| I |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| T |      |      |                              |    |   |   |   |   |
| E |      |      |                              |    |   |   |   |   |
| G |      |      |                              |    |   |   |   |   |
| R |      |      |                              |    |   |   |   |   |
| A |      |      |                              |    |   |   |   |   |
| T |      |      |                              |    |   |   |   |   |
| I |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| F |      |      |                              |    |   |   |   |   |
| U |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| C |      |      |                              |    |   |   |   |   |
| T |      |      |                              |    |   |   |   |   |
| I |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| M |      |      |                              |    |   |   |   |   |
| I |      |      |                              |    |   |   |   |   |
| L |      |      |                              |    |   |   |   |   |
| E |      |      |                              |    |   |   |   |   |
| S |      |      |                              |    |   |   |   |   |
| T |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| E |      |      |                              |    |   |   |   |   |
| C |      |      |                              |    |   |   |   |   |
| H |      |      |                              |    |   |   |   |   |
| R |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| N |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| L |      |      |                              |    |   |   |   |   |
| O |      |      |                              |    |   |   |   |   |
| G |      |      |                              |    |   |   |   |   |
| Y |      |      |                              |    |   |   |   |   |
| ( |      |      |                              |    |   |   |   |   |
| 3 |      |      |                              |    |   |   |   |   |
| p |      |      |                              |    |   |   |   |   |
| a |      |      |                              |    |   |   |   |   |
| g |      |      |                              |    |   |   |   |   |
| e |      |      |                              |    |   |   |   |   |
| s |      |      |                              |    |   |   |   |   |
| ) |      |      |                              |    |   |   |   |   |
+===+======+======+==============================+====+===+===+===+===+
| L | M    | Date | Predecessors And Successors  | F  | S | S | A | P |
| i | iles | (Mon |                              |    |   | u |   | M |
| n | tone | ths) |                              |    |   | b |   | I |
| e | Acr  |      |                              |    |   |   |   | T |
| \ | onym |      |                              |    |   |   |   |   |
| # |      |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | PPD  | I-13 | Payload Procedures &         | X  | I | I | X |   |
|   | DS   |      | Displays Data Set: ECR to    |    | - | - |   |   |
|   | Disp |      | Baseline Displays            |    | 1 | 1 |   |   |
|   | lays |      |                              |    | 1 | 1 |   |   |
|   | (ECR |      | > 5 month after Usability    |    |   |   |   |   |
|   | to   |      | > Verification.              |    |   |   |   |   |
|   | B/L) |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | Refl | I-18 | Training for "Reflight"      |    | I | I | I |   |
|   | ight |      | Payloads                     |    | - | - | - |   |
|   | P/L  |      |                              |    | 1 | 1 | 1 |   |
|   | Trai |      | > Reflight Pressurized       |    | 6 | 6 | 6 |   |
|   | ning |      | > facility (rack-level)      |    |   |   |   |   |
|   |      |      | > payloads not requiring PD  |    |   |   |   |   |
|   |      |      | > training support could     |    |   |   |   |   |
|   |      |      | > start earlier.\            |    |   |   |   |   |
|   |      |      | > 12 months before Start     |    |   |   |   |   |
|   |      |      | > Complement Training.       |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 3 | P    | I-16 | Procedures Tabletop          | X  | I | I | X |   |
|   | roce |      |                              |    | - | - |   |   |
|   | dure |      | > After first procedure      |    | 1 | 1 |   |   |
|   | Tabl |      | > delivery.\                 |    | 4 | 4 |   |   |
|   | etop |      | > Before Usability           |    |   |   |   |   |
|   |      |      | > Verification and/or PTDR.\ |    |   |   |   |   |
|   |      |      | > Window of 2 months.        |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 4 | U    | I-   | Usability Verification of    | X  | 1 | 1 | X |   |
|   | sabi | 15.5 | Payload Specific Displays    |    | 3 | 3 |   |   |
|   | lity |      |                              |    | . | . |   |   |
|   | Veri |      | > Window is 2 months long.\  |    | 5 | 5 |   |   |
|   | fica |      | > Before PTDR.\              |    |   |   |   |   |
|   | tion |      | > After Candidate Display    |    |   |   |   |   |
|   |      |      | > Delivery.\                 |    |   |   |   |   |
|   |      |      | > After Procedures Tabletop. |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 5 | P/L  | I-12 | Payload Training Data Set    | X  | I | I | I |   |
|   | Trai |      | (Baseline)                   |    | - | - | - |   |
|   | ning |      |                              |    | 1 | 1 | 1 |   |
|   | DS   |      | > 1 month before PTDR.\      |    | 0 | 0 | 0 |   |
|   | (    |      | > 2 months before Start New  |    |   |   |   |   |
|   | B/L) |      | > P/L Training.              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 6 | PTDR | I-11 | Payload Training Dry Run     | X  | I | I | I |   |
|   |      |      |                              |    | - | - | - |   |
|   |      |      | > This milestone is          |    | 9 | 9 | 9 |   |
|   |      |      | > applicable to new payloads |    |   |   |   |   |
|   |      |      | > or payloads with major     |    |   |   |   |   |
|   |      |      | > revisions in objectives or |    |   |   |   |   |
|   |      |      | > training products as       |    |   |   |   |   |
|   |      |      | > determined by TST.\        |    |   |   |   |   |
|   |      |      | > 1 month before Start New   |    |   |   |   |   |
|   |      |      | > P/L Training.              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 7 | New  | I-10 | Training for "New" Payloads  | X  | I | I | I |   |
|   | P/L  |      |                              |    | - | - | - |   |
|   | Trai |      | > 1 month after PTDR.\       |    | 8 | 8 | 8 |   |
|   | ning |      | > 2-4 months before Start    |    |   |   |   |   |
|   |      |      | > Complement Training.       |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 8 | GDS  | I-10 | Ground Data Services Blank   | X  | X | X | X |   |
|   | BB   |      | Book (Baseline)              |    |   |   |   |   |
|   | (    |      |                              |    |   |   |   |   |
|   | B/L) |      | > 3 months after GDS Blank   |    |   |   |   |   |
|   |      |      | > Book is sent to PDs.       |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 9 | POIC | L-7  | POIC Command & Telemetry     | X  |   | X | X |   |
|   | Cmd  |      | Databases (I)                |    |   |   |   |   |
|   | &    |      |                              |    |   |   |   |   |
|   | Tlm  |      | > 2 months after C&DH        |    |   |   |   |   |
|   | DB   |      | > Interim dataset.           |    |   |   |   |   |
|   | (I)  |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | P/L  | I-7  | Payload Regulations          | X  | X | X | X |   |
| 0 | Regs |      |                              |    |   |   |   |   |
|   |      |      | > 5 months before Payload    |    |   |   |   |   |
|   |      |      | > Regulations (Baseline).    |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | EPAS | L    | Earth-To-Orbit Vehicle       | X  | X | X | X | X |
| 1 | (    | -6.5 | (Shuttle) Payload Activity   |    |   |   |   |   |
|   | Prel |      | Summary (Preliminary)        |    |   |   |   |   |
|   | imin |      |                              |    |   |   |   |   |
|   | ary) |      | > Flight specific            |    |   |   |   |   |
|   |      |      | > milestone.\                |    |   |   |   |   |
|   |      |      | > This is a POIF product     |    |   |   |   |   |
|   |      |      | > submittal to MOD.          |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | FOR  | L    | FOR Data Package Available   |    |   |   |   | X |
| 2 | Data | -6.1 | for Review                   |    |   |   |   |   |
|   | Pack |      |                              |    |   |   |   |   |
|   | Re   |      |                              |    |   |   |   |   |
|   | view |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | Co   | I-6  | Complement Training for the  | X  | X | X | X |   |
| 3 | mple |      | Increment                    |    |   |   |   |   |
|   | ment |      |                              |    |   |   |   |   |
|   | Trai |      | > 2-4 months after Start New |    |   |   |   |   |
|   | ning |      | > P/L Training.\             |    |   |   |   |   |
|   |      |      | > 3 months before Start      |    |   |   |   |   |
|   |      |      | > JMST.                      |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | Fl   | L-6  | Flight Rules Annex           | X  | X | X | X | X |
| 4 | ight |      |                              |    |   |   |   |   |
|   | R    |      | > 2 months before Shuttle    |    |   |   |   |   |
|   | ules |      | > Flight FOR.\               |    |   |   |   |   |
|   | A    |      | > This is a POIF product     |    |   |   |   |   |
|   | nnex |      | > submittal to MOD.          |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | ETOV | L    | Earth-To-Orbit Vehicle       | X  | X | X | X |   |
| 5 | Pay  | -5.5 | (Shuttle) Payload Procedures |    |   |   |   |   |
|   | load |      | Submit to U.S. Systems       |    |   |   |   |   |
|   | Pr   |      | Operations Data File         |    |   |   |   |   |
|   | oced |      |                              |    |   |   |   |   |
|   | ures |      | > 1.5 months before Shuttle  |    |   |   |   |   |
|   | to   |      | > Flight FOR.\               |    |   |   |   |   |
|   | U.S. |      | > This is a POIF product     |    |   |   |   |   |
|   | SODF |      | > submittal to MOD.          |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | P/L  | I-   | Payload Planning Data Set    | X  | X | X | X | X |
| 6 | Plan | 4.25 | (Baseline)                   |    |   |   |   |   |
|   | ning |      |                              |    |   |   |   |   |
|   | DS   |      | > 3.75 months after Planning |    |   |   |   |   |
|   | (    |      | > Data Set submittal.\       |    |   |   |   |   |
|   | B/L) |      | > 2.25 months before P/L OOS |    |   |   |   |   |
|   |      |      | > and P/L GR&C.              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | POIC | L-4  | POIC Command & Telemetry     | X  |   | X | X |   |
| 7 | Cmd  |      | Databases (F).               |    |   |   |   |   |
|   | &    |      |                              |    |   |   |   |   |
|   | Tlm  |      | > 2 months after C&DH Final  |    |   |   |   |   |
|   | DB   |      | > dataset.                   |    |   |   |   |   |
|   | (F)  |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | In   | L-3  | Integrated EXPRESS Rack      | X  |   |   |   |   |
| 8 | tegr |      | Payload Safing Procedure     |    |   |   |   |   |
|   | ated |      | (Baseline)                   |    |   |   |   |   |
|   | ER   |      |                              |    |   |   |   |   |
|   | P/L  |      | > After individual payload   |    |   |   |   |   |
|   | Sa   |      | > safing procedures are      |    |   |   |   |   |
|   | fing |      | > baselined.                 |    |   |   |   |   |
|   | Proc |      |                              |    |   |   |   |   |
|   | (    |      |                              |    |   |   |   |   |
|   | B/L) |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 1 | PPD  | I-4  | Payload Procedures and       | X  | X | X | X |   |
| 9 | DS   |      | Displays Data Set: Manual    |    |   |   |   |   |
|   | Pr   |      | Procedures (Baseline)        |    |   |   |   |   |
|   | oced |      |                              |    |   |   |   |   |
|   | ures |      |                              |    |   |   |   |   |
|   | (    |      |                              |    |   |   |   |   |
|   | B/L) |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | P/L  | I-3  | Payload Regulations          | X  | X | X | X | X |
| 0 | Regs |      | (Baseline)                   |    |   |   |   |   |
|   | (    |      |                              |    |   |   |   |   |
|   | B/L) |      | > 4 months after Payload     |    |   |   |   |   |
|   |      |      | > Regulations input.         |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | JMST | I-3  | Joint Multi-Segment Station  | X  | X | X | X |   |
| 1 |      |      | Training                     |    |   |   |   |   |
|   |      |      |                              |    |   |   |   |   |
|   |      |      | > 3 months after Start       |    |   |   |   |   |
|   |      |      | > Complement Training.       |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | In   | L-3  | Integrated EXPRESS Rack      | X  |   |   |   |   |
| 2 | tegr |      | Payload Safing Procedure     |    |   |   |   |   |
|   | ated |      | (Baseline)                   |    |   |   |   |   |
|   | ER   |      |                              |    |   |   |   |   |
|   | P/L  |      | > After individual payload   |    |   |   |   |   |
|   | Sa   |      | > safing procedures are      |    |   |   |   |   |
|   | fing |      | > baselined.                 |    |   |   |   |   |
|   | Proc |      |                              |    |   |   |   |   |
|   | (    |      |                              |    |   |   |   |   |
|   | B/L) |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | GCP  | L-3  | Ground Command Procedures    | X  | X | X | X |   |
| 3 | Book |      | Book (Final)                 |    |   |   |   |   |
|   | (F)  |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | PSM  | L-3  | Payload System Manual        | X  | X | X | X |   |
| 4 | (F)  |      | (Final)                      |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | EPAS | L    | Earth-To-Orbit Vehicle       | X  | X | X | X | X |
| 5 | (    | -2.5 | (Shuttle) Payload Activity   |    |   |   |   |   |
|   | B/L) |      | Summary (Baseline)           |    |   |   |   |   |
|   |      |      |                              |    |   |   |   |   |
|   |      |      | > Flight specific            |    |   |   |   |   |
|   |      |      | > milestone.\                |    |   |   |   |   |
|   |      |      | > This is a POIF product     |    |   |   |   |   |
|   |      |      | > submittal to MOD.          |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | P/L  | I    | Payload Increment On-Orbit   | X  | X | X | X | X |
| 6 | OOS  | -5.5 | Operations Summary           |    |   |   |   |   |
|   |      | to   |                              |    |   |   |   |   |
|   |      | I    |                              |    |   |   |   |   |
|   |      | -2.0 |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | P/L  | I    | Payload input to Groundrules | X  | X | X | X | X |
| 7 | GR&C | -2.0 | and Constraints (Final)      |    |   |   |   |   |
|   | (F)  |      |                              |    |   |   |   |   |
|   |      |      | > 2.25 months after Planning |    |   |   |   |   |
|   |      |      | > Data Set (F).\             |    |   |   |   |   |
|   |      |      | > Same time as P/L OOS (F).\ |    |   |   |   |   |
|   |      |      | > 1.5 months before signed   |    |   |   |   |   |
|   |      |      | > Integrated OOS (F) and     |    |   |   |   |   |
|   |      |      | > GR&C (F).\                 |    |   |   |   |   |
|   |      |      | > This is a POIF product     |    |   |   |   |   |
|   |      |      | > submittal to MOD.          |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+
| 2 | Tran | L-3  | Transfer List Review Start   |    |   |   |   | X |
| 8 | sfer | w    |                              |    |   |   |   |   |
|   | List | eeks |                              |    |   |   |   |   |
|   | Rev  |      |                              |    |   |   |   |   |
+---+------+------+------------------------------+----+---+---+---+---+

+----+------+------+-------------------------------+---+---+---+---+---+
| [  |      |      |                               |   |   |   |   |   |
| ]{ |      |      |                               |   |   |   |   |   |
| #_ |      |      |                               |   |   |   |   |   |
| _R |      |      |                               |   |   |   |   |   |
| ef |      |      |                               |   |   |   |   |   |
| He |      |      |                               |   |   |   |   |   |
| ad |      |      |                               |   |   |   |   |   |
| in |      |      |                               |   |   |   |   |   |
| g_ |      |      |                               |   |   |   |   |   |
| __ |      |      |                               |   |   |   |   |   |
| To |      |      |                               |   |   |   |   |   |
| c1 |      |      |                               |   |   |   |   |   |
| 77 |      |      |                               |   |   |   |   |   |
| 26 |      |      |                               |   |   |   |   |   |
| 57 |      |      |                               |   |   |   |   |   |
| 56 |      |      |                               |   |   |   |   |   |
| .  |      |      |                               |   |   |   |   |   |
| an |      |      |                               |   |   |   |   |   |
| ch |      |      |                               |   |   |   |   |   |
| or |      |      |                               |   |   |   |   |   |
| }t |      |      |                               |   |   |   |   |   |
| ab |      |      |                               |   |   |   |   |   |
| le |      |      |                               |   |   |   |   |   |
| 4  |      |      |                               |   |   |   |   |   |
| .0 |      |      |                               |   |   |   |   |   |
| -6 |      |      |                               |   |   |   |   |   |
| K  |      |      |                               |   |   |   |   |   |
| EN |      |      |                               |   |   |   |   |   |
| NE |      |      |                               |   |   |   |   |   |
| DY |      |      |                               |   |   |   |   |   |
| S  |      |      |                               |   |   |   |   |   |
| PA |      |      |                               |   |   |   |   |   |
| CE |      |      |                               |   |   |   |   |   |
| CE |      |      |                               |   |   |   |   |   |
| NT |      |      |                               |   |   |   |   |   |
| ER |      |      |                               |   |   |   |   |   |
| I  |      |      |                               |   |   |   |   |   |
| NT |      |      |                               |   |   |   |   |   |
| EG |      |      |                               |   |   |   |   |   |
| RA |      |      |                               |   |   |   |   |   |
| TI |      |      |                               |   |   |   |   |   |
| ON |      |      |                               |   |   |   |   |   |
| M  |      |      |                               |   |   |   |   |   |
| IL |      |      |                               |   |   |   |   |   |
| ES |      |      |                               |   |   |   |   |   |
| TO |      |      |                               |   |   |   |   |   |
| NE |      |      |                               |   |   |   |   |   |
| CH |      |      |                               |   |   |   |   |   |
| RO |      |      |                               |   |   |   |   |   |
| NO |      |      |                               |   |   |   |   |   |
| LO |      |      |                               |   |   |   |   |   |
| GY |      |      |                               |   |   |   |   |   |
| (2 |      |      |                               |   |   |   |   |   |
| pa |      |      |                               |   |   |   |   |   |
| ge |      |      |                               |   |   |   |   |   |
| s) |      |      |                               |   |   |   |   |   |
+====+======+======+===============================+===+===+===+===+===+
| Li | M    | Date | Predecessors And Successors   | F | S | S | A | P |
| ne | iles | (Mon |                               |   |   | u |   | M |
| \# | tone | ths) |                               |   |   | b |   | I |
|    | Acr  |      |                               |   |   |   |   | T |
|    | onym |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 1  | KSC  | L-12 | Kennedy Space Center          | X | X | X | X |   |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | ISS  |      | Set International Space       |   |   |   |   |   |
|    | to   |      | Station to Payload Operations |   |   |   |   |   |
|    | P/L  |      | and Maintenance Requirements  |   |   |   |   |   |
|    | O    |      | and Specifications, File 10,  |   |   |   |   |   |
|    | MRS, |      | Volume 2 (Preliminary)        |   |   |   |   |   |
|    | File |      |                               |   |   |   |   |   |
|    | 10,  |      | > 0.5 month after KSC TRDS    |   |   |   |   |   |
|    | Vo   |      | > OMRS File 10, Volume 2 (P)  |   |   |   |   |   |
|    | lume |      | > submittal.\                 |   |   |   |   |   |
|    | 2    |      | > 3 months before KSC TRDS    |   |   |   |   |   |
|    | (P)  |      | > OMRS, File 10, Volume 2     |   |   |   |   |   |
|    |      |      | > (B/L).                      |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 2  | KSC  | L-12 | Kennedy Space Center          |   |   |   | X |   |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | Bay  |      | Set Bay to Payload Operations |   |   |   |   |   |
|    | to   |      | and Maintenance Requirements  |   |   |   |   |   |
|    | P/L  |      | and Specifications File 2,    |   |   |   |   |   |
|    | O    |      | Volume 2 (Preliminary)        |   |   |   |   |   |
|    | MRS, |      |                               |   |   |   |   |   |
|    | File |      | > 0.5 month after KSC TRDS    |   |   |   |   |   |
|    | 2,   |      | > OMRS File 2, Volume 2 (P)   |   |   |   |   |   |
|    | Vo   |      | > submittal.\                 |   |   |   |   |   |
|    | lume |      | > 4 months before KSC TRDS    |   |   |   |   |   |
|    | 2    |      | > OMRS, File 2, Volume 2      |   |   |   |   |   |
|    | (P)  |      | > (B/L).                      |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 3  | KSC  | L-9  | Kennedy Space Center          | X | X | X | X | X |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | ISS  |      | Set International Space       |   |   |   |   |   |
|    | to   |      | Station to Payload Operations |   |   |   |   |   |
|    | P/L  |      | and Maintenance Requirements  |   |   |   |   |   |
|    | O    |      | and Specifications, File 10,  |   |   |   |   |   |
|    | MRS, |      | Volume 2 (Baseline)           |   |   |   |   |   |
|    | File |      |                               |   |   |   |   |   |
|    | 10,  |      | > 3 months after OMRS, File   |   |   |   |   |   |
|    | Vo   |      | > 10, Volume 2 (P).           |   |   |   |   |   |
|    | lume |      |                               |   |   |   |   |   |
|    | 2    |      |                               |   |   |   |   |   |
|    | (    |      |                               |   |   |   |   |   |
|    | B/L) |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 4  | KSC  | L-8  | Kennedy Space Center          |   |   |   | X | X |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | Bay  |      | Set Bay to Payload Operations |   |   |   |   |   |
|    | to   |      | and Maintenance Requirements  |   |   |   |   |   |
|    | P/L  |      | and Specifications, File 2,   |   |   |   |   |   |
|    | O    |      | Volume 2 (Baseline)           |   |   |   |   |   |
|    | MRS, |      |                               |   |   |   |   |   |
|    | File |      | > 4 months after OMRS, File   |   |   |   |   |   |
|    | 2,   |      | > 2, Volume 2 (P).            |   |   |   |   |   |
|    | Vo   |      |                               |   |   |   |   |   |
|    | lume |      |                               |   |   |   |   |   |
|    | 2    |      |                               |   |   |   |   |   |
|    | (    |      |                               |   |   |   |   |   |
|    | B/L) |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 5  | KSC  | L    | Kennedy Space Center          | X | X | X |   | X |
|    | TRDS | -5.1 | Technical Requirements Data   |   |   |   |   |   |
|    | Orb  |      | Set Orbiter Middeck to        |   |   |   |   |   |
|    | iter |      | Payload Operations and        |   |   |   |   |   |
|    | MDK  |      | Maintenance Requirements and  |   |   |   |   |   |
|    | to   |      | Specifications, File 2,       |   |   |   |   |   |
|    | P/L  |      | Volume 2 (Preliminary)        |   |   |   |   |   |
|    | O    |      | submittal                     |   |   |   |   |   |
|    | MRS, |      |                               |   |   |   |   |   |
|    | Fil  |      | > 1 month after MDK OMRS,     |   |   |   |   |   |
|    | e 2, |      | > File 2, Volume 2 (P).\      |   |   |   |   |   |
|    | Vo   |      | > 2 months before MDK OMRS,   |   |   |   |   |   |
|    | lume |      | > File 2, Volume 2 (B/L).     |   |   |   |   |   |
|    | 2    |      |                               |   |   |   |   |   |
|    | (P)  |      |                               |   |   |   |   |   |
|    | s    |      |                               |   |   |   |   |   |
|    | ubmi |      |                               |   |   |   |   |   |
|    | ttal |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 6  | KSC  | L-4  | Kennedy Space Center          | X | X | X |   | X |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | Orb  |      | Set Orbiter Middeck to        |   |   |   |   |   |
|    | iter |      | Payload Time-Critical Ground  |   |   |   |   |   |
|    | MDK  |      | Handling Requirements Table   |   |   |   |   |   |
|    | to   |      | (Preliminary) submittal       |   |   |   |   |   |
|    | P/L  |      |                               |   |   |   |   |   |
|    | TGHR |      | > 0.5 month after Orbiter MDK |   |   |   |   |   |
|    | T    |      | > TGHR table (P).\            |   |   |   |   |   |
|    | able |      | > 2 months before Orbiter MDK |   |   |   |   |   |
|    | (P)  |      | > TGHR table (B/L).           |   |   |   |   |   |
|    | s    |      |                               |   |   |   |   |   |
|    | ubmi |      |                               |   |   |   |   |   |
|    | ttal |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 7  | CEIT | L-4  | Crew Equipment Interface Test | X |   | X | X | X |
|    |      |      |                               |   |   |   |   |   |
|    |      |      | > Before Cargo Bay/Carrier    |   |   |   |   |   |
|    |      |      | > installation.               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 8  | KSC  | L    | Kennedy Space Center          | X |   |   |   | X |
|    | Uti  | -3.5 | Utilization Turn-Over to      |   |   |   |   |   |
|    | liza |      | Rack\                         |   |   |   |   |   |
|    | tion |      | KSC Utilization Hardware T/O  |   |   |   |   |   |
|    | T/O  |      | for MPLM installation. H/W    |   |   |   |   |   |
|    | Rack |      | T/O need date will be         |   |   |   |   |   |
|    |      |      | provided by the ISS Program   |   |   |   |   |   |
|    |      |      | to support outfitting the     |   |   |   |   |   |
|    |      |      | MPLM schedule.                |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 9  | KSC  | L-3  | Kennedy Space Center          | X | X | X |   | X |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | Orb  |      | Set Orbiter Middeck to        |   |   |   |   |   |
|    | iter |      | Payload Operation and         |   |   |   |   |   |
|    | MDK  |      | Maintenance Requirements and  |   |   |   |   |   |
|    | to   |      | Specifications, File 2,       |   |   |   |   |   |
|    | P/L  |      | Volume 2 (Baseline)           |   |   |   |   |   |
|    | O    |      |                               |   |   |   |   |   |
|    | MRS, |      | > 2 months after MDK OMRS,    |   |   |   |   |   |
|    | Fil  |      | > File 2, Volume 2 (P).       |   |   |   |   |   |
|    | e 2, |      |                               |   |   |   |   |   |
|    | Volu |      |                               |   |   |   |   |   |
|    | me 2 |      |                               |   |   |   |   |   |
|    | (    |      |                               |   |   |   |   |   |
|    | B/L) |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 10 | KSC  | L-2  | Kennedy Space Center          | X | X | X |   | X |
|    | TRDS |      | Technical Requirements Data   |   |   |   |   |   |
|    | Orb  |      | Set Orbiter Middeck to        |   |   |   |   |   |
|    | iter |      | Payload Time-Critical Ground  |   |   |   |   |   |
|    | MDK  |      | Handling Requirements Table   |   |   |   |   |   |
|    | to   |      | (Baseline)                    |   |   |   |   |   |
|    | P/L  |      |                               |   |   |   |   |   |
|    | TGHR |      | > 2 months after Orbiter MDK  |   |   |   |   |   |
|    | T    |      | > TGHR table (P).             |   |   |   |   |   |
|    | able |      |                               |   |   |   |   |   |
|    | (    |      |                               |   |   |   |   |   |
|    | B/L) |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 11 | CEIT | L    | Crew Equipment Interface Test | X |   | X |   | X |
|    | (    | -1.6 | for P/L flying in the Middeck |   |   |   |   |   |
|    | Midd |      |                               |   |   |   |   |   |
|    | eck) |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 12 | KSC  | H/W  | Kennedy Space Center Support  | X | X | X | X | X |
|    | SRDS | O    | Requirements Data Set         |   |   |   |   |   |
|    | (    | /D-3 | (Baseline)                    |   |   |   |   |   |
|    | B/L) |      |                               |   |   |   |   |   |
|    |      |      | > 3 months before P/L H/W O/D |   |   |   |   |   |
|    |      |      | > at KSC.\                    |   |   |   |   |   |
|    |      |      | > 2 months before LSSP        |   |   |   |   |   |
|    |      |      | > Addendum (B/L).             |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+
| 13 | MIP  | H/W  | Launch Site Support Plan      | X | X | X | X | X |
|    | A    | O    | Addendum (Baseline)           |   |   |   |   |   |
|    | nnex | /D-1 |                               |   |   |   |   |   |
|    | 8    |      | > 2 months after KSC SRDS     |   |   |   |   |   |
|    | LSSP |      | > (B/L).\                     |   |   |   |   |   |
|    | Adde |      | > 1 month before P/L H/W O/D  |   |   |   |   |   |
|    | ndum |      | > at KSC.                     |   |   |   |   |   |
|    | (    |      |                               |   |   |   |   |   |
|    | B/L) |      |                               |   |   |   |   |   |
+----+------+------+-------------------------------+---+---+---+---+---+

# INTERNATIONAL PARTNER LAUNCH VEHICLE UNIQUE MILESTONES

The unique payload integration milestones for payloads launching on ESA
ATV are covered in Section 5.1. Integration milestones for payloads
launching on Russian (Soyuz or Progress) vehicles are covered in Section
5.2. Integration milestones for payloads launching on JAXA HTV are
covered in Section 5.3, HII Vehicle Milestones.

## Automated Transfer Vehicle (ATV) Launch Milestones

Actual ISS Program flight schedules for ATV flights will vary greatly
from flight to flight. Variability will depend on whether the payload
hardware is a first time flyer or re-flight. The following list of ATV
launch integration milestones does not encompass nominal payload
submittals which are already contained in the four PIM Schedule
templates (Pressurized, Subrack, Small, Attached). The focus of this
list is simply to identify cargo processing activities and unique data
submittals exclusively related to ATV flights.

When first producing a unique PIM Schedule for a new payload, milestones
in this table should be added to the appropriate PIM Schedule template
if the payload is manifested or expected to be launched on an ATV
vehicle. The payload integration milestones for payloads launching on
ESA ATV are covered in Table 5.1-1, ATV Milestones.

  -----------------------------------------------------------------------
  []{#__RefHeading___Toc177265757 .anchor}Table   
  5.1-1 ATV Milestones (2 pages)                  
  ----------------------------------------------- -----------------------
  ATV Milestones                                  Launch Minus Template\
                                                  (L-Date)

  **Payload Safety (Flight):**                    

  Flight Certification to ESA                     L-4 M

  Phase 3 Flight Safety Data Package (FSDP) \[PD  L-7 M
  Submit\]                                        

  Phase 3 Flight Safety Review (FSR)              L-5.5M

  Export License (If required)                    L-7.5 M

                                                  

  **Payload Safety (Ground):**                    

  Ground Checklist to ESA                         L-7 M

                                                  

  **CoFR ATV Flight Template**                    **Reference OZ CoFR
                                                  Website**

  OZ2 CoFR Pre-Coordination Review                L-6 M

  OZ2 Bi-Lateral CoFR Pre-coordination Review (if L-6 M
  necessary)                                      

  Release OZ CoFR Instruction Letter              L-5.5 M

  OWTL Inputs Due                                 L-4.5 M

  OZ ATV Cargo Integration Readiness Review       L-4 M

  ESA ATV Cargo Integration Readiness Review &    L-4 M
  CoC Signature                                   

  OZ2 OWTL Review                                 L-7 W

  CoFR Endorsement Package Due                    L-6.5 W

  OZ2 CoFR Endorsement Package Review             L-5.5 W

  IP/P CoFR Readiness Review (OZ participation as L-5 W
  required)                                       

  OZ Multilateral CoFR Readiness Review           L-4 W

  ESA ATV Cargo Integration Readiness             L-4 W

  SORR Stage Operations Readiness Review          L-2 W to L-3 W

                                                  

  **ATV Unique Documentation**                    

  Cargo Integration Agreement                     L-4 M

  **Hardware Processing at JSC (nominal)**        

  On-Dock at JSC                                  L-17.5 W

  Hardware Verification Review (HVR)              L-16.5 W

  Bench Review                                    L-15.5 W

  Hardware Ship From JSC to Kourou                L-13 W

                                                  

  **Hardware Processing at KSC (nominal)**        

  On-Dock at KSC                                  L-19.5 W

  Hardware Verification Review (HVR)              L-17.5 W

  Bench Review                                    L-15 W

  Hardware Ship From KSC to Kourou                L-13 W

                                                  

  **Hardware Processing at KSC (late)**           

  On-Dock at KSC                                  **\<TBD 5-1\>**

  Hardware Verification Review (HVR)              **\<TBD 5-2\>**

  Bench Review                                    **\<TBD 5-3\>**

  Hardware Ship From KSC to Kourou                **\<TBD 5-4\>**

                                                  

  **Hardware Processing at Turin (nominal)**      

  On-Dock at Turin                                L-4.25 M

  Bench Review                                    L-3.5 M

  Hardware Ship From Turin to Kourou              L-3 M

  **Hardware Processing at Turin (late)**         

  On-Dock at Turin                                L-2 M

  Bench Review                                    L-1.75 M

  Hardware Ship From Turin to Kourou              L-1 M

                                                  
  -----------------------------------------------------------------------

Definitions:

Date Template: M = month, W = week

This table is an OZ-specific subset of SSP 50489, Mission Integration
Template, OZ CoFR website, ATV Flight Schedule:
<http://iss-www.jsc.nasa.gov/ss/issapt/payofc/OZ2/COFR/COFR-schedule.html>.

## RUSSIAN Vehicle (RV) Launch Milestones

Actual ISS Program flight schedules for Russian Progress and Soyuz
flights will vary greatly from flight to flight. Variability will depend
on whether the payload hardware is a first time flyer or re-flight. The
following list of Russian launch integration milestones does not
encompass nominal payload submittals which are already contained in the
four PIM Schedule templates (Pressurized, Subrack, Small, Attached). The
focus of this list is simply to identify cargo processing activities and
unique data submittals exclusively related to Russian Soyuz or Progress
flights.

When first producing a unique PIM Schedule for a new payload, milestones
in this table should be added to the appropriate PIM Schedule template
if the payload is manifested or expected to be launched on a Soyuz or
Progress vehicle. The payload integration milestones for payloads
launching on Russian (Soyuz or Progress) vehicles are covered in Table
5.2-1, Russian Vehicle Milestones.

[]{#__RefHeading___Toc177265758 .anchor}TABLE 5.2-1 RUSSIAN VEHICLE
MILESTONES

  ------------------------------------------------------- ---------------
  Russian Vehicle (Soyuz or Progress)\                    Launch Minus
  Milestones                                              Template\
                                                          (L-Date)

  **Payload Safety**                                      

  Phase 3 flight Safety Data Package (SDP) (PD Submit)    L-7.5 M

  Phase 3 Flight Safety Review (FSR)                      L-6 M

  PSRP review Complete, Approved (Confirmation received   L-3.5 W
  from PSRP)                                              

                                                          

  **CoFR Russian Template**                               **Reference OZ
                                                          CoFR Website**

  OZ2 CoFR Pre-Coordination Review                        L-4 M

  OZ2 Bilateral CoFR Pre-Coordination Review (if          L-15 W
  necessary)                                              

  Release OZ CoFR Instruction Letter                      L-13 W

  OWTL Inputs Due (ISS and Russian Vehicle-specific)      L-9 W

  OZ2 OWTL Review                                         L-7.5 W

  CoFR Endorsement Package Due                            L-7 W

  OZ2 CoFR Endorsement Package Review                     L-6 W

  IP/P CoFR Readiness Review (OZ participation as         L-5 W
  required)                                               

  OZ Multilateral CoFR Readiness Review                   L-4 W

  SORR - Stage Operations Readiness Review                L-2 W to L-3 W

  FRR - Flight Readiness Review (Soyuz crew rotation      L-1 W to L-2 W
  flights only)                                           

                                                          

  **Manifest Changes**                                    

  OZ CEF Submittal (PD)                                   L-6 M

  OZ MR Submittal (Manifest Lead)                         L-4.5 M

  OC-sponsored manifest presented to MIOCB                L-3.75 M

  OC MIOCB Manifest -- final approval                     L-3.5 M

                                                          

  **Payload Engineering Integration**                     

  Verification Data (Non-EXPRESS, Stage Analysis (SSP     L-3.5 M
  L-7.5 M)                                                

  Re-Verification Memo                                    L-3 M

                                                          

  **Russian Unique Documentation**                        

  Technical Data Sheet (TDS)                              L-5 M
                                                          (Progress)\
                                                          L-4 M(Soyuz)

  Export Control Worksheet (ECW) (JSC Form 1724)          L-4.5 M
                                                          (Progress)\
                                                          L-8 (Soyuz)

  ProForma (formerly DUC, embedded within ECW) (JSC Form  L-4.5 M
  1735)                                                   (Progress)\
                                                          L-8 M (Soyuz)

  Technical Passport                                      L-12 W

  Hardware Accountability Matrix review (HAMR) -- Initial L-4.5 M
  Reviewed by: RV PIM, PD PIM + PD                        

  Hardware Accountability Matrix Review (HAMR) -- Final   L-4 M
  (RV PIM)                                                

  On-Dock at Flight Crew Equipment (FCE)                  L-9.5 W
                                                          (Commercial)

  Hardware Verification Review (HVR)                      L-7.75 W
                                                          (Commercial)

  Bench Review                                            L-7.5 W
                                                          (Commercial)

  Hardware Ship From JSC to Russia                        L-5.5 W
                                                          (Commercial)
  ------------------------------------------------------- ---------------

Definitions:

Date Template: M = month, W = week

This table is an OZ-specific subset of SSP 50489, Mission Integration
Template, OZ CoFR website, Russian Flight Schedule:\
http://iss-www.jsc.nasa.gov/ss/issapt/payofc/OZ2/COFR/COFR-schedule.html.

## HII Transfer Vehicle (HTV) Launch Milestones

The payload integration milestones for payloads launching on JAXA HTV
will be covered in Table 5.3-1, HII Vehicle Milestones.

[]{#__RefHeading___Toc177265759 .anchor}TABLE 5.3-1 HII VEHICLE
MILESTONES

TBD \<5-5\>

Appendix A - Acronyms and abbreviations

  ----------------- -----------------------------------------------------
  A                 Attached

  A&I               Assembly and Installation

  ATV               Automated Transfer Vehicle

                    

  BB                Blank Book

  B/L               Baseline

  BR                Bench Review

                    

  C&DH              Command and Data Handling

  CCCD              Crew Compartment Configuration Drawing

  CCCR              Crew Compartment Configuration Review

  CDR               Critical Design Review

  CE                Cargo Element

  CEIT              Crew Equipment Interface Test

  CIR               Cargo Integration Review

  CIRD              Cargo Integration Review Dry Run

  CMC               Cargo Mission Contract

  CMD               Command

  CoC               Certificate of Compliance

  CoFR              Certification of Flight Readiness

  CR                Change Request

  CSRD              Current Stage Requirements Document

                    

  DP                Data Pack

  DS                Data Set

  DUC               Data Usage Chart

  Dwg               Drawing

                    

  ECL               Engineering Configuration List

  ECR               Engineering Change Request

  ECW               Export Control Worksheet

  EIRR              EXPRESS Integration Readiness Review

  EMC               Electromagnetic Compatibility (Control)

  EMI               Electromagnetic Interference

  EPAS              ETOV Payload Activity Summary

  ER                EXPRESS Rack

  ESA               European Space Agency

  ETOV              Earth-to-Orbit Vehicle

  EVA               Extravehicular Activity

  EXPRESS           EXpedite the PRocessing of Experiments to the Space
                    Station

                    

  F                 Facility

  FAO               Flight Activity Officer

  FCE               Flight Crew Equipment

  FCSD              Flight Crew Support Division

  FOR               Flight Operations Review

  FPM               Flight Payload Manager

  FPSR              Flight Planning and Stowage Review

  FR                Flight Rules

  FRD               Flight Requirements Document

  FRR               Flight Readiness Review

  FSDP              Flight Safety Data Package

  FSR               Flight Safety Review

                    

  GAS               Getaway Special

  GCP               Ground Command Procedure

  GDS               Ground Data Services

  GL&C              Guidelines and Constraints

  GPVP              Generic Payload Verification Plan

  GR&C              Groundrules and Constraints

  GSDP              Ground Safety Data Package

  GSE               Ground Support Equipment

  GSP               Ground Support Personnel

  GSR               Ground Safety Review

                    

  HAMR              Hardware Accountability Matrix Report

  HCI               Human Computer Interface

  HDW               Hardware

  HFIT              Human Factors Interface Team (Integration)

  HTV               H-II Transfer Vehicle

  HVR               Hardware Verification Review

  H/W               Hardware

                    

  I                 Increment

  I-                Increment minus

  ICA               Interface Control Annex

  ICD               Interface Control Document

  IDD               Interface Definition Document

  IDP               Integrated Data Package

  IDRD              Increment Definition and Requirements Document

  IDRP              Increment Definition Requirements Plan

  I/F               Interface

  IMS               Inventory Management System

  IOR               Increment Operations Review

  IORR              Integrated Operation Readiness Review

  IP                International Partner

  IPE               Increment Payload Engineer

  IPIC              ISS Payload Integration Contract

  IPLAT             ISS Payload Label Approval Team

  IPM               Increment Payload Manager

  IP/P              International Partner/Participant

  IPV               International Payload Viewer

  IRD               Interface Requirements Document

  IRR               Increment Requirements Review

  ISPR              International Standard Payload Rack

  ISS               International Space Station

  ISVR              Independent Safety Verification Review

  IVT               Interface Verification Test

                    

  JAXA              Japan Aerospace Exploration Agency

  JMST              Joint Multi-Segment Station Training

  JPRCB             Joint Program Requirements Control Board

  JSC               Johnson Space Center

                    

  KSC               Kennedy Space Center

                    

  L                 Launch

  L-                Launch minus

  LON               Launch On Need

  LPA               Launch Package Assessment

  LP/CE             Launch Package/Cargo Element

  LPMT              Launch Package Management Team

  LSSP              Launch Site Support Plan

                    

  MCC               Mission Control Center

  MDK               Middeck

  MDM               Multiplexer/Demultiplexer

  MI                Mission Integration

  MIDAS             Mission Integration Database Applications System

  MIOCB             Multilateral Mission Integration And Operations
                    Control Board

  MIP               Mission Integration Plan

  MOD               Mission Operations Directorate

  MPCB              Multilateral Payloads Control Board

  MPLM              Multi-Purpose Logistics Module

  MR                Manifest Request

  MSFC              Marshall Space Flight Center

                    

  NASA              National Aeronautics and Space Administration

                    

  OC                Operation Controller

  O/D               On-Dock

  OFK               Official Flight Kit

  OMRS              Operations and Maintenance Requirements and
                    Specifications

  OOS               On-Orbit Operations Summary

  OpNom             Operations Nomenclature

  Ops               Operations

  ORU               Orbital Replacement Unit

  ORG               Organization

  OWTL              Open Work Tracking Log

                    

  P                 Preliminary

  PCB               Payloads Control Board

  PCF               Payload Multiplexer/Demultiplexer Configuration Files

  PCS               Portable Computer System

  PD                Payload Developer

  PDL               Payload Data Library

  PDR               Preliminary Design Review

  PDS               Payload Data Set

  PEI               Payload Engineering Integration

  PFE               Program Furnished Equipment

  PHCM              Payload Hazard Control Matrix

  PIA               Payload Integration Agreement

  PIM               Payload Integration Manager

  PIRN              Preliminary/Proposed Interface Revision Notice

  P/L               Payload

  PMI               Payload Mission Integration

  PMIT              Payload Mission Integration Team

  POCC              Payload Operations Control Center

  PODF              Payload Operations Data File

  PODFCB            Payload Operations Data File Control Board

  POIC              Payload Operations Integration Center

  POIF              Payload Operation Integration Function

  PP                Planning Period

  PP-               Planning Period minus

  PPD               Payload Procedures and Displays

  PPIL              Payload Product Integrated List

  PRCU              Payload Rack Checkout Unit

  PRO               Payload Rack Officer

  PRR               Payload Readiness Review

  PSI               Payload Software Integration

  PSIVF             Payload Software Integration Verification Facility

  PSM               Payload System Manual

  PSRP              Payload Safety Review Panel

  PTC               Payload Training Compliment

  PTDR              Payload Training Dry Run

  PTP               Payload Tactical Plan

  PVP               Payload Verification Plan

  PVPP              Payload Verification Program Plan

                    

  RCAR              Requirements Change Assessment Report

  Rev               Review

  RF                Radio Frequency

  RMDP              Return Manifest Dispositioning Plan

  RPO               Research Program Office

  RR                Readiness Review

  RV                Russian Verification

                    

  S                 Small

  SC                Support Contractor

  SDP               Safety Data Package

  SDT               Shuttle Data Tape

  SME               Subject Matter Expert

  SODF              System Operations Data File

  SORR              Stage Operations Readiness Review

  SRDS              Support Requirements Data Set

  SRS               Software Requirements Specification

  Sub               Subrack Standard

  SSCCD             Space Station Configuration Control Drawing

  SSE               Station Support Equipment

  SSP               Space Shuttle Program

  SSPCB             Space Station Program Control Board

  SSTF              Space Station Training Facility

  STS               Space Transportation System

  S/W               Software

                    

  TBD               To Be Determined

  TBR               To Be Resolved

  TDS               Technical Data Sheet

  TGHR              Time-Critical Ground Handling Requirements

  TIM               Technical Interchange Meeting

  T/O               Turn-Over

  TRDS              Technical Requirements Data Set

  TSC               Telescience Support Center

  TST               Training Strategy Team

                    

  U/D               Update

  U.S.              United States

  USA               United States of America

  US Lab            United States Laboratory

  US PODFCB         United States Payload Operations Data File Control
                    Board

                    

  VADAR             Verification Analysis data Acceptability Review

  VAR               Verification Acceptance Review

  VER               Verification

  VLA               Verification Loads Analysis

  VMDB              Vehicle Master Database

                    

  WORF              Window Observation Rack Facility
  ----------------- -----------------------------------------------------

APPENDIX B -- GLOSSARY OF TERMS

**Hardware Accountability Matrix Report**

The Hardware Accountability Matrix Report (HAMR) is used to track
completion of ISS requirements and completion of physical processing
actions associated with physical processing milestone activities. The
HAMR is generated from a subset of data in Mission Integration Database
Applications System (MIDAS) to be used by the Launch Package Manager and
Hardware providers. MIDAS includes all components of the IDRD Annex 1
(the Manifest) and additional information for ISS hardware. Categories
utilized in MIDAS for the HAMR typically include, but are not limited
to: nomenclature, quantity, part number, on-dock and bench review dates,
barcode/imagery/certification requirements, and hardware points of
contacts.

**Strategic Planning**

Strategic planning is the long-range planning that occurs between PDR
and I-18 months (start of ISS Program tactical phase).

**Tactical Planning**

Tactical planning and manifesting is performed for each Increment.
Tactical planning and manifesting is a multilateral function, which
defines the resources, allocations, research objectives, priorities, and
manifests for each increment (expedition). These requirements are
documented in the Increment Definition and Requirements Plan (IDRP)
Increment Definition and Requirements Document (IDRD) series and
annexes.

**Verification Analysis Data Acceptability Review**

The Verification Analysis Data Acceptability Review (VADAR) will be
conducted between the SSP and the Cargo Element (CE) developers just
prior to starting the Verification Loads Analysis (VLA). The VADAR will
be scheduled after all CE models have been received and validated.
Specific cargo bay configurations, math models, forcing functions, CE
data, analysis methods, and response data recoveries that are planned
for the VLA will be clearly identified by the Support Contractor (SC).
Each CE developer shall either concur with the SC provided data or
provide updated data prior to or during the VADAR. After completion of
this review, formal authorization will be provided to begin the VLA.

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

  ------- ----------- ----------------------------------------------------
  TBD     Section     Description

  1-1     1.3         ATV Schedule Milestone Reference

  1-2     1.3         HTV Schedule Milestone Reference

  5-1     Table 51-1  On-Dock at KSC

  5-2     Table 5.1-1 Hardware Verification Review (HVR)

  5-3     Table 5.1-1 Bench Review

  5-4     Table 5.1-1 Hardware Ship From KSC to Kourou

  5-5     Table 5.3-1 HII Vehicle Milestones
  ------- ----------- ----------------------------------------------------

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

  ------- ----------- ----------------------------------------------------
  TBR     Section     Description

                      

                      

                      
  ------- ----------- ----------------------------------------------------

Appendix D - SCHEDULE TEMPLATES

![](media/image2.wmf){width="8.997222222222222in" height="5.875in"}

![](media/image3.wmf){width="9.030555555555555in"
height="5.8381944444444445in"}

![](media/image4.wmf){width="9.005555555555556in"
height="5.8381944444444445in"}

![](media/image5.wmf){width="9.01388888888889in"
height="5.999305555555556in"}

![](media/image6.wmf){width="8.849305555555556in"
height="5.753472222222222in"}

![](media/image7.wmf){width="9.07986111111111in"
height="6.048611111111111in"}

![](media/image8.wmf){width="9.030555555555555in" height="5.94375in"}

![](media/image9.wmf){width="8.972222222222221in" height="5.9in"}

![](media/image10.wmf){width="8.947916666666666in"
height="5.850694444444445in"}

![](media/image11.wmf){width="8.988888888888889in"
height="5.993055555555555in"}

![](media/image12.wmf){width="9.046527777777778in"
height="5.955555555555556in"}

![](media/image13.wmf){width="8.964583333333334in"
height="5.980555555555555in"}

![](media/image14.wmf){width="8.849305555555556in" height="5.9125in"}

![](media/image15.wmf){width="8.988888888888889in"
height="6.018055555555556in"}

![](media/image16.wmf){width="8.890277777777778in" height="5.91875in"}

![](media/image17.wmf){width="8.980555555555556in" height="5.94375in"}

![](media/image18.wmf){width="8.881944444444445in"
height="5.782638888888889in"}

![](media/image19.wmf){width="8.890277777777778in"
height="5.955555555555556in"}

![](media/image20.wmf){width="8.988888888888889in"
height="5.993055555555555in"}

![](media/image21.wmf){width="8.89861111111111in"
height="5.788194444444445in"}

![](media/image22.wmf){width="8.881944444444445in"
height="5.955555555555556in"}

![](media/image23.wmf){width="8.890277777777778in"
height="5.999305555555556in"}

![](media/image24.wmf){width="8.824305555555556in" height="5.95in"}

![](media/image25.wmf){width="8.856944444444444in" height="5.94375in"}

![](media/image26.wmf){width="8.93125in" height="5.955555555555556in"}

![](media/image27.wmf){width="8.865277777777777in" height="5.9in"}

![](media/image28.wmf){width="8.980555555555556in"
height="5.999305555555556in"}

![](media/image29.wmf){width="8.947916666666666in" height="5.9in"}

![](media/image30.wmf){width="8.865277777777777in" height="5.89375in"}

![](media/image31.wmf){width="8.93125in" height="5.94375in"}

  -----------------------------------------------------------------------
  **D5 -Generic PMIT Schedule**                 **Template Date**
  --------------------------------------------- -------------------------
  Pressurized Payloads                          

  Flight Safety Review (FSR) Data Package       L-45 days from FSR
  (DP) - Ph III                                 

  Ground Safety Review (GSR) DP - Ph III        L-45 days from GSR

  FSR Safety Review - Ph III                    L-5.6

  GSR Safety Review - Ph III                    L-5.6

  MPLM Ph III FSDP                              L-4

  MPLM Ph III FSR                               L-2.5

  ISPR Payloads                                 

  Rack Mass Properties & Test Verified Model    L-10.5 to L-9.5

  VADAR                                         L-7

  Rack HDW O/D                                  L-6

  Verification Acceptance Review (VAR)          L-3.5

  KSC                                           

  SRDS (Cargo Bay) B/L PD Input                 L-12.5

  SRDS B/L PD Input                             L-6 HDW O/D

  SRDS B/L                                      L-3 HDW O/D

  MIP Annex 8 LSSP Addendum - B/L               HDW O/D -1

  HDW O/D for testing                           L-6

  HDW Offline Testing                           L-6 to L-4.5

  HDW PRCU Testing                              L-4.5 to L-3.5

  Rack HDW T/O                                  L-3.5

  CEIT (Orbiter)                                L-4

  HDW O/D for KSC nominal installation          L-22 Days to L-8 days

  HDW O/D for KSC late installation             L-15 Days to L-28 hours

  HDW T/O for KSC nominal installation          NLT L-8 days

  D5 -Generic PMIT Schedule                     Template Date

  HDW T/O for KSC late installation             L-3 Days to L-28 hours

  TRDS OMRS (ISS & Cargo Bay to PL)-            L-12.5
  Preliminary PD Submit                         

  OMRS (ISS & Cargo Bay to PL) B/L Submit to    L-9
  SSP                                           

  OMRS (ISS & Cargo Bay to PL) - B/L            L-8

  TRDS OMRS (MDK to PL) - Preliminary PD Submit L-6

  OMRS (MDK to PL)- B/L Submit to SSP           L-5.1

  OMRS (MDK to PL) - B/L                        L-3

  TRDS PD Submit for TGHR                       L-4.5

  TGHR inputs to SSP                            L-4

  TGHR B/L                                      L-2

  CEIT (MDK)                                    L-1.6

  Program (Increment Reviews)                    

  IRR                                           I-12

  IORR                                          I-9

  IOR                                           I-4

  Program (Increment Documents)                  

  Incr Research Directive                       I-15

  IDRD B/L (Rev A \@I-12; Rev B \@I-8, I-6,     I-16
  I-4)                                          

  IDRD Appendix I (Transfer Priorities) Submit  L-10
  due to LPMT                                   

  IDRD Appendix I (Transfer Priorities)         L-8
  Approval                                      

  Current Stage Requirements Document (CSRD)    L-3.5w

  IDRD Annex 5 B/L CR Release                   I-15

  IDRD Annex 5 B/L CR Comments Due              I-15 + 3weeks

  IDRD Annex 5 B/L CR CM                        I-14

  IDRD Annex 5 B/L CR approved at MPCB          I-10 (+2 weeks from CM\
                                                & per MPCB monthly
                                                schedule)

  D5 -Generic PMIT Schedule                     Template Date

  IDRD Annex 3 B/L (Flight Requirements)        L-1.75

  Program (Flight Documents)                     

  FRD B/L                                       L-13.2

  MIP Cargo Bay Inputs                          L-17

  MIP B/L                                       L-16

  MIP Appendix E (MDK) Inputs Due               L-11.1

  MIP Annex 1 B/L Inputs                        L-14.5

  MIP Annex 1 B/L                               L-10

  MIP Annex 2 Part 1 Inputs Due                 L-11

  MIP Annex 2 Part 1 B/L                        L-4.9

  MIP Annex 4 B/L Inputs                        L-11.6

  MIP Annex 4 B/L                               L-7.7

  MIP Annex 5 B/L Inputs due                    L-14.3

  MIP Annex 5 B/L                               L-7.3

  Program (Flight Reviews)                       

  CIR Dry Run                                   L-9.8 (or CIR+3w)

  CIR                                           L-9

  FPSR List                                     L-9.2

  FPSR                                          L-7.7

  Official Flight Kit (OFK) Submit to SSP due   L-3
  date                                          

  Deliver OFK items                             L-2

  CCCR Freeze                                   L-3

  CCCR                                          L-2

  Installation Readiness Review (IRR) Kick-off  L-4 w from HDW
  (MPLM/Node Only Flights)                      Installation

  IRR Final (MPLM/Node Only Flights)            L-2w from HDW
                                                Installation

  D5 -Generic PMIT Schedule                     Template Date

  Program (CoFR)                                 

  OZ2 CoFR Pre-Coordination Review              L-5

  OZ2 Bilateral CoFR Pre-Coordination Review    L-4.5

  Release OZ CoFR Instruction Letter            L-4

  CoFR Open Work Tracking Log & LPA Inputs Due  L-3

  OZ2 OWTL & LPA Review                         L-10w

  OZ OWTL & LPA Review                          L-9w

  CoFR Endorsement Packages Due                 L-7w

  ISSP LPA                                      L-7w

  OZ2 CoFR Endorsement Package Review           L-6w

  IP/P CoFR Readiness Review (OZ participation, L-5.5w
  as required)                                  

  OZ Multilateral CoFR Readiness Review         L-4.5w

  SORR                                          L-3.5w

  FRR                                           L-2w

  Manifest & Stowage (Documentation)             

  Manifest &Stowage (M&S) Data Set (D.S.) BL    L-15 to L-12.5
  Inputs Due                                    

  M&S Data Set Kit Contents Due                 L-2M from BR (L-6 MPLM &
                                                L-3 MDK)

  IMS/Bar Code Data Due                         L-1M from BR (L-5 MPLM &
                                                L-2 MDK)

  IDRD Annex 1 Call for MRs                     L-15

  IDRD Annex 1 B/L MRs Due                      L-12.5

  IDRD Annex 1 B/L (L-6, L-3, L-6w to 2w)       L-12

  ICA Submit Due date                           L-11.1

  ICA B/L                                       L-9

  ICA Reserve CR inputs for L-10 day BR Submit  L-1.3

  ICA Reserve CR for L-10 day BR Approval       L-28 days

  RMDP Release                                  L-2

  D5 -Generic PMIT Schedule                     Template Date

  RMDP B/L                                      Launch

  Manifest & Stowage (Reviews & Drawing Data)    

  HAMR Release (MPLM/Node & MDK)                L-8

  MPLM/Node & MDK HDW Audit                     L-7.5

  MAPs Baselined (MPLM/Node)                    L-7

  HDW O/D MPLM/NODE                             L-5 toL-4.5

  SSCCD Final                                   L-4

  MPLM/NODE BR #1 @ KSC                         L-4

  Late Load HDW O/D MPLM/NODE                   L-3.5

  MPLM/NODE BR #2                               L-3

  HAMR Release (MDK Only)                       L-4.5

  MDK Only HDW Audit                            L-4

  CCCD Release                                  L-2

  HDW O/D Nominal MDK Bench Review              L-2 w from BR

  Hardware Verification Review                  L-1w from BR

  MDK Nominal Bench Review @ JSC                L-1

  CCCD Release for L-10 Day BR                  L-18 days

  HDW O/D L-10 Day MDK Bench Review             L-2 w from BR

  MDK L-10 Day Bench Review @ JSC               L-10 days

  POIC                                           

  PL Planning Data Set PD Submit                I-8

  PL Planning D.S. B/L                          L-4.25

  PL OOS                                        I-5.5 to I-2

  P/L GR&C                                      I-2

  EPAS (Preliminary)                            L-6.5

  EPAS B/L                                      L-2.5

  D5 -Generic PMIT Schedule                     Template Date

  Flight Rules Annex Submit to MOD              L-6

  P/L Regs (B/L)                                I-3

  FOR Data Pacakge Available for Review         L-6.1

  FOR                                           L-3.7

  Transfer List Review Start                    L-3 weeks

  Payload Engineering & Integration              

  HDW ICD B/L                                   L-12

  Launch/Return Verification Data               L-12 to L-3 (or HDW T/O)

  On-Orbit Verification Data PD Submit          L-9.5 to L-7.5

  Launch/Return CoC                             L-4.5 to L-3.5

  Late Load HDW Verification Data and CoC       HDW T/O

  Engineering Stage Analysis Report             L-4.5

  GL&C                                          L-4

  ISS Level P/L Complement Analysis Report      L-3

  P/L Engineering Stage Verification Memo       L-6w
  -----------------------------------------------------------------------