Prepared by Maxsoft Africa for maintenance, operations and management-system decision-makers. Examples are illustrative.

Define what “not working” means

Software may be accessible while maintenance is still managed in notebooks and messages. Interview a planner, technician, stores user and manager separately, then follow one work order together. Record observable problems: no asset identifier, jobs never assigned, parts omitted, confusing permissions or reports that exclude open work. “The system is too complicated” is a useful starting complaint, not yet a diagnosis. Avoid assuming that a named ERP or CMMS is inherently unsuitable.

Protect the current system before making changes

Confirm the contract owner, licence entitlements, installed version, administrator access and publisher-support arrangements. Export the relevant configuration and records, and verify a recoverable backup with the responsible administrator. Use a test environment where available. A recovery project should not begin with unreviewed changes to live data or the deletion of historical work orders.

Separate the causes

Classify each issue so the remedy matches it. A missing asset may be a data problem; an unassignable job may be permissions or workflow configuration; an unused preventive plan may reflect workload or unclear ownership. An unsupported interface is a different problem from an import that was never reconciled. Keep a decision log showing evidence, owner, proposed correction and acceptance test.

  • Data: identifiers, duplicates, mandatory fields and missing history
  • Configuration: statuses, permissions, teams and calendars
  • Process: approvals, priorities, parts issue and closure rules
  • Integration: stock, purchasing, finance and interface failures
  • Adoption: task-specific training, devices and supervision
  • Ownership: administrator, support route and change control

Run a recovery pilot, not a second big launch

Choose one maintenance team and a manageable asset family. Clean only the records required for the pilot, repair the work-order path and rehearse it with the actual users. An illustrative example is a preventive generator inspection: schedule it, assign it, record readings and parts, approve completion and verify the history. This is a test scenario, not a reported client result. Track unresolved exceptions during a defined observation period before extending the changes.

Decide whether to repair, extend or replace

Compare the pilot evidence with the requirement. Repair may be sufficient when data, permissions or training caused the gap. An extension may be justified for a missing but supportable workflow. Replacement deserves consideration when essential requirements cannot be met within the permitted version, interfaces, licence or ownership constraints. Document migration cost, operational disruption and long-term support, not just licence price. The maintenance manager should approve the operational decision alongside IT.

Make recovery sustainable

Handover must identify who approves new assets, changes preventive tasks, monitors failed interfaces and answers user questions. Agree support hours, escalation and an initial review. Use measured indicators with clear definitions, such as complete closure records or reconciled open jobs. Keep the baseline and do not describe anticipated improvements as achieved savings. Maxsoft Africa can assess the current setup and propose a staged recovery scope with acceptance criteria.

  • Written diagnosis supported by examples
  • Approved pilot scope and protected source data
  • Tested workflow and role-based training
  • Signed acceptance checks and administrator guide
  • Support ownership, review date and next-phase decision
All insights