--- name: claims-engineering description: Construction claims & delay analysis engine. Performs windows delay analysis (as-planned vs as-built), Extension of Time (EOT) entitlement narratives, disruption / loss-of-productivity claims (measured mile), FIDIC clause mapping, evidence/contemporaneous-records matrix and claim chronology. Use when a user asks about delay analysis, EOT, extension of time, disruption claim, prolongation, FIDIC clauses, concurrent delay, windows analysis, time impact, or building a claim narrative. ---

⚖️ claims-engineering — هندسة المطالبات وتحليل التأخير

> بديل داخلي يجمع: P6/XER delay analysis + EOT narratives + disruption + FIDIC clause mapping + evidence matrix. > يستفيد من p6-ai-planner (CPM/windows) و legal-advisor (FIDIC) و OCR للأدلة.

---

🎯 القدرات

1. Windows delay analysis — تقسيم المدة لنوافذ زمنية ومقارنة as-planned vs as-built لقياس أثر كل حدث على الحرج (critical path). 2. EOT entitlement — حساب الاستحقاق الزمني + تصنيف (excusable/compensable/concurrent). 3. Disruption (measured mile) — قياس فقد الإنتاجية بمقارنة فترة غير متأثرة بفترة متأثرة. 4. FIDIC clause mapping — ربط الحدث ببنود FIDIC المناسبة (1999/2017 Red Book). 5. Evidence matrix — مصفوفة الأدلة المعاصرة (notices, RFIs, site records, correspondence). 6. Chronology — جدول زمني للأحداث الرئيسية.

---

📚 المعرفة المرجعية (FIDIC + delay methods)

طرق تحليل التأخير المعتمدة (SCL Protocol)

1. Impacted As-Planned       (prospective, simplest, weakest evidentially)
2. Time Impact Analysis (TIA) (prospective, window-by-window, strong)
3. Time Slice Windows         (retrospective, recommended for complex)
4. As-Planned vs As-Built     (retrospective, factual)
5. Collapsed As-Built (but-for)(retrospective)

بنود FIDIC الشائعة (Red Book 1999 / 2017)

8.4  / 8.5   : Extension of Time for Completion
20.1 / 20.2  : Contractor's Claims (notice within 28 days)
1.9          : Delayed Drawings/Instructions
2.1          : Right of Access to Site
4.12 / 4.24  : Unforeseeable conditions / fossils
13.x         : Variations & Adjustments
8.9 / 8.10   : Suspension consequences
19 (1999)/18 (2017): Force Majeure / Exceptional Events

تصنيف التأخير

Excusable + Compensable   : Employer risk events -> EOT + cost (prolongation)
Excusable, non-Compensable: Neutral events (e.g. exceptional weather) -> EOT only
Non-Excusable             : Contractor risk -> no EOT, possibly LD liability
Concurrent                : two+ delays overlap -> apportionment / dominant cause

---

🛠️ السكربت

scripts/claims.py

الأوامر

bash
1) Windows delay analysis (as-planned vs as-built events)
python3 scripts/claims.py windows --input delay.json
2) EOT entitlement summary
python3 scripts/claims.py eot --input delay.json
3) Disruption / measured mile
python3 scripts/claims.py disruption --baseline-rate 1.0 --impacted-rate 0.65 --units 5000
4) FIDIC clause mapping for an event type
python3 scripts/claims.py fidic --event "differing site conditions"
5) Demo (built-in dataset)
python3 scripts/claims.py demo
python3 scripts/claims.py --help

صيغة delay.json

json
{
  "planned_completion": 400,
  "events": [
    {"id":"E1","desc":"Late access to site","window":"0-30","delay_days":15,
     "category":"compensable","critical":true,"fidic":"2.1"},
    {"id":"E2","desc":"Exceptional rainfall","window":"60-90","delay_days":8,
     "category":"excusable","critical":true,"fidic":"8.4"},
    {"id":"E3","desc":"Contractor rework","window":"90-120","delay_days":10,
     "category":"non-excusable","critical":false}
  ]
}

📐 معادلات (داخل code blocks — لا LaTeX)

Measured-mile productivity loss:
  lost_units      = impacted_units  (1 - impacted_rate / baseline_rate)
  loss_pct        = (1 - impacted_rate / baseline_rate)  100
Net EOT (critical only, excusable):
  EOT = sum(delay_days for events if critical and category in {compensable, excusable})
  (concurrent overlaps apportioned separately)

⚠️ قواعد

• لا تدّعِ استحقاقاً بدون أثر على الحرج (critical path) — التأخير غير الحرج لا يستحق EOT.
• وثّق دائماً: notice date + contemporaneous records + cause-effect link.
• التأخير المتزامن (concurrent) يتطلب تحليل dominant cause / apportionment — لا تخلطه.
• هذا أداة هندسية تحليلية، ليست رأياً قانونياً نهائياً — للقانون راجع legal-advisor.