Machine visibility
Run, stop, idle, fault, cycle state, counters, and operator-facing status.
SCADA · IoT · MQTT · Modbus
Industrial monitoring built around trustworthy data
Connect machines, PLCs, meters, sensors, and gateways to dashboards that clearly show what is live, stale, alarming, or offline.
Java Electrindo designs practical monitoring systems for operators, engineers, and supervisors. The architecture can stay local on the factory LAN, extend through MQTT, or support controlled remote visibility when required.
Operational outcomes
Start from what the factory needs to see
The dashboard structure follows the process, the available data source, and the decisions people need to make.
Process values
Temperature, pressure, flow, level, humidity, energy, and other validated measurements.
Alarm & downtime
Active alarms, acknowledgement, recovery, repeat faults, and maintenance follow-up.
Production & OEE
Output, reject, availability, performance, quality, and shift-level reporting when source data supports it.
Architecture
A clear data path from the machine to the people who use it
A typical project reads field data, validates it at the controller or gateway layer, stores selected history locally, and serves dashboards without hiding communication health.
The final design depends on the actual PLC/controller, register or topic map, update rate, network boundary, and required operating mode.
1Sensor / meter / PLC source
2Validation & engineering units
3Local history / MQTT broker
4Dashboard, alarm & reporting
Protocols
Modbus reads devices; MQTT distributes selected data
One project may use either protocol or both. Protocol choice is based on the equipment and network—not on marketing preference.
Modbus
Practical register-based communication for PLCs, meters, VFDs, instruments, and local gateways.
MQTT
Publish/subscribe messaging for distributing selected values, events, alarms, and dashboard data through a broker.
Used together
A gateway can poll Modbus devices, validate engineering values, then publish only the required data to MQTT consumers.
Monitoring scope
What a useful industrial dashboard should make obvious
The interface should reduce interpretation time, not just place more numbers on a screen.
Machine state
Run, stop, idle, mode, cycle and fault.
Process trend
Current value, engineering unit, timestamp and historical trend.
AACKOK
Alarm lifecycle
Active, acknowledged, recovered and reported.
12,480output
Production counters
Batch, output, reject, target and shift context.
42.8kWh
Energy visibility
kWh, current, load pattern and demand where metering is available.
LIVESTALEINVALID
Data quality
Live, stale, invalid, disconnected, simulated or manual states.
Reliability
A dashboard must show whether its data can be trusted
Old or invalid values should never look identical to live values. Communication state, data age, source quality, and alarm history are part of the monitoring design.
Current source value inside the accepted update window.
The source has not updated within the expected time.
The value fails range, format, or engineering validation.
The device, gateway, or data path is unavailable.
Local-first option
Selected deployments can keep dashboards and history available on the local network even when the internet is unavailable.
Implementation
A controlled path from survey to handover
Good monitoring starts with verified source data and ends with an operator workflow that has been tested.
Survey
Confirm machines, signals, protocols, users, network boundaries and reporting needs.
Mapping
Document registers, topics, units, scaling, alarm conditions and data ownership.
Build
Configure gateway, dashboard, trends, alarms, roles and reporting outputs.
Validate
Test values, stale/offline behaviour, alarms, permissions and recovery paths.
Handover
Provide access, backup, operating guidance and technical references for responsible users.
FAQ
Common questions before a monitoring project
Can the dashboard work without internet?
Yes. A local-LAN deployment can provide internal monitoring. Remote access depends on the approved network design.
Can existing PLC data be used?
Yes, when the controller or gateway exposes a documented and supported path such as Modbus TCP, Modbus RTU, or MQTT.
Is remote control automatically included?
No. Monitoring and control are separate scopes. Commands that can affect equipment require permission design, commissioning, and safety validation.
Can the system generate reports?
Yes, when the necessary source data is available and validated.
Need a monitoring architecture for an existing machine or line?
Share the controller model, available protocol or register map, values to monitor, alarm expectations, and whether the system should stay local or support remote access.