Montreal, Canada

1
Autonomous Operation for Japanese Experiment
Module (JEM) Cost Reduction
Montreal, Canada May 17 21 2004
Kazuya Imaki /JAMSS lt imaki_at_jamss.co.jp
gt Nobuyuki Hoshino /JAMSS lt nhoshino_at_jamss.co.jp
gt
2
1. Abstract

• The following is a proposal to introduce more
  autonomous operation for the Japanese Experiment
  Module (JEM) (also known as Kibo (Hope) in
  Japanese) in the International Space Station
  program for the purpose of cost reduction and
  efficient operations. If this proposal is
  adopted, critical skills of JEM Flight
  Controllers (FCs) can be improved, cost for
  preparation and operation can be reduced, and
  efficient and validated operation during and
  after the JEM activation and checkout phase can
  be achieved.

3
2. JEM Ground Operations system overview

• The JEM ground operation systems are located at
  the Tsukuba Space Center in Japan as part of the
  Space Station Integration and Promotion Center
  (SSIPC). From here, ground systems and personnel
  operate the JEM systems and Japanese payloads by
  planning, commanding and telemetry monitoring,
  and decision making.
• The JEM ground operation systems overview is
  shown in next page.

4
2. JEM Ground Operations system overview (cont)
SSIPC Space Station Integration and Promotion
Center
Weightless Environment Test System (WETS)
Operations Data Network System
Logistics and Maintenance Operations Management
System
Element Integration System
Operations Control System (OCS)
Operations Procedure Verification and Training
System (PVT)
5
2. JEM Ground Operations system overview (cont)
6
3. Why is JEM a Candidate For Autonomous
Operations?
The JEM is a candidate for manned flight system
autonomous operation because of the following
(a) The JEM system and ground operation systems
are smaller and simpler than the U.S. system,
and do not have a life retention system nor
attitude control system. (b) The JEM is not
launched yet, so the autonomous operation
systems can be verified by ground test. (c)
High performance computers are readily available,
which can handle large amounts of data and
calculate quickly.
7
4. JEM Autonomous Operation Concept
Current and past manned space flight (ISS,
Shuttle missions, and satellite missions) was
researched for autonomous operations. Using
lessons learned from these missions, the
following autonomous operation concepts are
proposed (a) Autonomous Commanding
Operations (b) Maintain FC Skills (c) FC
Support Tools (d) Procedure Development Support
Tools The following concepts need further study
(a) Autonomous operation using artificial
intelligence (b) Autonomous operation using
on-orbit system
8
5. Autonomous Commanding Operations
The following two concepts are proposed for
efficient and reliable autonomous commanding
operations - Integrated ground operations
systems - Autonomous function with rule-based
operation For Nominal Operations (a) Command
execution based on mission timeline Operation
image is shown in next page.
9
5. Autonomous Commanding Operations(cont)
OCS display data
Mission time line
Automatically selects activity from mission
timeline.
10
5. Autonomous Commanding Operations(cont)
For Nominal Operations (cont) (b) Automated
Commanding and Telemetry monitoring FCs can
currently execute Command operations using
Command script files in the SSIPC Ops. If the
OCS has a function to automatically verify
Telemetry before and after sending a Command,
based on rule- based operation, FCs time can be
saved by reducing tedious tasks during routine
operations. For Off Nominal Operations If the
Ground system has an automatic troubleshooting
function using malfunction procedures, the FCs
can save time and execute certain
troubleshooting. Operation image is shown in
next page.
11
5. Autonomous Commanding Operations(cont)
12
6. Maintain FC Skills (Not completely autonomous
operation!)
If the flight and ground system were
integrated, a completely autonomous operation
system could be developed. But, based on the
current flight and ground system design, the
system will often encounter failures that FCs
need to troubleshoot (i.e. on-board
configuration, unique configuration, multiple
failure cases). The FC must remain a part of the
automated system. Therefore, the following
operations should not be automated to maintain FC
skills for unique and unexpected off-nominal
operation (a) Procedures, rules, and mission
timeline development (b) Real-time unique
operations (c) Crew support (d) Technical
judgment in certain malfunction procedures
13
7. FC Support Tools

