POH_Vol_2_2-2-18.pdf

POIF-1005

Approved for Public Release; Distribution is Unlimited

National Aeronautics and Space Administration International Space Station Program Marshall Space Flight Center Huntsville, Alabama

International Space Station

Payload Operations Handbook Volume 2: Increment Operations

Payload Operations Integration Center

February 2018

Revision O

(This Page Intentionally Blank)

February 2, 2018 i

REVISION AND HISTORY PAGE

REV. DESCRIPTION PUB. DATE

Document Under MSFC Control – Replaces SSP 58312 Revision F.

- Baseline Release per NPOCB PB3-02-0444 03/06

A Revised per NPOCB PB3-02-0474 08/06

B Revised per NPOCB PB3-02-0532/A 05/07

C Revised per NPOCB PB3-02-0568/A 10/07

D Revised per NPOCB PB3-02-0598 04/08

E Revised per NPOCB PB3-02-0634 10/08

F Revised per NPOCB PB3-02-0683 04/09

G Revised per NPOCB PB3-02-0784 04/10

H Revised per NPOCB PB3-02-0952 09/11

I Revised per NPOCB PB3-02-0996 04/12

J Revised per NPOCB PB3-02-1096 03/13

K Revised per NPOCB PB3-02-1161 11/13

L Revised per NPOCB PB3-02-1308 01/15

M Revised per NPOCB PB3-02-1420 01/16

N Revised per NPOCB PB3-02-1546 12/16

O Revised per NPOCB PB3-02-1747 2/18

February 2, 2018 ii

INTERNATIONAL SPACE STATION PROGRAM

PAYLOAD OPERATIONS INTEGRATION CENTER

PAYLOAD OPERATIONS HANDBOOK

VOLUME 2: INCREMENT OPERATIONS

CONCURRENCE

Edwin Smith HP21 Prepared by:

BOOK MANAGER ORGN

/s Edwin Smith 2-16-18

SIGNATURE DATE

Carrie Olsen HP21 Concurred by:

Operations Directors Office ORGN

/s Carrie Olsen 2/21/2018

SIGNATURE DATE

Jason Norwood HP20 Concurred by:

Assistant Manager for Flight Operations ORGN

/s/ Jason Norwood 2/16/18

SIGNATURE DATE

February 2, 2018 iii

February 2, 2018 iv

PAYLOAD OPERATIONS INTEGRATION CENTER

PAYLOAD OPERATIONS HANDBOOK

VOLUME 2: INCREMENT OPERATIONS

PREFACE

This document contains the Payload Operations Integration Center (POIC) Standard Operating Procedures (SOP). These procedures address increment operations activities internal to the POIC, both stationwide and U.S. partner, activities between the POIC and NASA Users, and activities between the POIC and other organizations such as Telescience Support Centers (TSC), Payload Engineering Integration (PEI), and Payload Software Integration and Verification (PSIV/F).

This document may be obtained from the POIF home page web site at https://poif.ndc.nasa.gov/station/. Questions or comments should be directed to Edwin Smith/EO03/MSFC/ (256)961-2263/edwin.b.smith@nasa.gov or the POD.

February 2, 2018 v

February 2, 2018 vi

INTERNATIONAL SPACE STATION OPERATIONS

PAYLOAD OPERATIONS INTEGRATION CENTER

PAYLOAD OPERATIONS HANDBOOK

VOLUME 2: INCREMENT OPERATIONS

LIST OF CHANGES

December 2016

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

CBD/OCR # ENTRY DATE CHANGE PARAGRAPH(S)

PB3-02-0444 March 2006 Baseline SOPs 1.4, 1.10, 1.13, 1.14, 1.17, 1.18, 3.1, 3.4, 3.7, 3.9, 3.10, 3.11, 3.12, 3.14, 4.1, 4.7, 5.2, 5.3, 6.2, 6.12, 6.13, 7.9, 7.13, 7.14, 10.1, 10.2, 10.3, 10.7, 10.8, 10.9, 11.18, 11.28, 11.29, 12.9,

13.1 and 13.4. Add new SOPs 4.9, 4.10, 6.23, and 9.3. Delete SOPs 5.1, 11.14, 11.15, 11.25, and 13.2

PB3-02-0474 August 2006 Revision A SOPs 1.5, 9.3, 5.3, 6.5, 6.6, 10.8, 1.4, 8.2, and 1.15. Add new SOP 11.14. Delete SOP 6.23.

PB3-02-0532/A May 2007 Revision B SOPs 3.8, 3.10, 3.11, 3.16, 4.1, 4.3, 4.5, 5.3, 6.7, 7.8, 7.11, 8.1, 8.3, 10.3, 10.8, 12.5, 12.9, and

12.12. Add new SOP 4.11.

Delete SOPs 6.24 and 11.16.

February 2, 2018 vii

CBD/OCR # ENTRY DATE CHANGE PARAGRAPH(S)

PB3-02-0568/A October 2007 Revision C Update SOPs 1.1, 1.2, 1.3, 1.5, 1.7, 1.8, 1.9, 1.11, 1.12, 1.14, 1.15, 1.17, 1.18, 3.5, 3.14, 4.1, 4.5, 4.6, 4.9, 4.10, 4.11, 5.2, 5.3, 6.3, 6.4, 6.5, 6.6, 6.7, 6.11, 6.12, 6.13, 6.14, 6.16, 6.18, 6.19, 6.21, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 7.11, 7.12, 7.13, 7.14, 8.2, 9.3, 10.1, 11.1, 11.2, 11.3, 11.6, 11.7, 11.9, 11.17, 11.22, 11.23, 11.24, 11.30, 12.1, 12.3, 12.4, 12.5, 12.6, 12.7, 12.8, 12.9, 12.10, 12.11, 12.12, 12.13, 12.14, 12.15, and 13.4. Add new SOPs 3.17, 4.12, and 6.23.

Delete SOPs 1.13, 1.16, 6.17, 11.20, 7.3, 11.6, 11.19, 11.18, and 12.2 and links to these procedures.

Update Introduction and Scope.

Additional Global Updates:

Change ISS FD to HOUSTON FLIGHT. Change FD loop to ISS FD loop. Delete instances of TV Ops and Data Plan loops.

PB3-02-0598 April 2008 Revision D Update SOPs 1.5, 1.7, 3.14, 3.16, 4.3, 4.5, 4.7, 6.3, 6.4, 7.7, 7.12, 8.2, 8.3, 10.1, 10.2, 11.7, 12.1, 12.5, 12.7, and 12.15.

Add new SOPs 1.13, 6.17, 6.24, 7.3, and 8.4.

Delete SOP 6.21 because it has been incorporated into SOP 6.4.

PB3-02-0634 October 2008 Revision E Update SOPs 1.15, 1.17, 4.7, 6.4, 6.13, 8.3, 10.2, 10.6, 10.7, 10.10, 12.1, 12.3, 12.4, 12.5, 12.6, 12.7, 12.8, 12.9, and 12.10 Add new SOPs 1.16 and 12.2

