CAFMTEK Implementation Phases

Last updated

In short

A CAFMTEK implementation runs in four phases: kick-off, installation, testing and commissioning, and go-live. Before go-live, the client and HITEK AI prepare asset data, the location register, SLA timings, PPM job plans and schedules, problem codes, the audit setup and user accounts. HITEK AI then trains the users.

Applies to: New CAFMTEK deployments

The four phases

Phase What happens [CONFIRM activities]
1. Kick-off The project starts. HITEK AI shares onboarding documents listing the data and setup prerequisites.
2. Installation CAFMTEK is activated and configured, and the client’s data is loaded.
3. Testing and commissioning The configured system is tested with the client’s data and workflows before live use.
4. Go-live Users start working in CAFMTEK on web and mobile.

Who does what

Responsibility Client HITEK AI
Asset data, location register, SLA timings Provides Loads into CAFMTEK [CONFIRM]
PPM job plans, PPM schedules, problem codes Provides Uploads [CONFIRM]
Audit module setup Agrees audit requirements Configures [CONFIRM]
User accounts Nominates users and roles Creates accounts [CONFIRM]
Site access, gate passes and permits Provides
Activation, training, project management Delivers

Professional services included

A CAFMTEK implementation includes three HITEK AI professional services:

  • Activation: setting up and configuring the CAFMTEK environment.
  • Training: training administrators, supervisors and technicians.
  • Project management: running the implementation from kick-off to go-live.

What affects the timeline

Every implementation timeline is agreed per project. The main factors are:

  • Portfolio size: the number of assets and locations.
  • Data readiness: how complete and accurate the asset data is.
  • Integrations: for example ERP, BMS or IoT connections.
  • Users: the number of users and roles to train.
  • Configuration: any customisation to match client processes.

Integrations and customisation

  • Integrations: connections to third-party systems, such as ERP for procure-to-pay, are scoped for each project.
  • Customisation: CAFMTEK can be configured to match client processes. [CONFIRM scope of standard configuration versus customisation]

Frequently asked questions

How long does a CAFMTEK implementation take?
It depends on portfolio size, data readiness, integrations and the number of users. HITEK AI confirms the timeline once the scope is agreed.

Is training included?
Yes. Training is one of the professional services in a CAFMTEK implementation.

What does the client need to provide?
Asset data, the location register, SLA timings, PPM job plans and schedules, problem codes, audit requirements, user details, and site access where needed. See Data Needed Before CAFMTEK Go-Live.

Related pages