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

Solution Feature Maps | IronKernel Solutions

Solution-specific feature maps that expose the concrete product-feature routes used to validate operational outcomes.

Dispatch confidence feature map

Feature-depth route bundle for dispatch confidence with persona and benchmark continuity.

  • 3 mapped feature highlights
  • 3 verification playbook steps
  • 14 supporting continuity routes
Open feature map Solution brief

Feature-map proof

  • TMS load lifecycle orchestration includes planning, persistence, and downstream contract surfaces.

    verified

    docs/products/tms/product.md · Module Catalog > Load Lifecycle and Planning

    Code: backend/services/tms/internal/modules/loads

    Contract: proto/tms/loads/v1

  • TMS load lifecycle workflows are implemented in service modules and proto contracts.

    verified

    docs/products/tms/product.md · Module Catalog > Load Lifecycle and Planning

    Code: backend/services/tms/internal/modules/loads

    Contract: proto/tms/loads/v1

  • Crew readiness and eligibility signals are implemented for assignment-gating workflows.

    verified

    docs/products/crew/product.md · Module Catalog > Readiness & Eligibility

    Code: backend/services/crew/internal/readiness

    Contract: proto/crew/v1

Yard throughput feature map

Feature-depth route bundle for yard throughput with persona and benchmark continuity.

  • 3 mapped feature highlights
  • 3 verification playbook steps
  • 14 supporting continuity routes
Open feature map Solution brief

Feature-map proof

  • YMS gate operation execution is implemented with dedicated gate rule modules and geofence-ready integrations.

    verified

    docs/products/yms/product.md · Module Catalog > Gate Operations

    Code: backend/services/yms/internal/modules/gates

    Contract: proto/yms/gates/v1

  • YMS gate execution is implemented in dedicated gate modules.

    verified

    docs/products/yms/product.md · Module Catalog > Gate Operations

    Code: backend/services/yms/internal/modules/gates

    Contract: proto/yms/gates/v1

  • Gate Operations scope is defined in product module catalog.

    verified

    docs/products/yms/product.md · Module Catalog > Gate Operations

Maintenance and dispatchability feature map

Feature-depth route bundle for maintenance and dispatchability with persona and benchmark continuity.

  • 3 mapped feature highlights
  • 3 verification playbook steps
  • 14 supporting continuity routes
Open feature map Solution brief

Feature-map proof

  • 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

  • Maintenance Operations scope is defined in product module catalog.

    verified

    docs/products/cmms/product.md · Module Catalog > Maintenance Operations

Field execution continuity feature map

Feature-depth route bundle for field execution continuity with persona and benchmark continuity.

  • 3 mapped feature highlights
  • 3 verification playbook steps
  • 14 supporting continuity routes
Open feature map Solution brief

Feature-map proof

  • Pilot trip workflows and stop progression are implemented in mobile load and stop views.

    verified

    docs/products/pilot/product.md · Module Catalog > Trip and Stop Management

    Code: frontend/apps/mobile/src/pages/Loads.tsx

    Contract: proto/tms/loads/v1

  • Pilot trip and stop workflows are implemented in mobile and load components.

    verified

    docs/products/pilot/product.md · Module Catalog > Trip and Stop Management

    Code: frontend/apps/mobile/src/components/load

    Contract: proto/tms/loads/v1

  • Trip and Stop Management scope is defined in product module catalog.

    verified

    docs/products/pilot/product.md · Module Catalog > Trip and Stop Management

Commercial to execution feature map

Feature-depth route bundle for commercial to execution with persona and benchmark continuity.

  • 3 mapped feature highlights
  • 3 verification playbook steps
  • 14 supporting continuity routes
Open feature map Solution brief

Feature-map proof

  • CRM modules support intake processing, route projection, and qualification lifecycle evidence.

    verified

    docs/products/crm/product.md · Module Catalog > Intake & Qualification

    Code: backend/services/crm/internal/modules/intake

    Contract: proto/crm/intake/v1

  • CRM intake and qualification flows are implemented in dedicated modules and contracts.

    verified

    docs/products/crm/product.md · Module Catalog > Intake & Qualification

    Code: backend/services/crm/internal/modules/intake

    Contract: proto/crm/intake/v1

  • Intake and Qualification scope is defined in product module catalog.

    verified

    docs/products/crm/product.md · Module Catalog > Intake & Qualification

How to use feature maps

Run these maps during technical discovery to connect solution narrative to concrete feature behavior.

  1. 1. Start from the solution brief

    Anchor on problem and outcome framing before diving into implementation routes.

  2. 2. Walk mapped feature routes

    Open each feature route and capture observable signals relevant to the buyer workflow.

  3. 3. Close on continuity checks

    Use supporting routes to confirm persona, journey, and benchmark alignment.