Management Plan -...

COPERNICUS MARINE ENVIRONMENT MONITORING SERVICE

CMEMS

NRT DU

Management Plan

Reference: CMEMS-NRTDU-MP

Validated by: V. Forneris (CNR) Document release number: 1.0 Date: 2017-10-06

Contributors : V. Forneris (CNR), G.Manzella (ETT)

NRT DU Management Plan

Ref : CMEMS-NRTDU-MP

Date : 06-10-2017

Issue : 1.0

COPERNICUS MARINE ENVIRONMENT MONITORING SERVICE PAGE 2/ 24

CHANGE RECORD

Issue Date § Description of Change Author

1.0 2017-10-06

all First version of document V. Forneris (CNR) G.Manzella (ETT)



Date : 06-10-2017

Issue : 1.0


TABLE OF CONTENTS

I Scope ................................................................................................................................................................. 6

II Work Breakdown Structure ............................................................................................................................. 6

III Organisation ............................................................................................................................................... 12

IV Main Management Procedures ...................................................................................................................... 14

V Configuration Management ........................................................................................................................... 23

VI Quality Assurance Management .................................................................................................................... 23

VII Risk Management ...................................................................................................................................... 24



Date : 06-10-2017

Issue : 1.0


GLOSSARY AND ABBREVIATIONS

CMEMS Copernicus Marine Environment Monitoring Service

DU Dissemination Unit



Date : 06-10-2017

Issue : 1.0


APPLICABLE AND REFERENCE DOCUMENTS

Ref Title Date / Issue

DA 1 Statement of Work For

Dissemination Unit Operations

August 2017

1.0

DA 2 Service Interface Operations Process Manual (SIOPM)

DA 3 85-OD-MF-CMEMS Statement of work for copernicus marine environment monitoring service dissemination

service (SoW)

March 2016

DA 4



Date : 06-10-2017

Issue : 1.0


I SCOPE

The purpose of this "Management Plan" (MP) is to presents how processes and activities will be executed to assure the contract’s successful completion.

This Management Plan describes:

The Work Breakdown Structure: work packages description and list of activities

The Organisation, including Roles & Responsibilities

The main Management procedures (Development, Tests, Planning, Monitoring, Meetings …)

The Configuration Management Plan (or a reference to a separated document)

The Quality Assurance Management Plan (or a reference to a separated document)

The Risk Management Plan (or a reference to a separated document)

This Management Plan is intended for both LOT1 (NRT) & LOT2 (MY): same structures/approaches will be adopted, in case of one or both LOTs assigned. Updates may be required.

II WORK BREAKDOWN STRUCTURE

The Work Breakdown Structure (WBS) is the main structure used in managing the project. The WBS defines the scope of the work and is based on an analysis of all the Work Package’s tasks as presented in the Sow.

The CMEMS NRTDU WBS is composed of five main work packages. Same structure will be used in case of LOT1, LOT2 or both.



Date : 06-10-2017

Issue : 1.0


Figure 1 - DU Operator Work Breakdown Structure

Partners and Subcontractors roles

CNR ACRI ETT IFREMER SERCO CLS

adwaïsEO

mgmt deputy monitori

ng

OBS sDU MFC sDU sw devel INS sDU delivery sw devel 3rd level

SD 3rd level

SD support

3rd level SD

2nd lev SD

support DR

TASK 1 INITIAL SETTINGS OF THE DISSEMINATION ENVIRONMENT

Task 1.1 Setting operational infrastructure X

Task 1.2 Making existing products available

X X X X

Task 1.3 Software installation/configuration

X X X X X X

Task 1.4 Interface with production units X

TASK 2 MAINTENANCE AND EVOLUTION OF THE DISSEMINATION ENVIRONMENT

Task 2.1 Maintenance of the dissemination environment

X X X X

Task 2.2 Evolution of the dissemination environment

X X X X X X X

TASK 3 integration of catalogue versions

Task 3.1 Setting integration infrastructure X

Task 3.2 Integration activities X X X X X X

