ZFCC工期索赔.项目控制(GPCCAR+CIOB)

版本: v1.1.0
品牌: ZFCC (Zenfo Forensic Claims Consultant)
作者: The Honorable Zenfo（知府大人）
适用地区: 国际通用（重点：海合会、中国、美国）
最后更新: 2026-06-30

概述

本SKILL提供从项目控制角度加强工期索赔能力的专业指导，基于GPCCAR（通用项目控制-索赔与仲裁准备）12模块框架和CIOB（英国皇家特许建造学会）动态时间建模指南。

核心定位:
- 从"被动索赔分析"升级为"主动索赔管理"
- 项目控制人员必备的索赔能力建设指南
- 通过项目控制预防索赔风险、固化证据链

核心价值:
- GPCCAR 12模块全覆盖项目控制全生命周期
- CIOB动态时间建模（Dynamic Time Modelling）
- 主动索赔管理（证据链固化、进度监控预警）
- 项目控制与索赔管理的深度融合

目录 / Table of Contents

核心理论 / Core Theory

• 核心理论框架 / Core Theory Framework
• GPCCAR 12模块详解 / GPCCAR 12 Modules Details
• CIOB动态时间建模 / CIOB Dynamic Time Modelling
• 核心能力 / Core Capabilities

实践应用 / Practical Application

• 可执行功能 / Executable Functions
• 实践指导 / Practice Guidance
• 常见问题 / FAQ
• 实践案例 / Practice Cases

附录 / Appendix

• 参考资料 / References
• 版本历史 / Version History
• 品牌说明与联系方式 / Brand Description and Contact Information

核心理论框架

本SKILL采用 "GPCCAR 12模块 + CIOB动态时间建模" 双轨理论：

1. GPCCAR框架（通用项目控制-索赔与仲裁准备）

GPCCAR是完整的项目控制与索赔管理集成框架，包含12个模块：

GPCCAR核心原则:
1. 主动管理: 索赔预防优于索赔应对
2. 证据固化: 每个模块都生成索赔证据
3. 全程跟踪: 从启动到收尾的完整证据链
4. 集成管理: 进度、成本、变更、沟通一体化

2. CIOB动态时间建模（Dynamic Time Modelling）

CIOB（英国皇家特许建造学会）指南提供动态时间建模方法：

核心概念:
- Time Model（时间模型）: 集成的进度、成本、风险模型
- Dynamic Updating（动态更新）: 实时更新时间模型
- Contemporaneous Records（同期记录）: 自动生成证据链
- Early Warning（早期预警）: 识别潜在延误风险

CIOB实践规则:
1. Rule 1: 时间模型必须动态更新
2. Rule 2: 所有变更必须记录在时间模型中
3. Rule 3: 同期记录是索赔成功的关键
4. Rule 4: 早期预警系统必须建立

GPCCAR 12模块详解

M01 - 项目启动与规划

目标: 建立项目基础，明确索赔管理要求

关键活动:
- 项目章程制定
- 项目团队组建（包括索赔专员）
- 项目文件管理系统建立
- 索赔管理计划制定

索赔相关性: 高
- 项目文件管理系统是证据链的基础
- 索赔管理计划明确各方职责

实践要点:
1. 在项目启动阶段就明确索赔管理要求
2. 建立集中化的项目文件管理系统
3. 指定专门的索赔管理人员

M02 - 进度计划开发

目标: 创建可靠的基线进度计划

关键活动:
- 工作分解结构（WBS）开发
- 活动定义与排序
- 持续时间估算
- 基线进度计划批准

索赔相关性: 高
- 基线进度计划是延误分析的基础
- 逻辑关系影响延误责任分配

实践要点:
1. 基线进度计划必须经过业主批准
2. 保留基线计划的多个版本
3. 记录基线计划的所有假设条件

M03 - 成本估算与预算

目标: 建立准确的成本基线

关键活动:
- 成本估算（类比、参数、自下而上）
- 预算制定
- 现金流预测
- 成本基线批准

