Find a Tender
planned
Official procurement procedure
Journey Advice and next best action Proof of Concept (PIN only)
IT services: consulting
software development
Internet and support
UK
Published value
Not published
Submission deadline Not published
Lots published1
Procurement Executive Summary
AI & Search Synopsis
Generated from official OCDS record
Tenderline Synopsis: London North Eastern Railway Ltd.: "Journey Advice and next best action Proof of Concept (PIN only)". Published status: planned. Published value: Value not published. 1 published lot. Submission deadline not published. See the official notice for participation instructions.
| Contracting Authority | London North Eastern Railway Ltd. | Scope & Categories | Not published | Submission Window | planned No deadline published |
|---|---|---|---|---|---|
| Submission Gateway | Direct notice route | Legal Basis & Regime | Standard procurement | Estimated Value (exc. VAT) | Not published |
Bidder Intelligence · Authority Profile: London North Eastern Railway Ltd.
Market Analytics
Derived from OCDS awards & bid statistics
Published history for London North Eastern Railway Ltd.. These figures describe retained records, not a forecast of bids or a measure of buyer bias.
Published-to-award variance
Not availableInsufficient comparable data
Competition Density
4Bids / Report
Supplier ConcentrationNo estimate
Insufficient attributable awardsNo concentration estimate availablePayment Terms
Check noticePublished terms
Coverage: 5 active published awards; 1 bid reports (which may be per lot). Supplier values exclude multi-supplier awards, frameworks and DPS, and use GBP only. They are published award values, not payments. Published-to-award variance compares single-lot, single-award, single-supplier GBP procedures with explicitly non-framework/non-DPS status; increases remain in the average. Unpublished data stays unknown. Awarded suppliers are winners, not all bidders.
Procedure terms
Contracting AuthorityLondon North Eastern Railway Ltd. | Procedure methodNot published | Procurement categoryNot published |
Statusplanned | Framework / DPSNot published | CompetitionNot published |
Above thresholdNot published | Legal basisNot published | Tender period startsNot published |
Clarification deadlineNot published | Electronic submissionNot published | Submission languagesNot published |
Published10 Nov 2022, 16:22 GMT | Last source update10 Nov 2022, 16:22 GMT | Recurring procurementNot published |
ClassificationIT services: consulting, software development, Internet and support | ||
Delivery area UK | ||
OCIDocds-h6vhtk-03834b | ||
What is being bought
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).
What changed
From the official release history
- Status changed to planned
10 Nov 2022, 16:22 GMT - Official notice release published
10 Nov 2022, 16:22 GMT - Buyer information updated
10 Nov 2022, 16:22 GMT
Lots and requirements (1)
Published by the contracting authority
- Lot 1 · #1Individual lot title not publishedplannedPublished valueNot publishedWe 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).Contract periodNot publishedEligibilityNot publishedOptions / renewalNot published
Timeline
- Procedure published
10 Nov 2022, 16:22 GMT
Commercial outcome and competition
AwardsNo award published |
ContractsNo contract published |
Bid statisticsNo aggregate bid statistics published |
Buyer and organisations in this procedure
London North Eastern Railway Ltd.
Contracting authority GB-FTS-13680Documents (0)
Official links; attachments are not copied
No linked documents are published
Related procedures (0)
No related procedures published