1. OCAMS Orbital Communications Adapter (OCA) Management System NASA/JSC/DO/Tim Hall Aug 2011

2. What is OCA and OCAMS? Problem Description Legacy Solution NASA Intercenter Collaboration OCAMS History OCAMS Approach OCAMS Solution OCAMS Implementation Other Application of OCAMS Q&A Agenda 2

3. What is OCA… Data is both downlinked and uplinked to the ISS (International Space Station) Two basic ways data is transferred between ISS and the ground…. –Telemetry –File transfers ISS has multiple local area networks (LANs) onboard: –For example: Crew Support LAN(CSL), Operations LAN (Ops LAN) –All ISS LANs use laptops as the primary interface for the crew The Orbiter Communications Adapter (OCA) card provides two way space-to-ground communication between networks via the TDRSS Ku-band link –OCA can virtually connect space and ground LANs. OCA translates between COTS-based computers/networks and proprietary NASA communications systems on Shuttle and ISS OCA cards are installed into Microsoft Windows-based Laptops –OCA utilizes SWRDFSH (Software to Ready Data Files to Send Hastily) to transmit files on space-to-ground 3

4. How many laptops are onboard ISS today? 1.17 2.141 3.76 4.35

5. ISS Laptops Answers…. Total number of laptops onboard = 141 Total active/in use laptops = 80 Laptops in use on Ops LAN ~ 22 What is the most common failure for ISS laptops? - Screen failure 5

6. OCA’s Officers Role OCA Officer is a console position in the ISS Mission Control Center (MCC) at JSC –It is the primary interface for the exchange of files and data between ISS Ops and CSL LANs and the ground Ops LAN and CSL data transferred via OCA includes: Uplink: Crew email Crew Personal Daily Ops Updates: Schedule Updates (OSTPV) Ops Messages Procedure Updates Inventory Payload data Commands Config files Downlink: ISS imagery Crew Email Crew Personal Daily Ops Updates : Schedule Updates (OSTPV) Ops Messages Procedure Updates Inventory Payload Data 6

7. What is the Uplink/Downlink rate that we have available for OCA file transfers? 1.1.5MB up /8.5MB down 2.9.5MB up /99.5MB down 3.1.5GB up/150MB down 7

8. The Problem… 8 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security 365x24x7 support Double coverage during Joint Ops Dynamic environment with multiple changing “customers” Workarounds were tedious Mind numbing work for engineers Hard to maintain proficiency SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving

9. Real OCA Use Case… 9 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving 1.Flight Note from BME (Biomedical Engineer) requesting downlinks of multiple files from multiple locations 2.OCA Officer connects onboard and manually finds and downlinks each file per note 3.OCA Officer manually FTPs (File Transfer Protocol) to BME 4.OCA Officer knows not to Archive or Mirror since it’s medical/personal data 5.OCA Officer notifies BME of their files (via loops or via e-mail) 6.OCA Officer manually updates Internal Note with info, marks as closed 7.OCA Officer updates handover Log with file transfers and console observations. 1.Flight Note from BME (Biomedical Engineer) requesting downlinks of multiple files from multiple locations 2.OCA Officer connects onboard and manually finds and downlinks each file per note 3.OCA Officer manually FTPs (File Transfer Protocol) to BME 4.OCA Officer knows not to Archive or Mirror since it’s medical/personal data 5.OCA Officer notifies BME of their files (via loops or via e-mail) 6.OCA Officer manually updates Internal Note with info, marks as closed 7.OCA Officer updates handover Log with file transfers and console observations.

10. How many Files/Size on average do we downlink from ISS Ops LAN each Week? 1.420 Files/ 310 MB 2.1120 Files/ 830 MB 3.3,540 Files/ 4.5 GB 4.7,680 Files/ 49.5 GB 10

11. How many files/GBs on average do we downlink from ISS Ops LAN each Month? Uplinked (Weekly Avg) –2,370 files uplinked –18 GB uplinked Hi =55 GB, Low= 6 GB Downlinked (Weekly Avg) –7680 files downlinked –49.5 GB downlinked Hi 110GB Low 20 GB Since April 2001-May 2011: Total Files Uplinked: 603,973 Total Files Downlinked: 2,511,011 Total Bytes Uplinked: 2,043,906,850,065 (1.9 TB) Total Bytes Downlinked: 10,055,933,620,320 (9.1 TB) 11