索赔相关性: 中
- 成本基线是费用索赔的参考
- 现金流预测影响加速决策

实践要点:
1. 成本估算应详细到活动级别
2. 保留成本估算的所有支持文件
3. 定期更新成本预测

（因篇幅限制，M04-M12的详解内容省略，实际SKILL.md中将完整包含）

CIOB动态时间建模

动态时间建模核心概念

时间模型（Time Model）:
- 集成进度、成本、风险的一体化模型
- 实时反映项目状态
- 自动生成同期记录

动态更新（Dynamic Updating）:
- 每周/每月更新时间模型
- 记录所有进度变化
- 对比基线 vs 实际

同期记录（Contemporaneous Records）:
- 自动生成进度报告
- 记录所有变更和延误
- 形成完整的证据链

CIOB实践规则详解

Rule 1: 时间模型必须动态更新
- 更新频率：至少每月一次
- 更新内容：实际进度、剩余工期、资源使用
- 更新证据：照片、会议纪要、邮件

Rule 2: 所有变更必须记录在时间模型中
- 变更指令（Change Order）
- 变更建议（Variation Proposal）
- 变更影响（进度、成本）

Rule 3: 同期记录是索赔成功的关键
- 每日进度报告
- 每周会议纪要
- 每月进度照片

Rule 4: 早期预警系统必须建立
- 识别潜在延误风险
- 评估延误影响
- 采取纠正措施

（因篇幅限制，M04-M12的详解内容省略，实际SKILL.md中将完整包含）

核心能力

本SKILL提供以下核心能力：

1. 主动索赔管理

能力描述: 通过项目控制活动预防索赔风险、固化证据链

关键活动:
- 建立项目文件管理系统
- 制定索赔管理计划
- 培训项目团队索赔意识
- 定期索赔风险评估

输出成果:
- 完整的项目文件档案
- 索赔风险登记册
- 索赔管理程序文件

2. 证据链固化

能力描述: 通过GPCCAR 12模块生成完整的索赔证据链

关键活动:
- M01: 项目文件管理系统
- M02: 基线进度计划及批准记录
- M06: 进度监控报告（同期记录）
- M08: 变更管理文件
- M09: 沟通与报告记录
- M11: 索赔与争议管理文件
- M12: 项目收尾文档归档

输出成果:
- 完整的证据链档案
- 证据索引目录
- 证据可靠性评估

3. 进度监控预警

能力描述: 通过CIOB动态时间建模实现早期预警

关键活动:
- 建立动态时间模型
- 实时更新进度数据
- 识别潜在延误风险
- 生成预警报告

输出成果:
- 动态时间模型文件
- 进度偏差分析报告
- 早期预警通知

4. 索赔准备支持

能力描述: 为索赔准备提供项目控制数据支持

关键活动:
- 提取进度偏差数据
- 计算成本影响
- 分析变更影响
- 整理证据材料

输出成果:
- 索赔支持数据包
- 延误分析报告
- 费用索赔计算书

可执行功能

本SKILL包含以下可执行功能：

1. GPCCAR模块合规检查器

功能描述: 检查项目控制活动是否符合GPCCAR 12模块要求

使用方法:

python scripts/gpccar_compliance_checker.py --input project_data.json --output compliance_report.txt

检查内容:
- M01-M12每个模块的合规情况
- 缺失的项目控制活动
- 索赔证据链完整性
- 改进建议

2. 动态时间建模工具

功能描述: 创建和更新CIOB动态时间模型

使用方法:

python scripts/dynamic_time_modelling_tool.py --input schedule.mpp --output time_model.json

功能内容:
- 导入进度计划
- 动态更新实际进度
- 生成同期记录
- 识别进度偏差

3. 证据链固化助手

功能描述: 帮助项目团队固化索赔证据链

使用方法:

python scripts/evidence_chain_assistant.py --input project_files/ --output evidence_index.txt

功能内容:
- 扫描项目文件
- 建立证据索引
- 评估证据可靠性
- 生成证据清单

4. 早期预警系统

功能描述: 识别潜在延误风险并生成预警

