Department for Business, Energy and Industrial Strategy (BEIS)

UK SBS IT17443 BEIS NMO Digital Service - Beta

Incomplete applications

3
Incomplete applications
2 SME, 1 large

Completed applications

12
Completed applications
9 SME, 3 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Tuesday 24 October 2017
Deadline for asking questions Tuesday 31 October 2017 at 11:59pm GMT
Closing date for applications Tuesday 7 November 2017 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work Regulatory Delivery (part of BEIS) requires a team to carry out the Beta phase of the NMO testing and certification service. The work will include travel (at least one day per week) to Teddington to work closely with the NMO engineers.
Latest start date Monday 4 December 2017
Expected contract length 6 months with the option to extend for up to an additional 2 months
Location London
Organisation the work is for Department for Business, Energy and Industrial Strategy (BEIS)
Budget range £700,000 to £780,000 excluding VAT

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done Regulatory Delivery (RD) has legal responsibility for overseeing the UK’s system of weights and measures and offers a range of technical testing and certification services to manufacturers and other businesses across the world. The testing and certification services enable businesses to test products, launch/export them legally, and ensure quality. This range of services offered by RD forms the NMO service. The NMO service is world class and widely recognised to be one of very few top authorities on weights and measures in the world. These services are available through Gov.uk.
Problem to be solved Customers of Regulatory Delivery’s technical testing and certification services (NMO service) struggle to access the services using the existing digital portal, which is not compliant with the Digital Service Standard. We are aiming to make it easier for users to apply for services, including submitting information to NMO, receiving regular updates on progress and obtaining certificates for their products. We want to improve our service efficiency through better management information, as well as improve the way we communicate to our customers.
Who the users are and what they need to do UK/International businesses need to be able to: view the full suite of NMO services, apply for certifications, view the process/progress of certifications/testing, view fee estimates, view processes for submitting products/prototypes for testing, upload documentation as part of the certification process, and create an account.
RD officials need to be able to: notify customers of application progress, manage customer documentation, send documentation to customers, and communicate costs to customers.
Early market engagement
Any work that’s already been done An initial Discovery has been conducted covering a number of RD services delivered on a commercial basis, including NMO. We decided only to take forward work on NMO services into an Alpha stage. During the 12 week Alpha we produced end-to-end prototypes for the ‘enquire’, ‘apply’ and ‘assess’ phases of the product certification technical service. The prototypes were developed assuming that the service would not be hosted on GOV.UK. However, following research during Alpha, the digital service will now be hosted on GOV.UK. As such, prototypes will need to be reworked in line with GOV.UK styling and functionality.
Existing team The existing team consists of a Product Owner, Service Manager, and internal staff with expertise in subject areas and knowledge of user communities. The NMO team are based in Teddington and the supplier would be expected to work from Teddington at least one day a week to facilitate good access to the NMO team.
Current phase Beta

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place 1 Victoria Street, London, with a minimum of one day a week to work from our Teddington office (Stanton Avenue, Teddington, Middlesex, TW11 0JZ)
Working arrangements The team must be co-located at 1 Victoria Street, London and adhere to BEIS normal working hours (09:00 - 17:00). Suppliers must comply with BEIS travel and subsistence policy. There is a possibility of travel for user research purposes, which could be anywhere in the United Kingdom (BEIS will meet any additional travel costs incurred away from the London office for the purposes of user research or attendance at other BEIS sites). Travel to Teddington should be expected at least one day per week.
Security clearance Baseline Personnel Security Standard (BPSS) clearance required.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions

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
  • Demonstrate how you will apply your skills and expertise to… (Please do not answer this question as it will not be scored)
  • Deliver digital services that meet the GDS Digital Service Standard criteria and pass GDS service assessments and how this will ensure the successful delivery of this project.
  • Design and build a service which meets user needs and follows GDS design patterns and how this will ensure the successful delivery of this project.
  • Conduct user research and testing remotely and how this will ensure the successful delivery of this project.
  • Develop production ready code for private/public Beta releases from Discovery and Alpha outputs (e.g. low-fi/hi-fi prototypes) and how this will ensure the successful delivery of this project.
  • Develop prototypes (wire frames/coded prototypes/etc.) iteratively via user testing/research and how this will ensure the successful delivery of this project.
  • Use automated (testing) environments and implement continuous integration, delivery & deployment and how this will ensure the successful delivery of this project.
  • Demonstrate how you will prioritise key content and features using metrics and analytics and how this will ensure the successful delivery of this project.
