We’d like to give you a sense of how Parsable implementation works so you can factor this into your planning. In this section, we follow best practices for deploying any enterprise-class software or procedure-based system, but we will demonstrate how this value can be delivered in a very compressed timeline.
1. Reconfirmation of Focus and Scope – Duration: 1-2 Weeks
Before we begin implementation, it is important to reconfirm the results of the discovery process when our customers buy our solution. In the buying process, we work with our customers to identify which KPIs that are heavily impacted by people processes they want to impact. As corporations change priorities, we make it a point to reconfirm that the customer’s implementation team wants to drive the business to the same result. If there is a change in company priority, we may recommend an additional workshop to identify processes that would most drive
In general, we recommend that our customers choose processes that will strongly impact key KPIs, are widely used in all facilities, and take the shortest time to implement so that more people at the company can learn about Parsable and the benefits of standardization. Additionally, if the process is used in multiple facilities, there is an exponential effect that occurs where best practices and issues that happen in multiple locations quickly become part of the same
2. Rapid Start Phase – Duration: 6-12 Weeks
In this phase, it is critical to deep dive into processes to
After the first few procedures are created, we begin training the trainers who will be the rollout champions for this new solution. We use these initial solutions to show them how to use Parsable and how to roll out jobs in their teams. We also show them how to monitor work as it is being performed. In many cases, we also train them to utilize the data Parsable generates to replace previously paper-based reporting. Once the trainers have been trained and the procedures have been written, it is time to begin rollout.
At this point, we work with customers to consider the processes they will employ to bulk load devices, determine who receives one, distribute devices, and deploy procedures to the devices and ensure that they are properly cared for, charged regularly, and used correctly to upload data to the platform. When customers are ready to roll out Parsable to the first
As the first facilities start using Parsable, we also begin creating an integration blueprint to ensure that customers have a complete plan for what will trigger human work and where data collected needs to be delivered.
3. User Adoption Phase – Duration: 3-18 weeks, depending on
number of locations, countries.
In the User Adoption Phase, we help our customers deploy other use cases. This is where other work groups and often other business units get involved. The initial rollout at the company serves as the blueprint here as users want to hear about the experiences at their own company. This is the phase where scale happens as questions around authoring, data collection, data use, reporting, device deployment, and device etiquette have all been answered.
In practice, we find that customers accelerate rapidly in this phase, taking control of their implementations and rolling out new business units at an increasingly faster pace. Where an initial deployment might have taken 9 weeks, additional groups might take as little as three weeks, if proper attention has been paid to procuring devices and training staff.
Additionally, in this phase planning and design begins for any required integrations identified in the first phase.
4. Integration Phase – Duration: 10-18 weeks, depending on scope
The final phase of rollout is integration. Here we are working with our customers to ensure that all triggering systems and all systems requiring the collected data have been connected to Parsable. Essentially, this is where Parsable becomes part of the permanent fabric of how the company operates. This phase may have several steps as system integrations are prioritized. In principle, we find that most customers limit connected systems to ERP, possibly MES, and in some cases HR for competency tracking. As requirements here vary, Parsable is ready to work with customers to tackle their unique needs.
For customers that have had experience rolling out enterprise-class systems, rolling out a “Connected Worker” solution, like Parsable, is a breath of fresh air. What is measured in weeks on a Parsable rollout is typically measured in months or even years with traditional enterprise