Start date: Thursday 7 November 2019
Value: £36,000
Company size: SME
The Met Office

Implamentation of a CICD Environment for OpenWIS AISBL

11 Incomplete applications

10 SME, 1 large

11 Completed applications

10 SME, 1 large

Important dates

Friday 30 August 2019
Deadline for asking questions
Friday 6 September 2019 at 11:59pm GMT
Closing date for applications
Friday 13 September 2019 at 11:59pm GMT


Summary of the work
The work should deliver:
- CI setup triggered on OpenWIS code changes
- CD setup (cloud) to make artefacts available for deployments
- Transition of that cloud environment to the OpenWIS Association.
- Training of setups to OpenWIS maintainers at location TBD
- An approach to sustaining a CI/CD environment
Latest start date
Saturday 30 November 2019
Expected contract length
2-3 months.
South West England
Organisation the work is for
The Met Office
Budget range
Max 55K Euros

About the work

Why the work is being done
The OpenWIS software implements a web service for data discovery and exploitation for the meteorological community. The software is written in JAVA and hosted as open source project on GitHub (
Since 2018 the setup of automatic Continuous Integration testing (CI)/Continuous Delivery (CD) for the software has stopped working as a consequence of the underlying cloud service has ceased to exist. This RFPs aims to establish a new setup to provide an automatic CI/CD for the OpenWIS software.
Problem to be solved
Implement a new CI test setup which is triggered automatically from code changes on the OpenWIS code GitHub repository. New installable artefacts of the OpenWIS software should be created and made available to users as part of an automatic CD process.
Who the users are and what they need to do
Users are the developers/maintainers of the OpenWIS software themselves. These developers require rapid feedback on their code changes to see if their code changes cause any regressions and ensure that the new software versions can be deployed by users straight away.
Early market engagement
Any work that’s already been done
Since the previous setup ceased to operate there is no existing test setup for the OpenWIS software. The bidders are encouraged to make use as much as possible of existing services around GitHub to implement the CI/CD setups. Ideally the services should be free of charge, but the consortium will consider paid services if required.
Existing team
The OpenWIS consortium is international and includes beside the Met Office, Météo France, NWS, BOM, FMI, IMD, MFI, KMA and ECMWF. The team collaborates though the OpenWIS GitHub space. Any issues, queries and delivery of results should be through this platform if not stated otherwise.
Current phase
Not started

Work setup

Address where the work will take place
The work will be done remotely but the principal customer is the Met Office, Exeter, UK
Working arrangements
The work will be done remotely, and work arrangements are left for the bidder to decide. Video calls can be arranged if required. It is envisioned to have at the end of the work a face-to-face meeting with maintainers to train them and discuss the setups. The meeting location is TBD (Options include Météo France in Toulouse, ECMWF in Reading, and UK Met Office in Exeter).
Security clearance
Not required, since work will be done on open platforms, such as GitHub.

Additional information

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.

Essential skills and experience
  • Demonstrated experience on a variety of CI tool suites including Cloudbees and Travis.We're focused on using free and open source technologies.
  • demonstrate experience of deploying and testing Java developments
  • demonstrate experience of managing projects in GitHub. For example (but not limited to) the use of Kanban to track progress of github.
  • demonstrate experience of management in GitHub Ticketing System
  • Demonstrated experience on a variety of unit testing tool suites that are compatible with github such as (but not limited to) Jenkins
  • demonstrate experience of deploying services in the cloud, e.g. AWS
Nice-to-have skills and experience
  • demonstrate experience of two past cases of Knowledge transfer during and at the completion of contract. How was this transfer managed?
  • Demonstrable project management skills in Agile, Kanban and scrum, so that team can deliver work in a planned and organised manner and align with wider Met Office project delivery approaches.
  • Relevant technical skills and experience of the team to undertake the work. Demonstrate different skill levels and flexibility to adjust resources according to work load during the project.
  • Flex up/Flex down resources throughout duration of contract

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • Overall perceived quality of proposed Technical Solution
  • Quality of evidence provided to support proposed solution and provide assurance of technical capability
  • Approach and methodology
  • How the approach or solution meets user needs
  • Value for money
  • Quality of 2 Examples given and how closely they reflect capability to meet our requirements
  • Technical resources offered/quality proposed of proposed resources to meet requirements
Cultural fit criteria
  • Good ability to communicate clearly with IT and non-IT specialisms to share their knowledge and experience with Met Office staff and other third parties.
  • Ability to meet security requirements included in Cyber Security Questionnaire
  • Share knowledge and experience with members of the organisation and hand over
Payment approach
Fixed price
Assessment methods
Written proposal
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Any reason the budget is in EUR and not GBP or is this a mistake?
No. The work is being carried out through the Met Office on behalf of the OpenWIS Association (international but based in France) and the available budget is held by the association treasury, and therefore in Euros
2. You asked "Demonstrated experience on a variety of unit testing tool suites that are compatible with github such as (but not limited to) Jenkins"
Do you mean unit testing frameworks or tools for driving the automation of unit tests as part of a CI/CD pipeline?
We mean both framework and tools as well as their practical and best practise implementation.