Logistics Process Decomposition
Collection
Workings around creating a model focused on taking a logistics process description and turning it into structured JSON steps. • 1 item • Updated
Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed
Error code: DatasetGenerationError
Exception: ValueError
Message: Expected object or value
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1827, in _prepare_split_single
for key, table in generator:
^^^^^^^^^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 613, in wrapped
for item in generator(*args, **kwargs):
~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 281, in _generate_tables
examples = [ujson_loads(line) for line in batch.splitlines()]
~~~~~~~~~~~^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/utils/json.py", line 20, in ujson_loads
return pd.io.json.ujson_loads(*args, **kwargs)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
ValueError: Expected object or value
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1694, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1880, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
example_id string | input string | output dict |
|---|---|---|
GLD-001 | The forklift operator takes the pallet from one location to a staging lane at the end of the storage aisle. All transactions are validated by scanning the pallet being moved. | {
"actor": {
"actor_label": "Forklift operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Pickup the pallet",
"process_unit": "pallet",
"execution_mode": "human_operated_equipment",
"equipment": [
"forklift"
],
"quantities": "{}",... |
GLD-002 | The material handler walks to the pick area after reading their scanner to figure out which tote to grab. Once they identify the correct tote they grab it, walk to the conveyor and place it on the conveyor belt. Scans of the tote occur to validate the picking and the placing. | {
"actor": {
"actor_label": "Material handler",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Read from scanner",
"process_unit": "tote",
"execution_mode": "human_operated_equipment",
"equipment": [
"barcode_scanner"
],
"quantities": "... |
GLD-003 | The forklift operator gets a transfer order from their VMU to tell them where to go. They take that and drive down the dock to the aisle they need to get the pallet from, turn traveling up that location's aisle and they go grab the pallet out of the selective racking, raising forks to whatever level needed if needed. T... | {
"actor": {
"actor_label": "Forklift operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Read from VMU",
"process_unit": "pallet",
"execution_mode": "human_operated_equipment",
"equipment": [
"VMU"
],
"quantities": "{}",
"f... |
GLD-004 | This is our process for unloading a trailer from our production facility, where we recieve 40 pallets a trailer. The operator steps off of their lift and walks to the button to open the dock door and presses it, getting back on their lift after. They will then remove the stacks of pallets from the truck in stacks of tw... | {
"actor": {
"actor_label": "Forklift operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Dismount forklift",
"process_unit": "trailer",
"execution_mode": "manual",
"equipment": null,
"quantities": "{}",
"frequency": 1
},
{
... |
GLD-005 | We have an operator reach into the box and grab a part for inspection, they take a look at it and place it in a good or no good box. Right now its about 50/50 on good and no good. | {
"actor": {
"actor_label": "Operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Reach and grab part",
"process_unit": "part",
"execution_mode": "manual",
"equipment": null,
"quantities": "{}",
"frequency": 1
},
{
"step_id":... |
GLD-006 | Our material handler grabs a part from the tote and conducts a visual inspection. If a defect is found it is placed in the N-GOOD tote, otherwise it is placed on the conveyor. | {
"actor": {
"actor_label": "Material handler",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Reach and grab part from tote",
"process_unit": "part",
"execution_mode": "manual",
"equipment": null,
"quantities": "{}",
"frequency": 1
},
... |
GLD-007 | Our sequencer follows a pretty simple process, we don't have any fancy following racks or anything like that. They start the rack off by walking to the printer and back at the start. They tape the two pick sheets they grabbed from the printer to the rack, and now they're ready to pick. We have a 34 slot rack and they g... | {
"actor": {
"actor_label": "Sequencer",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Walk to printer",
"process_unit": "rack",
"execution_mode": "manual",
"equipment": null,
"quantities": "{}",
"frequency": 1
},
{
"step_id": 2,... |
GLD-008 | Our sorter pushes a cart filled with different color totes down a sorting line. They stop at each of our four conveyor loading spots and place however many of that color they have at a given time, and move on to the next stop. Once they have finished with the fourth stop they walk back to the beginning with their cart,... | {
"actor": {
"actor_label": "Sorter",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Push cart to first conveyor point",
"process_unit": "cart",
"execution_mode": "human_operated_equipment",
"equipment": [
"cart"
],
"quantities": "{}",
... |
GLD-009 | Our loader's job is to take the pallet off of the wrapper conveyor and turn their forklift right around and load it straight into the trailer that is staged behind them. | {
"actor": {
"actor_label": "Loader",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Position forks to pickup height",
"process_unit": "pallet",
"execution_mode": "human_operated_equipment",
"equipment": [
"forklift"
],
"quantities": "{... |
GLD-010 | Our replenishment forklift driver gets a transport order sent directly to their VMU and after reading it they will drive to the rack location, grab the pallet from the rack and bring it back here to the picking cell location that the VMU tells them to, and yes they scan the pallet using their VMU scanner for picking an... | {
"actor": {
"actor_label": "Replenishment driver",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Read transport order",
"process_unit": "pallet",
"execution_mode": "human_operated_equipment",
"equipment": [
"VMU"
],
"quantities": "{}"... |
GLD-011 | Our lift truck operator picks up a pallet from the completed lane and drives down an L-shaped aisle to place it in a staging lane for another operator to load. They'll scan the pallet barcode on pickup and then the staging lane on placement. | {
"actor": {
"actor_label": "Lift truck operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Pickup pallet",
"process_unit": "pallet",
"execution_mode": "human_operated_equipment",
"equipment": [
"forklift"
],
"quantities": "{}",
... |
GLD-012 | Our AGV cycles from the warehouse to the plant. It sits in the warehouse until a pallet is placed on it's cart, once it senses that it will drive to the location at the plant, belt the material off of it's cart into the line location, then drive back. | {
"actor": {
"actor_label": "AGV",
"actor_type": "autonomous"
},
"steps": [
{
"step_id": 1,
"action": "Wait until pallet is detected on cart",
"process_unit": "pallet",
"execution_mode": "autonomous",
"equipment": null,
"quantities": "{}",
"frequency": 1
}... |
GLD-013 | Here we conduct route picking by out Tugger operators. They follow a predetermined rectangular route making four turns, and stop at each location that their scanner guides them to. When they reach each location they will stop, get off, pick the part, scan it, and place it in their cart, and get back on. They start and ... | {
"actor": {
"actor_label": "Tugger operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Scan pick sheet",
"process_unit": "route",
"execution_mode": "human_operated_equipment",
"equipment": [
"barcode_scanner"
],
"quantities": "{}... |
GLD-014 | Our operator places the widget against the jig nice and snug, you know to keep it tight. Then he'll go on and press the button for the automated drill to come down and drill the holes. After it's done he'll take that part, inspect it, and place it in the completed parts bucket. | {
"actor": {
"actor_label": "Operator",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Place widget against jig",
"process_unit": "widget",
"execution_mode": "manual",
"equipment": [
"jig"
],
"quantities": "{}",
"frequency": 1
... |
GLD-015 | The material handler checks their stack sheet, grabs the necessary number of totes from the pit. They'll put those totes in their cart to make a pallet, and they push it to the stacking zone. Once there they are gonna have to take the totes out of the cart and stack them on an empty pallet till they make a full one. | {
"actor": {
"actor_label": "Material handler",
"actor_type": "human"
},
"steps": [
{
"step_id": 1,
"action": "Check the stack sheet",
"process_unit": "pallet",
"execution_mode": "manual",
"equipment": null,
"quantities": "{}",
"frequency": 1
},
{
... |
null | null | null |
Logistics Golden Set Development Pilot
About This Dataset
The goal was to come up with an initial 15 logistics scenarios that will be used to conduct experiments around SFT and RL of models. This dataset is purely taking standard logistical processes and breaking them down into individualized steps. Anyone is welcome to use this dataset as they see fit, there will be others made in the future to build this out even further. My socials are available on my profile for any questions or opprotunities.
Annotation Conventions
- Single participant: Each example represents one human operator or one autonomous participant. Human-operated equipment is recorded as equipment, not as a separate actor.
- Ordered steps: Steps follow process order. Action wording may vary while preserving the same operational meaning.
- Step-specific process units: Each step defines its own reference unit, such as a pallet, trailer, tote, or route. Different units may coexist within one process.
- Quantities: A dictionary records supported physical quantities and action counts. Repeated scans can be consolidated using
scans; repeated step executions can usecycles. Physical quantities describe each execution and should not be multiplied by the cycle count twice. - Frequency: Frequency represents the proportion of a step’s process units on which the action occurs. Repetition belongs in quantities. Unknown frequencies remain
null. - Alternative outcomes: Described alternatives use separate, outcome-qualified actions. Known outcome proportions determine frequency; unknown proportions remain
null. Mutually exclusive alternatives are not interpreted as sequential work on the same item. - Warehouse motion: Travel follows a rectilinear convention with efficient 90° or 180° turns. This is a project modeling assumption, not a claim about every warehouse layout.
- Scan timing: When confirmation scanning is established but timing is unspecified, physical pickup precedes pickup confirmation and placement precedes placement confirmation. Explicit source timing overrides this default.
- Rack positioning: Unspecified rack levels are represented through positioning at pickup/placement height and travel height, without inventing numeric heights or adjustment directions.
- Execution mode and equipment: Scanning, driving, display reading, and pushing carts use
human_operated_equipment. Mounting/dismounting ismanual. Passive jig positioning remainsmanualwith the jig recorded. Powered dock-door controls usehuman_operated_equipmentwithdock_door. - Missing information: Unsupported values are not invented. Empty quantities (
{}) mean no quantity was extracted, not zero. Equipmentnullmeans unspecified;[]means explicitly none.
Limitations
- Development pilot: This release contains 15 human-authored examples and 129 annotated steps. The examples informed annotation-rule development and are not an untouched test set.
- Review scope: Labels received AI-assisted consistency review under the author's domain judgment. Independent annotator agreement has not been established.
- Limited coverage: The dataset does not establish coverage of all logistics processes, equipment types, writing styles, or operational exceptions.
- Single-participant scope: Multi-operator coordination, handoffs, and joint work are outside the current experiment.
- Flat process representation: Explicit loop boundaries and branch relationships are omitted. Adjacent steps with equal cycle counts do not necessarily belong to the same loop. Detailed control flow may require the original text or a future schema extension.
- Mixed-unit conversion: Converting per-tote, per-pallet, or per-route work into a common basis may require additional information. A frequency of
1does not imply those conversion quantities are known. - Downstream engineering: Travel distances, numeric placement heights, MTM/MOST calculations, labor standards, and optimization are outside the output scope.
- Project-specific conventions: Annotations follow the documented modeling rules; they should not be interpreted as universal industry standards.
- Validation boundary: Parser validation confirms structural requirements, not operational correctness. No model performance or generalization claim is established by this dataset release.
- Downloads last month
- 48