Digital Transformation

Digitalization for the High Seas

The sun is shining in Hamburg, and the mild autumn air is in motion – even though I am perfectly equipped for rainy weather. In early October, shipbuilders from around the world gather in a conference hotel near the harbor for the CADMATIC Digital Wave Forum. The user meeting invites participants to experience CADMATIC’s CAD application for shipbuilding firsthand and to learn about current trends, product innovations, and new developments. The highlight: CADMATIC Wave, an integrated CAD/PLM solution specifically designed for shipbuilding and jointly developed by CADMATIC and CONTACT.

Model visualization simplifies data retrieval and collaboration

After our first coffee, we slowly make our way into the conference hall. The morning is filled with numbers and facts around CADMATIC’s digitalization strategy. In the afternoon, our Managing Director Maximilian Zachries presents CADMATIC Wave to the 200 participants. As we demonstrate the first functionalities of the integrated Product Data Management (PDM), some attendees quickly pull out their phones to snap a photo of the feature. I am somewhat excited – now it’s official. Now we also need the data model. And that isn’t quite so simple.

Cadmatic's Atte Peltola introduces the audience to Cadmatic Wave

CADMATIC’s Atte Peltola presents CADMATIC Wave. (© CADMATIC)

The resounding call for a data model for shipbuilding carries me through the three days in Hamburg. During my conversations with industry colleagues, it becomes evident that the information required and generated in the shipbuilding process must be able to be mapped within the model. Model-centric is the magic word: the ship’s geometry is visualized, including equipment, fittings, and logistics. Information can then be retrieved and added via the specific parts of the model. Model visualizations provide a shared and intuitive view of the ship for all involved trades, significantly simplifying information retrieval. This enhances the efficiency of engineering activities and collaboration, also with partners.

Basing a data model on ship geometry is challenging

Engaged in a discussion with a research associate from the Norwegian University of Science and Technology (NTNU), we stumble upon a question: Is the geometry model even suitable for generating a generic product structure for data storage in the PDM? After all, as a placeholder in a data model, there are quite a few locations in such a ship. And let me put it this way: data models are typically organized along the processes in product creation, not the geometry of a ship model. I am curious to see how we will solve this challenge in CADMATIC Wave.

The evening event takes place on the Cap San Diego, a museum ship in the Hamburg harbor. The rustic flair of a ship’s belly and the lavish buffet create a cozy atmosphere for lively conversations. We talk about life in Finland and Norway and the difference between information and data management. The evening ends stormy and rainy, and I finally put my rain gear to good use and return to the hotel dry and warm.

SEUS brings European shipbuilding to a new efficiency level

At the CADMATIC Digital Wave Forum, I also meet my consortium partners from the Smart European Shipbuilding (SEUS) project for the first time. Among them are representatives from NTNU and CADMATIC, as well as employees from two shipyards, the Norwegian Ulstein Group and the Spanish Astilleros Gondan SA. SEUS is an EU-funded research project with the goal of developing an integrated CAD and PLM solution for shipbuilding. This endeavor goes way beyond the functionalities we develop in CADMATIC Wave. For instance, we aim to incorporate knowledge management and utilize AI for searching within product data.

In this context, the broad positioning of our research department, CONTACT Research, works to our advantage. Our focus areas include not only Digital Lifecycle Management, where we conduct research on digitalization strategies for various industries, but also Artificial Intelligence. The AI product data search we aim to implement in SEUS allows us to bring our self-declared motto to life: “Bringing artificial intelligence into the engineering domains.”

As three days in Hamburg come to an end, three strong impressions remain:

It is necessary to design an abstract data model for shipbuilding. One that contains the modules of a ship and yet can be customized to fit the specific needs of any shipbuilder. This data model must be closely linked to the development process.
Personal exchange and meeting each other face to face have been an enriching experience for me in this new work area. This positive feeling motivates me for my future work in the SEUS project.
In Hamburg, rain gear is a must.

Asset Administration Shell as a catalyst of Industry 4.0

“Country of poets and thinkers” or ” Country of ideas”: Germany is proud of its writers, scientists, researchers, and engineers. And of its meticulous bureaucracy, which aims for absolute precision in statements or indications. Combined, this often results in awkward word creation when naming technical terms. A current example of this is the “Verwaltungsschale” (literally: administration shell), whose innovative potential and central relevance for Industry 4.0 are not immediately apparent.

What is an Asset Administration Shell?

“Verwaltungsschale” is not a dusty administrative authority, but the very German translation of the English term “Asset Administration Shell” (AAS). The AAS is a standardized complete digital description of an asset. An asset is basically anything that can be connected as part of an Industrie 4.0 solution (for example, plants, machines, products as well as their individual components). It contains all information and enables the exchange and interaction between different assets, systems, and organizations in a networked industry. Therefore, it is pretty much the opposite of a sluggish authority and currently the buzzword in digital transformation.

As with many new topics, definitions of AAS vary and are quite broad. From very specific like the Asset Administration Shell as an implementation of the digital twin for Industry 4.0 to the loose description of AAS as a data plug or integration plug for digital ecosystems.

I prefer the representation of the AAS as a metamodel for self-describing an asset. With this metamodel, further models can be generated to provide collected information. Through the use of software, these models are then “brought to life” and are made available to others via interfaces.

Concept and usage of the Asset Administration Shell

As a digital representation of an asset, the AAS provides information or functions related to a specific context through its submodels. Examples include digital nameplates, technical documents, the component or asset structure, simulation models, time series data, or sustainability-relevant information such as the carbon footprint. The information is generated along the various phases of the lifecycle, and it depends on the specific value network which asset information is of importance. Thus, submodels are initially created in certain lifecycle phases, specified and elaborated in subsequent phases, and enriched or updated with information in the further process. Thereby, the AAS refers to either a very generic (type) or a very concrete (instance) representation of an asset.

