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

TelePulse: Scenario Building and Management

Visual scenario builder with 5-step wizard: basic info (name, description, duration, time acceleration), drivers (starting positions, HOS remaining), loads (pickup/delivery stops with appointments), events...

Problem

Simulation runs lose operational value when scenario composition is ad hoc and non-repeatable.

Capability

Visual scenario builder with 5-step wizard: basic info (name, description, duration, time acceleration), drivers (starting positions, HOS remaining), loads (pickup/delivery stops with appointments), events...

How it works

  1. 1 Define scenario scope, duration, and acceleration settings.
  2. 2 Configure route, driver, load, and event composition.
  3. 3 Validate and persist scenario configuration for replay.

Operational outcomes

  • Faster creation of repeatable simulation scenarios for demos and validation.
  • More consistent scenario handoff across product, ops, and QA teams.

Integration boundaries

  • Simulation Engine
  • HOS (Hours of Service) Simulation

Proof model

Feature-level proof

  • Scenario Building and Management scope is defined in product module catalog.

    verified

    docs/products/telepulse/product.md · Module Catalog > Scenario Building & Management

  • 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.