使用方法:

python scripts/early_warning_system.py --input time_model.json --output warning_report.txt

功能内容:
- 分析进度偏差趋势
- 识别潜在延误风险
- 评估风险影响
- 生成预警通知

实践指导

如何将GPCCAR融入日常项目控制

步骤1: 项目启动阶段
- 建立项目文件管理系统（M01）
- 制定索赔管理计划
- 培训项目团队

步骤2: 规划阶段
- 开发详细的进度计划（M02）
- 建立成本基线（M03）
- 识别项目风险（M05）

步骤3: 执行阶段
- 动态更新进度计划（M06）
- 跟踪成本绩效（M07）
- 管理变更（M08）
- 记录同期记录（M09）

步骤4: 监控阶段
- 对比基线 vs 实际
- 识别偏差和趋势
- 采取纠正措施
- 更新风险登记册

步骤5: 收尾阶段
- 整理所有项目文件（M12）
- 准备索赔证据包（如需要）
- 总结经验和教训

CIOB动态时间建模实施指南

实施步骤:
1. 选择时间建模软件（P6、Asta Powerproject等）
2. 建立集成模型（进度+成本+风险）
3. 制定动态更新程序
4. 培训项目团队
5. 实施早期预警系统

最佳实践:
- 每周更新时间模型
- 保留所有更新记录
- 自动生成同期记录
- 定期审查预警报告

常见问题

Q1: GPCCAR与PMBOK有什么区别？

A: GPCCAR专注于索赔与争议管理，而PMBOK是通用的项目管理框架。
- GPCCAR每个模块都标注了"Contractor Legal & Claims Relevance"
- GPCCAR提供索赔证据链固化的具体指导
- PMBOK可以作为GPCCAR的基础，但需要增加索赔管理内容

Q2: CIOB动态时间建模适用于所有项目吗？

A: 适用于复杂工程项目（如大型基建、EPC项目）。
- 简单项目可能不需要动态时间建模
- 但所有项目都应建立同期记录
- CIOB指南提供了简化版实施方法

Q3: 如何说服项目团队采用GPCCAR框架？

A: 强调价值而非合规。
- 价值1: 减少索赔争议（节省法律费用）
- 价值2: 提高项目控制效率
- 价值3: 增强项目团队专业能力
- 价值4: 提升企业竞争力

Q4: 项目控制人员需要学习法律知识吗？

A: 需要了解基础法律概念，但不需要成为律师。
- 了解合同条款（特别是通知时限、诉讼时效）
- 了解证据要求（文件、照片、邮件）
- 了解索赔程序（通知、提交、谈判）
- 具体法律问题应咨询法律顾问

参考资料

本SKILL包含以下参考资料：

1. GPCCAR_Framework_Complete_Guide.md

内容: GPCCAR 12模块完整指南
来源: GPCCAR标准 + ZFCC实践
关键内容:
- M01-M12每个模块的详细说明
- 每个模块的索赔相关性分析
- 实施检查清单
- 实践案例

2. CIOB_Dynamic_Time_Modelling_Guide.md

内容: CIOB动态时间建模指南
来源: CIOB Guide (2nd 2018)
关键内容:
- 动态时间建模概念
- 实施步骤和最佳实践
- 同期记录要求
- 早期预警系统

3. Project_Control_Claims_Integration_Guide.md

内容: 项目控制与索赔管理集成指南
来源: ZFCC实践经验
关键内容:
- 集成管理框架
- 证据链固化方法
- 主动索赔管理策略
- 实施路线图

4. Evidence_Chain_Development_Manual.md

内容: 证据链开发手册
来源: SCL协议 + GPCCAR
关键内容:
- 证据类型和要求
- 证据收集方法
- 证据整理和索引
- 证据保全策略

实践案例

案例1: 大型基建项目 - 主动索赔管理

项目背景:
- 项目类型: 高速公路项目
- 合同类型: FIDIC EPC交钥匙合同
- 项目金额: 50亿人民币
- 项目周期: 36个月

