Planning

Journey Advice and next best action Proof of Concept (PIN only)

LONDON NORTH EASTERN RAILWAY LTD.

This public procurement record has 1 release in its history.

Planning

10 Nov 2022 at 16:22

Summary of the contracting process

The London North Eastern Railway Ltd. is planning a procurement process for the provision of Journey Advice and next best action Proof of Concept IT services. The aim is to address customer pain points related to ticket journey advice and provide timely, personalised information to enhance the travel experience for rail customers. The procurement stage is currently planned, and interested parties can access detailed project information via the provided questionnaire and appendix. The planned future notice date for this opportunity is 12th December 2022.

This tender from London North Eastern Railway Ltd. offers opportunities for businesses providing IT services, consulting, software development, and Internet support. Companies specialising in innovative solutions for improving customer experiences in the rail industry would be well-suited to compete for this tender. The procurement process involves engaging with third parties to develop a proof of concept or pilot to address identified pain points and enhance customer decision-making during rail journeys.

Find more tenders on our Open Data Platform.
How relevant is this notice?

D3 Tenders Premium

Win More Public Sector Contracts

AI-powered tender discovery, pipeline management, and market intelligence — everything you need to grow your public sector business.

Notice Title

Journey Advice and next best action Proof of Concept (PIN only)

Notice Description

LNER is continually looking for innovation that can address our customer pain points through their journeys on Rail. This innovation can be stimulated by LNER under our innovation remit, to look for solutions to pain points we have identified, and then canvass the market for an adaptable solution. If there is no solution apparent, LNER has budget to investigate with third parties a proof of concept or pilot to validate our hypothesis. Pain Point description: Ticket journey advice was highlighted as a pain point by station managers at LNER stations. Customers arriving at stations are not always clear on the most appropriate train service, carrier and platform for their journey. There is further evidence commissioned by our research and insight team that rail customers are not clear on the validity of a ticket and which services it is appropriate for. This pain point applies to both non disruption and disruption periods on the rail network. However disruption brings a greater need for clear information in the moment regarding alternative travel options. LNER believes that information sources do exist to advise customers, but the key information needed to allow a customer to decide the next best action for their journey is not surfaced to the customer in an easy to digest manner. Challenge statement: "How might we provide our customers with simple, personalised and timely information in the moment on their journey with using the ticket in their hand, so they can make the best travel decisions appropriate to their needs at that moment"

Lot Information

Lot 1

Solution outline: We are open to proposals for a pilot system in the following formats: * No-code solution (to fit tablet or large-scale digital screen), with demonstratable proof that the data sources/extracts supporting the no code application are available and could be accessed in real time if a live working prototype was subsequently developed. * An application prototype (to fit tablet or large scale digital screen), which has integration to key rail systems to obtain the necessary data. Both the above approaches should be able to demonstrate an easy to understand user interface which allows a ticket holder to be fully informed and make the best decision for their onward journey. Attached with this PIN is further information from LNER on the systems we believe are available to address this challenge and a simple ideation of the type of information the customer interface may well convey. Any use of public or private data sources to address the challenge should be compliant with GDPR rules around use of personalised data. An agile approach to accurately delivering requirements to time, cost and quality, in addition to having the scope and capability to further develop at pace, as requested by LNER, is a fundamental requirement. Project completion and success criteria: The award of this pilot/proof of concept to any party does not infer a commitment to purchase a long term solution from the provider. The successful applicant is expected to report in line with our innovation key measures below :- Desirability - Do users have a need for this service and how important is that need. What does a successful implementation look like for users. (pre pilot research and pilot feedback) Feasibility - Can it fit in with LNER existing core business operations and are any new capabilities requiring to be built to deliver to meet the objectives. Viability - Is there an implementation (based on Pilot feedback) which is sustainable for LNER to implement or would likely lead to a viable business case in the future. Period of Pilot / Proof of concept: For this challenge, LNER are open to suggestions and reasoning from the applicant on the length of time needed to measure success. For initial guidance, LNER would not expect a pilot period longer than 3 months (which should allow opportunity for a number of 'disruptive' rail days).

Publication & Lifecycle

Open Contracting ID
ocds-h6vhtk-03834a
Publication Source
Find A Tender Service
Latest Notice
https://www.find-tender.service.gov.uk/Notice/031894-2022
Current Stage
Planning
All Stages
Planning

Procurement Classification

Notice Type
Planning Notice
Procurement Type
Standard
Procurement Category
Services
Procurement Method
Not Specified
Procurement Method Details
Not specified
Tender Suitability
Not specified
Awardee Scale
Not specified

Common Procurement Vocabulary (CPV)

CPV Divisions

72 - IT services: consulting, software development, Internet and support


CPV Codes

72000000 - IT services: consulting, software development, Internet and support

Notice Value(s)

Tender Value
Not specified
Lots Value
Not specified
Awards Value
Not specified
Contracts Value
Not specified

Notice Dates

Publication Date
10 Nov 20223 years ago
Submission Deadline
Not specified
Future Notice Date
12 Dec 2022Expired
Award Date
Not specified
Contract Period
Not specified - Not specified
Recurrence
Not specified

Notice Status

Tender Status
Planned
Lots Status
Planned
Awards Status
Not Specified
Contracts Status
Not Specified

Contracting Authority (Buyer)

Main Buyer
LONDON NORTH EASTERN RAILWAY LTD.
Contact Name
Not specified
Contact Email
anke.tymens@lner.co.uk
Contact Phone
Not specified

Buyer Location

Locality
YORK
Postcode
N/A
Post Town
Not specified
Country
Not specified

