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

TelePulse feature index

Browse module-level feature pages for this product.

Product context

Module-backed feature inventory with linked continuity routes and implementation evidence.

Source module catalog and implementation references are used to keep feature scope visible and auditable.

Back to TelePulse Product directory Get in touch

Feature pages

All feature pages for TelePulse (12 routes).

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

Outcomes

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

Exchange and Event Streaming

Provides webhook management (create/update/delete endpoints, subscribe to event types, HMAC-SHA256 signature verification, delivery attempt tracking with retry).

Outcomes

  • Improved confidence in simulated partner and event-delivery behavior.
  • Clearer verification path for integration testing and demo readiness.
Open feature detail

Simulation Engine

Provides multi-simulation support with time acceleration, lifecycle management, state persistence, distributed execution, and bookmark navigation.

Outcomes

  • Multi-simulation execution runtime with concurrent scenarios, lifecycle state, persistence, and distributed fanout.
  • Scenario speed control and progress tracking support large-scale demo and validation workflows.
Open feature detail

HOS (Hours of Service) Simulation

Supports multi-jurisdiction HOS regulations including US DOT (11/14/70-hour rules), Canadian NSC (13/14/70-hour with split sleeper berth), and Mexican NOM-087 (14/16/70-hour rules).

Outcomes

  • Multi-jurisdiction HOS runtime with US/Canada/Mexico rules and state transition persistence.
  • HOS compliance checkpoints, break enforcement, and rule-specific validations are enforced end-to-end.
Open feature detail

Route Simulation & Generation

Generates routes between origin/destination using OSRM for real road-following or linear interpolation for simple testing.

Outcomes

  • OSRM + linear route generation with waypoints, realistic speed/depth and route fallback behavior.
  • Route metadata including travel-time and bearing/enrichment feeds for stop simulation.
Open feature detail

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

Outcomes

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

Trip Simulation & Multi-Stop Support

Generates Trip simulations with generic Stop[] sequences enabling testing of freight (Pickup → Delivery), LTL (multi-stop freight), DSD (warehouse → customer stops → return),...

Outcomes

  • End-to-end multi-stop journey simulation across freight/LTL/DSD/field service patterns.
  • Stop-level event modeling and HOS projection across route sequences.
Open feature detail

Exchange Engine (VAN Simulator)

204/990/214/210/997 transaction processing with envelope batching and SFTP transport simulation.

Outcomes

  • 204/990/214/210/997 transaction processing with envelope batching and SFTP transport simulation.
  • Transport/ack tracking with timeouts and adaptive retry behavior.
Open feature detail

Trading Partner Simulator

Status: Implemented (Phase 1 Complete) Trading partners are active participants with behavior, state, and bidirectional communication.

Outcomes

  • Trading partner stateful transport for VAN-style lifecycle with EDI transaction and status semantics.
  • Multi-protocol partner behavior and ELD mock APIs (Samsara/Motive/generic) are implemented.
Open feature detail

Bookmarks & Timeline Navigation

Named time markers (e.g., "First pickup", "HOS warning") with time offset from scenario start, optional camera position for map view, and jump-to-bookmark capability for...

Outcomes

  • Scenario bookmark/time-marker system with timeline navigation and quick jump capabilities.
  • Replayability and demo pacing improvements through deterministic timeline control.
Open feature detail

Expectation Validation & Testing

CI/CD integration with expected events defined in scenario YAML, automatic validation during simulation, pass/fail results with failure reasons, and JUnit XML export for CI...

Outcomes

  • Expectation engine with scenario-driven validation and JUnit-compatible verification exports.
  • CI-oriented pass/fail assertions that bind simulation outcomes to expected events.
Open feature detail

Public Demo Mode

Full-screen map view with minimal chrome, floating controls overlay, auto-start demo scenario, and screenshot mode for proposals.

Outcomes

  • Minimal visual runtime for demos with auto-start and scenario-first UX controls.
  • Shared demo controls for public-facing walkthrough and screenshot capture readiness.
Open feature detail

Solution relevance

Select solution routes where this product participates in operational continuity.

This product index is currently expanding. Browse solution routes first, then return here to add continuity context as those mappings land.

Open solutions index

Continuity routes

Power-pair continuity routes that compress this product into reusable evaluation patterns.

Power-pair continuity links are introduced from solution routes as matching continuity patterns emerge.

Product-level proof for feature scope

  • 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

  • TelePulse event injection and fault simulation are implemented in scenario modules.

    partial

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

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

    Contract: proto/telepulse/simulator/v1

  • TelePulse route and HOS simulations are implemented with dedicated runtime modules.

    partial

    docs/products/telepulse/product.md · Module Catalog > Route Simulation & Generation

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

    Contract: proto/telepulse/simulator/v1

  • TelePulse trading-partner exchange behavior is implemented in VAN and partner simulator modules.

    verified

    docs/products/telepulse/product.md · Module Catalog > Trading Partner Simulator

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

    Contract: proto/telepulse/simulator/v1

  • TelePulse webhook and streaming contracts are implemented with event subscriptions and telemetry contracts.

    partial

    docs/products/telepulse/product.md · Module Catalog > Webhook & Event Streaming

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

    Contract: proto/telepulse/telematics/v1

  • TelePulse exchange and event pipelines are validated through cross-product contract registry usage.

    verified

    docs/products/telepulse/product.md · Cross-Product Integration Contracts

    Contract: proto/telepulse/telematics/v1

  • TelePulse exchange and scenario workflows are implemented in shipper and telemetry module boundaries.

    verified

    docs/products/telepulse/product.md · Cross-Product Integration Contracts

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

    Contract: proto/tms/streaming/v1