Gate Configuration
A gate is a named crossing point. Before anyone can check an asset in or out, at least one gate has to exist — the Gate screen has nothing to work with otherwise.
Gate setup is split across two screens:
| Screen | What you do there |
|---|---|
| Location Editor | Create the gate and place it on the map. This decides where the gate is. |
| Gate Editor, in Admin Configuration | Set its direction, activate or deactivate it, and edit or delete it. This decides how it behaves. |
Both are Admin screens.
Creating a Gate
Gates are created in the Location Editor, because a gate is a location: a point under a facility, or directly under the site.
- In the Gate Editor, choose Add Gate. It opens the Location Editor.
- Choose the Gate tool, click the map, and name the gate.
You can also open the ⋯ menu on any existing location and choose Make a gate. See Gates in the Location Editor for the details.
A new gate starts as bidirectional and active. Adjust it in the Gate Editor.
The Gate Editor
The Gate Editor lists every gate:
The table is sortable. Its main columns:
| Column | What it shows |
|---|---|
| Name | What operators see in the gate selector. Use the name the gatehouse actually uses — "North Gate", "Scale House". |
| Location | The location the gate sits at. A gate whose location can no longer be found shows Location not found in red. |
| Parent | The facility the location is in, or the site. |
| Direction | Inbound, Outbound, or Bidirectional. |
| Associated Location ID | The id of the gate's associated location, when one is set. |
| Active | Whether the gate appears in the operator's selector. |
| Created, Updated | When the gate was created and last changed. |
Open a gate's ⋯ menu for Edit, Activate or Deactivate, and Delete. Activating, deactivating and deleting ask you to type the action word to confirm.
Edit opens a drawer where you can change the Gate Name, the gate's location and its Direction. The location field is labeled Site, with the hint "Site location is required", even though it picks a facility or location. A place that has no id yet is greyed out with Save this location in the Location Editor first. Pick a different place here to fix a gate that shows Location not found.
Direction
Direction is about what the gate is for, not a hard restriction on traffic:
- Inbound — an arrivals gate. Operators check assets in here.
- Outbound — a departures gate. Operators check assets out here.
- Bidirectional — one crossing point handling both, which is the common case for smaller yards with a single entrance.
Pick the one that matches how the gatehouse is staffed. A single bidirectional gate is simpler to operate than two one-way gates covering the same physical lane.
Deactivating vs Deleting
Deactivate a gate that is out of service — closed for the season, under construction, or retired. It vanishes from the operator's selector, and its crossing history stays intact and reportable. Choosing Stop being a gate on the location in the Location Editor does the same thing, and Make a gate reactivates it.
Delete only a gate created in error. History that references a deleted gate loses the ability to resolve its name.
Deactivating is almost always the right choice.
The location stays on the map. Only the gate is removed.
Practical Notes
- Start with one gate. Most yards need exactly one. Add more when you genuinely have separate staffed crossing points, not to model lanes at the same gatehouse.
- A gate is a location with gate behavior. The gate records the crossing; the asset's destination is another location. An asset checked in at North Gate and parked in Row 12 has both.
- A location that a gate uses cannot be deleted. Yard Spot refuses and names the gate. This applies to inactive gates too. See Deleting.
- Rename freely. A gate is tied to its location by id, so renaming the location does not break it. Deactivate rather than rename when a gatehouse changes purpose, since renaming rewrites how past crossings read.