No edit summary
(Editorial changes as per digital playbook document.)
 
(32 intermediate revisions by 3 users not shown)
Line 5: Line 5:
rect 2737 128 3539 257 [[Digital_OEM|More...]]
rect 2737 128 3539 257 [[Digital_OEM|More...]]
rect 2737 257 3539 390 [[Digital_Equipment_Operator|More...]]
rect 2737 257 3539 390 [[Digital_Equipment_Operator|More...]]
rect 2737 385 3539 518 [[Hybrid_Models|More...]]
rect 2737 385 3539 518 [[Platforms|More...]]
rect 2737 523 3539 655 [[Hybrid_Models|More...]]
rect 2737 651 3539 784 [[Scalability|More...]]


desc none
desc none
</imagemap>
</imagemap>
== Hybrid Models==
 
Hybrid models that combine aspects of the Digital OEM and the Digital Equipment Operator are more often the norm than the exception. Nevertheless, differentiating between these two roles can be very helpful for understanding many of the different concepts associated with them. This section looks at hybrid models in more detail, following again the ''why'', ''what'', ''how'' structure from the Introduction.
 
__TOC__
__TOC__
==WHY==
[[File:0.2.3 Why.png|800px|frameless|center|Why]]


==WHAT==
=WHY=
[[File:0.2.3 Comparison.png|800px|frameless|center|Comparison]]
In many cases, companies will seek to create an integrated business model that combines the OEM and operator roles. For example, an electric vehicle manufacturer might also choose to own and operate its own network of fast charging stations (such as Tesla with its network of supercharger stations). In this case, combined KPIs are likely to include revenue and usability.  
===Example: Predictive-maintenance-as-a-Service===
 
[[File:0.2.3 Hydraulic Example.png|800px|frameless|center|Example: Predictive Maintenance]]
Alternatively, the OEM may choose an Asset-as-a-Service business model, which also means that it will play a hybrid role. In this case, the hybrid model will be based on a combination of typical OEM and operator KPIs, e.g., including both revenue and OEE.
====Hydraulic components in the manufacturing supply chain====
 
[[File:0.2.3 Hydraulic Overview.png|800px|frameless|center|Hydraulic Component Supply Chain]]
Another example of a hybrid model is the Productized Retrofit Solution, e.g., a productized predictive maintenance solution. Here, the KPIs will combine revenue with costs for customer-specific modifications to the solution.
====Predictive maintenance for hydraulic components====
 
[[File:02.3 Hydraulic Predictive.png|800px|frameless|center|Predictive maintenance for hydraulic components]]
 
====Development process vs custom AI solutions====
[[File:0.2.3 Why.png|800px|frameless|center|link=|Why]]
[[File:0.2.3 Hydraulic Process.png|800px|frameless|center|Predictive maintenance for hydraulic components - process]]
 
=WHAT=
The definition of ''What'' exactly constitutes a hybrid model will heavily depend on the specifics of the product or solution. The table following compares the typical aspects of the Digital OEM and the Digital Equipment Operator, including aspects such as typical customers, offering, positioning of the assets on the balance sheet, typical KPIs, level of standardization, etc. A hybrid model might differ in any of these dimensions, or provide a combination thereof.
 
[[File:0.2.3 Comparison.png|800px|frameless|center|link=|Comparison]]
 
==Example: Predictive-Maintenance-as-a-Service==
A good example of a hybrid model is the Predictive-maintenance-as-a-Service solution described in detail in the [[Predictive_Maintenance_for_Hydraulic_Systems|case study from Bosch Rexroth]]. One product category offered by the company are hydraulic components, including hydraulic motors, pumps, tanks and filters. These hydraulic components are used in many different applications, including manufacturing, mining and off-road vehicles. In order to offer customers of these hydraulics products an improved maintenance solution, Predictive-maintenance-as-a-Service for hydraulic components was developed. The main issue here is that it turned out that the algorithms for detecting anomalies related to the hydraulic components differ from application to application. To address this, Rexroth had to establish a setup that allowed them to standardize the offering as far as possible, and provide customer-specific customizations as efficiently as possible. This is a good example of a productized retrofit solution as per the table preceding.
 
[[File:0.2.3 Hydraulic Example.png|800px|frameless|center|link=|Example: Predictive Maintenance]]


===Example: Drone-based Facade Inspection<span id="drone"></span>===
==Example: Drone-based Building Facade Inspection<span id="drone"></span>==
[[File:0.2.3 Drone Insepection.png|800px|frameless|center|Example: Drone-based Building Facade Inspection]]
Another good example of a hybrid model is the Drone-based Building Facade Inspection developed by TUEV SÜD. Again, this is described in more detail in the [[Drone-based_Building_Facade_Inspection|case study]]. This solution utilizes drones equipped with cameras, thermal scanners, and LIDAR (laser scanners) to create a detailed scan of the facades of buildings. On the drone, AI is used for flight path control, collision avoidance, and position calculation. In the TÜV Cloud, AI is used to detect anomalies such as concrete cracks, concrete spalling, corrosion, etc. The customer gets a detailed report about any potential problems with the facade that need to be addressed as part of the building maintenance process. In this case, TÜV SÜD is both the OEM and operator of the solution.
====Drone control====
[[File:0.2.3 Drone Control.png|800px|frameless|center|Drone Control]]
====Customer Journey====
[[File:0.2.3 Done Journey.png|800px|frameless|center|Drone Customer Journey]]
====Drone data analysis: Facade Inspection====
[[File:0.2.3 Drone Facade.png|800px|frameless|center|Drone-data analysis / building facades]]


