Skip to content
English
Submit Support Ticket Customer Support Portal
Contact us
  • There are no suggestions because the search field is empty.

Orbalux - Cloud telemetry & analytics

A non-technical overview of Orbalux, WISE Group’s cloud platform for telemetry and environmental data.

Purpose

Orbalux is WISE Group's cloud platform for centralising telemetry and environmental data from multiple sites. It provides secure ingestion, configurable storage, and dashboards and APIs for viewing, querying, and exporting data. This article is a concise, non-technical introduction to Orbalux. It explains what Orbalux provides, how data typically reaches the cloud, the security and connectivity model, practical matters to agree early, and common operational benefits.

What does Orbalux provide?

Orbalux centralises telemetry and environmental data from multiple sites. It accepts secure, time-stamped data, applies agreed tag naming and unit rules, stores data with configurable retention periods, and exposes dashboards and standard APIs for viewing, querying and exporting data. Contact your WISE Group project team to confirm the retention period applicable to your deployment.

Typical uses

Organisations use Orbalux to:

  • Operate central dashboards and compare data across many assets.

  • Use a single API or export point for downstream systems rather than many per-site integrations.

  • Maintain long-term records for reporting, audits and verification.

  • Ensure consistent tag names and units so data from different sites is comparable.

How does data typically reach Orbalux?

Common patterns are:

  • Lightweight telemetry pushes such as HTTPS POST or MQTT carrying time-stamped measurements.

  • Periodic secure file uploads (for example CSV over SFTP) for bulk or historical transfers.

  • API pulls where authorised systems request data from Orbalux.

  • Buffered forwarding from edge systems so site data is kept locally during outages and forwarded when connectivity is restored.

Sharing data with third parties

Orbalux can be used to share data with authorised third parties. Sharing is typically achieved through the web interface (dashboards and exports), standard APIs, or via dedicated interface modules where required. Some customers use custom interface modules to meet third-party formats or operational requirements (for example specialised aviation interfaces). Third-party sharing is managed by the customer’s access controls and the platform’s export/API facilities so that recipients only receive agreed data and views. Projects should confirm the legal, regulatory and contractual terms that govern any third-party sharing, together with the technical format and delivery method.

Security and connectivity model

Orbalux uses the following security and connectivity principles:

  • Data is sent using secure transport (MQTT over TLS or HTTPS). Connections are outbound-only from the customer network; the cloud does not initiate inbound connections.

  • Client authentication is certificate-based and managed per gateway instance. The cloud broker is a managed EMQX Cloud deployment. Confirm the current hosting region with your WISE Group project team, as regional availability may be subject to change.

  • Two gateway approaches are supported: a software gateway integrated into the on-site DADAS service, or a hardware gateway box that isolates the DADAS system from IP networks and publishes securely to the cloud. In the hardware option, the DADAS system communicates with the gateway box over a serial link (JSON messages), and the gateway box publishes to the cloud.

  • The platform supports redundancy, monitoring and logging under WISE Group operational control. Private peering or VPN options are available where traffic must remain off the public internet.

What should be agreed before going live with Orbalux?

Before deploying Orbalux, confirm the following with your WISE Group project team and any relevant third parties:

  • Ingestion method — for example HTTPS POST, MQTT, SFTP, or API pull — and the credentials or certificates required for each site.

  • Tag-naming conventions and engineering units so that data from all sites is consistent and comparable from day one.

  • Timestamp format and time-zone handling, including how aggregation boundaries are defined.

  • Data retention period applicable to your deployment.

  • Access control requirements, including which users, systems, or third parties need access and at what permission level.

  • Legal, regulatory, and contractual terms governing data storage and any third-party sharing.

Integration and downstream use

Orbalux complements on-site historians and per-site exports by acting as a central ingestion and normalisation layer. It feeds reporting tools, business intelligence platforms, and other downstream consumers via APIs or data exports. Before integration, agree units, timestamp formats, and aggregation methods with all participants — including your WISE Group project team — to ensure consistent results across the platform.

Common operational benefits

  • Central dashboards across a fleet of platforms.

  • Cross-site trend analysis and long-term reporting.

  • Single API for business systems that need consolidated site data.

  • Consolidated verification evidence and regulatory reporting across multiple installations.

Key takeaway

To ensure cloud integration and data sharing are reliable, compliant, and ready from day one, agree the following early with your WISE Group project team and any relevant third parties:

  • Ingestion methods and gateway approach for each site.

  • Security requirements and data-residency needs.

  • Retention periods and supported API formats.

  • Data conventions: tag naming, units, timestamp formats, and time-zone handling.