Line 16: Line 16:


=Smart, connected solutions: Rollout=
=Smart, connected solutions: Rollout=
Effective management of the rollout process for AIoT-enabled solutions is a key success criteria. How exactly this looks like will depend on many factors: is this for one site or one asset only, or is this for multiple sites with multiple assets? Is this for internal customers only, or for external customers? Will this require customizations for individual target sites?
We have discussed a couple of different examples already, which are representing different scenarios, e.g.:
* Single site, single asset: monitoring of particle collisions at the Large Hadron Collider
* Multi site, multi asset: Rollout of a predictive maintenance solution for escalators in train stations
* Multi site, multi asset with customization: Rollout of a predictive maintenance solution for different users of hydraulic components
The following describes a generalized process which could be suitable, for example, for a multi site, multi asset situation.
During rollout prepration, a portfolio of all relevant assets and sites (e.g. train stations and escalators) must be created. This portfolion must be evaluated and prioritized. Based on this assessment, a project plan including rollout schedule and resouce management has to be created.
Rollout execution will then require a generalized plan which can be applied to each individual site. In this case, it includes site preparation (e.g. aligning with the train station`s facility management, preparing for deployment), asset preparation (e.g. cordoning off the escalators, enabling access to the reqired internal parts), solution deployment (e.g. deploying an IoT gateway and an ultra-sound sensor), testing the solution (e.g. simulating a problem with the escalator and checking if this is recognized by the solution), and finally transferring everything to operations.
Back to the porfolio level, the next area is performance and control. For example, this can monitor the rollout of the escalator monitoring solution and suggest corrections in case of inefficiencies. Finally, if this is a fixed set of sites / assets, the rollout project needs to be closed properly. This will include preparting measurs for new assets being onboarded. For example, also new escalators acquired in the future should be equipped with the monitoring solutions.


[[File:Rollout GTM.png|800px|frameless|center|Rollout of AIoT-enabled solutions]]
[[File:Rollout GTM.png|800px|frameless|center|Rollout of AIoT-enabled solutions]]


=Smart, connected products: Go-to-Market=
=Smart, connected products: Go-to-Market=

Revision as of 11:01, 26 September 2021

More...More...More...More...More...More...More...Agile AIoT Grid

How to introduce our smart, connected products and solutions to their customers, be they external or internal, B2B or B2C? For solutions, this usually involves a dedicated rollout process, while for products the Go-to-Market is important.

Smart, connected solutions: Rollout

Effective management of the rollout process for AIoT-enabled solutions is a key success criteria. How exactly this looks like will depend on many factors: is this for one site or one asset only, or is this for multiple sites with multiple assets? Is this for internal customers only, or for external customers? Will this require customizations for individual target sites?

We have discussed a couple of different examples already, which are representing different scenarios, e.g.:

  • Single site, single asset: monitoring of particle collisions at the Large Hadron Collider
  • Multi site, multi asset: Rollout of a predictive maintenance solution for escalators in train stations
  • Multi site, multi asset with customization: Rollout of a predictive maintenance solution for different users of hydraulic components

The following describes a generalized process which could be suitable, for example, for a multi site, multi asset situation.

During rollout prepration, a portfolio of all relevant assets and sites (e.g. train stations and escalators) must be created. This portfolion must be evaluated and prioritized. Based on this assessment, a project plan including rollout schedule and resouce management has to be created.

Rollout execution will then require a generalized plan which can be applied to each individual site. In this case, it includes site preparation (e.g. aligning with the train station`s facility management, preparing for deployment), asset preparation (e.g. cordoning off the escalators, enabling access to the reqired internal parts), solution deployment (e.g. deploying an IoT gateway and an ultra-sound sensor), testing the solution (e.g. simulating a problem with the escalator and checking if this is recognized by the solution), and finally transferring everything to operations.

Back to the porfolio level, the next area is performance and control. For example, this can monitor the rollout of the escalator monitoring solution and suggest corrections in case of inefficiencies. Finally, if this is a fixed set of sites / assets, the rollout project needs to be closed properly. This will include preparting measurs for new assets being onboarded. For example, also new escalators acquired in the future should be equipped with the monitoring solutions.

Rollout of AIoT-enabled solutions

Smart, connected products: Go-to-Market