PB3-02-0683 April 2009 Revision F Update SOPs 1.4, 1.5, 1.6, 1.14, 3.4, 3.6, 3.10, 3.11, 3.14, 3.16, 4.1, 4.3, 4.5, 4.7, 5.2, 5.3, 6.2, 6.5, 6.6, 6.7, 6.19, 6.23, 7.3, 7.4, 7.6, 7.7, 7.9, 7.10, 7.11, 7.12, 7.13, 8.1, 9.1, 10.1, 10.2, 10.4, 10.7, 10.9, 12.3, 12.5, 12.9, 12.10, 12.15, 13.4 and appendix.

Add new SOP (OCR to Rev E) 7.15

February 2, 2018 viii

CBD/OCR # ENTRY DATE CHANGE PARAGRAPH(S)

PB3-02-0784 April 2010 Revision G Update SOPs: 1.1, 1.4, 1.7, 1.8, 1.9, 1.18, 3.7, 4.5, 4.11, 5.3, 6.2, 6.4, 6.15, 6.23, 7.9, 7.13, 7.14, 7.15, 8.3, 10.1,10.7, 10.8, 11.7, 12.5, 12.11 and 12.13 per the attachments.

Note: Editorial only changes to add EXPRESS Logistic Carrier and WORF to SOPs: 1.1, 1.7, 1.8, 1.9, 1.18, 5.3, 6.2, 6.4, 6.15, 6.23, 7.14, 10.7, 12.5, 12.11, 12.13 New SOPs: 1.19 and 10.11 Totally Rewritten (no track changes) SOPs: 3.4 and 3.13

PB3-02-0952 September

Revision H Added SOPs: 6.25, 10.12, 7.16 Deleted SOPs:1.6, 1.10, 6.16, 7.5, 7.11, 11.4, 11.11, 11.21 Updated SOPs: 1.2, 3.1, 1.3, 1.5, 1.7, 1.8, 1.9, 1.11, 1.12, 1.13, 1.14, 1.15, 1.16, 1.17, 1.18, 1.19, 2.1, 2.2, 3.4, 3.6, 3.10, 3.11, 3.12, 3.13, 3.14, 3.16, 3.17, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.9, 4.10, 4.11, 4.12, 5.2, 5.3, 6.4, 6.5, 6.6, 6.7, 6.12, 6.14, 6.17, 6.18, 6.20, 6.22, 6.23, 6.24, 7.2, 7.3, 7.4, 7.6, 7.7, 7.8, 7.9, 7.10, 7.12, 7.13, 7.14, 7.15, 8.1, 8.2, 8.3, 8.4, 9.1, 9.2, 9.3, 10.1, 10.3, 10.4, 10.5, 10.7, 10.8, 10.9,11.3, 11.17, 11.27, 12.13, 12.14, 13.4, Appendix A

February 2, 2018 ix

PB3-02-0996 April 2012 Revision I Added SOPs: 3.18, 3.19, 6.16, 12.1 Deleted SOPs:11.10, 12.1 to 12.14 Updated SOPs: 1.2, 1.9, 1.14, 3.4, 3.9, 3.13, 3.17, 4.1, 4.3, 4.7, 4.9, 5.2, 5.3,7.9, 7.10, 7.15, 7.16, 8.1, 8.3, 9.3, 10.1, 10.3, 11.5,

12.15 (moving to section 7..renumbered to 7.17) 13.1, 13.3, 13.4, vol2app

PB3-02-1096 March 2013 Revision J Added SOPs: 1-20, 3-20 Deleted SOPS: 6.1 Updated SOPS:1.1, 1.5, 1.7, 1.8, 1.11, 1.12, 1.13, 1.14, 1.15,1.18, 3.6, 3.13, 3.16, 4.3, 4.7, 4.9, 4.10, 4.12, 6.4, 6.8, 6.9, 6.11, 6.14, 6.16, 6.17, 6.19, 6.22, 6.24, 6.25, 7.3. 7.4, 7.6, 7.7, 7.9, 7.10, 7.12, 7.14, 8.2. 8.3, 10.9, 10.10, 11.9, 11.23, 11.24, 12.2, 13.1, 13.3, vol2app

PB3-02-1161 November

Revision K Added SOPs: 1.21, 1.22, 7.18, 7.19 Deleted SOPs: 1.16, 1.17 Updated SOPs: 1.1, 1.13, 1.8, 1.9, 1.15, 3.1, 3.11, 3.12, 4.3, 4,7, 4.9, 4.12, 6.5, 6.16, 6.24, 7.3, 7.4, 7.6, 7.7, 7.8, 7.9, 7.13, 7.14, 8.3, 8.4, 9.2, 9.3, 11.3, 11.17, 12.2, vol2app

PB3-02-1308 January 2015 Revision L Added SOPS 1.23, 7.20 Deleted SOPS: None Updated SOPS: 1.1, 1.5, 1.9, 1.14, 1.15, 1.21, 3.4, 3.10, 4.1, 4.3, 4.10, 5.3, 6.4, 6.6, 6.19, 6.5, 7.3, 7.14, 7.16, 7.19, 10.3, 10.8, 10.9, 10.10, Vol2 App, Doc Info tco1all000222 11/10/15 N/A Updated SOPS: 7.3, 7.4, 7.8 pod1all000741 11/16/15 N/A Updated SOPS: 3.4 pycmall000490 11/16/15 N/A Updated SOPS: 5.4 pod1all000742 11/25/15 N/A Updated SOPS: 3.18

PB3-02-1420 January 2016 Revision M Added SOPS: None Deleted SOPS: None Updated SOPS: 1.7, 3.16, 6.2, 6.8, 6.17, 6.19, 6.20, 6.22, 7.15, 7.18, 7.19, 10.1, 10.7 Updated SOPS(by OCR):

4.13,5.3, 6.26, 7.3, 7.6, 7.7, 7.8, 7.9, 7.10, 7.13, 7.14, 10.13, 13.4 Vol2 App, Doc Info

February 2, 2018 x fcolall000701 1/20/16 N/A New SOPS: 6.27 tco1all000224 1/20/16 N/A Updated SOPS: 4.7 pod1all000748 2/2/16 N/A Updated SOPS: 4.7, 6.5, 7.13 dmc1all000149 2/17/16 N/A New SOPS: 6.28 pod1all000753 3/11/16 N/A Updated SOPS: 7.9 ocpcall001317 3/28/16 N/A New SOPS: 1.6 pod1all000756 4/16/16 N/A Updated SOPS: 3.12 pom1all000113 5/12/16 N/A Updated SOPS: 2.2 ppm1all000185 5/25/16 N/A New SOPS: 7.21 sftyall000212 6/1/16 N/A New SOPS: 8.5 dmc1all000160 6/10/16 N/A Updated SOPS: 1.14, 1.15 stowall000328 7/6/16 N/A New SOPS: 9.4 pycomall000523 7/15/16 N/A Updated SOPS: 5.4 octmall000496 8/5/16 N/A Updated SOPS: 3.3, 4.3, 4.7, 4.9, 7.3, 7.4, 7.8 octmall000497 8/5/16 N/A Updated SOPS: 4.10 pom1all000143 8/16/16 N/A Updated SOPS: 7.14 dmc1all000163 8/16/16 N/A New SOPS: 1.10

PB3-02-1546 December

