Possession Conflict Checker
READ + PREPARE
Checks each possession request against the timetable, other requests, and access rules the moment it is filed, and returns the conflict list to the requester while rebooking is still trivial.
RAIL & PUBLIC TRANSPORT
Punctuality is planned days before departure.
Possession conflicts, fleet availability, and delay attribution decide what the timetable can deliver. 009 rail AI agents read those records inside your operator systems for punctuality improvement and rolling stock maintenance.
YOUR PERIMETER · zero data egress
Your operating landscape
Built around the systems your teams already use.
Recon reads the records behind your operation, then shows where work slows, repeats, or waits for a decision.
Maximo, IFS, and EAM platforms
Exams, defects, work orders
Timetable planning systems
Paths, conflicts, service patterns
Possession management systems
Requests, conflicts, protections
Performance and attribution systems
Delay minutes, causes, disputes
Depot management systems
Berthing, balancing, exam slots
Wayside and fleet data feeds
Read via business systems, not control
WHERE THE HOURS GO
Possession conflicts surfacing days before the weekend instead of at filing.
Diagrams assuming availability the defect queue has already spent.
Analyst weeks consumed by attribution disputes under the performance regime.
Km-based exams drifting past due while depot slots sit unbalanced.
What gets agentified
Planning exam schedules against km accrual, depot capacity, and the diagram
Exam Planner projects each unit's exam due point from live mileage and proposes depot slots that protect the diagram, for the fleet engineer's release
Compiling shift and incident handover reports from operational records
Handover Compiler assembles the end-of-shift picture from incidents, defects, and restrictions, every line traceable to its record
What Recon maps.
Agents designed for your operation.
Delay Attribution Agent
READ + PREPARE · APPROVAL GATED
Reads delay incidents against telemetry, fault logs, and precedent, prepares the attribution with evidence attached, and holds disputed or high-value minutes for the attribution manager.
Fleet Availability Forecaster
READ + REPORT
Projects availability for the coming period from maintenance due dates, defect load, and depot capacity, and identifies which specific exams or defects put the diagram at risk.
Defect Triage Agent
READ + ROUTE
Structures incoming defect reports, assigns severity from your standards and the unit's history, merges duplicates, and routes to the responsible depot with parts references attached.
Exam Planner
READ + PROPOSE
Projects exam due points from actual kilometre accrual, matches them to depot capacity and diagram commitments, and proposes the schedule with its constraints shown, released by fleet engineering.
Handover Compiler
PREPARE · APPROVAL GATED
Builds the shift handover from incidents, open defects, TSRs, and possessions in your standard format, reviewed and released by the duty manager.
What this sector asks first.
Our delay attribution is contractually sensitive. Who decides?
Your attribution manager decides. The agent prepares the case with evidence, disputed minutes are structurally gated, and the audit trail records the basis of every attribution for later challenge.
Does this connect to signalling or train control systems?
No. The agents read business and maintenance systems. The boundary with control systems is documented in Phase 0 and enforced by access scope.
We are a multi-operator network. Whose perimeter does it run in?
Whichever entity owns the engagement, with data boundaries between operators set in the access plan. Nothing crosses those boundaries because nothing leaves the perimeter at all.
Where exactly is the boundary with signalling and train control?
Agents never touch ETCS, interlockings, or any control system. They read business and maintenance records, the boundary is documented in Phase 0, and the access scopes issued make crossing it impossible rather than merely prohibited.
Mixed operation: passenger services and heavy minerals traffic. One model or two?
One Command Center with the institutional model built per traffic type, since exam regimes, attribution rules, and planning constraints differ; the baseline reports each on its own terms. Metro operations AI and heavy-freight planning share the sovereign transport AI perimeter but hold separate rule sets.
Adjacent sectors
Recon shows where your delay minutes are manufactured.
Recon runs read-only and ends with the simulated case for your specific processes.
GET STARTED