{
  "title": "Logistics consulting process-event and elapsed time data for AI",
  "source_page": "https://fiund.com/industries/logistics-consulting-event-definition-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Queue time and handling time use different event boundaries",
    "context": "An original dummy process map has arrival, work-start, finish and data-entry times. It contains no real shipment, route, customer or warehouse layout.",
    "records": [
      [
        "LGT1",
        "Practice job A event log",
        "Arrival 08:00; handling starts 08:20; handling ends 08:35."
      ],
      [
        "LGT2",
        "Entry metadata",
        "All A events entered in the system at 09:00; entry time is not an operating event."
      ],
      [
        "LGT3",
        "Practice job B",
        "Arrival 08:00 and finish 08:40 recorded; handling-start event absent."
      ]
    ],
    "question": "What queue and handling durations are supported for A, and can B's total elapsed time be split into those measures?",
    "answer": "LGT1 supports A's queue as 20 minutes from arrival to handling start and handling as 15 minutes from start to finish. LGT2's 09:00 entry time does not change those event intervals. LGT3 supports B's 40-minute arrival-to-finish elapsed time but lacks the start needed to separate queue from handling. Preserve that unresolved split instead of assigning A's proportions or using data-entry delay as process duration.",
    "failureModes": [
      "Using record-entry time as the finish or handling-start event.",
      "Splitting a total elapsed time without a documented boundary or copying another job's durations."
    ],
    "fields": [
      [
        "Event definition and job",
        "Defines each interval boundary."
      ],
      [
        "Occurred versus entered time",
        "Separates the process from documentation delay."
      ],
      [
        "Missing start event",
        "Makes an unavailable duration explicit."
      ]
    ],
    "holdout": "Supply B's start time after its finish, creating an intentional conflict. Require a chronology flag rather than a negative or silently corrected handling duration.",
    "boundary": "Use original dummy events. Exclude customers, products, routes and warehouse layouts."
  }
}