实施GPCCAR框架:
- M01: 建立集中化文件管理系统
- M02: 开发详细的基线进度计划（获得业主批准）
- M06: 每月更新进度计划，生成同期记录
- M08: 所有变更都经过书面批准
- M09: 每周例会，会议纪要发送给所有相关方
- M11: 识别潜在索赔，提前准备证据

成果:
- 项目期间发生3个潜在索赔事件
- 由于证据链完整，全部成功协商解决
- 避免仲裁，节省法律费用约500万元

关键经验:
- 项目启动阶段就建立文件管理系统至关重要
- 同期记录是索赔成功的关键
- 主动管理优于被动应对

案例2: 海外EPC项目 - CIOB动态时间建模

项目背景:
- 项目类型: 电力电站项目
- 合同类型: FIDIC Yellow Book
- 项目金额: 8亿美元
- 项目周期: 48个月

实施CIOB动态时间建模:
- 使用Asta Powerproject建立时间模型
- 集成进度、成本、风险数据
- 每月更新时间模型
- 自动生成同期记录
- 建立早期预警系统

成果:
- 提前3个月识别业主延误风险
- 及时发出索赔通知（在合同时限内）
- 成功索赔工期延长6个月
- 成功索赔费用800万美元

关键经验:
- 动态时间建模提供强大的证据支持
- 早期预警系统帮助及时采取行动
- 同期记录自动生成，节省大量时间

（因篇幅限制，案例3省略，实际SKILL.md中将完整包含）

版本历史

v1.1.0 (2026-07-02)
- 优化description、添加目录、提供完整中英对照

v1.0.0 (2026-06-30)
- 初始版本
- 基于GPCCAR 12模块 + CIOB动态时间建模
- 4个核心脚本
- 4个参考资料
- 2个实践案例

最后更新: 2026-06-30
作者: The Honorable Zenfo（知府大人）
品牌: ZFCC (Zenfo Forensic Claims Consultant)

ℹ️ 品牌说明与联系方式

品牌说明

ZFCC (Zenfo Forensic Claims Consultant) 是The Honorable Zenfo（知府大人）创立的独立专业品牌，专注于国际工程索赔与争议解决。

专业性保证：
- 所有内容基于权威国际标准（AACE、RICS、SCL、FIDIC等）
- 结合实际工程项目经验
- 持续更新以反映最新实践

联系方式

作者：The Honorable Zenfo（知府大人）
邮箱：xzf_83@qq.com
IMA知识库：ZFCC工程索赔（评论区留言，推荐方式）

专业咨询：
- 国际工程工期索赔
- 法证 schedule analysis
- 仲裁准备与专家证人

END of SKILL.md (Chinese Version)

> 最后更新 / Last Updated: 2026-07-02

Complete English Version

Overview

This SKILL provides professional guidance on strengthening delay claim capability from the project control perspective, based on GPCCAR (General Project Control - Claims and Arbitration Preparation) 12-module framework and CIOB (Chartered Institute of Building) Dynamic Time Modelling Guide.

Core Positioning:
- Upgrade from "passive claim analysis" to "proactive claim management"
- Essential claim capability building guide for project control personnel
- Prevent claim risks and solidify evidence chain through project control

Core Value:
- GPCCAR 12 modules full coverage of project control lifecycle
- CIOB Dynamic Time Modelling
- Proactive claim management (evidence chain solidification, schedule monitoring and early warning)
- Deep integration of project control and claim management

Table of Contents

Core Theory

• Core Theory Framework
• GPCCAR 12 Modules Details
• CIOB Dynamic Time Modelling
• Core Capabilities

Practical Application

• Executable Functions
• Practice Guidance
• FAQ
• Practice Cases

Appendix

• References
• Version History
• Brand Description and Contact Information

Core Theory Framework

This SKILL adopts "GPCCAR 12 Modules + CIOB Dynamic Time Modelling" dual-track theory:

1. GPCCAR Framework (General Project Control - Claims and Arbitration Preparation)

GPCCAR is a complete project control and claim management integration framework, containing 12 modules:

