Department for Transport, Buses and Taxis Division

Bus Open Data Service – Alpha / Beta

Incomplete applications

8
Incomplete applications
4 SME, 4 large

Completed applications

7
Completed applications
3 SME, 4 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Tuesday 26 June 2018
Deadline for asking questions Tuesday 3 July 2018 at 11:59pm GMT
Closing date for applications Tuesday 10 July 2018 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work Please find detail via the following link:

https://docs.google.com/document/d/1iyLU8W0XjpmZDsbb0Iz66__NzwwC31coV3aJfZ32bNI/edit?usp=sharing
Latest start date Monday 6 August 2018
Expected contract length 12 weeks for alpha/4 weeks GDS service assessment. Beta to be determined
Location London
Organisation the work is for Department for Transport, Buses and Taxis Division
Budget range £350,000 - £600,000 (this is for Alpha alone and is inclusive of VAT and T&S) Indicative costs are required for full project delivery through to Beta live, although these will fall outside of the evaluation.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done To develop a new Bus Open Data service to transform the way in which bus operators and local authorities open up data including:
- Routes and timetables
- Fares and ticketing
- Real time information
- Punctuality information
The portal will be the one-stop-shop for operators of local bus services to index links to data files. Third party developers will then access this data and integrate it with their own journey planning applications.
This requirement is for an Alpha/Beta to develop/test prototypes and determine the final solution for beta including technical feasibility, build and maintenance costs and any key risks.
Problem to be solved The final output will be a Bus Open Data portal that operators across England can use to index data, including:
• Build upon the user personas, creating backlogs and determining acceptance criteria.
• Develop and test prototypes or wireframes through UX research
• Develop/test chosen option, demonstrating it’s technical, contractual and legally feasibility
• Identify what we need to do in Beta, highlighting risks/dependencies
• Provide indicative costs for full system development
• Consider tools and training required by the industry to adopt solution
• Mobilise bus industry and open data communities to share technical knowledge, best practice and expertise.
Who the users are and what they need to do Users are

• bus operators of varying sizes including small/medium sized operators and the BigFive bus companies and staff ranging from data managers to CEO.
• local transport authorities including bus data managers/analysts
• technology suppliers providing transport data management systems(Trapeze, Omnibus, Mentz)
• data aggregators including not for profits (Traveline) and private companies (ITO World, Transport API)
• central government, including Bus Service Operators Grants caseworkers, policy officers, analysts and statisticians, local politicians and councillors;
• third party developers including journey planners and app developers.
• end users or bus passengers including the elderly, the young and disabled travellers.
Early market engagement N/A
Any work that’s already been done Discovery reports, that include As Is and To Be process maps, user personas and options report. These will be made available in a redacted form to all successful shortlisted suppliers

The discovery phase has provided a set of user personas which will be provided to suppliers who are successful in reaching the second stage, i.e. written proposals. It is worth noting that some additional work may be required with the user personas to determine acceptance criteria and translate the stories into a development backlog.
Existing team The supplier will be working with DfT project manager, policy lead and team leader (service manager) plus stakeholders from the bus industry, local authorities and other users.
Current phase Alpha

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place We would expect the appointed supplier to be able to work at Department for Transport offices when required and approximately 2-3 days a week.
Address: Department for Transport, Great Minster House, 33 Horseferry Road, Westminster, London, SW1P 4DR.
The team should also have the ability to travel to other locations and agencies as required to meet users. It is also worth noting that DfT facilities do not include user testing labs therefore the successful bidder will need to have access to their own user testing labs. Please reference your arrangement in the proposal.
Working arrangements The team will need to work 5 days a week for 12 weeks. There will be a requirement to complete a Government Digital Service Assessment towards the later stages of the alpha, requiring an additional 4 weeks also.

Some events or additional meetings with users may be needed around the country. Expenses will be paid in accordance with DfT rates. Exact milestones will be determined once an Supplier is appointed
Security clearance BPSS, evidence of which will be required as part of the proposals at second stage.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions N/A

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • Specialist capability and experience in transforming business critical, legacy technology and processes into efficient modern solutions.
  • Experiencedelivering projects using Agile project management methodology, delivering a minimal viable product/proof of concept through Alpha successfully delivering a robust product into 'live' on behalf of a Government department
  • Proven ability to support a flexible way of working, making late changes to plans and re-formulating to maintain project progress against tight timelines.
  • Proven service design and development demonstrating technical expertise in delivering a digital service particularly in the public sector.
  • Have demonstrable experience of complex technical investigation to inform future project stage
  • Demonstrable experience of carrying out user research with a diverse mix of users and stakeholders.
  • Demonstrable evidence of excellent planning, coordination, communication and project management skills.
  • Demonstrable evidence of incorporating latest technologies to enhance product specifications, resulting in increased functionality and improved user experience
  • Demonstrable experience delivering digital projects in line withGDS Service Design Manual and Service Standards, including Security Health Check and Penetration Testing, culminating in successful completion of the GDS service assessment.
  • Demonstrable evidence of a robust risk management process, including risk identification, mitigations and governance.
  • Evidence of working with 3rd parties to develop standard interfaces and data exchange portals
  • Suppliers must understand the open data principles and have experience of designing open data platforms.
  • Demonstrate evidence of using NCSC’s cyber security principles and using a risk-based approach.
