What does an implementation look like?
A standard Mingo implementation schedules a 90-minute meeting, once-a-week at the same day and time for trainings.
Every implementation will be a little different, as the needs of each company is a little different, but the following outline should help give a better understanding of the level of effort required to get up-and-running on Mingo.
The Blueprint phase
Kickoff Call
The blueprint phase starts with a kickoff call.
The purpose of the kickoff call is the give your team a chance to meet their Mingo implementation team, discuss your goals, and to outline the implementation process.
Following the kickoff, we will try to find a day and time that we can meet for 90 minutes every week for the next 4-5 weeks depending on whether you plan to use the work order scheduling functionality in Mingo.
System Overview
The system overview will be our week 1 meeting. This meeting has two main purposes.
1. Introduce your team to all of the reporting tools available in Mingo
2. Decide which reporting tools we will need to use to achieve your goals
This conversation should result in the creation of a document we call 'The Blueprint', which outlines the optimal path we will take to achieve your goals.
Software and Hardware Paths
With 'The Blueprint' in place, we start the work of implementing Mingo.
There are 2 concurrent projects we begin in week 2. Each project will have it's own team, although there may be overlap.
The software team will focus on learning how to use Mingo to model and track your operations.
The hardware team will focus entirely on ensuring the data collection needed to support our vision is installed and giving accurate results.
If you're using manual data collection only, the hardware path can be ignored.
Software Trainings
These 3-4 trainings are typically schedule for the same 90 minute time slot on the same day for 3-4 weeks.
Admin Training 1 & 2
Our week 2 and 3 trainings will be focused on teaching about the configuration options available to you in the 'Administration' tab.
Initially we will learn about basic administration tasks like adding new users, setting up permissions, and learning about the ways Mingo enables you to model your operations as easily as possible no matter how complicated they may be.
We will end this training by learning to configure aspects of the system meant to model your operations such as setting cycle time targets, adding in additional downtime reasons, and adjusting your shifts to capture overtime.
Scheduler Training
This training is included in any implementation where the end goal involves being able to track specific work orders or jobs. We will discuss with your team what level of scheduling you have today, and what aspects of the scheduling fit best within Mingo.
Go-live Plan
By week 5, or 4 if not using scheduling, we should be finished configuring Mingo so that it is ready for us to begin collecting data.
For this last meeting we will focus on outlining the reporting tools we want visible day 1 and how we will ensure standards on collecting any data we will need from the operators themselves.
Hardware Installation
This can vary greatly depending on the style of data collection you've chosen to employ, but there is a general process any installation follows.
Hardware Overview
After 'The Blueprint' has been finalized, we will have a meeting with our hardware team to outline the approach we will be taking for data collection. At this point, any changes needed to the hardware approach in order to achieve the goals outline in the blueprint will be discussed and finalized. If any additional hardware is needed it will be ordered following this meeting.
Configuration and Ship
For most hardware, it will initially be shipped to a Mingo engineer so that it can be pre-configured and tested. This process typically takes 1-2 business days upon receipt of original shipment.
Installation
Once the hardware has arrived on-site it will need to be installed. This can range from straight-forward tasks like running network connections to equipment, to more sophisticated efforts like wiring in to existing signals on the equipment or configuring the PLC to allow data-sharing.
Mingo does not offer installation services directly, but can make recommendations to partners if you would lack the internal knowledge to make the necessary changes or your team members that have the know-how lack the time to take on another project.
Verification
Once all of the hardware installation has been finalized, the hardware team will reconvene to confirm we are seeing all of the data we need end-to-end, and that the data we are seeing seems accurate to what we would expect to see.
A more thorough verification process will happen during go-live.
Go-live
Once both software and hardware paths have achieved their final stages, a Mingo representative will come on-site to help launch our first day of data collection. This process involves a short training for the operators followed by a live test of our data collection. We will then review the data to confirm it meeting expectations.