12. How we handled the Problem from 2000-2009 Like any other self respecting operations organization, we threw people at it! But, this solution was costly… –365x24x7 support –Double coverage during Joint Ops (both Space Shuttle and ISS flying) –Dynamic environment with multiple changing “customers” –Workarounds were tedious –Mind numbing work for new engineers –Hard to maintain proficiency 12

13. ARC/JSC Collaboration Joint collaboration with ARC (Ames Research Center) and JSC (Johnson Space Center) Mission Operations Directorate (MOD) was initiated in 2006/2007 ARC MODAT (Mission Operations Design and Analysis Toolkit) was identified as a possible solution for improving productivity of flight controllers in the MCC –MODAT utilizes the Brahms multi-agent language developed at ARC in the Work Systems Design and Evaluation group –Agents are used to automate tasks and leverage network infrastructure to automatically distribute information or communication –Technology simulates current and future environments to demonstrate gains or proposed solution outcomes –The simulations can then be used to build operational solutions ARC /JSC Project team began developing the agent based OCA Mirroring System (OCAMS) to automate OCA operations in 2008 13 JSC ARC

14. Agent-Based Systems Integration OCAMS is an application implemented in the Mobile Agents Architecture –MAA is a service-oriented infrastructure that enables interoperability among arbitrary hardware & software components –MAA has been used to develop a variety of workflow systems in NASA’s advanced operations research –Integrated components include: NOMAD, EFN, biosensors, voice commanding software, robots, cameras, GPS, & databases OCAMS was designed using the Simulation-to-Implementation software engineering method: –Work practice observation => simulation using actual mission data => design & embed prototype software tool in simulation => verification & validation of prototype => standalone agent system –Provides baseline–projected comparative productivity metrics 14

15. The Approach Understand what flight controllers spend their time doing on console Identify repetitive, administrative tasks Implement Software “Agents” that automate these tasks by integrating data and commands across subsystems Reduce operations cost by reducing manual tasks and increasing productivity and accuracy of console operations 15 OCAMS 2008 15

16. Design Methodology: Simulation to Implementation 16 Future Ops Simulation Metrics & Data Current Ops Simulation Work System Design Workflow Tool Operations Observation & Modeling Deployment & Refining in Practice SWRDFSH

17. The ISS Astronauts have internet access while on orbit. 1.True 2.False 17

18. ISS Internet Access As of Jan 2010, ISS crew has had internet access –Crew has been “Tweeting” ever since Was a concern for our OCA team over bandwidth usage 18

19. Inside the OCAMS software… All OCAMS agents (aka actors) are written in the Java language –To maximize performance, the Brahms logic was compiled down into Java for R4 and above OCAMS uses the ARC developed Collaborative Infrastructure (CI) for inter-agent communication Agents communicate using structured messages (CommunicativeActs) based on the FIPA specification OCAMS R4 agents use the open source Spring layered Java/J2EE application framework –Improves agent/application design; decouples component implementations used by agents –Configures an agent’s components to enable it to provide its specific services OCAMS persistence is managed using Spring and the open source Hibernate object-relational mapping (ORM) –Abstracts away interface to database (SQL) –Ability to change DBMS without changing application code 19

20. Remember the Problem… 20 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security 365x24x7 support Double coverage during Joint Ops Dynamic environment with multiple changing “customers” Workarounds were tedious Mind numbing work for engineers Hard to maintain proficiency SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving

21. Email JSC Office Environment MAS Platform Mission Support Network Low Security Flight Notes OCA LAN Moderate Security The OCAMS Solution… 21 File Transfers Publication of Products/Data to the world Notifications Console Logs File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Notifications SWRDFSH Archiving Console Operator OCAMS Agent (OA) OA OCAMS Management Console OCAMS software agents strategically placed in this environment to manage files transfers and user requests OCAMS Agents use multiple file attributes and rules to manage traffic OCAMS software agents strategically placed in this environment to manage files transfers and user requests OCAMS Agents use multiple file attributes and rules to manage traffic MCC LAN High Security Flight Following High Security Mirror LAN OA

22. The OCAMS First Deployment… 22 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving ARC teams analyzed the OCA environment and development of the Current Simulation model From this model and analysis, the OCAMS team (both JSC/OCA and ARC) decided to deploy OCA Mirroring as first implementation of OCAMS agents in the environment ARC teams analyzed the OCA environment and development of the Current Simulation model From this model and analysis, the OCAMS team (both JSC/OCA and ARC) decided to deploy OCA Mirroring as first implementation of OCAMS agents in the environment

