DnV’s Software Class - · PDF fileOS-F201 RP-F201 RP-F202 Wellheads: OS-E101 Mooring: OS-E301 SEMI-SUB ... DNV-OS-D203: A set of best practices to manage software dependent projects

DnV’s Software Class

Trondheim 111015 Even-André Karlsson DnV Norway contact: Are Jørgensen, [email protected]

© Det Norske Veritas AS. All rights reserved. 2

Why Offshore Classification ?

§  Basis for registration in national register and flag – required by IMO for international voyage

§ Represents internationally accepted safety standard

§  Known and recognised by the maritime industry

§ Normal requirement for insurance


The Maritime and Energy industries have worked with structured processes for materials, welding and structures for many decades

§  The welding process is for example well defined with: -  Welding procedure qualification and testing -  Welder qualification and certification -  Non-destructive testing after welding -  Qualification and certification of test personnel -  In service inspections -  Traceable documentation

§  This process is well defined and accepted by everyone in the industry

In Out


Pipeline: OS-F101 RP-F101 RP-F104 RP-F105 RP-F106 RP-F107 RP-F108

Risers: OS-F201 RP-F201 RP-F202

Wellheads: OS-E101

Mooring: OS-E301

SEMI-SUB Safety:

OS-A101 Materials: OS-B101

Hull: OS-C101 OS-C103 RP-C103 OS-C-401 Stability: OS-C301

Marine/Machinery: OS-D101

Electrical: OS-D201

Instrumentation: OS-D202

Fire Safety: OS-D301

Production Plant: OS-E201 Drill Plant:

OS-E101 Helideck: OS-E401

FPSO Safety:




Electrical: OS-D201



FSO Safety:




Electrical: OS-D201



Anchors: RP-E301 RP-E302

Chain: OS-E302

Wire rope: OS-E303

DNV Offshore Codes - Global standards, practices and related services covering many areas and aspects of offshore field development and operation


The offshore industry is facing rapid product innovation with more and more software embedded systems

Mechanical operation

Computer-based operation and monitoring systems

Remote operation and support

§  This evolution changes the risk picture -  Increased dependency on IT systems and increasing system complexity -  New operational challenges and changed requirements to knowledge and competence

§  and creates new demands in the industry -  Transparency and real time information more important -  Operational excellence and improved efficiency expected from new technology


…but the software processes have not been given the same attention in these industries

§  Software processes are treated randomly -  Roles and responsibilities are often unclear -  Little transparency -  Delegation to suppliers and sub-suppliers -  Vague specifications -  Emphasis on testing and in-service failure

mitigation

§  DNV’s ambition is to change the industry practice for working with software

In Out

In Out


Our services is part of a long term development in DNV

Before 2008 2008 - 2010 2010 and beyond

n  DNV develops and acquires competence on software development and quality assurance

n  200+ specialist with experience from:

-  Automotive -  Telecom -  Defence -  Aerospace -  Finance

n  DNV launches the Recommended Practice for Integrated Software Dependent Systems (RP D201)

n  Gather experience from 10+ projects for

-  Drilling rigs -  Cruise ships -  Seismic vessels

n  New Offshore Standard Launched April ‘10

n  First Pilot project started in April ’10

n  Additional pilots to be performed during ‘10

n  Continuous improvement regular updates of the Standard is key for our long-term strategy


Customers and Needs

Owner

Operator

Yard

Supplier

§  Reduce delays in New-builds and Upgrades

§  Shorter time between commissioning and start of operation

§  Reduced downtime caused by software in the operational phase

§  Efficient operations – systems fitting needs of users

§  Get control over running systems and updates

§  Manage suppliers

§  Improve quality to reduce rework during commissioning

§  Fulfill Yard and Owner requirements

§  Improve efficiency and quality of own deliveries


DNV is now launching a new class notation for systems and software - Integrated Software Dependant Systems - ISDS

n  This voluntary class notation is focusing especially on integration of software for various systems

n  The new class notation is based on the document DNV-OS-D203 Integrated Software Dependant Systems

n  We want to standardize software quality assurance for the maritime and energy industries to improve safety, reliability and transparency

n  We have adapted recognized methods from other industries like aerospace, automotive and telecom


DNV-OS-D203: A set of best practices to manage software dependent projects

Five responsibilities:

Owner System Integrator Operator Supplier Independent Verifier

Four confidence levels:

CL0 CL1 CL2 CL3

Lifecycle of five phases:

A. Concept

B. Engineering

C. Constructi

on

D. Acceptance

E. Operation

There is a milestone/Decision Gate between each phase

M0 M1 M2 M3 M4 M5

O O O

140 activities 14 process areas


Confidence Levels

Potential Consequences Suggested Confidence

Level Safety Environmental Business impact

The function not behaving as expected does not compromise safety in any significant way.

Loss of function does not impact the environment in any manner.

Loss of function has minimal impact on the operation. The function might lead to loss of auxiliary processes but does not affect the main purposes of the system. 0

Negligible safety implications. Loss of function may lead to minor pollution.

Loss of function might lead to a temporary shutdown of non-critical systems that are easily repairable. May result in increased operator workload. Loss of function might lead to minor financial loss

1

Loss of function may lead to major injuries or potential for a fatality.

Loss of function may lead to significant pollution.

Loss of function may lead to prolonged loss of the main function of the system. The incident could escalate to major financial loss or severe damage to the system. Degradation of company reputation

2

May lead to multiple fatalities Severe environmental impact Loss of function might lead to catastrophic loss of the system and severe financial impact. Loss of company reputation 3

§  Determined by the potential consequences if a function does work as expected

§  Adapts the expectations on the way of working

§  Decided by the Owner of the system


Disciplines

§ Requirements Engineering

§  Solution Definition

§ Design

§  Implementation

§  Acquisition

§  Integration

§  Verification

§  Validation and Acceptance

§ Reliability, Availability, Maintainability, and Safety (RAMS )

§  Project Management

§ Configuration Management

§  Process and Quality Assurance

§ Risk Management


Activities Examples (1)

Activity Name & Description C.L. Resp.

Collect requirements Owner and operator requirements shall be collected. These requirements should focus on operational needs, but also the constraints the owner is placing on the system. Collection of the requirements may be supported by prototyping, market survey or technology demonstrations. Supplier should be proactive to help the purchaser to formulate its requirements

CL0 SI

Manage change requests Change requests shall be collected and managed. Requests shall be analyzed to assess impact and feasibility. A commission board shall be accountable for decisions regarding change requests and change orders. This change control board shall comprise representatives from the owner, operator, system integrator, and suppliers, as needed.

CL1 OW SI SU OP

Document system design System design shall be documented, including components and interface descriptions as well as operational scenarios and use cases.

CL2 SI


Activities Examples (2)

Activity Name & Description C.L. Resp.

Document component design The design of each component shall be documented.

CL2 SU

Review consistency of interface design Design documents from all components shall be reviewed to verify completeness and consistency of the interfaces between the components.

CL2 SI SU

Define verification strategy The verification strategy shall be defined and documented. It shall define the means to ensure that the system meets the requirements (which product to verify, methods, environments). The verification strategy shall plan the verification activities, define the quality criteria and targets for each verification stage.

CL2 SI


Standard can be downloaded from www.dnv.com


References


Safeguarding life, property and the environment

www.dnv.com

Documents

DnV’s Software Class - · PDF fileOS-F201 RP-F201 RP-F202 Wellheads: OS-E101 Mooring: OS-E301 SEMI-SUB ... DNV-OS-D203: A set of best practices to manage software dependent projects