Timeliner: Automating Procedures on the ISS

1
Timeliner Automating Procedures on the ISS

• Dr. Robert A. Brown
• Presented at Space Ops 2002

2
What is Timeliner?

• Timeliner is both a programming language and an
  execution environment.
• The programming language is a scripting or
  procedural language.
• Used to write automated procedures that can
  execute autonomously, be event, time, ground
  and/or crew command driven, based on OSTP
  activities, and can be initiated by on-board
  payload requests (or combination of these).
• Can be used in conjunction with manual crew
  procedures (as a step in a crew procedure) or can
  request the crew to perform a manual procedure
  via Timeliner message capabilities.
• The execution environment is a combination of ISS
  CDH software and related ground software.
• On-Board Software
• the Timeliner Executor
• Running in the Payload MDM as part of the PEP
  software
• Running in the CC MDM as part of the CCS
  software
• Running in the JEM as part of the JCP software
• the Automated Procedure Viewer (APV) PCS display.
  
• Ground Software
• Timeliner compiler and supporting database tools
• Integrated into the Payload Information
  Management System (PIMS) for payload procedures
• Integrated into the Integrated Planning System
  (IPS) for core procedures
• Ground operations tools
• Planning tools

3
Technological Advances
Enhanced Human Interface
Integrated Mission Planning Monitoring

• Voice recognition and message annunciation for
  hands-free procedure interaction and control
• Text to speech for crew/operator messages
• Crew/operator response to scripted queries
• e.g. CONFIRM Anomaly detected, do you wish to
  continue?

• Mission specific GUI-based, object-oriented layer
  for planning system procedure development tools
• Object-oriented, picture-based, coordinated
  procedure/plan and system execution monitoring

Extended Target System Description Interface

• Greater abstraction of target system description
  interface
• Allows for easy integration with existing
  databases
• Provides wide flexibility for definition of new
  system

4
What is the history of Timeliner?

• Created by the Charles Stark Draper Laboratory in
  1982.

• Used to emulate the actions of the Space
  Shuttle crew in timelines and on-board crew
  procedures.
• Still being used for that purpose today (in
  training, simulations, testing).

• Chosen as the User Interface Language (UIL)
  for the Space Station program in 1992.

• Timeliner is being used by the U.S. core and
  payload communities.
• Timeliner is also being developed by NASDA for
  both core and payload functions.
• The NASDA Timeliner is known as PREX for
  Procedure Executor.
• Timeliner is also known as UIL, automated
  procedures, and bundles, the name for Timeliner
  files.

5
What is the current status of Timeliner?

• Timeliner Executor is on-orbit aboard the Payload
  MDM now
• Planned for first use on ISS Flight 9A to
  automate Payload MDM and Payload Rack Operational
  Functions
• Prototype bundles have been developed and are in
  test
• Ground interfaces to Timeliner for PLMDM and rack
  ops use is undergoing final integration
• Currently developing PODF Management Plan annex 1
  and Operations Concepts documents
• Payload Experiment automation using Timeliner
  projected for Flight 12A may occur sooner
• Targeting several experiments as first users at
  the science level
• Time-based functions For example, MAMS payload
  daily file downlinks
• Extensive ground command script users For
  example, EXPPCS and ZCG payloads
• Timeliner Executor will reside on the CC MDM at
  Flight 12A (CCS R3) and will become operational
  for initial use in automating Core functions
• Pathfinder automated procedure for Thermal
  Control System reconfiguration developed and
  being tested
• USA is integrating Timeliner compiler into IPS,
  using IMARS products
• Flight control team is just coming up to speed on
  Timeliner
• Timeliner automated procedures will be used to
  upgrade power controller firmware at Flight 13A
• Boeing to generate automated procedure
  executables that will be delivered as part of the
  13A flight software load
• Draper is developing tools to allow Boeing to use
  Draper-provided Timeliner compiler and their own
  Ground Data Base as well as to verify the
  executables generated

6
Timeliner Language

• Specialized computer language designed for the
  writing of automated control procedures, which
  serve as an aid for human operators
• The main language characteristics are
• English-like, intended for system specialists,
  not computer programmers
• Time-oriented, based on keywords like when,
  whenever, wait, before, etc.
• Conditional logic for making decisions (if x or
  y ...)
• condition is general can be system data,
  time, or combinations
• Action statements for
• Interacting with target system
• Issuing operator messages
• Controlling procedure execution

Conditional Constructs WHEN condition WHENEVER
condition actions actions IF condition EVERY
condition actions actions
Action Statements COMMAND system_command,
parameters SET system_object TO value MESSAGE
message to operator INSTALL script_to_be_insta
lled START procedure_to_be_started
7
Timeliner System Components
System Cmd/Obj Description
System Cmd/Obj Standard Output
Timeliner Command and Object Description Tools
Search Interface
Timeliner Script Compiler
Script Source Files
System consists of two majorcomponents
Compiler and Executor
Script Executable Files
Script ASCII Listing Files
Executor Connectors

• Procedure compilation canoccur separate from
  systembuild
• Compiler queries Target System Description for
  Command/Object Definitions
• Procedures are rolled-in(installed) to be
  executed