Nice-to-have skills and experience
  • Demonstrate how you will apply your skills and expertise to… (Please do not answer this question as it will not be scored)
  • Develop the service using Drupal 8 (or equivalent) and how this will ensure the successful delivery of this project.
  • Implement Government as a Platform services (Notify and PaaS) and how this will ensure the successful delivery of this project.
  • Upskill client staff and how this will ensure the successful delivery of this project.
  • Research/test permissions and access levels of user accounts how this will ensure the successful delivery of this project.
  • Map and test the end-to-end journey from Google into the new service and how this will ensure the successful delivery of this project.
  • Identify key performance indicators for the service and the tools to measure them and how this will ensure successful delivery of this project.
  • Carry out an accessibility audit of the service and how this will ensure the successful delivery of this project.

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 3
Proposal criteria
  • Approach and methodology
  • Technical solution
  • How the approach or solution meets user needs
  • Estimated timeframes to complete the work
  • Team structure (with roles and responsibilities)
  • How risks and dependencies are identified and approaches to manage them
  • Approach to maintaining control, transparency and quality
Cultural fit criteria Demonstrate how you will work transparently and collaboratively with the BEIS Regulatory Delivery team when making decisions throughout this project
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Presentation
Evaluation weighting

Technical competence

75%

Cultural fit

5%

Price

20%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Would the authority consider working arrangements of one day per week at the BEIS London office, one day per week at Teddington and 3 days per week remote within an agile methodology, using regular communications e.g. Skype, Slack etc where required? No, the team must predominantly be based at the London office, with at least 1 day per week in Teddington. There is the possibility of travel for user research purposes.
2. Could you confirm the context in which you are referring to “testing” in Box 4. Is this a) testing of the service with users or b) technical testing of developed software? We are referring to a) testing of the service with users.
3. Ordinarily we would expect the majority of prototyping work (referred to in box 6) to be carried out prior to the beta phase. Are there any particular areas of uncertainty where you believe further prototyping are required? Some functionality will need to be revised to ensure it is in line with GOV.UK styling and features, this may require additional prototyping/testing. However, the core journey will remain unchanged.
4. Could you confirm that you are referring to prioritisation of requirements (user stories) through findings from user testing activities referred to in the final essential criteria? And that you are referring to metrics and analytics gathered through that user testing? We are referring to metrics and analytics of data in general. Some of this will come through user testing (e.g. 70% of users said they need to…) and some will come from data produced during private Beta and public Beta (e.g. 25% of users spent more than 2 minutes on a certain page). The data will then be used to prioritise features and content, this may not necessarily be a whole user story (e.g. adding clarifying text to a page).
5. Map and test the end-to-end journey from Google into the new service and how this will ensure the successful delivery of this project: Are you referring to a) use of analytics tools to test the end to end user journey for the service or b) what a user journey initiated through a search engine (such as google) might look like? We are referring to b) what a user journey initiated through a search engine (such as Google) might look like
6. Hello team, Which incumbent supplier completed the Alpha ? and also was it GDS assessed. Are they applying to the beta ? The information relating to the identity of the incumbent supplier is not required to produce a bid for this requirement.

A BEIS service assessment has been carried out in accordance with the GDS Service Standards, which was passed. A GDS assessment was not required due to the number of transactions falling below the GDS threshold.

