INDUSTRY FIELD GUIDE
Liquid pipeline batch records for offline AI evaluation
A scheduled batch in a document does not prove what moved.
NAICS 486110 · Pipeline Transportation of Crude Oil
NAICS 486910 · Pipeline Transportation of Refined Petroleum Products
A scheduled batch in a document does not prove what moved. PHMSA publishes material on pipeline product and service changes. An operator can build an entirely fictional packet to test whether a model keeps scheduled and observed records separate. The output is a retrospective evidence summary. PHMSA guidance on product and service changes
Invent two batches and a receipt summary. Match the verified receipt to one batch and give the other a nomination with a similar time and a later cancellation. Ask which batch record supports the receipt and which field remains unresolved. Separate commodity labels, record source, and the meaning of each timestamp. Include crude and refined examples only where the exercise preserves their distinct context.
Keep actual routes, product compositions, identifiers, pressure, flow values, control interfaces, and operating procedures out of the dataset. Use dummy records reviewed by an authorized specialist. Do not connect the evaluation to live systems.
Describe a simulated batch-record review
Original Fiund exercise
A canceled nomination does not establish an observed batch movement
An entirely fictional retrospective packet uses abstract batch and commodity labels. It contains no route, composition, pressure, flow, control interface or operating procedure.
| Record | Source | What it records |
|---|---|---|
| PB1 | Batch A receipt | Verified original receipt R-A explicitly names batch DEMO-A and abstract commodity C1 at reference time T1. |
| PB2 | Batch B nomination | Nomination N-B schedules DEMO-B, commodity C2, near T1. Later cancellation explicitly names N-B; no movement confirmation supplied. |
| PB3 | Summary metadata | R-A is an observed receipt; N-B is a schedule and its cancellation is administrative. No C1-to-C2 equivalence or B receipt exists. |
Question for the model
Which batch supports the observed receipt, and does B's similar schedule establish movement or a commodity substitution?
Show the reference answer and checks
PB1 explicitly supports receipt of DEMO-A under commodity label C1. PB2 schedules then cancels DEMO-B and supplies no movement evidence. PB3 distinguishes those record types and provides no equivalence between commodities. Similar timing cannot attach R-A to B or establish a substitution. Report A's receipt and B's canceled schedule with their separate sources, leaving unobserved movement unresolved without making any pipeline operational decision.
- Treating a nomination as proof that a batch moved.
- Matching by nearby times while ignoring batch identity, commodity label and cancellation.
Fields to preserve
- Batch and abstract commodity
- Defines the record scope.
- Scheduled versus observed event type
- Separates intention from evidence.
- Receipt reference and cancellation target
- Supports the retrospective summary.
Test another case
Add a B receipt at a different time but omit its commodity label. Require movement evidence to resolve while commodity attribution remains incomplete.
Use specialist-reviewed dummy records only. Exclude operational values and live systems; no navigation, transfer or control action is taken.
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.