OZ-10-056BASELINEPayload Developers and Principal Investigators Payload Planning,Integration and Operations PrimerInternational Space Station ProgramISS National Laboratory OfficeJune 2010BASELINENational Aeronautics and Space AdministrationInternational Space Station ProgramJohnson Space CenterHouston, Texasi


OZ-10-056REVISION AJUNE 2010ContentsList of Tables and Figures. viii1Introduction . 91.1Objective . 91.2Layout . 92Background . 102.1Payload Integration Templates Definitions . 102.1.1 Standard Payload Integration Template . 102.1.2 Lean Payload Integration Template . 123Overall Research and Planning Cycle. 133.1Multilateral Research Planning Working Group (MRPWG) Roles and Responsibilities133.2Overall Research Planning . 143.2.1 Call for Payload Inputs through Release of Research Plan (RP) Development DataPackage . 143.2.2 Data Package Information Gathering Process . 143.2.3 Payload Candidate List Submittal and Review . 163.2.4 Payload Requirements Review (2-Pager, PTP tables) . 173.2.5 Human Use Life Science Research Complement Review . 173.2.6 Research Plan Development Support. 173.2.7 Human Use Life Science Investigation Activity . 183.2.8 MRPWG Approval of the Increment Research Plan . 183.2.9 Payload Boards Approval of the Increment Research Plan . 193.3Other MRPWG Supporting Products . 193.3.1 Input for ISS Stage unique Load Shed Table (LST) . 193.3.2 Input for Pre-increment Science Symposium . 194Overall Mission Integration Process . 204.1Mission Integration Roles and Responsibilities. 204.2Mission Integration Processes. 204.2.1 Payload Integration Manager (PIM) Roles and Responsibilities . 204.2.2 Payload Integration Agreement (PIA) letter . 214.2.3 Hardware Feasibility Assessment . 214.2.4 Basic Understanding of the Increment Definition and Requirement Document(IDRD)--Annex 5--Development process. 224.2.5 Certificate of Flight Readiness (CoFR ) process . 224.2.6 Basic Understanding of the Change Evaluation Form Process . 234.2.7 Hardware Delivery . 234.2.8 Bench Review Process and Crew Equipment Interface Test (CEIT) . 235Overall Engineering Integration Process . 245.1Engineering Integration Roles and Responsibilities . 245.2Interface Requirements . 245.3Hardware Interface Control Document (ICD) . 265.4Stage Analysis . 26iii

OZ-10-056REVISION AJUNE 20105.5Guidelines and Constraints . 265.6Human Factors Integration Team (HFIT) Support . 265.6.1 ISS Payload Label Approval Team (IPLAT) Support . 275.7Acoustics Support . 285.8Verification Review/Approval and Tracking. 285.9Exceptions . 285.10 Conditioned Stowage Assets and Integration . 286Overall Software Integration Process . 286.1Software Integration Roles and Responsibilities . 286.2Software Architectures Description . 296.3Payload Software Integration Products . 346.3.1 Command and Data Handling (C& DH) Dataset Development . 346.3.2 Ground System Requirements Development via Ground Data Services Dataset. 346.4Laptop Software Products . 356.4.1 Display Development and Review. 356.4.2 Compatibility Testing . 356.4.3 Media Processing for Launch . 356.5Software Testing . 367Overall Payload Operations Integration Process . 367.1Payload Operations Roles and Responsibilities . 367.2Crew Training Process . 367.2.1 Training Strategy Process . 377.3Planning Process . 377.3.1 Planning Requirements Submittal. 377.3.2 Planning Product Development . 377.3.3 Real Time Usage of the On-Orbit Summary (OOS) by the LIS for OperationsDecision/Execution . 387.4Flight Product Development . 387.4.1 Crew Operations Procedures. 387.4.2 Ground Command Procedures . 397.4.3 Flight Rules/Payload Regulations . 397.5Ground Support Team Training . 397.5.1 Payload Developer (PD) Team Training . 407.5.2 Cadre/PD Simulations. 407.6POIC Ground Systems Services Products and Development . 407.6.1 Ground Support Capabilities. 417.6.2 Ground Support Services Standard Template . 417.6.3 Ground Data Services (GDS) Blank Book . 417.6.4 Network Interface Support Configuration Process . 427.6.5 Ground System IT Security Requirement Certification Process . 427.6.6 Ground Service Capability Training . 427.6.7 ISS Downlink Video . 427.6.8 Account Request Process . 428Overall Payload Safety Review Process . 43iv

