12 Questions Industry Leaders Asked at the Maintenance Heroes Summit

At the Maintenance Heroes Summit on October 7, our speakers shared hard-won lessons on maintenance success. But some of the liveliest conversations happened in the chat. 

Maintenance leaders from water utilities, zoos, YMCAs, casinos, manufacturers, universities, municipalities, and more traded hundreds of messages over four hours. They asked hard questions, swapped tactics, and answered each other in real time.

The chat also showed where most teams are today. In a live poll, more than half of respondents described their maintenance as mostly reactive, and only a handful called themselves predictive. When asked how many hours of hands-on wrench time their techs get in a typical shift, the most common answer was 3 to 5 hours, and about a quarter said 3 or fewer. That echoes Limble’s new State of Maintenance Report, where more than 60% of leaders and technicians estimated 3 hours or less. 

We pulled the 12 questions that came up most, grouped them by theme, and paired each with answers from Limble experts and fellow attendees.

Getting your team on board

1. "My veteran techs have been here 30 years and don't want to change. What do I do?"

This was the most-discussed topic of the day. The consensus: you can't mandate your way to adoption, but you can make the system worth using.

• Start with the why. One attendee advised writing a department vision and mission, then asking techs for input so they own the change.
• Show them what's in it for them. The feature that wins skeptics fastest is seeing work order history and parts availability in the field, so they stop hunting and chasing.
• Pair veterans with new hires. One manufacturer suggested paying senior techs a bonus to train new hires on the system. Several attendees noticed that new hires adopt without friction, which makes resisting less socially acceptable.
• Aim for progress, not perfection. As one attendee put it, 80% adoption beats none.

2. "I can't even get my techs to put in daily work order notes. How do I fix that?"

Attendees shared what actually worked for them:

• Tie it to performance. A chemical manufacturer added note quality to annual pay progression. An airport now evaluates field techs yearly on the quality of their CMMS logs. A startup facility reports close rates monthly and ties them to appraisals.
• Let peer accountability work. When one tech finds an unlogged repair on an asset they just fixed again, they hold the other tech accountable.
• Create the "aha" moment. A water operations admin waited for each tech to need historical data, then pulled it up for them. Showing a tech that their field readings become the dots on an asset's trend line made it click.
• Reward, don't shame. Recognize the techs using the system well rather than calling out the holdouts.

Tracking labor accurately

3. "How do I track two or more techs working the same job?"

Assign every tech who works the job to the same task. Each one then logs their own time on it.

A tech can log time without closing the task, using the log time option from the task's action button. That works when a helper jumps in partway through, or the job spans several visits. We also recommend letting users edit their own time rather than relying only on the automatic task timer, which keeps running if a task is left open.

4. "Every new user gets a $20 average wage. What rate should I use, and what happens when rates change?"

The $20 is just a default. You can change the average wage on each user, and it's best to do it as soon as you add them.

Two tips from the chat:

• Use the burdened rate, not the pay rate. Benefits, taxes, and overhead push the true cost of a tech's hour well above their wage. One consultant estimated it is likely above $50 an hour.
• Rate changes apply going forward. Updating a wage on January 1 won't inflate last year's labor costs, so set rates promptly to keep reports accurate.

Hours, mileage and meter-based PMs

5. "All our PMs are based on hours or mileage. Can readings trigger PMs automatically?"

Yes. The setup takes three steps:

1. Add a number field to the asset, such as "Hours Run."
2. Create a PM with a number instruction linked to that field, so each reading updates the asset.
3. Create a second PM scheduled "every X number of units" on that field, such as every 2,000 hours.

Past readings stay on the asset card and can be exported to a spreadsheet. If a reading jumps past several intervals at once, Limble generates every missed PM. 

You don't have to rely on manual entry either. One equipment-heavy attendee connects manufacturer telematics such as Geotab directly to Limble. For brands not yet connected, they run an export and update in bulk. Limble's open API makes other monitoring systems possible to connect.

6. "Operators entering hours and mileage is a constant battle. Is there a better way?"

Besides telematics, attendees suggested two fixes:

• Make readings part of a routine inspection. A lumber company uses weekly inspections to capture hours, which then trigger the hour-based PMs.
• Require location check-ins. A water operations team is rolling out a GPS check-in instruction on work orders for hydrant flushing, which confirms the tech is physically at each asset. QR codes on equipment serve a similar accountability purpose.