Major Region (ITL 1)
Not specified
Basic Region (ITL 2)
Not specified
Small Region (ITL 3)
Not specified
Delivery Location
Not specified

Local Authority
Not specified
Electoral Ward
Not specified
Westminster Constituency
Not specified

Open Contracting Data Standard (OCDS)

View full OCDS Record for this contracting process

Download

The Open Contracting Data Standard (OCDS) is a framework designed to increase transparency and access to public procurement data in the public sector. It is widely used by governments and organisations worldwide to report on procurement processes and contracts.

{
    "tag": [
        "compiled"
    ],
    "id": "ocds-h6vhtk-03834a-2022-11-10T16:22:06Z",
    "date": "2022-11-10T16:22:06Z",
    "ocid": "ocds-h6vhtk-03834a",
    "description": "Applicants are requested to complete the questionnaire at https://forms.office.com/r/XLxZHLiSVi to give initial insights. Please contact anke.tymens@lner.co.uk to request an appendix to provide greater guidance on the known information sources which LNER have assessed to be available and the access endpoints. The developer API guidance for each endpoint is not provided and suppliers will require to assess suitability themselves with the information providers. The appendix provided is for guidance and suppliers are able to submit their own designs and data access points as part of their proposal.",
    "initiationType": "tender",
    "tender": {
        "id": "DN1425",
        "legalBasis": {
            "id": "32014L0025",
            "scheme": "CELEX"
        },
        "title": "Journey Advice and next best action Proof of Concept (PIN only)",
        "status": "planned",
        "classification": {
            "scheme": "CPV",
            "id": "72000000",
            "description": "IT services: consulting, software development, Internet and support"
        },
        "mainProcurementCategory": "services",
        "description": "LNER is continually looking for innovation that can address our customer pain points through their journeys on Rail. This innovation can be stimulated by LNER under our innovation remit, to look for solutions to pain points we have identified, and then canvass the market for an adaptable solution. If there is no solution apparent, LNER has budget to investigate with third parties a proof of concept or pilot to validate our hypothesis. Pain Point description: Ticket journey advice was highlighted as a pain point by station managers at LNER stations. Customers arriving at stations are not always clear on the most appropriate train service, carrier and platform for their journey. There is further evidence commissioned by our research and insight team that rail customers are not clear on the validity of a ticket and which services it is appropriate for. This pain point applies to both non disruption and disruption periods on the rail network. However disruption brings a greater need for clear information in the moment regarding alternative travel options. LNER believes that information sources do exist to advise customers, but the key information needed to allow a customer to decide the next best action for their journey is not surfaced to the customer in an easy to digest manner. Challenge statement: \"How might we provide our customers with simple, personalised and timely information in the moment on their journey with using the ticket in their hand, so they can make the best travel decisions appropriate to their needs at that moment\"",
        "lots": [
            {
                "id": "1",
                "description": "Solution outline: We are open to proposals for a pilot system in the following formats: * No-code solution (to fit tablet or large-scale digital screen), with demonstratable proof that the data sources/extracts supporting the no code application are available and could be accessed in real time if a live working prototype was subsequently developed. * An application prototype (to fit tablet or large scale digital screen), which has integration to key rail systems to obtain the necessary data. Both the above approaches should be able to demonstrate an easy to understand user interface which allows a ticket holder to be fully informed and make the best decision for their onward journey. Attached with this PIN is further information from LNER on the systems we believe are available to address this challenge and a simple ideation of the type of information the customer interface may well convey. Any use of public or private data sources to address the challenge should be compliant with GDPR rules around use of personalised data. An agile approach to accurately delivering requirements to time, cost and quality, in addition to having the scope and capability to further develop at pace, as requested by LNER, is a fundamental requirement. Project completion and success criteria: The award of this pilot/proof of concept to any party does not infer a commitment to purchase a long term solution from the provider. The successful applicant is expected to report in line with our innovation key measures below :- Desirability - Do users have a need for this service and how important is that need. What does a successful implementation look like for users. (pre pilot research and pilot feedback) Feasibility - Can it fit in with LNER existing core business operations and are any new capabilities requiring to be built to deliver to meet the objectives. Viability - Is there an implementation (based on Pilot feedback) which is sustainable for LNER to implement or would likely lead to a viable business case in the future. Period of Pilot / Proof of concept: For this challenge, LNER are open to suggestions and reasoning from the applicant on the length of time needed to measure success. For initial guidance, LNER would not expect a pilot period longer than 3 months (which should allow opportunity for a number of 'disruptive' rail days).",
                "status": "planned"
            }
        ],
        "items": [
            {
                "id": "1",
                "deliveryAddresses": [
                    {
                        "region": "UK"
                    }
                ],
                "relatedLot": "1"
            }
        ],
        "communication": {
            "futureNoticeDate": "2022-12-12T00:00:00Z"
        }
    },
    "parties": [
        {
            "id": "GB-FTS-13680",
            "name": "London North Eastern Railway Ltd.",
            "identifier": {
                "legalName": "London North Eastern Railway Ltd."
            },
            "address": {
                "locality": "York",
                "region": "UK",
                "countryName": "United Kingdom"
            },
            "contactPoint": {
                "email": "anke.tymens@lner.co.uk"
            },
            "roles": [
                "buyer"
            ],
            "details": {
                "url": "http://www.lner.co.uk",
                "classifications": [
                    {
                        "scheme": "TED_CE_ACTIVITY",
                        "id": "RAILWAY_SERVICES",
                        "description": "Railway services"
                    }
                ]
            }
        }
    ],
    "buyer": {
        "id": "GB-FTS-13680",
        "name": "London North Eastern Railway Ltd."
    },
    "language": "en"
}