Why a Dependent-Parallel Child Is Exempt From the Over-Booked Check

In EDGEBIC by User Solutions, mirrored dependent-parallel load is deliberately excluded from the over-booked capacity check. Three synchronized drills each booked eight hours on the same day put twenty-four hours of allocation on a machine whose calendar opens for eight, and that is not a fault. It is what the plant does.

This is one of the few places where a scheduling report is asked to not flag something that arithmetic says is out of bounds, and the reasoning is worth understanding because it explains what an exception report is actually for.

What Dependent-Parallel Means

A dependent-parallel operation runs on several machines at once, locked together. The parent schedule is mirrored onto each dependent work center, every mirror runs in the same window as the parent, and each carries its own allocation hours against its own machine.

That is the point of the configuration. A weld cell where three heads must run simultaneously on one frame is not three independent operations that happen to overlap. It is one operation occupying three machines, and the schedule has to say so on all three.

The mechanics are in how dependent-parallel mirroring locks machines together, and the choice between the two parallel modes is in dependent versus independent parallel.

Why It Looks Like an Over-Book

Capacity checking is straightforward: sum the hours booked on a machine for a day, compare against what the calendar opens for, and flag the excess.

Run that over a synchronized cell and the arithmetic is unambiguous. Eight hours on the parent, eight on each of two mirrors, twenty-four total, against a calendar that opens for eight. Sixteen hours over.

Every one of those numbers is correct. The conclusion drawn from them would be wrong, because the three bookings do not compete for the same eight hours. They are the same eight hours, expressed on three machines.

The Failure Mode That Forced the Exemption

Now consider what a report that flagged it would look like in practice.

Every synchronized multi-machine operation would produce a capacity violation. Every day one runs. Forever. There would be no configuration change that clears it, because the load is contractual: the engine is supposed to book those hours on those machines.

An exception report that carries a permanent red count nobody can clear stops being an exception report. Planners learn that the over-booked chip is noise, they stop clicking it, and the day a genuine over-book appears it is invisible inside the false ones.

That is the worst available outcome for a checklist. The value of a parameter is entirely in the fact that a hit means something, and a check that cries wolf on ordinary operations has traded its only asset for arithmetic purity.

Two Loads, One Day

The resolution is not to hide the hours. It is to keep two figures for the same bucket and use them for different questions.

So a three-way mirror on an eight hour day reads as twenty-four hours assigned, three hundred percent utilized, zero hours over, and classifies as a heavily loaded day rather than a breach.

The planner sees the real load and the real intensity. What the report refuses to do is call it a violation.

Exposure, Not Suppression

That distinction matters, because "exempt" reads like "hidden" and it is not.

A genuinely over-committed synchronized machine still surfaces on the capacity grid. It surfaces as a loaded day carrying an eye-watering utilization figure, which is exactly the signal a planner can act on. Nothing is dropped from the grid and no hours vanish from any total.

Only the word changes, and only for the load whose over-capacity shape was designed in.

The same discipline appears elsewhere in the plan's health checks: mirrored allocations are excluded from the hard capacity gate in the anomaly report for the same reason, which is that flagging them there would mask real bypasses inside false alarms. See how the anomaly report keeps a bad schedule off the floor.

What Is Still Judged Normally

The exemption is narrow, and it is worth being precise about its edges.

Only mirrored load is exempt. If that same machine also carries an unrelated single-machine job on the same day, those hours are judged normally and can absolutely produce a violation.

Both sides of the mirror are exempt. A schedule qualifies when its routing step carries an active dependent alternative whose parent or alternative work center matches the schedule's own machine. The parent's own allocation belongs to the same synchronized burst, so exempting only the copies would leave the originating machine flagged for hours it had no choice about.

Independent parallel is not exempt. Independent parallel splits a job across machines that each do a share of the work, so their hours genuinely compete for capacity and a breach there is a real breach. See how independent parallel splits a job across machines.

Every other parameter still applies. A synchronized job can be late, behind pace, carrying anomalies, out of sequence, or short of material like any other. The exemption touches one check.

Reading a Synchronized Day

Practical guidance when a mirrored cell shows up in the capacity grid.

Do not read the utilization percentage as a warning on its own. Anything above one hundred percent on a machine that runs synchronized work is expected and describes the mirroring, not a problem.

Do read the day's job list. The hidden column listing which jobs are booked on the bucket is how you tell mirrored load from unrelated work sharing the same machine on the same day. The second kind is what can genuinely over-book it.

Do not raise the calendar capacity to make the number look tidy. Inflating a machine's calendar to absorb its mirrors means it will fail to flag a real over-book on every day no mirror runs, and it corrupts utilization reporting for the rest of the year. Fix the judgment, not the calendar. If capacity genuinely needs to move for a specific day, daily capacity overrides are the correct instrument and they are a different conversation.

The Bottom Line

An exception report earns its place by being right about what counts as an exception. Mirrored dependent-parallel hours are over capacity by arithmetic and correct by design, so they are shown in full, counted toward utilization, and excluded from the breach verdict. The result is a capacity chip that stays green until something is actually wrong, which is the only condition under which anyone keeps clicking it.

For the report itself see the Schedule Reconciliation report explained, and for the wider loop, the shop floor execution guide or the platform at EDGEBIC.