.png)
The Checklist for Transportation Companies and Integrators.
Key Points
- The performance of a passenger information system depends as much on the management software (CMS) as it does on the display hardware. These two components must work in perfect synergy.
- Opt for a platform that is truly hardware-agnostic. A CMS compatible with LED, LCD, and e-paper displays offers greater flexibility, avoids dependence on a single manufacturer, and makes it easier to meet the requirements of public tenders, which prioritize functional criteria over a specific manufacturer.
- Cybersecurity certifications are only truly relevant if they are up to date and validated by independent audits, not merely displayed on a vendor’s website.
- Before any deployment, integrators and installers should ensure that the CMS supports the required data sources (GTFS-RT, API, XML, JSON, CSV) to avoid integration issues.
- A vendor’s real-world experience is an excellent indicator of reliability. Deployments at recognized agencies and verifiable results are often more revealing than a long list of features.
- Beyond passenger information, a high-performance CMS can also serve as an internal communication platform for effectively disseminating messages to frontline staff and operational teams.
Hardware is important, but it’s the CMS that makes the whole system work.
When a transit agencies or integrator evaluates a new system, the first questions usually concern the hardware: screen type, brightness, protection rating, certifications, or even the manufacturer. However, a digital signage network is never static. As it evolves, it often combines multiple technologies—such as LED, LCD, and e-paper displays—from different manufacturers. It is the CMS that ensures the consistency of this ecosystem and enables all this equipment to work together within a single platform.
The CMS is what ensures the longevity of your network. While hardware will inevitably be replaced or supplemented over the years, the CMS must be able to evolve alongside it. By being “hardware-agnostic,” it allows for the integration of displays from different manufacturers and using different technologies without jeopardizing investments already made.
This is not just a best practice, but a requirement for most public agencies. In Canada, the United States, and the United Kingdom, public procurement rules generally require that requests for proposals be based on performance criteria and functional requirements rather than on a specific manufacturer or brand. This approach promotes fair competition and allows for the evaluation of equivalent solutions.
A CMS that functions optimally only with a single manufacturer can quickly become a constraint. Agencies then risk unintentionally tailoring their specifications to a specific supplier or having to accept lower performance from other compatible solutions. Conversely, a “hardware-agnostic” CMS allows them to remain compliant with procurement requirements while giving integrators the freedom to choose, for each project, the most suitable manufacturer and display technology, without being limited by the software.
Unifying communications on a single platform
This same advantage extends far beyond passenger information. Many transit agencies still use a separate platform for their internal communications, whether to broadcast safety instructions, work schedules, or notices intended for frontline staff. This approach involves managing two systems, two vendors, two training programs, and two administrative environments.
A modern CMS can bring these needs together within a single platform. In addition to informing passengers, it allows for the distribution of internal communications to employees from the same interface, the same content library, and the same administrative tools. The result is simplified management, greater consistency in communications, and reduced operational complexity.
Here are seven questions transit agencies, along with the systems integrators and installers that support them, should ask before choosing a passenger information system.
1. Is the platform truly hardware-agnostic?
Many CMS systems are designed around a single display technology and then adapted to support others. In practice, this makes a significant difference. A truly “hardware agnostic” platform natively supports LED, LCD, and e paper displays, regardless of the manufacturer, through a single interface and a single management workflow. Whether it’s a solar powered bus shelter or an LCD screen in a subway station, all equipment is managed in the same way.
For integrators, this greatly simplifies deployments. A single CMS means a single training session, a single commissioning process, a single management platform, and a single point of support—rather than having to master multiple environments depending on the display technology installed.
Conversely, some manufacturers tie their displays to their own CMS. This approach may suit organizations that wish to source from a single vendor, but it limits long-term flexibility. Technology choices, upgrades, and software development then remain closely tied to that manufacturer’s roadmap.
Ask the vendor: Is it possible to manage LED, LCD, and e-paper displays from a single instance of the CMS, using the same content templates, right now, not in a future version?
2. Is the platform cloud-native, and where is it hosted?
The term “cloud-based” is often used for marketing purposes, but it guarantees neither the quality of the infrastructure nor the level of service. The questions to ask are simple: where is the platform hosted, what infrastructure does it run on, what availability guarantees are offered, and what happens to the data if the provider changes its hosting environment?
A platform hosted on enterprise-grade cloud infrastructure generally offers better redundancy, greater resilience, faster incident response, and proven security mechanisms. For a passenger information network, these elements are essential to ensuring business continuity, even during an outage or a major incident.
Ask the provider: On which cloud platform is your CMS hosted? In which region is the data located? What level of availability (SLA) do you guarantee? Is this information documented in writing?
3. Are the security certifications valid, up-to-date, and independently audited?
Many providers highlight certifications such as ISO 27001 or SOC 2. However, not all such claims are equal. Sometimes the certification covers a different entity within the company, a different product, or is simply no longer valid. In other cases, it may be a simple declaration of compliance without an independent audit.
For transportation companies and public agencies, this is not merely a marketing ploy. Security certifications are often an eligibility requirement in procurement processes and serve as an important indicator of the maturity of a vendor’s cybersecurity practices.
Beyond the certificate itself, it is also important to verify the frequency of security audits, the existence of a penetration testing program, and the presence of an information security management system (ISMS). A vendor with truly mature practices will generally be able to provide this information without difficulty.
Ask the vendor: Can you provide a copy of your ISO 27001 or SOC 2 certificate, specifying the entity and products it covers, as well as the date of the most recent audit? Do you conduct regular penetration tests, and do you have a documented ISMS?
4. Does it integrate well with the data you already have?
A CMS never operates in a vacuum. It must integrate with the data that already powers your operations, including real-time schedules and arrivals (GTFS and GTFS-RT), service alerts, weather data, and content from internal systems. A platform that supports only proprietary formats or requires custom development for each new integration adds an ongoing workload to your IT team, as every change to a data source requires new adjustments. Conversely, a CMS that supports open standards and major exchange protocols facilitates integrations, reduces maintenance costs, and allows the network to scale more easily.
Ask the vendor: Which formats and protocols are natively supported (GTFS, GTFS-RT, XML, JSON, CSV, REST API, etc.)? Can the CMS integrate with the systems and tools we already use?
5. What does the installation and commissioning ecosystem look like?
This question is just as important for transit agencies as it is for integrators. A CMS vendor that relies on an established network of partners for installation and commissioning, rather than a single in house team, is generally able to deploy projects more quickly and provide better on site support. For integrators, the quality and openness of this ecosystem are often a deciding factor. A CMS that collaborates with multiple partners allows each to showcase its expertise while offering transit agencies greater flexibility in choosing their service providers.
Questions to ask the provider: Who handles the installation and commissioning of equipment in my region? Do you work with local partners, and can I communicate directly with them?
6. Does the provider have a track record of actual, verifiable deployments?
The presence of client logos on a website is a good starting point, but it does not constitute proof. Ask for concrete examples: How many networks does the provider currently operate, in which markets, and for how long? Experience matters. A provider that has been operating in the public transit sector for several years has generally already encountered and resolved most of the challenges associated with deploying and operating a passenger information system. This experience often translates into a more mature platform, proven processes, and better support.
Ask the provider: Can you provide me with three references from transit agencies I can contact, ideally ones comparable in size and complexity to mine?
7. Will the platform evolve with your needs?
The cost of a CMS isn’t limited to its purchase price. A platform that locks you into a single hardware vendor, a proprietary data format, or a rigid template system can quickly become more expensive in the long run.
A passenger information system is bound to evolve. New display technologies, new languages, new data sources, or new operational requirements will inevitably be added over the years. The real question, therefore, is whether these changes can be implemented easily using standard configuration, or whether they will require custom development and incur additional costs.
Ask the vendor: If we want to add a new type of display, a new language, or a new data source in two years, what will be the steps, timelines, and associated costs?
“A transit agency doesn’t just deploy a network of displays. It builds a relationship with a platform that will need to evolve over a decade or more, regardless of the display technologies and manufacturers it chooses over time. We designed ITEStransit with this reality in mind: a single, multi-technology, hardware-agnostic platform compatible with LED, LCD, and e-paper screens, hosted on Microsoft Azure and backed by a very high level of security, notably thanks to its ISO 27001 certification. This is what transit companies and their integration partners need to make an informed and sustainable decision, while delivering a better experience for passengers and employees.”— Richard Fortin, President, ITESMEDIA
Frequently Asked Questions
What is a Passenger Information Display System (PIDS) CMS?
A Passenger Information Display System (PIDS) CMS is the software platform that enables the management, scheduling, and real-time distribution of schedules, arrival estimates, service alerts, and other content across a transit agency’s entire digital signage network.
Why is hardware agnosticism important for a Passenger Information Display System (PIDS) CMS?
Transportation networks often use multiple display technologies, such as LED screens at outdoor stops, LCD screens in stations, and solar-powered e-paper screens in locations where power or connectivity is limited. A hardware-agnostic CMS capable of supporting these different technologies within a single platform avoids the need for multiple systems and allows transit companies to choose the display technology best suited to each location, rather than the one dictated by software limitations.
Can a passenger information system CMS also manage internal communications for employees?
Yes. A modern CMS is not limited to information intended for passengers. The same platform can also display safety instructions, work schedules, service alerts, and other communications on screens intended for employees. By centralizing internal communications and passenger information within a single administrative interface, the CMS becomes a true communication hub for the entire organization.
What certifications should a transportation company require from a CMS provider?
At a minimum, look for a provider with valid, up-to-date, and independently audited ISO 27001 or SOC 2 certification. Also request a copy of the certificate and verify the date of the most recent audit, the relevant legal entity, and the specific products or services actually covered. A mention on the provider’s website alone does not constitute proof of compliance.
Who should evaluate the CMS: the transportation company or the integrator?
Both. The transit agency must ensure that the CMS meets its requirements for security, reliability, data integration, and scalability. For their part, integrators must confirm that the platform is compatible with the display technologies they deploy, that it integrates easily with existing systems, and that it is supported by a network of partners capable of handling installation, commissioning, and long-term support.
Ready to compare?
If you’re evaluating a passenger information system for your transit agency or looking for a hardware-agnostic platform for your integration projects, contact the ITEStransit team to discuss your needs and discover how our solution can help you achieve your goals.