Operations-Based Lessons Learned for Space Telerobotics System Design

Paper number

IAC-05-D1.5.04

Author

Mr. Timothy Braithwaite, Canadian Space Agency, United States

Coauthor

Mr. Sarmad Aziz, Canadian Space Agency, United States

Year

2005

Abstract

The experience of commissioning and operating Canada’s Mobile Servicing System (MSS) on the International Space Station (ISS) has provided invaluable lessons learned for space-based robotics systems design.  The MSS’ ability to maneuver and precisely position very large ISS elements has made the assembly of the ISS possible.  However, the complexity of this widely-distributed system has necessitated the development of new operational techniques and practices.  This experience has illustrated that the operability of such a system can be enhanced by ensuring that specific attributes are incorporated into the design.  Similarly, steering clear of certain design pitfalls will allow the system to avoid negative attributes.

This paper explores these ideas, supporting them with the experience of real-life International Space Station robotic operations and illustrating them by examples.  It also discusses the inevitable trade-off between operational simplicity (often embodied in large complex software incorporating expert decision making and sequencing) and the need to be able to control individual low-level software functions in off-nominal (or unanticipated) situations.  The successful application of these principles will ultimately enhance system robustness, as well as increasing the degree to which all system components and sub-units can contribute to mission success.

The paper first expresses the lessons of the MSS operations experience as a set of fundamental tenets, including:  design for system robustness; maximize operational flexibility and operator control over the system; maximize operator insight into system status; design for operational simplicity and economy.  These ideas are then expanded into a more specific checklist of attributes and pitfalls that can be applied to existing systems where options exist for software and system upgrades.  However it will be most usefully applied to a system that’s still relatively early in the design process.

Abstract document

IAC-05-D1.5.04.pdf

Manuscript document

IAC-05-D1.5.04.pdf (🔒 authorized access only).

To get the manuscript, please contact IAF Secretariat.