01
Data intake
LOGFAS remains the source. Relay resolves units down to the individual object, with dimensions, weight and load class, and pairs cargo with carrier before departure day forces it.
Relay · Logistics
From the NATO deployment plan to the parking slot.
Relay runs the deployment nodes of Germany's logistics hub: seaport, airport, railhead and convoy support centre. What comes out of NATO planning becomes a site plan, is executed in the field and reported back as evidence.
What Relay does
Plan, execute and document deployments.
Relay is the software for the place where units are transloaded: from ship to road, from road to rail, from aircraft into the convoy.
01 · Situation
Germany is the hub.
Allied units arrive at German seaports, airports and railheads and must move on east. At each of these nodes hundreds of vehicles and containers are unloaded, parked and sent off again in convoys.
02 · Problem
Planning stops at the gate of the node.
NATO planning says which unit arrives when. What then fits on which area, in which order it is parked and who blocks whom is handled today with experience, spreadsheets and radio. That costs hours per convoy, and nobody knows exactly what is on the ground right now.
03 · Solution
Relay makes the node plannable and visible.
Relay takes the NATO plan, calculates what fits on the area, assigns every vehicle a slot and guides the staff in the field by handheld. What happens is logged and reported back to planning. Offline, even without an outside connection.
Four modules
One set of data for three roles, in four steps.
Sending nation, host nation and command structure work on the same picture. The NATO plan becomes a site plan, the site plan becomes work in the field, the work in the field becomes evidence.
02
Area and sequence planning
Draw the node area on the map, calculate capacity instead of guessing, derive the parking order from the departure sequence. Whoever drives in first no longer ends up at the back.
03
Field execution
The same picture, reduced for the marshal to the next action: slot, carrier, conflict warning. Capture at the object via QR or RFID, offline on the local network, less radio traffic.
04
Evidence
Complete event log, throughput, dwell time, commander's report. Actual data back into planning. The follow-on operation stands on real numbers.
Nodes
Four node types, one model.
Seaport
Space. Heavy equipment in loading order, separated from the carrier. The node type Yarded was field-tested on.
Airport
Apron. The clearing sequence controls the arrival rate, cadence in minutes.
Railhead
Ramp and train formation. A sequencing error shows up hundreds of kilometres later.
Convoy support centre
Supply as the binding resource: fuel, food, repair. Without the CSC, the unit does not get through.
Origin
Born as Yarded. From the troops, awarded by NATO.
„After two hours of training, as fast as after two years in the old process.“
Field trial with Logistics Battalion 163, January 2024
June 2022
Innovation Challenge Logistics
The Bundeswehr Logistics Command and the Cyber Innovation Hub select eight prototypes from 86 ideas. Yarded is one of them.
2023
Built with Logistics Battalion 163
Process mapping during a real mission at the port of Emden, workshops with the troops, demonstrator delivered in September.
November 2023
First place, NATO Innovation Challenge
Military Mobility category, Ljubljana. Ahead of 39 ideas, including major international consultancies.
January 2024
Field trial in Delmenhorst
Three days under real conditions with soldiers of Logistics Battalion 163. Adjustments were deployed during the exercise.
2026
Relay at MKS
The team behind Yarded builds Relay at MKS as a new development: the seaport first, then airport, railhead and convoy support centre. Designed for disconnected operation and accreditation from day one.
Differentiation
What sets Relay apart from yard, terminal and tracking software.
Deployment nodes are not freight yards. Relay is built for the doctrine, the roles and the security situation of the troops.
01
Domain, not toolkit
Four node types, each with its binding constraint, march order, blocking logic and the pairing of carrier and cargo. No yard, terminal or ERP software has that.
02
LOGFAS-native
NATO planning remains the source. Import as a file first, later via the interfaces of the new NATO logistics systems. No bolt-on, no replacement.
03
Capacity as a calculation
Dimensions, load classes, manoeuvring clearances, timeline. Relay calculates, proposes and explains. The authorised user decides.
04
Field first
Handheld flows for arrival, parking and retrieval. Offline on the local network, radio-light, with unique identifiers on the object. Derived from the Yarded field trial.
05
Evidence and feedback
Complete event log, throughput, commander's report. Actual data back into planning and to headquarters.
06
Sovereign and accreditable
Developed in Germany, designed for disconnected operation and accreditation. Need-to-know instead of everyone sees everything.
Boundary
What Relay does not take over.
- Relay does not replace NATO movement planning. It makes that plan executable on the node.
- Movement credits and route clearances stay with the competent authorities.
- Relay controls the movement node, not the fight.
- Conflicts are shown. Decisions stay with the authorised user.
Relay
From the NATO deployment plan to the parking slot.
Relay runs the deployment nodes of Germany's logistics hub: seaport, airport, railhead and convoy support centre. What comes out of NATO planning becomes a site plan, is executed in the field and reported back as evidence.