DfT - Passenger Demand Forecasting System - Phase 3 Development

Description

Pre-market engagement DfT previously commissioned an independent model and code reviews of the current system, MOIRA2.2. The language and functionality were independently reviewed. User lessons learnt was also collated, particularly for use in franchising. These studies were: • Source code review ITS Leeds - 2017 • Source code review for DfT - 2017 • MOIRA2.2 review - 2017 • Lessons learned by Systra on CrossCountry franchise - 2018 The PDFC also commissioned BJSS to run a Discovery Phase. This Discovery project validated the existing MOIRA 1 & 2.2 systems (models, algorithms and technology platform). It then explored whether the creation of a new system was required to address un-met or new needs. Having identified the users and understood their needs, it also identified the scope and potential options and solutions for further exploration in a follow up stage”. DfT hired a Business Analyst who built a catalogue with the Business Requirements of the new system. Work done so far Modelling users have developed a good understanding of how existing models work, and the use cases for where an improvement of its functionality is crucial. The Discovery phase identified who the users would be and the needs of those users, while the limitations of the existing system have been explored. The Core Algorithm and the Report Generator of the new system has been built in C# and they are accompanied by their technical documentation. DfT has documented the business requirements for the new system. The Core Algorithm and the Report Generator have been built in C#. The MOIRA 2 Specification for Production documents can be used for the development. The MOIRA 2 Source Code (Delphi) is also available. The current MOIRA2.2 model will stay fully operative and DfT will do parallel testing while developing and enhancing each component separately. Which phase the project is in Not applicable Existing team Project Leader, Digital Architect, Rail Modelling Team, MOIRA 2.2 working group, IT Specialist Address where the work will be done Department for Transport, Great Minster House, 33 Horseferry Road, London, SW1P 4DR. The suppliers will work from their offices. Meetings will be on Microsoft Teams Working arrangements Supplier staff may work remotely or at supplier premises, and most meetings with DfT staff or other stakeholders will be via Microsoft Teams. Provide more information about your security requirements: Baseline Personnel Security Standard (BPSS) Latest start date 2024-12-16 Enter the expected contract length: 1 year, 2 months Write the term or acronym: DfT Write the term or acronym: PDFS Write the term or acronym: PDFC Write the term or acronym: NR Write the term or acronym: TOCs Are you prepared to show your budget details?: Yes Indicative maximum: £350,000 Confirm if you require a contracted out service or supply of resource Contracted out service: the off-payroll rules do not apply Summary of work DfT is developing a new Passenger Demand Forecasting System. The intention is that this system will replace the current MOIRA 2.2. The ambition is to own a tool that could be deployed and used widely to provide a common basis for rail demand modelling, forecasting and appraisal, providing wider opportunities to use, develop, support and maintain the product. The project includes the development of the User Interface module that will work with the existing Core Algorithm and the Report Generator modules (already developed – Opportunities To Travel Report to be in the project) based on the Business and Functional Requirements of Rail Industry. Where the supplied staff will work London Where the supplied staff will work No specific location (for example they can work remotely) Why the work is being done • The User Interface module to be part of an integrated system that is yet to be built and it will replace the current MOIRA 2.2. The Core Algorithm and the Report Generator modules have been built and the code will be updated according to the latest MOIRA 2.2 updates. • Think about innovative ways to achieve modern and more user-friendly modules than the current MOIRA 2.2 system; • These modules should be built according to a list of Business and Functional Requirements; • All the code to be written with regards to coding best practice with full annotation, full model documentation and quality report. • Need for a system that DfT owns with no reliance on proprietary code The business problem you need to solve DfT are looking to develop a system that will replace the existing legacy system (MOIRA 2.2). The expectation is to have a user friendly, fast and reliable system that will be attractive to users. DfT want the system to follow the development best practices and the GDS standards. First user type: The new system will be used by different stakeholders for a wide range of purposes, mainly: • DfT and NR will use the new system to determine the value for money of rail infrastructure and rolling stock schemes. • Bidders for rail franchise competitions can use the system to show the effects their proposed timetables may have, and DfT can use it to assess those bids. • TOCs will use the system to optimise the train timetable for their network, and to decide which types of trains should be used for each service. Most users will use the system to predict demand and passenger revenue.