FIDIC bo'yicha Concurrent Delay: time but no money prinsipi

Concurrent delay - delay claims ichidagi eng nozik mavzulardan biri. U Employer riskiga kiruvchi delay va Contractor riskiga kiruvchi delay bir davrda completionga ta’sir qilganda paydo bo’ladi.

Amaliy natija ko’pincha time but no money deb aytiladi. Contractor delay damagesdan himoyalanish uchun EOT olishi mumkin, lekin shu davr uchun prolongation costs olmasligi mumkin.

Bu universal mexanik qoida emas. Contract, Particular Conditions va facts asosida ehtiyotkor tahlil kerak.

Haqiqiy concurrent delay nima

Har bir “bir vaqtdagi muammo” concurrent delay emas.

Odatda kerak bo’ladigan elementlar:

• ikki yoki undan ortiq independent events;
• turli risk owners;
• completion date yoki critical pathga ta’sir;
• ta’sir davrlarining overlap bo’lishi;
• bitta event boshqasini yutib yuborganini aytish qiyinligi.

Employer event va contractor issue bir oyda bo’lgan bo’lsa ham, agar critical pathga faqat bittasi ta’sir qilgan bo’lsa, bu concurrency bo’lmasligi mumkin.

Nega pul qismi qiyin

EOT Contractorni late completion liabilitydan himoya qiladi. Money claim esa alohida asos talab qiladi.

Agar Contractor ham shu davrda critical pathni kechiktirgan bo’lsa, Employer shunday deydi: “Bizning event bo’lmasa ham, siz baribir o’z vaqtida tugatmas edingiz.” Shu yerda time but no money tijoriy ahamiyatga ega.

Natija:

• EOT berilishi mumkin;
• delay damages olib tashlanishi yoki kamayishi mumkin;
• prolongation costs rad etilishi yoki qisqartirilishi mumkin.

FIDIC 2017 va Particular Conditions

FIDIC 2017da concurrent delay Particular Conditions orqali tartibga solinishi mumkin. Shuning uchun faqat General Conditionsga qarab tahlil qilish xavfli.

Claimdan oldin tekshiring:

• concurrent delay clause bormi;
• critical delay qanday aniqlangan;
• apportionment ruxsat etilganmi;
• delay analysis method belgilanganmi;
• notices va particulars qanday yuboriladi;
• MDB yoki Employer-specific talablar bormi.

Particular Conditions jim bo’lsa, governing law, loyiha practice va SCL Protocol kabi guidance ko’riladi.

Qaysi metodlar yordam beradi

Concurrent delay uchun critical path vaqt bo’yicha qanday o’zgarganini ko’rsatadigan metod kerak:

• windows analysis;
• time impact analysis;
• as-planned vs as-built faqat yordamchi sifatida;
• contemporaneous programme updates;
• event-by-event critical path review.

Loyiha oxirida umumiy as-built chart chizib, “hamma hammani kechiktirdi” deyish causationni isbotlamaydi.

Records

Concurrent delayni contemporaneous programme recordsiz tahlil qilish juda qiyin.

Kerak:

• regular programme updates;
• har update uchun narrative;
• access, approvals, drawings, RFI logs;
• Contractor resources records;
• mobilisation, procurement, subcontractors evidence;
• resequencing decisions;
• mitigation correspondence.

Contractor o’z muammolarini ham halol yozishi kerak. Ularni yashirish analysis credibilitysini buzadi.

FAQ

Concurrent delay har doim time but no moneymi?

Yo’q. Bu keng tarqalgan amaliy natija, universal dogma emas. Contract, law va facts boshqa natija berishi mumkin.

Concurrent delayda pul olish mumkinmi?

Ba’zan mumkin: compensable delay ajratilsa, cost impact alohida isbotlansa yoki contractor delay o’sha windowda critical bo’lmasa.

Eng muhim narsa nima?

Sifatli programme updates va halol event-by-event explanation. Busiz analysis retrospective positionga aylanadi.

Bridge Consult concurrent delay bo’yicha delay submissions, Particular Conditions va recordsni Engineer, DAAB yoki arbitrationdan oldin tekshirishga yordam beradi.

Sources and further reading

• Society of Construction Law, Delay and Disruption Protocol, 2nd Edition, February 2017.
• FIDIC, Conditions of Contract for Construction, 2017 edition.
• Shuningdek qarang: EOT va delay analysis va Prolongation Costs.