===Example: Parking Spot Detection (Multi-Sided Business Platform)<span id="spot"></span>===
[[File:0.2.3 Drone Insepection.png|800px|frameless|center|link=|Example: Drone-based Building Façade Inspection]]
This is an example for a multisided business platform enabled by AIoT: Cars equipped with ultra-sound sensors can detect available parking spots as they are passing by them. This data is collected in a centralized platform and monetized, e.g. via a find-a-free-parking-spot app.
[[File:0.2.3 Parking Spot Detection.png|800px|frameless|center|Example: Parking Spot Detection (Multi-Sided Business Platform)]]


==HOW==
=HOW=
[[File:0.2.3 How.png|800px|frameless|center|Hybrid Models: HOW]]
Again, there is no common blueprint for implementing hybrid AIoT business models. However, it is clear that a hybrid model must somehow combine the key processes of the Digital OEM with those of the Digital Equipment Operator, as indicated by the figure following. As we noticed, for example, in the Drone-based building inspection case study, TUEV SUED is both manufacturing and operating the solution. This will be true for many hybrid models.
[[File:0.2.3 How.png|800px|frameless|center|link=|Hybrid Models: HOW]]

Latest revision as of 02:45, 24 June 2022

More...More...More...More...More...More...Hybrid Models

Hybrid models that combine aspects of the Digital OEM and the Digital Equipment Operator are more often the norm than the exception. Nevertheless, differentiating between these two roles can be very helpful for understanding many of the different concepts associated with them. This section looks at hybrid models in more detail, following again the why, what, how structure from the Introduction.

WHY

In many cases, companies will seek to create an integrated business model that combines the OEM and operator roles. For example, an electric vehicle manufacturer might also choose to own and operate its own network of fast charging stations (such as Tesla with its network of supercharger stations). In this case, combined KPIs are likely to include revenue and usability.

Alternatively, the OEM may choose an Asset-as-a-Service business model, which also means that it will play a hybrid role. In this case, the hybrid model will be based on a combination of typical OEM and operator KPIs, e.g., including both revenue and OEE.

Another example of a hybrid model is the Productized Retrofit Solution, e.g., a productized predictive maintenance solution. Here, the KPIs will combine revenue with costs for customer-specific modifications to the solution.


Why

WHAT

The definition of What exactly constitutes a hybrid model will heavily depend on the specifics of the product or solution. The table following compares the typical aspects of the Digital OEM and the Digital Equipment Operator, including aspects such as typical customers, offering, positioning of the assets on the balance sheet, typical KPIs, level of standardization, etc. A hybrid model might differ in any of these dimensions, or provide a combination thereof.

Comparison

Example: Predictive-Maintenance-as-a-Service

A good example of a hybrid model is the Predictive-maintenance-as-a-Service solution described in detail in the case study from Bosch Rexroth. One product category offered by the company are hydraulic components, including hydraulic motors, pumps, tanks and filters. These hydraulic components are used in many different applications, including manufacturing, mining and off-road vehicles. In order to offer customers of these hydraulics products an improved maintenance solution, Predictive-maintenance-as-a-Service for hydraulic components was developed. The main issue here is that it turned out that the algorithms for detecting anomalies related to the hydraulic components differ from application to application. To address this, Rexroth had to establish a setup that allowed them to standardize the offering as far as possible, and provide customer-specific customizations as efficiently as possible. This is a good example of a productized retrofit solution as per the table preceding.

Example: Predictive Maintenance

Example: Drone-based Building Facade Inspection

Another good example of a hybrid model is the Drone-based Building Facade Inspection developed by TUEV SÜD. Again, this is described in more detail in the case study. This solution utilizes drones equipped with cameras, thermal scanners, and LIDAR (laser scanners) to create a detailed scan of the facades of buildings. On the drone, AI is used for flight path control, collision avoidance, and position calculation. In the TÜV Cloud, AI is used to detect anomalies such as concrete cracks, concrete spalling, corrosion, etc. The customer gets a detailed report about any potential problems with the facade that need to be addressed as part of the building maintenance process. In this case, TÜV SÜD is both the OEM and operator of the solution.

Example: Drone-based Building Façade Inspection

HOW

Again, there is no common blueprint for implementing hybrid AIoT business models. However, it is clear that a hybrid model must somehow combine the key processes of the Digital OEM with those of the Digital Equipment Operator, as indicated by the figure following. As we noticed, for example, in the Drone-based building inspection case study, TUEV SUED is both manufacturing and operating the solution. This will be true for many hybrid models.

Hybrid Models: HOW