Revision N Added SOPS: 7.5, 7.11, 12.3 Deleted SOPS: 3.4, 4.2, 4.5, 4.11, 7.2, 7.15 Updated SOPS: 1.5, 1.7, 1.8, 1.9, 1.15, 1.18, 1.21, 3.5, 3.6, 3.7, 3.9, 3.11, 3.13, 3.15, 3.20, 4.1, 4.4, 4.6, 4.7, 4.9, 4.10, 5.2, 5.3, 6.19, 7.3, 7.5, 7.6, 7.7, 7.9, 7.10, 7.11, 7.12, 7.13, 7.16, 10.1, 10.2, 10.5, 10.11, 11.14, 11.24, 11.30, 13.1 Updated SOPS(by OCR): 1.6, 1.10, 1.14, 2.2, 3.3, 3.12, 4.3, 5.4, 6.5, 6.27, 6.28, 7.8, 7.14, 7.21, 8.5, 9.4

February 2, 2018 xi

NPOCB PB3-02-1609 3/31/17 Added SOPS: 6.1, 6.18 and 3.4 Deleted SOPS: 7.19 and 7.20 Updated SOPS:

1.4,1.12,1.14,1.15,1.19,1.21,1.23 ,2.1,2.2,3.3,3.4,3.6,3.7,3.8,3.9,3.

10,3.11,3.18,4.1,4.3,4.9,4.12,5.2, 6.2,6.3,6.4,6.5,6.8,6.10,6.11,6.12 ,6.14,6.15,6.16,6.22,6.26,7.3,7.5, 7.6,7.7,7.9,7.11,7.12,7.14,7.18,1 0.1,10.3,10.4,10.6,10.7,10.8,10.9 ,10.13,10.14,11.1,11.2,11.3,11.5, 11.7,12.3,13.3 and 13.4 Vol2 App, Doc Info

Deleted SOPS: 6.3 Updated SOPS: 11.9, 11.23, and 11.24

PB3-02-1617 April 20, 2017 N/A Updated SOP 1.1

PB3-02-1621 May 1, 2017 N/A Updated SOP 6.19

PB3-02-1669 August 9, 2017 N/A Updated SOPS: 1.1, 1.2,1.3, 1.4, 1.8, 1.9, 3.6, 3.9, 3.11, 3.13, 4.7, 4.13, 5.3, 5.4, 6.6, 6.7, 6.20, 7.9, 7.14, 8.1, 8.2 and 8.3

PB3-02-1683 August 28, N/A Added SOPS: 6.29,10.15,10.16 and 10.17

Updated SOPS: 10.8,10.9 and 10.10

PB3-02-1684 August 30, N/A Added SOP: 6.30

PB3-02-1703 October 27, N/A Updated SOPS: 1.4, 3.10, 4.4, 5.3, 6.2, 6.5, 6.7, 6.25, 7.3, 7.11, 8.1, 10.1, 10.2, 10.3, 10.5, 10.7, 10.12, 10.13, 10.14, 10.15, 11.1, 11.2, 11.3, 11.7, 13.1, Vol2 App, Doc Info

Deleted SOPS: 10.4, 10.8, 10.9 and 10.10

PB3-02-1721 November 17, N/A Added SOP: 3.21

PB3-02-1740 January 8, N/A Updated SOP: 1.15

PB3-02-1747 February 2, Revision O Updated SOPs: 1.14, 3.4, 3.16, 3.17, 4.1, 4.1, 4.7, 4.9, 4.12, 6.19, 7.3, 8.1, 8.3, 8.4, 8.5 and 12.3

February 2, 2018 xii

February 2, 2018 xiii

TABLE OF CONTENTS

SECTION PAGE

REVISION AND HISTORY PAGE ..........................................................i TITLE PAGE..............................................................................................ii PREFACE...................................................................................................iv LIST OF CHANGES ..................................................................................vi TABLE OF CONTENTS............................................................................viii LIST OF FIGURES ....................................................................................xiv LIST OF TABLES......................................................................................xv INTRODUCTION ......................................................................................xvi PURPOSE...................................................................................................xvi SCOPE ...................................................................................................xvi CHANGE CONTROL................................................................................xvi REFERENCE DOCUMENTS....................................................................xvii

1.0 ANOMALY COORDINATION

1.1 PAR PROCESSING ...................................................................................1.1-1

1.2 PAR GENERATION..................................................................................1.2-1

1.3 ACTIVATION OF TIGER TEAM AND EXTERNAL SUPPORTING

ORGANIZATIONS....................................................................................1.3-1

1.4 CONTINGENCY RESPONSE...................................................................1.4-1

1.5 UNPLANNED TRANSITION FROM THE PRIMARY PL MDM TO

THE BACKUP PL MDM...........................................................................1.5-1

1.6 RODENT RESEARCH EMERGENCY EUTHANASIA PROCESS .......1.6-1

1.7 EXPRESS AND WORF RIC REBOOT AND RECOVERY ....................1.7-1

1.8 PAYLOAD SAFING GUIDELINES .........................................................1.8-1

1.9 ON-BOARD ANOMALY TROUBLESHOOTING/COORDINATION ..1.9-1

1.10 SURFACE PRO 3 ANOMALY RESOLUTION .......................................1.10-1

1.11 ISS VIDEO SYSTEM ANOMALY ...........................................................1.11-1

1.12 C&DH AND C&T SYSTEMS ANOMALY..............................................1.12-1

1.13 UNPLANNED C&C MDM TRANSITION...............................................1.13-1

1.14 FAILURE OF AUTOMATED PAYLOAD SWITCH (APS) ...................1.14-1

1.15 PEHG FAILURE/LAN TRANSITION WITH JSL ...................................1.15-1

1.16 RESERVED

1.17 RESERVED

1.18 LOAD SHED RESPONSE AND RECOVERY.........................................1.18-1

1.19 PAYLOAD-GENERATED CAUTIONS AND WARNINGS...................1.19-1

1.20 POIC-MER INITIAL COORDINATION OF ANOMALIES ...................1.20-1

1.21 KU COMM UNIT ANOMALY RESOLUTION ......................................1.21.1

1.22 ISS HD VIDEO ANOMALY .....................................................................1.22.1

1.23 POIC FLASH ALERT................................................................................1.23.1

2.0 FIRE AND WEATHER

February 2, 2018 xiv

2.1 FIRE AND SEVERE WEATHER..............................................................2.1-1

2.2 INSTRUCTIONS FOR SUPPORT DURING REDUCED STAFFING

SITUATIONS .............................................................................................2.2-1

3.0 GENERAL OPERATIONS

3.1 CONSOLE LOG.........................................................................................3.1-1

3.2 CONSOLE LOG STORAGE AND ARCHIVAL .....................................3.2-1

3.3 CADRE HANDOVER AND SITUATION REPORT GUIDELINES ......3.3-1

3.4 PD STATUS DISPLAY…………………………………………………..3.4-1

3.5 USER SCIENCE INPUT TO LIS REP .....................................................3.5-1

3.6 CADRE COMMUNICATION METHODS ..............................................3.6-1

3.7 ON-CALL AND OFF-DUTY SUPPORT POSITION ACTIVATION &

RESPONSIBILITIES ................................................................................3.7-1

3.8 CONSTRAINTS TO PAYLOAD OPERATIONS.....................................3.8-1

3.9 USER CONSOLE CHECK-IN/OUT PROCEDURE.................................3.9-1

3.10 REALTIME OPERATIONS FEEDBACK COORDINATION.................3.10-1

