U.S. Payload Operations Data File Management Plan

SSP 58700, REV H

SSP 58700, REV H

U.S. PAYLOAD OPERATIONS DATA FILE MANAGEMENT PLAN

FLIGHT PROJECTS DIRECTORATE

CONCURRENCE

Prepared by:

/s/ Dorinna Thom2/12/04

Dorinna Thom, Book Manager, FD35Date

Concurred by:

/s/ Rose M. Lindsey 2/12/04

Rose Lindsey, Payload Operations Data File Control Board ChairDate

INTERNATIONAL SPACE STATION PROGRAM

U.S. PAYLOAD OPERATIONS DATA FILE MANAGEMENT PLAN

FLIGHT PROJECTS DIRECTORATE

LIST OF CHANGES

January 2004

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

TABLE OF CONTENTS

SectionPage

Revision and History Page...... 2

Concurrence Page...... 3

List of Changes...... 4

Table of Contents...... 5

1.DESCRIPTION OF THIS DOCUMENT...... 8

1.1Purpose of this Document...... 8

1.2How to Use this Document...... 8

1.3Scope...... 9

1.4Change Authority...... 9

1.5Applicable Documents...... 9

1.6Applicable Websites...... 10

1.7Publication and Revision of this Document...... 10

1.8Effectivity of Document...... 10

1.9How to Use This Document...... 10

1.10Export Control of the U.S. Payload Operations Data File (PODF)...... 10

2.OVERVIEW OF U.S. PODF...... 11

2.1Contents of U.S. PODF...... 11

2.2Initial Contact Between POIF and Payload Developer (PD)...... 12

2.3Products: Overview and Definitions...... 13

2.3.1Products Managed by the Crew Operations Team...... 16

2.3.1.1Operations Concept...... 16

2.3.1.2Displays...... 16

2.3.1.3Operations Nomenclature (OpNom)...... 16

2.3.1.4Manual Procedures...... 16

2.3.2Products Managed by Operations Control (OC) Team...... 16

2.3.2.1Ground Command Procedures...... 16

2.3.2.2Integrated Rack Safing Procedures...... 17

2.3.2.3Daily Status Check...... 17

2.3.3Products Managed by Command and Data Systems (CDS) Team...... 17

2.3.3.1Automated Procedures (Timeliner)...... 17

2.3.4Products Outside U.S. PODFCB Control...... 17

2.3.4.1Earth-To-Orbit Vehicle (ETOV) Procedures...... 18

2.3.4.2Hardware Labels: ISS Payload Label Approval Team (IPLAT).....18

2.3.4.3Hazard Report...... 18

2.3.4.4Procedure Hazard Control List...... 18

2.3.4.5Payload Hazard Control Matrix...... 18

2.4PODF-Related Teams...... 19

2.4.1Payload Developer (PD) Team...... 19

2.4.2Crew Operations Team...... 19

2.4.3Other PODF-Related Teams...... 22

3.DEFINING PAYLOAD OPERATIONS...... 24

3.1Overview...... 24

3.2Operations Concept...... 25

3.3Operations Analysis with Emphasis on Crew Roles...... 25

3.4Resources for Defining Payload Operations...... 26

4.DISPLAYS...... 27

4.1Developing Preliminary Displays...... 28

4.2Display Process Overview...... 29

4.3Displays and Procedures (Integrated) Process Flow...... 29

4.3.1Preliminary Displays Review Process...... 32

4.3.2Candidate Flight Displays Review Process...... 32

4.3.3Candidate Procedures Review Process...... 32

4.3.4Usability Verification...... 33

4.3.4.1Usability Verification Method...... 33

4.3.4.1.1Test...... 33

4.3.4.1.2Trial...... 34

4.3.4.2Usability Verification Plan...... 34

4.3.4.3Usability Verification Report...... 34

4.3.5Final Flight Displays...... 35

4.3.6Baselining Payload Displays...... 35

4.3.7Changing Baselined Payload Displays...... 36

4.4Displays Only Process Flow...... 36

4.5Procedures Only Process Flow...... 36

4.6Resources for Displays and Usability...... 36

5.OPERATIONS NOMENCLATURE (OpNom)...... 37

5.1OpNom Overview...... 37

5.2Developing and Submitting a Preliminary OpNom...... 39

5.3Pre-ECR Review...... 39

5.4OpNom Waiver...... 39

5.5Baselining an OpNom ...... 39

5.6Changing a Baselined OpNom...... 40

5.7Resources for OpNom...... 40

