1. June 16, 20051 PMDIS TIM Shuttle Operations Coordinators (SOC) Roles & Responsibilities Beth Griggs Shuttle Operations Coordinator 256-961-1926 Beth.V.Griggs@msfc.nasa.gov

2. June 16, 20052 Agenda SOC Description SOC Pre-Increment Functions SOC Real Time Functions

3. June 16, 20053 Shuttle Operations Coordinator (SOC) SOC is the Payload Operations Integration Center (POIC) member responsible for all Payloads while located inside the Shuttle Shuttle Middeck Multi-Purpose Logistics Module, Spacehab NOT Shuttle Cargo Bay SOC monitors payloads in Shuttle and coordinates within the POIC, with Payload Developers (PD), and with Partner Control Centers (PCC) SOC coordinates with the Assembly and Checkout Officer (ACO) Team at the Mission Control Center (MCC) about payload operations, planning, crew procedures, and transfers

4. June 16, 20054 Current SOC Staffing

5. June 16, 20055 Shuttle Operations Coordinators (SOC) Pre Mission Functions

6. June 16, 20056 Sortie Overview  The ISS Payloads Office (OZ) has been tasked with coordinating all payloads that fly inside the Shuttle, not just the ones destined for the ISS. This change moves responsibility for ‘sortie’ payloads from the Shuttle Program office to OZ office.  POIF has been tasked with providing operational support of all sortie payloads resident in the Shuttle  Includes ISS (transfer) payloads and sorties  Pre-mission operations product development, CoFR, and real-time support for all payloads  Excludes DSOs (Med Ops) and DTOs (systems)

7. June 16, 20057 SOC Functions - Procedures Procedures –SOC will spearhead the POIF coordination of gathering Payload Developer requirements and Spacehab inputs for sortie payloads and transfer operations procedures PD provides SOC with all procedural experiment ops info; noms, mals, alts. SOC combines the above with any ISS ops into an integrated procedure SOC provides PMDIS sortie procedures to ACO –SOC is responsible for development, review, and updating of payload procedures used during Shuttle ascent/descent, sortie and transfer activities. Spacehab will be involved with review of procedures; IPLFOR, FOR, CR, OCR, EFN.

8. June 16, 20058 SOC Functions - OPNOM OPNOM –Sortie Payloads will have to follow the OPNOM process. SOC will spearhead the POIF coordination of gathering Payload Developer OPNOM requirements. –Current PMDIS OPNOM:

9. June 16, 20059 SOC Functions - OPNOM (cont) OPNOM –Current PMDIS OPNOM (cont):

10. June 16, 200510 SOC Functions - OPNOM (cont) OPNOM –Current PMDIS OPNOM (cont):

11. June 16, 200511 SOC Functions - Training Crew Training –SOC will collect training requirements from PD and put into PDL. CTC will work requirements with Shuttle Training Manager –SOC will certify PL trainer and PL training material –SOC will oversee all transfer and sortie training with coordination from Spacehab counterpart concerning any direct interface with module (i.e. bolting/unbolting)

12. June 16, 200512 Flight Operations Review (FOR) SOC is responsible for overall POIC coordination of the Flight Operations Review –Coordinate review FOR Data Package SODF and FDF (Payload Procedures) Joint Operations and Integration Procedures Flight Rules Flight Plan Middeck Layout and Plug-In Plan (if available) Road To Flight XXX –Collect and submit Discrepancy Notices (DN) from POIC, Payload Developers, and Partners –Attend FOR to represent POIC, Payload Developers, and Partners

13. June 16, 200513 Post-FOR Changes to Procedures SOC coordinates procedure updates required after FOR –PD request –Updates resulting from crew training –Updates resulting from Shuttle or manifest changes Updates are made via Change Requests (CR) until CR cutoff of ~L-6 weeks Updates are made via Operational Change Requests (OCR) from ~L-4 weeks through implementation of flight

14. June 16, 200514 12A.1 Schedule Procedure inputs have been received and are in work. Still waiting on PMDIS MAL procedure updates April 29th: Training Requirements were input –Requirements include Payload Name, Lesson Titles, Hours Required, Lesson Objectives, Ready for Training Date July 18th: Familiarization Briefing due to SOC for review June, July, August timeframe: Payload Training Readiness Review. SOC will certify the hands-on lesson plan and the PD is ready for crew training. (via telecon) L-6 to L-4 (Sept/Oct - Dec): FAM Briefing and Crew Training Sessions.

15. June 16, 200515 PMDIS Crew Training Requirements

16. June 16, 200516 Shuttle Operations Coordinators (SOC) Real Time Functions

17. June 16, 200517 SOC Console Staffing SOC Console in POIC –Staffed as required from ~L-1 month to L-1 day –Staffed 24x7 from L-1 day to Landing –Email account: soc@mps.hosc.msfc.nasa.gov –Phone number: 256-544-6072

