The Iliad Was a Logistics Problem
The Iliad is remembered for heroes, battles and gods.
But behind the mythology sits a much less romantic problem: logistics.
Thousands of people, ships, equipment and supplies had to arrive at the right place, remain operational and be supported over time.
A ship alone was not enough. Neither was a warrior.
Capability depended on the system around them.
More than two thousand years later, that distinction still matters.
We often discuss the transformation of transport by looking at the most visible asset: the vehicle.
Electric car. Electric truck. Bus. Aircraft. Autonomous platform.
But a vehicle does not create an operating system. It depends on one.
The asset is only the visible layer
An electric truck may be technically capable of completing a route.
That does not mean the transport operation is capable of supporting it.
Energy has to be available at the right location, at the right time and at the required power level.
Charging has to fit operating windows. Grid capacity has to match demand.
Storage may or may not improve the system.
Local generation may or may not make economic sense.
Digital control may become important when several energy flows, loads and operating requirements have to be coordinated.
Physical infrastructure has to accommodate all of it.
And the economics must survive contact with reality.
That is why the relevant question is not simply:
Does the technology work?
It is:
Can the complete operating system support the required transport capability?
From vehicles to infrastructure
This is the distinction behind Transport Energy Infrastructure.
TEI does not begin with a predetermined technology stack.
It begins with the operation.
What has to happen at this location?
How frequently?
How much energy is required?
When is it required?
What infrastructure already exists?
Where is the binding constraint?
Only then does the technology question become useful.
At one site, the critical intervention may be additional grid capacity.
At another, storage.
Elsewhere, charging architecture, local generation, load management, physical redesign or a combination of several elements may produce the stronger case.
And at some locations, the right answer may be to leave an apparently attractive technology out altogether.
The constraint determines the intervention.
Logistics has always been a systems problem
This is where Homer becomes unexpectedly relevant.
Large transport systems have never depended on one exceptional asset.
They depend on coordination.
Routes.
Resources.
Timing.
Availability.
Physical infrastructure.
And the ability to keep the operation functioning when individual components change or fail.
The technologies are different today.
The systems problem is not.
A highly capable vehicle without the infrastructure required to operate it remains a highly capable vehicle standing still.
The same applies at larger scale.
Installing chargers does not automatically create a viable charging system.
Adding storage does not automatically solve a capacity problem.
Generating electricity locally does not automatically mean that generation is available when the transport operation requires it.
Infrastructure emerges only when these elements are engineered around a defined operating requirement.
Start with the real location
For that reason, the most useful starting point is usually not another abstract discussion about future mobility.
It is a real site.
A port.
An airport.
A logistics centre.
A depot.
A motorway environment.
A transport corridor.
Then the questions become concrete.
What happens here every day?
What is changing?
Where does the energy requirement emerge?
What limits the operation?
Which existing assets can be used?
Which intervention improves the system?
And does the technical case also produce an economic one?
That is where a concept becomes an infrastructure decision.
Homer needed gods to move the story forward.
Modern infrastructure has a less dramatic requirement:
the right capability, at the right location, supported by a system that actually works.