3.11 PAYLOAD DEVELOPER COMMUNICATION METHODS.................3.11-1

3.12 ON-THE-JOB TRAINING.........................................................................3.12-1

3.13 PROCESSING MESSAGES SENT FROM POIC.....................................3.13-1

3.14 POIC CADRE ERROR REPORTING .......................................................3.14-1

3.15 PAYCOM STAFFING DURING LIMITED PAYLOAD

OPERATIONS ……………………………………………………………3.15-1

3.16 PAIL SUBMISSION, RESOLUTION AND CLOSURE………...…….…3.16-1

3.17 PAYLOAD OPERATIONS LEAD SUPPORT OF PLANNED REAL TIME

OPERATIONS ……………………………………………………………3.17-1

3.18 CONFIGURATION TRACKING LOG…………………………………..3.18-1

3.19 FACILITY OPERATIONS LEAD SUPPORT…………………………...3.19-1

3.20 PAYLOAD DEVELOPER CONSOLE REPORT TIME COORDINATION..

…………………………………………………………………………….3.20-1

3.21 RODENT RESEARCH (RR) SUBJECT MATTER EXPERT (SME) ROLES

AND RESPONSIBILITES……………………………………………….3.20-1

4.0 CREW COMMUNICATION

4.1 PAYLOAD FLIGHT CREW COMMUNICATION...................................4.1-1

4.2 RESERVED

4.3 SPACE-TO-GROUND (S/G) ENABLEMENT OF POIC CADRE

AND USERS ...............................................................................................4.3-1

4.4 ON-BOARD CREW TRAINING MANAGEMENT..................................4.4-1

4.5 RESERVED

4.6 EXECUTE PACKAGE INPUTS ................................................................4.6-1

4.7 NON-IMAGE FILE UPLINK/DOWNLINK AND DISTRIBUTION........4.7-1

4.8 USER REQUESTS FOR CREW MEDICALLY SENSITIVE DATA

VIA PMC .....................................................................................................4.8-1

4.9 REAL-TIME IMAGE REQUESTS.…………………………………….…4.9-1

February 2, 2018 xv

4.10 PAYLOAD SPECIFIC IMAGERY DOWNLINK AND

DISTRIBUTION….………………...……………………………………..4.10-1

4.11 Reserved

4.12 GENERIC PAYLOAD VIDEO DISTRIBUTION PROCESS …………..4.12-1

4.13 FLASH CARD COORDINATION …………............4.13-1

5.0 CREW PROCEDURES

5.1 RESERVED

5.2 MANUAL CREW PROCEDURE LOG FILE AND CREW RECORDED DATA

FILE DOWNLINK .....................................................................................5.2-1

5.3 US PODF MANUAL CREW PROCEDURE CHANGES FOR IPV ........5.3-1

5.4 DEVELOPING EXECUTE TAILORED PROCEDURES ........................5.4-1

6.0 COMMAND AND CONTROL

6.1 WORF SHUTTER ACTUATOR SYSTEM USE DURING VISITING VEHICLE

DOCKED/BERTHED OPERATIONS…………………………………...6.1-1

6.2 EXPRESS OR WORF RACK INTERFACE CONTROLLER (RIC)

TABLE FILE UPDATE PROCESS………………. ..................................6.2-1

6.3 RESERVED

6.4 NASA RACK OPERATIONS AND SUBRACK PAYLOAD

OPERATIONS............................................................................................6.4-1

6.5 COMMAND LINK MANAGEMENT.......................................................6.5-1

6.6 CRITICAL COMMAND COORDINATION ............................................6.6-1

6.7 HAZARDOUS COMMAND COORDINATION......................................6.7-1

6.8 PL MDM MSD KU-BAND FILE DOWNLINK .......................................6.8-1

6.9 TIME TAG BUFFER RECYCLE ..............................................................6.9-1

6.10 S-BAND FILE UPLINK PROCEDURE....................................................6.10-1

6.11 DATA SYSTEMS CONTROL/COORDINATION...................................6.11-1

6.12 NEAR REALTIME VIDEO DUB REQUEST...........................................6.12-1

6.13 PERMANENTLY MISSING INTERVAL (PMI) TRACKING................6.13-1

6.14 CONTROL AND COORDINATION OF REALTIME AND

NEAR-REALTIME VIDEO.......................................................................6.14-1

6.15 EXPRESS OR WORF RACK LAPTOP VIDEO ROUTING

COORDINATION......................................................................................6.15-1

6.16 AMS AUTOMATED PAYLOAD SWITCH (APS)

CONFIGURATIONS .................................................................................6.16-1

6.17 PLANNED TRANSITION FROM THE PRIMARY PL MDM TO THE

BACKUP PL MDM ...................................................................................6.17-1

6.18 KU IP SERVICES………………………………………………………...6.18-1

6.19 C&C AND PL MDM HRDL CARD RESET AND RECOVERY ............6.19-1

6.20 BACKUP COMMANDING FOR PAYLOAD USERS.............................6.20-1

6.21 RESERVED

6.22 SUBMITTING A FILE FOR UPLINK/DOWNLINK AND TRANSFER

THROUGH THE PL MDM........................................................................6.22-1

6.23 RESERVED………………………………………....................................6.23-1

6.24 PLANNED C&C MDM TRANSITION ....................................................6.24-1

February 2, 2018 xvi

6.25 REALTIME UPDATE OF PAYLOAD EXECUTIVE SOFTWARE (PES)

CURRENT VALUE TABLES (CVT)........................................................6.25-1

6.26 KU IP SERVICES FILE UPLINK PROCEDURE .....................................6.26-1

6.27 EXPRESS SUBRACK LAPTOP PAYLOAD APPLICATION

UPLINK AND INSTALL........................................................................... 6.27-1

6.28 PAYLOADS NETWORK ATTACHED STORAGE .................................6.28-1

6.29 SPACEBORNE COMPUTER…………………………………………….6.29-1

6.30 KU IP SERVICES FILE UPLINK PROCEDURE FOR MSG FACILITY AND

MSG PAYLOADS………………………………………………………...6.30-1

7.0 PLANNING

7.1 PRE-IMMT TAG-UP TELECON SUPPORT ..........................................7.1-1

7.2 RESERVED

7.3 PLANNING PRODUCT UPDATES .........................................................7.3-1

7.4 PLANNING CHANGE REQUEST COORDINATION............................7.4-1

7.5 CONTINGENCY PLAN DEVELOPMENT COORDINATION ………..7.5-1

7.6 PAYLOAD WEEKLY LOOK-AHEAD PLAN (WLP)

DEVELOPMENT COORDINATION .......................................................7.6-1

7.7 PAYLOAD SHORT TERM PLAN (STP) DEVELOPMENT

COORDINATION......................................................................................7.7-1

7.8 OSTP REPLANNING ................................................................................7.8-1

7.9 OSTP REVIEW ..........................................................................................7.9-1

7.10 TASK LIST DEVELOPMENT ..................................................................7.10-1

7.11 TIMELINE INTEGRATION PRODUCT SUMMARY (TIPS)………….7.11-1

7.12 DATA FLOW PLAN (DFP) GENERATION............................................7.12-1

7.13 OBSERVATION PLANNING PROCESS ................................................7.13-1

7.14 READINESS CHECK FOR PAYLOAD OPERATIONS .........................7.14-1

