Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

CMMS: Warranty and Recovery

OEM warranty coverage tracking by date and mileage dimensions via Connect RPC CRUD (list, create, get, update, delete).

Problem

OEM warranty coverage tracking by date and mileage dimensions via Connect RPC CRUD (list, create, get, update, delete).

Capability

OEM warranty coverage tracking by date and mileage dimensions via Connect RPC CRUD (list, create, get, update, delete).

How it works

  1. 1 Warranty records, coverage checks, and claim lifecycles are fully CRUD-backed with recovery analytics.
  2. 2 60/30/7 alerting and claim-status tracking are integrated into maintenance recovery workflows.

Operational outcomes

  • Warranty records, coverage checks, and claim lifecycles are fully CRUD-backed with recovery analytics.
  • 60/30/7 alerting and claim-status tracking are integrated into maintenance recovery workflows.

Integration boundaries

  • Journey Contracts (Normative)
  • Crew Integration
  • TMS Integration

Proof model

Feature-level proof

  • Warranty and Recovery scope is defined in product module catalog.

    verified

    docs/products/cmms/product.md · Module Catalog > Warranty and Recovery

  • CMMS asset dispatchability state is maintained in fleet modules and shared to downstream execution planners.

    verified

    docs/products/cmms/product.md · Module Catalog > Asset Registry and Dispatchability

    Code: backend/services/cmms/internal/modules/assets

    Contract: proto/cmms/fleet/v1

  • CMMS dispatchability workflows are implemented in asset and fleet modules.

    verified

    docs/products/cmms/product.md · Module Catalog > Asset Registry and Dispatchability

    Code: backend/services/cmms/internal/modules/assets

    Contract: proto/cmms/fleet/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (2).