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

TelePulse: Event Injection & Fault Simulation

Supports injectable events including delay events (traffic delays with reason and duration), breakdown events (vehicle breakdowns with repair time), duty status changes (force status...

Problem

Supports injectable events including delay events (traffic delays with reason and duration), breakdown events (vehicle breakdowns with repair time), duty status changes (force status...

Capability

Supports injectable events including delay events (traffic delays with reason and duration), breakdown events (vehicle breakdowns with repair time), duty status changes (force status...

How it works

  1. 1 Fault/event injection framework for delays, breakdowns, duty changes, and trailer operations.
  2. 2 Structured event model with severity tagging and replay-safe simulation outcomes.

Operational outcomes

  • Fault/event injection framework for delays, breakdowns, duty changes, and trailer operations.
  • Structured event model with severity tagging and replay-safe simulation outcomes.

Integration boundaries

  • Simulation Engine
  • HOS (Hours of Service) Simulation

Proof model

Feature-level proof

  • Event Injection & Fault Simulation scope is defined in product module catalog.

    verified

    docs/products/telepulse/product.md · Module Catalog > Event Injection & Fault Simulation

  • TelePulse simulation engine behavior is implemented as first-class simulation modules.

    partial

    docs/products/telepulse/product.md · Module Catalog > Simulation Engine

    Code: backend/services/telepulse/internal/modules/simulation

    Contract: proto/telepulse/simulator/v1

  • TelePulse simulation workflows are implemented in service runtime modules.

    verified

    docs/products/telepulse/product.md · Module Catalog > Simulation Engine

    Code: backend/services/telepulse/internal

    Contract: proto/telepulse/simulator/v1

Solution routes that reuse this feature

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

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.