{
  "title": "Utilities management consulting metric scope data for AI",
  "source_page": "https://fiund.com/industries/utility-management-metric-scope-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An expanded service boundary breaks a simple monthly revenue comparison",
    "context": "Invented service areas and account counts form a consulting documentation exercise. Practice revenue units are synthetic; the records contain no customer accounts, network map or regulatory filing.",
    "records": [
      [
        "UM1",
        "Month 1 basis",
        "Boundary v1 includes Area A only: 100 accounts and 1,000 practice revenue units."
      ],
      [
        "UM2",
        "Month 2 basis",
        "Boundary v2 includes Areas A and B: 160 accounts and 1,520 units combined. A contributes 100 accounts and 1,040 units; B contributes 60 accounts and 480 units."
      ],
      [
        "UM3",
        "Comparison note",
        "No Month 1 B revenue supplied. Summary draft calls the combined total change a 52% improvement for the same territory."
      ]
    ],
    "question": "Which revenue change is comparable from the supplied records, and what is missing for a constant-expanded-boundary comparison?",
    "answer": "UM1 and UM2 support Area A's change from 1,000 to 1,040 practice units, a 4% increase for the stated A boundary. Combined totals rise 52%, but UM2 adds B and 60 accounts, so that percentage does not describe the same territory. UM3 lacks Month 1 B revenue; a v2-boundary restatement needs it. The exercise does not establish why A changed or measure operational savings.",
    "failureModes": [
      "Attributing added-area revenue to improved performance within an unchanged footprint.",
      "Filling a missing prior-area component with a current-period value to force comparability."
    ],
    "fields": [
      [
        "Boundary version and included areas",
        "Defines the population summarized."
      ],
      [
        "Period, revenue unit and account base",
        "Makes totals and rates interpretable."
      ],
      [
        "Component provenance and missingness",
        "Supports a defensible restatement."
      ]
    ],
    "holdout": "Supply Month 1 B revenue of 500 units. Require recomputation of the expanded-boundary change as 20/1,500, about 1.33%, while retaining the separate A result.",
    "boundary": "Use fictional aggregates and original charts. Exclude customer records, grid details and confidential utility plans."
  }
}