<!-- LLM INSTRUCTIONS: Fill in the Resource Breakdown Structure based on the
project context.

Context and Definition:
The resource breakdown structure is a hierarchical structure used to organize
the resources by type and category. It can be shown as a hierarchical chart or as
an outline. It is an output of Estimate Activity Resources, and its resources are
based on the project scope: a stable scope gives a stable resource tree, and an
evolving scope gives one that must be re-examined each time scope moves.

It can receive information from:
*   Assumption log
*   Resource management plan
*   Scope baseline
*   Activity attributes

It provides information to:
*   Duration estimates worksheet

Tailoring Tips:
*   Decompose the team branch further when the project mixes skill levels,
    required certifications or locations, since a branch holding all three
    cannot be estimated against anything.
*   Organise by geography instead of by type when the work is spread across
    sites and the constraint is where people are.
*   Keep the numbering contiguous. A gap in the codes reads as a missing node
    rather than a deliberate skip.

Alignment:
The resource breakdown structure should be aligned and consistent with:
*   Resource management plan
*   Resource requirements

Section Instructions:
*   1. Resource Breakdown Structure (Outline): Give the hierarchy as rows of code
    and node. The code is the position in the tree, written as 1, 1.1, 1.1.1 so a
    reader can rebuild the tree from the text alone.
*   2. Resource Breakdown Structure (Hierarchical Chart): State which view the
    diagram takes, then give the node labels in the same order as the outline.
    The chart and the outline must agree.
-->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">RESOURCE BREAKDOWN STRUCTURE</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## 1. Resource Breakdown Structure (Outline)

| RBS Code | Resource Node |
| :--- | :--- |
| 1 | [ Project Name ] |
| 1.1 | People |
| 1.1.1 | [ Add details... ] |
| 1.1.2 | [ Add details... ] |
| 1.2 | Equipment |
| 1.2.1 | [ Add details... ] |
| 1.3 | Materials |
| 1.3.1 | [ Add details... ] |
| 1.4 | Supplies |
| 1.4.1 | [ Add details... ] |
| 1.5 | Locations |
| 1.5.1 | [ Add details... ] |

## 2. Resource Breakdown Structure (Hierarchical Chart)

**Chart Form:** [ Add details... ]

**Node Labels:**
[ Add details... ]

```mermaid
mindmap
  root((Project))
    People
      PlaceholderP1["[ Add details... ]"]
      PlaceholderP2["[ Add details... ]"]
    Equipment
      PlaceholderE1["[ Add details... ]"]
      PlaceholderE2["[ Add details... ]"]
    Materials
      PlaceholderM1["[ Add details... ]"]
      PlaceholderM2["[ Add details... ]"]
    Supplies
      PlaceholderS1["[ Add details... ]"]
      PlaceholderS2["[ Add details... ]"]
    Locations
      PlaceholderL1["[ Add details... ]"]
      PlaceholderL2["[ Add details... ]"]
```

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Resource Manager** | {{Resource_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **PMO Lead** | {{PMO_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> RESOURCE BREAKDOWN STRUCTURE | <strong>Ref:</strong> PMO-04.06.03 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.06.03.schema.json",
  "title": "Completed RESOURCE BREAKDOWN STRUCTURE Data Contract",
  "description": "Additive structural schema validating completed RESOURCE BREAKDOWN STRUCTURE artifact data payloads (PMO-04.06.03).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.06.03"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "resource_breakdown_structure_outline": {
      "type": "object",
      "properties": {
        "rbs_code": {
          "type": "string",
          "minLength": 1,
          "description": "The position of the node in the hierarchy, written as 1, 1.1, 1.1.1 so a reader can reconstruct the tree from the text alone. A node numbered 1.2.1 with no 1.2 above it means a level was skipped."
        },
        "resource_node": {
          "type": "string",
          "minLength": 1,
          "description": "What the node names. A first-level node is the project, a second-level node is a resource category such as people or equipment, and a third-level node is an individual resource carrying its quantity. A category node with nothing beneath it leaves the branch empty."
        }
      },
      "required": [
        "rbs_code",
        "resource_node"
      ]
    },
    "resource_breakdown_structure_hierarchical_chart": {
      "type": "object",
      "properties": {
        "chart_form": {
          "type": "string",
          "minLength": 1,
          "description": "Which view the chart takes: a mindmap for a single hierarchy, or a flowchart where the nodes carry relationships rather than only parentage. Stated so a reader knows what the diagram is meant to show."
        },
        "node_labels": {
          "type": "string",
          "minLength": 1,
          "description": "The node labels, one per line, in the same order as the outline. The chart and the outline must agree: a branch present in one and absent from the other is the defect this section exists to prevent."
        }
      },
      "required": [
        "chart_form",
        "node_labels"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "resource_breakdown_structure_outline",
    "resource_breakdown_structure_hierarchical_chart"
  ]
}

{
  "form_name": "RESOURCE BREAKDOWN STRUCTURE",
  "document_reference": "PMO-04.06.03",
  "_llm_instructions": "Populate the fields of 'RESOURCE BREAKDOWN STRUCTURE' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.06.03.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_RBS_Code": {
      "section": "Resource Breakdown Structure (Outline)",
      "label": "RBS Code",
      "guidance": "The position of the node in the hierarchy, written as 1, 1.1, 1.1.1 so a reader can reconstruct the tree from the text alone. A node numbered 1.2.1 with no 1.2 above it means a level was skipped.",
      "value": ""
    },
    "f02_Resource_Node": {
      "section": "Resource Breakdown Structure (Outline)",
      "label": "Resource Node",
      "guidance": "What the node names. A first-level node is the project, a second-level node is a resource category such as people or equipment, and a third-level node is an individual resource carrying its quantity. A category node with nothing beneath it leaves the branch empty.",
      "value": ""
    },
    "f03_Chart_Form": {
      "section": "Resource Breakdown Structure (Hierarchical Chart)",
      "label": "Chart Form",
      "guidance": "Which view the chart takes: a mindmap for a single hierarchy, or a flowchart where the nodes carry relationships rather than only parentage. Stated so a reader knows what the diagram is meant to show.",
      "value": ""
    },
    "f04_Node_Labels": {
      "section": "Resource Breakdown Structure (Hierarchical Chart)",
      "label": "Node Labels",
      "guidance": "The node labels, one per line, in the same order as the outline. The chart and the outline must agree: a branch present in one and absent from the other is the defect this section exists to prevent.",
      "value": ""
    }
  }
}