Meteorological Observation Systems · Meteorological Observation Systems TECO 2016, Madrid ......

Requirement Specifications for

Meteorological Observation Systems

TECO 2016, Madrid

Foeke Kuik

Association of HMEI

World Bank Group

A jointly funded World Bank (GFDRR)/HMEI project

C&E ConsultancyAssociation of HMEIWorld Bank Group

Content

Procurement of Meteorological Observation Systems

Project Approach & Deliverables

Q&A

Project Background

?




Q&A

Project Background

?


• Climate change

• Extreme weather• Floodings• Droughts• Forest fires

• Huge impact on every day life, different per region

Global Changing Environment

• Quality of observations not good enough• incomplete, • no well defined

specifications, • lack of training, • poor maintenance, • inappropriate life cycle

management.

Problems

Forest fires

Floodings

Extreme weather Droughts

Why are we doing this project?

• Environmental observations are fundamental for hydro-meteorological applications.

• Global growing demand of good quality observation data

Monitoring of Changes


• Sufficient consistent and good qualitysurface observation data

• Good quality surface observation networks

• Good quality consistent requirement specifications for procuring surface-based observing networks

• More awareness on operational procedures, calibrations, maintenance, life cycle management

Desirable situation

Why are we doing this project?

• Reliable data suitable for risk mitigation plans and public safety

• Reliable data for modelling environmental processes

• Benefit for all stakeholders• NMHS’, • financial stakeholders, development

banks, • industry

Results

Floodings

Extreme weather DroughtsForest fires


Why do we want Requirement Specifications?

• Procurement of equipment not suitable for tasks

• Many monitoring programs failed during the last decade

• Data quality not good enough for what the data has to be used for

Association of HMEI World Bank Group WMO

Industry support Financial support User support

Observed problems

• Observations from different systems cannot be compared (globally)

• Vendor/customer dissatisfaction

• Complexity of various WMO guides and manuals

……………………….


How it got started

• Initiative started in 2014 as a cooperation between HMEI, WMO and World Bank to prepare such Requirement Specifications.

• WB involvement (Global Facility For Disaster Reduction and Recovery):• GFDRR Hydromet Program Towards effective partnerships in support of global hydromet services1,

• Requirement Specifications for Meteorological Observation Systems• Took some time to find suitable consultant• Project has started in June 2016, will finish by the end of 2016• Funded by the World Bank and HMEI• WMO takes advisory role and will define in second phase how to make results available in WMO community

1Presentation of V.Tsirkunov and M. Suwa at the InterMet Asia, March 2016, World Bank, http://www.wmo.int/gfcs/sites/default/files/Makoto_Suwa_World%20Bank.pdf

Association of HMEI World Bank Group WMO

Industry support Financial support User support


Prepare Requirement Specifications for Meteorological Observation Systems

• Provide comprehensive and coherent automatic weather station system specification

• Requirement specifications compliant with WMO manuals and guides

• Functional vendor independent requirement specifications

• Detailed technical specifications only if required

• Tender specifications easy to understand to achieve an effective and efficient purchasing process

• A set of vendor independent good quality requirement specifications that everybody can use when an observation network/system has to be procured through tendering

• Documents can be customized for own tender

• A web based tool to generate tender documentation in an easy manner.

• Additional documentation required for public tenders.

Objectives of the project

ResultsObjectives, to consider……




Q&A

Project Background

?


• Publish public tender

• Collect proposals from tenderers

• Evaluate proposals

• Select preferred supplier

• Meetings with preferred supplier

• Final selection of supplier

• Signing of contract

• Kick-off meeting

• Design phase

• Design reviews

• Design approval

• Factory integration, testing, training

• (Project) Documentation

• Factory Acceptance Test

• Shipping of equipment to customer

• Site installations

• Site testing

• Site Acceptance Test, commissioning, site training

• Transfer of ownership

• Start warranty

• Analyze existing system

• Define requirements for new systems

• Prepare budget

• Talk to potential suppliers

• Prepare Requirement Specifications documents

• Prepare other tender documents

• NMHS: internal consensus on new systems

Pre-tender phaseAnalysis and tender documentation

Pre-tender phaseAnalysis and tender documentation

Procurement procedurePublic tenderProcurement procedurePublic tender

ImplementationphaseImplementationphase

Operational phase, life cycle management

Operational phase, life cycle management

• Maintenance plans

• Spare part list

• SLA (if desirable)

• Calibrations (servicing)

• Preventative/corrective maintenance

• Life cycle updates/upgrades

• System modifications (ECPs)

Procurement of meteorological observation systems


Activity Description Responsible DocumentationTender preparation

The NMHS has to prepare the documentation to start a tender procedure.

NMHS Requirement specifications Statement of Work Concept Agreement Tender evaluation procedure Pricing Acceptance protocols Training and Documentation requirements Project planning Delivery Schedule and delivery locations Test procedures Maintenance conditions Payment schedule and Bonds Quality Management System requirements Escrow conditions Minutes of meetings Recommended spare parts list Certificate of conformity Engineering Change Proposal

