Crew Operations Team Alexia R. Matthews Cold Stowage CPE (256)

2 Crew Operations Team Crew Ops Team Contact –NASA Point of Contact:Brian Blair(256) –Team Lead:Bruce Coole(256) Roles and Responsibilities –Assist the payload developer with Operational Nomenclature (OpNom) process and baseline –Ensures the crew has usable payload displays and accurate payload manual procedures to conduct science operations –Author manual crew procedures for the payload developer –Develop flight products: PODF onboard Manual Procedure Viewer (MPV) library and the integration of new International Procedure Viewer (iPV). –Ensure payload stowage requirements are integrated with ISS program and coordinate stowage/inventory activities during real-time operations. –Crew Ops Team consists of 3 functional sub-teams: Procedures Team –Crew Procedure Engineers (CPEs) –PODF Support (HOSC Real-Time Operations) Displays Team POIC Stowage Team –Both Ops Prep and Real-Time Ops

3 Level 1 - POI Overview PD inputProcessPayload Integration product/outputISS/SSP program product Legend: I-20 I-9I-19I-14I-12I-18 Payload Planning Payload Training Payload Developer Functions Crew Training Req’ts Trained Crew Trained GSP Configured Ground Systems OOS & Flight Plan Displays & OpNoms Crew Procedures Basic Planning Req’ts Phase II Safety Inputs GSP Training Req’ts Safing/Ground Procedures Basic Ops Constraints Phase III Safety Inputs Ground Systems Final Products Basic Payload Planning Process Console Products TLM and CMD DB Development Update Facilities Configure POIC Training Plans & TrainersCrew Training Courses & Scripts GSP Training & Simulations I-6 Planning Req’ts Final Ops Constraints Final Payload Planning Process Tran- sition Payload Display & Procedures & Displays OpNom OpNom Coordination Display Development ISS Crew Procedures Development Payload Operations Payload Safety Console Products Flight Safety Review Process Ground Safety Review Process Ops Hazard Control Verif Hazardous Cmd Verif Hazmat Validation PSM/Ground Command Procedure Development Flight Rules & PL Regulations Development Integrated Safing Procedures Dev. PHCM PEP/PL MDM Config File Development Bench Review & Waste Process Stowage Req’ts Ground System Req’ts (I-13) GDS Req’ts Display Usability Process Bench Review

4 PRODUCTS: –OpNom Payload NamePreliminary Design Review (PDR) Acronyms & Abbreviations Facility I-20 months, Subrack I-18 Parts & MaterialsFacility I-17 months, Subrack I-15 –Crew Procedures Preliminary Facility I-16 months, Subrack I-14 Baseline Facility I-5.5 months, Subrack I-5.5 –Payload Displays Operations ConceptsAll = I months Operations Analysis/FlowsAll = I-22 months Preliminary Facility I-20 months, Subrack I-18 BaselineFacility I-17 months, Subrack I-15 Crew Operations Team * Latest versions of above products are delivered to support training, Usability, PTDR, etc.

