The electronic pdf versions of the documents found through http://www.dnv.com/ are the officially binding versions. Copyright Det Norske Veritas.
![[Table of Contents]](/dwicons/b_toc.gif)
|
DNV-OSS-401 Technology Qualification Management
|
SECTION 1
GeneralSec.1
A. General
Sec.1
A 100 Introduction
Sec.1 A
101 This new Offshore Service Specification (OSS) gives guidance
on Technology Qualification Management as a service provided by
DNV.Sec.1
A 200 Objectives
Sec.1 A
201 The objectives of this document are to:
| — | describe DNV's Technology
Qualification Management services for offshore structures and systems |
| — | provide guidance for technology owners and other parties for
selecting and determining the extent of involvement of those carrying
out the technology qualification activities |
| — | provide a common communication platform for describing
the extent of technology qualification activities. |
Sec.1
A 300 Scope of application
Sec.1 A
301 This Offshore Service Specification (OSS) applies to qualification
of technology for offshore structures and systems, particularly
addressing qualification of new technology with reference to DNV-RP-A203.
Sec.1 A
302 This OSS applies to technology qualification within general
technology development projects as well as qualification of new
technology related to offshore field development projects.
Sec.1 A
303 This OSS describes the necessary activities to be carried out
to obtain DNV statements of feasibility, statement of endorsement
and certificate of fitness for service.Sec.1
A 400 Structure of this document
This document consist of three sections and three appendices:
| — | Section 1 - gives the general
scope of the document, background information, definitions and references. |
| — | Section 2 - gives an overview of DNV's general
technology qualification process which is further detailed in DNV-RP-A203. |
| — | Section 3 - describes DNV's services related
to DNV-RP-A203; describes the deliverables from these services and provides
guidance for selection of the scope of work. |
| — | Appendix A - provides examples of DNV qualification statements. |
| — | Appendix B - provides a table that can be used as a
basis for contractual specification of scope of work. |
| — | Appendix C - provides a project start-up check list
to support the DNV project management in establishing good communication
lines with the client. |
Sec.1
B. Background
Sec.1
B 100 Introduction
Sec.1 B
101 Technology qualification is in this document defined as: "the process of providing the evidence that the
technology will function reliably within specified operational limits
with an acceptable level of confidence". DNV's
technology qualification services thus differ from DNV's
third party services (as classification, certification and verification),
which are to confirm that the technology is documented in compliance
with specified codes and procedures.
Sec.1 B
102 New technology is generally not adequately covered by established
codes and procedures. New technology must therefore be qualified
by following a systematic process where the required functionality
and reliability is obtained by identifying uncertainties, which
need to be reduced through adequate qualification methods, such
as testing and analyses. A guideline for such a systematic qualification
process is given by DNV-RP-A203.
Sec.1 B
103 While DNV-RP-A203 provides a general process applicable to
the technology owner and his affiliates, this document describes
DNV's services based on that process. These services are
here divided into three groups:| — | Technology qualification management. |
| — | Fitness for service verification. |
| — | Qualification executions. |
Sec.1 B
104 Technology qualification according to this document, and the
work process as described in DNV-RP-A203 may constitute a necessary
part of product certification, (see guidance note) when the technology
or parts thereof is unproven and/or not adequately covered
by established codes and procedures.Guidance note:
Product certification is used above as a general term to denote independent
verification of a final product versus established codes and procedure,
which is affirmed either by a type approval certificate or by a
project specific statement or certificate. When the technology (or
part thereof) is unproven, and hence not fully covered by established
codes and procedures, then the basis for product certification may
be complemented by technology qualification of the unproven parts.---e-n-d---o-f---G-u-i-d-a-n-c-e---n-o-t-e---
Sec.1
C. Definitions
Sec.1
C 100 General
Sec.1 C
101 The definitions in DNV-RP-A203 also apply to this document.Sec.1
C 200 Verbal forms
Sec.1 C
201 The terms will, can and may are
used when describing DNV's actions or activities, and the
terms shall, should and may are
used when referring to other parties than DNV.
Sec.1 C
202 "Shall": Indicates
requirements strictly to be followed in order to conform to this
OSS and from which no deviation is permitted.
Sec.1 C
203 "Should": Indicates
that among several possibilities, one is recommended as particularly
suitable, without mentioning or excluding others, or that a certain
course of action is preferred but not necessarily required. Other
possibilities may be applied subject to agreement.
Sec.1 C
204 "Will": Indicates
a mandatory action or activity to be undertaken by DNV. (Ref. "shall" for
other parties.)
Sec.1 C
205 "Can": Indicates
an action or activity that DNV will not necessarily do unless specifically
requested by the client. (Ref. "should" for other
parties.)
Sec.1 C
206 "May": Verbal
form used to indicate a course of action permissible within the
limits of the OSS.Sec.1
C 300 Definitions
Sec.1 C
301 Client: DNV's
contractual partner. It may be the purchaser, the owner or the contractor.
Sec.1 C
302 Conceptually feasible: A
technology at an early stage of development is considered conceptually
feasible if the main challenges have been identified and judged
to be resolvable by use of sound engineering practice.Guidance note:
Although a technology has been stated conceptually feasible, there
are still activities necessary to be executed in order prove that
the technology is fit for service. Consequently, there will be a
possibility that the technology contrary to expectations will not be
stated fit for service.---e-n-d---o-f---G-u-i-d-a-n-c-e---n-o-t-e---
Sec.1 C
303 Fit for service: A
technology is considered fit for service when the failure modes
that have been identified through the systematic process outlined
in this OSS have been properly addressed, and the supporting evidence
substantiates that the technology fulfils all stated functional
requirements and meets the stated reliability target.Guidance note:
Although a technology has been stated fit for service, the
technology has not necessarily an in-service record that eliminates the
possibility for failures due to unidentified or misjudged failure
modes. Consequently, there will be a possibility that the technology
contrary to expectations will fail in-service.---e-n-d---o-f---G-u-i-d-a-n-c-e---n-o-t-e---
Sec.1 C
304 Hazard: A deviation
(departure from the design and operating intention) that could cause
damage, injury or other form of loss (Chemical Industries Association
HAZOP Guide).
Sec.1 C
305 HAZID (HAZard IDentification): A
structured review technique with the purpose of identifying all
significant hazards associated
with the particular activity or operation under consideration.
Sec.1 C
306 New technology: Technology
that is not proven. This implies that the application of proven
technology in a new environment or an unproven technology in a known
environment, are both new technology. The degree of new technology will
be classified in categories to be used as input to risk assessment.
Sec.1 C
307 Probability of success: The
probability of completing a qualification activity or a set of qualification
activities within available time and with a successful result.
Sec.1 C
308 Proven technology: In
the field, proven technology has a documented track record for a
defined environment. Such documentation shall provide confidence
in the technology from practical operations, with respect to the
ability of the technology to meet the specified requirements.
Sec.1 C
309 Risk: The qualitative
or quantitative likelihood of an accident or unplanned event occurring,
considered in conjunction with the potential consequences of such
a failure. In quantitative terms, risk is the quantified probability
of a defined failure mode times its quantified consequence.
Sec.1 C
310 Risk reduction measures: Those
measures taken to reduce the risks to the operation of the technology
and to the health and safety of personnel associated with it or
in its vicinity by:| — | reduction in the probability
of failure |
| — | mitigation of the consequences of failure. |
Sec.1 C
311 Statement of endorsement: A
document issued by DNV affirming that, at the time of assessment,
it has been found that the new technology can be proven fit for
service through the remaining planned qualification activities.
Sec.1 C
312 Statement of feasibility: A
document issued by DNV affirming that, at the time of assessment,
the new technology is considered conceptually feasible and suited
for further development and qualification according to the principles
outlined in DNV-RP-A203.
Sec.1 C
313 Certificate of fitness for service: A
document issued by DNV affirming that, at the time of assessment,
the new technology is considered fit for service.
Sec.1 C
314 Technology qualification: A
confirmation by examination and provision of evidence that the new
technology meets the specified requirements for the intended use.
Hence, qualification is a documented set of activities to prove
that the technology is fit for service.
Sec.1 C
315 Verification: An examination
to confirm that an activity, a product or a service is in accordance
with specified requirements.Sec.1
D. References
Sec.1
D 100 References
Sec.1 D
101 DNV-RP-A203 "Qualification Procedure for New Technology".
Sec.1 D
102 DNV Standards for Certification No. 1.2 "Conformity Certification
Services - Type Approval".
Sec.1 D
103 DNV-OSS-300 "Risk Based Verification".
![[-]](/dwicons/i_colpse.gif)