Cold-Chain Shipment Monitoring
Design a monitoring workspace that distinguishes temperature excursions, sensor uncertainty, product exposure, and required response.
The brief
Understand the problem
Background
Temperature-sensitive medicines move through trucks, warehouses, and airports with several sensors and custodians. A threshold alert does not by itself reveal whether product quality is affected or whether a sensor failed.
User context
Yuki monitors international vaccine shipments. One pallet reports 9.1°C for twenty-two minutes during an airport transfer, while a second sensor on the pallet continues to report 5.4°C.
Product problem
Yuki needs to assess evidence, preserve chain of custody, and coordinate containment without making a product safety determination from incomplete telemetry.
Objective
Create fleet overview, excursion investigation, response coordination, and disposition handoff for one monitored shipment.
What to design
Define the experience
Required experience
- Identify shipments with meaningful monitoring risk
- Compare sensor traces, thresholds, custody, and location events
- Start a containment and evidence plan
- Hand the case to an authorized quality reviewer
Screens and states
- Cold-chain overview
- Excursion investigation
- Containment coordination
- Quality review handoff
Core user flow
Follow the critical path
- 01
Yuki sees one shipment move from warning to conflicting-sensor review
- 02
She compares calibrated sensor readings against transfer events
- 03
The destination is instructed to quarantine the pallet on arrival
- 04
Yuki packages the trace, custody log, and photos for quality disposition
Product rules
Requirements and constraints
Requirements
- Show threshold, duration, severity source, and sensor confidence
- Align temperature, location, and custody events on one timeline
- Distinguish operational containment from final product disposition
- Track acknowledgements across carrier, warehouse, and quality roles
- Export an immutable evidence bundle
Constraints
- The monitoring product cannot independently declare medicine safe or unsafe
- Sensor data may arrive late or with gaps
- Shipment details and facility locations require role-based access
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Shipment readings
- Sensor A: peak 9.1°C for 22 minutes
- Sensor B: range 4.8°C to 5.6°C
- Configured range: 2°C to 8°C
- Last custody scan: Airport Transfer Bay 6 at 14:32 UTC
Finish line
What to deliver
- Four responsive screens covering detection through quality handoff
- An event model for warning, confirmed excursion, sensor fault, contained, and disposition pending
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.