Space Weather R2O2R - University of Surrey

Concepts

• exeter
• surrey
• university
• weather
• r2o2r
• met office team
• met office
• met office systems
• existing software
• code bug resolution

Location

Description

Software and operational support delivery requirements This sets out the general requirements for the work required to accelerate the implementation of the SWIMMR R2O projects on Met Office systems. The scope is to assist the Met Office in the transition of the SWIMMR models towards operational status, as measured by Application Useability Levels (aiming for AUL9). To facilitate this process, the following general software engineering processes and practice should be adhered to: Play a key and proactive role in the maintenance of existing software. In particular, • Monitor the list of open pull requests (PRs) on the GitHub repository containing the model code daily. When new PRs appear (and within a working week), o Respond to any questions raised by MO SSEs. o Accept any requests to review code contributions authored by MO SSEs. o Where appropriate, engage in the online discussions around these. OFFICIAL - COMMERCIAL 6 OF 58 • When you discover issues, contribute (via PR) carefully tested code fixes within an agreed time frame of two weeks. o Aim to respond to and act on reviewer queries within one business week. o Merge in the code changes into the alpha branch within three working days, when changes (pull requests) have been approved - changes to the beta release will be merged by Met Office team • Resolve critical security vulnerabilities (resolution and approved PR) in collaboration with MO teams within two weeks (backlog completed by March 2026) • Maintain existing software by routinely patching to ensure security updates, version updates are implemented as soon as possible and within two weeks • Follow the PR process outlined above and documented on the portal. • Participate in knowledge exchange to enable Met Office to become more self-sufficient in model maintenance • provide technical/scientific 4th line support in code bug resolution [working days support- response/resolution timeline to be agreed] • work with Met Office (MO) Scientific Software Engineers (SSEs) to measurably increase the robustness of the codes (e.g. through test coverage assessment and defining required tests) by improving testing and logging according to the principles documented on the Met Office R2O portal. • Ensure logging sufficient to diagnose workflow issues ensure containers have sufficient test coverage to allow deployment. • Support the continued feature and functional design development of the Research to Operations portal/ platform, through participation in activities such as user interviews and, usability testing • Contribute expertise as part of user research discussions with end users (MOSWOC/industry) in determining the product strategy for utilising the MAIRE+ data to deliver the most value.

Award Detail

CPV Codes

• None found

Legal Justification

Competition is absent for technical reasons and proprietary rights: The deliverables within the contract are associated with a model and code already developed and owned by the partner, (supplier) to a specific maturity under the SWIMMR Programme. The academics hold the model code IPR and provide model access to Met Office under Licence (pending renewal on signature of the contract) and therefore are uniquely placed to provide these services to the Met Office. Delivery will 'accelerate' the model's development towards transition to operations within the Met Office Space Weather service as mandated by DSIT. The purpose of the contract is to continue development of the models (which requires the 'deep expertise' of the model developer) and to transfer model and model code knowledge and expertise. In short, there is no other supplier for the work associated with this model as the Met Office requires the code and expertise solely located at Surrey.

Other Information

** PREVIEW NOTICE, please check Find a Tender for full details. **