6.MANUAL CREW PROCEDURES...... 41

6.1Procedure Process Overview...... 41

6.2Developing Procedures...... 43

6.2.1Required Procedures...... 46

6.2.1.1Quick Response...... 46

6.2.1.2Payload Messages...... 46

6.2.1.3Procedure Hazard Control List...... 47

6.3Preliminary Delivery of Procedures...... 47

6.4Review and Revision of Procedures Prior to Baselining...... 47

6.4.1Usability Test...... 48

6.4.2Payload Training...... 48

6.5Baselining Procedures...... 48

6.6Resources for Procedures...... 50

7.REAL-TIME OPERATIONS...... 51

7.1Onboard Library...... 51

7.2PIMS...... 51

7.3Real-time Changes to PODF Products...... 52

7.3.1Displays...... 52

7.3.2Operations Nomenclature (OpNom)...... 52

7.3.3Manual Procedures...... 52

7.3.4Other PODF-Related Procedures...... 52

7.4Transition of Newly Baselined Products to Real-time Operations...... 52

7.4.1Displays...... 53

7.4.2OpNom...... 53

7.4.3Manual Procedures and Supporting Products...... 53

7.4.4Transition of Key Flight Specific Files...... 53

7.5.5Other PODF-Related Procedures...... 53

7.5Real-Time Library Maintenance...... 53

7.5.1Increment Transition of Payloads...... 53

7.6Resources for Real-time Operations...... 54

8.ODFCB REQUIREMENTS...... 55

8.1Safety of Flight...... 55

8.2Certificate of Flight Readiness (CoFR)...... 56

8.3U.S. PODF Flight Product Delivery...... 56

8.3.1Paper Products...... 56

8.3.2Flight Product Delivery...... 56

8.4Changes to SODF/FDF...... 56

8.4.1JSC Initiated SODF Changes...... 57

8.4.2MSFC Initiated SODF/FDF Changes...... 57

8.4.3REAL-TIME SOFD/FDF Procedures Changes...... 57

8.5Resources for ODFCB Requirements...... 57

TABLES

Table 1-1 Documents Applicable to the U.S. PODF Management Plan...... 9

Table 1-2 Web Sites Applicable to the U.S. PODF Management Plan...... 10

Table 2-1 Teams and PODF-Related Products They Manage...... 13

Table 2-2 Deliverables Managed by Crew Operations Team...... 20

Table 2-3 Deliverables Managed by OC Team...... 21

Table 2-4 Deliverables Managed by CDS Team...... 21

Table 4-1 Usability Test Types and Products...... 31

Table 4-2 Usability Test Participants Roles and Responsibilities...... 31

Table 6-1 Flight Procedure Categories and Descriptions...... 44

Table 6-2 Support (Not for Flight) File Categories and Descriptions...... 44

Table 6-3 Filenaming Convention...... 45

Table 6-4 POIF Team Responsibility for Procedure Review...... 49

FIGURES

Figure 2-1 Overview of U. S. PODF Products...... 12

Figure 2-2 Integrated Process for Crew Operations Team-Managed Products for Sub-rack Payloads.14

Figure 2-3 Integrated Process forCrew Operations Team-Managed Products for Facility-Class Payloads15

Figure 3-1 On-Orbit Payload Functions Allocated to System Elements

(Hardware, Software, Crew)...... 25

Figure 4-1 Display Template Due Dates for Subrack Payloads...... 28

Figure 4-2 PDRT Displays and Procedures (Integrated) Process Flow...... 30

Figure 5-1 OpNom Template Due Dates for Subrack Payloads...... 38

Figure 6-1 Manual Crew Procedure Template Due Dates for Subrack Payloads...... 42

APPENDICES

AAbbreviations And Acronyms...... 58

BTerms...... 61

CTemplates...... 63

1.DESCRIPTION OF THIS DOCUMENT

The section addresses these topics:

1.DESCRIPTION OF THIS DOCUMENT

1.1Purpose of this Document

1.2How to Use This Document

1.3Scope

1.4Change Authority

1.5Applicable Documents

1.6Applicable Websites

1.7Publication and Revision of this Document

1.8Affectivity of Document

1.9Resolution of Issues

1.10Export Control of the U.S. Payload Operations Data File (PODF)

1.1Purpose of this Document