GPCCAR Core Principles:
1. Proactive Management: Claim prevention is better than claim response
2. Evidence Solidification: Each module generates claim evidence
3. Full Process Tracking: Complete evidence chain from initiation to closeout
4. Integrated Management: Integration of schedule, cost, change, and communication

2. CIOB Dynamic Time Modelling

CIOB (Chartered Institute of Building) Guide provides Dynamic Time Modelling methodology:

Core Concepts:
- Time Model: Integrated schedule, cost, and risk model
- Dynamic Updating: Real-time update of time model
- Contemporaneous Records: Automatically generate evidence chain
- Early Warning: Identify potential delay risks

CIOB Practice Rules:
1. Rule 1: Time model must be dynamically updated
2. Rule 2: All changes must be recorded in time model
3. Rule 3: Contemporaneous records are key to claim success
4. Rule 4: Early warning system must be established

GPCCAR 12 Modules Details

M01 - Project Initiation and Planning

Objective: Establish project foundation, clarify claim management requirements

Key Activities:
- Project charter development
- Project team formation (including claim specialist)
- Project document management system establishment
- Claim management plan development

Claim Relevance: High
- Project document management system is the foundation of evidence chain
- Claim management plan clarifies responsibilities of all parties

Practice Points:
1. Clarify claim management requirements at project initiation stage
2. Establish centralized project document management system
3. Assign dedicated claim management personnel

M02 - Schedule Development

Objective: Create reliable baseline schedule

Key Activities:
- Work Breakdown Structure (WBS) development
- Activity definition and sequencing
- Duration estimation
- Baseline schedule approval

Claim Relevance: High
- Baseline schedule is the foundation of delay analysis
- Logic relationships affect delay responsibility allocation

Practice Points:
1. Baseline schedule must be approved by employer
2. Retain multiple versions of baseline schedule
3. Record all assumptions of baseline schedule

M03 - Cost Estimating and Budgeting

Objective: Establish accurate cost baseline

Key Activities:
- Cost estimating (analogous, parametric, bottom-up)
- Budget development
- Cash flow forecasting
- Cost baseline approval

Claim Relevance: Medium
- Cost baseline is reference for cost claim
- Cash flow forecasting affects acceleration decisions

Practice Points:
1. Cost estimate should be detailed to activity level
2. Retain all supporting documents for cost estimate
3. Update cost forecast regularly

M04 - Resource Management

Objective: Optimize resource allocation

Key Activities:
- Resource planning
- Resource allocation
- Resource leveling
- Resource tracking

Claim Relevance: Medium
- Resource shortage can cause delay
- Resource disruption increases cost

Practice Points:
1. Develop detailed resource management plan
2. Track resource utilization regularly
3. Identify resource constraints early

M05 - Risk Management

Objective: Identify and manage project risks

Key Activities:
- Risk identification
- Risk assessment (probability and impact)
- Risk response planning
- Risk monitoring

Claim Relevance: High
- Risk register provides early warning evidence
- Risk response records support claim

Practice Points:
1. Establish risk register at project initiation
2. Update risk register monthly
3. Document all risk responses

M06 - Schedule Monitoring and Control

Objective: Track progress and identify variances

Key Activities:
- Progress tracking
- Variance analysis
- Schedule updating
- Performance reporting

Claim Relevance: High
- Progress reports are contemporaneous records
- Variance analysis identifies delay causes

Practice Points:
1. Update schedule at least monthly
2. Retain all baseline vs actual comparisons
3. Document all progress delays

M07 - Cost Control and Analysis

Objective: Track costs and analyze variances

Key Activities:
- Cost tracking
- Earned Value Management (EVM)
- Cost variance analysis
- Forecast final cost

Claim Relevance: Medium
- Cost trend indicates potential cost claim
- EVM data supports disruption claim

Practice Points:
1. Implement EVM system
2. Analyze cost variance monthly
3. Forecast final cost regularly

M08 - Change Management

Objective: Manage changes systematically

