ISDS class notation

To ensure on-board computer systems work together, DNV offers the class notation for Integrated Software Dependent Systems.

It can take many months for a vessel to be ready for operations. And  often, problems arise which are related to complex systems not designed to work together – potentially lowering the efficiency of operation for years.

By opting for the DNV ISDS class notation, all parties involved – the owner, yard and suppliers – perform well-defined activities that make sure the individual systems are delivered according to best practices within the software industry. What’s more, they must ensure the systems are designed and verified to actually work together when it matters the most.

DNV monitors the activities in question throughout the system’s entire life cycle and regularly reports on any gaps so that these can be dealt with as early as possible. 

The ISDS standard is based on experiences from other industries. It contains a number of practices, mainly:

• Integration of software-dependent systems into ships and offshore units
• Communication and cooperation between stakeholders through specific activities and responsibilities for each organization
• Proven-in-use software development processes, including RAMS definition, requirement traceability, reviews and software testing
• Planning and verification of system integration with a clear definition of responsibilities

With the DNV ISDS class notation, you can profit in many ways:

• Less problems and delays during commissioning, because the systems have been through a more thorough verification scheme before they are brought on board
• Assurance that owner-specific requirements are identified and managed throughout the project
• Early knowledge about obsolete risks, also for third-party software components (e.g. Microsoft Windows) to enable you to plan for updates and avoid unexpected updates initiated by the system’s supplier
• Assurance that all technical interfaces are identified early and managed throughout the project – ensuring interoperability between different systems can be systematically verified
• Early verification that the systems will work together as a whole in real-life operational situations, reducing the risk of last-minute changes and easing the actual operation of the systems
• Full insight and control over the changes made to the software after FAT make sure that there are no surprises after a change has been made
• Verified use of proven methods for good system and software development, ensuring that the quality of the system and the documentation is high and fit for use
• Less problems with the systems during operations, leading to fewer incidents and more productive time