The detailed actions for each transition in each crate need to be defined. A first draft of these, for normal runs, are given in the appendix in tables 1, 2, 3, 4, 5, 6, 7, 8.
Further work is required to list the additional actions
required for the various types of calibration and test run.
In general, each crate will read all necessary information from the
database at the Load step. Some run type independent settings and
checks can be made at the Configure step. Final downloading of run
type dependent information to the modules can be done at the Start
step. It may be wise to use the Resource
Manager (RM) package to lock crates (or possibly individual modules
in some cases?) against simultaneous use by another partition.
Some actions on the whole system require the use of the TTC system.
They are the kind of actions which might naturally be allotted to an
overall system controller, but as they require access to the TTCvi
are naturally implemented in the TTC crate.
Note that the DSS crate (or modules) are only required in some test setups.