Incremental deployment and scalability

A key success factor for a multi-site rollout is to structure the deployment steps in a way to realize benefits as early as possible without overwhelming the end users on their daily job. An incremental rollout approach helps to ensure a fast adoption on the stepwise delivered solution scope and limits the disruption of the daily business on the shop floor. To move the operational workforce stepwise out of their today’s comfort zone reduces the program risk, however sometime only a 'big bang' approach can be realized. In that case rollback scenario’s will be applicable.

The AVEVA Composable MES enables a structured approach of incremental deployments. The modularization and composability ensure a seamless extension of the installed use case base and also the exchange of individual use cases when required. This enables a detailed planning of what site will get when what set of use cases deployed. This also limits the risk of missing specifications during the design phase. The exchange of modified/enhanced use cases can happen whenever required.

The abstracted program plan below shows some typical deployment scenarios the AVEVA Composable MES can support. The program starts with the identification of available use cases in the AVEVA use case library. This initial set of use cases can be deployed rapidly and generates fast benefit generation in an early stage of the program.

In a second step, the leftover scope after the first step of fast benefit realization will be divided in meaningful increments to be delivered by (sub) projects of the overall program. These increments can require changes of existing use cases, or the creation of completely new use cases based on the specialization of the customers production.

Each project will deliver value added scope in short phases and delivers 'installable use cases' for the further deployment planning.

The figure above illustrates typical example scenarios covered by the AVEVA modular and Composable MES: 

• Increment can be installed fully or partially 

• Increment can be installed parallel or sequentially (sequence of site is variable) 

• No need to rollout all Use cases of an increment to all other sites before you can install the next increment (no dependency) 

• Increments can be installed partially on a site in a first step and another part can be installed later (or never) 

• Independency of the sequence of "site-extensions"