デモを開く
ケース / 計画と管理
計画と管理

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ステップ9 分総合建設会社プロジェクト / 施工管理者

仕組みをステップごとに

プラットフォーム全体で3ステップ - 各ステップで何をするか、そしてなぜ重要か。

1

Find the long-lead items

調達

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.

理由: 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.

入力Procurement scheduleSupplier lead times出力Long-lead item listRequired-on-site dates
2

Tie order dates to the programme

高度なスケジュール

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.

理由: 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.

入力Long-lead item listBaseline programme出力Order-by datesProcurement milestones
3

Report the remaining exposure

レポート

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.

理由: 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.

入力Order-by datesCurrent procurement status出力Exposure reportAt-risk items

計画と管理の他のケース