Kit Digital: how to make the most of it

What the program covers and what it doesn’t is explained in implementing a CMMS with Kit Digital. This article is about something else: how to plan the project so the grant actually leads somewhere.

Because the risk of a subsidized rollout isn’t different from any other: it’s bigger. When the entry cost drops, the temptation to take on more goes up, and taking on more is what leaves projects half-finished.

The trap of the grant

A subsidized CMMS that nobody uses costs exactly the same as a paid one nobody uses: the wasted time.

The work of getting a system up and running — registering assets, defining what gets checked on each family and how often, getting the team used to recording in the field — isn’t covered by any grant. You put that in, and it’s the biggest line item.

So the right question when planning it isn’t how much the voucher covers, but how many hours of your team’s time you can actually spare in the first few weeks.

A four-week plan

If you need to make the most of the grant with a tightly scoped rollout, this is the breakdown that works.

Week 1: critical assets. Not the full inventory. The equipment that stops production or service if it fails, and the equipment with a regulatory obligation: usually fewer than fifty items. With their model, serial number, installation date and warranty end date, grouped by system, family and model.

Week 2: schedules and frequencies. By family, not by individual piece of equipment. Checklists get resolved in a cascade, so you define one once per type of equipment. Few fields, and the ones that measure something should carry a minimum and maximum value.

Week 3: the team in the field. A small group of technicians actually using the app: stopwatch inside the order, checklist, photos and signature. This is the week that decides the project.

Week 4: entry point for unplanned work. Where incidents come in and what statuses exist, each with its maximum time.

By the end of the month there should be preventive orders generating themselves, technicians closing them in the field, and the first report with real data.

What’s better left for later

And this is where the grant invites mistakes, because “well, it’s already paid for” tempts you to switch everything on.

The warehouse and purchasing, which start making sense once orders are already being closed smoothly.

The client portal, once there’s content worth showing. An empty portal generates more calls than it saves.

ERP integration, once everything else has been running on its own for months.

Migrating old historical data, which is almost never worth it: what actually gets consulted is recent data.

Turning on modules that don’t get used isn’t neutral: it takes away clarity and makes the system feel more complicated than it is.

The two decisions that come first

They don’t depend on the grant or the vendor, and they determine the outcome more than anything else.

How far you want to go. Just record technical work and pull reports, or have the system reach all the way into purchasing and administration? The first is rolled out in weeks; the second requires agreements between departments that take longer than the configuration itself.

Who owns the project. Someone in-house who knows the operation and can make decisions without calling a meeting for every question.

What to look at when choosing, even if it’s subsidized

There’s an understandable temptation when a grant exists: choosing the solution that best fits the subsidized category instead of the one that best fits your work. It ends up costing more, because the voucher runs out and the tool stays.

The criteria that decide whether a system works are the same with a grant as without one, and none of them appear on a product spec sheet:

Whether the technician will actually use it. Bring them to the demo. You can tell in two minutes if the app is going to waste their time, and it’s what best predicts the outcome.

Whether it truly works without coverage. Not caching screens: being able to create without a network, and having an action that fails to sync stay flagged instead of disappearing. Maintenance happens in basements and machine rooms.

Whether it’s configured by equipment family. With two hundred identical pieces of equipment, the difference between configuring by family and configuring one at a time is weeks.

Whether it talks to what you already have, and with exactly what scope. Integrations has the detail on each connector, which isn’t the same for all of them.

How you get your data out if you ever decide to switch.

There’s a full guide on how to choose the best CMMS. It’s worth applying before looking at what’s subsidized, not after.

The cost that’s still there after the grant

Worth checking when choosing, because the grant covers the launch, not the subscription in the years that follow.

If the software is priced per user, the cost grows with the team, and as soon as you need to give access to clients or subcontractors the bill spikes. What tends to happen then is accounts get shared, and the moment two people sign in with the same user, the history stops being worth anything as evidence.

At GMAO CLOUD, licenses are unlimited across all three plans. Run the numbers with the headcount you’ll have in three years, not today’s.

And don’t mix up the programs

Kit Consulting funds advisory services, not software licenses. It’s for having an expert help define how to digitalize, not for buying the tool.

They can complement each other, but they’re not interchangeable, and that confusion is why a lot of people end up in the wrong program. There are pages for Kit Digital and Kit Consulting.

Before filing anything

Amounts and categories change with each call for applications, so the good source is always the official one for the program. And in parallel, do the work that doesn’t depend on any grant: write the list of your critical assets and what gets done to each one, and how often.

Once you have that, request a demo on those specific pieces of equipment. It’s the best way to know if it fits before starting the paperwork.