Notice Information
Notice Title
Journey Advice and next best action Proof of Concept (PIN only)
Notice 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).
Lot Information
Lot 1
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).
Notice Details
Publication & Lifecycle
- Open Contracting ID
- ocds-h6vhtk-03834b
- 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
Buyer & Supplier
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
Further Information
Open Contracting Data Standard (OCDS)
View full OCDS Record for this contracting process
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-03834b-2022-11-10T16:22:06Z",
"date": "2022-11-10T16:22:06Z",
"ocid": "ocds-h6vhtk-03834b",
"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": "ocds-h6vhtk-03834b",
"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": "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).",
"lots": [
{
"id": "1",
"description": "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"
}