RobustelConnect. Compute. Create.
PLAN YOUR OEM PILOT

Plan an OEM data-service pilot.

Start with one machine function, a repeatable device setup and data you can use. Agree who will maintain the setup and what needs to pass your checklist before the next project decision.

Applies to: For OEM teams planning an industrial data serviceReviewed: 29 October 2026Store guide v2 · match your installed release
FROM FIELD SIGNAL TO USEFUL DATARS-485 · Modbus RTU
Robustel S6000U multifunctional Modbus sensorS6000UModbus sensor data
Robustel EG5120 industrial edge computing gatewayEG5120Local processing & applications
ON THE GATEWAYE2C Factory

Collect, organise and visualise industrial data locally.

DEVICE OPERATIONSRCMS

Monitor and manage the gateway through an internet connection.

Connection diagram. Your quote confirms the hardware variant and included software and services.

Choose the machine task and who will help

Choose one question your team needs to answer, such as whether an agreed machine condition can be seen remotely. Name the machine owner, application developer, receiving-system owner and gateway/account administrator.

  • Prepare the machine interface and approved data points.
  • Identify pilot quantities, locations and expected operating conditions.
  • List the required local functions, destination system and intended users.
  • Involve your existing distributor or integrator when planning the pilot.

  1. Prepare a setup you can repeat

    Record the gateway variant, firmware, application version and required software rights. Keep shared settings separate from each machine’s addresses, identifiers and credentials. Decide how to identify each pilot unit and who keeps its setup record.

    Start with a read-only data point you have tested or the sensor exercise before expanding the application.

  2. Define the data your application needs

    Describe each measurement by name, unit, device identity and expected update behaviour. Explain how the receiving application will recognise a missing or older sample. Save one example with sensitive details removed and explain what it means in your project notes.

    Check the chosen interface with the receiving-system owner. The MQTT guide offers a focused exercise when MQTT is appropriate.

  3. Decide who manages the gateways

    Decide which organisation owns the gateway-management account, who can view devices and who may approve changes. Complete one RCMS identity and diagnostic check for the selected service. Record who to contact for help and what the local site contact should do if connectivity is lost.

  4. Check setup and recovery on another unit

    Use another authorised pilot unit or an approved reset-and-restore exercise to check whether you can repeat the setup. Note which settings must change for each device and which should stay the same. Confirm that you can find a saved configuration and restore it through the documented procedure.

    Watch what happens during a planned interruption and recovery of the data path. Review firmware or application updates separately, including compatibility, approval of changes and rollback steps.

  5. Review the results and next steps

    • The selected machine function has an agreed result and a named person to approve it.
    • The shared setup, per-device differences and required data are documented.
    • Checks of local data and remote management are recorded separately.
    • The results of a repeated setup or recovery exercise are recorded.
    • Someone is responsible for resolving open questions about installation, software rights, support and regional purchasing.

    Use the project brief template to record the results and the next phase you need. Continue with purchasing and partner support when you are ready to discuss the next step.

Checks when something does not work

The pilot works on one machine but not another

Compare controller firmware, mapping, device identifiers, network access and the included software features against the saved setup. Investigate the differences before assuming the setup supports other machines.

Who will support the setup after the pilot?

Identify who owns the hardware, local application, receiving service and gateway-management account. Assign renewal, updates, incident handling and site attendance separately before approving the next deployment phase.

Official technical references

E2C Factory manual — features and setup RCMS account and device-management reference EG5120 model and firmware references