One remote monitoring platform. Configured around the field problem.
R3CON combines field I/O, cellular telemetry, local data storage and web reporting so DFELAB can deploy the same core platform across different monitoring applications.
Built to collect the signals field operations already understand.
The current R3CON architecture includes support for industrial sensing and communications such as pressure, K-type thermocouples, pulse inputs, RS-485 and local storage, depending on the deployed configuration.
| Temperature | Multiple K-type thermocouple channels |
|---|---|
| Pressure / analog | Industrial analog input configurations |
| Pulse | Compatible meter and counter pulse monitoring |
| Field bus | RS-485 capability |
| Connectivity | Cellular telemetry |
| Local resilience | MicroSD data storage |
| Power visibility | Battery and power-system monitoring |
See what each R3CON functional block contributes.
The field unit and dashboard are one product system.
R3CON collects the signal at the asset, preserves context about device health and connectivity, and turns it into a remote operating view. The demo at right combines the pressure/temperature and pulse interfaces used across R3CON applications.
Demo note: Simulated telemetry, representative interface.
The hardware is only useful if people can act on the data.
Dashboards
Current status and historical trends organized by customer, site and device.
Alerts
Threshold-based workflows that surface conditions requiring attention.
Reporting
Date-range exports and operational reporting for historical review.
Access control
Customer and user structures designed for multi-site deployments.
Use DFELAB from anywhere or put R3CON data into the system your operators already use.
The DFELAB cloud can be the complete operating view for standalone deployments. When the customer already has SCADA, a historian or a reporting platform, R3CON data can be delivered through API, FTP and custom views rather than forcing a separate workflow.
API
Expose selected R3CON data to customer applications, SCADA connectors and enterprise workflows.
FTP delivery
Provide scheduled data files for systems that use file-based ingestion and established batch workflows.
Custom views
Build customer-specific views, exports and handoff formats around the fields their existing system expects.
DFELAB cloud
Use the web backend from anywhere for dashboards, alerts, reports and account-based access without customer-hosted infrastructure.
R3CON can integrate with SCADA environments that can consume one of the supported API, FTP or custom data interfaces. The customer's PLC/RTU and control logic can remain in place while R3CON supplies additional remote field data.
Start with the field problem. Configure the platform around it.
The same core platform can support different field signals, but each deployment should begin with a specific operating question: what must be visible remotely, how fast must the team know and what action follows?
A common hardware and software foundation simplifies deployment and support while allowing each site to be configured around the signals and reporting that matter there.
Have a monitoring problem that does not fit one of the three standard offers?
Tell us what signal exists in the field, what you need to know remotely and how the information changes an operating decision.