Organizing Component Requirements Across Project Releases
A project that releases components in phases needs each phase defined. Quantities held for later are a conversation, not an assumption.
Large projects rarely want every component at once. A building is released in packages, and a phased order has to be organized so that each release is quoted and built against something definite.
Release, not remainder
The useful unit is a release with its own scope: this many of this part, to this revision, needed on this date, to this location. A schedule that says half now and the rest later leaves the second half undefined, which means it cannot be quoted or planned.
Write each release as if it were a separate order, even when one drawing set covers all of them.
What has to stay fixed between releases
- The part, at the revision being used. If a revision changes between releases, say so, because the second release is then a different part.
- The finish. A phase one delivery in one colour and a phase two delivery in another is a real outcome of leaving this open.
- The quantity basis, so a release of forty and a release of sixty makes sense against an overall schedule.
Quantities and what they imply
Say the total and the split. If the split is not settled, give the totals and the likely phases with a confidence level, the same way a forecast is described for repeat work. What KorFab does not do is hold finished components in storage awaiting a later release, or commit to scheduled releases and delivery arrangements in advance. Each release is reviewed when it comes.
That is worth knowing early, because it changes how a phased project is planned: components arrive close to when they are needed rather than manufactured in one run and stored.
Delivery destinations
A phased release often means several destinations rather than several dates. Say where each release goes. KorFab delivers locally, statewide and by freight, and can deliver to multiple project locations, with the planning depending on dimensions, weight and destinations.
The revision trap
The most expensive phasing problem is not quantity. It is a revision that lands between release one and release two: the first release is built, the change is approved, and the second release no longer matches the first. If a revision is likely, flag it before release one is cut, because that is the point where the two can still be reconciled.
Where this fits
Planning fabricated components for a commercial build covers the package definition that sits above the release schedule. This article covers what to do once the package is split into phases.