Record the event the time window controls
Synthetic van leaves at 09:30, travels twenty minutes to A, serves A for fifteen, then travels twenty to B. B requires arrival from 10:00 inclusive to 10:30 exclusive. The planned B arrival is 10:25. Durations are invented planning inputs, not road conditions or an actual delivery promise.
| Constraint | Required record | Example decision rule |
|---|---|---|
| Route sequence | Start + travel A + service A + travel B | 09:30 + 20 + 15 + 20 = 10:25 |
| Window event | Arrival at B | Arrival must be before 10:30 |
| Service completion | Separate service-end time | Finish after 10:30 does not change arrival test |
Test arrival at and before the boundary
| Case | Input | Expected decision |
|---|---|---|
| B arrival 10:25 | Within [10:00,10:30) | Window met |
| B arrival 10:30 | Excluded end | Window not met |
- Read ordered stop sequence
- Add supplied durations
- Compare B arrival with window
- Keep actual arrival separate from forecast
Unknown travel time leaves the estimate incomplete; do not insert zero to make a window pass.
Service at A becomes twenty-five minutes. Does B still meet its window?
Show the worked answer
No. Arrival becomes 10:35, five minutes after the excluded 10:30 end.
The brief should name arrival versus service-end explicitly, and show both forecast and observed times in the demonstration.