Data Needed Before CAFMTEK Go-Live

Last updated

In short

Before CAFMTEK goes live, eight items must be ready: asset data, a location register, SLA timings, PPM job plans, PPM schedules, problem codes, the audit module setup and user accounts. HITEK AI shares onboarding documents listing these prerequisites once the contract is finalised.

Applies to: New CAFMTEK deployments

The eight prerequisites

# Item What it is Where CAFMTEK uses it
1 Asset data The list of maintainable assets and their details Asset Management
2 Location register The structure of sites, buildings, floors and spaces Assets, work orders, Space Management
3 SLA timings Response and completion times agreed for each type of work SLA & KPI Management
4 PPM job plans The tasks and checklists for each type of planned maintenance Preventive Maintenance
5 PPM schedules How often each job plan runs, and on which assets Preventive Maintenance
6 Problem codes The categories used to classify faults and requests Work orders, helpdesk, reporting
7 Audit module setup The audit checklists and inspection requirements Snagging & Auditing
8 User accounts The people who will use CAFMTEK, and their roles System Administration

[CONFIRM] The required fields for each item, and whether HITEK AI provides templates (for example, spreadsheets).

If your asset data isn’t ready

Asset data is usually the item that takes longest to prepare. If you don’t have a verified asset register, CONDTEK, HITEK AI’s asset condition intelligence module, captures asset data through mobile field surveys, including AI-assisted condition grading and criticality scoring. [CONFIRM that CONDTEK surveys can be used to prepare CAFMTEK asset data]

Data for the AI modules

Fault Detection and Diagnostics, Predictive Maintenance and Anomaly Detection need more than the eight core items:

  • Live data: data points from a BMS, smart meters or sensors for monitored assets.
  • History: maintenance and fault records for each asset.

More data points, and a longer history, give more accurate AI results.

Common data problems to fix early

These are common issues in FM data preparation generally, not specific to CAFMTEK:

  • Duplicate assets: the same asset recorded under different names or IDs.
  • Inconsistent locations: the same room or floor named differently across sources.
  • Unlinked assets: assets not tied to a location.
  • Orphan schedules: PPM schedules not attached to specific assets.
  • Vague problem codes: codes too broad to show useful fault patterns in reports.

Frequently asked questions

When do we receive the prerequisite list?
HITEK AI shares onboarding documents with the full prerequisite list once the contract is finalised.

Can data be migrated from another CAFM system or spreadsheets?
[CONFIRM supported sources and migration approach]

Do we need BMS data to go live?
Not for the core modules. Live BMS, smart meter or sensor data is only needed for the AI modules, such as Fault Detection and Diagnostics. [CONFIRM]

Related pages