Met Office

Digital Channels Partner 2020-22

Incomplete applications

32
Incomplete applications
30 SME, 2 large

Completed applications

24
Completed applications
18 SME, 6 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Tuesday 1 October 2019
Deadline for asking questions Tuesday 8 October 2019 at 11:59pm GMT
Closing date for applications Tuesday 15 October 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work For the last two years, the Met Office has responded to meet user needs to provide a critical public resource for weather and warnings. This has seen the creation of a new responsive website. This proposal aims to identify a partner to work with us to build on this work.
Latest start date Monday 10 February 2020
Expected contract length 2 years
Location South West England
Organisation the work is for Met Office
Budget range Whilst Met Office has some key activities, such as app support, that will require continuity of resource, the majority of activities will be defined and, resourced on a SoW basis. Met Office will work with the successful supplier to identify, scope, cost and resource activities in a timely fashion, but is looking for a supplier that has the capability to flex resource to help us meet our challenges.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done Apps:
Met Office has an ongoing requirement to support and iterate the native iOS and Android apps. Both apps are due to be migrated from their current to new data sources. Met Office will be relying on the successful supplier for the technical implementation, as well as the ongoing support.

Website: The website has recently been rebuilt to provide a new responsive site. Three major deliverables are anticipated:
1. Migration of underlying data sources to a new platform
2. Work to explore how we might expose new types of data
3. Potential transfer of Support and Delivery Capability
Problem to be solved Protect and consolidate market share in an increasingly competitive market through our Met Office digital consumer channels. This includes growing downloads, improving engagement and loyalty through continuous iterative improvement.
Who the users are and what they need to do The users of this service are any internet user, but the service is focused on UK users at home and abroad. This encompasses a broad range of personas accessing weather forecasts and other related data for a variety of reasons ranging from weather warnings to social activity planning.
Early market engagement An early market engagement event took place on 10th July 2019. The primary objective of this event was market warming.
Any work that’s already been done Apps:
Mature and already well established in the marketplace for native IoS and Android.

Website:
The website has recently been rebuilt to provide a new responsive site. The work was founded on a significant UX investment and the findings from this are still being implemented. The site will continue to iterate. A significant amount of the UX work used to deliver this has not yet been implemented.
We currently have well established backlogs and a strong, outcome-focused roadmap for the next few years.
Existing team The Met Office Digital team is responsible for maintaining and developing our consumer digital channels, including the Met Office app and websites. The team is a blend of product ownership, UX and technical skills. The makeup of the team will vary across the lifetime of the contract in negotiation with the successful supplier.
Current phase Live

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place The work will be delivered via the Met Office at Exeter.
The Met Office website is PaaS hosted and the Met Office makes extensive use of cloud based tooling and videoconferencing for the sharing of requirements, work activities and for the holding of meetings. Hence suppliers would not be expected to work primarily onsite at Exeter. However, for key stakeholder meetings and ceremonies, the supplier would be expected to attend onsite. Potential suppliers should be aware of the Exeter location of the Met Office and consider the costs and logistics of such attendance in their proposals.
Working arrangements The working arrangements will vary according to the activity. In the case of the apps, we expect that the team will operate as an offsite Kanban team, with local leadership, reporting to a Met Office product owner.

Work on the web will be led by Met Office product owner and technical leadership with the supplier aligning to the Met Office development lifecycle. As responsibility for the Website potentially moves to the supplier in the later stages of the contract, it is expected that these arrangements may vary.
Security clearance Work at the Met Office requires SC clearance, however clearance will not be required for teams that work primarily offsite. Met Office will expect that potential suppliers have robust vetting and security processes in place. This should include formal alignment to external standards or demonstrably comprehensive internal processes.

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 awareness of the market and future technology trends in web and app development with examples of how you have been able to exploit opportunities to use new technologies
  • Provide evidence of an ability to provide enterprise level insight into the strategic direction of relevant areas
  • Demonstrate experience of the ability to develop effective complex, informational, user facing websites
  • Provide evidence of a strong capability to deliver user experience design, ideally aligned to GDS principles
  • Provide evidence of expertise in accessibility, specifically WCAG compliance
  • Provide evidence of capabilities to engage with users via quantitative and qualitative user research and testing throughout the development process
  • Provide evidence of enterprise level native app development (iOS and Android) capabilities with the capacity to commit full time resources to the Met Office for app development and support
  • Provide experience in building, deploying, managing, supporting solutions on public cloud, ideally based on using AWS capabilities including serverless implementations
  • Provide strong evidence of an ability to work using agile principles and techniques
  • Demonstrate the ability to supply technical leadership with extensive app experience
  • Provide strong evidence of organisational expert level development skills in web technologies
  • Provide evidence of skills in web services (RESTful APIs and microservices)
  • Provide evidence of resources and flexibility for reach back into your organisation for additional skills such as, but not constrained to, development, UX, or product ownership
  • Evidence strong capabilities in cloud solution design, ideally on AWS including AWS Well Architected Framework
  • Evidence an organisational ability to offer 24/7 fix response for business-critical incidents across both web and app
Nice-to-have skills and experience
  • Have the ability to develop and deliver training to Met Office teams, either one to one, or one to many
  • Provide experience of Behaviour Driven Development (BDD)
  • Provide experience of the weather market
  • Provide experience with BloomReach CMS or other similar capability
  • Provide evidence of familiarity with the BEIS/GDS approvals process
  • Provide experience of public sector procurement policy
  • Provide evidence of digital advertising expertise
  • Provide evidence of representing technical/scientific data to meet user needs

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • Technical solution
  • Approach and methodology
  • How the approach or solution meets user needs
  • How the approach or solution meets your organisation's policy or goal
  • Estimated timeframes for the work
  • How they've identified risks and dependencies and offered approaches to manage them
  • Team structure
  • Value for money
  • Ability to meet security requirements included in Cyber Security Questionnaire
