Limited context after delivery
A service request may arrive without the alarm history, operating state, or configuration details needed for triage.
Remote service for machine builders and industrial OEMs
Build secure remote diagnostics, machine monitoring, and a repeatable service path into new or installed equipment.
What does remote service give a machine builder?
Remote service for machine builders combines a machine-side Orenda Box, organization-authorized access to selected resources, and configured operational data. An OEM service engineer can inspect a delivered machine without receiving broad access to the customer’s plant network. Customer approval, change control, operating safety, and PLC logic remain with the customer and the engineered control system.
Use configured machine context: Review the status, alarms, counters, trends, and service screens that the installation has been configured to expose.
Limit the access target: Authorize the service team for selected apps, devices, or services instead of assuming it needs the whole customer network.
Repeat the deployment method: Use the same readiness checklist and handover method for new deliveries and suitable retrofits.
Keep people in control: Engineers interpret the evidence and follow the customer’s approval, safety, and change-control procedures.
How the machine-side service path works
Each layer has a narrow job. The access path supports diagnosis and approved service activity; it does not become the machine’s control or safety system.
- Customer machine The PLC and engineered control system continue to run the machine and enforce the designed operating behavior.
- Orenda Box and local apps Configured machine data and local MES, SCADA, or service apps stay close to the equipment.
- Selected resource Organization configuration defines which app, device, or service a user is authorized to reach.
- OEM service engineer A named user opens an assigned resource in Orenda Connect and works within the customer’s service procedure.
Remote monitoring, diagnostic access, and control are different
Separating these modes makes scope, responsibility, and customer expectations easier to document before deployment.
| Mode | Purpose | Typical boundary | Orenda’s role |
|---|---|---|---|
| Monitoring | Observe configured status, alarms, counters, or trends. | Read-only views where the connected app and data path support them. | Provide machine-side data and authorized access to the selected view. |
| Diagnostic access | Inspect a service application, HMI, device, or engineering tool. | Orenda authorization determines reachability; the connected application and control system determine available actions, while customer procedure governs whether they are permitted. | Provide a resource-specific access path; access alone is not approval to change the machine. |
| Machine control | Issue commands, change logic, or alter the physical process. | Owned by the engineered control and safety systems and the site’s operating procedures. | Orenda is not the PLC, safety system, or customer approval workflow. |
What machine builders deal with
Different customer boundaries
Every customer has its own network rules, approval process, safety responsibilities, and maintenance windows.
One-off service methods
Different VPNs, credentials, contacts, and handover notes make the installed base difficult to support consistently.
Recommended service model
Start with one defined support scenario and one machine. Validate the customer boundary, hardware, power, network, protocols, data points, applications, roles, and handover evidence. When the operating method is accepted, use that checklist—not an assumed universal template—for the next suitable installation.
- Choose the machine and a specific diagnostic or monitoring scenario.
- Confirm cabinet space, power, network policy, protocol compatibility, and local ownership.
- Define the minimum data points, apps, devices, or service screens required for that scenario.
- Onboard the Orenda Box and configure the selected resources and organization access.
- Test monitoring and access with local personnel under the customer’s safety and change-control procedure.
- Record the handover, support contacts, recovery steps, and conditions for future service.
Where it creates value
A useful pilot has a narrow job, named owners, and evidence that the customer can operate the service path safely.
New machine delivery
Include the agreed resource scope, local installation, user onboarding, and service handover in the delivery plan.
Warranty diagnostics
Review configured alarms, counters, history, and service views before choosing the next diagnostic step.
Remote commissioning support
Support appropriate commissioning tasks when local personnel, safety procedures, test plans, and change control allow.
Installed-machine retrofit
Add a service path only after validating cabinet, power, network, protocol, data, application, and ownership requirements.
Operational outcomes
Better-defined triage
Give service engineers an agreed starting point and the configured machine context available at that installation.
Clearer customer handover
Document resources, roles, limits, contacts, and local responsibilities before remote service starts.
A repeatable service standard
Use consistent readiness and handover checks while preserving each customer’s network and operating authority.
Deployment requirements and limits
Remote access is one part of an OEM service process. Scope it with the customer and validate every installation rather than treating connectivity as permission or assuming every machine is compatible.
- The customer owns request approval, maintenance windows, change control, operating safety, and local authorization to work.
- Protocol, PLC, network, cabinet, power, application, and data compatibility must be checked for each machine design or retrofit.
- Monitoring shows only the signals and history that have been configured and made available by the connected systems.
- Named Orenda Connect users provide individual organization identity; a shared vendor link is a target-scoped bearer credential and does not identify each person who receives it.
- Optional MES AI sends relevant operational context to the configured OpenAI service for people to review; it does not change PLC logic or control the machine.
- Orenda does not guarantee remote resolution, reduced downtime, avoided travel, or regulatory compliance.
Machine builder remote service questions
What is remote service for machine builders?
It is an operating model that combines a machine-side data and application layer, authorized access to selected resources, and a documented customer service process. It can support monitoring and diagnosis while the customer retains approval, safety, and control responsibilities.
Can Orenda remotely control a machine?
Orenda provides access to configured resources; it is not the PLC or safety system. Whether a connected application permits a command is governed by that application, the engineered control system, user permissions, and the customer’s operating and change-control procedures.
Does Orenda replace the customer’s VPN or approval workflow?
Orenda can provide a resource-specific path for selected support workflows, so a user does not need broad plant-network access for every task. It does not replace the customer’s request, approval, maintenance-window, or change-control process, and network requirements still need site review.
What must be checked before retrofitting an installed machine?
Check cabinet space, power, environmental conditions, customer network policy, supported protocols, required data points, local applications, resource ownership, user roles, safety procedures, recovery steps, and handover evidence before deployment.
How are OEM service users authorized?
Named organization users can open assigned resources through Orenda Connect. A target-scoped vendor link can be revoked and may have an optional expiry, but it is a bearer credential and should be handled under the customer’s own sharing and approval rules.
Does remote service guarantee less downtime or travel?
No. Better access to configured evidence may help a team triage an issue, but resolution, downtime, travel, and service results depend on the fault, machine design, available data, local personnel, spares, procedures, and customer decisions.
Related pages
Orenda Box Industrial edge computer for machine data and local apps. Orenda Connect Named users open the selected machine resources assigned to them. Installed machine base Apply a documented service standard across suitable delivered machines. Security principles Review resource scope, endpoint identity, encryption, and revocation boundaries. Plans and pilot options Choose a narrow first workflow and a practical pilot scope.
Build a machine service pilot
Tell us what machine you build, what the customer permits, which resources and data the service team needs, and which diagnostic workflow should be tested first.
Plan a machine builder pilot