23. 23 Current Operations: Mirroring Activities ≈ > 5% shift time Future Operations (with OCAMS): Mirroring Activities ≈ <.5% shift time Checking 25% Communicating 10% Configuring Resource 3% Deleting 3% Moving 35% Verifying 24% Statistics: Manual (current) vs. Automated (future) OCA Mirroring

24. The OCAMS First Deployment… 24 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving OA OCAMS established connectivity to the Mirror LAN OCAMS deployed an Agent on the Mirror LAN to read KFX log (transaction log for ISS file traffic) KFX was replaced with SWRDFSH Agent repeated actions taken onboard ISS by OCA Officer OCAMS established connectivity to the Mirror LAN OCAMS deployed an Agent on the Mirror LAN to read KFX log (transaction log for ISS file traffic) KFX was replaced with SWRDFSH Agent repeated actions taken onboard ISS by OCA Officer

25. OCAMS 1.0 OCA MAS PC OCA Machine Mirroring Staging PC OCA Mirroring System (OCAMS) PHASE A DESIGN (July ‘08) LEGEND: CA = Brahms Agent = Communication Agent (Java) OCA Officer = External System or Document - PF1 Server FTP PF1 Folders & Files KFX Log Folders & Files to/from the ISS KFX MirrorLAN Mirrored Folders & Files 25

26. Can the Astronauts call anywhere in the world, including to your cell phone right now? 1.Yes 2.No William Gerstenmaier, NASA Associate Administrator for Space Operations 26

27. Can the Astronauts call anywhere in the world, including to your cell phone right now? Yes, the Astronauts have a Cisco IP phone onboard –Used for unofficial communication only –Can call any valid phone number (looks like JSC calling on caller ID) Crew uses the phone to call family, friends and arrange events back on Earth –Birthday parties, Anniversaries, etc Checkout Cisco’s web site –Article Name: The first 90,000 Miles are Toll-Free –http://www.cisco.com/global/EMEA/sitewide_assets/ pdfs/tdm/iptel/Nasa.pdfhttp://www.cisco.com/global/EMEA/sitewide_assets/ pdfs/tdm/iptel/Nasa.pdf Crew Temporary Sleep Station on ISS 27

28. The OCAMS automation grows… 28 File Transfers (manual) Notifications Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving OA OCAMS Agent (OA) OA Deployments of OCAMS versions 2.0 and 3.0 distributed OCAMS Agents across environment Capabilities grew to include automated archiving, delivery and notification to customers (e-mail, flight notes), console log generation Evolution of users GUI and Rules Editor also progressed significantly Deployments of OCAMS versions 2.0 and 3.0 distributed OCAMS Agents across environment Capabilities grew to include automated archiving, delivery and notification to customers (e-mail, flight notes), console log generation Evolution of users GUI and Rules Editor also progressed significantly OCA Management Console

29. OCAMS 3.0 29

30. The OCAMS final pieces… 30 File Transfers (manual) Notifications OCA Management Console Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving OA OCAMS Agent (OA) OA Deployments of OCAMS 4.0 and 4.1 in early FY12 will include: ISS Upload/Download (e.g., processing Flight/Internal notes) Integrated Procedure/Rule Editor with Handover Log rules; more powerful procedure language & execution; prioritized file delivery; parallel FTP Deployments of OCAMS 4.0 and 4.1 in early FY12 will include: ISS Upload/Download (e.g., processing Flight/Internal notes) Integrated Procedure/Rule Editor with Handover Log rules; more powerful procedure language & execution; prioritized file delivery; parallel FTP

31. OCAMS 4.1 31

32. OCA Mgmt Console ….. Notification Icon indicates what type of notification is to be performed..(i.e. Flight Note, Email, etc) c c Action, Monitor, Log, Archive, Notification, Log c c 32