As assets change over time (as-defined, as-designed, as-ordered, as-built, as-maintained), so does the Asset Administration Shell. Thus, multiple AASs can exist for the same asset over the lifecycle. In order to utilize the information in the AAS within its value network, it needs to be accessible. Access is usually given via the Internet or via the cloud (repository-deployed AAS). In intelligent systems, the management shell can also be part of the asset itself (asset-deployed AAS).

Information can be exchanged in various ways. Either via files, so-called AASX files (AAS type 1), via a server-client interaction such as RestAPI (AAS type 2) or via peer-to-peer interaction (AAS type 3), in which the AASs communicate independently using the so-called I4.0 language and perform tasks cooperatively.

While type 1 and 2 take a passive role in the value network and are more likely to be used with repository-held AAS, type 3 describes an active participation in the value network and is more likely to be used with asset-held AAS running smart products.

Common standards connect!

No matter what type of Asset Administration Shell you choose: Important is that the recipient and the provider speak the same language. To achieve this, the exchange of concrete information must be standardized. Considering the amount of different industries, scenarios, assets, and functions, this is an immense number of submodels that need to be standardized. Organizations and associations such as the Industrial Digital Twin Association (IDTA), formed by research institutes, industrial companies, and software providers, are tackling this mammoth task. The rapidly growing number of members as well as the lively exchange at trade fairs and conferences among each other illustrate the potential for the industry. It is important not to leave SMEs behind, but to involve them in the standardization work in the best possible way.

Conclusion

The Asset Administration Shell is at the core of successful Industrie 4.0 scenarios. It enables manufacturer-independent interoperability and simplifies the integration of all types of assets into a collaborative value network. It increases efficiency within production processes by providing complete transparency of the real-time status of each asset. And it also offers a comprehensive security concept to protect the data. Within a very short time, the AAS has thus transformed from a theoretical construct to a real application in practice. Together with partners from research and industry, we are working within the ESCOM and Flex4Res research projects to make it usable on an industrial scale.

AAS in practice

In CONTACT Elements for IoT, you can create, manage and share asset administration shells. Our blog post ‘The asset administration shell in practice’ explains how companies benefit from this.

With the digitization roadmap to a truly digital company

The digitization of business processes has received remarkable attention in recent years. On the one hand, the Corona pandemic ruthlessly exposed digital gaps, and on the other hand, in view of the political, social and ecological changes, companies are being called upon more than ever to act in a more agile and sustainable way. Motivation is high enough and progress in digitization is becoming more and more visible. However, implementation is usually less based on a digitization roadmap that shows the milestones and waypoints to the goal, but rather on a salami tactic.

Digitalization in small bites poses risks

When I talk to representatives of medium-sized companies about digitization, the answer is often: Yes, we do it all the time! Examples include actions such as the creation of policies to increase the use of Office software features throughout the company, the introduction of a ticket system, or the use of a requirements management tool in product development.

This reflects a common practice of carrying out digitization projects on a divisional or departmental basis, in relation to individual tasks or sub-processes. At first glance, it often seems attractive to plan and implement projects from a departmental or site perspective, because the coordination effort is lower and department-specific solutions can supposedly be implemented quickly.

In principle, implementing demanding projects in manageable steps is a sensible approach. So does generating benefits quickly and making digitization progress continuously visible. However, the fragmented approach also carries risks: This is when the target image of digitization is unclear and the path to achieving it is not adequately described. Here, there is a realistic risk of not achieving essential goals of digitization projects. For example, not exploiting the potential of new, digital business models and thus not driving forward the digital transformation of the company. Or not using the company-wide and cross-company data treasures if the focus is only on local optimization.

The benefits of a digitization roadmap

To put it up front: With a digitization roadmap, companies can minimize the above-mentioned risks with little effort. It provides a reliable, medium-term guideline for all digitization activities in the company, aligned with a clear target image. With its different perspectives on the topic of digitization, it addresses the specialist departments, IT and management. The digitization roadmap should contain some essential information:

What is the company’s level of digitization?
The basis of the digitization roadmap is an inventory of the current level of digitization in the company. For this purpose, the existing target images, requirements, and activities in the various corporate divisions and hierarchies are reviewed. Common maturity models help to assess the company’s level of digitization.
What is the target scenario?
Once the status quo has been established, a clear, coordinated target scenario for digitization can be drawn up. The target scenario contains an overview of the future digitally end-to-end business processes as well as the future application architecture and the necessary information services.
Which sub steps are necessary?
Once the goal is clear, the next step is to define and describe the necessary subprojects. In order to prioritize the subprojects in a meaningful way, the required internal and external resources and the possible project risks are estimated. The information previously obtained from the inventory is also used to extrapolate the benefit and business potential of the individual digitization subprojects. This makes it possible to calculate business cases for the planned projects.
The project team and management are thus able to decide on the subprojects and their prioritization according to objective cost/benefit criteria, resource availability and other company-specific parameters. In this way, today’s digitization bites become defined, evaluated subprojects within an overarching context.
What is the business case?
The high degree of concretization of digitization activities, especially of the relevant business case, is an essential basis for reliable financing of digitization projects. For example, special IT project financiers offer flexible top-up leasing that adjusts the leasing rates to the expected increase in benefits. Or even the financing of internal personnel resources. With such financing models, digitization then even succeeds without any restrictions on liquidity.

Conclusion

In the past, only individual projects were often launched. Currently, however, more and more of our customers are taking advantage of strategic planning with digitization roadmaps. With little effort, they offer a reliable orientation for the digital transformation with a clear target picture, concrete business case and alternative financing options.