TASK 4 OPERATIONS



Date : 06-10-2017

Issue : 1.0


Task 4.1 Gathering and checking input products

X

Task 4.2 Making products available on dissemination interfaces

X X X X X

Task 4.3 Service desk X X X X

Task 4.4 Double dissemination X X X X

Task 4.5 Product delivery monitoring X

Task 4.6 Dissemination monitoring X

Task 4.7 Security monitoring X X X X

TASK 5 MANAGEMENT AND QUALITY ASSURANCE

Task 5.1 Management of infrastructure activities

X X

Task 5.2 Management of integration activities

X X

Task 5.3 Management of operations X X

Task 5.4 Global management X X

Table 1- Organisation/Task Break Down

WP1 (TASK 1): Initial Settings of the Dissemination Unit (CNR)

Partners: CNR, ACRI, ALTRAN, CLS, ETT, IFREMER, SERCO Italia

The objective of this WP is to set up the next Dissemination Unit system, assuring service continuity. The WP, consists of developing the new systems on a new cloud environment, setting up DU specific external interfaces, setting up new functionalities (e.g. dashboards) and collecting data from PUs/previous DUs supporting the conversion of data (e.g. filename syntax update). It is a short-term WP (first phase only), yet is the most demanding package and particular attention to interactions with PUs and assuring the highest service continuity allowed but this activity.

WP1 activity and delivery plan

Task 1: Initial Settings of the dissemination environment

setting operational infrastructure

making exisitng products available

software installation and configuration

interface with production unit

M1 DU-001-005/010

M2 DU-006

M3 DU-007 DU-009

M4 DU 011

M5 DU-021 DU-008 DU-012-013

M6 DU-014-017

M7

M8 DU-018-020 DU-022

M9

M10



Date : 06-10-2017

Issue : 1.0


M11

M12

WP2 (TASK 2): Maintenance and evolution of the Dissemination Unit (CNR)


The objective of this WP is to maintain operational Dissemination Unit and to evaluate, propose and implement potential evolutions. Partners have long and strong backgrounds in IT/ICT service provisioning, SW development, specifically designed for Earth-Observation data, and CMEMS Dissemination Activities in particular, so the DU operator is able to provide strong feedbacks on infrastructure, service and SW evolutions.


Task 2: Maintenance and evolution of the dissemination environment

maintenance of dissemination environment

evolution of the dissemination environment

M1

M2

M3

M4

M5

M6

M7

M8

M9 DU-023-027

M10

M11

M12 DU-023-027 DU-081-083

WP3 (TASK3): Integration of Catalog versions (ACRI)


The objective of this WP is to integrate new catalog versions. The activity consists of creating (and dismantle, once unused) of development environments, performing tests and move the configuration into operations, according to SoW (and Mercator Océan).


Task 3: Integration of the catalogue versions

setting integration infrastructure integration activities

M1



Date : 06-10-2017

Issue : 1.0


M2

M3

M4

M5

M6

M7

M8

M9 DU-028-031

M10 DU-034-036

M11

M12 DU-032-033

WP4 (TASK4): Operations (SERCO Italia)


The objective of this WP is to perform daily activities on the Dissemination Unit and all the related services, including: gather, check and deliver product files to the appropriate sub-DU, monitor deliveries and interfaces, provide DU Service Desk interfaced with CMEMS Central Service Desk, provide the Double Dissemination approach whenever needed.


Task 4: Operations

Gathering and checking the input data & products

make products available on dissemination interfaces service desk

double dissemination

product delivering monitoring, dissemination monitoring and security monitoring

M1

M2

M3

M4

M5

M6

M7

M8

M9 DU-037-038

DU-058-059; DU-062-065, DU-067; DU-069; DU-071-072

M10 DU-041-045 DU-046

M11 DU-204; DU-206-207

M12 DU-039-040 DU-052-057

DU-060; DU-061,DU-066; DU-068; DU-073;DU-074



Date : 06-10-2017

Issue : 1.0