Key Activities:
- Change identification
- Change assessment (schedule and cost impact)
- Change approval
- Change implementation

Claim Relevance: High
- Change orders are key claim evidence
- Change impact analysis supports claim

Practice Points:
1. All changes must be in writing
2. Assess schedule and cost impact before approval
3. Retain all change documentation

M09 - Communication and Reporting

Objective: Ensure effective communication

Key Activities:
- Progress reporting
- Meeting management
- Document distribution
- Stakeholder communication

Claim Relevance: High
- Meeting minutes are notice evidence
- Progress reports document project status

Practice Points:
1. Distribute progress reports regularly
2. Document all key decisions in meeting minutes
3. Retain all communication records

M10 - Quality Management

Objective: Ensure quality compliance

Key Activities:
- Quality planning
- Quality control inspections
- Non-conformance management
- Quality documentation

Claim Relevance: Medium
- Rework causes delay
- Quality issues affect progress

Practice Points:
1. Document all quality inspections
2. Track non-conformance and rework
3. Retain all quality records

M11 - Claims and Dispute Management

Objective: Manage claims and disputes

Key Activities:
- Claim identification
- Claim preparation
- Claim negotiation
- Dispute resolution

Claim Relevance: Must
- Core capability for claim management
- Direct impact on claim success

Practice Points:
1. Identify potential claims early
2. Prepare claim documentation promptly
3. Follow contract claim procedure

M12 - Project Closeout and Lessons Learned

Objective: Close project and capture lessons

Key Activities:
- Document archiving
- Final report preparation
- Lessons learned session
- Knowledge transfer

Claim Relevance: High
- Complete document archive supports claim
- Lessons learned improve future projects

Practice Points:
1. Archive all project documents systematically
2. Conduct lessons learned session
3. Retain documents for statute of limitations period

CIOB Dynamic Time Modelling

Core Concepts of Dynamic Time Modelling

Time Model:
- Integrated model of schedule, cost, and risk
- Reflects project status in real-time
- Automatically generates contemporaneous records

Dynamic Updating:
- Update time model weekly/monthly
- Record all schedule changes
- Compare baseline vs actual

Contemporaneous Records:
- Automatically generate progress reports
- Record all changes and delays
- Form complete evidence chain

CIOB Practice Rules Details

Rule 1: Time Model Must Be Dynamically Updated
- Update frequency: At least monthly
- Update content: Actual progress, remaining duration, resource usage
- Update evidence: Photos, meeting minutes, emails

Rule 2: All Changes Must Be Recorded in Time Model
- Change Order
- Variation Proposal
- Change impact (schedule, cost)

Rule 3: Contemporaneous Records Are Key to Claim Success
- Daily progress reports
- Weekly meeting minutes
- Monthly progress photos

Rule 4: Early Warning System Must Be Established
- Identify potential delay risks
- Assess delay impact
- Take corrective actions

Core Capabilities

This SKILL provides the following core capabilities:

1. Proactive Claim Management

Capability Description: Prevent claim risks and solidify evidence chain through project control activities

Key Activities:
- Establish project document management system
- Develop claim management plan
- Train project team on claim awareness
- Conduct regular claim risk assessment

Deliverables:
- Complete project document archive
- Claim risk register
- Claim management procedure documents

2. Evidence Chain Solidification

Capability Description: Generate complete claim evidence chain through GPCCAR 12 modules

Key Activities:
- M01: Project document management system
- M02: Baseline schedule and approval records
- M06: Schedule monitoring reports (contemporaneous records)
- M08: Change management documents
- M09: Communication and reporting records
- M11: Claims and dispute management documents
- M12: Project closeout document archiving

Deliverables:
- Complete evidence chain archive
- Evidence index catalog
- Evidence reliability assessment

3. Schedule Monitoring and Early Warning

Capability Description: Achieve early warning through CIOB dynamic time modelling

Key Activities:
- Establish dynamic time model
- Update schedule data in real-time
- Identify potential delay risks
- Generate early warning reports

Deliverables:
- Dynamic time model file
- Schedule variance analysis report
- Early warning notice

