Naviquate

Situations where alternatives are preferable

• If account-based ticketing (ABT) modernization is the primary program
  • Consider a ticketing specialist rather than a broader data/RTPI suite.
• If independently validated security/compliance posture is a strict procurement requirement
  • Vendors with public trust centers, SOC 2 reports, and clearly listed certifications may reduce procurement friction.
• If strategy focuses on publishing open data and relying on the ecosystem for passenger UX
  • Authorities may prefer investing in high-quality GTFS/NeTEx/open RT feeds and partnering with consumer apps rather than owning the passenger UX stack.
• If operations are primarily outside the UK & Ireland
  • A vendor with a more global footprint and regional references may provide stronger localization and references.

Red flags in the buying process to watch

• The lack of clear public pricing, SLAs, uptime commitments, and security certifications on public pages
• Potential for a services-heavy delivery model and dependency on change-order services for feature delivery

Current limitations acknowledged by the vendor

• No explicit public “known issues” page or status page was found in accessible sources.

Features on the roadmap

• Not publicly documented in accessible sources.

Scale limitations

• Not publicly benchmarked; buyers should request performance references for:
  • Peak query load
  • Real-time prediction latency
  • High-volume multi-operator integration

Security or compliance gaps

• Public certification posture is unclear (SOC 2 / ISO not clearly stated). This may cause procurement delays for security-conscious buyers.

API limitations or integration constraints

• Not documented publicly; should be validated through technical workshops.

Competitive advantages supported by available evidence (limited)

• Emphasis on UK & Ireland standards
  • Novus Data Manager documents support for NaPTAN, TransXChange, ATCO CIF, and EBSR workflows.
• Integrated portfolio
  • The product family provides a path from data management through real-time passenger information and outward publicity channels.

Differentiation vs competitors (balanced)

• Differentiators
  • Local market focus (UK & Ireland) and a rebrand intended to clarify market positioning
  • Ownership by Modaxo, providing parent-group scale and corporate backing
• Areas where competitors may have advantages
  • Masabi: focused ticketing platform with extensive account-based ticketing integrations
  • IVU/INIT: broader international operational control and ITS references

Vendor/legacy case-study quotes (vendor-published)

• trentbarton (operator) case study includes a Systems Analyst describing operational goals; Trapeze states Novus-RT consolidated real-time inputs and produced departure predictions used across displays, apps, and third-party systems. Quote excerpt:
  • “we want to run our service the best we can [and] do what we can to encourage people onto the buses.” (Trapeze case study about Novus-RT)
• Gloucestershire case study highlights improvement versus schedule-only predictions. Quote excerpt:
  • “Previously we had RTPI running on schedule information… we would get people asking why buses weren’t at stops when the display units said they should be.” and later “Now… the new systems are so much more accurate, using real-time data from multiple sources…” (Trapeze case study)

Third-party critical mention (negative; not a consumer review, but an external report signal)

• A technology analysis memo includes a critical statement about Trapeze Novus projected running times, indicating “Trapeze Novus projected running times are not accurate and results in poor schedule optimization and on-time…” (context: agency assessment; not necessarily Naviquate’s current RTPI stack, but relevant to the broader Novus ecosystem perception).

• Vendor materials state trentbarton implemented Novus Real Time in late 2020.
• Described outcomes include consolidating real-time feeds, generating departure predictions, and providing data to support local authority funding bids.

• The case study presents qualitative outcomes and links to funding applications; it does not provide independently audited ridership uplift, detailed prediction-accuracy metrics, or a documented ROI methodology.

• Funding-application enablement is plausible and relevant, but buyers should request:
  • Before/after KPI definitions
  • Accuracy measurement approach (for example, error metrics vs observed arrivals)
  • Data governance processes (ownership of authoritative datasets)

• The case study describes a transition from schedule-based predictions to real-time predictions using multiple data sources.

• The narrative describes passenger frustration under schedule-only predictions and claims improved accuracy after introducing real-time feeds.

• The narrative aligns with general RTPI improvement patterns, but lacks:
  • Accuracy statistics
  • Coverage metrics (proportion of stops/routes with live data)
  • Change-management detail (operator compliance, AVL device quality)

• Novus Data Manager (schedule / registrations / stops / timetables data management)
• Novus Realtime (RTPI generation and distribution)
• Novus Journey (trip planning / passenger information)
• Novus Publicity (multi-channel passenger information)
• Novus Connect (collaboration/coordination)
• Novus Ticketing (payments/ticketing)

• Local transport authorities (LTAs) and regional authorities
• Public transport operators (bus, and potentially multi-modal)
• UK public-sector procurement contexts (e.g., Digital Marketplace listings still reference legacy Trapeze branding for Novus components)