Met Office

Next Generation National Severe Weather Warning Service (NSWWS) Development

Incomplete applications

10
Incomplete applications
9 SME, 1 large

Completed applications

7
Completed applications
3 SME, 4 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 20 March 2017
Deadline for asking questions Monday 27 March 2017 at 11:59pm GMT
Closing date for applications Monday 3 April 2017 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work The Met Office is currently undertaking a significant refresh of the National Severe Weather Warnings Service for the United Kingdom. This is a mission critical programme and a Public Weather Service milestone.
Latest start date 17/04/2017
Expected contract length 15 months
Location South West England
Organisation the work is for Met Office
Budget range up to £160k

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done To provide a fit for purpose and enhanced National Severe Weather Warning Service
(NSWWS) based on evidence gathered through extensive customer engagement and
feedback to provide accurate, authoritative and trusted weather warnings to the public,
responders and government for major weather impacts that pose an immediate risk to life/property

The National Severe Weather Warnings Service is the Met Office’s flagship service (NSWWS). The service communicates severe weather impacts and potential hazards to the public, emergency responders and commercial partners. Warnings information is disseminated in a large range of data formats and into many Met Office and third party products.
Problem to be solved A set of key deliverables within the programme are the forecaster tools for defining and creating weather warnings and a managed API to facilitate their publication. The programme is now looking to accelerate delivery of this tranche of work.

The components being developed to fulfil this need are primarily in Java/Spring, with Javascript/Angular for the front end and Postgres/S3 storage. The API will be RESTful and make heavy use of the Atom format. It will be API Managed using a 3rd party cloud based tool.

Delivery will be considered complete when the components and capabilities outlined are operational
Who the users are and what they need to do The users are Chief Forecasters in the Met Office, based in Exeter and Aberdeen. These group of users need to be able to create, edit, and issue warnings in a reliably and consistently.
Early market engagement
Any work that’s already been done The project is already in the ‘build’ phase. It is supported by a comprehensive backlog of user stories which is constantly evolving in line with the scrum process.
Payment will be based on deliverables.
Existing team There are team of 5 Developers, Technical Lead and Tester working directly on development and delivery of the forecaster tools for defining and creating weather warnings and a managed API to facilitate their publication.

There are other development teams working on publication of warnings on the web, mobile applications.

There is also a fully engaged and resourced: Programme Board, Programme Manager, and Project Manager.
Current phase Alpha

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place FitzRoy Road
Exeter
Devon
EX1 3PB
United Kingdom
Working arrangements On-Site
Security clearance Basic clearance (minimum), SC clearance, ideally

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
  • components being developed to fulfil this need - primarily in Java/Spring, Javascript/Angular for the front end and Postgres/S3 storage. The API will be RESTful and make use of Atom format.
  • • Java
  • • Spring / Spring Boot
  • • Testing Frameworks (jUnit, Mockito, groovy, spock, cucumber)
  • • APIs / REST
  • • Amazon Web Services (AWS)
  • • Angular JS
  • • Weather domain knowledge
  • • Agile/SCRUM
Nice-to-have skills and experience
  • • BDD
  • • Training and Mentoring
  • • Security Clearance (SC)

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 3
Proposal criteria
  • • The proposed approach and methodology
  • • How the approach or solution meets user needs
  • • Value for money of the proposal
Cultural fit criteria Work in highly collaborative team and interact with other teams from time to time within our organisation
Payment approach Capped time and materials
Assessment methods Written proposal
Evaluation weighting

Technical competence

60%

Cultural fit

15%

Price

25%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Can you please clarify what the expected outcome will be and also the size of the team you are expecting to work on this project? The expected outcome is twofold:
1. We have a well educated team with improved productivity gained from both third parties
2. We gain a new platform built for purpose, aided and guided by people with the right skills that Met Office do not currently hold.
2. Can you please confirm your expectation as to whether this assignment is outside or inside IR35? This is a deliverable based assignment therefore don't believe that IR35 come into. We will be paying on deliverables.
3. What are the key deliverables within the programme? Part One response:
The aim of this Programme is to deliver enhance and evolve NSWWS to:
• improve the communication of warnings through all channels within scope
• improve the efficiency of warning production.
• improve user experience and access to warnings.
• enhance public safety against additional weather impact.

The Programme is investing in the underpinning technology for NSWWS as the current technology is some years old and is not as robust or scalable as more modern technologies.
4. What are the key deliverables within the programme? Part 2 response:
The Programme will be implementing a new warnings creation and dissemination capability which is built using cloud technologies, it will enable warnings creation to be more robust and timely. The programme will also be enhancing the way warnings information is presented visually and textually to address feedback from the public/civil contingency community.

Currently the Met Office is the market leader for warnings dissemination amongst public/commercial channels. The Met Office needs to retain this position ensuring end users of the data continue to find it accessible/relevant and enable them to make decisions that ensure public well being.
5. In the summary you mention that the project is already in the 'build' phase. Could you please confirm if the current team is being supplied by a third party supplier or through internal resources? The majority of the current team are resourced from internal resources
6. "The project is already in the ‘build’ phase. It is supported by a comprehensive backlog of user stories which is constantly evolving in line with the scrum process. Payment will be based on deliverables." Please can you clarify how payment on deliverables will be undertaken when the backlog is constantly evolving? The Epics (below) related to this project and payment will be against the delivery of these Epics

Epic name:

Update Warning, Cancel Warning, Expired Warning, Multiple Warnings, Replacement Warnings Manager, Dashboard, Warning Text Detail, Archive, Map Features, Enhanced Map Layers, Enhanced Drawing Features, 7 Day Lead Times, TS & Lightning Warning Type(M), Impact Table, Impact Table, Small Area Warnings, Appropriate Alerting, Consistency Across Channels, Triple Warnings, Decommissioning, Technical Preparation, OpenShift
7. "Weather domain knowledge" as an essential skill or experience. On the other hand, the deliverables of the project (answers 3 and 4) emphasise presentation of information to members of the public and others (rather than on the more specialist tasks that lead to generating this information ). Can you clarify what kind of knowledge is needed, please? Weather domain knowledge is the key skill/knowledge area we are looking for.
8. Will the current development team detailed under ‘Existing Team’ remain in place for the entire project? Are there any targets for ‘accelerated delivery’? Are both the in-house Met Office team and the supplier accountable for the completion of the deliverables? From your knowledge of the platform, and the progress made in ‘build’, what roles do you believe are required to ‘accelerate delivery’ to achieve your outcomes? Have designs been completed and agreed as part of the discovery phase of the project? Is there scope to iterate and improve them throughout construction? Yes, existing team will remain in place.
Yes, there is a ‘Stretch target for delivery at October 2017’.
Yes, both the supplier and the in-house team are accountable.
The roles required to accelerate delivery are defined in the requirement
Yes, designs appropriate to the phase have been completed.
Yes, there is scope to iterate and improve upon Designs.
9. Please could you elaborate on what level of weather domain knowledge and/or experience is required, and if it is required of all resources provided for the project? Weather is our primary business. Weather Domain knowledge would be beneficial but is one of many aspects to the requirement.
All prior experience against each of the requirements should be included.
10. You mention a start date of 17th April 2017. This is a national bank holiday, so do you mean 18th April or will you be starting on the Monday? No that was an error, the planned start date would be on or around 18th April 2017.
11. Please confirm the size of team you expect to need for this project, and whether they would work alongside the existing team of 5 that is mentioned, or would replace some or all of this team. This is not about the size of the team but an output being delivered.