The time spent to implement the predefined EMS template is five days. Using cloud technology and working with predefined templates accelerates the process. This chapter described the project activities and customer participation.

Activities and project planning

The table below shows the estimated time spent per activity. The project distinguishes five phases. Most time is spent on adjusting the dashboards to the customer needs. The table below displays the project activities, estimated duration and planning.

ASB = Analytics for Industry, Cust = Customer

All data prerequisites must be met, and the data meets the described quality conditions to be able to do the project in 5 days and avoid delays in lead time. Bringing data to the cloud and preparing it for EMS usage is typically a separate project in the preliminary phase of the EMS implementation project. Time spent on this project highly depends on the maturity of the industrial automation systems, data and network infrastructure. Analytics for Industry can advise on this project as well as helping to find a trusted and experienced partner (if needed) to set up the automated data publishing process.

Customer participation

Customer participation is key to realize a successful implementation. The customer will be involved at every step of the way to not only make sure the EMS solution meets the requirements, but also to ensure the end-users understand how data is transformed before it reaches the dashboard KPIs. Trust in the numbers that are being shown in a dashboard is the most important aspect of a dashboard being used or not.

The customer is required to perform the following activities during the implementation project:

  • Grant Analytics For Industry Access to Insight, BI Gateway, and the BI-Tool (1.1 in the table above). Then, make sure the right permissions are set to perform the activities.

  • Assign an internal product owner with the following responsibilities:

    • Be a central point of contact for end-users and Analytics for Industry (during implementation and aftercare)

    • Owning the taglist and metadata for EMS (master data management)

    • Identify all potential end-users of the system and map their most desired EMS needs

  • Attend at the meetings and remote sessions that are being organized:

    • Kickoff (1.3 in the table)

    • Insight dashboard demonstration (2.4 in the table)

    • BI Gateway demonstration (3.4 in the table)

    • Custom dashboard workshop (4.3 in the table)

    • Participating in 1 or 2 dashboard development workshops and/or short feedback meetings (4.4 + 4.5 in the table). The main goal is to ensure the dashboards being built match customer requirements. We also want to make sure data in the dashboards looks realistic (contribution to data validation). Next to this the customer can experience the self-service possibilities of the software during the sessions to get better understanding in the data pipeline and software functionalities

    • Project delivery and evaluation meeting

  • Prepare the following for presentation during the kickoff meeting:

    • Production process explanation (provide us with documentation)

    • Tag and available data explanation

    • Input on different and additional dashboard requirements

  • Participate in the dashboard user training with at least 2 persons

  • Provide Analytics for Industry with an Excel file containing all requested metadata for all tags described in data prerequisites. Analytics For Industry will provide the customer with the file that needs to be filled in

Aftercare & support

After implementation and go-live Analytics For Industry will keep supporting the software and solution. The software can be described as the product in general, the solution is what has been built/configured in the software within the 5-day implementation scope.

See Service Level Agreement