Go to the bottom.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL: PLAN_WINDOWS.SDDL
!
! Purpose: This defines the plan_windows relation.
!
! Modification History:
!
! Date PR Who Reason
! -------- ------- --- -------------------------------------------------
! 07/18/94 27073 SSW SPSS Planning Windows Support
! 02/02/95 28292 SK Modified "REPLICATION" wording under
! SUBSYSTEM_USING
! 01/16/96 30681 EGB Use new LRP_NAME_TYPE
! 04/16/97 33890 MRB Field names changed in ASSIST from wnd_ to _window
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
LANGUAGE FORTRAN,SQL
INCLUDE ZSPSS_USER_TYPES.SDDL
CONSTANT WINDOW_TYPE_PLANNING
VALUE 2
END_CONSTANT
RECORD PLAN_WIN_TYPE
!------------------------------------------------------------------------------
!
! RECORD INFORMATION
!
!------------------------------------------------------------------------------
DESCRIPTION
"Plan windows are defined to be the time interval in which SPSS must
schedule a scheduling unit. Plan windows are generated by SPIKE and
the set of plan windows for all SUs defines the Long Range Plan (LRP).
This relation contains multiple sets of plan window sets, i.e. it
contains one or more versions of the Long Range Plan. The lrp_base_cat
relation tells which LRP is the current operational LRP to use.
Plan windows are treated as a scheduling constraint by SPSS.
Therefore, SPSS does its best to ensure that each scheduling unit is
scheduled before its last plan window ends.
Constraint windows are related to plan windows, but are broader
in the sense that they are time intervals in the proposal cycle where
SPIKE thinks a scheduling unit (SU) can be scheduled. This is based
on the target position, orientation requirements, links, locks,
phase windows and the minimum visibility period. The windows are
start-to-start, i.e., a an SU must start before the window end, but
may end after the window end.
A plan window will be a subset of a constraint window and SPSS users
can verify SPIKE constraint windows using the CALOPT/VERIFY command.
This gives SPIKE feedback on the accuracy of its constraint windows and
with that information it can create a more accurate LRP comprised of
plan windows known to be schedule on SPSS calendars."
!------------------------------------------------------------------------------
!
! FIELD INFORMATION
!
!------------------------------------------------------------------------------
FIELD sunit_id
TYPE SUNIT_ID_TYPE
END_FIELD
FIELD version_num
TYPE VERSION_NUM_TYPE
END_FIELD
FIELD lrp_name
TYPE LRP_NAME_TYPE
RELATED_FIELDS "lrp_base_cat.lrp_name"
END_FIELD
FIELD visit_id
TYPE VISIT_ID_TYPE
END_FIELD
FIELD prop_id
TYPE INT_PROPOSAL_ID_TYPE
END_FIELD
FIELD status
TYPE C10
DESCRIPTION "This field will be used to indicate the
following states:
- Window generated by SPIKE
- SU was ignored
- Window set by focus set
- Pool focus set
- At least one edge of the window
is a hard constraint.
The field is used to aid program coordinators. The
valid values are yet to be defined."
END_FIELD
FIELD window_begin
TYPE SOGS_CHAR_TIME_TYPE
DESCRIPTION "This field is the start time of the plan window."
END_FIELD
FIELD window_end
TYPE SOGS_CHAR_TIME_TYPE
DESCRIPTION "This field is the end time of the plan window."
END_FIELD
END_RECORD
!------------------------------------------------------------------------------
!
! RELATION DECLARATION
!
!------------------------------------------------------------------------------
RELATION plan_windows
TYPE PLAN_WIN_TYPE
DESCRIPTION "Long Range Plan Windows Relation"
SUBSYSTEM_USING "SPSS", "SPIKE", "REPLICATION-TO-SOGS", "TRANS", "CCLIST"
RELATED_FIELDS "constraint_windows.*" "constraint_windows_ver.*" "lrp_base_cat.*"
INDEX plan_windows_1
TYPE unique, clustered
FIELDS sunit_id, version_num, lrp_name, window_begin
END_INDEX
END_RELATION
!------------------------------------------------------------------------------
!
! INSTANCE DECLARATION
!
!------------------------------------------------------------------------------
INSTANCE plan_windows
TYPE PLAN_WIN_TYPE
END_INSTANCE
Go to the top.