Chladni FAQ

The Chladni Platform gives maintenance and reliability teams one place to see machine health, developing faults, alerts, trends, work orders, and recent activity across the plant.

The Chladni Platform gives maintenance and reliability teams one place to see machine health, developing faults, alerts, trends, work orders, and recent activity across the plant.

Primarily maintenance, reliability, engineering, and plant operations teams responsible for keeping industrial equipment running.

Primarily maintenance, reliability, engineering, and plant operations teams responsible for keeping industrial equipment running.

No. Chladni is designed to turn machine data into understandable faults, severity, and help you make the right decisions rather than requiring every user to interpret raw vibration data.

No. Chladni is designed to turn machine data into understandable faults, severity, and help you make the right decisions rather than requiring every user to interpret raw vibration data.

You get an overview of your plant, including current machine health, new alerts, updates to existing issues, recent work orders, and the assets that need attention.

You get an overview of your plant, including current machine health, new alerts, updates to existing issues, recent work orders, and the assets that need attention.

Yes. Multiple members of your maintenance and reliability team can access the platform, helping your team work from the same machine-health information and diagnostic findings.

Yes. Multiple members of your maintenance and reliability team can access the platform, helping your team work from the same machine-health information and diagnostic findings.

Yes. You can manage multiple facilities through a single Chladni account, giving your team visibility into monitored equipment across your sites.

Yes. You can manage multiple facilities through a single Chladni account, giving your team visibility into monitored equipment across your sites.

No. Plant leadership can use the higher-level overview while reliability teams can go deeper into diagnostics and trends.

No. Plant leadership can use the higher-level overview while reliability teams can go deeper into diagnostics and trends.

You don’t need to check the platform every day. Chladni continuously monitors your machines and will notify your team when a new issue is detected or an existing fault meaningfully changes. You can open the platform anytime for a full view of machine health, trends, alerts, and recent activity.

Then Chladni should make that clear too. The purpose isn't to constantly create maintenance work; it's to help your team know where attention is actually needed.

Start with equipment whose unexpected failure would significantly affect production, safety, product quality, or the operation of a critical line. Chladni’s Plant Builder helps determine the monitoring configuration for those assets.

Yes. Many plants prefer to begin with the equipment where an unexpected failure would have the largest operational consequence and expand monitoring later.

Yes. New equipment can develop problems related to installation, alignment, commissioning, manufacturing defects, or operating conditions. Monitoring from the start also helps establish a baseline of normal machine behavior, making it easier to identify changes over time.

Yes. Chladni can monitor equipment that runs intermittently, operates at variable speeds, or moves between different operating states. This includes batch equipment and machines that regularly stop and restart.

You can describe the equipment you want to monitor through Chladni's Plant Builder. Chladni determines the appropriate monitoring configuration based on the machine and drivetrain.

No. Tell us what equipment you have. Chladni determines the monitoring points and configuration.

If a machine cannot be confidently configured automatically call us at +1 945-206-2195 or email us at Info@Chladni.com

Yes. The system is designed so additional equipment can be added as your monitoring program expands.

Yes. When a monitored machine is replaced, you can reset the sensor so Chladni can begin learning the replacement machine’s operating behavior. Place the diagnostic cover on the sensor, then select the reset option in the Chladni app and follow the instructions.

Yes. The Plant Builder is designed to let you add your equipment, generate the monitoring configuration, and see pricing without having to wait for a traditional quotation process.

No. You describe the machine; Chladni handles the monitoring logic.

Yes. Saved configurations are intended to let you return and continue building your plant without starting again.

For larger configurations, Chladni can support a more efficient asset-import workflow rather than requiring every machine to be entered individually.

The intended workflow supports importing plant asset information so Chladni can process larger equipment lists and determine which assets can be configured automatically and which require engineering review.

Pricing can scale based on the number of monitoring points required. Larger or custom multi-motor systems may receive lower pricing per monitoring point as monitoring volume increases.

Yes. Once you complete your plant configuration and see your pricing, you can place your order directly through the Chladni website.

You can speak with our expert before moving forward, particularly for larger plants or more complex equipment.

A Chladni engineer reviews the equipment and confirms the monitoring configuration before the final setup is approved.

The deployment process begins as soon as your order is confirmed. We ship the hardware, arrange installation, and activate monitoring once the devices are installed and connected. Shipping and installation timelines are confirmed for your deployment.

Data comes from Chladni monitoring hardware installed on or around the equipment, including wireless vibration sensors and MCA hardware where applicable.

The Chladni Puck offers up to 10 years of battery life. Actual battery life depends on operating conditions and monitoring settings.

No. Chladni does not require access to your plant’s internal network to provide predictive monitoring.

No. Once monitoring is installed and connected, machine data flows into the Chladni system automatically.

No. One of the main purposes of continuous monitoring is to give your team visibility without requiring someone to manually check every machine continuously.

The affected device will appear as offline in the Chladni platform, so your team can clearly see when it is no longer connected. Monitoring updates and notifications may be limited until connectivity is restored.

Contact our support team for assistance. If a sensor or gateway supplied for your active subscription has a covered defect, we will replace it at no additional cost, including standard return and outbound shipping. This replacement protection continues throughout your active subscription.

No. Chladni is not currently intended for hazardous areas or extreme operating environments. All hardware must be installed and operated within its documented environmental limits.

Yes. The overview is designed to give you a plant-level picture before you drill down into individual machines.

Yes. Each monitored asset can have its own machine page with its health information, alerts, trends, monitoring devices, and activity.

Monitored assets can be given a clear machine-health view so teams can quickly understand which equipment appears healthy and which requires attention.

It reflects the available condition-monitoring information and detected machine-health issues rather than simply representing one raw sensor measurement.

