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

TelePulse module

TelePulse is a fleet ecosystem simulator that generates realistic vehicle tracking, Electronic Logging Device (ELD), Hours of Service (HOS) data, and external trading partner...

Business outcome

High-scale data ingestion. Transform raw telemetry into operational insights and equipment health alerts in real-time.

IoT Ingestion

Capability pillars

  • Simulation Engine
  • HOS (Hours of Service) Simulation
  • Route Simulation & Generation
  • Scenario Building & Management

Workflow highlights

  • Scenario Building and Management workflow
  • Exchange and Event Streaming workflow
  • Simulation Engine workflow

Feature pages

Each deep product includes feature pages with problem/capability flow and evidence references.

Open full feature index

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

Open feature

Exchange and Event Streaming

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

Open feature

Simulation Engine

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

Open feature

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

Open feature

Route Simulation & Generation

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

Open feature

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

Open feature

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

Open feature

Exchange Engine (VAN Simulator)

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

Open feature

Trading Partner Simulator

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

Open feature

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

Open feature

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

Open feature

Public Demo Mode

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

Open feature

Solution relevance map

These solution routes consume this product to validate cross-flow continuity and buyer outcomes (0).

This product is currently represented through adjacent solution and feature index routes. Use adjacent solution pathways to inspect how it is consumed in cross-flow journeys.

Continuity routes

Power-pair routes compress solution continuity into evaluation runbooks for this product.

Product-level continuity routes are still maturing. Browse the solution and power-pair families first, then return here for route-level continuity details as the map expands.

Proof model

Product-level proof

  • 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

Continue product evaluation

Move into feature detail pages, then follow cross-product pathways to validate execution continuity.

Scenario Building and Management Exchange and Event Streaming Simulation Engine HOS (Hours of Service) Simulation Route Simulation & Generation Event Injection & Fault Simulation Trip Simulation & Multi-Stop Support Exchange Engine (VAN Simulator) Trading Partner Simulator Bookmarks & Timeline Navigation Expectation Validation & Testing Public Demo Mode View solutions Get in touch