What's different in project manufacturing
Unlike flow lines, complex equipment projects intertwine subcontract parts, test resources, and assembly steps. One power-plant auxiliary or packaged system may involve hundreds of subcontract items and multiple test windows—any slip can shift the entire critical path.
Traditional Gantt treats subcontract as notes or tribal knowledge—not hard constraints. Plans look fine until capacity is full or delivery windows misalign; then full replans.
Why subcontract becomes a blind spot
Subcontract info lives in procurement email, vendor replies, ERP attachments, and personal spreadsheets. Master planning watches assembly cadence; subcontract detail sits elsewhere—often out of sync.
Under delivery pressure, subcontract cascades surface in the final week: assembly waiting on parts, tests slip, shipment delays—little room left to adjust.
- Subcontract capacity by vendor/month—not just "delivery date";
- Subcontract ops hard-linked to in-house ops—they can't slide independently;
- Critical-path subcontract needs priority—not equal treatment.
Bind subcontract calendars to key operations
In COMPASS, subcontract capacity, delivery windows, and routing dependencies model together. Gantt drag surfaces conflicts; capacity views show vendor/month load—plans can't look feasible when supply isn't.
Critical-path highlighting focuses teams on what truly drives delivery. Visible subcontract windows let planning and procurement discuss alternate vendors, batch splits, or in-house sequence changes on one view.
- Subcontract windows aligned with assembly cadence—instant conflict hints;
- Gantt drag validates subcontract capacity occupancy;
- Changes sync back to planning tables.
Customer practice: power-plant auxiliary projects
One leading auxiliary customer tracked subcontract in Excel, separate from master Gantt. After COMPASS, vendor capacity entered capacity views; key subcontract ops linked to in-house assembly.
Typical wins: conflicts caught at scheduling time, not at receiving; planning/procurement meetings shift from "reconciling data" to "choosing options"; delay warnings often 3–5 business days earlier.
Less endless plan rework
When subcontract lives in the model—not email—planners and procurement share one reference. Changes can be versioned with clear "why we moved from A to B."
For project manufacturing, subcontract isn't an appendix to scheduling—it's part of the critical path. Modeling it in-system reduces rework and improves delivery control.
Takeaway
If project manufacturing keeps getting disrupted by subcontract slips, you may need subcontract windows inside the scheduling model—not just faster follow-up.
Contact us to learn COMPASS practices in complex equipment and subcontract-heavy scenarios.