We are unaware of which suppliers are applying for beta.
7. Has the Alpha been developed using Drupal8, and does BEIS expect the Alpha code to be repurposed for GOV.UK, or thrown away? Is Drupal8 the preferred technical solution for the Beta (and if so, can you give the reasons why)? The Alpha prototype was developed using HTML5, JavaScript (ECMAScript 5), and CSS versions 2, and 3. We would like this repurposed if possible.
Drupal 8 is not a preferred solution. Drupal 8 or equivalent is a nice to have but is not a preferred technical solution.
8. Is this project expected to be delivered outside of IR35? This is unable to be determined at this time as it is possible for contractors who are both in and out of scope of the off payroll working rules to be engaged through DOS. The successful supplier / contracting authority will need to check the status in accordance with the HMRC online tool prior to contract commencement. A link to this tool can be found here: https://www.tax.service.gov.uk/check-employment-status-for-tax/setup
9. Can you give us an indication of why Drupal has been named as a suitable product? Drupal 8 is not a preferred solution and has not been named as a preferred product. Drupal 8 or equivalent is a nice to have but is not a preferred technical solution. BEIS have used Drupal to deliver another of RD's digital services. The CMS functionality offered by Drupal reduces RD's dependence on external developer resource.
10. How many users of the service will there be? 200 - 400 initially. We expect this to increase year on year.
11. How many individual customer requests are expected to be dealt per year with once the service is in operation? 600 - 800 initially. We anticipate that the number of requests for the technical services will increase year on year following the launch of the new digital service.
12. How many documents updates are expected per year once the service is in operation? If this is referring to documents uploaded to the service, we expect this to be 600 - 1200. We expect this to increase year on year.
13. Is there any existing data that needs to be migrated into the service? There is no data to be migrated to the new service.
14. At a high level what are the existing workflow steps within the certification process? Customers make enquiries to the NMO team through various means (email, telephone, online form) to enquire about the technical services and discuss testing. Once the team has the relevant information, they can provide a cost estimate to the customer. If the customer accepts the cost estimate, further emails and calls take place to discuss the delivery of the instrument (if required), the testing schedule, and any further documentation that may be required. A member of the team is assigned to carryout the required testing. The customer is notified following the testing (pass, fail, reschedule testing).
15. What weighting do you give to mobile vs laptop / desktop usage? We expect the majority of applications will be completed via desktop given the technical detail required. However, the solution should be responsive so it can be used on mobile devices as well. This will be researched continuously throughout Beta.
16. It was mentioned that you struggle to access the current service? What do you think has been the main issues up to now? Users struggle to find and complete the relevant form on GOV.UK. The supporting information on GOV.UK needs updating to better meet user needs.
17. Does the service require multilingual support? The MVP does not require multilingual support. However, as customers of the service expand into overseas territories, this may need to be revisited. This will be monitored throughout Beta.
18. Do you envisage a requirement for online payments? The MVP does not require pay support as this will happen outside the system. However, we have engaged with the GDS Pay team and will continue to engage with them throughout Beta. We will also continue to research user needs relating to online payments. We do not expect online payments to be delivered by the end of the contract.
19. Hi, do you have any documents available from the Discovery and Alpha please? And any working prototypes that can be shared? We have user stories and a high level service map which we will share with the shortlisted suppliers successful in reaching the assessment stage. We can also share screenshots of the prototypes.
20. You stated you're looking for Drupal 8 experience. Does the Beta have to be built using Drupal 8? Does it have to be built with open-source technologies? We propose to use our COTS product which utilises open-source technologies, and we'd like to know if BEIS are comfortable with this approach (like the other Government departments and agencies we work with!) The Beta does not have to be built using Drupal 8 and we are open to equivalent products, but the solution must be compliant with the Digital Service Standard and with the Technology Code of Practice. BEIS are comfortable with the COTS product as an equivalent.