FCs use large amounts of source information
from hardware developers to develop procedures,
rules, and mission timelines. These documents
are kept as reference for the lifetime of the
program in case of off-nominal operations.
During operations and especially during
off-nominal operations, it is difficult to search
through the necessary documents quickly. There
is a possibility of miss operation if the
information has not been organized efficiently.
Therefore we need to have practical support
tools. - Command and telemetry data - Photo,
Test data - Power and communication data -
Total flow and caution and warning information
etc,
14
7. FC Support Tools (cont)
Picture info.
CMD/TLM info.
TCS general info.
Ex) ATCS support tool (sample)
We are currently determining what types of FC
tools the FCs require, and considering a
development plan and requirements for each FC
support tool.
15
8. Procedure Development Support Tool
Procedure development support tools are
desirable because many procedures need to be
developed with a limited number of FCs. We can
save cost and time by using Support tools to
develop procedures (including malfunction
procedures) and to validate the procedures.
Note NASA is developing and testing a tool to
aid in applying standards (i.e. layout, font,
look/feel, etc) to the procedures. The following
tool can be used in conjunction with NASAs tool.
The Procedure development tool has the following
functions
16
8. Procedure development Support Tool (cont)
Procedure development (1) Command and Telemetry
search engine The following tool is a Web-based
command and telemetry search engine using the
ground system database. It is very useful for
making procedures.
17
8. Procedure development Support Tool (cont)
Procedure development (2) Procedure
configuration management tool on web The
Web-based procedure configuration management tool
manages the following source data and each
procedures revision. If a source data is
modified, the FCs can identify the impacted
procedures quickly. - Requirements, - Rules
and constraints - Related procedures, -
Telemetry and command
18
8. Procedure development Support Tool (cont)
Procedure Inspection (1) Procedure requirements
automatic comparison This tools major
functions are as follows - Import procedure
(MS word file) to database. - Command and
telemetry unique identifier, Name, Value,
Onboard/Ground display name matching. etc,
Command and telemetry sequence by procedure
Inspection menu
Inspection result (vs. requirement)
19
8. Procedure development Support Tool (cont)
Procedure Inspection (2) Malfunction Procedure
inspection Malfunction inspection tools are
being developed. Majoring functions are
follows - Automatically converts a Mal-Flow
diagram (MS-Word or XLM files) to a model
description - Consistency analysis -
Suitability analysis Details are shown in
section 10.
20
9. Future work for JEM Autonomous operation
The following areas of study will be performed
this year (a) Feasibility study of possibility
to use each autonomous function with hardware
developer (b) How much manpower can be reduced
from original operation concept if we use
autonomous operation (c) Clarify FC support
tools detailed functions (d) Upgrade Procedure
Development Support Tool
21
10. Pilot program

• Difficulties to develop the logical flow diagrams
  of malfunction procedures (Mal-Flow)
• Complicated spacecraft system
• Difficult to confirm consistency in case of
  complicated system composed of many Mal-Flows
• Contain technical information
• Difficult to confirm suitability of Mal-Flows
  that is complex and not easy to understand
• Develop a method to automatically confirm
  consistency and suitability of Mal-Flows time
  saving and quality improvement
• (1) Development of Mal-Flow Model Development
  Tool
• (2) Development of Mal-Flow Analysis Tool
• (3) Validation of analytical method by sample
  Mal-Flow

22
10.1 Development of Mal-Flow Model Development
Tool
Mal-Flow Model Development Tool automatically
converts a Mal-Flow diagram to a model
description. (1) Drawing Mal-Flow by CAD and
save the Mal-Flow in Scalable Vector Graphics
(SVG) form (2) Executing Mal-Flow Model
Development Tool and Mal-Flow model is output
automatically
23
10.2 Development of Mal-Flow Analysis Tool

• Mal-Flow Model Analysis Tool automatically checks
  Mal-Flow model.
• Consistency analysis
• Warn if there are multiple identical judgments
  in a single path of a Mal-Flow, where one
  judgment concludes Yes, and the later judgment
  concludes No.
• Executing Mal-Flow Analysis Tool and analysis
  result is output automatically

24
10.3 Validation of method by sample Mal-Flow

• The analytical method is validated using a sample
  Mal-Flow provided by the FCs.
• Result No Consistency
• There is a judgment Is BIT Result-Normal?No,
  and this path later leads to the judgment Is BIT
  Result-Normal?Yes'.
• However, according to inspection of Mal-Flow, we
  found that they are not the same BIT Result, no
  problem of the consistency.
• Analysis result could give appropriate attention
  to the reviewer of a potential vagueness in a
  description
• More effective to analyze large volumes and
  complex Mal-Flows

25
10.4 Conclusion - View of the future

• Developed Mal-Flow Model Development and Analysis
  Tool, and effective analysis result related to
  consistency could be obtained
• To make the analysis tool useful in the future,
  the following additional functions will be
  examined
• ? Completeness analysis
• ? Consistency analysis of configuration
• ? Consistency analysis with mission priority
• ? Identify the part where the hazard control
  temporarily becomes impossible by the operation
  in emergency

26
11. Backup
27
11. Backup (cont.)
Japan developed an experiment module called JEM
(Kibo). JEM (Kibo) is the first manned facility
for Japan in which a maximum of four astronauts
can perform experimental activities for long
duration. JEM (Kibo) consists of four main
components, two experimental facilities (the
Pressurized Module (JPM) and Exposed Facility
(JEF)), and two logistics modules attached to
each facility (Pressurized module (JLP) and
exposed facility (JLE), respectively. Also, a
Robotic Manipulator System (JEMRMS) and an
Airlock on the JPM will be used for experiments
or ORU change out tasks.
JLP
JEMRMS
JPM
JEF
JEM Airlock
JLE
JEM System overview
28
11. Backup (cont.) Malfunction procedure sample
29
11. Backup (cont.) Ground system display
(Sample)