Documentation required for tender


Documentation Implementation phase 1

Where Activity Description Responsible DocumentationFactory Kick-off meeting Start of the project; clear plans and assignment of responsibility Contractor Minutes of the kick-off meeting.

Documentation plan.

Project plansDesign phase, hardware and software

Contractor to make design of the hardware configuration;

Software design if software needs to be developed. Also applies for software configuration.

Contractor Hardware design document

Software design document (if applicable).

Software configuration documentReviews Reviews of the design made by the Contractor. Customer Review reports

Approval system design First project milestone; first payment. CustomerContractor

Approved design documents

Purchasing hardware Contractor to start purchasing equipment, instruments, loggers, computers, masts, cabinets, etc. ContractorSoftware development and configuration

Contractor to prepare the software for the systems; configuration of the software can be a large part of the work.

Contractor

HMI design Contractor to design HMI and to discuss with customer. Contractor HMI document

Factory integration Contractor to build up the entire system in the factory, including software. Contractor

Documentation Contractor to prepare documentation as agreed in the project and documentation plan.A transition plan is required if new system has to be built and run in parallel with the old system. The new and old system cannot interfere operational services, for example only one synop for each station should be sent to the GTS.

Contractor User manuals

Technician manuals (software and hardware)

Administrator manual

A-built drawings

Trouble shooting manual

Training documentation

Equipment manuals

Transition planApproved HMI Customer approved the GUI designed and proposed by the Contractor. Customer

ContractorApproved HMI document

Factory testing Contractor to test the entire system, hardware and software, in the factory. ContractorFactory training Customer receives training on the system before Factory acceptance testing. Contractor Training documentationFAT document and SAT document Contractor to prepare the Factory Acceptance Test document; The Site Acceptance Test document

can be prepared as a draft.Contractor FAT document

Draft SAT documentApproved FAT document Customer to review and approve FAT document. Customer

ContractorApproved FAT document

Factory Acceptance Test Contractor will execute FAT, usually witnessed by customer. Customer has to sign off the acceptance.Usually a project milestone and payment to contractor.

ContractorCustomer

Signed FAT document

Shipping to site After successful FAT, contractor will pack all equipment and ship it to the customer. Contractor Equipment list


Where Activity Description Responsible DocumentationOn site Site preparation The site(s) have to be prepared for installation. This can be

arranged by the customer itself or as part of the contract by the contractor. The contractor shall prepare the site preparation plan.

Customercontractor

Site preparation plan

Site installation Equipment installed on the installation site(s).SAT document approval Customer to review SAT document. Customer

ContractorApproved SAT document.

On‐site testing Contractor to test installed equipment. ContractorSite Acceptance Test After successful testing, the formal SAT is done. Contractor to

show based on FAT and site testing that the system is fully operational. Milestone, usually with payment.

ContractorCustomer

Signed SAT document

Commissioning After the SAT the new system can be commissioned under guidance of the contractor.

CustomerContractor

Approval documentation All the documentation that has to be delivered for the project has to be finished by the contractor.

Contractor All documents that are part of the contract approved and accepted by the customer.

Operational site test, final acceptance

Sometimes customers want a 30 day test period in which the system has to run uninterrupted before the final acceptance of the system. Final milestone and final payment.

ContractorCustomer

Final acceptance document

Transfer of system to Customer Customer accepts full system; transfer of ownership. Customer

Factory Start of warranty period. The warranty period starts after the system acceptance by the customer. Contractor provides the customer with a service level agreement outlining the warranty conditions, but also offering maintenance and support services that reflect what is needed during the life cycle of the system.

Contractor Service Level Agreement (SLA)

Contractor support to Customer

Support to customer as agreed per SLA. Regular meetings (once per year) will be held.

ContractorCustomer

SLA

Documentation Implementation phase 2




Q&A

Project Background

?


Starting Points

After kick-off meeting in Geneva in June with HMEI, WMO, World Bank:• “Functional” Requirement Specifications (where possible)

• Specification for automatic stations only• Only sensors/instruments with an electrical interface

• Including installation requirements

• Many things cannot be put in a Requirement Specification, but they are added in guiding text.

• Uniquely numbered specifications with qualifications

• Maintenance/life cycle support documents shall be provided

• Various project management documents shall be provided. They can be used as needed.

Initial principles

Schedule, Milestones, Deliverables Project Approach


Project Approach

• MIL-STD-498, Software Development and Documentation Standard, excellent for “ICT-systems”

• Project planning and oversight• Establishing a development environment• System requirements analysis (SSS)• System design (SSDD)• Software/system requirements analysis• Software/system design• Software/system implementation and unit testing• Unit integration and testing• CSCI/HWCI qualification testing• CSCI/HWCI integration and testing• System qualification testing• Preparing for use• Preparing for transition

• 1. Scope

• 2. Referenced Documents

• 3. (Detailed) Requirement Specifications

• 4. Qualification Provisions

• 5. Requirement Traceability

• 6. Notes

• Appendixes

Initial approach: prepare requirement specification document

ContentMIL-STD-498, SSS


