Table 1: SCHEDULE: Schedule characteristics
SHEDULE: Schedule information

Name

Format

Units

Measure

Comments

Columns

Data

SCHEDULE_INTENT  

String

Schedule intent

SCHEDULE_TYPE

String

Schedule type

SCHEDULE_DURATION

float

s

Approximate duration if execited

SCHEDULE

String 

Scheduling Block 

NUMBER_SCAN

Int

Number of different SCANs in this Scheduling Block 

SCAN_INTENT

String (NUMBER_SCAN)

Intent of each SCAN in the Scheduling Block

OBSERVING_MODE  

String(*)

Observing mode



Notes: This table contains the list of scheduling blocks generated by observation preparation tools. A summary of informations is attached to each scheduling block. It is indexed directly from the sub-table EXECUTE_OBSERVATION via SCHEDULE_ID. The associations of Scheduling Blocks are defined in the OBSERVATION_UNIT_SUMMARY sub-table using list of SCHEDULE_IDidentifiers.
SCHEDULE_INTENT
Goal of Scheduling Block (SB). Several SBs may share a common SCHEDULE_INTENT.
SCHEDULE_TYPE
The schedule type, with the current reserved types VLBA-CRD1  VEX2  WSRT3  ATNF4 In the ALMA context: Sheduling Block (SB). ALMA will need to reserve its type.
SCHEDULE_DURATION
Approximate duration which would be required to execute this SCHEDULE.
SCHEDULE
Unmodified schedule file, of the type specified, and as used by the instrument.
NUMBER_SCAN
Number of SCANs defined for the scheduling.
SCAN_INTENT
List of intents with these different SCANs.
OBSERVING_MODE
Observing mode, e.g. singleField, mosaic (origin: OT) One SB cannot have more than one observing mode Example: FS (for FastSwitching), RC (for with radiometric corrections), FSRC (for both FS and RC), mosaicingPointed, mosaicingOTF etc...
OBSERVING_MODE was in the MSv2 OBSERVATION sub-table. It is moved in this new sub-table since one SB must correspond to a single observation mode. 
Why a single observing mode? .

Remark:  
Notice that the same SCAN may be executed in different SCHEDULEs! This suggests to have a SCAN sub-table and a reference here via a list of SCAN_ID.
This table could be generated at the stage of the preparation of the projects while the observations have not yet started.