Work Plans
Transactional file delivering work orders and cellar tasks from the ERP system. Populates Claret's Work Planning module.
Work orders / cellar tasks issued from the ERP system. One row per work plan. In Claret, these populate the Work Planning module's board, kanban, and capacity views.
Schema
1
external_system_id
The ERP's identifier for this work order. Unique per row. Used as the merge key so re-deliveries update the same work plan in Claret.
WO-2026-0501-001
2
activity_type
The kind of work being done. Must be one of the values in Controlled vocabularies.
Cap Management
3
status
Current state of the work plan. Must be one of the values in Controlled vocabularies.
Scheduled
4
description
Short title.
Punch-downs on Tank 4
5
location_name
The site where the work occurs. Must match a location from the Locations file.
ZAM-WINERY
6
priority
One of: Critical, High, Medium, Low. Defaults to Medium.
High
7
location_area_name
Sub-area within the location. Must match a location_area from the Locations file.
North
8
item_name
The item this work targets, if applicable. Can reference any item level: an FG item_name or vintage_name from the Finished Good Items file, or a parent_wip_name or child_wip_name from the Bulk Wine Items file. Use the level that best matches what the work order is actually for. A generic "rack a barrel of Cab" might target the parent WIP ZAMNVCAS; "transfer SS-01 to SS-02" for the 2020 vintage targets ZAMNVCAS20.
ZAMNVCAS20
9
comments
Long-form notes from the ERP.
Twice daily punchdowns until end of fermentation
10
earliest_start_date
The earliest date this work can begin, as YYYY-MM-DD.
2026-05-08
11
due_date
When this work must be completed, as YYYY-MM-DD.
2026-05-12
12
scheduled_start
Planned start, as YYYY-MM-DD HH:MM (24h, client local time).
2026-05-08 07:00
13
scheduled_end
Planned end, as YYYY-MM-DD HH:MM.
2026-05-08 09:00
14
actual_start
Actual start, as YYYY-MM-DD HH:MM. Omit until work begins.
2026-05-08 07:05
15
actual_end
Actual end, as YYYY-MM-DD HH:MM. Omit until work completes.
2026-05-08 08:55
16
quantity
Estimated work quantity (e.g., gallons to move, cases to handle). Numeric value. Decimals fine, whole numbers fine. No thousands separators.
5000
17
uom
Unit of measure for quantity.
Gallon
Header row
Sample data
Row 1: bulk wine, child WIP target (
ZAMNVCAS20).Row 3: FG bottling, vintage target (
122-16).Row 4: bulk wine, parent WIP target (
ZAMNVCAS), used when the work isn't tied to a specific vintage.Row 5: no item; work is location-only (sanitation).
Snapshot semantics
Full snapshot of all open and recently-closed work plans every delivery. Plans completed or cancelled more than 30 days ago may be omitted.
external_system_idis the merge key; re-delivering the same id updates the existing plan in place.A work plan absent from a new file but present in a prior file is not treated as cancelled. To cancel, deliver the row with
status=Cancelled. (This avoids accidental loss when an ERP query temporarily excludes recent records.)Activity types, statuses, and priorities must use the controlled vocabularies below. Unknown values will be rejected.
Controlled vocabularies
Activity types
activity_type must be one of:
Additions, Bottling, Cap Management, Centrifuge, Circulation, Cross Flow, De-alc, De-va, Drain/Press, Filter, Harvest, Inventory, Measure, Moves, Oak Additions, Pickup Inbound, Pickup Outbound, Sanitation, Site Projects, Ullage
Statuses
Planned
Work identified but not yet scheduled to a specific date/time
Scheduled
Work assigned a specific scheduled start/end
In Progress
Work has started but is not yet complete
On Hold
Work has been paused; will resume
Completed
Work is done
Cancelled
Work will not be performed
Priorities
priority must be one of:
Critical, High, Medium, Low
Last updated
Was this helpful?