Spartakus APM: A pilot project/proof for the software?

Certainly, when it comes to exploring the possibilities of implementing the Spartakus Asset Performance software (APM), the option of conducting a pilot project/proof of concept is available.

Our typical approach for such a type of project involves selecting a specific area in which we would like to test the platform for carrying out the wanted type of technologies (PM, PdM or multiples technologies).

We usually select an area where preventive maintenance (PM) and predictive maintenance (PdM) inspections are regularly conducted. Selecting an area where we will execute inspections in Spartakus on a regular basis will allow two things: 

  1. Quickly allows the users of the platform to become familiar with the platform, provides us with insights into their satisfaction with the platform and assesses whether the platform meets the customer’s expectations. 
  2. Quickly document the benefits and the return on investment (ROI) of using the platform for the area included in the pilot project. 

Example of deployment plan for Spartakus APM

To carry out this project, three things must be estimated to be up and running: 

  1. Estimate the necessary work for creating and implementing the pilot project tasks within Spartakus.  
  2. Estimate the necessary work required to train all key players on the customer’s end to get them up and running with the pilot project. 
  3. Estimate the necessary work required to assist the customer all along the pilot project period with questions and adjustments as the project progresses. 

Consequently, from a financial perspective, the charge for the customer will only be associated with the required manpower for software implementation, training, and continuous support from the Spartakus team. No charge regarding licensing fees will be applied for the duration of the pilot project. Typically, a pilot project can last up to three months. 

Example of full implementation Gantt chart for Spartakus APM

Note that prior to launching the project, we will define success criteria, timelines, roles and responsibilities for both the customer’s team and Spartakus’ team. Once the period of the pilot project is completed, we will review together whether the success criteria have been met and decide whether to proceed with a full deployment or not. This approach offers a low-risk strategy for both Spartakus and the customer’s team. 

Share this article