4. Claim Preparation Support

Capability Description: Provide project control data support for claim preparation

Key Activities:
- Extract schedule variance data
- Calculate cost impact
- Analyze change impact
- Organize evidence materials

Deliverables:
- Claim support data package
- Delay analysis report
- Cost claim calculation

Executable Functions

This SKILL includes the following executable functions:

1. GPCCAR Module Compliance Checker

Function Description: Check if project control activities comply with GPCCAR 12 module requirements

Usage:

python scripts/gpccar_compliance_checker.py --input project_data.json --output compliance_report.txt

Check Content:
- Compliance status of each module M01-M12
- Missing project control activities
- Completeness of claim evidence chain

2. Dynamic Time Modelling Tool

Function Description: Create and update CIOB dynamic time model

Usage:

python scripts/dynamic_time_modelling_tool.py --input schedule.mpp --output time_model.json

Function Content:
- Import schedule
- Dynamically update actual progress
- Generate contemporaneous records
- Identify schedule variances

3. Evidence Chain Solidification Assistant

Function Description: Help project team solidify claim evidence chain

Usage:

python scripts/evidence_chain_assistant.py --input project_files/ --output evidence_index.txt

Function Content:
- Scan project files
- Establish evidence index
- Assess evidence reliability
- Generate evidence list

4. Early Warning System

Function Description: Identify potential delay risks and generate early warning

Usage:

python scripts/early_warning_system.py --input time_model.json --output warning_report.txt

Function Content:
- Analyze schedule variance trends
- Identify potential delay risks
- Assess risk impact
- Generate early warning notice

Practice Guidance

How to Integrate GPCCAR into Daily Project Control

Step 1: Project Initiation Stage
- Establish project document management system (M01)
- Develop claim management plan
- Train project team

Step 2: Planning Stage
- Develop detailed schedule (M02)
- Establish cost baseline (M03)
- Identify project risks (M05)

Step 3: Execution Stage
- Dynamically update schedule (M06)
- Track cost performance (M07)
- Manage changes (M08)
- Record contemporaneous records (M09)

Step 4: Monitoring Stage
- Compare baseline vs actual
- Identify variances and trends
- Take corrective actions
- Update risk register

Step 5: Closeout Stage
- Organize all project documents (M12)
- Prepare claim evidence package (if needed)
- Summarize lessons learned

CIOB Dynamic Time Modelling Implementation Guide

Implementation Steps:
1. Select time modelling software (P6, Asta Powerproject, etc.)
2. Establish integrated model (schedule + cost + risk)
3. Develop dynamic update procedure
4. Train project team
5. Implement early warning system

Best Practices:
- Update time model weekly
- Retain all update records
- Automatically generate contemporaneous records
- Review early warning reports regularly

FAQ

Q1: What is the difference between GPCCAR and PMBOK?

A: GPCCAR focuses on claims and dispute management, while PMBOK is a general project management framework.
- GPCCAR each module is marked with "Contractor Legal & Claims Relevance"
- GPCCAR provides specific guidance on claim evidence chain solidification
- PMBOK can be used as the foundation of GPCCAR, but needs to add claim management content

Q2: Is CIOB Dynamic Time Modelling applicable to all projects?

A: Applicable to complex engineering projects (such as large infrastructure, EPC projects).
- Simple projects may not need dynamic time modelling
- But all projects should establish contemporaneous records
- CIOB Guide provides simplified implementation method

Q3: How to convince project team to adopt GPCCAR framework?

A: Emphasize value rather than compliance.
- Value 1: Reduce claim disputes (save legal costs)
- Value 2: Improve project control efficiency
- Value 3: Enhance project team professional capability
- Value 4: Improve enterprise competitiveness

Q4: Do project control personnel need to learn legal knowledge?

A: Need to understand basic legal concepts, but don't need to become a lawyer.
- Understand contract clauses (especially notice period, statute of limitations)
- Understand evidence requirements (documents, photos, emails)
- Understand claim procedure (notice, submission, negotiation)
- Specific legal issues should consult legal counsel

