Beta This is a new service – your feedback will help us to improve it.

Procurement details: DfT Report Generator for the new Rail Passenger Demand Forecasting System

6

Applications submitted

£250000

Indicative Budget

Outside scope

Off-payroll status

09 March 2023

Application Closing Date

1. Context and requirements

• About adding context and requirements:

  test

• Pre-market engagement:

  DfT have commissioned independent model and code reviews of the current system, MOIRA2.2. The language and functionality were independently reviewed. Additionally, work has been pulled together on user lessons learnt, particularly for use in franchising. These studies are: • Source code review ITS Leeds - 2017 • Source code review for DfT - 2017 • MOIRA2.2 review - 2017 • Lessons learned by Systra on CrossCountry franchise - 2018 Passenger Demand Forecasting Council (PDFC) have commissioned BJSS to run a Discovery Phase. This Discovery project validates the existing MOIRA 1 & 2.2 systems (models, algorithms and technology platform). It then explores if the creation of a new system is required to address un-met or new needs. Having identified the users and understood their needs, it also identifies and scope 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:

  Model users have developed a good understanding of how existing models work, and the use cases where an improvement of its functionality is crucial. The Discovery phase has 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 of the new system has been built in C# and it is accompanied by its technical documentation.

• 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:

  The suppliers will work on the project until a working and tested version of the module with full documentation has been delivered. Regular updates will be given to DfT every couple of weeks.

• Provide more information about your security requirements:

  No security clearance needed

• Latest start date:

  2023-04-24

• Enter the expected contract length:

  1 year

• Are you prepared to show your budget details?:

  Yes

• Indicative maximum:

  250000

• 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:

  The Report Generator development will be a waterfall or hybrid development. The aim is to develop the Report Generator using the MOIRA 2 specifications combined with the updated requirements and the user expectations. It is expected that some innovation should be applied on the top of it. The current system will be available for comparison and testing.

• Where the supplied staff will work:

  No specific location (for example they can work remotely)

• Why the work is being done:

  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 Report Generator which will work with the Core Algorithm (already developed) based on the Business and Functional Requirements of Rail Industry.

• The business problem you need to solve:

  • The Report Generator modules 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 module has been built. • 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 Requirements; • The Report Generator functionality, outputs and usability should be improved through innovation to align with current business and user reporting 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.

• First user type:

  DfT and Network Rail

• First user type:

  Bidders for franchise competitions

• First user type:

  Train operators

• Enter more details about this user type:

  As DfT and Network Rail, we need the new system to determine the value for money of rail infrastructure and rolling stock schemes, so that we decide whether to progress with the investment.

• Enter more details about this user type:

  As Bidders for rail franchise competitions need the system to show the effects their proposed timetables may have, so that DfT assess those bids.

• Enter more details about this user type:

  As Train operators we need the system to optimise the train timetable for their network, so that we decide which types of trains should be used for each service.

---

• About assessment criteria:

  test

• Select your pricing model:

  Capped time and materials

• Additional assessment methods:

  Presentation

• Additional assessment methods:

  Case study

• Describe the question and answer session:

  No question and answer session will be held for this procurement.

• Create your scoring criteria:

  3

• How many suppliers to evaluate:

  5

• Technical competence:

  70

• Cultural fit:

  10

• Social value:

  0

• Price:

  20

• Essential skills and experience:

  30

• Technical questions:

  70

• Describe the essential skill or experience:

  Provide demonstrable evidence of transport modelling experience, especially in rail.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  20

• Describe the essential skill or experience:

  Provide demonstrable evidence of developing code to a modern and open-source programming language.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  15

• Describe the essential skill or experience:

  Provide demonstrable evidence of experience in producing and maintaining technical documentation and a knowledge base.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  10

• Describe the essential skill or experience:

  Provide demonstrable evidence of experience of designing and implementing algorithms and physical data models to enable integration and reporting requirements.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  10

• Describe the essential skill or experience:

  Provide demonstrable evidence of experience in design/development of complex web systems and applications using HTML, CSS and JavaScript to create responsive web designs to WCAG 2.1 accessibility standards.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  10

• Describe the essential skill or experience:

  Provide demonstrable experience in leading or supporting projects for discovery, UX (User Experience) design, development and build stages of digital services and websites conforming to Government Digital Service standards.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  10

• Describe the essential skill or experience:

  Provide demonstrable evidence of experience in structural redevelopment and optimisation of C# and Delphi applications, including data interaction on complex webpages, forms and databases.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  10

• Describe the essential skill or experience:

  Provide demonstrable evidence of experience of delivering a service assessed against the Government Service Standard, with alignment to the Technology Code of Practice

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  15

• Describe the nice-to-have skill or experience:

  Provide demonstrable evidence of experience in working with non-technical users to describe technical solutions and agile processes in a simplified way, providing training where necessary.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  25

• Describe the nice-to-have skill or experience:

  Provide demonstrable evidence of experience in building, developing, integration and securing APIs.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  25

• Describe the nice-to-have skill or experience:

  Provide demonstrable evidence of working within a challenging and complex public-sector environment.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  15

• Describe the nice-to-have skill or experience:

  Provide demonstrable evidence of handover knowledge on system to internal staff in specialised and experience technical roles for post-implementation maintenance and support.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  15

• Describe the nice-to-have skill or experience:

  Provide demonstrable evidence in delivering conformance to the System specification and Cloud Strategies (IaaS, PaaS and SaaS) for incremental functional replacement including approach to migration/management of legacy applications.

• Enter a weighting for this skill or experience in whole numbers, for example 30:

  20

• Explain the technical question:

  Describe the specific technical approach or solution you’re proposing.

• Enter a weighting for this technical question in whole numbers, for example 30:

  22

• Explain the technical question:

  Describe the approach or methodology you’ll take to meet the buyer’s requirements. Include how you’ll manage the work and maintain quality.

• Enter a weighting for this technical question in whole numbers, for example 30:

  22

• Explain the technical question:

  Please provide demonstrable evidence on how your approach or solution meets the user and organisation needs.

• Enter a weighting for this technical question in whole numbers, for example 30:

  14

• Explain the technical question:

  Please explain how you will identify risks and dependencies and offer approaches to manage them.

• Enter a weighting for this technical question in whole numbers, for example 30:

  14

• Explain the technical question:

  Say when you can deliver the work. Break down the work into phases and say when each phase will be done.

• Enter a weighting for this technical question in whole numbers, for example 30:

  14

• Explain the technical question:

  Please provide information on how you will deliver value for money during this contract.

• Enter a weighting for this technical question in whole numbers, for example 30:

  14

• Your question:

  Provide demonstrable evidence of working as a team with our organisation and other suppliers.

• Enter a weighting for this question:

  25

• Your question:

  Provide demonstrable evidence of transparent and collaborative decision making.

• Enter a weighting for this question:

  25

• Your question:

  Provide demonstrable evidence of transparent and collaborative decision making.

• Enter a weighting for this question:

  25

• Your question:

  Provide demonstrable evidence of sharing approach, knowledge and skills with other team members and with the department by example.

• Enter a weighting for this question:

  25

---

• Publication of stage 1:

  February 23, 2023, 12:00 AM

• Clarification period closes:

  March 1, 2023, 4:00 PM

• Deadline for suppliers to submit their stage 1 responses:

  March 9, 2023, 4:00 PM

---

Clarification questions and responses

There are no questions and clarifications relating to this opportunity.

---

Help

You can contact us by email, phone or using the enquiry form (opens in a new tab) .

Email:

info@crowncommercial.gov.uk

Telephone:

0345 410 2222

CCS customer services team is available Monday to Friday, 9am to 5pm.