Earlier this year, we shared that Kanoa was developing an Ignition-native maintenance-management solution with input from manufacturers and systems integrators.
Today, that solution is ready.
Kanoa Maintenance is now generally available as part of Kanoa MES 1.15.
Kanoa Maintenance gives manufacturers a structured way to plan, generate, assign, execute, and analyze maintenance work inside the same Kanoa MES and Ignition environment used for production operations. It connects maintenance activity to plant assets and operating context—without requiring teams to begin with another disconnected application or a blank custom-development project.
Maintenance Work Does Not Happen in Isolation
A maintenance work order may begin with a failed component, a runtime threshold, a recurring inspection, or an observation from the plant floor. But the work itself is always connected to something larger:
- The asset being maintained
- The production area affected
- The operating conditions that triggered the work
- The technician responsible for completing it
- The procedure that should be followed
- The response, repair, and reliability trends surrounding that equipment
Traditional separation between maintenance and production systems makes that context harder to preserve. Teams may manage work in one application, equipment data in another, procedures in shared folders, and performance analysis in spreadsheets or reporting tools.
Kanoa Maintenance takes a different approach. It builds maintenance workflows on the shared asset hierarchy and operational foundation established by Kanoa Ops, allowing maintenance information to remain connected to the plant where the work occurs.
Plan Work Once, Then Generate It When Needed
Kanoa Maintenance uses reusable work-order templates to define the work that should happen and the rules that determine when an executable work order should be created.
A template can define:
- The responsible asset
- Maintenance and work classifications
- Priority
- Instructions and procedures
- Scheduling or condition rules
From that foundation, teams can support three common maintenance patterns:
One-time work
Create work for repairs, installations, project tasks, and other ad hoc maintenance needs.
Recurring work
Generate preventive maintenance, routine inspections, safety checks, and other tasks on a defined schedule.
Condition-based work
Generate maintenance after a configured runtime, counter, condition, or threshold is reached—so work does not have to depend on calendar dates alone.
This separation between planning and execution helps teams standardize repeatable work while preserving flexibility for real-world maintenance requests.
Give Technicians Clear, Structured Work
Once generated, each work order moves through an observable lifecycle—from creation and assignment through execution, completion, hold, or cancellation.
Maintenance teams can use configurable priorities, maintenance types, work types, statuses, and status categories to reflect how work is organized in their plant. Assignments, status transitions, timestamps, labor hours, comments, images, and execution history can be captured as the work progresses.
Kanoa Maintenance also supports digital procedures that break work into major steps and detailed checks. Procedures can include:
- Instructions and descriptions
- Entry options for recording results
- Required checks
- Estimated time
- Reference images
Required checks can prevent a work order from being completed before the necessary procedure steps have been performed. This helps turn maintenance knowledge into a repeatable execution process instead of leaving technicians to rely entirely on memory, paper, or tribal knowledge.
Ignition Perspective interfaces support technician workflows on compatible phones, tablets, and desktops, helping teams capture work information closer to where maintenance happens.
Turn Maintenance Activity into Performance Insight
Closing work orders is not the end of the maintenance process. Teams also need to understand whether work is being acknowledged, completed, and managed effectively over time.
Kanoa Maintenance includes analysis for:
- Mean Time to Acknowledge (MTTA): How quickly work receives its first response
- Mean Time to Repair (MTTR): How long work takes to complete after it begins
- Mean Time Between Failures (MTBF): How frequently failure events occur for an asset
- Schedule compliance: Whether completed work was finished on or before its scheduled due date
- Backlog aging: How long open work has remained active
- Work-order flow: Whether created, completed, and open work indicate a growing or shrinking backlog
- Workflow churn: How often work moves backward or repeatedly transitions between statuses
Because maintenance is performed against the Kanoa MES asset model, analysis can retain equipment context and support views across assets, lines, areas, and plants.
A Maintenance Foundation for Ignition
Kanoa Maintenance is delivered as a licensed solution within Kanoa MES—not as a separate software stack.
For manufacturers, this creates a clearer connection between maintenance work and the operational environment surrounding it. For systems integrators and Ignition developers, it provides a productized maintenance foundation that can be configured and extended using familiar Ignition tools.
Plant-specific interfaces, workflows, reports, notifications, and integrations can be implemented through Ignition where requirements call for them. Kanoa Maintenance can also participate in integrations with ERP, inventory, purchasing, and other adjacent systems when those connections are implemented for the customer environment.
Connect Maintenance Work with Spare Parts
Kanoa Maintenance and Kanoa Inventory are separate add-on solutions, but they can work together when both are licensed.
Parts can be issued from Kanoa-managed inventory to a maintenance work-order event, preserving a transaction history that connects the part, inventory location, asset, and maintenance activity.
Manufacturers that use another inventory or ERP system can instead implement the appropriate integration through Ignition for their environment.
Kanoa Maintenance Is Available Now
Kanoa Maintenance is generally available beginning with Kanoa MES 1.15. It is an add-on solution built on the Kanoa Ops foundation.
If your team manages maintenance through paper, spreadsheets, a disconnected system, or a custom Ignition application—and wants to connect that work more directly with production assets and plant context—schedule a conversation with the Kanoa team.
We are excited to see what manufacturers and Ignition integrators build with Kanoa Maintenance.
.png)
No Comments Yet
Let us know what you think