Sensors and integrations

7. "Can Limble take in vibration, temperature, and lubrication data, without sending me to another vendor's website?"

Yes. Limble doesn't sell sensors, so you aren't locked into one hardware brand. It partners directly with Monnit for condition-monitoring sensors and integrates natively with Augury, AssetWatch, VibeCloud, and AVEVA.

You set the threshold that matters for each asset. When a reading crosses it, Limble notifies the team and can open a work order on that asset automatically. Every reading is logged against the equipment, which builds a condition history over time.

8. "Can Limble connect to the other tools we use, like calendars, purchasing or our PLCs?"

Often, yes. Our experts confirmed in the chat that Limble integrates with Outlook and Google Calendar, and has a prebuilt purchasing integration with Coupa. Attendees also use Microsoft Power Automate to send email notifications for PMs and work requests.

If your tool isn't on the Integrations page, ask your Customer Success Manager whether it can be built.

Planning the workload

9. "I'm a supervisor with no planner and 300+ PMs a month. Is there a faster way to assign them?"

Yes, two features help here.

Bulk reassign PM templates: On the Manage PM Templates page, Bulk Actions lets you pick many PMs and reassign them to one user or team at once. You can also change their asset or tags in bulk. PM relations let you update the assignee, schedule, or instructions across linked PMs with one change. 

Resource planning: The Workload View shows each tech's capacity by day. You drag unassigned, future, or missed tasks onto a tech's schedule, and overbooking shows in red. Smart time estimates fill in task durations from past completions, and AI scheduling suggestions group similar or nearby work together. 

AI and the Limble MCP

10. "What is MCP, and which AI tools can I use it with?"

MCP stands for Model Context Protocol. It's how you connect your Limble data to the AI assistant you already use, so you can ask questions of your maintenance data in plain language.

Limble's official MCP server works with Claude Desktop, Claude Code, Cursor, GitHub Copilot, and Microsoft Copilot Studio. To set it up, you need Limble API credentials and a few lines of configuration in your AI tool. Because it runs through your own AI tool, you'll need access to one of those tools.

Attendees already using it shared real examples:

• Daily work order and purchase order "hygiene" notes, tailored to each user and team.
• A weekly task that reformats techs' parts entries into clean records.
• A weather station that creates inspection work orders when rainfall crosses a threshold.
• An AI "facilities chief of staff" that handles daily monitoring, first drafts and lookups.

11. "Won't AI make our data quality worse?"

It can, if it's used in the wrong place. One water operations admin described techs running their field notes through AI before submitting them, which garbled the details she needed. Her ask: give her the raw information.

The takeaway from the chat was to aim AI at the right jobs. Keep a record of what techs actually saw and did in their own words. Use AI on top of that record to monitor, summarize, flag gaps, and clean formatting. The foundational practices that make AI useful, like accurate time, consistent asset data, and complete notes, make the data more trustworthy for people too.

Making the case to leadership

12. "Preventive work looks non-billable to leadership. How do I prove it's worth it?"

Let the data make the argument. Attendees who won this fight shared how:

• Show the cost of "no." Capture what it costs when leadership declines maintenance investment, so the data leads them to conclude they can't afford to skip it.
• Find your most expensive equipment. A paving company used nine months of cost data in Limble to show which machines cost the most, which shaped its equipment purchases.
• Build a repair-vs-replace case. Asset history and repeat-failure data make a case your manager can't easily argue with. One consultant forecasts replacement in future-value dollars to account for the time value of money.
• Give it time. One admin spent about a year and a half building assets and habits before her dashboards changed leadership's view. She also coached her bosses on realistic timelines: good isn't fast.

Keep the conversation going

The questions don't stop when the summit ends. Here's where to keep learning:

• Watch the sessions on demand at the Maintenance Heroes Summit page.
• Join the Limble Community to swap dashboards, tactics, and answers with other maintenance pros.
• Bring your questions to office hours or a live training session. Sign up through the Help Center.
• Meet us in person at the Maintenance Heroes Roadshow: Columbus (Oct 27), Chicago (Oct 29), Anaheim (Nov 5), and Fort Worth (Nov 12).

Thank you to every hero who asked a question, shared a tactic, or answered a peer in the chat. You made this year's Summit.