Use the DFELAB cloud, your existing SCADA system, or both.
R3CON is not limited to a standalone dashboard. It can collect remote field data and deliver it through DFELAB's cloud backend or integrate that data into existing SCADA and reporting workflows through API, FTP and custom views.
One field unit, multiple operating workflows
- Remote dashboards from anywhere
- Alerts, trends and reporting
- No customer SCADA required
- Vendor-independent data delivery
- Feed existing control-room workflows
- Custom views for customer-specific integrations
R3CON does not require the customer to abandon SCADA
Some sites have no practical remote visibility today. For those locations, the DFELAB cloud can be the complete monitoring interface. Other operators already have a SCADA standard and want new remote points to appear inside the workflow their control room already uses. R3CON can support that model as well.
The integration path can use API access, scheduled FTP delivery or customer-specific views and data exports. That makes the field hardware useful across mixed fleets where some assets live entirely in DFELAB and others need to feed an established SCADA, historian or reporting system.
Three common deployment models
| Deployment | Where operators view data | Best fit |
|---|---|---|
| Standalone R3CON | DFELAB cloud portal | Remote assets without an existing telemetry path |
| R3CON + SCADA integration | Customer SCADA / historian and optionally DFELAB | Operators who want remote R3CON data inside an existing enterprise workflow |
| R3CON alongside PLC/RTU control | Existing HMI/SCADA plus DFELAB as needed | Sites where engineered control remains in place but additional remote sensing is useful |
What R3CON is not trying to replace
Safety-critical logic, process interlocks, closed-loop control and engineered actuation should remain in the appropriate PLC/RTU or control system. R3CON's role is field data acquisition, connectivity, cloud visibility, reporting, alerting and integration. That distinction lets DFELAB complement existing automation instead of forcing a rip-and-replace decision.
Why this matters economically
An operator does not have to choose between a large new SCADA project and no data at all. R3CON can connect a difficult field point, provide an immediate cloud view, and later feed that same information into the customer's broader SCADA environment if the workflow requires it.
Integration planning starts with the receiving system
DFELAB reviews what the customer wants to receive, how often it should update, which fields and units are required, and whether API, FTP or a custom view is the best handoff. Because the receiving system consumes a standard data interface rather than a proprietary field bus, R3CON can integrate across SCADA vendors that can accept one of those supported data paths.