7.15 RESERVED

7.16 ISS HAM CONTACT PLANNING PROCESS...………………………..7.16-1

7.17 EXPRESS RACK PAYLOAD RELOCATIONS ...………………...……7.17-1

7.18 SCAN TESTBED PLANNING AND OPERATIONS ..............................7.18.1

7.19 RESERVED

7.20 RESERVED

7.21 TRANSLATION OF ACTIVITIES FOR RUSSIAN CREW....................7.21.1

8.0 SAFETY

8.1 UPDATING PAYLOAD HAZARD CONTROL MATRIX

(PHCM) DOCUMENT...............................................................................8.1-1

8.2 PAYLOAD SAFETY COORDINATION..................................................8.2-1

8.3 VALIDATING, INSTALLING AND ACCESSING HAZMAT...............8.3-1

8.4 PAYLOADS WITH EXPIRED SAFETY CERTIFICATIONS……...…..8.4-1

8.5 POIC RESPONSIBILITIES FOR YELLOW TAGGED PAYLOADS.....8.5-1

9.0 STOWAGE

February 2, 2018 xvii

9.1 LOCATING STOWAGE DURING ON-BOARD INVENTORY

MANAGEMENT SYSTEM (IMS) FAILURE ..........................................9.1-1

9.2 INVENTORY AUDIT REQUESTS...........................................................9.2-1

9.3 COLD STOWAGE LOCATION COORDINATION/UPDATES….……9.3-1

9.4 WASTE DISPOSAL….……......................................................................9.4-1

10.0 FLIGHT SUPPORT PRODUCTS

10.1 REAL-TIME INTERIM UPDATES TO OPERATIONS

DOCUMENTATION .................................................................................10.1-1

10.2 UPLINKING PAYLOAD AUTOMATED PROCEDURES .....................10.2-1

10.3 PAYLOAD OPERATIONAL PRODUCT RELEASES AND POIC FORMS

……………………….................................................................................10.3-1

10.4 RESERVED

10.5 OPERATIONS APPEAL PROCESS .........................................................10.5-1

10.6 MATERIALS AND DOCUMENTS ARCHIVAL, STORAGE AND

RETRIEVAL ..............................................................................................10.6-1

10.7 GROUND COMMAND PROCEDURES BOOK UPDATES...................10.7-1

10.8 RESERVED

10.9 RESERVED

10.10 RESERVED

10.11 MSFC REALTIME COFR PROCESS FOR ONBOARD INACTIVE

PAYLOADS ...............................................................................................10.11-1

10.12 POI APPROVAL OF SYSTEM OR PARTNER PRODUCTS ON BEHALF OF

A PAYLOAD DEVELOPER .....................................................................10.12-1

10.13 OCR GENERATION FOR PAYLOAD SOFTWARE UPDATES……... 10.13-1

10.14 TRANSLATION OF PAYLOAD OPERATIONS PRODUCTS

INTO RUSSIAN.........................................................................................10.14-1

10.15 OPERATIONS CHANGE REQUEST PROCESSING…………………..10.15-1

10.16 OCR GENERATION……………………………………………………..10.16-1

10.17 OCR GENERATION FOR NEW/MODIFIED ACTIVITIES OR SCHEDULING

CHANGES………………………………………………………………..10.17-1

11.0 GROUND SYSTEMS

11.1 POIC FACILITY/REMOTE SITE PROBLEM REPORTING..................11.1-1

11.2 POIC SYSTEM STATUS AND COORDINATION .................................11.2-1

11.3 GROUND SYSTEMS RECOVERY..........................................................11.3-1

11.4 RESERVED

11.5 REALTIME COMMAND AND TELEMETRY DATABASE

MODIFICATION .......................................................................................11.5-1

11.6 RESERVED

11.7 HOSC FACILITY SERVICE OUTAGE COORDINATION....................11.7-1

11.8 HOSC DROP BOX SYSTEM LOSS WORKAROUND PROCEDURE ..11.8-1

11.9 REQUIRED CONFIGURATIONS FOR LOW-RATE S-BAND..............11.9-1

11.10 RESERVED

11.11 RESERVED

February 2, 2018 xviii

11.12 HOSC ACCESS APPROVAL....................................................................11.12-1

11.13 NEW/UPGRADED SOFTWARE INSTALL REQUESTS FOR

MISSION PC ..............................................................................................11.13-1

11.14 JSC-MAS ACCOUNT TEMPORARY EXTENSION…………………...11.14-1

11.15 RESERVED

11.16 RESERVED

11.17 LOSS OF PPS SYSTEMS..........................................................................11.17-1

11.18 RESERVED

11.19 RESERVED

11.20 RESERVED

11.21 RESERVED

11.22 PAYLOAD DATA SERVICES SYSTEM (PDSS) DATA STORAGE

MANAGER (DSM) PLAYBACK PRIORITY..........................................11.22-1

11.23 PAYLOAD DATA SERVICES SYSTEM (PDSS) DATA STORAGE

MANAGER (DSM) REBOOT...................................................................11.23-1

11.24 PDSS TIMELINE CHANGES ...................................................................11.24-1

11.25 RESERVED

11.26 POIC AND REMOTE SITES COMMAND INTERFACE AND

VERIFICATION.........................................................................................11.26-1

11.27 MCC-H DROPBOX PASSWORD CHANGE NOTIFICATION..............11.27-1

11.28 IPV SERVER FAILOVER.........................................................................11.28-1

11.29 IPV SOFTWARE PROBLEM RESOLUTION..........................................11.29-1

11.30 IPV RECONFIGURATION .......................................................................11.30-1

12.0 VISITING VEHICLE

12.1 VISITING VEHICLE TRANSFER OPERATIONS PHILOSOPHY........12.1-1

12.2 COORDINATION OF THE PREPACK/UNPACK/PACK/TRASH LISTS

…………………………………………………………………………….12.2-1

12.3 CREATION AND IMPLEMENTATION OF THE VISITING VEHICLE NASA

PAYLOAD INHIBIT PAD……………………………………………….12.3-1

13.0 TRANSITION

13.1 GENERIC TRANSITION COORDINATION...........................................13.1-1

13.2 RESERVED

13.3 CONFIGURING THE PRIMARY AND BACKUP PL MDM FOR

OPERATIONS............................................................................................13.3-1

13.4 UPLINKS OF USPODFCB APPROVED CREW PROCEDURES IN IPV

…………………………………………………………………………….13.4-1

APPENDIX A ABBREVIATIONS AND ACRONYMS...............................A-i APPENDIX B CADRE POSITION DESCRIPTIONS.................................B-i APPENDIX C GLOSSARY OF TERMS.......................................................C-i APPENDIX D TBR/TBD MATRX ................................................................D-i

February 2, 2018 xix

LIST OF FIGURES

FIGURE PAGE

1.2-1 PAYLOAD ANOMALY REPORT FORM .........................................1.2-2

1.3-1 TIGER TEAM AND EXTERNAL INTERFACES .............................1.3-2

3.5-1 PAYLOAD SCIENCE STATUS REPORT FORM .............................3.5-2

3.12-1 OJT RECORD SAMPLE......................................................................3.12-5

4.10-1 EARTHKAM PHOTO DISTRIBUTION PROCESS……………….. 4.10-4

4.11-1 CREW TRAINING MATERIALS REAL TIME TRACKING