33. Same Task, New Process… 33 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving OA OCAMS Agent (OA) OA 1.Flight Note from BME (Biomedical Engineer) requesting downlinks of multiple files from multiple locations 2.OCAMS Agents parses Internal Note, creates and presents the procedure to the OCAMS Manager for review 3.OCAMS Manager reviews and releases the procedure 4.OCAMS communicates to SWRDFSH the locations and files to be downlinked 5.SWRDFSH downlinks the requested files. 1.Flight Note from BME (Biomedical Engineer) requesting downlinks of multiple files from multiple locations 2.OCAMS Agents parses Internal Note, creates and presents the procedure to the OCAMS Manager for review 3.OCAMS Manager reviews and releases the procedure 4.OCAMS communicates to SWRDFSH the locations and files to be downlinked 5.SWRDFSH downlinks the requested files. OCA Management Console

34. Same Task, New Process… 34 File Transfers (manual) Notifications OCA Officer Console Logs Flight Following High Security Mirror LAN File Transfers (Share Drive) File Transfers (FTP) ISS OpsLAN File Transfers (Drop box) Email JSC Office Environment OCA LAN Moderate Security SWRDFSH MCC LAN High Security MAS Platform Mission Support Network Low Security Flight Notes Publication of Products/Data to the world Notifications Archiving OA OCAMS Agent (OA) OA 6.OCAMS delivers the files to BME via FTP 7. OCAMS does not to Archive or Mirror based on procedures and rules definitions 8. OCAMS notifies BME of their files via e- mail 9. OCAMS updates the Internal Note 10.OCAMS updates the OCAMS Handover Log with file transfers 11. OCAMS Manager updates the OCAMS Handover Log with any console observations 12. Handover Log available to be generated from OCAMS as required 6.OCAMS delivers the files to BME via FTP 7. OCAMS does not to Archive or Mirror based on procedures and rules definitions 8. OCAMS notifies BME of their files via e- mail 9. OCAMS updates the Internal Note 10.OCAMS updates the OCAMS Handover Log with file transfers 11. OCAMS Manager updates the OCAMS Handover Log with any console observations 12. Handover Log available to be generated from OCAMS as required 10 11 12 OCA Management Console

35. OCAMS Current ROI 36

36. Potential Other OCAMS Uses Additional Mission Control Center (MCC) Automation –MCC21 project to redesign MCC for 21 st century may apply agents technologies to help manage legacy and new applications communication Support Government Green Facilities/Building Initiatives –Build an integrated Brahms model of facilities + work practice + environmental systems, to simulate environment –Final product could lead to software "Power Agents" agents that interact with the building occupants –Allows occupants and engineers to get data, alerts, trend interpretations, etc. anywhere, anytime NASA FAA “Authority and Autonomy” research –ARC is working on using Brahms for ATC (Air Traffic Control) simulation –Project is exploring the possibility of extending formal human-system performance modeling from the individual level to the level of complex multi- agent teams incorporating human experts and software agents in realistic mixed-initiative scenarios. –These scenarios may entail reconfiguration of airspace and reassignment of roles and responsibilities among human and software agents Funded for FY12 Other potential projects: 37

37. Does an iPad screen auto rotation work in Zero G? 1.Yes 2.No 38

38. Does the iPad screen auto rotation work in Zero G? http://www.youtube.com/watch?v=syWwp CxJcfkhttp://www.youtube.com/watch?v=syWwp CxJcfk Author Note: This was also tested by a NASA Astronaut on an ESA Zero G test flight in 2010 as well Interesting note was that not only did not work in Zero G (over the top of the parabola) but it didn’t work at greater than 1 G (at the bottom of the parabola) either 39

39. POC (JSC) : Tim Hall timothy.a.hall@nasa.govtimothy.a.hall@nasa.gov POC (ARC): William.J.Clancey@NASA.GovWilliam.J.Clancey@NASA.Gov Reports: http://bill.clancey.namehttp://bill.clancey.name Technology: http://www.agentisolutions.comhttp://www.agentisolutions.com

43. OCAMS Releases Release 1 – July 2008 –Mirrors files to the MirrorLAN; all operations logged in Handover Log Release 2/2.1 – March 2009 –Distributed configuration; Archiving & Deletion; Prototype editor for file management rules; GUI on MAS Release 3 – September 2009 –Delivery of products to customers & Notification (e-mail, flight notes) Release 4 – Summer 2011 –ISS Upload/Download (e.g., processing Flight/Internal notes) Release 4.1 – early FY12 –Integrated Procedure/Rule Editor with Handover Log rules; more powerful procedure language & execution; prioritized file delivery; parallel FTP; etc. 43

44. 44 Description/Archite cture: MAS Mirror LAN OCA LAN ISS Ops LAN OCAMS Phase A