COMKISS - Kick off meeting Friday 25th September 1998, Lund

Contents

A) Minutes
B) Actions
C) Milestones
D) Data Requirements

A) Minutes

1. Present:

Georg Lindgren (GL) , Igor Rychlik (IR) , Anders Holtsberg (AH) - University of Lund;
Tom Allan (TA) , David Cotton (DC) - Satellite Observing Systems;
Michel Olagnon (MO), - IFREMER;
Raymond Nerzic (RN) - OPTIMER;
Guy Parmentier (GP) - Bureau Veritas;
Cees Leenars (CL)- DOCKWISE N.V.

i. Unfortunately no representative from CEO was able to attend the meeting.
ii. Corsica Ferries participation in COMKISS is not funded (but is approved by CEO), therefore no representative attended.

2. Welcome - GL

GL welcomed all the participants. He distributed copies of the final version of the Work Programme and Technical Annex, as approved by CEO. Within these documents, the University of Lund are identified as COMKISS Programme Co-ordinator , and Satellite Observing Systems as COMKISS Programme Manager. The respective requirements of these roles was established. The agenda was approved.

3. Introducing the Team - ALL

Those present briefly introduced themselves, and outlined their particular areas of interest. There were some changes in COMKISS personnel from those in the proposal: Guy Parmentier will represent Bureau Veritas in COMKISS, in place of Michel Huther. Tom Allan from Satellite Observing Systems will be joined by David Cotton.

It was still not clear at this time which CEO official would be responsible for overseeing the COMKISS programme.


Responsibilities

University of Lund, Department of Mathematical Statistics (UL) :

Project Co-ordination, Statistical Analyses

Satellite Observing Systems (SOS)

Project Management, Near Real Time Altimeter Data

TA noted that the commitment of Satellite Observing Systems to COMKISS, in term of man days, had been reduced (to approximately half) from earlier estimates to enable them to meet CEO financial rules. Thus the role of Satellite Observing Systems within COMKISS was now primarily that of Programme Manager, with less time available for the scientific work packages. The main scientific contribution is now limited to provision of near real time satellite data.

IFREMER (IF)

Archived satellite wave data, analysis, modelling

OPTIMER (OT)

Comparisons of model output and satellite data

Bureau Veritas (BV)

Route/Ship certification

Dockwise NV (DW)

Transportation of unconventional loads. Open ocean installations and operations

Corsica Ferries (CF)

High speed passenger transport

4. COMKISS Programme Overview - TA

4.1 Work Programme

TA briefly reviewed the Work Programme as detailed in the documentation:

WP1000 Programme Management

UL Project Co-ordinators - Responsible to CEO

SOS Project Management - responsible for technical co-ordination and reporting.

WP2000 Project Definition

User Requirements need to be confirmed and updated. Project Definition should be continuously revisited throughout programme

WP3000 Ship Certification

Do the BV priorities agree with those stated in the work programme?

WP4000 High Speed Ferries

CF are not being funded by CEO, but wish to participate in programme. Level of participation will reflect their unfunded status

WP5000 Unconventional Loads

DW later provided a presentation of their aims for COMKISS (see below)

WP6000 Demonstration Modules

Example Demonstration Module Templates have been generated within EWSE. SOS have already produced DM’s for other programmes.

WP7000 Report/Validation

A more detailed discussion on the priorities of the first six months of the COMKISS programme followed. Early milestones and actions were agreed (see subsequent sections).

Documentation

TA noted that the documentation had been revised to meet CEO requirements, and that the format of the Technical Annex was based on a CEO template. It was acknowledged that CEO have formal requirements for documentation and procedures, and that the team would strive to meet these requirements. However, no CEO representative was available to provide further guidance.

5. Satellites and Models

Ways in which satellite data and model output could be used together to address user requirements were discussed. This was seen to be mainly the responsibility of IFREMER and OPTIMER, supported by UL, with SOS’ role mostly restricted to the provision of Near Real Time data.

MO (IFREMER) outlined his perspective for COMKISS. He noted that model nowcast output was relatively inexpensive, in contrast to hindcast and forecast data, which were more expensive. He suggested that the approach of COMKISS should be to use the satellite data to identify the occasions and conditions under which model forecasts are unreliable, and hence where the input of satellite data would be most effective. He suggested that the most appropriate use of models would be simply to propagate information from the locations where satellite data were available, rather than simply employ a large model grid and assimilate satellite data. In this way the influence of the models (and possible inaccuracies therein) would be minimised.

6. Roles of Partners