MATRIX...............................................................................................4.11-3

5.3-1 REALTIME IPV LIBRARIES USE/MANAGEMENT.......................5.3-2

6.22-1 FILE UPLINK/DOWNLINK ...............................................................6.22-7 7.14-1 JUST-IN-TIME MILESTONE TEMPLATE .......................................7.14-2 10.8-1 OCR PROCESSING FLOW ................................................................10.8-4 10.11-1 COFR MATRIX FORM.......................................................................10.11-3

February 2, 2018 xx

LIST OF TABLES

TABLE PAGE

1.4-I POIC SYSTEM IMPOUNDMENT LIST…………………………….1. 4-5

1.14-I LEGACY APS FAILURE IMPACTS..................................................1.14-2 1.14-II APS FAILURE IMPACTS...................................................................1.14-3

1.14-III RECONFIGURATION PROCEDURE MATRIX .…………………..1.14-5

3.6-I POSITION CALL SIGN, SHIFT, PRIME LOOP, BACKUP

COMM and EMAIL ADDRESS ...........................................................3.6-2 3.9-I TSC PHONE NUMBERS .....................................................................3.9-2 3.11-I MSFC VOICE LOOPS SETS .............................................................. 3.11-2 3.11-II MSFC/PD VOICE LOOPS .................................................................. 3.11-3

3.11-III LSOS WITH DVIS LOOPS AVAILABLE……………………… ......3.11-5

3.18-I CONFIGURATION TRACKING LOG………………………………3.18-2

4.1-I GUIDE TO PAYLOAD CREW COMMUNICATION METHODS....4.1-2

4.1-II POIF DAILY SUMMARY INPUT GUIDELINES ..............................4.1-8

5.3-I US PODF CHANGE SUPPORTING ATTACHMENT

DESCRIPTIONS ...................................................................................5.3-3 5.3-II PODF REVIEW RESPONSIBILITIES.................................................5.3-6 6.5-I COMMAND RESPONSE TABLE .......................................................6.5-4 6.6-I POIC CRITICAL COMMANDS ..........................................................6.6-3

7.9-I PCA-1 TIMELINE REVIEW RESPONSIBILITY.............................. 7.9-2

7.9-II OSTP REVIEW MATRIX ....................................................................7.9-5

7.12-I PRELIMINARY AND FINAL DFP DEVELOPMENT SCHEDULE. 7.12-2

7.14-I JUST IN TIME MEETING PARTICIPANTS ......................................7.14-3 10.3-I PAYLOAD OPS PRODUCTS/LOCATIONS ......................................10.3-2 10.8-I ADVANCE TIMES FOR OCRS...........................................................10.8-3 11.1-I POIC PROBLEM REPORTING MATRIX ..........................................11.1-3

11.1-II REMOTE SITE PROBLEM REPORTING MATRIX..........................11.1-5

11.3-I ISS CRITICAL SERVICES IDENTIFICATION GUIDELINES.........11.3-3

February 2, 2018 xxi

INTRODUCTION

The operations concept for POIC payload operations requires the development of an efficient team consisting of the POIC cadre, the User Operations teams, and the payload crew. This team concept requires a well-prepared group of people dedicated to getting the job completed. The success of operating the ISS fully depends on developing a good mission design, having a well-trained payload crew with good on-board procedures, having a cohesive, trained cadre and User community, and practicing all of these facets in a high-fidelity environment.

This document defines the payload Standard Operations Procedures (SOP) for the POIC.

These procedures establish the standard operating procedures used in planning, organizing, and controlling the payload operations that are managed by POIC. These procedures define the responsibilities, personnel interfaces, and the step-by-step operations.

PURPOSE

The purpose of this document is to provide consistent procedures for the conduct of payload operations for all payloads managed by the POIC.

SCOPE

The procedures defined in this document define the POIC interfaces and tasks required to conduct real-time payload operations. These procedures apply to the POIC cadre and NASA User organizations, including International Partners operating a payload within a NASA payload rack. The procedures defined in this document also apply to International Partners for sortie and powered or complex ETOV transfer operations. All other procedures involving International Partners are defined in the Operating Interface Procedures (OIPs) and are only referenced in this document. Procedures defining interfaced with MCC-H are defined in the Joint Operation Interface Procedures (JOIP).

CHANGE CONTROL

The POIC POH will be under the control of the NASA Payload Operations Control Board (NPOCB). Changes to POH require submission of an MSFC Engineering Change Request (ECR) to the NPOCB. Interim changes are made via Operations Change Request (OCR).

February 2, 2018 xxii

REFERENCE DOCUMENTS

Concept of Operation and Utilization (SSP 50011-01, Rev C) Execute Planning Process Definition (SSP 50474) Flight Control Operations Handbook (FCOH), Station Operations (JSC-29229) Generic Remote Joint Operations Procedures (RJOP-178C) Generic Requirements for the EHS (MSFC-RQMT-1440) Getting Started with HOSC Applications Software (HOSC-EHS-120) HOSC Users Handbook (HOSC-HUH-233) Increment Definition and Requirement Document (IDRD) (SSP 54103) ISS Generic Requirements, Groundrules and Constraints, Vol. 2: Execute (SSP

50261-02) ISS Increment-Specific Execute Planning Groundrules and Constraints - Payload

Portion MCC-H/POIC Joint Operations Interface Procedures (JOIP), Execution

Operations (SSP 58034) MSFC Space Shuttle Contingency Plan (MSFC-SSCP-5-77-REV-A) Configuration Management Plan for Payload Operations Integration (SSP

58334/POIF-1007)

NASA Payload Regulations (POIF-1190) NASA Mishap Reporting and Investigating Policy (NPD 8621.1G) ODF Management Plan (SSP 50252) On-Orbit Inventory Stowage Implementation Plan (SSP 50427) OSTP Operations Manual (POIF-OC-0006) Payload File Transfer Operations Manual (POIF-OC-0009) Payload Operations and Integration Function (POIF) Data Management Plan (SSP

58335/POIF-1008)

POIC POH Volume 1: Pre/Post-Increment Operations (POIF-1004) Payload Support Systems (PLSS) Operations Manual (POIF-OC-0011) Payload to Ground User Interface Definition Document (SSP 50305) Payload Executive Processor (PEP) Operations Manual (POIF-OC-0005) PIMS Ops Concept POIC Capabilities Document (PCD) (SSP 50304) POIF Payload Stowage Operations Manual (POIF-OI-0008) Pressurized Payloads Generic Verification Plan (SSP 57010) Station Program Implementation Plan (SPIP) Vol. 9: Realtime Operations (SSP

50200-09) Support Count Handbook (SCH) TDRSS Network Operations Support Plan (TNOSP) for ISS (450-602/ISS) U.S. PODF Management Plan (SSP 58700/POIF-2001) U.S. PODF Management Plan, Payload Timeliner Automated Procedure Annex 1

(SSP 58700-ANX1/POIF-2001-ANX1)

Using the HOSC Database Change Software (HOSC-EHS-190)

SOP 1.1 PAYLOAD ANOMALY REPORT (PAR) PROCESSING

February 2, 2018 1.1-1 POIF-1005 Revision O

PURPOSE

To define the procedure for processing Payload Anomaly Reports (PARs).

PARTICIPATION

