Cost Plan Generation

Block cost plan generation if either schedule or risk register is missing.

Pre-Generation Cross-Check (Mandatory)

Before writing any cost figures, perform all checks below. Fix any gap before proceeding.

1 — Schedule alignment

• Phase names and date ranges in cost plan must match phase names and dates in {ProjectName}_Project_Schedule.xlsx.
• Phase breakdown rows must cover every phase present in the schedule — no phase missing, none added.
• Resource names in cost plan category blocks must map to resource names used in the schedule Resource Names column. If a schedule resource has no matching cost line, add one. If a cost line has no schedule counterpart, remove or rename it.

2 — Risk register alignment

• Review every risk in {ProjectName}_Risk_Register.xlsx with Status = Amber or Red or Risk Rating ≥ 12.
• For any such risk whose mitigation involves external cost (contractor, consultant, legal counsel, MSP, licensing top-up, tooling), add a corresponding CAPEX / contingency line to the cost plan with:
  • Description referencing the risk (e.g. Risk Register #5)
  • Estimated range (or TBC with confirmation QG noted)
• Cross-reference the risk register in the cost plan header line.

3 — Resource name consistency

• Schedule Resource Names use + to separate multiple resources per task.
• Each +-split token that appears in the schedule must be traceable to at least one cost plan line.
• Do not invent resource labels that are not present in the schedule (e.g. Integration Team if the schedule says App Teams + Test Team).

Required Columns (data schema)

CATEGORY, RESOURCE, TOTAL DAYS, TOTAL HRS, HOURLY RATE (EUR), TOTAL COST (EUR)

Mandatory Worksheet Sections (in order)

1. Header block — include Based on: {ProjectName}_Project_Schedule.xlsx and Risk-aligned: {ProjectName}_Risk_Register.xlsx, grey fill
2. Cost category blocks — one section per category; mid blue category header, alternating white/light-blue data rows, light blue SUBTOTAL row
3. Overall Project Total — dark Bosch blue fill, white bold, number-formatted EUR
4. Cost breakdown by category — mid blue section header, alternating rows
5. Cost breakdown by phase — phase names and dates must match schedule exactly
6. CAPEX / additional costs — excluded from labour total; must include risk-driven contingency lines
7. Notes — grey fill, italic; cross-reference risk register for each contingency line

XLSX Formatting Standards

Follow the Bosch blue theme used in generate_bravo_cost_plan.py:

• Number format #,##0 on all EUR cost and rate cells.
• Column widths: A=52, B=32, C=10, D=10, E=16, F=16.
• Freeze pane below column header row.

Generator Script Pattern

Create generate_{ProjectName}_cost_plan.py as a new script from scratch:

• Derive CATEGORIES, PHASE_BREAKDOWN, CAPEX_ROWS, NOTES from the current project's schedule and risk register — never copy these data structures from another project's generator.
• Use existing generators only as format/structure reference for the write_xlsx(path) function and Bosch blue theme styling.
• Output path: {ProjectName}/{ProjectName}_Cost_Plan.xlsx.

Rules

• Labour only totals in core plan.
• Hardware, licences, WAN, co-lo, travel excluded from labour total.
• Stand Alone and Integration model notes must differ.
• Budget baseline state must be explicit (TBC - to be approved at QG0 or QG1 if unknown).
• Do not recycle resource names or CAPEX lines from reference projects (AlphaX, Trinity).

Output Completeness

Cost plan output is complete when this file exists:

• {ProjectName}/{ProjectName}_Cost_Plan.xlsx ← primary deliverable (XLSX, not CSV)