The Schedule data area breaks down into the following detail data tables:
Figure 2: Schedule Data
Schedule - Data that represent specific Schedule rules such as Schedule settings, optimization parameters, business rules, routing parameters, bucket rules, etc. The Schedule data attributes typically represent the business perspective in a Schedule problem.
· A Route cannot exist without a Schedule.
· A Stop cannot exist without a Schedule.
· A bucket cannot exist without a Schedule.
· A Schedule can exist without a Route, Stop, bucket, or window.
· The Schedule receives its initial attributes from a corresponding (Schedule) supporting data element.
· The Schedule can only reference one corresponding (Schedule) supporting data element.
Route&emdash; Data that represent the equipment, personnel, availability, and rules needed to perform the work. The Route data attributes represent the physical perspective in a typical Schedule problem. A Route record is a link record between a specific Schedule and specific corresponding (resource) supporting data element.
· A Route can only belong to one Schedule.
· A Route can have many Stops associated with it.
· The Route can only reference one corresponding (resource) supporting data element.
· A Route will have different time and capacity constraints from its corresponding (resource) supporting data element.
Stop - Data that represent the work needed to be done at a specific location. The Stop data attributes represent the customer order perspective in a typical Schedule problem. A Stop record is a link record between a specific Schedule and specific corresponding supporting data element (activity).
· A Stop can only belong to one Schedule.
· The Stop can only reference one corresponding (activity) supporting data element.
· A Stop will have different time quantity constraints from its corresponding (activity) supporting data element.
Bucket - Data that represent the time-related business rules associated with the availability and user presentation of when the work can be performed.
· The bucket data are optional and only used when the Schedule is used to perform reservation type functionality.
· A bucket must belong to only one Schedule.