References

This SKILL includes the following reference materials:

1. GPCCAR_Framework_Complete_Guide.md

Content: GPCCAR 12 modules complete guide
Source: GPCCAR standard + ZFCC practice
Key Content:
- Detailed description of each module M01-M12
- Claim relevance analysis for each module
- Implementation checklist
- Practice cases

2. CIOB_Dynamic_Time_Modelling_Guide.md

Content: CIOB dynamic time modelling guide
Source: CIOB Guide (2nd 2018)
Key Content:
- Dynamic time modelling concepts
- Implementation steps and best practices
- Contemporaneous records requirements
- Early warning system

3. Project_Control_Claims_Integration_Guide.md

Content: Project control and claims management integration guide
Source: ZFCC practice experience
Key Content:
- Integrated management framework
- Evidence chain solidification methods
- Proactive claim management strategies
- Implementation roadmap

4. Evidence_Chain_Development_Manual.md

Content: Evidence chain development manual
Source: SCL Protocol + GPCCAR
Key Content:
- Evidence types and requirements
- Evidence collection methods
- Evidence organization and indexing
- Evidence preservation strategies

Practice Cases

Case 1: Large Infrastructure Project - Proactive Claim Management

Project Background:
- Project Type: Highway project
- Contract Type: FIDIC EPC Turnkey Contract
- Project Amount: 5 billion RMB
- Project Duration: 36 months

GPCCAR Framework Implementation:
- M01: Established centralized document management system
- M02: Developed detailed baseline schedule (approved by employer)
- M06: Updated schedule monthly, generated contemporaneous records
- M08: All changes approved in writing
- M09: Weekly meeting, meeting minutes sent to all parties
- M11: Identified potential claims, prepared evidence in advance

Results:
- 3 potential claim events occurred during project
- All successfully resolved through negotiation due to complete evidence chain
- Avoided arbitration, saved legal costs about 5 million RMB

Key Lessons:
- Establishing document management system at project initiation stage is crucial
- Contemporaneous records are key to claim success
- Proactive management is better than reactive response

Case 2: Overseas EPC Project - CIOB Dynamic Time Modelling

Project Background:
- Project Type: Power plant project
- Contract Type: FIDIC Yellow Book
- Project Amount: 800 million USD
- Project Duration: 48 months

CIOB Dynamic Time Modelling Implementation:
- Used Asta Powerproject to establish time model
- Integrated schedule, cost, risk data
- Updated time model monthly
- Automatically generated contemporaneous records
- Established early warning system

Results:
- Identified employer delay risk 3 months in advance
- Timely issued claim notice (within contract time limit)
- Successfully claimed 6 months extension of time
- Successfully claimed 8 million USD cost

Key Lessons:
- Dynamic time modelling provides strong evidence support
- Early warning system helps take action timely
- Contemporaneous records automatically generated, saving significant time

Version History

v1.0.0 (2026-06-30)
- Initial version
- Based on GPCCAR 12 modules + CIOB Dynamic Time Modelling
- 4 core scripts
- 4 reference materials
- 2 practice cases

Last Updated: 2026-07-02
Author: The Honorable Zenfo (知府大人)
Brand: ZFCC (Zenfo Forensic Claims Consultant)

Brand Description and Contact Information

Brand Description

ZFCC (Zenfo Forensic Claims Consultant) is an independent professional brand founded by The Honorable Zenfo (知府大人), focusing on international engineering claims and dispute resolution.

Professionalism Guarantee:
- All content based on authoritative international standards (AACE, RICS, SCL, FIDIC, etc.)
- Combined with actual engineering project experience
- Continuously updated to reflect latest practices

Contact Information

Author: The Honorable Zenfo (知府大人)
Email: xzf_83@qq.com
IMA Knowledge Base: ZFCC Engineering Claims (leave message in comment section, recommended method)

Professional Consultation:
- International engineering delay claims
- Forensic schedule analysis
- Arbitration preparation and expert witness

END of SKILL.md (English Version)