The United States Payload Operations Data File (U.S. PODF) Management Plan documents the guidelines and processes for the development, review, maintenance, and control of payload displays, procedures, operations nomenclature, and related products that comprise the U.S. PODF. The charter and scope of authority of the U.S. PODFCB are defined in the Operations Data File (ODF) Management Plan (SSP 50252), which describes the processes for definition, development, and control of all ODF information for the International Space Station (ISS) program. Specific requirements levied on the U.S. PODF in the ODF Management Plan have been met and documented in this plan.

The purpose of this document is to: a) define the products, schedules, and responsibilities involved in producing and operating the U.S. PODF; b) make the process easy to understand and follow; and c) show how the U.S. PODF meets the requirements levied by the ODFCB. This document provides lists of resources that describe how products are developed. The resources include documents and web sites containing detailed instruction, templates, examples, etc.

The latest version of the U.S. PODF Management Plan resides on the Payload Operations Integration Function (POIF) web site. A copy of the document also resides on the Program Automated Library System (PALS) web site. See Table 1-2 for web site addresses.

1.2How to Use This Document

The U.S. PODF Management Plan provides a road map and reference guide to the parties responsible for developing and qualifying payload deliverables as ready for flight. Read Section 2 in its entirety for a comprehensive overview of the products (deliverables), schedules, and responsibilities under the umbrella of the U.S. PODF Control Board (U.S. PODFCB). Section 2 clearly states what comprises the U.S. PODF, what is presented in detail in this document, and where to find topics not covered in detail in this document.

Processes in this document are presented in sequence and should be worked in the order they occur. Each section contains an overview, schedule, concurrent activities, deliverables, responsibilities, review, approval (baselining), and reference material. This document is intended to make the processes easy to understand and follow.

The lessons for successfully developing products and qualifying them for flight are:

• develop the Operations Concept using a rigorous operations analysis approach before developing displays and procedures
• follow the sequence of processes laid out in this document; don't try to delay or omit one
• develop collaborative working relationships early with other team members and take advantage of their experience.

1.3Scope

The National Aeronautics and Space Administration (NASA), Agenzia Spaziale Italiana (ASI), and Agencia Espacial Brasileira (AEB) shall abide by this plan for all U.S. PODF related activities. The Russian Space Agency (RSA), European Space Agency (ESA), and Japanese Aerospace Exploration Agency (JAXA) shall abide by this plan for all multi-element payload procedures.

1.4Change Authority

This plan was developed under the authority vested in the Marshall Space Flight Center (MSFC) Flight Projects Directorate (FPD) and the POIF by the ODFCB.

1.5Applicable Documents

Table 1-1 provides a list of documents that are applicable to the extent specified within this document

Table 1-1 Documents Applicable to the U.S. PODF Management Plan

1.6Applicable Websites

Table 1-2 provides addresses of web sites that are referenced in this document.

Table 1-2 Web Sites Applicable to the U.S. PODF Management Plan

1.7Publication and Revision of this Document

The POIF at MSFC is responsible for overseeing the preparation, coordination, and maintenance of this document. The Chairperson of the U.S. PODFCB approves this document and all changes to it after approval by the U.S. PODFCB members. Annex 1 Payload Automated Procedures to this document is published separately.

Any changes to this document should be submitted by ECR to the U.S. PODFCB Chairperson. If there are comments or questions on this plan, contact the appropriate book manager.

1.8Effectivity of Document

The information, requirements and processes described in this document are effective beginning with Increment 8.

1.9Resolution of Issues

If a situation arises where the payload developer (PD) does not believe that the Crew Operations team point of contact (for OpNom, displays, or procedures) has adequately addressed their concern, the issue should be discussed with the U.S. PODFCB Chairperson.

1.10Export Control of the U.S. Payload Operations Data File (PODF)

The U.S. PODFCB will control the release of information to foreign persons as laid out in the SSP 58334 FD32 Configuration Management (CM) Plan for Payload Operations Integration. All documentation will be classified and controlled according to Export Control laws as defined by CFR 15 and CFR 22. CM personnel may use the services provided by NASA Center Export Representatives (CERs) to determine the eligibility of reviewers. The contents of the PODF and supporting documents are classified as EAR99 with no export license required. The MSFC Export Representative granted this classification in May 2001.

2.OVERVIEW OF U.S. PODF

This section defines the products (deliverables) which are included in the U.S. Payload Operations Data File (PODF), the teams that manage development of the products, the life cycle of a product, and reference material.

This section addresses these topics:

2.OVERVIEW OF U.S. PODF

2.1Contents of U.S. PODF

2.2Initial Contact Between POIF and Payload Developer (PD)

2.3Products: Overview and Definitions

2.3.1Products Managed by the Crew Operations Team

