Skip to content
DREAMESOURCE

Cloud & remote service

A machine that has been delivered is not finished. The cloud platform keeps it visible: which units are online, what failed, what was worked, and which software version is actually in the field.

What it does

  • Fleet status

    Which units are online, what software version each is running, and when each last reported. This alone answers most "is it us or the machine?" support calls.

  • Remote diagnosis and service tickets

    Fault codes arrive with context, so a dealer can decide whether to send a technician before driving out. Service work is recorded against the machine, not against someone memory.

  • Work data and reporting

    Operating hours, counters and duty cycles per machine, for maintenance planning and for answering warranty questions with data.

  • Field software updates

    Firmware and application updates pushed over the air, with a rollback path if a release misbehaves in the field.

  • Web portal for service staff

    Dealers and service partners reach the machine record from a browser, on a phone in the workshop. No desktop application to install.

  • Your data, exportable

    Work records can be exported per machine or per period. Your operational data is yours, and we do not treat holding it as leverage.

What leaves the machine

Only what you enable. The terminal does not send anything you have not configured it to send.

  • Device state: online, firmware version, uptime, last contact
  • Selected machine parameters you map in EmbedBuilder (engine hours, counters, setpoints)
  • Fault codes and alarm history
  • Position, only if you configure it and only at the interval you choose

What it does not do

  • It does not stream continuously. Values are logged at an interval you set, and pushed by MQTT or HTTP.
  • It does not give us access to your control logic or your production data beyond the parameters you map.
  • It does not require your machine to be permanently online. Values are buffered on the device and sent when a connection exists.

Where it runs

The platform is operated by us, in the European Union, on the same infrastructure as this website. If your organisation requires it, we can scope a self-hosted deployment instead — say so early, because it changes the project.

Machine data and the GDPR

Machine telemetry is usually not personal data, but the operator name on a service ticket is. We keep the two apart: the platform stores machine identifiers and work records, and any personal data in the service workflow is handled under the same privacy policy as this website.

Privacy policy

Ask what the platform would see on your machine

Give us the machine type and the parameters you care about, and we will show you the concrete mapping before you commit to anything.

Request a technical session