WP5 (TASK 5): Management and quality assurance (CNR)


The main objectives are to

Lead and coordinate all partners involved in the technical issues of the CMEMS DU

Facilitate top-down and bottom-up communication between Mercator Ocean and the partners.

Lead the network of service and operations activities

Manage the sharing and distribution of responsibilities,

Lead the appropriate information exchange in order to prepare for the next generation of services

Monitor the compliance of current activities with the work package commitments.


Task 5: Management and quality assurance

Management of infrastrucutre activities

management of integration activities

management of operations global management

M1 DU-100-108; DU-111-112; DU-120

DU131-132; DU137-138; DU150

M2

M3 DU-100-108 DU-133-136; DU-151-152

M4

M5

M6 DU-100-108 DU-133-136; DU-151-152

M7

M8

M9 DU-100-108 DU-133-136; DU-151-152

M10 DU-113-115

M11

M12 DU-75-080 DU-084-085

DU-086-090; DU-100-108; DU-110; DU-116-121; DU121-124; DU-125

DU-133-136;DU139-142;DU143-144;DU149;DU-151-152



Date : 06-10-2017

Issue : 1.0


III ORGANISATION

In order to meet the high level of service required by CMEMS, a new Consortium will be formed, led by CNR (prime Contact Point) and composed by CNR, ACRI, IFREMER, ETT; moreover, the Consortium has these subcontractors: CLS and SERCO (CNR), ALTRAN (IFREMER), adwäisEO (ACRI).

Management is based on the CMEMS DU Management Plan (MP, this document) and the Service Interface Operations Process Manual (SIOPM):

The CMEMS-DU-MP describes the CMEMS DU organization, task breakdown structure, teams, roles and responsibilities, the development plan and required documentation.

The CMEMS-DU-SIOPM describes how the CMEMS DU operator will participate in the processes as described in the Operations Process Manual.

These documents and all other documents linked to this proposal can be downloaded from:

http://gosweb.artov.isac.cnr.it/cmems-du-docs

The CMEMS DU operator Consortium will be led by CNR, with the support of ETT as deputy: these are the sole partners involved in this WP. CNR will be the primary contact for Mercator Ocean.

Consortium board will be formed by DU Leader, DU Deputy and a member per partner, for a total of 4 members.

Management of the CMEMS DU service will draw on the experience gained from CNR’s management and organization of the MyOcean, MyOcean2, MyOcean-FO and CMEMS OCTAC dissemination and production centres.

The expertise of all partners in ICT/IT solutions applied to Earth Observation and service providers (profiles of the Institutes and Companies are available upon request) assures the highest level of professionalism as the responsibility to identify and perform all tasks necessary to meet the service requirements not listed in the SoW.

The key bodies of the management structure are: DU Leader (DUL) is the decision making body; the DU Deputy (DUD), supported by the Technical Manager (TM), the Virtual Infrastructure Manager (VIM), Interfaces Manager (IM).

DUL and DUD will be in charge of executive management. The TM, VIM and IM, coordinated by the DUD, will be responsible for the implementation.

The key principle in the decision process will be that the lowest adequate level has to decide, taking into account the guidance on technical and strategic policy matters. These principles apply to all tasks of the project.

Within the management structure, two different decision levels are established:

Strategic level, represented by the DUL and DUD to assess the overall technical progress of the project and manage financial activities.

Operational level, represented by the DUL, DUD, TM, VIM, and IM to implement the technical activities necessary to achieve the objectives of the project.

The management structure will consist of the following bodies:

http://gosweb.artov.isac.cnr.it/cmems-du-docs



Date : 06-10-2017

Issue : 1.0


Role Name Surname Institute / Company

DU Leader Vega Forneris CNR

DU Deputy Antonio Novellino ETT

DU board member Vega Forneris CNR

DU board member Antonio Novellino ETT

DU board member Gilbert Barrot ACRI

DU board member Thierry Carval IFREMER

Contract Manager Rosalia Santoleri CNR

Global Management Vega Forneris / Antonio Novellino CNR / ETT

