{
  "title": "Water utility data for testing AI on simulated distribution events",
  "source_page": "https://fiund.com/industries/water-utility-simulation-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Read a detached simulation's missing-sample event",
    "context": "An original simulation packet uses abstract node aliases and demonstration values. It is not a real network and has no operational connection or equipment instructions.",
    "records": [
      [
        "SIM-V1",
        "Practice run definition",
        "Run V1 states that samples at 09:00 and 09:05 are expected for abstract node N."
      ],
      [
        "EVENT-S1",
        "Simulation event log",
        "For V1 only, the 09:05 measurement is deliberately suppressed as a synthetic dropout."
      ],
      [
        "TRACE-S2",
        "Exported practice trace",
        "N has a value of zero at 09:00 and no observation at 09:05."
      ],
      [
        "TRACE-S3",
        "Different run",
        "Run V2 has a low recorded value at 09:05 under its own definition."
      ]
    ],
    "question": "What does V1 establish about the zero and the absent sample? Can V2's value fill the gap?",
    "answer": "V1's 09:00 zero is a recorded demonstration value. Its 09:05 observation is absent, and S1 documents the synthetic suppression for that same run. V2's value belongs to a different run and cannot fill V1's gap. The event log explains the invented dropout only within V1; it supplies no real utility diagnosis or operational action.",
    "failureModes": [
      "Converting the absent observation into a measured zero.",
      "Combining traces from different simulation versions without an authorized mapping.",
      "Applying a synthetic event explanation to a real system."
    ],
    "fields": [
      [
        "Run version",
        "Keep event log and trace in the same simulation."
      ],
      [
        "Sampling expectation",
        "Document which intervals should contain observations."
      ],
      [
        "Missingness and value",
        "Retain presence separately from the numeric reading."
      ]
    ],
    "holdout": "Create a new run with a recorded low value and no suppression event. The model must stop calling every low or absent reading the same event.",
    "boundary": "Use a wholly fictitious or authorized isolated environment. Exclude real network maps, controls, customer usage, access credentials and asset locations."
  }
}