Terminal equipment file
The cranes at your terminals, on file once a year.
Ship-to-shore and yard cranes at the container terminals on your list, counted, typed and attributed to a maker where the design shows.
Spec table
- GSD
- ≤0.5 m (VHR)1
- Cadence
- Annual2
- Platform
- VHR satellite / aerial
- Spectral
- RGB
- Unit of delivery
- one terminal, one numbered inventory file
- Fields
- crane count, type, maker where visible, rough height and reach3
- Dimensions
- modelled by photogrammetry, comparison grade4
01. What is in the file
Exhibit A
- Deliverable
- A.1Terminal inventory
- Format
- one file per terminal
- What is in it
Crane count by type for each terminal in your list: ship-to-shore cranes and yard cranes, with yard cranes split by the gantry type visible. Delivered once a year after the pass, for your competitive file.
- crane count
- type
- STS
- RTG / RMG
- Cadence
- annual, after the pass
- Deliverable
- A.2Maker attribution
- Format
- field in the inventory
- What is in it
Each crane carries a maker where the design cues allow one, and a flag where they do not. Attribution is a reading of the machine's visible shape, never a confirmation, and uncertain units are marked uncertain rather than forced into a name.
- maker
- uncertain
- Cadence
- with the inventory
- Deliverable
- A.3Rough dimensions
- Format
- field in the inventory
- What is in it
Height and outreach per ship-to-shore crane, modelled from the imagery by photogrammetry. Good for comparing one terminal's fleet against another's. Not a certified survey.
- height (m)
- outreach (m)
- Cadence
- with the inventory
- Deliverable
- A.4Terminal map
- Format
- GIS layer
- What is in it
The terminals on your list with the crane positions, so the inventory can be checked against your own records and opened alongside territory maps.
- terminal
- crane position
- Cadence
- with the inventory
- Deliverable
- A.5Method note
- Format
- one page per delivery
- What is in it
The pass date for each terminal, the imagery used, and every crane that was occluded or attributed with low confidence, so a gap in the file is a stated gap.
- pass date
- imagery used
- occluded
- low confidence
- Cadence
- each delivery
Exhibit A. What one delivery holds.
02. How it works
Exhibit B
01In
Terminal list in
You send the ports or the region you want filed, or a list of terminals with their operators. Terminals we cannot cover with suitable imagery are named back to you before anything is agreed.
02Pass
Annual pass
A very high resolution satellite or aerial pass over each terminal, collected once a year. The date depends on when clear imagery is available at each one.
03Read
Count, type, attribute
Cranes are found and counted, typed, and attributed to a maker where visible design cues allow. Dimensions are modelled from the imagery.
04Out
Inventory out
A numbered inventory file per terminal, plus the terminal map and the method note.
Exhibit B. From your terminal list to the file.
03. Limits
Exhibit C
- Condition
- Occlusion
- Effect on the file
- Cranes under canopies, behind stacked containers or partly hidden by a vessel may be missed or under-specified.
- In the delivery
- The method note lists them.
- Condition
- Attribution is a reading
- Effect on the file
- The maker is read from visible design cues. Where two makers' machines look alike from above, the crane is flagged uncertain.
- In the delivery
- It is never presented as confirmed.
- Condition
- Dimensions are modelled
- Effect on the file
- Height and outreach come from photogrammetry and are good for comparing fleets.
- In the delivery
- They do not replace a survey, and they should not go into a tender document.
- Condition
- Half a metre is the floor
- Effect on the file
- At ≤0.5 m a crane is many pixels across and easy to find. Small fittings, spreader details and fine markings are not resolved.
- In the delivery
- Anything that depends on them is left out.
- Condition
- Annual, not live
- Effect on the file
- The file is a snapshot aligned to the pass.
- In the delivery
- A crane delivered or scrapped after the pass shows up at the next one.
- Condition
- Coverage follows tasking
- Effect on the file
- Whether a terminal can be filed depends on VHR imagery being available for it in the year.
Exhibit C. Operating envelope.
04. Why the installed-base file has holes
Your file of who has which cranes where is built from trade-press photos, terminal press releases, order announcements and whatever sales brings back from visits. A terminal gets a row when someone happens to have a source, so the file is full where you already sell and thin where a competitor is winning.
Ask how many cranes a rival runs at a given terminal and the honest answer is a guess. Flying someone to every quay to count is not a budget line.
05. Who it's for
For
- Market-intelligence and competitive-analysis leads at port equipment makers who keep an installed-base file.
- Analysts building territory lists for sales and product teams from that file.
Not for
- Teams that need a certified survey of a crane's dimensions.
- Live tracking of crane moves or terminal throughput.
- Confirmed manufacturer identification for a legal or contractual purpose.
- Condition, age or maintenance state of a crane. The imagery shows the machine, not its service history.
06. Questions from the evaluator
Q1Is maker attribution guaranteed?
No. It is read from visible design cues and flagged uncertain when the maker cannot be told apart reliably.
Q2How accurate are the dimensions?
They are modelled from photogrammetry. Useful for comparing fleets, not survey grade, and no accuracy figure is promised.
Q3What happens to cranes that are partly hidden?
They may be missed or under-specified. Each one is listed in the method note so you can see where the file is weak.
Q4How current is an annual file?
It matches the pass date for each terminal. It is not a live feed.
Q5Does it cover every port?
No. Coverage depends on VHR imagery being available for that terminal in the year. Terminals we cannot cover are named before you commit.
Q6How do we check it against what we already know?
Take the terminals where you hold firm records of the fleet and compare them first. The terminal map and method note are laid out so that comparison is quick, and any mismatch is worth raising in the pilot.
Q7Can we use the data in our own files and materials?
Use and ownership terms for the delivered inventory are written into the contract before work starts. The imagery sources keep their own licences.
Q8How is it priced?
A pilot is scoped on the terminals and region you choose. You get a written scope to take through your own approval.
End of file
Open your terminal file.
Send the ports you track and we will say which terminals we can cover.