Description of the procurement
Solution offering which can consume inputs from multiple sources and
• share insights through dashboards, threshold-based alerts, commenting, storyboards, infographics. This should highlight for each user the most meaningful changes in the business for them, with root causes, predictions and prescriptions given their role and context;
• produce outputs which can be consumed by applications (via API’s, files, data-streams), end-users and business processes;
• support end-users in receiving data which they can consume on an ad-hoc, scheduled basis which will provide actionable insights;
• work with end-users to develop/adapt new/improved real time monitoring and historic data reporting tools. Reporting outputs/dashboards accessible from different types of devices;
• machine learning routines to flag operational recommendations;
• support rapid prototyping;
• support collaboration among users through integration with digital assistants and chatbots, support within the vendor organisation;
• ingest data from multiple sources (internal and external to BÉ) via bulk/batch loading and real-time/continuous data loading through data-streams and API’s. Data should include but not be limited to:
— Automatic Vehicle Location (AVL);
— Ticketing Data;
— Siri (Service Interface for Real time Information);
— VDV, GTFS (General Transit Feed Specification), TransXchange;
— WiFi;
— Telematics-GPS;
— Other On-Bus Event Data eg tachograph, engine, fuel, Society of Automotive Engineers standard SAEJ1939 interfaces;
— Finance, HR, Schools, Customer (including customer experience);
— web and social media;
— service alerts and updates;
— 3rd Party eg AA Roadwatch, Map Data;
• Real time operational tracking which will deep dive into performance metrics via conventional dashboards and reports, which should support:
— measurement of KPI’s (against benchmarks);
— rostering optimisation;
— driver/vehicle planning and scheduling optimisation;
— capacity predictions for buses, stops in advance;
— real time passenger metrics and customer demand flattening;
— driver behaviour reports such as punctuality compliance and variations to average dwell/speed;
— fleet management;
— arrival and next trip predictions;
— end of trip layover shortfall reporting;
— load factor;
— mobility pattern analysis;
— unscheduled stops, off route events, incomplete trips for AVL/punctuality;
— reliability reporting of stop departures, trips and duty operation by operating time/day etc.;
— NTA agreed metrics.
For all reports there should be the ability to drill down from an aggregate to a detail level and filter by attributes such as day, depot, driver, route, service type allowing monitoring in real time and reporting on a periodic, quarterly and annual basis. Reports are customisable by BE and it must be possible for BE to create their own reports and export the data. PQQ response should showcase reporting and analytics capability.
Within the solution it must be possible to define workflows to trigger actions on the back on KPI metrics being within specified ranges.
Preference is a SaaS solution to support elasticity, scalability and efficient services.