See Machine Condition Before the Problem Becomes Obvious.
MachineGuard connects machine-condition measurements to the Siteplore platform — turning vibration, temperature and relevant operating data into trends, alerts and engineering insight that support better maintenance decisions.
Machines rarely go from healthy to failed in one moment.
Many equipment problems develop progressively through changes in vibration, temperature, load or operating behavior. If condition information is only collected during periodic inspection, the degradation may develop between inspection intervals without being visible to the maintenance team.
Periodic Inspection Gaps
Manual routes provide valuable snapshots, but machine condition can change between inspection intervals.
Failure Without Trend Context
A high reading has limited value when there is no historical baseline to show how rapidly the condition is changing.
Maintenance Becomes Reactive
Without early evidence, teams may only investigate after abnormal noise, overheating, process impact or equipment failure becomes visible.
Condition → Trend → Warning → Diagnosis → Action
MachineGuard creates a continuous data path from selected machine-condition measurements to the engineering information maintenance teams need for investigation and prioritization.
Machine Condition
Sensors capture selected vibration, temperature or operating parameters.
Edge Monitoring
Field measurements are collected and transported into Siteplore.
Historical Context
Measurements become time-series trends instead of isolated readings.
Early Warning
Deviations and configured conditions highlight assets requiring attention.
Maintenance Decision
Evidence supports inspection, diagnosis and maintenance prioritization.
Monitor the signals that explain machine behavior.
Measurement selection depends on the machine, expected failure modes, operating conditions, criticality and the engineering objective of the deployment.
Vibration
Track relevant vibration indicators and their change over time.
Temperature
Observe bearing, casing or other applicable temperature behavior where instrumented.
Speed / Running State
Add machine operating context where suitable speed or running-state information is available.
Operating Context
Combine condition data with available load, process or electrical operating information.
Available measurements depend on the selected sensors, machine configuration and project scope. Detailed vibration diagnostics, waveform analysis, spectral analysis or additional condition-monitoring techniques require appropriate sensors, acquisition capability and engineering configuration.
Retrofit monitoring for selected rotating equipment.
MachineGuard is intended to help extend connected condition visibility to equipment that may not justify a large dedicated machinery-monitoring system.
More useful than a single alarm value.
MachineGuard combines sensing, historical information and operational context so teams can evaluate how machine condition is developing over time.
Continuous Condition Trends
Build historical machine-condition data between conventional inspection intervals.
Configurable Early Warnings
Highlight selected deviations and conditions that require maintenance attention.
Baseline & Trend Comparison
Compare current behavior against historical conditions and relevant operating periods.
Multi-Asset Dashboard
Review selected machines through centralized Siteplore monitoring views.
Operating Context
Relate condition information to available running, process or loading information.
Engineering Review
Managed service options can support interpretation and maintenance investigation.
Event History
Preserve condition changes and monitoring events for later technical review.
Expandable Deployment
Start with critical machines and scale monitoring according to demonstrated value.
The objective is not to collect vibration. It is to understand what changed.
Historical condition information helps teams move from isolated measurements toward structured technical investigation.
Early warning is valuable when it leads to better investigation.
A developing machine problem should become a maintenance question before it becomes an operational interruption.
Example: Increasing Pump Vibration
A typical path from condition change to maintenance action.
Condition monitoring is not machinery protection.
MachineGuard is designed to improve condition visibility and support maintenance decisions. Safety-critical shutdown and machinery protection functions require dedicated, appropriately engineered protection systems.
| Function | MachineGuard | Dedicated Protection System |
|---|---|---|
| Historical condition trends | Yes | System-dependent |
| Remote dashboards | Yes | System-dependent |
| Early-warning monitoring | Yes | Often available |
| Maintenance trend analysis | Primary purpose | System-dependent |
| Automatic machinery trip | No | Designed where required |
| Safety-critical protection | No | Dedicated function |
Better maintenance decisions start with better evidence.
MachineGuard does not eliminate failures by itself. Its role is to make important machine-condition changes more visible so maintenance teams can investigate earlier and prioritize resources more effectively.
Earlier Awareness
Identify developing condition changes between conventional inspection intervals.
Better Prioritization
Focus inspection and maintenance attention on machines showing relevant changes.
Historical Evidence
Preserve machine behavior before, during and after maintenance events.
Remote Visibility
Review selected equipment without depending entirely on local observation.
Improved Investigation
Use trends and operating context to support technical troubleshooting.
Scalable PdM Foundation
Build structured condition data that can support progressively more advanced analysis.
Start with the machines where earlier information matters.
MachineGuard deployment should begin with equipment criticality, known failure modes, monitoring gaps and the maintenance decisions the data should support.
Assess
Review asset criticality, failure history, operating conditions and existing maintenance strategy.
Engineer
Define monitoring parameters, sensor locations, installation and connectivity architecture.
Baseline & Validate
Establish initial machine behavior, validate data quality and configure monitoring views.
Monitor & Improve
Review trends, investigate deviations and expand deployment where value is demonstrated.
Choose how far you want to go beyond monitoring.
Begin with connected condition visibility and expand toward deeper analysis and engineering support. Final scope depends on number of assets, sensors, machine configuration and site requirements.
Monitor
For teams that need centralized machine-condition visibility, trends and configurable monitoring.
Optimize
For teams that need monitoring plus deeper trend comparison, operating context and analytical views.
Managed Insight
For teams that want MachineGuard monitoring supported by ongoing engineering review, interpretation and maintenance-oriented insight.
MachineGuard FAQ
What is MachineGuard?
MachineGuard is a retrofit condition-monitoring and early-warning solution that connects selected machine-condition sensors to Siteplore for historical trending, monitoring and engineering review.
Is MachineGuard a machinery protection system?
No. MachineGuard is intended for condition monitoring, early warning and maintenance decision support. It does not replace dedicated vibration protection, overspeed protection, protective relays, shutdown systems or safety-critical protection.
What machines can MachineGuard monitor?
Typical applications can include motors, pumps, fans, blowers and other selected rotating equipment. Suitability should be evaluated based on equipment configuration, criticality, failure modes and monitoring objectives.
What parameters can MachineGuard monitor?
Depending on the selected configuration, MachineGuard may use vibration, temperature, running state, speed and other relevant operating information. Available parameters depend on installed sensors and project requirements.
Does MachineGuard predict exactly when a machine will fail?
No. MachineGuard should not be assumed to provide an exact failure date or Remaining Useful Life prediction. Its primary purpose is to identify and contextualize changes in machine condition so that investigation can begin earlier.
Can MachineGuard diagnose bearing failure automatically?
MachineGuard can provide condition trends, warnings and analytical information. Detailed fault diagnosis depends on the sensors, available signal information, acquisition capability, machine characteristics and engineering analysis. Findings should be verified before maintenance action.
Can it replace periodic vibration inspection?
Not necessarily. Online or connected monitoring and periodic specialist inspection can complement each other. The appropriate maintenance strategy depends on machine criticality, failure modes and monitoring capability.
Can we start with only a few machines?
Yes. A focused initial deployment is often practical. Equipment can be selected based on criticality, failure history or known monitoring gaps, then expanded after the use case is validated.
Can MachineGuard be installed in hazardous areas?
Hazardous-area deployment must not be assumed. It requires appropriately certified equipment, installation methods and engineering review for the applicable area classification.
How should we start?
Start with machines that have operational consequence, repeated maintenance problems or insufficient condition visibility. Rekacipta can assess the equipment, monitoring objective, sensor requirement and practical deployment architecture.
What would change if you could see machine degradation earlier?
Start with a MachineGuard site assessment. Rekacipta can help identify suitable machines, monitoring parameters, sensor locations, connectivity requirements and a practical path toward connected condition monitoring.