18. June 16, 200518 SOC Real Time Interfaces SOC serves as the interface between the POIC and the Shuttle Mission Control Center (MCC) –Supports the Assembly & Checkout Officer (ACO) –Provides the POIC and PDs a window into the Shuttle MCC –Communications loops PRIME OPS loop for POD, SOC, Spacehab to ACO ETOV COORD loop for SOC to ACO support personnel SOC serves as the interface between the PD, the POIC, and the MCC on all Shuttle payload issues –SOC loop for discussions between SOC and PD –TBD loop for discussions between SOC and Spacehab –POD loop for discussions involving the POD, or other POIC cadre

19. June 16, 200519 SOC Real Time Interfaces Payload Coordination Payload & Shuttle Status Mission Planning FAO Payload Priorities Payload Stowage SOC Payload Ops Lead Partner Control Center Payload Operations and Integration Center Payload Coordination Mission Control Center - Houston NASA Payload Developer Payload Coordination Operations Coordination OC Team POIC Stowage POD Payload Coordination ISS FD Payload Operations Coordination LIS Rep TCO ACO Support ACO Flight Plan Coordination Payload Coordination Payload Integration & Planning Group Manifest Coordination STS FD Spacehab Payload Coordination

20. June 16, 200520 Monitor Payloads in Shuttle SOC responsible for all Payloads while in Shuttle –Ascent, joint ops (docked), and descent –Operations in the Shuttle Middeck –Sortie Payloads in Spacehab SOC monitors selected Shuttle environmental parameters (e.g., cabin pressure and temperature) that may impact payloads The SOC responds to payload questions from the Shuttle Crew - via the ACO Team through CAPCOM

21. June 16, 200521 Communications During Joint Operations POIC SOCOCPODOther Cadre NASA Payload Developer Voice Loops ISS Flight CAPCOMACOSTS Flight Shuttle and ISS Crew MCC-H Payload Operations Lead PCC SPACEHAB

22. June 16, 200522 Coordinate Products for Payloads SOC supports the ACO Team in coordinating and updating payload-related products –Flight Plan –Crew procedures –Troubleshooting malfunctions –Priorities during Shuttle situations that impact payloads –Failure impact and workarounds (coordinating Payload Anomaly Reports with OC Team)

23. June 16, 200523 More Information

24. June 16, 200524 Shuttle Procedures Development Process Process OCR for Flight Process CR L-12I - 8.5 L-1.5 FOR I - 7.5 IPLFOR Launch PD delivers procedures inputs Works with PD to develop payload procedures L - 6 L - 4 Baselined procedures to support Crew Training and Flight Procedures submitted for IPLFOR FOR IPLFOR Prepares procedures for FOR Procedures submitted for FOR SOC Activities Increment-Based Activities Flight-Based Activities PD submits procedures changes

25. June 16, 200525 Shuttle Procedures Locations Systems Operations Data File (SODF) - Assembly Operations Procedures (AOP) book –Middeck Status Check Cue Card (ascent/descent) –Middeck and Spacehab Nominal, Transfer, Alternate, and Malfunction Operations Flight Data File (FDF) –Sortie Payload Nominal, Alternate, and Malfunction Operations –Payload Power Down (priority power down) –Payload Safing (rapid power down) –Ascent and De-orbit Checklists (switch configuration)

26. June 16, 200526 Planning and Manifest Coordination SOC coordinates with the Lead PPM for the Earth- To-Orbit Vehicle (ETOV) Payload Activity Summary (EPAS) development and review –EPAS developed by Lead Planner based on iURC data –SOC provides information on sorties and transfer operations/ constraints for inclusion into EPAS SOC coordinates with Payload Integration and Planning Team (OZ2) for payload manifest and payload stowage integration

27. June 16, 200527 Pre-Pack and Transfer Coordination SOC coordinates with Cargo Integration Officer (CIO)Team for the payload portion of the Pre-Pack List (PPL) –PPL development begins ~L-6 weeks –PPL updates ~L-4 weeks to docking –POIC provides “GO for pre-pack” for payload items SOC coordinates with Assembly and Checkout Officer Team for the payload portion of the Transfer List (TL) –TL development begins ~L-12 weeks –SOC coordinates payload operational constraints in TL –SOC monitors TL updates (updates due to manifest changes worked by OZ)

28. June 16, 200528 Coordinate and Monitor Payload Transfers Payload Transfer Activities –Unpowered payload transfers are coordinated by the ACO with SOC support as required Generally not on Flight Plan, crew transfers when appropriate Crew reports transfer progress at end of each day –Powered payload transfers are coordinated jointly by the ACO, SOC, and OC Timelined due to coordination required Crew reports transfer progress in real time