01
Where is the load building?
Station, track, train and time.
APTA 2026Meet us at TRANSform & EXPO · Chicago · October 4–7
Tagus Orbit APC · Automatic Passenger Counting
Passenger counts, with the context to act on them.
Stationary and onboard APC in one software layer. Real-time counts, occupancy, sensor health, alerts and data quality for transit agencies and technology partners.
The challenge
The operational blind spot
Passenger demand changes by the hour. The numbers alone don’t say whether a quiet reading means quiet service or a disconnected sensor.
02
Which sensors need attention?
Connection, fault and tamper states.
03
Which readings need investigation?
Quality signals before anything is reported.
Counts say how many. Operations also need to know whether to trust them.
The platform
Stationary and onboard APC, one software layer
Stationary
Platform-mounted sensors with station and track context.
Onboard
Bus and train door sensors with vehicle and trip context.
Real-time counts
Train In and Train Out by station, track and train, with point-level inspection.
Occupancy & events
Boarding and alighting alongside train load and vehicle-event context.
Sensor health
Every sensor’s state and timestamp. The one that needs attention stands out.
Alert workflows
Detect, notify, investigate, verify recovery. Rules agreed per deployment.
Data quality
Transmission patterns, quality diagnostics and control charts before reporting.
Open integration
A REST API to agency systems and technology partners.
Case in point
The Chicago solution
Counts, sensor condition and data quality side by side, the way operators and analysts use them.
Captured views from the Chicago solution dashboards, not a live feed. Metric definitions are confirmed during technical scoping.
Architecture
From sensor to agency systems
01
Sensor inputs
Stationary and onboard APC
02
Ingestion & processing
Counts, occupancy and quality context
03
Operations & history
Dashboards, alerts and stored events
04
REST API
Agency systems and technology partners
Cloud
A hosted environment with an agreed access and operations model.
On-premises
An agency-controlled environment with an agreed infrastructure and support model.
Conceptual architecture. Containerized services; protocols, schemas, authentication and latency are confirmed during integration design.
Next step
Start with a focused pilot
One operating area. Agreed acceptance criteria. Evidence you can review with operations and IT.
- 01
Scope
Choose a station, corridor or vehicle group, and the sensors and integrations in play.
- 02
Measure
Counts, data delivery and fault handling against a baseline agreed up front.
- 03
Review
Walk through the results together with operations and IT, then decide what’s next.
Let’s explore your station or fleet.
Request a Chicago solution walkthrough or a partner integration session.
contact@tagusorbit.com