Nice-to-have skills and experience
  • Knowledge/experience of the bus industry including bus scheduling/ fares across England (outside of London) and provision of real time information.
  • Experience of working with users and stakeholders at all levels organisations across the public and private sector, ideally within the Transport Sector.
  • An understanding of the bus open data policy area and approach the government and the data community are taking on open data and the benefits this provide.
  • Demonstrable experience of utilising Open source technologies to affect change.
  • Demonstrable evidence where innovative solutions have been applied to assist in project delivery.

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 6
Proposal criteria
  • Identify the approach and methodology to the Alpha project planning and delivery, identifying the main stages and activities proposed at each stage. (10%)
  • Detailed resource plan – demonstrating how in-house, supplier and external resource will be used and at what stage (5%)
  • Clear demonstration of how the approach or solution meets user needs including for data providers, data users and secondary users such as BSOG caseworkers (5%)
  • Clear demonstration of how the approach or solution meets the policy goals and objectives (5%)
  • Clear demonstration of how they’ve identified risks and dependencies and offered approaches to manage them (5%)
  • Estimated timeframes for the work (5%)
  • Demonstration of value for money (5%)
  • Demonstration of how the requirements of other areas, such as bus operators and local authorities will be integrated into the project. (5%)
  • Suppliers must demonstrate experience in designing and developing end to end solutions (including front and back end) through a range of previous work for customers on a similar scale. (5%)
Cultural fit criteria
  • Experience of working as a team with our organisation and other suppliers (2.5%)
  • Experience of transparent and collaborative decision making (2.5%)
  • Experience of taking responsibility for their work and resolving problems effectively (2.5%)
  • Evidence where status quo has been challenged resulting in an improved final outcome (2.5%)
  • Demonstrable evidence of working with clients with low technical expertise (2.5%)
  • Experience of working with Government departments (2.5%)
  • Evidence demonstrating an ability to transfer knowledge & skills to Civil Servant team members (2.5%)
  • Evidence of strategic thinking striving to deliver best possible solution/concept possible. (2.5%)
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Presentation
Evaluation weighting

Technical competence

50%

Cultural fit

20%

Price

30%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. is it possible to share a full copy of the requirements? Outputs of Discovery will be made available to short listed suppliers at second stage. This supplementary information will provide a steer as to projects direction of travel
2. following evaluation of the evidence questions, when will a proposal doc be issued and response needed back by? will you be holding a Q&A session? We are looking to request the formal written proposals after the initial sift on 17.07.2018, with a response due on 24.07.2018. We are not anticipating holding a Q&A session
3. Have any commitments been made to specific technologies? If so, what? The Department remains technology agnostic at this point. However, there is a commitment that the web based Bus Open Data Portal will be hosted on Gov.Uk
4. If DfT is supplying a project manager, does that mean that DfT's PM will be responsible for delivery management and outcomes of the team, rather than the supplier? The Department would expect that a parallel resource would be available in both supplier and DfT project teams, working collaboratively on overall project delivery.
5. Was the discovery undertaken by an external partner? If so, who? Yes – the contract was undertaken by Deloitte, collaborating with the Open Data Institute.
6. Which data standards will be accepted from users, and therefore required standards for data validation. NeTEx /TXC /Atco-CIF? BSOG. Does the client foresee the platform directly consuming ETM data to validate? TXC for route and timetable data, NeTEx for fares and tickets data and Siri SM for Real Time Information.
7. Hi, 1. We note that your desired start date is Monday 6th August with a response deadline for the pre-qualification questions of Tuesday 10th July. Please could you clarify when you expect to contact shortlisted suppliers to submit their full proposal? 2. Does the Department have a preference regarding whether the solution can be delivered using (an) existing product(s) or whether the Discovery phase identified that a bespoke solution is required? Many thanks The Departments indicative timeline shows we will re-engage with succesful shortlisted suppliers on Tuesday July 17, there are some dependancies on meeting this which may have an impact on the date. The Department expects the service will be built as a bespoke product rather than an off the shelf solution. However, customisation of a COTS solution would be considered if appropraite
8. Roles and team shape for Alpha that a supplier should provide? The Department expects the supplier to provide sufficient resource to support a typical Alpha project, with roles including (but not limited to):
Delivery Manager
Agile Coach
Business Analyst
Content Designer
Data Architect
Designer
Developer
Security Consultant
Service Manager
Technical Architect
User Researcher
Web Operations

The Supplier will be expected to define the roles as part of their submission at second stage
9. will the new platform utilise tfl's current open standard? do you have a particular technology in mind ie open source? do you have a specific hosting in mind? Woudl the platform ustilise a current API specification or would the expectation be that one is developed? TfL are a stakeholder and are shaping our policy however we have not committed to using specific TfL standards. It is expected that the service would be cloud based/ free to access. The host will be GOV.UK. We have not yet determined whether APIs will be required and so will only determine a specification if required.
10. - What is the commercial basis of the commercial proposal? Is that a Time & Material, Capped Time & Material or Fixed price? - Can you confirm that the this procurement process is covering Alpha & Beta and that the value of the call-off contract will reflect the total budget including Beta? Therefore, can we presume that the published budget range would be for the initial Alpha statement of work? As per published advert the commercial proposal required is capped time and materials. The Call Off award will be for both Alpha and Beta phases, with the outline budget set out in the advert for the Alpha phase only
11. Could you please describe at a high-level the different data sources relevant to this requirement in terms of 1) volume 2) variety (ie CSV, relational database, unstructured data) 3) Velocity ( ie how often the data sources update, weekly batch, overnight, daily, hourly, near real-time, real time)? the Bus Open Data portal will simply serve as an index for data that exists and is hosted by operators (rather than a host itself). The details requested will be made available to shortlisted suppliers at second stage.