OZ-10-056REVISION AJUNE 20108.1Payload Safety Review Panel (PSRP) . 438.1.1 Roles and Responsibilities . 438.1.2 Initial Contact Briefing . 438.1.3 Process Requirements . 448.1.4 Technical Requirements. 448.1.5 Safety Data Packages . 448.1.6 Hazard Reduction Precedence . 458.1.7 Certification . 468.1.8 Post Phase III Safety Review and Safety Verification Tracking Log (SVTL) . 468.1.9 Website and Data Management System Access . 468.2Ground Safety Review Panel (GSRP) . 468.2.1 Roles and Responsibilities . 468.2.2 GSRP Process Overview. 478.2.3 Pre-Arrival . 478.2.4 Ground Processing . 488.2.5 Post-Flight . 488.2.6 Ground Safety at International Partners Launch Sites . 488.2.7 Ground Safety at Non-KSC U.S. Launch Sites . 489Overall Export Control Process . 489.1What is an Export? . 489.2Payload Developers Responsibilities . 499.3Additional Resources for Exporters . 4910 Overall Testing Integration Process . 4910.1 Testing Process . 4910.1.1Payload Rack Checkout Unit . 5110.1.2Hardware and Software Turnover . 5110.1.3Payload Software Revision Verification . 5110.1.4Off-line Testing . 5210.1.5Pre-Integration Testing . 5210.1.6Integrated Testing Process . 5210.1.7Physical Interface Verification/Setup Procedure Validation . 5210.1.8Human Factors Verification . 5210.1.9Integrated Payload with Facility Testing . 5310.1.10 End-to-End Data Stream Testing . 5310.1.11 Fluid Charging/ Sampling . 5310.1.12 Post-Test Review . 5310.1.13 Test Reports . 5310.1.14 Escort Policy . 5411 Launch and Landing Support at KSC . 5411.1 Basic Understanding of KSC Support Requirements . 5511.1.1Support Requirement Generation . 5511.1.2Equipment Support . 5511.1.3Facility Requirement . 5511.1.4Shipping . 56v

OZ-10-056REVISION AJUNE 201011.2 Acceptance Data Package/Integrated Data Package (ADP/IDP). 5611.2.1Turnover Process . 5611.3 Cargo Integration and De-integration . 5611.4 Technical Requirements Development and Implementation . 5711.4.1Late Access/Launch Delay . 5811.4.2Recovery/Retrieval . 5812 Launch and Landing Site Support for the International Partners and NASA CommercialResupply Service (CRS) Vehicles . 5812.1 International Partners’ Vehicles Launch and Landing Support . 5812.2 NASA Commercial Resupply Service (CRS) Vehicles Launch and Landing Support 5912.3 Launch Vehicles On Dock Date Requirements . 5912.3.1ATV and HTV . 5912.3.2Progress and Soyuz . 6012.3.3CRS Dragon (SpaceX) and Cygnus (Orbital) . 6012.4 Launch Site Laboratory Support and Equipment Availability . 6012.5 On-Site Sample Processing and Sample Return . 6212.6 Vehicles Late Load Access . 6312.6.1ATV . 6312.6.2HTV . 6312.6.3Progress . 6412.6.4Dragon. 6412.6.5Cygnus . 6412.7 Launch Vehicles Environment . 6412.8 Launch Site Escort Policy . 6413 Overall Real Time Support Process . 6513.1 Basic Understanding of Real Time Support Requirements . 6513.1.1Payload Developer Operations Team Structure for on Console Support . 6513.1.2Operations Change Request (OCR) Process . 6513.1.3Payload Anomaly Report (PAR) Process . 6613.2 Real Time Increment Teams Structures and Functions . 6613.2.1International Space Station Mission Management Team (IMMT) . 6613.2.2Increment Research Team (IRT) . 6713.2.3Increment Payload Real Time Management Team . 6713.2.4Lead Increment Science Representative (LIS-Rep) . 6813.2.5Daily Science Tag (DST) . 6814 Post Reporting . 6914.1 Post Reporting Requirements and Products . 6914.1.1Payload Lessons Learned . 6914.1.2Payload Crew Debrief Questions . 7014.1.3Payload 30-day Report . 7014.1.4Payload One-year Science Report . 7115 Summary . 72Appendix A:Lean Payload Integration Process Description . 73Glossary of Terms . 92vi

