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

AxialSim: Vibration Data Generation

Generate realistic vibration waveforms with fault signatures using 15+ preconfigured machine profiles: Motors (1800 RPM induction motors, VFD-controlled), Pumps (centrifugal, turbine pumps with vane...

Problem

Predictive model and analyzer validation stalls when realistic, labeled vibration datasets are hard to produce.

Capability

Generate realistic vibration waveforms with fault signatures using 15+ preconfigured machine profiles: Motors (1800 RPM induction motors, VFD-controlled), Pumps (centrifugal, turbine pumps with vane...

How it works

  1. 1 Generate machine-profile waveforms with configurable signal parameters.
  2. 2 Inject fault signatures and anomaly patterns across execution windows.
  3. 3 Stream labeled vibration outputs for downstream analysis and training.

Operational outcomes

  • Higher-quality synthetic datasets for model and workflow validation.
  • Faster validation cycles for fault detection and analysis tooling.

Integration boundaries

  • Scenario Management
  • Execution Management

Proof model

Feature-level proof

  • Vibration Data Generation scope is defined in product module catalog.

    verified

    docs/products/axialsim/product.md · Module Catalog > Vibration Data Generation

  • AxialSim scenario configuration workflows are implemented in scenario modules and simulator contracts.

    verified

    docs/products/axialsim/product.md · Module Catalog > Scenario Management

    Code: backend/services/axialsim/internal/modules/scenarios

    Contract: proto/axialsim/scenario/v1

  • AxialSim scenario and execution flows are implemented in backend modules.

    verified

    docs/products/axialsim/product.md · Module Catalog > Scenario Management

    Code: backend/services/axialsim/internal

    Contract: proto/axialsim/scenario/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.