1. I29/30 Robonaut Training Strategy Team (TST) Mike Joseph Robonaut Training Coordinator 281-218-3205 michael.h.joseph@lmco.com 1 Notice: Material contained within this presentation is considered export controlled.

2. Robonaut Points of Contact Beth Griggs- MSFC Ops Lead Mike Joseph –Training Jim Searcy –Training/Simulation Lisa Creech- OZ Payload Integration Manager Meganne Valerioti –Robonaut Operations Noe de La Pena- Robonaut Operations(Prime Trainer) 2

3. Agenda Introduction Increment Assumptions Operations Overview Current Training Efficiencies Planned Crew Training Tasks Proposed Training Session Description & Scheduling Development Schedule Future Increment Operations and Milestones Notes, Issues, & Concerns 3

4. Increments 29 & 30 Flight Sequence (4/26/11) Inc 29/30 ( D. Burbank - USOS) Inc 29/30 ( A. Shkaplerov– RS) Inc 28/29 M. Fossum– USOS) Inc 28/29 (S. Volkov- RS) Inc 29 Exp 28/29/30 crews Inc 30 Expedition 29/30/31 crews Inc 30/31 ( O. Kononenko RS) Inc 30/31 ( D. Pettit- USOS Inc 30/31 ( A. Kuipers– USOS) Inc 29 Inc 30 Inc 28/29 ( S. Furukawa– USOS) Inc 29/30 ( A. Ivanishin– RS) 2011 28S Sep 30 29S Nov 30 28S Return Mar 16 Jun 28 45P Oct 26 CRS SpaceX Demo 3 Oct 8 Burbank, Shkaplerov, Ivanishin Kononenko, Kuipers, Pettit 2012 HTV3 Jan 20 ULF 7 Teleop Gear CRS SpaceX CRS 1 Dec7 Orb Orbital Sciences OrbD1 Dec 14 46P Dec 27 ATV3 Feb 29 Orb Orbital Sciences Orb1 March 8 29S Return May16

5. Increment 29/30 Assumptions Launch Dates (per OZ working launch dates 4/25/11)  June 28, 2011 on Shuttle – ULF 7 (Teleop Gear)  Sep 30, 2011 on Soyuz - 28S – RSA Commander, RSA FE, US FE  Oct 8, 2011 CRS – SpaceX-Demo 3  Oct 26, 2011 Progress (45P) -- Resupply  Nov 30, 2011 on Soyuz – 29S RSA Commander, ESA FE, US FE  Dec 7, 2011 CRS – SpaceX- CRS1  Dec 14, 2011 Orb – Orbital Sciences Demo 1  Dec 27, 2011 Progress (46P) -- Resupply  Jan 20, 2012 HTV3 – Resupply  Feb 29, 2012 ATV3 – Resupply  Mar 8, 2012 Orb – Orbital Sciences 1 Prime Crewmembers  American- Dan Burbank(Exp 29 FE/30 CDR)  Russian- Anton Shkaplerov(Exp 29 FE)  Russian- Anatoly Ivanishin(Exp 29 FE)  Russian- Oleg Kononenko (Exp 30 FE/31 CDR)  American - Don Pettit(Exp 30 FE)  European- Andre Kuipers(Exp 30 FE) Dan Burbank Exp 30 NASA CDR Don Pettit 29S NASA FE Andre Kuipers 29S ESA FE 5

6. Robonaut Inc. 27 Ops Status Robonaut & Support HW launched on ULF5 On-Orbit Stowage Config completed Mar. 2011 (I-26) On-Orbit Soak estimated complete: Jun/Jul 2010 (I-27) Robonaut Checkout 1& 2 estimated complete: Aug. 2011(I-27) Initial Taskboard Ops estimated complete Sept. 2011 (I-27) 6

7. Planned Robonaut Operations for Inc. 29/30 7 Taskboard Operations (continued) TeleOps System Initial Ops

8. Increment 29/30 Assumptions All crew rotations via Soyuz. Launch dates are within 1 month of those listed on previous page. Crew swaps between backup and prime crewmembers should not necessitate a replan. Teleop Gear launches on ULF 7 Robonaut Checkouts complete in Increment 28, assuming crewtime available. Initial Taskboard Operations completed prior to March 2012 8

9. 9 Operations Overview

10. Phased Approach The ISS Program has tentatively agreed that Robonaut will be upgraded in phases over time The project has considered a reasonable, notional phased approach would be as follows: Phase 1 – Stationary IVA Ops (Initial ISS cert)  Stationary operation on a structural mounted platform (Current Phase) Phase 2 – Mobile IVA Operations  Upgrade Robonaut with a structural mounted appendage to anchor to handrails or other structural interface Phase 3 – EVA Operations  Upgrade Robonaut with the ability to go EVA and perform limited maintenance and worksite setup tasks

11. Phase 1 Operations Inc. 27/28 Unpack /deploy in US LAB On-Orbit Soak - Verify Pwr/Data/Video - Verify Health and Status Checkout 1  Verify Safety Controls  Perform finger & joint test Checkout 2  Verify Vision capability  Test Joint Range of Motion  Verify large arm and finger joints Initial Taskboard Ops  Taskboard Setup/Stow  Task Panel A (portions)

12. Phase 1 Operations Inc. 29/30 Initial Taskboard Ops (Continued)  Taskboard Setup/Stow  Task Panel A Free Space Operations (script execution) TeleOps System Setup/Configuration & Tasks Teleops serves as an alternative to pre-programmed scripts

13. TeleOps

14. TeleOps Gear (Continued) Goggles Gloves Vest

15. On Orbit Operations Notes Robonaut must always be connected to an SSC for operations Robonaut operates via: Scripts teleops Local control by crew is accomplished by using the GUI on the SSC or the teleops gear Ground operation will be accomplished via a Remote Desktop connection to the GUI on the SSC from the Admin PC in the MCC 15

16. Assumed Training Efficiencies We assume the crewmember can, within timeline constraints:  Unstow equipment with adequate procedures & stowage locations  Perform standard cabling of equipment  Stow equipment with adequate procedures & stowage locations 16

17. Planned Crew Training Tasks (Increment 29/30)  Robonaut Unstow/Stow & Assembly /Disassembly - Robonaut - Support Equipment (Baseplate and Stanchion) - Power /Data Cabling and cabin video camera. Note: Those tasks which, if done incorrectly, could damage hardware impair hardware functioning shall be emphasized.  Taskboard Assembly and Script Execution  Power-up sequence of Robonaut  TeleOps System Overview  Criteria for feedback on Robonaut specific diagnostic tests and system checks performed by Houston ground controllers 17

18. Proposed Training Session(s) Scheduling & Description 18

19. Training Schedule Considerations July 18 & 25 – P/L training week Sept. 12 – P/L training week 19

20. July Training - Session:#1 – Introduction to Robonaut Dates: Primary – July 18 Week Crewmembers:Dan Burbank Class Time:Approximately.5 hours Instructors:Primary – Ron Diftler Backup – Nic Radford Training Location:JSC/J32 Robonaut Lab Training Coordinators:Primary – Mike Joseph Backup – Jim Searcy Content:Robonaut Hardware & Functionality Overview Note: Both instructors have given this information many times before specifically to crewmembers at their request with positive results. We recommend the PTDR requirement be waived per POIF -1003, para 6.2, items A thru D. 20

21. July Training - Session:#2 – Robonaut Setup & Taskboard Ops Dates: Primary – July 18 Week Crewmembers:Dan Burbank Class Time:Approx. 1.5 hours Instructors:Primary – Paul Dinh Backup – Noe De La Pena Training Location:JSC/J32 Robonaut Lab Training Coordinators:Primary – Mike Joseph Backup – Jim Searcy Content:Robonaut Setup & Taskboard Configuration Operations Note: We recommend a PTDR be waived for this given that the content is a shortened version of the previous lessons given to the I27 & 28 crew. No content has been added. 21

22. July Training - Session:#3 – Robonaut Teleops Setup,Config, & Intro Dates: Primary – July 18 Week Crewmembers:Dan Burbank/Don Pettit Class Time:Approx. 1.00 hours Instructors:Primary – Noe De La Pena Backup – Paul Dinh Training Location:J32/ Robonaut Lab Training Coordinators:Primary – Mike Joseph Backup – Jim Searcy Content:Robonaut TeleOps Setup & Configuration for Functional Check 22

23. September Training - Session:#1 – Robonaut Teleops Tasks Dates: Primary – September 12 Week Crewmembers:Don Pettit Class Time:Approx. 2 hours Instructors:Primary – Noe De La Pena Backup – Paul Dinh Training Location:JSC/J32 Robonaut Lab Training Coordinators:Primary – Mike Joseph Backup – Jim Searcy Content:Robonaut Taskboard & Teleops Functional Check &Tasks 23 Note: Robonaut will be setup and ready for the Teleop task performance at the beginning of the class.

24. 24 Issues and Comments The need for TeleOps training was identified late due to lack of ground hardware/mature information to define an Ops/training concept. This Training Unit is to be delivered by the end of May. TeleOp on-orbit ops are targeted for Inc. 30. Depending on the outcome of the TST a CEF will need to be submitted to the program modifying the appropriate requirements Note: Robonaut will be setup and ready for theTeleop functional check & task performance at the beginning of the class.

25. 25 Draft procedures for Setup & Taskboard Ops – May 13 Presentation for Setup & Taskboard Ops Revised – May 20 Lesson Plan for Setup & Taskboard Ops Revised – May 25 Lesson Plan for Intro Class – May 27 Draft Crew Procedures for Teleop Checkout – June 15 Initial Presentation for Teleop Checkout – June 20 Internal Training Dry Run (ITDR) for Teleop Checkout – June 24 Payload Training Dry Run for Teleop Checkout (PTDR) – July 1 Second Instructor PTDR for Teleop Checkout – July 8 Training Development Schedule

26. 26 Draft Procedures for Teleop Tasks – July 31 Presentation & Lesson Plan for Teleop Tasks Class – August 12 ITDR for Teleop Tasks Class – August 19 PTDR for Teleop Tasks Class – August 31 2 nd Instructor PTDR for Teleops Tasks Class – September 7 Training Development Schedule

27. 27  Increment 31/32 Planned Operations: Additional Taskboard and Teleops Crew Training Scheduled for: November 2011 for Acaba & S. Williams Major Milestones: TST – July 2011 Draft Procedures f/Training Development – August 2011 ITDRs – Septmeber 2011 PTDRs – October 2011 Future Increments

28. 28  Increment 33/34 Planned Operations: Additional Taskboard and Teleops Crew Training Scheduled for: March 2012 for Hadfield & Marshburn April 2012 for Ford Major Milestones: TST – September 2011 Draft Procedures f/Training Development – October 2011 ITDRs – December 2011 PTDRs – January 2012 Future Increments

29. 29  Increment 35/36 Planned Operations: Additional Taskboard and Teleops Crew Training Scheduled for: November 2012 for Cassidy January 2013 for Nyberg Major Milestones: TST – November 2011 Draft Procedures f/Training Development – March 2012 ITDRs – June 2012 PTDRs – August 2012 Future Increments

30. 30  For I29/30 approximately half of the training development and certifications have been completed  Teleop equipment will be available for procedure & training development in mid-May  Milestones have been established to move us to a more nominal development schedule  Robonaut is more Basic Research (R&D) than Applied Research making working to the nominal development template difficult Summation