$6.99
Home › Templates › Logistics › Vector
Logistics dashboard template
Vector Freight Network Dashboard Template
Vector is a single-file HTML dashboard template for a freight network, with a route chart, shipment manifest, port stats, fleet assets, and delay costs.
Vector is a freight network dashboard template delivered as one self-contained HTML file. A freight network dashboard shows where the boxes are and what delays cost: containers in transit, lanes running late, port congestion, fleet utilization, and open claims. Vector renders all of that across five views in a light Admiralty theme with the accent #3D5A80, modeling a network of 14 ports, 16 active lanes, and 2,400 containers under management for week 27.
Vector opens on the Network view with a ribbon of four figures: 1,187 containers in transit at +42 against plan, network on-time at 83.6% against an 85.0% target, 3 of 16 lanes delayed with the lane codes named, and average door-to-door at 31.4 days, down 0.8 over the trailing 4 weeks. Below, a volume-weighted route chart draws the network, a port card opens on click, a top lanes panel ranks trade by boxes per month, and a Re-run ETA engine button demonstrates how a recompute action feels. The Shipments view is a container manifest where every row shows the lane, customer, a six-step milestone chain from gate-in to delivered, ETA, and drift, next to a rolling risk panel for missed connection odds. Ports ranks import dwell in days on terminal against target ticks, tables berth productivity with moves per hour, occupancy, cranes per call, and vessels waiting at anchor, and maps congestion heat over 4 weeks. Assets tracks the 9,860-unit container fleet with annualised turns, fleet mix, an idle-days ledger by depot, and a repositioning program marking planned versus completed moves. Exceptions closes with a cause-coded delay ledger with per-lane cost estimates, a cost-of-delay Pareto, 12 weeks of on-time performance, and a claims docket holding $147.9k in reserve.
What is inside Vector
- KPI ribbon with containers in transit (1,187, +42 vs plan), network on-time (83.6% vs 85.0% target), lanes delayed (3 of 16), and average door-to-door (31.4 days)
- Volume-weighted route chart of 14 ports and 16 lanes with a click-to-open port card and a Re-run ETA engine action
- Top lanes panel ranking trade lanes by boxes per month
- Container manifest with lane, customer, a 6-step milestone chain (gate-in to delivered), ETA, and drift per row
- Rolling risk panel scoring missed connection odds
- Import dwell ranking in days on terminal with target ticks and click-through port detail
- Berth productivity table with moves per hour, berth occupancy, cranes per call, and vessels waiting at anchor
- Container fleet view for 9,860 units with annualised turns, fleet mix, idle-days ledger by depot, and a repositioning program
- Exceptions view with a cause-coded delay ledger with cost estimates, a cost-of-delay Pareto, 12-week on-time performance, and a claims docket with $147.9k reserved
Specifications
| Format | Single self-contained HTML file; zero dependencies, no build step |
|---|---|
| Theme | Admiralty |
| Mood | Light |
| Category | Logistics |
| Price | $6.99, one-time |
Who Vector is for
Vector serves the network planners who live in the Network view: the ribbon tells them transit volume against plan and which of the 16 lanes are late before they touch the route chart. Logistics coordinators work the Shipments manifest, watching milestone chains stall and checking the rolling risk panel for likely missed connections. Port operations managers use the Ports view to argue dwell down: the ranking shows days on terminal against target, and berth productivity shows moves per hour and vessels waiting at anchor. Fleet managers own the Assets view, where idle days by depot and the repositioning program decide where empties move next. Commercial and claims teams read the Exceptions view, because every delayed lane carries a cost estimate and the claims docket totals the reserve.
When to reach for it
Vector is the pick when you are building for container shipping or freight forwarding and generic logistics templates read too thin. Milestone chains with ETA drift, dwell rankings, berth productivity, and a cost-of-delay Pareto are the actual vocabulary of a liner or forwarder operations team, and Vector ships them working with a coherent fictional dataset. It suits a forwarder prototyping a customer-facing shipment tracker, a shipping line mocking up a network control view, or a developer replacing a shared spreadsheet of container statuses and delay costs. The numbers tie together the way ops data should: the 3 delayed lanes named in the ribbon are the same lanes the delay ledger prices out. Because all of it renders from plain JavaScript arrays in one file, wiring it to a real EDI or tracking feed later means replacing the data, not the design.
Frequently asked questions
What views does the Vector freight dashboard template include?
The Vector freight dashboard template includes five views: Network, Shipments, Ports, Assets, and Exceptions. Network holds the route chart and KPI ribbon. Shipments is the container manifest. Ports covers dwell, berth productivity, and congestion. Assets tracks the 9,860-unit container fleet. Exceptions prices delays and holds the claims docket.
Does Vector show per-container milestone tracking?
Yes, Vector shows per-container milestone tracking. The Shipments view renders a manifest where each container row carries a six-step milestone chain: gate-in, loaded, departed, transshipped, arrived, and delivered. Each row also shows its lane, customer, ETA, and schedule drift, so late boxes are visible at row level.
How does Vector measure port performance?
Vector measures ports three ways. An import dwell ranking shows days on terminal against target ticks. A berth productivity table lists moves per hour, berth occupancy, cranes per call, and vessels waiting at anchor over a trailing 4 weeks. A congestion heat panel indexes boxes waiting over the same period.
Is Vector a single HTML file?
Yes, Vector is a single HTML file. The file is self-contained with no framework or build step, and the route chart, Pareto, tables, and milestone chains render from inline SVG and HTML driven by plain JavaScript data arrays. Open the file in a browser and every view and filter works.