POIC Cadre POIC Safety *POD RICO Users OC PSE SpOC

EFFECTIVITY

Non-Flight Specific

REFERENCE DOCUMENTATION

Generic Operations Interface Procedures, SSP 50643-GEN

GENERAL

A U. S. Payload anomaly (referred to as “anomaly”) is defined as an unexpected response during nominal operation of POIC Operated Equipment, U. S. Payload Facilities, U. S.

Payloads, or during execution of crew and/or ground procedures affecting the previously mentioned equipment. If a U.S. Payload anomaly affects crew safety, ISS vehicle safety, ISS common hardware, or IP systems, it is considered an Integrated Anomaly. Integrated Anomalies are defined in more detail in the Generic OIP and must be documented in the MIS Anomaly Log tool (Gen OIP SOP 9.2).

A PAR is the only real-time POIC document used for collecting and summarizing anomalies.

All PARs are tracked in the ISS Problem Analysis Reporting Tool (PART) hosted on MCC-H Gateway Engineering tab.

The purpose of a PAR is to:

1. Record off-nominal behavior with sufficient information of the circumstances surrounding the anomaly to enable experts to analyze the anomaly off line.

2. Drive resolution of the anomaly or provide an operational workaround to avoid the anomaly in the future.

3. Fully document all aspects of the operational anomaly analysis for future reference.

NOTE: This procedure documents the closed-loop process used by the POIC to effectively report, analyze, document, and disseminate disposition of payload on-orbit anomalies.

February 2, 2018 1.1-2 POIF-1005 Revision O

In the event of an anomaly, the primary responsibility of the real-time cadre is to ensure the safety of the crew or vehicle. After crew and vehicle safety issues have been addressed, the real-time cadre addresses complete or partial failure of system equipment, facilities, or payloads affected by the anomaly. In general, the User (Payload Developer or Operator of the affected system) will document the anomaly, analyze available data, determine troubleshooting for further diagnosis, develop resolution, provide necessary crew procedures (if needed), and seek scheduling for performance of troubleshooting using relevant POIC processes. The User also updates the PAR to reflect status of anomaly resolution through to closure.

All POIC Operated Core System Hardware (e.g. PEHG, APS, PLMDM, HRFM, HCOR, VTR, VSU, SCU and VBSP), U.S. Payload Facility (facility class payload rack, EXPRESS Rack, EXPRESS Logistics Carrier), U.S. Payload, and Laboratory Support Equipment (LSE) anomalies that affect Payload Operations, including anomalies occurring during Shuttle flights, will be documented in a PAR and tracked in PAL.

PAR Criteria:

All payload anomalies must be reported on the POD Loop. However, not all anomalies require opening a PAR. The criteria for opening are the following:

1. Anomaly affects any system external to the payload, including other payloads.

2. Anomaly is a safety concern, violates a hazard control, or has potential for a hazardous condition.

3. Anomaly causes a loss of science.

4. Anomaly causes a loss of insight into payload status greater than 60 seconds.

5. Anomaly requires POIC action to correct or safe the payload, or requires POIC to contact PD.

For example: power cycle, unscheduled commanding, crew call/action, etc…

6. PD requests a PAR.

These criteria are written to allow Payload Developers more flexibility in operating onboard ISS. Anomalies that are isolated completely internal to a payload and do not meet above criteria do not require opening a PAR, although they still need to be reported on the loops to POIC. Temporary loses of Health and Status (H&S) or telemetry are common occurrences on ISS and incidences of less than 60 seconds do not need to be documented.

February 2, 2018 1.1-3 POIF-1005 Revision O

Anomalies for duplicate payloads: Payloads with multiple identical items, such as MELFI or SABL. POIC will document anomalies on duplicate payloads in a separate PAR specific to the duplicate payload. The reason being that the resolution and corrective action is not always the same across duplicate payloads. As appropriate, these duplicate PARs will be fast tracked to closure.

PAR Status Review Team (PSRT):

POIC maintains a PSRT chaired by a POD with membership representing PSE, POIC Safety, and Payload Engineering Integration. MER Managers and PIRATe support as required for OB Managed Payload Facilities.

The PSRT provides assistance to PDs for closing PARs and approves all PAR dispositions. The PSRT Chair can also approve fast tracking PARs to closure.

PAR Rules:

The following rules shall be followed to document and resolve PARs. Any exceptions must be approved by the PSRT Chair or POM.

1. The PAR Originator is the Payload Developer, POIC cadre member, or other user directly responsible for the area in which a payload anomaly has occurred or that is affected by the ISS systems anomaly.

2. As soon as the PD, PSE, OC/SpOC, (or other designated party) identifies the anomalous condition and OC/SpOC, (or other designated party) verifies the signature has not been previously documented in a PAR and meets the PAR Criteria, the OC/SpOC shall assign a PAR number and originator to document the anomaly.

NOTE: PAR numbering is designed to ensure the documenting of anomaly signatures on the individual piece of POIC Operated Hardware, Facility, or subrack payload. Systemic anomalies must be documented on each piece of hardware the anomaly has manifested itself on.

3. The PAR Originator is responsible for providing the Anomaly Description and Anomaly Resolution for facility/payload-related PARs. A designated POIC cadre position or operations support group is responsible for providing the Anomaly Resolution for POIC operated hardware PARs; i.e., PRO for PLMDM issues.

4. PAR status is ASSIGNED, OPEN, OPEN - PENDING, OPEN - SUSPENDED, CLOSED, or WITHDRAWN. Explanations are as follows:

a. ASSIGNED – The anomaly signature has been identified. A PAR number has been generated. The designated party has been notified to complete and return the PAR with a projected closure date.

February 2, 2018 1.1-4 POIF-1005 Revision O

b. OPEN – The completed PAR has been returned to the POIC for review and is being worked to closure. The POIC must approve continued on-orbit operations for those OPEN PARs that represent a significant anomaly affecting payload operations (i.e., component failure, off-nominal hardware or software functionality). Additionally, if hardware or software is replaced on-orbit to correct an anomaly, Payload Engineering Integration (PEI) must evaluate verification/certification issues before operations can resume.

An OPEN PAR may be moved into one of the following categories:

i) OPEN - PENDING: The anomaly has been analyzed and corrective actions have been defined as an IFM or as a new software requirement to be implemented in the future. No remaining engineering analysis work is required. The resolution is dependent on a successful on-orbit activity (hardware change out, software upgrade, etc.) to correct the anomaly.

When the corrective action has been performed and operations are nominal, the PSE coordinates with the POD to transition the PAR to CLOSED status. If operations are still off-nominal, the PSE will coordinate the PAR transition to the appropriate status. NOTE: PSRT support may have been requested to assist in PAR resolution.

ii) OPEN – SUSPENDED: The PAR Originator and POIC both agree that no further action will be taken by the Real Time team to attempt recovery, diagnosis, or repair. The PSE will provide contact information and any associated problem reporting/tracking information for any off-line problem resolution. No further operation of the affected hardware will be allowed until off-line organizations (such as PEI, or Payload Software Integration, etc) provide closure rationale or corrective action in the PAR.

The PSE will then transition the PAR to the appropriate status. The OC or SpOC and POD will remain cognizant of all OPEN-SUSPENDED PARs to prevent inadvertent scheduled operations.