Chladni continuously analyzes incoming machine data using both machine learning and physics-based diagnostic rules. When sufficient evidence of an abnormal condition or known fault pattern is detected, the system can generate a fault for review.

Chladni is designed to detect up to 98% of common mechanical and electrical faults across monitored equipment, including bearing defects, imbalance, misalignment, looseness, rotor bar issues, and other recognizable fault patterns.

No. The goal is to identify the likely fault rather than simply report that a measurement crossed a threshold.

Machine learning learns the unique heartbeat of each machine, how it normally behaves over time. When that heartbeat changes, Chladni can detect that something is becoming abnormal. Physics-based diagnostics then look for known fault signatures to help determine what the problem actually is. Together, they help Chladni detect changes early and identify the likely fault with greater confidence.

No. They operate independently so one diagnostic method does not have to wait for the other to identify a developing problem.

No. Chladni combines learned machine behavior with physics-based diagnostic methods rather than relying only on a single static alarm threshold.

Yes. Chladni combines automated diagnostics with expert review so the detected fault, severity, can be validated before reaching your team.

No. The platform is designed around actionable machine-health information rather than creating unnecessary alert noise.

Alerts include severity so your team can distinguish between issues requiring immediate attention and conditions that can continue to be monitored.

The platform can categorize issues as Critical, High, Medium, or Low.

Yes. Diagnostic confidence helps your team understand how strongly the available data supports the detected condition.

Yes. As additional machine data arrives and a condition progresses or stabilizes, the assessment can be updated.

Yes. Trend information lets you see how the condition has developed over time instead of viewing an alert as a single isolated event.

Your team can receive notifications by email, SMS, or the Chladni mobile app, according to your preferred communication channels.

Your team can review the issue, investigate the machine, acknowledge the alert, create or associate maintenance work, and follow the issue through resolution.

Yes. Alerts can move through states such as Active, Acknowledged, and Resolved, making it easier to keep track of what has and has not been addressed.

Yes. Machine-health findings can be connected to the maintenance workflow so the issue does not remain separated from the work being performed.

Yes. The platform is designed to surface both new alerts and meaningful updates to existing conditions.

Yes. The asset history helps your team understand previous machine-health events and how the equipment has behaved over time.

Yes. Chladni provides trend information so you can see how machine behavior changes over time.

Yes. Historical trends are an important part of understanding whether a condition is stable, improving, or progressing.

Yes. Raw machine data is available directly in the Chladni Platform for every monitored machine, alongside trends, diagnostics, alerts, and historical data. Reliability teams can go beyond the diagnosis and inspect the underlying data whenever they want.

The platform provides access to deeper vibration information for reliability teams that need to investigate the data behind a diagnosis.

Where applicable, diagnostic views can include frequency-domain information used to understand machine behavior and fault signatures.

Yes. You can view and export raw monitoring data for your own analysis, internal reporting, and recordkeeping.

MCA analyzes electrical information from suitable AC motors to provide additional insight into motor condition.

No. MCA is recommended only where it provides useful additional coverage and the motor/application is suitable.

No. They are complementary. Vibration monitoring is particularly useful for mechanical conditions, while MCA can provide additional information about electrical motor behavior.

Not automatically. The two technologies monitor different fault populations, so Chladni treats their coverage independently.

Yes. The purpose of identifying the fault early is to help your team move from detection into planned action.

Yes. Recent maintenance activity can be surfaced alongside machine-health information so you can understand what has happened across the plant.

Chladni continues monitoring the machine after maintenance, helping your team assess whether its behavior returns toward normal. This provides visibility into the outcome of the repair and any signs that the detected condition may still be present.

No. Chladni gives your team earlier and better information so they can make maintenance decisions with more time.

No. It gives reliability professionals continuous visibility and additional diagnostic information between inspections.

No. Chladni is designed around machine health and predictive maintenance. It does not require you to abandon your existing maintenance processes simply to monitor your equipment.

Our architecture is being designed so machine-health information can work alongside existing maintenance workflows. Available integrations can depend on the system being used.

Yes. Chladni supports integrations with SAP, MaintainX, Fiix, and Limble. The integration scope and setup requirements depend on your system and the workflow you need to support.

Yes. Chladni is designed to combine software with access to people who understand machine condition monitoring.

Chladni provides analyst-reviewed plant-health reporting in addition to individual fault review.

It is intended to summarize the important machine-health conditions across the monitored plant, including issues requiring attention and relevant developments during the reporting period.

Chladni's diagnostic processing runs through its cloud platform rather than requiring the diagnostic intelligence to be configured individually at every machine.

Chladni may store information needed to operate the account and monitoring service, such as customer details, plant information, configured assets, monitoring information, quotations, and maintenance-related platform activity.

Your machine and plant data remains yours. Chladni only uses it to provide, support, and improve the monitoring service. Chladni retains ownership of its platform, algorithms, diagnostics, and underlying technology.

Your plant and machine data is treated as confidential. Our security commitments include encryption during transmission over public networks and at rest in hosted storage, restricted access, and separation between customer accounts. The security controls for your deployment are documented before installation. We do not sell your operational data or use it for targeted advertising.

No. Chladni does not sell customer plant, machine, or monitoring data.

No condition-monitoring system can guarantee detection of every possible failure. Chladni is designed to identify developing conditions that are observable through the monitoring technologies installed on the asset.

No. An alert means Chladni has detected evidence of a developing condition that deserves attention. Severity, confidence, trends, and expert review help your team determine the appropriate response.

No. Monitoring significantly improves visibility into supported failure modes, but it cannot eliminate every possible equipment risk.

No. Chladni is a predictive-maintenance and condition-monitoring system. It should not be treated as a replacement for required machine-protection, safety, or emergency-shutdown systems.