Configuration & Change Manager Vega Forneris / Antonio Novellino CNR / ETT

Management of integration activities Vega Forneris / Antonio Novellino CNR / ETT

Release and Transition Manager Vega Forneris / Antonio Novellino CNR / ETT

Reporting Manager Vega Forneris / Antonio Novellino CNR / ETT

Quality Manager Vega Forneris / Antonio Novellino CNR / ETT

Risk management Vega Forneris / Antonio Novellino CNR / ETT

Documentation Manager Vega Forneris / Antonio Novellino CNR / ETT

Schedule Manager Vega Forneris / Antonio Novellino CNR / ETT

Reviews and Meetings Vega Forneris / Antonio Novellino CNR / ETT

Technical Manager Gilbert Barrot / Olivier Sardou ACRI

Virtual Infrastructure Manager Stéphane Clouaire ACRI

Operation Manager Alessandra Paciucci SERCO

Security Manager Alessandra Paciucci SERCO

OBS/MFC interface evolutions Tarek HABIB / Jean-Michel Zigna CLS

INS interface evolutions Giuseppe Manzella / Antonio Novellino ETT



Date : 06-10-2017

Issue : 1.0


Disaster Recovery Manager Olivier Sardou ACRI

PU-DU interface coordinator Vega Forneris / Cristina Tronconi CNR

PU-DU interface INS manager Thierry Carval / Stéphane Tarot IFREMER

PU-DU interface MFC manager Giovanni Corato / Gaston Briot ACRI

PU-DU interface OBS manager Cristina Tronconi CNR

sub-DU manager - INS Stéphane Tarot IFREMER

sub-DU manager - MFC Giovanni Corato / Gaston Briot ACRI

sub-DU manager - OBS Vega Forneris / Flavio Lapadula CNR

Detailed CVs are available upon request.

The experience of the Partners in operative services, design, production, dissemination and SW development, allows the Consortium to provide a sustainable architecture and a service oriented toward user and internal PC’s partners, as well as the expertise for interacting with both the Top Level and the PC proposing further improvement and/or supporting PC during Transitions and Evolution Phases.

IV MAIN MANAGEMENT PROCEDURES

The Consortium is formed by public and private organisations. Previous section is providing the lists on distribution of responsibilities to which liabilities are associated. A common aspect of operations will include management of personnel, overview of finances, control of supplies, project relationships. All aspects (shown in figure 1), including ownership, will be regulated by a consortium agreement. This will also serve the purpose of formalizing operations across organizations.

The agreement will create consistency and make sure that all processes will run smoothly.

Working procedures will be established case by case to support the personnel how to operate the different parts of the work.

In the event of any communication, online or offline, concerning CMEMS and its activities in CMEMS will comply with the “external communication guidelines for CMEMS contractor” defined by Mercator Océan and will be under Mercator Océan approval.

The personnel of the consortium will be committed to work on normal working days (i.e. excluding Saturdays, Sundays and local public holidays of each partner). The local public holidays will be notified to Mercator Océan by the end of year N for the year N+1.



Date : 06-10-2017

Issue : 1.0


Commitment to amend management plan as necessary.

During the first six (6) months (KoM+6), any reasonable change to the applicable and reference documentations, upon which the deliverables depend, will be accommodated by the CMEMS DU operator at no extra cost.

Any change to the Key Personnel will be proposed prior to the planned change together with a detailed CV of the proposed replacement candidate. Mercator Océan shall approve the replacement of any Key Personnel and reserves the right to reject proposed replacement candidates.

Assessment of the working plan will be carried out every six months. The consortium will discuss the effectiveness of the plan and the success or failure of its implementation. DUL and DUP will assure ways for all management and personnel to submit their feedback regarding the plan.



Date : 06-10-2017

Issue : 1.0


According to the assessment, DUL and DUP will propose changes to the plan that must be approved and instituted, following the procedures defined in the signed contract and consortium agreement.

Project Coordinator and Project Office

