<aside> ⬅️ Back To: How to Set-Up Evocon
</aside>
<aside> ➡️ Skip To: Troubleshooting
</aside>
| [✔️] | Pre-Requisite | Responsibility |
|---|---|---|
| [ ] | The hardware is connected, and production signals are appearing on Shift View | CUSTOMER* |
| [ ] | Key users have accounts and are aware of support channels available | CUSTOMER |
| [ ] | Essential database settings are configured | CUSTOMER |
| [ ] | The customer has read and acknowledged the 7 best practices to improve OEE and productivity | CUSTOMER |
| [ ] | Agree to the end date of the trial (usually 30 days after the above is true) | CUSTOMER & PARTNER |
The following sections give guidance on how to help your client run the free trial, and our guidance and best practices on how to make it a success.
When a client decides to start the Evocon trial, they may already have some expectations about what they will gain from trialing the system.
It is important, both during the discovery call and implementation process to understand exactly what are their expectations and translate those expectations into key success criteria or a specific measurable goal that can be achieved during the trial. This will be valuable during the negotiations towards the end of the trial.
In addition, these expectations and desired outcomes give an indication of which product features will be the most useful for a client during the trial. Evocon has a vast amount of advanced settings and features, and it is neither necessary nor advisable to introduce a client to all of these settings during the initial stages of the trial. Instead, it is recommended to identify which features will best support your client in achieving their goal, and ensure that they are aware of their existence.
For example, if a client wants to track their machine downtime, a more specific goal might be to have the reason for production downtime accurately recorded in 80% of cases. And the advanced features which would support this goal might be auto-commenting downtime based on shift patterns, the maximum duration of stop reasons, and ensuring that stops and speed losses are correctly defined.
On the other hand, if a client expects to improve communication, a goal might be to have one user in each relevant department (e.g. operations, maintenance, and purchasing) with their own dashboard set up. Features that may support improved communication are mandatory comments, stop reason alerts, and the message system.
If your client has a goal for the trial and you are not sure which features are available to achieve this, contact your account manager for recommendations.
The following is a plan for the trial period which we share with the Project Champion when working with customers directly. You may find this beneficial to share with your customer, as it encourages adoption and introduces functionality at an appropriate pace.
Evocon Free Trial Plan for Partners [ready for review]
The following tasks are the essential actions that an operator must know how to complete, for the trial to be a success. Please ensure that your project champion is aware of these, and has communicated both how to complete these tasks, and why they are important to the operations team.
In addition, the following guide can also be shared with the operators who will use the Evocon system;