My Transit Days Used Calendar Days Instead of Working Days

A transit set to working-day mode that quietly counts calendar days has lost the work center it needs to read a working calendar: the routing step's work center is missing, inactive, or deleted. Without an active work center, the engine cannot tell which days are working days, so it silently falls back to calendar-day arithmetic, and the transit spans weekends and holidays it should skip. Reactivating or reassigning the step's work center and re-running scheduling restores working-day counting.

EDGEBIC by User Solutions lets a routing step add transit time between operations in one of two modes: calendar days, which count every day, or working days, which count only working days. Working-day mode needs an active work center to supply the calendar. This post, part of the EDGEBIC troubleshooting guide, explains the silent fallback and how to fix it.

Calendar Days Versus Working Days

Transit adds a delay between two steps, useful for moving work between plants or letting material ship. It runs in one of two modes:

• Calendar days count every day, so three calendar days from a Friday lands on Monday.
• Working days count only working days, so three working days from a Friday skips the weekend and lands later.

Working-day mode has to know which days are working days, and it gets that from the routing step's work center. When that work center is present and active, the transit counts working days correctly. When it is missing or inactive, the engine has no calendar to read, so it silently drops to calendar-day arithmetic. The transit still happens; it just counts the wrong days and lands sooner on the calendar than a working-day count would, which usually means the arrival is off from what you planned.

How to Tell

The tell is a transit that overshoots or lands across a weekend it should have skipped, on a step set to working-day mode. The anomaly report flags a working-day transit whose work center is missing, inactive, or deleted, naming the routing step. A useful comparison: if most routings honor their working-day transit and one does not, the odd one out almost always has a step whose work center is gone, since calendar mode needs no work center and would not show the difference.

This is a separate story from queue time and flow time fighting each other; transit is its own inter-step delay with its own mode setting.

The Fix

Restore the working calendar by giving the step a live work center:

1. Open the routing and find the step flagged for working-day transit with a missing work center.
2. If the work center was deactivated or deleted by mistake, reactivate or restore it so it exists and is active again.
3. If the machine is genuinely gone, reassign the step to an active work center that supplies the right working calendar.
4. Re-run scheduling for the affected job.

With an active work center in place, the engine reads its working calendar and the transit counts working days as intended, tightening the arrival back to the date you planned. See how to add transit days between two steps for where the mode and value live, and how queue and transit times work for how transit composes with the rest of the timing.

Confirming the Fix

After reactivating or reassigning the work center and re-running scheduling, re-open the anomaly report and confirm the transit chip returns zero rows. On the Gantt, the downstream step should now start on the working-day count you intended, skipping weekends and holidays rather than spanning them.

Prevention

• Keep transit steps on live work centers. Any routing step that uses working-day transit depends on its work center staying active. Before deactivating a machine, check whether any working-day transit relies on it.
• Deactivate rather than delete. A deactivated work center still supplies enough to keep references clean; a deleted one removes the calendar the transit needs. Prefer deactivation for machines with routing history.
• Choose the mode deliberately. Decide calendar days or working days for each transit on purpose. Calendar mode needs no work center and never hits this fallback, so it can be the safer choice when the delay is a pure ship time that should count weekends anyway.
• Audit after imports. If routings or work centers sync from your ERP and a machine is dropped or deactivated in the source, a scheduling pass and an anomaly-report read catch a transit that quietly reverted to calendar days.