5 iPV - MSFC Integration Contact –John F. Wade(256) International Procedure Viewer (iPV) Status: –MPV replacement –PODF iPV Operations Concept approved by PODFCB on 9 OCT 03 –Procedure Authoring Tool (PAT) Training Members of the Crew Operations Team have completed at MSFC –iPV Transition Schedule Procedure conversion/coordination is in work to support ULF1.1 Crew Operations Team members will be consulting each PD on priorities Training of crew with iPV will begin March 2004 Onboard transition to iPV – Fall 2004 –The PODF iPV Ops Concept and other useful iPV information can be found at ( Crew Operations Team

6 Procedures Team Alexia R. Matthews Cold Stowage CPE (256)

7 Procedures Team Contact –Gary Moore(256) Roles and Responsibilities –During Ops Preparation Phase Coordinate and approve Operations Nomenclature (OpNom) to maintain consistency among hardware labels and drawings, manifest listings, and crew procedures. Develop procedures for us e in crew training/simulation to ensure that PD and cadre training reflects the most current procedures available. Ensure that accurate payload procedures are available to the on-orbit crew –If requested by the PD, the Procedures Team will also work with the PD to develop/write a full set of payload procedures and OpNom, as well as perform all administrative functions to baseline these PODF products. –Review Payload Developer (PD) provided procedures for accuracy, Operations Nomenclature, ODF approved standards and formats –Procedure Team support is provided throughout the lifetime of the payload. –During Real-Time Operations – PODF Support (HOSC) Provide real-time support to ensure that new or updated procedures are in compliance with ODF standards and format. Provide 12x5 (24x7 On-Call) support Call sign: PODF SUPPORT Loop: PODF SPT s/telephone numbers: / ( 256) Procedures Team

8 Procedures will be developed using the Procedure Authoring Tool (PAT), stored in Payload Information Management System (PIMS), and reviewed via the International Procedure Viewer (iPV) Procedures will be developed per ODF Standards (SSP 50253) US PODF Management Plan (SSP 58700) contains the US PODF processes and delivery template schedules Procedure Deliveries –Preliminary – First cut at how the crew will operate the payload on ISS. The preliminary procedures are used to baseline displays, usability verifications, PTDR and crew training. The Training Team will use them in training lesson plan development and pre-ship testing of hardware. The preliminary delivery includes: Activation and Checkout, Nominal, Malfunction, Corrective, Reference, and Alternate Nominal procedures; Log files; files to be presented as Cue Cards; Files List, Links File, Validation Plan, and Validation Record supporting data. –Baseline - The procedure version released with the ECR that are placed under configuration control. This delivery incorporated the comments collected from reviews and U.S. PODF Control Board (CB) approved changes. They will also include any procedure hazard control list actions. Manual Procedures

9 Displays Team Michael R. Maroon (256)

10 Displays Team Contact –Joe Fittipaldi(256) Roles and Responsibilities –During Ops Preparation Phase Plan and provide human engineering design support, test, and verification of ISS payload software- crew interfaces. –Serve as displays Point-of-Contact starting at PDR and throughout the development phase. –Schedule and conduct end-to-end displays and procedures usability verification. –Assemble mandatory reviewers for usability verification which includes representatives from Displays / Procedures / Training / Crew Office. Review Payload Developer (PD) displays for standards compliance, usability, operations nomenclature and 1-to-1 interoperability with the crew procedures. –Assist PDs with Operations Concept; definition of the crew role; and identification of crew tasks. –Provide design guidance per Display & Graphics Commonality Standards (SSP 50313). –Plan, schedule and conduct the usability verification (Test or Trial). –Verify the Payload Developer complies with the guidelines as defined in the PODF Management Plan. –Provide final display products to Payload Integration Management System (PIMS) for Cadre reference/use. –Evaluate payload overall readiness for PTDR, Crew Training and Flight. Develop, maintain and administer Payload Display Development Training Class, as requested by the PD community. Represent the U.S. Payload Developer community to the Integrated Display and Graphics Standards (IDAGS) Panel. –During On-Orbit Operations Evaluate re-flight payload displays/crew procedures for impacts to usability; re-baseline displays as required. Displays Team

11 Usability Verification –Usability Readiness Review; conducted approx. 3 weeks prior to test –Conducted by the Displays Team at MSFC –Must be completed before PTDR and Crew training –Performed on payload displays and/or manual crew procedures as either integrated or individual evaluations –Method is a usability test or trial, depending on the complexity of interfaces –Goal Evaluate the interoperability of the payload display software and hardware crew interfaces, and crew procedures Gauge the effectiveness, efficiency and customer satisfaction of each product Human Factors Implementation Team (HFIT) Evaluation –Conducted by HFIT group at JSC –Performed on payload hardware, at the PD site –Goal Focus exclusively on the compliance of payload hardware crew interfaces with the human factors design requirements of SSP and SSP –Compliance documented via Form 881 Human Factors Requirements Checklist –Deviations from 57000, Section 3.12 tracked by HFIT using PIRN Form 882 Usability Verification vs. HFIT Evaluation

12 Stowage Team Scott Stinson Stowage Team Lead (256)

13 Stowage Team Contact –Scott Stinson(256) Roles and Responsibilities –During Ops Preparation Phase Coordinate payload stowage integration activities with PDs, OZ2, and EI Assess data in IDRD/Annex 1 and IMS to determine impacts to increment planning Review ECRs, CEFs, MRs, and CRs for stowage impacts Attend/participate in Bench Reviews: –Validate approved payload operations nomenclature (Op Nom) –Review packed configuration of hardware –Coordinate with OZ2 on payload Op Nom and label issues that impact procedures –Coordinate bench review actions with PODF and PDs –During Real-Time Operations Coordinate/integrate day-to-day NASA payload stowage/inventory activities. Provide 8x5 (24x7 On-Call) support to RT Ops for payload stowage issues. Provide daily stowage location information to MCC-H ISO to assist the crew in unstowing and restowing payload items. Assess need for inventory audit requests and coordinate with MCC-H ISO for implementation. POIC Stowage Team

14 POIC Stowage Team –During Real-Time Operations (cont) Call sign: POIC STOWAGE Loop: POIC STOW s/telephone numbers: / (256) / (256) –Stowage Links Mission Integration Database Application System (MIDAS) IMS Data on ISS: contains ops products and IMS search (Password/access required via JEDI web site) Barcode Inventory Tracking System (BITS) everything you wanted to know about bar codes –IMS labels are provided as GFE by the JSC Decal Design and Production Facility to ISS participants Laboratory Support Equipment (LSE) / Station Support Equipment (SSE):

15 “Search IMS” screen shot (Contact POIC Stowage for access)

16 Backup Charts

17 Level 2 - ISS Payload OpNom

18 Level 2 - ISS Payload Crew Procedures Payload Developer Crew Training Review of ECR/CM Process Preliminary PODF And updates SSP50254 (OpNom) and Annexes Put Procedures into format & standards SSP 50253, ODF Standards Prelim Manual Procedures incl.Files List, Val. Plan, Val. Records, MPV Links, P/L Messages, Log Files ECR to B/L Manual Procedures incl. Hazard Control List Payload Operations Integration DO3/ODFCB Preliminary Payload Unique OpNom for Product Dev Engineering Drawings Manual Procedure Updates, as Needed B/L PODF Flight Displays Flight Products Procedure or Combined Procedure/Display Usability Test; Test Report * * * * * PODF-CPE performs items for the PD Build Flight Products

19 Manual Procedure Categories –Activation and Checkout - Nominal procedures used to activate, power up and check-out payload systems or subsystem components. –Nominal - Procedures used to carry out day-to-day operations of the payloads, systems, or individual subsystem components. Deactivation procedures are a part of the nominal procedures, as are preventative and periodic maintenance procedures, and procedures for transfer of cargo between an ETOV and ISS. –Malfunction - Procedures that typically use the logic flow format to provide a decision network for troubleshooting problems that arise during the execution of a procedure. They are not considered time critical but are performed as soon as possible. May lead to a corrective procedure. –Corrective - Procedures designed to bypass or overcome a failure condition, not considered time critical but performed as soon as possible. –Reference - On-board non-executable support data that assists the crew. Examples: Lists of equipment lost when a bus malfunctions; earth observation maps; diagrams and drawings used for system familiarization and diagnostic troubleshooting; Any other information needed for the crew to perform payload operations. –Alternate Nominal - Procedures which, due to some anomaly or reconfiguration, will accomplish the science objectives without requiring additional resources. –Cue Card - Media used to present one of the procedure types. –Quick Response (Safing) - Procedures used to quickly safe the system or payload in the event of a failure or anomaly in the nominal operation. Must be accomplished within a limited amount of time (approximately 5 minutes). –Payload Message - All messages output by a payload that requires a crew response or that provide meaningful situational awareness. Procedures Team

20 Supporting File Categories –Files List - A list of all files delivered, including procedures, displays, reference data and support products. This is a table of contents of delivered product. –Links File - Identifies links between procedures to include reference data and log files. This is used to verify functionality of the links when MPV libraries are reviewed. –Validation Plan - Defines the process used by the PD to check procedures for technical accuracy and ability to meet science objectives. –Validation Record - A record of a procedure validation, the process for validation, the participants, and any related files that were used during the validation session. –Pre-Release Engineering Drawings - Pre-release versions of hardware label, and top-level assembly drawings. Used by Crew Operations Team for display and procedure development/review, by IPLAT for preliminary label review. –Released Engineering Drawings - Release versions of the flight hardware label, and top-level assembly drawings. Used by Crew Operations Team for display and procedure development/review, by IPLAT for final label review. –Procedure Hazard Control List - Identifies all procedurally controlled hazards and information for POIC safety verification. –Operations Nomenclature - A list of payload unique nomenclature used on hardware, displays, panels. Procedures Team

21 Level 2 - ISS Payload Displays Payload Developer US PODFCB Approved OpNom SSP50313 (DGCS) Assist PD with Ops and Display Development; Recommend Improvements Review Displays SSP50254 (OpNom) and Annexes Payload Operations Integration External ECR Review & CM Process Display Baselining ECR Payload Engineering Integration IPLAT Initial Label Evaluation IPLAT Scans Displays for Consistency with H/W Labels Ops Analysis Initial Crew Displays Pre-released Engineering Drawings Ops Concept Revised Crew Displays Preliminary OpNom for Product Dev Display Usability Test Option* CoFR US PODFCB Approved Displays Usability Test Report * See the Payload Usability Evaluation Process - PODF Mgmt Plan - POIF CM Plan Iterative Candidate PIMS

22 Displays Development Process

23 Pre-released Engineering Drawings - Pre-released versions of hardware label, and top- level assembly drawings. Operations Concept (Optional deliverable) - Is the first and most important phase of payload operations development. The Operations Concept expresses the purpose of the payload, the objectives required to fulfill that purpose, and the role of the on-orbit crew in meeting the objectives. While the Operations Concept is not a required delivery it is a key ingredient to the successful development of displays and procedures as well as other operations products. Operations Analysis (Optional deliverable) - Derives the payload functions required to fulfill the goals and objectives specified in the Operations Concept. In the Operations Analysis payload functions are allocated between hardware, software and crew based on the inherent strengths of each of those elements. The Operations Analysis also identifies the crew’s decisions and actions required for effective and efficient payload task completion. Displays Team - Definitions

24 Preliminary Displays - Are draft representations of what will evolve into the candidate flight displays. The preliminary displays undergo an iterative usability review process. The preliminary displays can be static screen shots (mockups) linked together in a PowerPoint- type format in order to simulate an operational sequence. On receipt, the initial displays will be entered into the PIMS PODF:Offline MOP. Candidate Flight Displays - Are final end-to-end set of screen shots depicting the crew displays that have undergone usability review, usability verification and PODFCB approval. The candidate flight displays are delivered by the PD to the Display Team at the conclusion of the usability test phase of the display review process. These displays will reflect a crew- display interface that is fully mature, ready for board approval, crew training and flight. After baselining, flight displays are entered into PIMS flight MOP for use by POIC cadre, et al. When feasible, Crew Ops Team will also request from the PD a fully functioning (dynamic) displays set; typically an executable file. Released Engineering Drawings - Release versions of the flight hardware label, and top- level assembly drawings. Displays Team - Definitions