Cultural fit criteria
  • Alignment with Met Office behaviours
  • Alignment with Met Office collaborative working practices
  • A commitment to equality and diversity
  • A commitment to sustainable working practices
  • Have a defined knowledge transfer process and be prepared to share knowledge with internal and external personnel
  • Site visit
Payment approach Time and materials
Additional assessment methods Presentation
Evaluation weighting

Technical competence

50%

Cultural fit

20%

Price

30%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Could the Met Office clarify if they would entertain suppliers with global resource delivery models or if you will only work with on-shore suppliers? Met Office currently holds regular face to face meetings which encourages the free exchange of views and allows us to align culture more quickly. Met Office does not currently have the resources or skills to engage with nearshore (or farshore) teams directly. However, we would be open to an arrangement with a supplier who is able to provide key leadership roles in the UK (e.g. Technical Lead, Product Owner, UX Lead) whilst taking responsibility for a remote development team. In order to facilitate any liaison with remote development teams, nearshore would be preferred for working day alignment reasons.
2. Has the BloomReach CMS been implemented? Yes, the website is operational on BloomReach PaaS at V12. Met Office expectation is that responsibility for the CMS implementation will ultimately pass to the supplier. However it should be understood that planning for this is at a very early stage and further discussion with both the chosen supplier and BloomReach will be necessary before a firm decision is made.
3. Would the Met Office consider a Consortium bid? Yes.
4. Please can you advise on the timelines for the next phases in the procurement process e.g. proposal and presentation. We expect to have shortlisted to the 5 top candidates by the end of October with the formal RfP released to them by then too. The evaluation, including site visits and presentations will take place throughout November and December with a view to awarding the contract by the end of the calendar year. This timeline is subject to change.
5. Could the Authority please share the market engagement event presentation if any? Interested suppliers may request a copy of the presentation slides by emailing procurement@metoffice.gov.uk.

The deadline for requesting a copy is Tuesday 8 October 2019 at 11:59pm GMT.
6. Which supplier is currently supporting in development and UX delivery? Our current prime contractor is Landmark Information Group.
7. Do you currently have a third party delivering these services or is this a new requirement for a Digital Channels partner? Yes we currently have a third party supplier that broadly delivers the requirements as detailed.
8. Can the Met Office publish information shared at the early market engagement day on 10th July? Interested suppliers may request a copy of the presentation slides by emailing procurement@metoffice.gov.uk.

The deadline for requesting a copy is Tuesday 8 October 2019 at 11:59pm GMT.
9. Can you confirm the approved budget for this contract? We anticipate a value of £4-6million over the lifetime of the contract.
10. How often would you expect the supplier to be on site? Initial on-boarding to the successful supplier will require significant on-site presence. As part of this process, we will consider appropriate ways of working depending on different roles and disciplines.
11. Can you give a view on the technical scope of the project is e.g. build apps, build front-end web components/sites, build middle tier services, build back-office systems (all of the above)? Broadly, build public facing front end components. Build middle tier. Interface to prebuilt API. Interface to in house AAA. Manage user profiles. Interface to API management system.
12. Can you give a view on the mix of greenfield and brownfield technologies that we will be working with? Most of the technologies to be used will be developed by the supplier using open source technologies on AWS. There will need to be interfaces to MS Dynamics, possibly ServiceNow, Azure B2C, possibly IBM API Connect portal.
13. How many partners are Met Office looking to select as part of this selection process? The preference is to have a lead supplier to service the contract. We do not have any concerns with the lead supplier subcontracting another supplier to support delivery of a specific expertise.
14. With regards to the evidence required for "Have the ability to develop and deliver training to Met Office teams, either one to one, or one to many" – can you confirm this is with regards to the upskilling of in-house capabilities? Yes
15. Can you clarify which relevant areas for the question 'Provide evidence of an ability to provide enterprise level insight into the strategic direction of relevant areas'. We have left this deliberately open. Please show evidence of insight into mobile, web, AWS or any other capability referred to, or inferred in the document.
16. Can you please clarify the requirements for digital advertising (i.e. content creation / SEO / ASO / ad buying / ad strategy)? There are currently no planned requirements for this to be supplied through this contract.
17. Will the Authority sponsor SC clearance if required? Yes, it is possible for the Met Office to arrange clearances if needed.
18. The Met Office wishes to clarify it's response to Q11: Can you give a view on the technical scope of the project is e.g. build apps, build front-end web components/sites, build middle tier services, build back-office systems (all of the above)? Maintain and enhance apps. Build front end components. Build data transformation capabilities. Support the CMS. No back office systems will be required.
19. The Met Office wishes to clarify it's response to Q12: Can you give a view on the mix of greenfield and brownfield technologies that we will be working with? We already have a CMS (BloomReach) which we are content with, however it will be subject to the normal reviews for cost and efficiency. The website and the apps both exist and are stable hence enhancement and maintenance. Hence most of the work will be ‘brownfield’ iteration of existing capability. However some new work to expose new data types via both the website and AWS capabilities will be required.
20. Can you clarify Q11, what is meant by "organisational expert level development skills in web technologies" do we focus on front end or back end individual skills our organisational thought leadership in this area? Front to mid, HTML, JS/CSS, Java, Python. As well as thought leadership across the web development space.
21. Can you confirm the level of WCAG compliance required? e.g Level AA or AAA? Web Content Accessibility Guidelines version 2.1 AA standard.