ABS - 272
GUIDANCE NOTES ON QUALIFYING NEW TECHNOLOGIES
Organization: | ABS |
Publication Date: | 1 April 2017 |
Status: | active |
Page Count: | 45 |
scope:
Overview
These Guidance Notes describe the ABS approach for qualification of new technologies to confirm their ability to perform intended functions in accordance with defined performance requirements. They also provide details of the required submittals, the ABS review process and the key interaction points with ABS during the new technology development.
This document introduces a systems engineering approach to qualification that allows for systematic and consistent evaluation of new technologies as it matures from a concept through confirmation of operational integrity in its intended application. The approach is divided into a multi-stage process that is aligned with the typical product development phases of a new technology. The qualification activities within each stage employ risk assessments and engineering evaluations that build upon each other in order to determine if the new technology provides acceptable levels of safety in line with current offshore and marine industry practice. The qualification efforts by all stakeholders including the vendor, system integrator and end-user at each stage are recognized and captured within a new technology qualification plan (NTQP). Completion of qualification activities as identified within each stage of the NTQP results in a Statement of Maturity being issued by ABS attesting to the maturity level of the new technology.
The process is also compatible with approaches based on technology readiness levels (TRLs), (e.g. API RP 17N/Q, ISO 16290/NASA, and US DoD); and can be tailored to projects that require the use of multiple pathways to qualification. The comparison of ABS Qualification Stages with industry TRLs can be found in Appendix 2.
It is to be noted that when applying these Guidance Notes for certification or classification purposes in conjunction with Novel Concept Class Approval process, the primary driver for classification acceptance will be safety even though there may be additional functional requirements (e.g., reliability) defined by the client.
Document History
