Displaying Segment SchedulesSegment schedules are schedules that indicate when the assembly parts that are required for the work in a particular line segment must be delivered to the shop floor warehouse. For each segment on a line, a range of offline periods is defined. And for each period a date is scheduled on which the assembly parts are required. Therefore, every product variant whose requested offline date falls in one of these periods requires its assembly parts for the segment in question on that date. The advantage of these schedules is that the assembly part requirements can be determined right from the schedule, if only the requested offline date of the product variant and the segment of the assembly parts is known. Compare this to the following procedure, which you must use if no segment schedules are used:
Segment schedules are used for a rough planning of assembly part requirements, especially in the more distant future, that is, the period after the allocation time fence, but before the demand time fence. However, the schedules cover the whole period in the demand time fence, including the allocation time fence. Note To prevent that no date can be scheduled for product variants whose requested offline date falls before the first period of a segment, the Planned Offline Date From field of the first period of a segment is empty. As a result, the date scheduled of that period applies for all dates before the Planned Offline Date To. The fields in the current session must be read as follows:
Important! The Calculate Assembly Part Requirements (tiapl2221m000) session must use the most up-to-date schedule. Therefore, that session automatically updates the segments if a change is detected that affects the schedules. However, not all changes can be detected automatically. In some cases, the schedule must be updated manually, either through the Update command on the appropriate menu of the current session, or by selecting the Update Segment Schedules check box in the Calculate Assembly Part Requirements (tiapl2221m000) session. The schedules must be updated manually when:
| |||