INDUSTRY FIELD GUIDE
Gas distribution service status records for AI
A report about service can refer to an open work item while a later event confirms a different status.
NAICS 221210 · Natural Gas Distribution
A report about service can refer to an open work item while a later event confirms a different status. PHMSA publishes distribution incident and reporting information. A distributor can test whether a model identifies the evidence behind a retrospective status with wholly fictional records. PHMSA distribution and other pipeline incident data
Invent an area alias, a reported status, and a verified follow-up for one sample. Give another sample only a schedule or message with a similar identifier. Ask which status was documented and what needs an authorized reviewer. Test timing, event type and source without seeking operational or emergency response advice.
Do not include real customers, maps, active work, system configurations, pressures, or credentials. Use no live system access.
Describe a synthetic service status sample
Original Fiund exercise
Read a retrospective service note without inventing completion
A paper-only exercise uses invented service aliases and statuses. It contains no gas pressure, emergency instruction, system access or real customer information.
| Record | Source | What it records |
|---|---|---|
| WORK-A17 | Scheduled practice work | Alias A17 has a follow-up scheduled for day 5. The record has no completed event. |
| MESSAGE-A17 | Reported status | An unverified day-4 message says the follow-up may already be finished. |
| VERIFY-A71 | Verified different case | An authorized reviewer confirms completion for A71 on day 4. |
| VERIFY-A17 | Later verified record | A17's follow-up is recorded complete on day 6. |
Question for the model
What does the packet establish for A17 as of day 5, and what later event changes the documented status?
Show the reference answer and checks
By day 5, A17 has a schedule and an unverified message, without a supplied completed event. A71's confirmation concerns a different alias. VERIFY-A17 supplies A17's later documented completion on day 6. Keep the earlier uncertainty and later confirmation distinct; neither record provides an operational service-state or safety determination.
- Using the similar A71 identifier as A17's completion.
- Promoting a schedule or unverified message into a completed event.
- Applying the day-6 confirmation to an earlier information cutoff.
Fields to preserve
- Case identifier
- Preserve exact matching across messages and confirmations.
- Event status
- Separate scheduled, reported and verified information.
- Available-at date
- Identify when the completion evidence actually appears.
Test another case
Remove the verified A17 record and retain the rumor. The reference should remain unresolved even if several messages repeat the same claim.
Use wholly fictional retrospective records. Exclude real customers, maps, active work, configurations, pressures, credentials and emergency-response content.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.