Border Master Data
Borders & Corridors → Border Master Data holds the reference data everything else in this group depends on: the border posts the fleet crosses and the corridors that run through them. Capture them once, accurately — dwell tracking, SLA reporting, cost schedules, and requirement-template corridor matching all key off these records.
Adding a border post
In Add border post:
| Field | Notes |
|---|---|
| Name | e.g. Lebombo — required |
| Neighbour country | Two-letter ISO code (e.g. MZ) — required |
| Road | Optional, e.g. N4 |
| Dwell SLA minutes | Optional turnaround target — without it, the post can never breach on Border Dwell SLA |
| Latitude / Longitude | Optional coordinates (validated to ±90 / ±180) |
Adding a corridor
In Add corridor:
| Field | Notes |
|---|---|
| Name | e.g. Maputo Corridor — required |
| Origin / Destination country | Two-letter ISO codes (e.g. ZA → MZ) — required |
| Border post | Optionally link the corridor to one of the captured posts |
Append-mostly
Both lists are read-only once captured — there is no edit or delete. Reference data is deliberately append-mostly: reports and schedules built on a post or corridor should never have it change under them. Capture carefully; a typo means a new record.
Where it's used
- Posts feed the crossing picker on Trip Dwell and the SLA gate on Border Dwell SLA.
- Corridors carry the priced cost models on Corridor Cost Schedule and are matched by Requirement Templates.