Airports, Ports & Railways
Vision Copilot for Transport Hubs
Map cameras to the places your team manages and ask Vision Copilot about transport-specific access and passenger-area review. OrionAlerts analyses scenes over time to surface alerts, recommendations and operational scores that help you decide what to review today and what to improve next.
Illustrative photograph — not a verified customer deployment
One video platform, distinct transport responsibilities.
Airports need to separate public and controlled operational areas. Ports combine waterside access, cargo activity and vehicle movement. Railway stations face changing passenger flows and restricted operational spaces. These environments share a need for scene verification, but their security plans, authorisations and response procedures differ. Configure each deployment around its operator's actual duties.
Ask your building what needs attention. OrionAlerts maps cameras to your sites, buildings, floors, zones and rooms, analyses scenes over time, and brings the results into Vision Copilot. Search in everyday language, review alerts and recommendations, and use operational scores to guide daily decisions and improvement priorities.
Building intelligence
Your operation, mapped
Organise views around the places the team recognises. Select the location to establish the context for scene observations and Copilot questions. This example uses the shared hierarchy; map the actual site rather than inventing rooms or camera coverage.
See your operation in the structure your team uses. Organise sites, buildings, floors, zones and rooms, then map cameras to their locations. A question about reception, a loading bay or a production area starts with a recognisable place and its available camera context.
Site
Facility Site
Building
Terminal Building
Floor
Concourse Level
Zone
Access Zone
Room
Entry Area
Cameras are mapped to the selected terminal entrance or access zone so questions about the selected terminal entrance start from recognisable operational context.
Vision Copilot
Ask Vision Copilot
Ask what happened. Find where it happened. Decide what to review next. Vision Copilot lets you type questions and search available visual observations in everyday language. Use the mapped location and a relevant period to focus the conversation on the operation you manage.
Illustrative example
Question
Show observations from the selected terminal entrance this morning.
Five ways teams use this
Use cases for your operation
Bring the right location into the decision
Connect transport-specific access and passenger-area review to the building tree and its mapped cameras. The team can start with a named operational area instead of trying to remember which camera covers it, making observations easier to interpret and discuss.
Search visual observations in everyday language
Ask Vision Copilot, “Show observations from the selected terminal entrance this morning.” Use the location and review period to focus the search on relevant available observations. The purpose is to reach useful context without manually working through unrelated camera views.
Identify recurring conditions across scenes
Ask, “Which covered concourse areas show recurring congestion?” Ongoing scene analysis supports review of patterns across the available observations. Use the recurring condition to frame the next investigation rather than treating one isolated alert as the whole operational picture.
Turn analysis into an improvement decision
Ask, “Summarise the observations for the terminal operations briefing.” Review the recommendation alongside the underlying observations and the team's operating knowledge. The example below shows a practical next step; it is a suggested action for human consideration, not an automatic instruction to change equipment or procedures.
Use scores to structure the next review
Use 0–100 scores to organise attention across comparable zones within the appropriate transport context; no common airport-port-rail safety rating. Review the contributing observations and coverage before acting. The proposed dimensions for this industry are Passenger-Area Flow, Service-Area Orderliness and Controlled-Zone Practices; use the approved product methodology when demonstrating actual values.
Illustrative decision story
From scenes to decisions
Illustrative decision story — not a customer result. Observe: Congestion observations recur at one passenger interface during a particular arrival window. Ask: “Summarise the observations for the terminal operations briefing.” Suggested recommendation: Review staffing and passenger guidance with the facility operator under its approved plan. Decide: The responsible team reviews the evidence and agrees an action. Follow up: Revisit the same area and comparable period to assess observations, coverage and score movement. A subsequent change is not proof of causation.
Cameras are mapped to the places your teams manage. Ongoing scene analysis brings observations and alerts into that location context. Use Vision Copilot to ask what happened and what needs attention, review recommendations, and decide on the next action. Return to the same scope and a comparable period to assess the observations and scores after a change.
Observed
Congestion observations recur at one passenger interface during a particular arrival window.
Recommendation
Review staffing and passenger guidance with the facility operator under its approved plan.
Follow up
Revisit the same area and comparable period to assess observations, coverage and score movement.
Operational scores
See what needs attention—and what changes after action.
Bring transport-specific access and passenger-area review into a structured review with operational scores out of 100. Use the score alongside the location, period and contributing observations to decide where to focus. Compare comparable zones within the appropriate transport context only when the assessment basis is consistent; there is no common airport-port-rail safety rating.
Proposed score names and formulas are design recommendations. Demonstrate only approved product values or clearly labelled illustrative states. If no valid opportunities exist, show Not assessed — never invent a flattering percentage.
Flow
Passenger-Area Flow
Not assessed
Proposed dimension · proposal-3.2
A sampled visible occupancy or queue at a defined concourse or entry stays within the agreed operational threshold.
Readiness/orderliness
Service-Area Orderliness
Not assessed
Proposed dimension · proposal-3.2
A mapped service pathway or staging space is clear according to an agreed observable criterion.
Access practices
Controlled-Zone Practices
Not assessed
Proposed dimension · proposal-3.2
Reviewed entry into a configured perimeter, cargo or operational controlled zone follows the agreed access rule.
Score presentation context
- Period
- Comparable arrival or operating window
- Scope
- Selected terminal, port or station zones with mapped cameras
- Coverage
- Monitoring Coverage shown separately when assessment windows are defined
- Evaluated checks
- Not assessed — awaiting approved product dataset
Deployment
Start with the cameras, conditions and decisions that matter.
A useful deployment starts with a defined problem. Review camera coverage, operating hours, lighting, network capacity and who will respond to an alert. Select a small set of observable events, agree how to assess them and expand after the pilot demonstrates useful results. Test long distances, weather, crowd occlusion and night scenes. Validate each transport setting separately. Agree control-room permissions and export handling, and avoid publishing sensitive maps or security-zone layouts.
- Mapped hierarchy for pilot terminal, port or station zones
- Operator-specific security plan and response ownership
- Control-room permissions and export-handling rules
- Representative testing across distance, weather, crowding and night scenes
Standards boundary
Standards and procurement considerations
ISPS provisions relate to covered ships and port facilities; they do not certify airport or railway analytics. Aviation and railway requirements need separate operator and regulator review.
ISPS (ship and port facility security)
Scope includes applicable ships and port facilities, not every logistics site. Airport and railway requirements are separate and need operator-specific verification; no common transport AI certificate is established.
How to evaluate a pilot
What to measure in a pilot
Pilot results depend on scene conditions and event definitions. Compare reviewed alerts with representative ground-truth observations, including missed events. Track nuisance alerts and response times before setting a wider rollout target. The measures shown here are evaluation criteria, not guaranteed improvements.
Reviewed perimeter-event usefulness
Confirmed relevant perimeter or controlled-zone events divided by reviewed alerts for the defined areas, using an agreed review rubric.
Source of truth: Authorised test events and operator review logs
Count error against sampled manual counts
Difference between camera-derived occupancy estimates and manual samples for the same concourse or entry window.
Source of truth: Manual samples and camera-derived counts
Known-incident retrieval time
Time for an authorised reviewer to locate the correct terminal, port or station clip from a defined starting input such as time window and entry area.
Source of truth: Timed investigation exercises and operator records
Recommended OrionAlerts solutions
Common questions
Frequently asked questions
Does one certificate cover all three transport modes?
No. Port, aviation and railway responsibilities must be assessed separately.
Can analytics identify a dangerous abandoned object?
A supported detector may flag an object under defined conditions. It cannot establish the object's contents or intent.
Can the system control train or aircraft movement?
This scope is surveillance and human review, not operational safety control.
What is Vision Copilot?
Vision Copilot is OrionAlerts' conversational interface for asking questions and searching available visual observations. It uses the mapped operational context to help teams review what needs attention and consider relevant next steps.
Why map cameras to a building tree?
A camera becomes more useful when its view is connected to a place the team recognises. The hierarchy connects sites, buildings, floors, zones and rooms with their cameras, giving searches and operational reviews a consistent location context.
What do scores out of 100 mean?
Scores help organise review of observed conditions. Read each score with its stated assessment basis, location, period and supporting observations. A score is not a certificate of safety or compliance, and missing observations do not prove that conditions are satisfactory.
Can recommendations guide property improvements?
Recommendations can help your team identify issues to inspect and changes to assess, such as staging arrangements, access practices or camera coverage. Review the evidence and operational constraints before deciding on a change; outcomes are not guaranteed.
Can we use our existing CCTV cameras?
Compatible IP camera streams may be reused after a technical assessment. Camera position, image quality, supported stream formats, network access and available compute determine which use cases are practical. Confirm the selected cameras and deployment architecture before rollout.
How should video access and retention be planned?
Define the purpose of monitoring, authorised users, retention period and incident-review process before deployment. Discuss the required access, storage and privacy controls during the assessment and verify what the selected configuration supports. Apply your organisation's policies and the requirements relevant to your location and people being recorded.
Ask Vision Copilot about your transport hubs.
See how Vision Copilot connects a mapped area with visual search, recommendations and scores for transport hubs.


