Åpne demo
Caser / Planlegging og styring
Planlegging og styring

Protect the programme from a long-lead item

Stop a long-lead item stalling the job: find the items whose delivery beats the programme, tie their order dates to the schedule, and report the exposure that is left.

3 trinn9 minHovedentreprenørProsjekt- / byggeleder

Slik fungerer det, steg for steg

3 trinn gjennom plattformen - hva du gjør i hvert og hvorfor det betyr noe.

1

Find the long-lead items

Innkjøp

Go through the procurement schedule for the items whose lead time is long against the programme, from switchgear to bespoke facades, and note the date each is actually needed on site.

Hvorfor: A long-lead item nobody flagged is the one that stops a trade dead. Finding them early is what gives you the weeks you need to order in time instead of expediting at a premium later.

InndataProcurement scheduleSupplier lead timesResultatLong-lead item listRequired-on-site dates
2

Tie order dates to the programme

Avansert tidsplan

Work back from each required-on-site date through the lead time to the date the order must be placed, and set those order-by dates as milestones on the programme the team works to.

Hvorfor: A required-on-site date on its own does not tell procurement when to buy. Backing the lead time onto the programme is what turns a delivery need into an order-by milestone somebody is accountable for.

InndataLong-lead item listBaseline programmeResultatOrder-by datesProcurement milestones
3

Report the remaining exposure

Rapporter

Report which long-lead items are ordered against plan and which order-by dates are slipping, so the items still at risk to the programme are visible to the team at every review.

Hvorfor: A procurement risk you cannot see is one you manage by luck. Reporting the exposure keeps the slipping items in front of the people who can expedite them before they become a delay on site.

InndataOrder-by datesCurrent procurement statusResultatExposure reportAt-risk items

Mer innen Planlegging og styring