OZ-10-056REVISION AJUNE 2010Appendix B:Appendix C:Appendix D:SAMPLE TEST READINESS REVIEW (TRR) PLAN . 93Acronym List and Definition . 98Contact and Contributors Acknowledgments . 103vii

OZ-10-056REVISION AJUNE 2010List of Tables and FiguresFigure 1 Standard Payload Integration vs. Lean Payload Integration Template . 13Table 1 – Software Integration Considerations for Highly Autonomous Payload Software . 29Table 4 – Software Integration Considerations for Software Based Research . 33Figure 10.1 Payload Testing Process Flow . 50Table A-1. Primer Content vs. Lean Payload Processing . 78Figure A-1 Lean Payload Integration Gate Process . 81Table A-2 Lean Integration Data Package . 82Figure A-2 Lean Payload Operations Integration Summary . 85Figure A-2 Lean Payload Operations Integration Summary . 85Table A-3 Lean EXPRESS Payload Interfaces . 86Figure A-3 Lean EXPRESS Payload Characteristics . 87Figure A-4 Ship and Shoot Processing Functional Flow . 89Table A-4 Lean MSG Payload Interfaces . 90viii

OZ-10-056REVISION A11.1JUNE 2010IntroductionObjectiveThe objective of this Payload Planning, Integration and Operations Primer is togive Payload Developers (PDs) and Principal Investigators (PIs) that are new to thepayload integration world an overview of the process and to outline the roles andresponsibilities of several organizations with whom the new PDs and PIs willinterface during the payload planning, integration and operations process. Thisprimer highlights the many products to which both PDs and PIs will either provideinputs to or develop for their own use, as well as identify services that are availablefrom several NASA ISS Payloads Office organizations that PDs and PIs will use aspart of the payload overall integration process.1.2LayoutThis primer starts from the beginning of the payload process and proceeds step bystep (albeit at a very high level) from a proposed payload to a “manifest payload”and from there to integration all the way to launch and payload return. In the lingoof the payload world, one will say from pre-increment planning, real time(execution), to post-increment. The main focus of this document is on the productsthat PDs/PIs need to develop, provide inputs to and the services that that areavailable to them to successfully accomplish their payload activities from preincrement planning to post-increment reporting.Every effort was made to eliminate as much as possible the daily lingo used in thecomplex world of payload integration in this document in order to make it asreadable as possible to the new-comers to this world. Throughout this documentthere are many web links that reveal themselves only while reading this documentfrom a display device. They are embedded in this document for those who mightwish to have more detailed information on a topic of interest. These web links takethe reader to the reference documents that were used to summarize the material forthat particular topic. All material (words, sentences, etc) in this document that isshown in a blue color has a web link embedded underneath; simply scroll themouse over it and follow the instruction to be redirected to that link.There is also a very important appendix in this document. Appendix A describes astreamlined payload integration process called “Lean Integration Process.” Theobjective of this Lean Integration Process is to make it easier for PDs to fly theirpayloads faster to ISS using a streamlined version of the standard PayloadIntegration Process. However, to use the Lean Integration Process certain criteriamust be met. All PDs and PIs are urged to carefully read Appendix A.9