2.3.1.1Operations Concept and Operations Analysis

2.3.1.2Displays

2.3.1.3Operations Nomenclature (OpNom)

2.3.1.4Manual Procedures

2.3.2Products Managed by Operations Control (OC) Team

2.3.2.1Ground Command Procedures Books

2.3.2.2Integrated Rack Safing Procedures

2.3.2.3Daily Status Check Matrix

2.3.3Products Managed by Command and Data Systems (CDS) Team

2.3.3.1Automated Procedures (Timeliner)

2.3.4Products Outside U.S. PODFCB Control

2.3.4.1Earth-To-Orbit Vehicle (ETOV) Procedures

2.3.4.2Hardware Labels: ISS Payload Label Approval Team (IPLAT)

2.3.4.3Hazard Report

2.3.4.4Procedure Hazard Control List

2.3.4.5Payload Hazard Control Matrix

2.4PODF-Related Teams:

2.4.1Payload Developer (PD) Team

2.4.2Crew Operations Team

2.4.3Other PODF-Related Teams

2.1Contents of U.S. PODF

The U.S. PODF is the collection of payload procedures and related products that support International Space Station (ISS) payload operations under the umbrella of the U.S. PODF Control Board (U.S. PODFCB). The U.S. PODF addresses interfaces related to payloads including manual, ground, and automated procedures, displays, and related products. This includes not only U.S. payload procedures, but also ASI and AEB payload procedures. The procedures contained in the U.S. PODF are used by flight controllers, the onboard crew, and the automated procedure executor software to operate and maintain ISS payloads and payload support systems.

The payload developer (PD) team is the key player in the development of these products. Figure 2.1 illustrates the break out of products for ISS payload operations. Functions identified in the operations concept (see section 3) are allocated to the resource that best meets the payload objectives: crew activity, ground activity, or automated control. The products are then developed under the management (or coordination) of four teams, the Crew Operations, SOC, OC and CDS teams. The information presented in this document is grouped by the team that manages the development of the product.

Figure 2-1 Overview of U. S. PODF Products

U.S. PODF products are managed by four teams: Crew Operations, SOC, OC, and CDS.

Those products managed by Crew Operations are addressed in detail in this document.

2.2Initial Contact between POIF and Payload Developer (PD)

The Mission Integration organization assigns a Payload Integration Manager (PIM) to serve as an advocate who guides the PD in executing his or her roles and responsibilities during the payload development process. As the initial contact from Mission Integration to the PD, the PIM coordinates PD activities, including Export Compliance activities, the negotiated schedule, Integration Agreements (IAs), Interface Control Documents (ICDs), and Payload Verification Plans (PVPs). For more information on PIMs, go to the PMIT web site, look under Flight Assignments, and click on PIM assignments. A Payload Processes Overview is available on the OZ2 web site under Miscellaneous; Road Show.

PMIT web site:

OZ2 web site:

The Payload Operations Integration Center (POIC) Operations Technical Interchange Meeting (TIM) generally serves as the first working meeting between the PD and most of the Payload Operations Integration Function (POIF) teams. The POIF first contact briefings are presented at this operations TIM. It introduces the PD to the processes for displays, procedures, safety, stowage, labels, training, crew office, and operations control. The PD provides payload information, and the POIF teams provide resources information. Subsequent Training Strategy Team (TST) TIM meetings include only a subset of POIF teams. The TST TIMs are implemented via the Payload Training Implementation Plan (PTIP). See the POIF web site for POIF team contacts. The agendas for the TIMs are published in the PTIP SSP 58309, Appendix C NASA P/L Training Strategy Team Guidelines; see the POIF web site.

2.3Products: Overview and Definitions

Table 2-1 lists teams, the PODF-related products they manage, residency, and controlling authority. For more information on teams see section 2.4. For more information on the Payload Information System (PIMS) Mission, Operational Support Mode, and Project (MOP), see Section 7.2. Figures 2-2 and 2-3 illustrate the integrated process for the Crew Operations team -managed products for subrack payloads and facility class payloads. Tables listing deliverables (products) and template due dates for which the PD is responsible are in section 2.4.1.

Table 2-1 Teams and PODF-Related Products They Manage

Figure 2-2 Integrated Process for the Crew Operations Team -Managed

Products for Subrack Payloads

The PD negotiates actual dates with the PIM and the displays or procedures POC for each payload based on these template dates. Configuration Management (CM) determines dates for all activities in the baseline process

(ECR submittal, review period, Technical Change Meeting (TCM), and approval).