The scientific/management roles had been discussed earlier in the meeting - CL (Dockwise) presented further information, and possible ways of including other HSC operators was discussed. Because GP (Bureau Veritas) was relatively new to the COMKISS project, he had no further information to add at this stage.

6.1 Dockwise

Dockwise have two main operational modes for predicting/responding to environmental conditions. The first is an office based system which is used to run a risk evaluation for proposed operations, by running Monte-Carlo simulations of the operations through an archive of environmental parameters. The second mode is an on-board system which provides route and decision making support, and monitors conditions en-route.

The use of Monte-Carlo simulations is an important feature of Dockwise’s procedures. Rather than extracting a single set of predicted/expected climate conditions for a given route, multiple model runs of the proposed operation are made through the archived climate data, incrementing by date/location so that statistics of loads/stresses/exceedances can be generated and failure probabilities (e.g.) assessed.

The COMKISS programme has complementarity with the SAFETRANS project, of which Dockwise is a partner, and whose main aim is to reduce risk during

transport and offshore installation. However, some key items are not included in the SAFETRANS programme, i.e.

1) The ability to analyse after the event exactly what the conditions were at the time of an operation.

2) The development of a package to predict movements and stresses on board a ship during certain planned operations.

DW have identified further areas where improvements are desirable : Improved accuracy in forecasts to aid short term planning. improved information for (semi) enclosed seas where model data are often unreliable (e.g Black Sea, Caspian Sea, Philippines, Indonesia). They currently use global statistics derived from models (covering a period of 5 years). They would be interested to compare these global statistics with those derived from satellite data.

From COMKISS DW hope to assess the potential improvement that could be achieved over existing practices through the application of satellite data, in the following areas:

1) Design data base.

Currently DW use a data base from Ocean Weather (New York, USA). Would satellite data be more reliable/accurate?

2) Near Real Time Data

They need a better description of the wave field during operations.

3) Surface Currents

Could satellite data be used to improve/modify the available information on surface currents? For instance could satellite data provide time variability to add to the steady state maps that are available?

Some discussion on this point followed. Altimeter data could only (potentially) provide information under an orbit track, either through inference from wave height enhancement in areas with steeply shelving bottom topography, or where hydrographic data under the satellite track is available. If 2 dimensional information were required, image data (e.g. SAR, ATSR, AVHRR) could provide detail of current structures.

One of the possible alternatives to using archived or real time satellite wave data could be forward looking radar. Thus the outputs of COMKISS could be used to establish whether satellite data provide a useful option which is economically beneficial.

6.2 High Speed Craft

The team was pleased that Corsica Ferries had agreed to participate, and was keen to help them play an active role. It was agreed to invite Capt. Dumont (CF) to the next COMKISS meeting in PARIS. It was agreed that other HSC operators (in the Mediterranean Sea, NW Europe) could be contacted for input. The possibility of running a Workshop mid-programme to which HSC operators would be invited was discussed, but no final decision made.

7. Demonstration Modules

These will be the joint responsibility of SOS/IFREMER. Example templates are available through EWSE. UL will be responsible for developing a WWW site. The WWW site and demonstration modules will be developed early in the programme. It was agreed that early versions of the Demonstration Modules will illustrate the operational problems for BV, DW and CF that COMKISS is addressing, and the solutions currently employed by the operators. IFREMER agreed to take the lead in compiling suitable input from Dockwise, Bureau Veritas, and Corsica Ferries, and preparing initial draft DMs. As the COMKISS programme develops, the satellite based solutions will be included in the modules and compared to the previously operational techniques.

8. Reporting Procedures

Internal reporting will take place chiefly through email, all reports will also be placed upon the project web site. Details of deliverables are provided on p36 of the Technical Annex - coded as to whether the documents are (a) internal reports, (b) internal reports with copies to CEO, (c) for external dissemination, or (d) Official CEO reports.

Further to this CEO will require 6 monthly cost statements (UL), annual reports (SOS to prepare first draft). The partners identified as leaders for individual work packages will be responsible for generating progress reports on these packages.

9. Next Meeting

Scheduled for 05/02/99, in PARIS, Bureau Veritas to host and cooperate with IFREMER with regard to local arrangements.

B) ACTIONS

UL Management Plan (WP1100); Completion date-25/09/98

UL QA Management Plan (WP1300); Completion date- 25/10/98

DW, BV, CF Operational and historical information requirements to SOS; Completion date- 25/10/98

IF/OP/UL Review operators? information requirements - generate detailed data requirements (Satellite data, in-situ data, forecast/hindcast/nowcast wave model output, ship response models - e.g. HSC); Completion date- 18/11/98

SOS User Requirements Document (WP2100); Completion date- 25/11/98

