Ermes Laboratory Equipment Management Cloud Platform by VELP
| Brand | VELP |
|---|---|
| Origin | Italy |
| Model | Ermes |
| Software Type | Mass Spectrometry–Compatible LIMS Platform |
| Deployment | Web-Based SaaS |
| Compliance Framework | Supports GLP/GMP-aligned data integrity principles |
| Remote Control Protocol | HTTPS-secured RESTful API |
| User Access | Role-based multi-user web interface (PC, tablet, mobile) |
Overview
The Ermes Laboratory Equipment Management Cloud Platform by VELP is a secure, web-native SaaS solution engineered to unify instrument control, operational monitoring, and experimental data governance across heterogeneous laboratory environments. Unlike traditional on-premise LIMS or standalone instrument software, Ermes operates on a zero-client architecture—requiring no local installation—and leverages TLS 1.2+ encrypted communication to establish bidirectional connectivity between analytical instruments (including mass spectrometers, thermal analyzers, and sample preparation systems) and authorized users. Its core architecture follows ISO/IEC 27001–informed security design principles, with data residency hosted in EU-based Tier III cloud infrastructure. Ermes does not perform analytical computation itself; rather, it serves as an interoperability layer that standardizes metadata exchange, enforces access controls, and enables traceable instrument lifecycle management—from commissioning and calibration scheduling to remote diagnostics and firmware orchestration.
Key Features
- Instrument Integration Hub: Supports seamless onboarding of VELP’s CE-marked analytical instruments via Ethernet or Wi-Fi using embedded MQTT/HTTP(S) agents—no hardware modification required.
- Real-Time Operational Dashboard: Visualizes instrument status (idle/running/error), temperature profiles, runtime counters, and consumables usage history with sub-minute polling intervals.
- Role-Based Access Control (RBAC): Administrators define granular permissions per user group (e.g., “QC Analyst” may view but not modify method parameters; “Lab Manager” can approve calibration logs).
- Automated Alerting System: Configurable notifications delivered via in-platform banner, email, or SMS for events including protocol deviations, maintenance due dates, and unauthorized access attempts.
- Remote Intervention Capability: Authorized personnel may issue authenticated stop commands or initiate safe shutdown sequences during critical fault conditions—log entries are cryptographically timestamped and retained for audit.
- Over-the-Air (OTA) Software Management: Validates digital signatures before deploying instrument firmware or application-layer updates, ensuring version consistency and rollback capability.
Sample Compatibility & Compliance
Ermes is agnostic to sample type or assay modality; its scope covers instrument-level metadata—not raw spectral or chromatographic data. It complies with foundational requirements of ISO/IEC 17025:2017 (clause 7.5.2 on data protection), supports ALCOA+ principles (Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, Available), and facilitates adherence to FDA 21 CFR Part 11 through electronic signature logging, audit trail activation, and immutable record retention. While not certified as a full 21 CFR Part 11-compliant system out-of-the-box, Ermes provides the technical foundation—user authentication, session timeouts, change tracking, and exportable audit logs—for laboratories to configure validation protocols aligned with GxP environments.
Software & Data Management
Data ingestion occurs exclusively via instrument-generated JSON/XML payloads transmitted over authenticated HTTPS channels. All user-generated annotations, method configurations, and alert rules are stored in AES-256 encrypted databases. Export functionality supports CSV, PDF, and XML formats with optional digital watermarking for regulatory submissions. Audit trails capture WHO (user ID + role), WHAT (action type), WHEN (UTC timestamp), and WHERE (IP address + device fingerprint)—retained for configurable durations up to 36 months. Integration with third-party ELN or enterprise LIMS is enabled via documented REST APIs and SCIM 2.0 identity synchronization.
Applications
- Centralized monitoring of distributed mass spectrometry workstations across multi-site R&D labs.
- Automated calibration certificate linkage to instrument serial numbers and scheduled maintenance calendars.
- Remote troubleshooting support: VELP Field Application Specialists access anonymized diagnostic telemetry (with explicit lab consent) to accelerate resolution.
- Regulatory inspection readiness: One-click generation of instrument uptime reports, user activity summaries, and firmware version inventories.
- Cross-departmental collaboration: Shared dashboards enable QA, R&D, and production teams to monitor shared equipment utilization without compromising data sovereignty.
FAQ
Is Ermes validated for use in regulated pharmaceutical laboratories?
Ermes is designed to support validation activities under GMP/GLP frameworks. Customers must perform site-specific IQ/OQ/PQ and document configuration settings per their quality management system.
Does Ermes store raw mass spectra or chromatograms?
No. Ermes manages metadata only—such as acquisition timestamps, operator IDs, instrument parameters, and status logs—not primary analytical data files.
Can Ermes integrate with non-VELP instruments?
Integration is currently optimized for VELP’s CE-certified product portfolio. Third-party instrument compatibility requires custom API development and is evaluated case-by-case under VELP’s Professional Services engagement model.
What happens to data if internet connectivity is lost?
Instruments continue local operation with buffered event logging. Once connectivity resumes, queued metadata synchronizes automatically with conflict-resolution logic to preserve chronological integrity.
How frequently are security patches applied to the Ermes platform?
Critical security updates are deployed within 72 hours of CVE disclosure; scheduled maintenance windows occur monthly and are communicated 72 hours in advance via the customer portal.