c. CLOSED – The anomaly has been resolved and the PAR has been signed by the PSRT Chair. A PAR is closed after meeting one of the following conditions:

i) Corrective Action: “Corrective action” has been verified by ground or on-orbit testing; or if testing is not feasible by thorough analysis and implemented. The entire corrective action development through implementation process must be documented in the PAR and updates to operations documentation published.

ii) Use-As-Is: The PAR Originator and POIC agree to a “Use As-Is”.

The PAR must identify any operational work-arounds and/or updates to operations documentation affected by “Use As-Is” anomaly.

iii) Single Event Upset (SEU): Engineering is unable to duplicate the problem in testing or determine the cause of the event, the event has not re-occurred on-orbit and thorough analysis indicates the anomaly was a “single event upset”.

February 2, 2018 1.1-5 POIF-1005 Revision O

iv) Explained Condition: The anomaly is an “explained” condition; that is, an anomaly which after investigation proves to be a normal condition not requiring remedial action.

d. WITHDRAWN – Upon further consideration, the PAR was deemed unnecessary. Rationale for this can include: anomaly is addressed by another PAR, or anomaly is traceable to a system outside the Originator’s or POIC’s control. A PAR may only be WITHDRAWN before initial review is conducted.

5. Recurrences of an OPEN anomaly will be documented per instructions in the PAR form. Once an anomaly is identified and a resolution provided, it is no longer considered an anomaly, but is considered “known”.

6. Any disagreement about PAR status, priority, or closure may be elevated to the PSRT Chair or POM.

PROCEDURE

1. When an anomaly has been identified the OC or SpOC for SpOC payloads initiates opening a new PAR. The OC or SpOC enters the Payload, PAR Type, Title, Originator, and Initial Signature. OC or SpOC may enter Anomaly Description for additional clarification. At this point the PAR status is ASSIGNED.

NOTE: SpOC initiates a new PAR for SpOC payloads while the SpOC console is staffed. If the SpOC console is not staffed, OC will open the PAR.

OIP NOTE: For Integrated Anomalies or per HOUSTON FLIGHT direction, the POD submits an Anomaly Log entry in the MIS Anomaly Log tool.

2. PAR Originator enters all aspects of the Anomaly Description have been captured and all available fields completed

NOTE: Step 2 should be completed within 24 hours from when anomalous condition occurred.

3. PART issues an email to PSE indicating the PAR needs to have reviewers assigned.

PSE reviews the PAR for completeness and accuracy. If additional information required PSE will return PAR to Originator for additional information.

4. PSE assigns reviewers to review PAR for impacts.

a) POIC Safety provides Safety Impact Assessment.

b) Payload/EXPRESS Integration Engineering provides ISS Interface Impact

Assessment.

February 2, 2018 1.1-6 POIF-1005 Revision O

c) PSE provides Station-wide Payload Resource and Cross Flight/Increment Interface Assessment.

d) EXPRESS Rack, EXPRESS Logistic Carrier, MELFI, and WORF OPS LEADS will review all designated PARs accordingly.

NOTE: If the PAR involves hardware that is common with ISS systems, that adversely affects the interface with and operations of ISS system hardware, or that adversely affects crew health or safety, the ISS MER Manager must be notified. PSE will initiate MER interface with the POM or POM Representative approval.

5. PART issues emails to selected reviewers to complete interface impact assessments.

6. PART issues emails to PSE when selected reviewers complete their interface impact assessments.

7. PSE reviews completed Impact Assessments. PSE updates PAR Executive Summary as needed, and returns PAR to Originator or designated support entity indicating the PAR has been returned for further analysis.

8. PSE will return updated PARs to previously assigned reviewers for additional Impact Assessments. PSE reports to POIC Cadre any PAR findings that affect real time ops or ops products.

NOTE: The PSRT may be requested by real-time cadre or Users to assist in bringing a PAR to closure at any time. PSRT will routinely review delinquent or stagnant PARs and prioritize PAR work.

9. When the anomaly is resolved, the PAR Originator enters the anomaly resolution information and returns PAR to the PSE.

10. PSE reviews the PAR anomaly resolution information for completeness and accuracy.

If additional information required PSE will return PAR to Originator for additional information.

11. PSE will return updated PAR to previously assigned reviewers for final Impact Assessment.

12. PART issues email to the Originator indicating the PAR requires final resolution according to its state.

a) If the PAR is OPEN, the Originator documents the progress of corrective action or workaround implementation in Anomaly Resolution. When all actions are completed and approved, the Originator updates Proposed Closure Date and selects “Problem Fixed”.

b) If the PAR is OPEN-PENDING, the Originator documents the progress of the on-orbit corrective or other pending actions in Anomaly Resolution. When all

February 2, 2018 1.1-7 POIF-1005 Revision O actions are completed and approved, the Originator updates Proposed Closure Date and selects “On-Orbit Corrective Complete”.

c) If the PAR is OPEN-SUSPENDED, the Originator documents any further analysis, resolution, and closure rationale (including any transfer to another problem tracking system) in Anomaly Resolution. When closure rationale is complete, Originator updates Proposed Closure Date and selects “Report Analysis/Resolution. PAL issues email to PSE indicating the PAR is ready for PSRT final review. PSRT evaluates the PAR and its final resolution as a whole.

d) If the resolution description is incomplete then PSRT selects “Return For More Info”, provides an explanation, and PAL returns the PAR to the Originator per step 12.

e) If the PAR is complete, PSRT enters a Closure Recommendation and Date, updates Proposed Closure Date, and selects “Recommend Closure”.

13. After PSRT conducts a final review of the PAR the POD enters his/her name and GMT and selects “Approve for Closure”.

14. PART issues email to PSE, OC, SpOC, and the Originator indicating the PAR has been signed by the POD and is closed. At this point the PAR status is CLOSED.

OIP NOTE: For Integrated Anomalies, the POD submits information from the CLOSED PAR to close the Anomaly Log entry in the MIS Anomaly Log tool.

15. PSE maintains PART as the status of all PARs.

SOP 1.2 PAR GENERATION

February 2, 2018 1.2-1 POIF-1005 Revision O

PURPOSE

To provide the definition of fields in the PAR form.

PARTICIPATION

POIC Cadre Users OC SpOC

RICO PSE *POD

EFFECTIVITY

Non-Flight Specific

REFERENCE DOCUMENTATION

None

GENERAL

The following procedure defines the fields on the PAR form that must be filled out by the originator, OC or SpOC, PSE, and POD. Please refer to Figure 1.2-1, PAR Form, while viewing this procedure.

PROCEDURE

1. OC or SpOC identifies the payload or experiment experiencing the anomaly or receiving the affect of an ISS system anomaly.

February 2, 2018 1.2-2 POIF-1005

FIGURE 1.2-1 PAYLOAD ANOMALY REPORT FORM

February 2, 2018 1.2-3 POIF-1005 Revision O

2. OC or SpOC assigns the PAR numbers according to the following naming convention:

(a) First six characters designate the payload or support equipment abbreviation, like CGBA or ExpRk2.

(b) The PAR type designates the nature of the problem Types used are:

ELE Electrical FLD Fluids GSE Ground Support Equipment HW Hardware MECH Mechanical SW Software SYS ISS Systems

(c) The PAR number is a four-digit sequential number, like 0001 or 0034.

Examples of…