Three teams just found out they need the same engineer next quarter.

Each project plans its resources in isolation, and each plan is reasonable on its own. Bioreactor Hall 2 needs the senior automation engineer in Q3. So does the MES rollout. So does the filling-line qualification. Nobody is wrong — there's just one of her, and three projects quietly assumed they had her.

You find out the way these things are always found out: late, in a planning meeting, when the dates are already committed and the only options left are bad ones. The collision was knowable months earlier. It just lived in three separate spreadsheets that never looked at each other.

How STRUCTURA handles it

STRUCTURA's forecast runs across the whole portfolio at once, not project by project. It rolls demand up by role and by period, so demand-versus-capacity conflicts surface as a shape on a chart — the quarter where Project Engineer demand spikes past what the team can supply — instead of as a surprise in a meeting.

The part that earns its keep: you can forecast hypothetical projects too. Before you commit to starting something, drop it into the forecast and see what it does to the resource picture — the collision shows up while it's still a question, not after it's a commitment. Lock a round as a baseline, model a scenario beside it, and compare the two side by side: what if this one slips? what if we start that one now?

And because it's reading the same live data, Coach John can call the conflict out in the role-targeted summary — “automation capacity is over-committed in Q3 across three projects” — and propose where to move, for a human to accept or reject. The contention stops hiding between plans.

What changes

The same engineer is still in demand three times over — that's real, and no tool conjures a fourth of her. What changes is when you know. The collision moves from “discovered in Q3” to “visible the moment the third project was penciled in,” while re-sequencing still costs a conversation instead of a crisis.