Schedule, Milestones, Deliverables

• Introduction on Requirement Specifications• Ta, Tg, Ts• Td, RH• P• WS, WD• Precip (intensity, amount, snow fall depth,

snow cover depth)• Solar radiation (GHI, DHI, DNI, Lw↑, Lw↓)• Sunshine duration

• Automatic Weather Station (AWS)• Meteorological Information Processing

System(MIPS)

• Requirement specification document reviewed by HMEI experts, partly by the World Bank.

What is in the document….

Content


• pre-processing and processing

• coding (reports)

• data communication

• local storage

• archiving, retrieval, recovery

• station quality monitoring• basic quality control• transmission of ”housekeeping” data

• specification of appropriate software

• items to be handled in the AWS or in the MIPS

• site conditions of stations

Data in AWS and MIPS

• data logger requirements

• ICT facilities and requirements

• data communication

• tools

• power consumptiom requirements and power supplies options

• installation accessories such as, junction boxes, enclosures, cabinets, lightning protection, cables, etc.

AWS and MIPS Hardware

Schedule, Milestones, Deliverables What will be in the documents?


• Introduction

• Operational Procedures

• General Requirements

• Calculated parameters

• Installation requirements

• Calibration requirements

• Physical output and protocols

• Power supplies, sensor excitation

Per meteorological parameter

Schedule, Milestones, Deliverables What will be in the documents?

• Visibility, MOR, RVR, BL• Weather (PW)• Cloud observations• Weather radar• Upper air observations• Wind profiles• BUFR (no details but can be

requested)

Second phase• This first project is a pilot!

What’s not there (yet)………..



• Visibility, MOR, RVR, BL• Weather (PW)• Cloud observations• Weather radar• Upper air observations• Wind profiles• BUFR (no details but can be requested)


Missing………….

What is not there (yet)…….



• Visibility, MOR, RVR, BL• Weather (PW)• Cloud observations• Weather radar• Upper air observations• Wind profiles• BUFR (no details but can be requested)


Missing………….

End of September

• “Other” Documentation

• Release of documents to World Bank

• Release of documents to WMO (CIMO & CBS experts)

• In parallel: start building Web Tool for generating requirement specifications (Gerhard Pevny)

End of 2016

• Processing feedback of WMO

• Processing feedback from World Bank.

• Implementation and testing of Web Tool.

• Final version of Documentation.

• Releasing documentation on HMEI website and …...

• Tender documentation available, Web Tool operational.

Schedule

What is not there (yet)…….


Document Remarks1 Instructions to Tenderers Describes what Tenderers have to do to submit a proposal based on the documents in this list.2 Concept Agreement An example of an Agreement that NMHI can adapt and use.3 Contract Awarding Criteria An example of awarding criteria where the weight can be on the price or on the technical evaluation.

4 Statement of Work Explains the activities and responsibilities in the project for both the NMHI and the Supplier.5 Requirement Specifications Document with the requirement specifications for the systems to be procured.6 IRS MIPS – MSS Interface requirements for the data server and the Message Switch (MSS).7 Compliance Table Spreadsheet with only the requirement specifications in which the Tenderer has to confirm the level of

compliance.8 Pricing An example document in which a pricing structure is shown.9 Payment Schedule Describes how the NMHI will do the payments based on project milestones.10 Planning & Schedule Describes the project schedule as requested by the NMHI.11 Training and Documentation Describes the requirements for training and the documentation to be delivered in the project.12 Test Procedures Describes requirements on how the Supplier shall prove the systems works through factory and site

acceptance testing.13 Installation Schedule & Activities Describes the planning from the NMHI for the installation schedule and activities of the system

components.14 Delivery Schedule & Addresses Describes when the NMHI wants to receive the equipment that is ordered through the project and defines

where the equipment shall be delivered.15 Quality Management System Requirements regarding the quality management system of the Supplier.

16 Acceptance Protocols Example documents for signing of the factory acceptance tests and site acceptance tests.

17 Glossary Glossary of all terms, acronyms and abbreviations.

18 Maintenance Conditions Describes the requirements for the Supplier for a proposal for the life cycle maintenance requirements.

19 Recommended Spare Parts Contains the recommended spare parts that are required in relation to the maintenance requirements for a life cycle period of 10 years.

20 Engineering Change Proposal Form A form that is used by both the Supplier and NMHI to describe a required change in the system, Both parties to approve.

Documentation supplied in this project



HMEI and the World Bank started ”Requirement Specifications” project, from June to end 2016• Requirement Specifications for Meteorological Observation Systems• Set of 20 additional tender documents• Web Tool: demonstrations in HMEI booth by Gerhard Pevny• “Lessons learned” document• Pilot project, to be continued….........

• World Bank/HMEI• HMEI Reviewers• WMO

Summary and Acknowledgements

Summary

Acknowledgements




Q&A

Project Background

?


Thank you!!

Meteorological Observation Systems · Meteorological Observation Systems TECO 2016, Madrid ......

Documents

Transcript of Meteorological Observation Systems · Meteorological Observation Systems TECO 2016, Madrid ......