OZ-10-056REVISION AJUNE 2010Finally, on the last page of this document, there is a list of Points of Contact withemail addresses that are provided as additional resources for PDs and PIs whomight want to seek some additional help or clarification on some of the topicscovered in this document.2BackgroundThe objective of this section is to discuss at a high level the overall ISS PayloadIntegration Process. Currently two payload integration templates are available tothe payload developer community: (1) The Standard Template and (2) The LeanTemplate. The standard Payload Integration Template is defined (in thisdocument) as one that involves the integration of a complex payload which requiresa high degree of integration with both the ISS vehicle and ground operations. Thestandard template is a flight/increment driven template in that a payload is assigneda flight on an increment and the Payload Developer (PD) works the associatedmilestones to meet that flight/increment’s template. The Lean Payload IntegrationTemplate, on the other hand, is PD’s payload readiness driven in that the PD startsthe ISS Payload Integration Process whenever the PD’s payload is ready and all theassociated integration technical data are completed for a flight assignment sixmonths prior to any available flight.2.1Payload Integration Templates DefinitionsAn increment is defined as a specific time period on the ISS which combinesdifferent operations. The duration of an increment is the time period from theundocking of a Russian Soyuz vehicle to the undocking of the next Soyuz.Currently, an increment lasts about six months. An increment is comprised of atleast one stage. A stage is a designated period defined by the ISS Program thatbegins and ends with a major activity on the ISS and is used for requirementsdocumentation and planning purposes. It is usually referred to as the period of onorbit configuration of the ISS after each flight which adds capability to the ISSvehicle.2.1.1Standard Payload Integration TemplateIf a standard integration template is used, the overall payload integration processcan be broken down into four phases: (1) Strategic; (2) Tactical; (3) Operations(Real-time); and (4) Post-Operations (Post-flight). The Strategic Phase defines thepayload requirements, the design and build hardware, safety reviews, the payloadincrement and flight assignment. The Tactical Phase defines the crew proceduredevelopment, the crew training, the requirements verification and the pre-shipreviews. The Operations Phase defines the integration of the hardware into thespacecraft, the launch, the on-orbit operations and the return of the payload fromthe ISS. The Post-Operations phase defines the vehicle deintegration requirements,10

OZ-10-056REVISION AJUNE 2010the return of payload samples/hardware from the landing site to the PayloadDeveloper (PD), the Lessons Learned, the Crew debrief and the required end ofmission or increment reports.The standard template timeframe for the payload integration process is defined interms of “Increment minus date” (I-XX), “Launch minus date” (L-XX) and“Return plus date” (R XX). An “Increment minus a date” indicates how manymonths, weeks or days an activity must occur before that increment begins. Forexample, I-6 Months indicates that six (6) months before that increment beginsitem X is due to the ISS Program from the Payload Developer. Currently, anincrement begins with the arrival or departure of a Soyuz vehicle. A “Launchminus a date” indicates how many months, weeks or days an activity must occurbefore that launch. Note that there might be multiple launches within an increment,therefore an ”increment minus date” is different from a “launch minus date”. Acrew’s “return plus a date” indicates when that activity begins after the end of thatincrement. The day the ISS crew returns to earth the clock is set to R 0 and itmoves forward from that point on.Some of the payload integration activities associated with the standard templateoccur sequentially, but the majority of them follows parallel paths. For example,the standard template normally begins with an agreement between the ISS Programand the PD. Such agreement is referred to as the Program Integration Agreement(PIA), which is discussed in the Mission Integration section below. After suchagreement is in place, a Payload Integration Manager (PIM) is assigned to help thePD navigates the ISS Payload Integration Process. From this point on, teams fromseveral NASA orga

Table 1 - Software Integration Considerations for Highly Autonomous Payload Software . 29 Table 4 - Software Integration Considerations for Software Based Research . 33 Figure 10.1 Payload Testing Process Flow . 50 Table A-1.