The DUL (CNR) will perform daily coordination and management of the project and will be supported for these tasks by the DUD (ETT). The DUL will manage the overall project and its technical contents. The DUL and DUD will safeguard the overall quality of the project

The DUD has the following management tasks:

Overall financial and person planning, in cooperation with the committing authority

Monitor, evaluate and control the overall progress of the project and its activities towards its objectives

Coordination of remediation plans for delayed and or unsuccessful activities

Coordination and finalising of all required reports, including progress and financial (costs statements) reports to the committing authority.

Ensure quality control of all the deliverables

Organisation of project meetings

Overall legal, financial, administrative, contractual management

Overseeing the promotion of gender equality and watching over ethical issues

Maintaining communication with the committing authority



Date : 06-10-2017

Issue : 1.0


Each task is coordinated by a task leader (i.e. TM, VIM, and IM) who will monitor and guide the progress of that activity by regular communication to the partners concerned. Tuning and coordination at project level will be undertaken at strategic level. If required, a task leader can decide to organize a Working Group meeting, involving a selection of partners for a specific activity, e.g. in order to prepare specifications.

The Project meetings, organised periodically, contribute to the overall coordination, because these meetings provide a platform to present and discuss a coherent development of all activities with all partners involved.

Further to this during the project the consortium will organize the minimum required number of meetings as reported in the following table

Activity Number of Meeting (*)

Number of Days per meeting

Minimum number

of attendees

Kick Off Review Physical meeting 1 2 2

Annual Operation Reviews Physical meeting 3 2 2

Coordination Meetings Physical meeting 6 2 1

MFC/TAC Specifications Review Physical meeting 3 2 1

MFC/TAC Design Review Physical meeting 3 2 1

Pre-Integration GO-NOGO meeting Webex 9(estimate) 0.25 1

Integration closure meeting Webex 9(estimate) 0.25 1

Entry Into Service of CMEMS version Webex 9(estimate) 0.25 1

System Evolution Design Review Webex 3(estimate) 0.5 1

System Evolution Acceptance Review Webex 3(estimate) 0.5 1

Follow-up meetings Webex 36 (12 per year)

0.15 1

Contract Closing Review Physical meeting 1 1 2

(*) Number of meetings for the full contract duration

The task leader role includes:

the main technical options for developing the technological elements;

validation of the technical specifications of the technical system components and the technical options

checking of their conformity with the specifications and their timely delivery to the partners and project office

checking the availability of appropriate documentation

control of the system monitoring log and analysis of the performances

technical perspective for improving the system including the estimation of its feasibility

the test and validation of the technical deliverables;

searching for an alternative solutions in case of unexpected technical problems.



Date : 06-10-2017

Issue : 1.0


Mid Term Review

An assessment meeting will be organised around the end of the 12th month of the project where all partners and committing authority representatives shall be invited to participate together. The goal of this review meeting will be to assess the progress to date, and to redefine (if necessary) the Project Programme for the remaining part of the contract. A Go/No-Go decision, regarding the specific objectives and milestones for the technical progress, will be made.

The Contractor shall prepare and attend to the physical meetings hereafter [REQ-NRT-DU-153]:

Kick Off Review

Annual Operation Reviews

Coordination Meetings

Contract Closing Review

The contractor shall attend specific Webex meetings [REQ-NRT-DU-154]:

Pre-integration GO/NOGO

Integration closure

Entry Into Service of CMEMS version

Monthly follow-up meetings

System Evolution Design Review

System Evolution Acceptance Review

The Contractor will attend for information to the meetings hereafter [REQ-NRT-DU-155]:

MFC/TAC Specifications Review

MFC/TAC Design Review

For each review, the Contractor will provide as a minimum the review deliverables defined in the section 5.2.3 [REQ-NRT-DU-156].

The documentation will be provided 4 weeks before the date of each review milestone [REQ-NRT-DU-157].



Date : 06-10-2017

Issue : 1.0


