28418 members and growing – the largest networking group in the maritime industry!

LoginJoin

Saturday, February 24, 2018

Maritime Logistics Professional

What is a Digital Ship (Twin)?

Posted to Shipbuilding and Offshore Software (by on January 19, 2018

What is a Digital Ship (Twin)?

  • Image: SSI
  • Image: SSI
We have heard the term “digital twin” being used more frequently throughout the literature we read or even at conferences we attend. I have also written several blog posts about the benefits of the digital twin as well as Achieving the Digital Twin. However, after receiving several inquiries about, “what is a digital twin?” I realized that I have not described the concept. Even though there are some really good resources that talk about the digital twin, I thought I would provide a very high-level view from a shipbuilding perspective. I also thought I would “simplify” it by providing an example which will hopefully resonate with you.

Very High-Level View
The concept of digital twin is not new. Its origins can be tracked back over a decade ago using different names which were not as catchy as the digital twin. The idea of the digital twin is that for each physical product such as an individual physical ship there is one and only one exact digital replica. The evolution of the physical ship throughout its lifecycle will mirror the digital version. This means if any changes happen to the physical asset, the digital version will also get updated.

This does mean for every single ship we produce there will be one and only one digital twin. Even each sister ship will have their own digital twin representation because we all know there are no two ships that are the same, ever.

The digital twin concept is similar to the shipbuilding term “As-Built” but goes a lot further throughout the entire lifecycle of the ship. As with the As-built terminology, all the geometric data and the attributes originating from the engineering CAD tool are included. However, much more data would be required to be a “true” digital twin. This will include linking to items such as:
  1. Class approvals
  2. Requirements of the ship linked to the items (parts, assemblies, etc.) that satisfy them
  3. Change Requests of clients and linked to items which are satisfy change request
  4. Vendor Furnished Information (VFI) linked to each instance of the item (engine, valve, pump, etc.)
  5. Production processes such as welding, assembly sequencing, workstation/workcenter
  6. Simulations and calculations
  7. Paint information

As well, information after delivery will be associated with the digital twin such as:
  1. Service records of replaced items for maintenance, warranty, etc. with information being associated to items
  2. Actual sensor data of items which record data
  3. Repair and retrofit changes
  4. Class surveys
  5. Removal of fouling documentation

The digital twin can add value throughout the lifecycle (conception, design, engineering, construction, procurement, testing, delivery, operations, etc.) of the ship; however, you will hear a lot about how it can significantly improve operations of a ship in the shipping industry. This is related to a parallel technology IoT which allows us to access real-time data from the sensors on the ship to make better informed decisions. There is no doubt that a digital twin can improve operations for the owner/operator; however, there is just as much benefit which can be leveraged prior to all stages before delivery. Not to mention that it will be the shipbuilders and designers which will have to build the digital twin for the owners/operators to leverage as I mentioned in my blog post Future of Shipbuilding: Detail Design and Production Planning (Part 2).

Digital Twin Example
I hope the information above provided a high-level overview of the digital twin. To aid in my attempt to explain what the digital twin is I thought I would also provide a simple example of a digital twin. The example is the same example I used in my blog post Business vs. Digital Transformation which is Google Maps.

Think of the roads and buildings in your city as your product (ship) and the information stored in Google Maps (street names, office buildings, restaurants, speed limits, parks, gas stations, links between information, etc.) as the single digital representation or the digital twin.

When there is a new road or building added or traffic patterns change, then the information in Google Maps is updated to reflect the real physical object (the roads & buildings).

With the digital twin you can better interact and consume information from your product with accurate real-time data. For example, you can search a location and be provided with its location on the map. Taking it one step further, people’s phones with GPS enabled are in essence an IoT device allowing you to get real-time information such as traffic congestion. This now allows the digital twin to not only show you the location you entered but also the fastest real-time route considering all traffic at the time of the search. The possibilities are endless when you have the digital twin.

Before you Criticize

I know the roads are not Google maps products, road/building information does not update all the time, etc. but hopefully you can get around those inconsistencies to understand the essence of what I am trying to convey.

A Good Enough Digital Twin
There is a lot of discussion about how complete a digital twin needs to be. Does it need to contain all possible information to be considered a twin?

In my opinion, a digital twin ideally would have all information but practically it will only have a subset of information. You do not want to waste time collecting information of anything that you will not action in the future. Also, your first iterations of your digital twin will only have a small subset of the information you want/need. This is 100 percent fine as the only way to get the digital twin you deserve is if you take small, value-adding steps.

Google maps is probably closer to a digital twin than we will get in manufacturing any time soon but it is also not perfect. For example, it is not always updated when a new road is complete. Some information is incorrect as it does rely on non-paid community members to update information. Also, there are locations that are off a major road like mall parking lots which do not work as well as on streets.

So even though Google Maps is not a 100 percent complete representation of its physical product, it is still a good enough digital twin.

Multiple Digital Twins?
For most practical purposes I believe we will have an issue with creating and maintaining one all-encompassing digital twin of our asset. As with Google Maps which has a lot of great information, it does not have all the information for a city planner. They will need additional information such as locations of water pipes, electrical grid information and various other types on important information.

This is where I believe we will have several platforms (software tools) which will contain certain types of information of the digital twin. Again, it would be nice to have just one, but there does not look like there is any possible platform/solution which will be able to hold all information despite what many software vendors say.

This is where you will see (hopefully) many software solutions/platforms that support a specific portion of the digital twin and link together to build a more comprehensive and unified view of a digital twin. If you refer to the Google Maps example, it is exactly this strategy that they used. The Google Maps platform is used for several other services which provide more valuable insight from calling a cab, getting restaurant reviews, seeing nearby friends, etc.

However, as mentioned before, you will see companies starting to leverage the digital twin with a single platform as this is the natural first step and will still add tremendous value for their business.

Closing Remarks
The digital twin concept has been around for over a decade; however, it seems to be getting a fair share of the limelight, and rightfully so. The benefits of implementing the digital twin can be huge in the short term and in the long term will be a requirement of doing business in manufacturing business such as shipbuilding.

A digital twin (digital ship) is “simply” a digital replica of the physical asset. It in theory includes all information about the ship; however, in practice in the near future will only contain a subset of the information. There is one and only one digital twin for every single ship, no more, no less. The digital twin will evolve with the physical ship and should mirror each other at all times.

IoT in many industries is what is driving the adoption of the digital ship; however, there is a lot of benefit that can be realized even without IoT.

There is no single platform which can holistically hold the entire digital twin. This is where you will see strategies similar to the ones used by Google Maps (and SSI😊). Effective strategies involve providing a platform that others can build on to fill out the digital twin.

I leave you with this quote:

“Digital twins are becoming a business imperative, covering the entire lifecycle of an asset or process and forming the foundation for connected products and services. Companies that fail to respond will be left behind.” -Thomas Kaiser, SAP Senior Vice President


The Author
Denis Morais is CTO of SSI where he is responsible for developing and directing the strategic product vision for SSI’s software and services. This involves analyzing industry needs and technological trends to prioritize SSI product creation and enhancement. Denis oversees SSI’s development team and consults with clients directly to implement optimized solutions that address their unique constraints and business requirements. Denis is a world authority regarding the future of shipbuilding and technology. He is an award winning author, writes a popular blog, and is a sought out presenter at international conferences. He is an active participant in several shipbuilding and technology organizations such as RINA, SNAME, the Autodesk Developer Network, VIATeC and Autodesk University.

This entry is republished from SSI's Waveform blog.

Tags: software technology shipbuilding