Platform
One platform runs every screen.
MP.TV is the software half of the managed service: the CMS your team touches, the data engine riders depend on, and the monitoring layer that never sleeps.
MP.TV CMS
Powerful for us. Simple for your team.
Three things your team does every day, from one console.
Build & design
Compose layouts from images, video, HTML, data feeds, and 100+ visual apps, then build looping playlists and timeline campaigns from a template library, with nesting, per-item duration, and transitions. No developer needed for day-to-day changes.
Schedule & target
Schedule by time of day, day of week, or date range so rush-hour messaging, weekend service notes, and holiday takeovers publish and expire themselves. Geo-regions inject content by location, plus triggers from RSS, APIs, and IoT sensors.
Run & prove
Content changes reach cellular-connected displays in seconds, while depot Wi-Fi handles heavy media overnight; every screen caches content and keeps playing through dead zones and outages, then re-syncs when it reconnects. Automated, scheduled proof-of-play reports show exactly what played, where, and when.
More in the CMS
No-code interactivity. Touch, keyboard, and timeout rules for wayfinding kiosks and trip planners.
One CMS, every panel. LCD, LED, OLED, and e-paper from one console, with fleet segmentation and multi-agency support.
Emergency override. One action replaces every screen on the network.
Roles that match your org. Granular per-task, per-content, per-player privileges.
Advertising & revenue. A built-in subsystem sells and schedules ad inventory alongside rider info.
On the glass
What a screen actually shows
The same CMS composes every display type. Illustrations of what a screen carries:
Illustrative layouts with sample data. The MP.TV CMS composes any layout, on any panel.
Real-time data engine
From raw feed to rider trust
The hosted engine ingests your real-time feeds on a 20-second cycle, reconciles predictions against static schedule data, and derives arrival, next-stop, and transfer information, published to displays over encrypted MQTT and to your back office over a REST API.
Deep native integrations with the major US CAD/AVL and prediction platforms (Avail, Vontas, TripSpark, and Novus), plus GTFS-RT breadth that picks up Swiftly, TripShot, TransLoc, Passio, ETA, Spare, and standard GTFS-RT/SIRI feeds, go beyond generic APIs, and multi-modal consolidation merges intercity and local services into one coherent picture at shared terminals.
Sources
GTFS-RT
vehicle positions
SIRI
arrival predictions
CAD / AVL
Avail · Vontas · TripSpark
MP.TV engine
publishes over MQTTS · REST
To the glass
Onboard
buses · rail
Wayside
shelters · totems
Terminal
departure walls
Back office
operations · reporting (REST)
KUBERNETES · EMQX MQTT · POSTGRESQL · ALL TRAFFIC TCP 443
Open by design
Partner, adapt, and only then build
MPM is standards-first as an operating principle: open standards and existing integration patterns come first, and custom development happens only when the market genuinely lacks a better option. Our displays run third-party software, and our software runs on third-party hardware. Your team, or any front-end developer, can build visual applications against published documentation and run them side by side with ours, and we will write the app for an agency that has no cycles for it.
The MP.TV ecosystem
Every level works. Each level up does more.
No MPM product requires another. Start with one thing, on one route, alongside equipment you already own, and scale on evidence instead of commitment.
- Open level
- GTFS / GTFS-RT on third-party screens and Windows devices: a working passenger-information system.
- Native level
- Vontas, Avail, TripSpark, and Novus APIs on MPM controllers and displays: richer data, deeper diagnostics, RDMC, the plugin layer, and configuration push. Both are supported. One is better.
We say the honest limit out loud: the further from our own OS and hardware, the more the deeply integrated capabilities, RDMC, the ADA-button voice engine, and the sensor layer, fall away.
Standards & protocols
The CMS client runs on
Change CAD/AVL vendors, run your own developers against the platform, or run MPM software on hardware you already own. Standards are how you avoid being trapped in a ten-year commitment.
Offline-first
Never a blank screen
The CMS compiles everything a display needs, layouts, schedules, route awareness, geofencing, and downloads it to the controller inside the screen. That controller then runs the show locally, whether the internet is there or not. A web-based signage player goes dark the moment the connection drops; an MPM display does not, because the decisions already happened on the device.
We have had screens run offline for six months and never stop showing the right content. Some hospitality customers deliberately disconnect their menu boards for a year and plug them back in only when the menu changes. On a bus through tunnels and dead zones, that is the difference between a screen that works and one that flickers blank all day.
What an outage actually costs: real-time schedule deviation and new service alerts, both picked up the instant connectivity returns. The system reconnects aggressively; nothing else degrades.
Offline behavior
- Scheduled content playbackContinues
- Zone layouts & rotationsContinue
- Route-aware & geofenced contentContinues
- Real-time schedule deviationResumes on reconnect
- New service alertsResumes on reconnect
- ReconnectionAggressive auto-retry
RDMC · Fleet monitoring
We see the fault before the complaint
RDMC watches every screen in revenue service around the clock: which are healthy, which are degraded, and which have dropped offline and for how long. It doesn't just flag faults, it acts on them. When a display goes dark, RDMC can recover many faults remotely, often before anyone in the field notices. Off-grid units report in too: solar charge state, battery voltage, and temperature stream from every solar stop.
Customer login · rdmc.mpmedia.tv↗RDMC · FLEET HEALTH
EVERY DISPLAY REPORTS IN · FAULT DETECTION · REMOTE DIAGNOSTICS · WEATHER + VANDALISM SENSING
01 Identify
See what needs attention
One dashboard shows which screens are healthy, which are degraded, and which have dropped offline and for how long, across every agency and panel type. Faults and stale data raise alerts to your team, not a call from the field.
02 Diagnose
See what's on the glass
Pull a live screenshot and device health from any player to understand a fault from your desk, without dispatching a tech to the stop.
03 Respond
Fix it from the console
Recover many faults remotely, and push content, settings, and on-screen apps to any player or the whole fleet. Most fixes never need a truck roll.
Proof-of-play & uptime records
Scheduled reports to your inbox
LCD, LED, OLED & e-paper, one console
The sensor layer
Every display is a sensor platform
Monitoring hardware built into each display streams eight telemetry channels to RDMC, so brightness adapts to daylight, enclosures heat and cool themselves, announcements ride above ambient noise, and an impact at 2 AM pages a human before the sun comes up. Off-grid sites report battery and solar charge state on the same channel, and LED walls are configured and health-checked entirely over the cloud.
Ambient light
··lux
auto-brightness scaling
Enclosure temp
··°F
heating & cooling triggers
Shock / vandalism
··g
impact alerts to RDMC
Ambient noise
··dB
dynamic ADA audio volume
EVERY MPM DISPLAY
MONITORED
FROM THE INSIDE
REPORTING TO RDMC
8 telemetry channels · 24/7
GPS + cellular
··sats
live location · geo-fence triggers
LTE signal
··dBm
connectivity watchdog
Door GPIO
··
next-stop & door-side awareness
Power & solar
··%
battery + charge-controller state
Security & compliance
Built to pass your IT department
Message Point Media has successfully achieved SOC 2 compliance, and the platform has passed security review at some of the largest transit agencies in the country. Procurement teams: everything below is available with documentation on request.