During the review period (from the documentation delivery to the review milestone) Mercator Océan will provide comments. The review is declared successful if there are no outstanding issues of substance, if all the review remarks are answered and their resolution agreed.

Whenever the DU leader cannot attend a management meeting, Mercator Océan will be informed at least three weeks beforehand and shall also be informed of the name of the substitute [REQ-NRT-DU-158].

Without prejudice to the above requirements, the Contractor will appoint the most qualified person to attend the meetings [REQ-NRT-DU-159].

Whenever the relevant person is not able to attend, the Contractor will nominate a Substitute [REQ-NRT-DU-160].

Prior to all Coordination Meetings, the Contractor will prepare a minimal set of handouts, including updated schedule, open risks/issues and proposed solutions, the status of actions. The Contractor will deliver electronics copies of identified handouts to Mercator Océan before each Meeting, 5 working days in advance [REQ-NRT-DU-161].

Whenever necessary, the Contractor will provide ad-hoc information, reports or presentation as a contribution to the specific meeting. The Contractor shall deliver electronic copies of identified handouts to Mercator Océan before each meeting, 5 working days in advance [REQ-NRT-DU-162].

Kick Off Review (KO)

A Kick Off Review will be held at the beginning of the Contract.

Annual Operation Review (AOR)

An Annual Operation Review (AOR) will be held every year to present the status of the service and plan for the coming year:

progress reports on Operations including statistics on resource availability, production performances, etc... and plan for the coming year

progress reports on technical evolutions and developments and plan for the coming year

progress report on other activities, including management, decisions taken, project schedule

Coordination meetings



Date : 06-10-2017

Issue : 1.0


Coordination Meetings will be held twice a year. The purpose of these meetings is to monitor the progress, verify the directions chosen and discuss technical issues. One of the coordination meetings will assess the Contractor’s Annual Activity Plan and specifications of the foreseen evolutions.

MFC/TAC review to attend for information only

In order to be informed on the evolutions to be operated in the Dissemination side, DU leader shall attend to the MFC/TAC reviews providing

MFC/TAC Specification Review (SR): The objective of the SR is to validate the specification of all the evolutions foreseen and assess the readiness for the design phase. The specification review meeting will be done in the framework of the Annual Activity Plan assessment.

MFC/TAC Design Review (DR): A DR is held at the end of the “design” phase. The objective of the DR is to validate the design of all the evolutions scheduled for the next coming year against the specifications and assess the readiness for the development phase. Every year will be held the Design Review meeting of the evolutions scheduled for the next coming year.

Note: Even if there is not a formal meeting with the Contractor at the end of the development phase of each evolution implemented by MFC/TAC (acceptance activities: to assess successful completion of the development and verification activities and to demonstrate readiness for integration), Mercator Océan will provide an acceptance report to the DU Contractor before their integration activities.

System evolution meetings

System evolution will be managed through the AAP and two kinds of milestones: Design Review and Acceptance review.

System evolution Design review

The Design review is held at the end of the “design” phase. The objective of the DR is to validate the design of all the evolutions scheduled and assess the readiness for the development phase. Every year will be held the Design Review meeting of the evolutions scheduled for the next coming year.

System evolution Acceptance review

The Acceptance review is held at the end of the “development” phase. The objective of the AR is to validate the implementation and tests performed. Every year will be held the Acceptance Review meeting of the implemented evolutions.

Integration meetings

Integration activities will be managed through two kinds of milestones: the first one (Pre-Integration GONOGO meeting) to launch the activities, and the second one (Integration closure meeting) to close them. Then the CMEMS version will be put in operations (Entry Into Service of CMEMS version). These meetings will be held through Webex.

Pre-Integration GO-NOGO meeting

The objective of the Pre-Integration GO-NOGO meeting is to launch integration activities, starting with pre-integration, by checking:



Date : 06-10-2017

Issue : 1.0


The scope of the version to be integrated is well defined,

All the required inputs are available,

Test descriptions are available,

The activity schedule is available.

The first Pre-Integration GO-NOGO meeting of the contract will fulfil an additional objective: Closure of

