Use Case:
ATCS Cold Start
Description:
This is the normal operation after a system complete or partial power-up or reboot.
Each required subsystem is brought from state OFF to state STANDBY and initialized.
A failure will leave the ATCS in state OFF substate ERROR.
Role(s)/Actor(s):
Primary: Operator, Maintenance
Secondary: Standard Packages
Priority: Major.
Performance: 10 minutes
Frequency: Typically, after relocation procedure.
Preconditions:
- ATCS is in state OFF
- ATCS ready to accept Mode Switching commands
Basic
Course: Cold start automatically
- Send command CSTART
to ColdStart ATCS
Exception Course: Command failed
- ATCS initializes and puts in STANDBY
all required and not ignored subsystems
Exception Course: Some sub-systems failed to initialize or to go to STANDBY
Postcondition: all required and
not ignored subsystems are initialized and in STANDBY state
- ATCS global
system state update
Postcondition: ATCS in state STANDBY, substate IDLE
- ATCS sends final OK reply
Alternate
Course: Cold start manually
- Initialize and puts in STANDBY all required and
not ignored sub-systems one by one
Exception Course: Some sub-systems failed to initialize
or to go to STANDBY
Postcondition: all required and
not ignored subsystems are initialized and in STANDBY state
Exception Course: Command failed
Exception Course: Some sub-systems failed to
initialize or to go to STANDBY
Postconditions:
- ATCS is in state STANDBY, substate IDLE
- All required and not ignored ATS subsystems
are initialized and in STANDBY
- Control loops are disabled and brakes engaged
Issues to be Determined or Resolved:
Notes:
Last modified: Thu Jun 28 13:32:50 UTC 2001