Northern Delivery
Where the cargo for northern settlements is now: on the situation map, in the waybill and in the driver's phone — in one system.
“Northern Delivery” is operational monitoring of cargo shipments to hard-to-reach districts of Yakutia: by river with vessels and by road with trucks. An agency operator sees the whole situation — vessels, vehicles, hot spots, wind — and a driver sees their own waybills and track in the app.
Why we took it on
Cargo to northern settlements travels for weeks and changes vehicle on the way: a barge, a warehouse, a truck. An operator needs two viewpoints — the map of the whole situation and a specific cargo by waybill — while a driver needs only their own trips and a status button. I designed one data model — waybill, track, status, history — and three ways to look at it: the map, the waybill card and the mobile app.
What blocked — and what changed
What blocked
- The situation consists of many layers — vessels, vehicles, satellite hot spots, wind, districts — and the map easily turns into a mess.
- From a waybill one must understand where the cargo is, how long it's been on the road and what has been unloaded.
- A vessel and a truck are different objects with different data, yet the operator's scenario must be one.
- A driver must quickly open a waybill and change status — on the move, in gloves, on a small screen.
What changed
- A situation map with a layers-and-filters panel on the left: each layer is a collapsible block with its own parameters.
- An object card on the map — a photo, key data, a “List of waybills” tab, the actions “Add to favourites” and “Route”.
- A waybill in three tabs: general information, cargo tracking, event log; a status scale on top, a history by points below.
- A driver app with four sections — Map, Tracking, Profile, Settings — and status selection in one tap.
How I worked
- 01
One model, three views
Waybill, track, status and history are common to the map, the card and the app. Only what is shown and what can be done differs.
- 02
Layers under control
Layers hide inside blocks, filters sit next to the layer they belong to; the map shows only what is switched on.
- 03
A trip as a ribbon
The status scale on top, the history by points below and the track player on the map turn a trip into a story that can be rewound.
- 04
Mobile: minimum on screen
Large waybill cards, status as a dropdown right on the map, bottom navigation with four sections.
Screens that move the work
Situation map: a vessel
On the left: layers and filters — ASN GIMS, municipalities, hot spots from VIIRS and NOAA-20 satellites for a period, districts, wind with speed, plume length and transparency, water transport, road transport. A click on a vessel opens the card “Vessel №26188”: a photo, name, type “Tanker — Hazard D”, MMSI, IMO, call sign and data timestamp; actions “Add to favourites” and “Vessel route”.
- Layers collapse into blocks with parameters
- Vessel data and actions in one card
Situation map: a carrier
The same map with road transport on: a click on a vehicle opens the carrier card — a truck photo, the name “Yakutsktransservice”, type “Three-axle — up to 25 tons”, plate number, generation key. On the map — a purple route from the departure point to the current position. The tab “List of waybills” shows what the vehicle carries.
Waybill: tracking a vessel
“Waybill 151”, tab “Cargo tracking”. The status scale: processing, shipped — 28.09.2024, Nizhny Bestyakh, in transit, unloaded, delivered. Below, the vessel data, the current position — 48 days on the move, 489 km in 24 hours, 28,941 km in 30 days, average speed 16.7 knots — and a map with a track player for a chosen period. At the bottom the cargo history: loading, Nizhny Bestyakh, Nizhneyansk, Olekminsk, Yakutsk.
- Status, position and history — three layers of one page
- The track can be played back for any period
The same scenario for a truck
The same screen, a different object: the carrier “Yakutsktransservice”, driver's name, plate number, vehicle type, destination, navigation status “On the way”, distance covered and the track. The operator needn't learn a second screen: the content of the block changes, the structure of the page stays.
Vehicle card
The carriers' vehicle registry: a form with key information on the left, a photo of the vehicle in the middle and a thumbnail of the last position on the map on the right. “Save changes” and “Cancel” under the form.
Driver app: waybills
Search and filters on top, large waybill cards below: “TTN-245678”, status “Delivered” with a coloured dot, plan no., track no., category, planned and actual delivery, shipping point and destination warehouse. Tabs at the bottom: Map, Tracking, Profile, Settings.
Driver app: map and status
A full-screen map, the vehicle with its plate number on the route and a status button “Rest” with a dropdown — the driver changes state without leaving the map.
Driver app: cargo position
A track on the map between Suola and Bedemya and a slide-up panel “Current cargo position”: carrier, plate number, navigation status “On the way”, shipping and destination points.
Driver app: profile
Profile data: a vehicle photo, plate number, vehicle type — “Refrigerator” — and the status “Rest”. Sign-in is a login and a password with a single “Sign in” button.
The outcome in numbers
- The operator sees the whole situation and, in two steps — from an object on the map to the waybill — reaches a specific cargo.
- Vessels and trucks are tracked in one scenario, so the operator doesn't learn two interfaces.
- A driver sees their waybills, track and status in one app and changes state without leaving the map.