Data ownership and storage in Spartakus APM ?

In 6 years, Spartakus APM has emerged as a game-changer in the world of asset health, PM optimization and lubrication rounds.

This article aims to provide valuable insights for future users about the ownership of data in Spartakus. We’ll explore the implications and risks associated with the hypothetical scenario of Spartakus ceasing operations or a service contract ending, shedding light on essential considerations for users and stakeholders. 

What is Spartakus APM again?

Spartakus APM is a web-based platform widely used for asset management and maintenance. Its users rely on its capabilities for efficient asset health monitoring and comprehensive maintenance programs. 

Spartakus Technologies hosts the solution, configures it to the end users needs and can do the integration with 3rd party apps (ex: CMMS). Spartakus Technologies also provides support in the implementation, data transfer, data integrity, training of users and continuous improvement. 

What type of Data is stored or collected?

Data is almost limited to condition-based maintenance rounds details: equipment hierarchy, components to check, task description, potential failures, inspection results (severity of problems, recommendations on how to repair). There is no personal information collected or stored in our databases. 

The “what if” scenario

In the event of Spartakus APM closing its doors or a contract ending, there are critical questions that users must grapple with, including the continuity of service, data security, and the fate of their asset management operations. 

Now, let’s delve deeper into these concerns. 

Data ownership and retrieval

The data stored on Spartakus’ servers is an asset for its users, encompassing a comprehensive hierarchy of asset information, maintenance programs, routes, and extensive historical data. The details go far beyond the surface, with intricate components such as oil quantity, brand, and grade, along with task frequencies and failure modes. 

This data is stored in the MySQL format, offering users the ability to export it conveniently in Excel or CSV formats. In fact, Spartakus users can download all the information stored in the database at any given moment, except for one exception: images. 

The absence of an easy setup for image downloads is simply due to a lack of prior requests, not a technical limitation. Spartakus could easily add this functionality if necessary. Therefore, in the event of Spartakus closing its doors or at the end of a contract, users can rest assured that they won’t lose their data. They can swiftly and efficiently download their valuable information as Excel or CSV files, with the possibility of image download functionality being added if required. 

Continuity of Service: Can I Keep Using Spartakus APM? 

One of the immediate worries if Spartakus APM was to close or contract would end is whether users can continue using the web platform and mobile application. Spartakus operates as a web-based platform, distinct from traditional software installations. Consequently, its services are intricately tied to its servers. In the unfortunate scenario of closure, Spartakus’ servers would inevitably go offline. 

While some clients might contemplate hosting the platform themselves, the feasibility and associated workload may pose significant challenges. Moreover, without ongoing support from Spartakus, maintaining the platform independently could become cost prohibitive. Thus, the stark reality is that users would no longer have access to the platform or its mobile application, raising questions about how to replace its vital functionalities. 

Spartakus APM, a prominent web-based platform for asset health and maintenance, has been in operation for six years. This article delves into the aspects of data ownership and continuity of service in the event of Spartakus ceasing operations or ending service contracts, offering valuable insights to users and stakeholders. 

 Spartakus APM, a product of Spartakus Technologies, plays a pivotal role in asset management and maintenance, catering to user needs by providing support, integration with third-party applications, and extensive training. 

 Data stored in Spartakus is primarily related to condition-based maintenance rounds, with no personal information collected. Users can conveniently export this data in MySQL format to Excel or CSV files. The only exception is image data, which can be added upon request. 

 The article assures users that in case of closure, their data can be downloaded efficiently. However, the continuity of service raises concerns, as Spartakus operates as a web-based platform intricately tied to its servers. If the platform were to cease operations, users might face challenges in maintaining it independently, emphasizing the importance of considering alternative solutions to replace its essential functionalities. 

Share this article