summary of planned obsets and their quality C3 BASE_36 When a proposal is accepted into the PMDB by SPSS it must be assigned a unique 3 character base 36 program identifier. This is done by the PMDB/ACCEPT_PROP command. Is is used for identification of proposals by spacecraft and OPUS software. It is also used in the OPUS and DADS rootname for all archived science data files. Because of flight design software, program_id must be three characters. C2 BASE_36 An observation set is a collection of one or more alignments that are grouped together based on FGS pointing requirements. That is, if multiple alignments can all be executed using the same guide star pair, they are grouped into the same observation set. C9 C5 A proposal consists of many individual observations submitted as a package by a proposer. When a proposal is processed by the proposal entry system (RPS2), it is assigned a proposal identifier. That identifier is an integer that is converted into a 5 character base 36 string. C7 A scheduling unit consists of one or more observation sets and is the fundemental object which is placed on SPSS calendars. A synonym for a scheduling unit in SPSS is a 'candidate.' A scheduling unit is identified by a seven character base 36 string. For operational proposals the first five characters are the proposal ID (with a leading zero). C17 This field is set to the earliest start time of the observations in qolink_sms for a given program_id, obset_id, sms_id. C17 This field is set to the latest end time of the observations in qolink_sms for a given program_id, obset_id, sms_id. C1 is this scheduling unit dependent on another? C5 the prime obset for this scheduling unit, if any C5 the pathfinder obset for this scheduling unit, if any C5 the obset containing a mode 1 target acquisition (interactive) for this scheduling unit, if any C1 should this obset be reviewed by an operations astronomer? C1 was this obset assessed for quality? C25 file name containing a comment that applies to the quality of all observations in this obset C1 the first unused key field in this record C14 a keyword that pertains to the quality of observations in this obset C3 the obnum of the observation in the obset to receive this keyword C14 a keyword that pertains to the quality of observations in this obset C3 the obnum of the observation in the obset to receive this keyword C14 a keyword that pertains to the quality of observations in this obset C3 the obnum of the observation in the obset to receive this keyword C14 a keyword that pertains to the quality of observations in this obset C3 the obnum of the observation in the obset to receive this keyword C14 a keyword that pertains to the quality of observations in this obset C3 the obnum of the observation in the obset to receive this keyword I4 numeric code for failure. This field maps to the comment field in dq_comments. C2 moniker of observations astronomer reviewing obset SYBASE_DATETIME when was quality evaluated? text a comment that applies to the quality of all observations in this obset SYBASE_DATETIME when was the last file needed to assess quality removed from online storage? C1 assessment products previously deleted SYBASE_DATETIME Date and time the record was inserted into this table SYBASE_DATETIME Date and time the record was last updated SYBASE_DATETIME Date and time when all records are deleted from qolink_sms for a given program_id, obset_id and sms_id. The rti_table record remains and the delete_date is filled in indicating this record is inactive. RTI_TABLE_TYPE summary of planned obsets and their quality OPUS unique clustered