BV Identify suitable computer Models for HSC; Completion date - 25/11/98

SOS Redefine Project (WP2200); Completion date- 25/12/98

UL Redefine Priorities (WP2300) - generate specific guidance notes for each of packages WP3000, WP4000, and WP5000; Completion date- 25/12/98

IF Prepare draft demonstration modules with input from DW, BV, and CF; Completion date- 25/12/98

BV Commence Ship Certification Activities (WP3000); Completion date- 25/01/99

Further detail on individual work packages only possible after revision of user requirements. BV responsible for providing updated requirements to SOS and (with UL) for final definitions of Work Packages within 3000.

BV/IF Host/organise 1st COMKISS progress meeting; 05/02/99

IF/SOS/CF Commence High Speed Craft WP (WP4000); 25/03/99

Further detail on individual work packages only possible after revision of user requirements. IF/SOS responsible for acquiring updated requirements from CF and IF (with UL) responsible for final definitions of Work Packages within 4000.

HSC model will then be run archived wave spectral data- derived from satellite data and/or model output. It may also be possible to improve fatigue life predictions.

DW Commence Unconventional Loads WP (WP5000); 25/03/99

Further detail on individual work packages only possible after revision of user requirements. DW responsible for providing updated requirements and (with UL) for final definitions of Work Packages within 5000.

C) COMKISS MILESTONES - YEAR 1

Milestones dates are based on T0 at KO meeting date (25/09/98) - Italics indicate Work Packages which may be redefined after WP2200/2300 :

WP1100 Management Plan (UL); Completion date; T0 (25/09/98)

WP1300 QA Management Plan(UL); Completion date; T0+1 (25/10/98)

COMKISS project WWW page (UL); Completion date; T0+2 (25/11/98). (To allow posting of reports, memos, draft documents etc.)

WP2100 User Requirements(SOS); Completion date; T0+2 (25/11/98)

WP2200 Internal memo on redefined Project(SOS); T0+2 (25/11/98)

WP2200 Redefine Project(SOS); 1st revision; T0+3 (25/12/98)

WP2300 Redefine Priorities (UL)

- Guidance notes for WP3000; T0+3 (25/12/98)

- Guidance notes for WP4000; T0+3 (25/12/98)

- Guidance notes for WP5000; T0+3 (25/12/98)

WP3000 Ship Certification Activities (BV); Commences T0+4 (25/01/99)

WP3100 Satellite Archives (BV); Commences T0+4 (25/01/99)

WP6000 Prepare draft of Demonstration Modules containing description of current status of operators procedures (IF/SOS)

WP6100 Certification (BV/IF) T0+4 (25/01/99)

WP6200 HSC(IF) T0+4 (25/01/99)

WP6300 Unconventional Loads (DW/IF) T0+4 (25/01/99)

1st COMKISS progress meeting (BV/IFR) PARIS (05/02/99)

Cost statements (ALL to UL) (25/03/99)

WP3200 HSC Certification(BV) Commences T0+6 (25/03/99)

WP3300 NRT data (SOS) Commences T0+6 (25/03/99)

WP2200 Redefine Project(SOS) 2nd revision T0+6 (25/03/99)

WP4000 High Speed Craft (IF) Commences T0+6 (25/03/99)

WP4100 HSC performance (IF) Commences T0+6 (25/03/99)

WP4200 NRT data (SOS) Commences T0+6 (25/03/99)

WP5000 Unconventional Loads - Commences T0+6 (25/03/99)

WP5100 Long term planning (DW) Commences T0+6 (25/03/99)

WP5200 Surface Currents(DW) Commences T0+9 (25/06/99)

WP5300 NRT data (SOS) Commences T0+9 (25/06/99)

2nd COMKISS progress meeting T0+11 (25/08/99)

WP2200 Redefine Project (SOS) 3rd revision T0+12 (25/09/99

Cost statements (ALL to UL) T0+12 (25/09/99)

COMKISS Annual Report (UL/SOS) T0+12 (25/09/99)

D) DATA REQUIREMENTS

These headings are simply intended to provide some guidance when considering requirements, and data specifications.

1. Define routes, dates, information required: DW, BV, CF

Historical Operations for review

Real Time Operations

2. Ship Data, Buoy Data Requirements

Archive Data

Near Real Time Data

Parameters

Statistical Data

Resolution

3. Satellite Data Requirements.

Archive Data

Near Real Time Data

Parameters

Statistical Data

Resolution

4. Wave Models

Model output / Model code

global / local

hindcast / nowcast / forecast

Statistical Data

Resolution

5. Ship Response Models (e.g. for High Speed Craft).