Frequently asked questions

Implementation typically takes 1-3 days, depending on the number of assets and complexity of the plant. We provide a simple data import template to get started. Since our system works offline and doesn't require operator login, minimal IT setup is required. However, if you need customization or integration with existing systems, it may take longer, up to 7-10 days. Our support team will guide you through the process during your 14-day free trial.

AssetAI is a cloud-based CMMS, so no server installation is required. However, operators will need to download and install a mobile app for QR fault reporting. The app works offline, allowing reporting from anywhere in the plant. Administrators can access the web application through a browser, with no installation needed.

AssetAI supports data import from Excel, but it's a manual process and requires formatting your data according to our template. Our team will guide you through this process. However, historical maintenance records older than 2 years will be imported as read-only, and only the last 2 years of work order history will be available for analysis and reporting. This is to ensure data relevance and system performance.

Technicians don't need extensive training to use AssetAI. The QR-based fault reporting feature is simple and intuitive, allowing them to report issues quickly without needing to log in. However, some basic orientation on scanning QR codes and understanding the reporting process may be necessary. AssetAI's simplicity and offline functionality make it easy to adapt to, minimizing the need for lengthy training sessions, which is particularly beneficial in a fast-paced Indian manufacturing environment.

Free for 14 days — 25 assets, 5 users, all core modules, no card. It exists so you can prove value on your own machines before paying.

Per-user pricing makes companies restrict logins, which kills adoption — and adoption is the whole point. One price per plant, add everyone.

Monthly or annual (2 months free), GST invoice provided. Enterprise plans can include an onboarding service where we import your data, print QRs and train your team on site.

7-day grace, then the account suspends. Your data is retained for 90 days and remains exportable throughout — it is never held hostage.

You do, unambiguously. Settings → Download all data exports every record as CSVs, one click, anytime.

Yes — tenant isolation is enforced at the database layer and verified by automated tests on every release.

The audit trail is immutable (entries can never be edited or deleted) and exports to CSV: who approved what, when, with remarks. PM on-time % answers the compliance question auditors ask first.

A read-only REST API for ERP/BI integration, plus an authenticated endpoint for IoT meter pushes. Nothing can be modified through the API by design.

Yes — the machine QR pages work offline; reports queue on the phone with a visible banner and submit automatically when the network returns.

English, हिन्दी, العربية (RTL), Deutsch, Français, Español, 日本語, 中文 and more — each user picks their own from the header; the company sets the default.

Connect your own gateway (Meta Cloud API, UltraMsg, AiSensy, Twilio or Interakt) in Settings. Every event can then ring bell + email + WhatsApp, with editable templates.

Yes — completion is blocked until failure mode, cause and remedy are set. That discipline is what makes the failure Pareto real.

It is a first-class flow: coverage badges at approval, send-to-vendor service calls, quote approval gates, and bill passing to the work-order cost.

Downtime cost is calculated based on the asset's maintenance history and production data. AssetAI uses a standard formula: (asset hourly production rate * average hourly revenue) * downtime hours. However, this calculation assumes uniform production rates and revenue, which may not reflect complex production scenarios. For precise calculations, integration with ERP or production planning systems may be necessary, which is not currently supported by AssetAI.

A reasoned recommendation per machine from its repair-cost ratio, failure acceleration, downtime losses and age — printed on its one-page History Card with the reasons listed.

Completely — they are captured as people do their jobs (report, approve, start, finish), not entered afterwards. That is why the analytics can be trusted.