• Displays monitor and control script execution
• Scripts issue commands to Target System
• Scripts reference Target System Data Objects

Timeliner Script Executor
Timeliner GUI Monitor Control Displays
Executor Status
Executive Control Commands
Target System Commands
Target System
Distributed System Data Objects
8
Script Organization Control
Executor
Control

BUNDLE
FREEZE_ALL
RESET_FREEZE
Sequence A
Sequence B
Sequence C
Sequence
Control

Bundle
START
call
Control
STOP

INSTALL
RESUME
REMOVE
SINGLE STEP
Subsequence X
HALT
HOLD AT
JUMP TO

• Each Bundle is composed of Sequences that execute
  in parallel with each other
• Compiled Bundles can be Installed, Removed on
  command
• Sequences can be Started, Stopped, Single
  Stepped individually and independently
• Sequences can utilize shared Subsequences

9
ISS Timeliner Big Picture
U.S. Lab
JEM
CC MDM
Payload MDM
JCP
IPS
CCC
NASDA Compiler
PSIV
POIC
Training
Training
Requirements Sources
JSC
MSFC
CC - Command Control CCC - Central Control
Complex (JSC) IPS - Integrated Planning System
JCP - Japanese Control Processor JEM - Japanese
Experiment Module MDM - Multiplexer/Demultiplexer
NASDA - National Aerospace Development Agency
(Japan) POIC - Payload Operations and
Integration Center PSIV - Payload Integration
and Verification (Facility)
10
Payload Operations Components
PAYLOAD CREW
POIC CADRE
Thermal Systems
Payload Systems
Vacuum/Vent Systems
Time Critical Commanding
P/L SYSTEMS S/W ( crunching logic)
Rack Act/Deact
Payload Data/Info to Crew/Ground
PAYLOAD - MDM
Electrical Power System
Payload Complement Management
etc.....
Payload Reconfiguration
Timeliner Executor
Bundle - A
CVT
Sequence -1
123 556 124 3456 125 3595.0 126
9854.9
Payload A
Payload Users
Payload B
Individual Payload
Sequence -1
Time Critical Commanding
Experiment S/W ( crunching logic)
Payload C
Payload D
Payload Rack
Timeliner will allow Payload/Payload Systems to
operate
with minimal/no crew time and during LOS.
11
Mission Environment Utilization

• Perform pre-mission, during mission, and
  post-mission system checkouts
• Provide master sequencing for complete mission
• From remote controller workstation(s)
• Embedded, semi-autonomous, or fully autonomous
  mode
• Monitor for extraneous conditions and execute
  contingency plans

PCS
Cmds
Data
TL
Status
Flight
Messages
System
Selection
System
System
TL
Data
Cmds
Cmds
Timeliner Compiler
Timeliner Executor
Load
12
Automated Procedure Summary
High Level Monitor and Control of Timeliner
Executor Activities for Core or Payload
Operations
13
Detailed Procedure Monitor Control

• Allows Interaction with Procedures via
• Executor Commands and Crew Messages

• Automated tracking of procedure execution
• Individual procedure step control
• Resume
• Stop
• Jump To
• Single Step
• Dynamic crew annotation

14
Timeliner Toolsuite

• Complete set of software tools for automating
  process control
• Reuses software developed for NASAs ISS program
  with minimal modifications
• Target system description database development
  tool
• Timeliner Compiler GUI
• Timeliner Executor UNIX socket connections
• Automated Procedure Viewer
• General purpose interface can be applied to any
  target system
• Operates on Desktop PC
• Provides simple interface for network
  connectionsvia UNIX sockets
• Execution status control
• Target system commands data
• Target system description abstracted from process
  algorithm

15
Simulation Environment Utilization

• Initialize/drive simulations
• Simulate man-in-the-loop inputs
• Insert errors, perturbations, dispersions
• Capture data under specified conditions

Flight Displays
Monitor/Control
Flight
System
System
"Mission Ops" Timeliner
"Mission Ops" Timeliner
Simulation
(Models, etc)
Commands
Data
SIM Timeliner Executor
SIM Timeliner Compiler
Compiled
Test
Scripts
Designer
Selection
16
Mission Environment(Ground-based)
17
What is the Future for Timeliner?

• Timeliner provides a flexible tool for automating
  system operations
• Standard interfaces and methodology allow rapid
  integration of Timeliner executor with new target
  systems
• Commercially, Timeliner has been adapted to
  control delivery of broadband cable services to
  customers
• Draper has illustrated use of Timeliner to
  control
• Typical science experiment (Plant Growth)
• Embedded hardware (Button and light experiment)
• Draper has integrated Timeliner executor into
  various test environments
• MDM simulation used for APV acceptance testing
• Draper test environment for FQT of Timeliner
  compiler and executor
• Draper has integrated Timeliner executor into
  existing flight software
• Payload Executive Program (PEP) in a supporting
  role
• Command Control Software (CCS) as lead
  developer
• For future ISS consider
• Integration of Timeliner into the MCC ground
  environment to reduce ground support manpower
  requirements
• Promote increased use of Timeliner by payload
  developers to better automate payload operation