Repository Docs & Knowledge Base

Consolidated Spensara documentation repository (722 Markdown & architecture documents in ../repository)

Built Word Documents (.docx): Spensara Overview (.docx) Capability Assessment (.docx) Brink POS Ingestion Analysis (.docx) The Borg Ingestion Architecture (.docx)

Warehouse Model (93)

Analytical data warehouse schemas, curated tables, and Redshift/Athena data models.

warehouse-model/docs/features/ETL/warehouse-data/curated-model/kitchen_item_status_events.md 3,967 bytes · Updated Oct 23, 2026 10:44 AM EDT

Raw File

curated.kitchen_item_status_events

Purpose

This table stores the item-level event stream for kitchen execution. It captures status changes and timestamps that let downstream consumers reconstruct how an item moved through kitchen preparation.

It is mainly useful for queue timing, readiness analysis, bump-flow diagnostics, and monitor logic that needs more than the current item snapshot.

Schema contract

The deployed SQL under backend/Kds.Ai.Warehouse/Sql/Bootstrap/Tenant/Curated/ is the source of truth for the current column names, types, and nullability.

Column groups

Business properties describe the business entity, event, fact, or reference record represented by the table.
Technical and ETL properties describe warehouse lineage, surrogate keys, source reconciliation, tenant scoping, slowly changing dimension controls, and ingestion metadata.

Business properties

Column	Type	Nullable	Business Meaning
`guid`	`VARCHAR(36)`	No	Unique identifier of the kitchen status event row.
`item_guid`	`VARCHAR(36)`	Yes	Reference to the kitchen item this event belongs to.
`status`	`SMALLINT`	No	Current item status recorded by this event.
`last_status`	`SMALLINT`	Yes	Previous item status before this transition.
`prepared_local_time`	`INTEGER`	Yes	Local-time representation of when the item was marked prepared.
`done_local_time`	`INTEGER`	Yes	Local-time representation of when the item was marked done or bumped.
`prepared_device_id`	`INTEGER`	Yes	Device that marked the item as prepared.
`create_time`	`INTEGER`	No	Canonical event creation time used for ordering and time-window analysis.
`is_deleted`	`SMALLINT`	No	Soft-delete flag for downstream filtering.
`create_local_time`	`INTEGER`	Yes	Local-time representation of when the item was created.
`done_device_id`	`INTEGER`	Yes	Device that marked the item as done.
`update_time`	`INTEGER`	No	Canonical last update time for this event row.
`status_name`	`VARCHAR(100)`	Yes	Readable business label for the current item status.
`last_status_name`	`VARCHAR(100)`	Yes	Readable business label for the prior item status.
`prepared_device_name`	`VARCHAR(255)`	Yes	Readable name of the device or station that marked the item as prepared.
`done_device_name`	`VARCHAR(255)`	Yes	Readable name of the device or station that marked the item as done.
`station_name`	`VARCHAR(255)`	Yes	Readable kitchen station name associated with the event.
`event_time_utc`	`TIMESTAMP`	Yes	UTC timestamp representing the event in one canonical warehouse time field.
`business_date`	`DATE`	Yes	Business date associated with the event in curated reporting logic.

Technical and ETL properties

Column	Type	Nullable	Technical Meaning	Notes
`event_key`	`BIGINT`	Yes	Stable warehouse key for the kitchen item status event.
`source_system`	`VARCHAR(100)`	Yes	Canonical name of the source platform that produced the event.
`source_event_id`	`VARCHAR(199)`	Yes	Original event identifier from the source platform.
`tenant_key`	`BIGINT`	Yes	Stable warehouse key for the tenant, brand, or client that owns the event.
`tenant_name`	`VARCHAR(255)`	Yes	Readable tenant, brand, or client name associated with the event.
`event_sequence_number`	`BIGINT`	Yes	Canonical ordering number of the event within the kitchen item lifecycle.
`_etl_batch_id`	`VARCHAR(256)`	Yes	ETL batch lineage identifier.
`_etl_source_type`	`VARCHAR(100)`	Yes	Source adapter type used by ETL.
`_etl_ingested_at`	`TIMESTAMP`	No	Warehouse ingestion timestamp for the curated row.	Required ingestion audit timestamp.