Task1 “Initial settings of the dissemination environment”.

Outputs of the meeting are:

Frozen scope for integration activities,

Validated test descriptions

Validated schedule,

GO/NO GO decision.

Additional output of the first Pre-Integration GO-NOGO meeting of the contract:

Validation of Architecture Dossier first release.

Review and Closure of Task 1 “Initial settings of the dissemination environment”.

Integration closure meeting

The objective of the Integration Closure meeting is to close integration activities, after pre-integration and integration have been performed, by reviewing:

The scope of the tested version,

Test results,

Identified problems and corrections.

Outputs of the meeting are:

Validated test results

Validated integration status (problems and corrections),

CMEMS version ready for Entry Into Service technically speaking.

Entry Into Service of CMEMS version

The objectives of the Entry Into Service is start dissemination activities of the new CMEMS version.

Outputs: Mercator Océan provides the GO decision to the DU operator in order to switch the integration environment into operations.

Follow-up meetings

Web-ex follow-up meetings will be held every month in order to monitor the activities of the period described in the Monthly Report.



Date : 06-10-2017

Issue : 1.0


Contract Close Review (CCR)

At the end of the Contract.

Further details will be provided upon request.



Date : 06-10-2017

Issue : 1.0


V CONFIGURATION MANAGEMENT

‘Configuration Management Plan’ is provided as a separate document.

VI QUALITY ASSURANCE MANAGEMENT

The ‘final products’ must meet both CMEMS requirements as well as needs and we will refer to the

ISO 9001 Quality Management System framework. In particular two ISO 9000:2000 concepts will be

fully considered:

Acceptance criteria: are the standards against which a comparison is made to judge conformity

(i.e. fulfilment of requirements)

Adequacy: means suitable or sufficient for the intended purpose or need.

Other ISO/IEC 25010 elements that will be considered are:

Usability: as "The extent to which a product can be used by specified users to achieve specified

goals with effectiveness, efficiency, and satisfaction in a specified context of use."

Effectiveness: is the extent to which data fulfils the intended use.

Another specific document that will be at the base of the QA management is ISO 9004: A Quality Management Approach, from which methodologies on roles, responsibilities, coordination, project organisation, work environment will be adopted and adapted.

Roles and responsibilities have been defined in Section III.

DUL and DUP will use a systematic approach to reviewing available information (see also section V) and for ensuring that the information is used for decision making. Information will be collected from:

monitoring implementation/ developments,

assessments of the integrity and validity of products,

results of internal audit, self-assessment and benchmarking activities,

risk assessment, and

feedback from MO and other interested parties. Reviews will be performed at planned and periodic intervals (6-months), to enable trends to be determined, as well as to evaluate the organization's progress towards achieving its objectives. Reviews will also be used to identify opportunities for improvement, innovation and learning. Reviews will address the assessment and evaluation of improvement activities performed previously, including aspects of adaptability, flexibility and responsiveness in relation to the objectives.

Reviews will lead to a training methodology about Quality Assurance, as part of a ‘learning process’ (ISO 9004). In this case “learning that integrates the capabilities of individuals with those of the organization”. This will be achieved by combining the knowledge, thinking patterns, and behaviour patterns of people with the values of the organization. This involves consideration of:

stimulation of networking, connectivity, interactivity and sharing of knowledge both inside and outside the working group,

maintaining systems for learning and sharing of knowledge.



Date : 06-10-2017

Issue : 1.0


The DUL and DUD will draft at the start of the project a Project Plan with a definition of the internal management rules and methodologies for quality assurance. This Project Plan will serve as a manual for all partners and will be kept up-to-date in the course of the project. This will include the roles and tasks of the various coordinators and how they will contribute to achieving and safeguarding an overall high quality.

VII RISK MANAGEMENT

‘Risk Management Plan’ is provided as a separate document.

Date post:	28-Aug-2018
Category:	Documents
Upload:	ngohanh
View:	216 times
Download:	0 times

Management Plan -...

Documents