Connecting industrial data acquisition with browser-based monitoring
Industrial factories often have a large amount of existing automation equipment. PLCs, sensors, machines, and controllers may already be working well, but accessing their data through a modern web interface can be challenging.
Replacing the entire control infrastructure is rarely the most practical option.
A better approach is to modernize the monitoring layer while keeping the existing PLC infrastructure.
A Two-Layer SCADA Architecture
A practical concept is:
PLC / Industrial Devices
↓
ATDriver Server
Communication Layer
↓
FastWeb
Web SCADA Layer
↓
Web Browser
The two software components have different roles.
1. ATDriver Server: Industrial Communication
ATDriver Server is designed to work as a communication and data acquisition layer for industrial systems.
It can support communication with different PLCs and industrial devices through multiple protocols.
Typical functions include:
- PLC and device communication
- Industrial data acquisition
- Tag management
- Multi-protocol integration
- Centralized data communication
For more technical information, see the industrial communication solution:
https://scada-thai.com/products/drivers-collection-atdriver-server
2. FastWeb 5.0.0.1: Web-Based SCADA
After industrial data is available, FastWeb 5.0.0.1 can provide the web-based SCADA interface.
It is designed for building monitoring applications that users can access through a browser.
Key capabilities include:
- Real-time monitoring
- Industrial data visualization
- Alarm management
- Custom web interfaces
- Remote monitoring
- Browser-based SCADA applications
Explore the web SCADA platform:
https://scada-thai.com/products/web-interface-design-fastweb-v5-0-0-1
Why Separate Communication and Visualization?
Separating these functions can make an industrial architecture easier to manage.
The communication layer focuses on getting reliable data from industrial devices, while the web layer focuses on presenting that data to users.
This approach can be useful when:
- Existing PLCs need to remain in operation
- Multiple industrial protocols are involved
- Engineers need centralized data
- Operators need browser-based monitoring
- The monitoring system may need to expand later
Example: Factory Machine Monitoring
Consider a factory with several production machines.
Each machine may use different PLCs or communication protocols. Instead of replacing these controllers, the system can be designed around a centralized communication architecture.
The collected data can then be presented through a web-based SCADA interface for:
- Machine status
- Production information
- Alarms
- Process values
- Operational monitoring
This gives operators a common monitoring environment while allowing the existing automation equipment to remain in service.
Benefits for System Integrators
For system integrators, this architecture can provide a more flexible starting point for industrial projects.
Main benefits:
- Reuse existing automation infrastructure
- Centralize industrial data
- Support different communication requirements
- Build browser-based monitoring applications
- Simplify future system expansion
- Reduce unnecessary hardware replacement
Conclusion
Modernizing an industrial SCADA system does not always mean replacing the existing PLC infrastructure.
A communication layer such as ATDriver Server combined with a web-based SCADA environment such as FastWeb 5.0.0.1 provides an approach for building more accessible industrial monitoring applications around existing automation systems.
If you are planning to connect existing PLCs and industrial devices to a web-based monitoring system, the right architecture should start with your PLC brands, communication protocols, device count, and monitoring requirements.
Have an existing PLC system that needs web-based monitoring? Share your requirements to discuss a suitable SCADA architecture.
Top comments (0)