84.6°F against an 84.0°F threshold. Elevated disease and parasite risk under sustained heat. Alert opened 07:15 today. 2 open alerts — see Environment view.
Active lots (TLCs)
6
2 packed · 1 shipped this week
CV events today
1,284
All cameras reporting
Avg claw size (7d)
3.1 in
+0.2 in vs prior 7d
Water temp — Pen 3
84.6°F
Above 84.0°F threshold
Events missing batch ID
12
Queued for reconciliation
Water temperature — 30 days
Pen 3 · °F · dashed line = 84.0°F alert threshold
Salinity — 30 days
Pen 3 · ppt · target band 34–37 ppt
Live computer-vision event feed
Camera detections, most recent first · updates continuously in production
Flagged detections route to the alert queue and the GM's daily review list.
FSMA 204 traceability register
Every lot carries a Traceability Lot Code (TLC) with Key Data Elements captured at each Critical Tracking Event. FDA records requests must be answerable with an electronic sortable spreadsheet within 24 hours — one click below.
KDE completeness = captured Key Data Elements vs required set for that event type. Compliance date for the Food Traceability Rule: July 20, 2028.
GDST / EPCIS 2.0 event stream
Standards-based events for seafood traceability — ready for logistics-partner exchange
Event
Type
Lot
Time
ObjectEvent · commission
Harvest
TLC-2607-P1-006
Jul 15 · 06:20
AggregationEvent · pack
Pack
TLC-2607-P3-004
Jul 14 · 15:02
ObjectEvent · ship
Ship
TLC-2606-P1-003
Jul 13 · 09:44
ObjectEvent · commission
Harvest
TLC-2607-P2-005
Jul 12 · 06:35
Reconciliation queue
Events with missed or unreadable batch identifiers (QR/RFID)
Source
Count
Cause
Status
Camera 2 · Pen 3
8
QR glare misread
Needs review
Pack station
4
Tag not presented
Needs review
Offline buffer
0
—
Synced
Offline buffering holds events locally during connectivity loss and syncs with original timestamps — no data gaps in the register.
Capture success (7d)
99.1%
Target ≥ 98%
Errors caught (7d)
47
All queued or auto-resolved
Awaiting review
12
Missing batch IDs
Buffered offline
0
Last sync 09:44 today
Data loss (30d)
0
Buffer covered 2 outages
Error queue — caught, classified, routed
Capture failures are detected at ingestion, classified, and either auto-resolved or queued for a human · design goal: nothing silently dropped
Error type
Source
Count
Detected by
Resolution
Status
Missing batch ID
Camera 2 · Pen 3
8
Ingestion validation — event lacks TLC
Reconciliation queue, match by pen + time window
Needs review
Missing batch ID
Pack station
4
Ingestion validation
Reconciliation queue
Needs review
Low-confidence detection
All cameras
23
Confidence below 90% threshold
Routed to GM review list, excluded from analytics until confirmed
In review flow
Connectivity gap — 14 min
Camera 2 · Pen 3
1
Heartbeat monitor
Offline buffer replayed 61 events with original timestamps
Auto-resolved
Sensor dropout — 22 min
Pen 2 salinity probe
1
Expected-reading watchdog
Gap flagged on chart, hub backfilled on reconnect
Auto-resolved
Duplicate tag read
Pack station
6
Idempotency check on event ID
Deduplicated automatically
Auto-resolved
Malformed payload
Sensor hub firmware
4
Schema validation at API
Rejected with error log, retried by hub, all accepted
Auto-resolved
How errors are caught
Five layers between the water and the traceability register
Layer
Catches
1 · Schema validation
Malformed or incomplete payloads rejected at the API, never enter the register
2 · Identifier check
Events without a readable QR/RFID batch ID quarantined to the reconciliation queue
3 · Confidence threshold
CV detections under 90% confidence routed to human review
4 · Heartbeat + watchdog
Silent cameras or sensors flagged within minutes; gaps marked on charts
5 · Offline buffer
Connectivity loss = events held at the edge with original timestamps, replayed on reconnect
Why this matters for FSMA 204
Error handling is a traceability requirement, not a nice-to-have
An FDA records request is answered from the traceability register. A silently dropped event is a hole in that record. Catching every failure — and proving each one was either recovered or consciously resolved — is what makes the register defensible.
The error queue above doubles as an audit trail: every anomaly, when it was caught, how it was resolved, and by whom.
Water temperature — 30 days
Pen 3 · °F
Salinity — 30 days
Pen 3 · ppt
Alert thresholds
GM-configurable · triggers dashboard alert + email/SMS in production
Metric
Warning
Alert
Channel
Status
Water temp
≥ 83.0°F
≥ 84.0°F
Dashboard + SMS
Alert active — Pen 3
Salinity
< 34 or > 37 ppt
< 33 or > 38 ppt
Dashboard
In range
Dissolved oxygen
< 6.0 mg/L
< 5.0 mg/L
Dashboard + SMS
In range
Disease-flag rate
> 2% of detections
> 5% of detections
Dashboard + email
1.9% — watching
Claw weight — last week
655 lbs
+2.3% vs prior week
Meat yield — last week
45%
12-week high
Harvest events — 12 wks
36
3.0 / week average
Avg claw size — 12 wks
2.9 in
Trending up since June
Weekly claw weight harvested
lbs per week · 12 weeks
Meat yield
% of claw weight · 12 weeks
Ask CrabTrace
Natural-language queries over your operational and traceability data. Responses below are scripted for this demo.