Frequently asked questions about MatxFlow.

A CMMS (computerized maintenance management system) for industrial maintenance teams. It is used to record requests, schedule work orders, track how they are carried out in the field and keep the history of every piece of equipment.

Maintenance managers who receive requests and schedule the work, technicians who carry out work orders from the mobile app, and site managers who follow equipment downtime and team workload.

No. MatxFlow covers the day-to-day running of maintenance: requests, work orders, equipment, time. It can exchange data with an ERP when the ERP provides suitable interfaces.

No. The ticket is the common thread, but MatxFlow also handles technician schedules, work order forms, working and break time, consumables used, equipment downtime and dashboards.

The ticket is qualified, scheduled and assigned to a technician, then synchronized with their mobile app. The technician carries out and completes the work; the ticket is then validated and closed. Every status change is recorded with its date.

MatxFlow checks the work orders already scheduled for the technician. If there is an overlap, it moves the start to after the work order occupying the slot, with a five-minute buffer, until it finds a slot long enough. The estimated duration of the work order is not reduced.

They check the day's schedule, start, pause and complete work orders, fill in the assigned form and record the consumables used. A work order completed earlier than planned does not reappear on the following days.

Yes. MatxFlow distinguishes working time, recorded break time and the elapsed time between the start and the end of the work order. Each technician's dashboard shows these times, as totals and averages, over a day, a week, a month or a year.

If the ticket is cancelled before it is started, no work is counted; if it was assigned to a technician, it appears as "not carried out" in their dashboard. If it is cancelled after it was started, the work still counts as carried out.

Yes. Every work order is linked to a piece of equipment. Its record holds its identification, its condition, its work order history, and its downtime and returns to service.

Yes. You build one form per type of work order, organized into sections: general information, checks, measurements, observations, validation.

Text, number, choice from a list, date and time, image, attached file and signature.

Yes. An answer can reveal additional fields: for example, the description and photo of an anomaly are only requested if an anomaly has been reported.

Yes. Screens that provide for it offer an Excel export, and some offer import of a prepared file. An exported file can be completed and re-imported, as long as its structure is not changed.

It is possible when the ERP provides suitable interfaces, such as an API. There is no standard connection that works for every ERP: the data to exchange and the connection method are reviewed with your IT team.

Yes, depending on the architecture chosen. The most common cases are equipment synchronization, forwarding of maintenance requests and return of work order statuses.

The maintenance dashboard shows, for a given day, ticket progress, equipment that is down and technician workload. For analysis over a long period or combined with costs, the data can be exported to Excel.

No. Configuration starts from your equipment, your workshops and the information your technicians already record; forms are built from what you use today.

Yes. A deployment can start with one workshop, one type of work order or a few pieces of equipment before being extended.

It depends on the scope, how much the forms need to be customized and which integrations are needed. A set-up without integrations is quicker than an environment connected to an ERP.

Mainly by the number of technicians active on the mobile app, then by the plan chosen and any integrations. The Pricing page describes the three plans.