VAS — Vibration Analyser System
Catch bearing wear, imbalance, misalignment, and looseness on rotating machinery — before they become a breakdown. Continuous vibration analysis (time- and frequency-domain) on a single acquisition platform, feeding alarms and incidents into EREMOS V2.
FFT + order analysis · bearing / imbalance / misalignment / looseness · built on the mDAQ platform · feeds EREMOS V2.
Find the fault early enough to plan the intervention.
VAS is a vibration condition-monitoring system. It watches rotating machinery — motors, pumps, fans, gearboxes, conveyors — for deviations from normal vibration patterns, and identifies the developing fault: bearing wear, imbalance, misalignment, looseness, or structural cracking, before it becomes a breakdown. It runs the analysis a reliability engineer would run by hand, continuously.
It is part of the Condition Monitoring pillar — see the capability story → /capabilities/condition-monitoring. VAS is built on the mDAQ hardware platform, configured for specialized vibration acquisition and analytics — one acquisition platform, multiple application specialties, one intelligence stack (see → /mdaq). It feeds EREMOS V2: every flagged deviation becomes an alarm and a tracked incident in the same operational stack your team already uses.
What it does — and what it replaces.
Detects developing faults early
Watches for deviations from normal vibration patterns and flags bearing, imbalance, misalignment, looseness, and structural issues as the vibration signature develops.
Runs reliability-grade analysis, continuously
Time-domain severity and frequency-domain (FFT/spectrum) analysis on rotating equipment — not a once-a-quarter handheld spot-check.
Built on one platform
The same mDAQ acquisition platform, configured for vibration — one platform across your acquisition + condition-monitoring needs.
Feeds the maintenance workflow
Flagged deviations become EREMOS V2 alarms + tracked incidents — triage, assign, resolve, close.
VAS removes from the customer BOM:
- a dedicated vibration-analyser console (often a five-figure standalone instrument);
- a separate condition-monitoring software stack;
- manual handheld vibration spot-checks (which miss everything between visits);
- a third-party predictive-maintenance vendor relationship.
The analysis, and the platform it runs on.
Analysis capabilities are orientation-only / provisional — confirmed per deployment; not a locked feature matrix. The analysis package is configured per machine class — FFT/spectrum, RMS severity, order analysis, and advanced plots are selected where the machine and sensor setup require them. No formal certification claims (IP65 / IP67-compatible only).
| Category | Available / orientation capability — configured per machine class |
|---|---|
| Time-domain analysis | Peak detection, RMS severity (trend against normal) |
| Frequency-domain analysis | FFT / spectrum |
| Advanced analysis | Order analysis, Bode plot, polar plot, cascade, waterfall |
| Failure-mode mapping | Bearing, gear, and structural fault signatures |
| Acquisition platform | Built on the mDAQ hardware platform, configured for vibration acquisition — see /mdaq for the platform specs |
| Output / integration | Feeds EREMOS V2 (alarms, dashboards, incident workflows) over the canonical stream |
| Ingress protection | IP65 / IP67-compatible configurations can be scoped where the placement requires it; protection level + enclosure approach + any certification requirements confirmed during BOM scope. (Compatibility, not a certified rating — no formal IP certification currently claimed.) |
Confirmed during BOM scope (deployment-specific detail a reliability buyer expects — no invented numbers):
| Item | Confirmed during BOM scope |
|---|---|
| Sensors | Accelerometer type, axis count, sensitivity, frequency range, mounting method, cable routing, and placement count per machine |
| Acquisition | Sampling rate, resolution, bandwidth, measurement schedule (continuous vs. interval), and waveform / spectrum / trend retention |
| Speed / order reference | RPM source, tach / speed input if required, variable-speed assumptions, and order-analysis applicability |
| Analysis configuration | Which analyses + alarm thresholds per machine class; baseline / learning period; failure-mode templates |
| Mounting | Sensor mounting (stud / magnet / adhesive), cable routing, enclosure approach, environment |
| Integration | Alarm/incident mapping into EREMOS V2; report cadence |
How it goes on the machine.
| Sensors | Accelerometers mounted on the monitored equipment. Sensor type, mount (stud / magnet / adhesive), and placement confirmed during BOM scope. |
| Acquisition | Built on the mDAQ platform — vibration sampling rate / resolution and measurement schedule (continuous vs. interval) confirmed during BOM scope. |
| Baseline + thresholds | A baseline / learning period establishes "normal" per machine; alarm thresholds + failure-mode templates set per machine class. |
| Integration | Flagged deviations publish to EREMOS V2 as alarms + incidents. |
| Connectivity / power / environment | Per the mDAQ platform — connectivity, power, environment, and IP65 / IP67-compatible configuration confirmed during BOM scope (no certified rating claimed). |
The instrument in the stack.
ArchitecturePanel.interactive variant.
VAS shares the acquisition platform with mDAQ and the intelligence stack with EREMOS V2. For the oil-health instrument, see E-IDOS. The full stack → /architecture.
Start with the machine you worry about most.
Packaging labels are illustrative until commercial packaging is approved; this section describes how to engage + what it pairs with, not pricing.
VAS engagements start with a specific machine — the one whose failure would hurt most. It's scoped against the equipment class, the sensors + mounting, the measurement schedule, and the integration into EREMOS V2. For AMC providers, VAS turns a periodic spot-check service into continuous monitoring you can document for the customer; for in-house maintenance, it moves a critical machine from break-fix to condition-based planning. Bring the machine, its duty cycle, and its failure history; we'll scope sensors + analysis + alarms. Contact Elpis for availability and scoping; detailed pricing follows the scope. No pricing tables, SKU grids, or per-unit pricing on this page.
Built for the machine, proven in the field.
Built for the machine, on one platform.
VAS runs on the mDAQ acquisition platform, configured for vibration — ruggedized for rotating-equipment environments. Sensor mounting + IP65 / IP67-compatible configuration confirmed during BOM scope.
Where it's deployed.
Deployed in defense and space-agency programs — precision monitoring of high-value rotating equipment.
Maintenance and AMC providers across India and the Middle East use VAS to deliver their own condition-monitoring services.
Operating across India and the Middle East.
Formal third-party certifications are not currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope; IP65 / IP67-compatible configurations can be scoped where required, but certified/rated claims are published only when formal evidence exists. Specific customer names and case studies arrive with the Phase 3 customer-story program; the category descriptors above are the standing, authorized proof.
What maintenance teams ask.
What faults does VAS catch?
Developing faults on rotating machinery — bearing wear, imbalance, misalignment, looseness, and structural issues — by watching for deviations from each machine's normal vibration pattern and flagging them before they become a breakdown. It does not guarantee against every failure; it gives you early warning where the vibration signature shows it.
What analysis does it actually run?
Time-domain (peak detection, RMS severity) and frequency-domain (FFT / spectrum), with advanced analyses — order analysis, Bode, polar, cascade, waterfall — and failure-mode mapping for bearing, gear, and structural signatures. The specific analyses and alarm thresholds are configured per machine class during the scope.
Is this a separate box, or is it built on mDAQ?
VAS is built on the mDAQ hardware platform, configured for specialized vibration acquisition and analytics — one acquisition platform across your needs, not a separate hardware line. See /mdaq for the platform specs.
How does it fit my maintenance workflow?
Flagged deviations publish to EREMOS V2 as alarms and tracked incidents — triage, assignment, resolution, closure — in the same operational stack your team already uses. No separate condition-monitoring software silo.
We're an AMC provider — how does VAS help us?
It turns a periodic handheld spot-check service into continuous monitoring you can document for your customer: catch developing faults between visits, and hand over an evidence-backed diagnostic. Maintenance and AMC providers across India and the Middle East use VAS to deliver their own condition-monitoring services.
Is it certified? What about IP65 / IP67?
No formal third-party certifications are currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope. Where the placement requires IP65 / IP67-compatible protection, Elpis can scope a compatible configuration or enclosure approach; formal certification or rating claims are published only when the specific product/configuration has the required certification or test evidence.
What sensors does it use, and how are they mounted?
Accelerometers mounted on the monitored equipment; sensor type, frequency range, channel count per machine, and mount (stud / magnet / adhesive) are confirmed during BOM scope against the machine class and what you're watching for.
How is VAS different from E-IDOS?
Both are Condition Monitoring instruments for the maintenance buyer, but they watch different failure evidence. VAS is vibration on rotating machinery — bearings, imbalance, misalignment, looseness, and structural signatures — and feeds EREMOS V2 alarms / incidents today. E-IDOS is oil / fluid health on hydraulic and lubrication systems; its EREMOS V2 streaming status is handled on the E-IDOS page. See E-IDOS for hydraulics.
Bring us your most-watched machine.
The motor, pump, fan, or gearbox whose failure would hurt most — its duty cycle and its failure history. We'll scope the sensors, the analysis, and the alarms against that machine, and validate the warning logic before you scale it across the floor.