DEV Community: Phuc Bach

Building a Practical Queue Management System with AT-QMS and AT-KEYPAD01

Phuc Bach — Tue, 15 Sep 2026 07:14:26 +0000

Modern service environments need more than a ticketing system. Hospitals, clinics, banks, and customer service centers require better coordination between customers, service counters, and staff operations.

A queue management solution can help organizations improve customer flow, simplify counter operations, and create a more organized service experience.

This article explores how ATPro's AT-QMS Queue Management Software and AT-KEYPAD01 Industrial Keypad can be considered together when planning a queue management and counter-service automation project.

The Challenge: Managing Customer Queues Efficiently

In busy service environments, manual queue handling can create several operational challenges:

Customers may experience long waiting times.
Staff may need to manage queue operations manually.
Managers may have limited visibility into service counter activities.
Expanding the number of service counters can make coordination more difficult.

A digital queue management system provides a way to organize these operations through software and dedicated operator interfaces.

The Solution: AT-QMS + AT-KEYPAD01

ATPro combines queue management software with industrial hardware to support practical service automation.

The two products have different roles in the overall solution:

AT-QMS: Software for queue management and service coordination.
AT-KEYPAD01: A dedicated keypad for operator interaction and system integration.

The combination can be evaluated for projects that require both centralized queue management and a physical control interface at service counters.

1. AT-QMS Queue Management Software

AT-QMS provides a software-based environment for managing customer queues and coordinating service counters.

A queue management platform can support organizations in structuring customer flow, organizing service operations, and improving visibility into daily activities.

For more information, visit the AT-QMS Queue Management Software product page.

2. AT-KEYPAD01 Industrial Keypad

A practical queue management system also needs an operator interface that is convenient for staff to use.

AT-KEYPAD01 is an industrial keypad designed for operator interaction and automation system integration. Its supported communication interfaces can be evaluated for applications requiring a physical control device at service counters.

Explore the AT-KEYPAD01 Industrial Keypad product page for more information.

How the System Can Be Organized

A typical project architecture may include the following components:

Customer
   |
   v
Ticket Issuing System
   |
   v
AT-QMS Queue Management Software
   |
   v
Service Counter Operations
   |
   v
AT-KEYPAD01 Operator Interface

The exact communication architecture depends on the project requirements, including the queue functions, number of counters, display systems, and integration methods.

Key Benefits

Better Customer Flow

A structured queue management process helps organizations organize customer service and improve the overall waiting experience.

More Convenient Counter Operations

A dedicated keypad can provide service staff with a physical interface for interacting with queue-related functions.

Improved Operational Visibility

Centralized software can help organizations monitor service activities and identify opportunities to improve workflow.

Flexible Integration

The keypad's supported interfaces can be evaluated as part of a broader automation or service management system.

Practical Applications

This solution can be considered for:

Hospitals and clinics
Banks and financial service centers
Government service offices
Customer service centers
Organizations managing multiple service counters

Each application requires a technical assessment to determine the appropriate software configuration, hardware requirements, and integration approach.

Planning Your Queue Management Project

Before implementing a queue management system, organizations should evaluate:

The number of service counters.
The required queue management functions.
The operator interface requirements.
The communication architecture.
The need for displays, reporting, and system integration.

A clear understanding of these requirements helps ensure that the selected solution matches the actual service workflow.

Conclusion

AT-QMS Queue Management Software and AT-KEYPAD01 Industrial Keypad provide two complementary components for organizations exploring queue management and counter-service automation.

By combining software-based queue coordination with a dedicated operator interface, businesses can work toward more organized service operations and improved customer experiences.

Are you planning a queue management system for a hospital, clinic, bank, or service center?

Contact ATPro to discuss your application, technical requirements, and RFQ.

Connecting AI Forecasting with Web SCADA for Smarter Industrial Monitoring

Phuc Bach — Mon, 14 Sep 2026 07:19:58 +0000

Industrial AI becomes more valuable when forecasting results are connected directly to the monitoring environment. Instead of keeping predictions inside a separate application, engineers can display them alongside live SCADA data through browser-based dashboards.

From SCADA Data to Actionable Insights

ATSCADA AI Predictor analyzes historical and real-time industrial data to identify trends, forecast future conditions, and support predictive maintenance.

However, forecasting alone is not enough. If the results are available only on a dedicated workstation, remote engineers and managers may not see important information quickly.

This is where ATSCADA FastWeb becomes valuable.

Integrating AI Predictor with FastWeb

A typical workflow can be structured as:

Industrial Devices → Data Collection → SCADA Core → AI Predictor → FastWeb Dashboard

The SCADA system collects and processes data from industrial equipment. AI Predictor analyzes the data and generates forecasting insights. FastWeb then presents the results through customizable Web SCADA interfaces that authorized users can access using a web browser.

Benefits for Industrial Operations

Remote monitoring: View live SCADA values and forecasting results from supported devices.
Predictive maintenance support: Identify changing equipment conditions and plan maintenance activities earlier.
Improved decision-making: Compare current values, historical trends, and predicted behavior in one interface.
Multi-site visibility: Monitor production lines, departments, or facilities through centralized dashboards.
Flexible visualization: Design Web SCADA interfaces for production, energy, infrastructure, and process monitoring.

Practical Applications

This combined solution can support:

Equipment performance forecasting.
Production trend analysis.
Energy consumption monitoring.
Predictive maintenance dashboards.
Water and wastewater monitoring.
Factory-wide operational visibility.
Remote supervision of industrial processes.

Conclusion

AI forecasting becomes significantly more useful when its results are connected to daily industrial monitoring.

ATSCADA AI Predictor provides forecasting capabilities, while ATSCADA FastWeb presents these insights through browser-based Web SCADA dashboards. Together, they connect data collection, AI analysis, visualization, and remote monitoring in one practical industrial solution.

From Threshold Alarms to Predictive Monitoring for Server Room Cooling

Phuc Bach — Sat, 12 Sep 2026 07:23:47 +0000

A server room cooling system can look completely normal while its performance is gradually deteriorating.

For engineers managing IT infrastructure, this creates an important challenge: a threshold alarm can tell you when conditions have become unsafe, but it may not tell you that the cooling system has been getting worse for days.

This is where time-series analysis can add another layer to conventional environmental monitoring.

The Problem with Threshold-Only Monitoring

A typical server room monitoring system continuously measures parameters such as:

Temperature
Humidity
Environmental status
Alarm conditions

For example, an alarm might be configured to trigger when room temperature exceeds a predefined limit.

This works well for detecting an immediate abnormal condition.

However, consider a different scenario.

The room temperature remains below the alarm threshold, but:

The average temperature slowly increases
Temperature fluctuations become larger
The cooling system takes longer to restore the target temperature
Similar abnormal patterns appear repeatedly

None of these changes may immediately trigger a threshold alarm.

Yet together, they may indicate that the cooling environment is changing.

Using Historical Data as an Engineering Signal

A real-time server environment monitoring platform provides the data required to understand current and historical environmental conditions.

Instead of looking only at the latest temperature value, engineers can examine the time-series behavior of the system.

Conceptually, the workflow becomes:

Sensor Data → Historical Dataset → Trend Analysis → Forecasting → Maintenance Decision

This approach does not replace threshold alarms.

It complements them.

Where AI Time-Series Forecasting Fits

An AI time-series forecasting platform can be used to analyze historical time-dependent data and forecast future patterns.

For a server room application, temperature and humidity measurements can potentially become forecasting inputs.

The objective is to identify changes such as:

Normal trend → Gradual deviation → Increasing risk → Investigation

For example, if the predicted temperature trend consistently moves upward while historical recovery behavior also changes, the engineering team can investigate the cooling system before the environment reaches a critical alarm threshold.

The forecasting model does not need to replace the existing SCADA or monitoring architecture.

Instead, it can act as an additional analytical layer.

Monitoring vs. Prediction

These two functions solve different problems.

Monitoring	Predictive Analysis
Shows current conditions	Examines changing patterns
Detects threshold violations	Forecasts future trends
Generates immediate alarms	Supports early investigation
Focuses on current state	Focuses on time-series behavior

A robust strategy can use both.

Monitoring answers: “What is happening now?”

Forecasting helps answer: “What could happen next?”

Practical Engineering Benefits

Adding predictive analysis to environmental data can help organizations:

Identify gradual temperature changes
Detect unusual trends earlier
Support proactive maintenance planning
Reduce dependence on emergency intervention
Utilize historical monitoring data more effectively
Give engineering teams additional information for maintenance decisions

Most importantly, this approach can build on data that the monitoring infrastructure is already collecting.

There may be no need to start with a completely new sensor architecture.

A Practical Implementation Approach

For an existing server room, an initial implementation could follow these steps:

1. Collect

Gather historical temperature and humidity data from the existing monitoring system.

2. Validate

Check data quality, sampling intervals, missing values, and abnormal readings.

3. Analyze

Look for baseline changes, fluctuations, recovery behavior, and recurring patterns.

4. Forecast

Apply time-series forecasting to identify potential future trends.

5. Investigate

When an unusual trend appears, inspect the cooling equipment and operating conditions.

6. Maintain

Use the additional information to support a planned maintenance decision rather than waiting for a critical alarm.

Moving Toward Proactive Infrastructure Management

The key idea is simple:

A temperature alarm tells you when the environment has crossed a limit. Historical data may tell you that the system is moving toward that limit.

Combining real-time monitoring with predictive analysis creates a more complete view of server room conditions.

For organizations already collecting environmental data, this provides a practical path toward more proactive infrastructure management.

If you are evaluating this approach for your server room, data center, or industrial facility, ATPro can help discuss the monitoring architecture, available data, and potential forecasting workflow.

Contact ATPro for a technical consultation.

Building a SCADA-Based Water Level Monitoring System for Industrial Applications

Phuc Bach — Fri, 11 Sep 2026 06:27:48 +0000

From sensor data to real-time visualization, alarms, pump control, and historical monitoring

Industrial water tanks are often treated as simple infrastructure, but manual level checks can create operational risks. Overflow, low-water conditions, pump failures, and delayed responses can affect production and equipment reliability.

A practical approach is to connect a water level sensor to a SCADA monitoring system, allowing operators to collect, visualize, and act on water-level data in real time.

A Simple Industrial Architecture

A typical implementation can follow this structure:

Water Level Sensor
        ↓
     PLC / RTU
        ↓
 Communication Network
        ↓
      ATSCADA
        ↓
 Web SCADA Dashboard
        ↓
 Alarm / Pump Control / Reports

The sensor measures the water level and sends field data to the control layer. ATSCADA then converts this information into a centralized monitoring interface.

For a practical example of this architecture, see the SCADA-based reservoir and tank monitoring solution.

What Should the SCADA Dashboard Monitor?

A useful water-level dashboard should provide more than a single numerical value.

1. Real-Time Tank Level

Operators can immediately see the current water level and identify whether the tank is operating within its normal range.

2. High and Low-Level Alarms

Alarm thresholds can be configured to notify operators when the tank reaches abnormal levels.

For example:

Level > High Limit  → High-Level Alarm
Level < Low Limit   → Low-Level Alarm
Normal Range        → Normal Operation

This allows operators to respond before an abnormal condition becomes a larger operational problem.

3. Pump Status

Pump operation can be displayed alongside tank-level information.

This makes it easier to determine whether:

The pump is running
The pump is stopped
The tank level is increasing or decreasing
An abnormal condition requires attention

4. Historical Trends

Historical data can show how water levels change throughout the day, shift, or production cycle.

This information can help engineers analyze consumption patterns and optimize system operation.

Integrating Water Quality Monitoring

Some applications require more than tank-level information.

Factories and water-treatment facilities may need to monitor parameters such as pH, DO, TSS, COD, temperature, turbidity, TDS, and flow rate.

The Automatic Water Environment Monitoring System provides a broader monitoring approach, combining sensor data with centralized SCADA visualization, alarms, historical records, and reporting.

This allows the same monitoring concept to be applied to wastewater and water-treatment processes.

Why Use SCADA Instead of Manual Inspection?

The main advantage is continuous visibility.

A connected system can help facilities:

Reduce repetitive manual inspections
Detect abnormal water levels earlier
Improve pump monitoring
Reduce overflow risks
Maintain historical operational data
Support remote supervision
Make operational decisions using real-time information

Instead of asking “What is the tank level right now?”, engineers can also analyze “How has the level changed over the last 24 hours, and what caused the change?”

Practical Applications

This architecture can be adapted to many industrial environments:

🏭 Manufacturing plants
🚰 Water-treatment facilities
♻️ Wastewater systems
🏢 Commercial buildings
🛢️ Industrial storage tanks
🌾 Agricultural water systems
🏨 Hotels and large facilities

The hardware and communication layer can be selected according to the sensor type, tank configuration, control requirements, and existing automation infrastructure.

From Monitoring to Automation

Water-level monitoring becomes even more valuable when combined with automatic control.

For example:

Low Level Detected
        ↓
     Start Pump
        ↓
Tank Filling
        ↓
High Level Detected
        ↓
     Stop Pump

This creates a closed-loop approach where sensor data is not only displayed but also used to support automatic operation.

Final Thoughts

A water-level sensor by itself provides valuable field data. Connecting that data to SCADA turns it into an operational tool for visualization, alarming, historical analysis, and control.

For industrial facilities managing tanks, pumps, or water-treatment processes, this approach can provide a practical foundation for more reliable and data-driven water management.

📩 Need to design a water monitoring system for your facility? Contact SCADA-Thai to discuss your application and request an RFQ.

Your Server Room Temperature Is Normal. So Why Did the Hardware Fail?

Phuc Bach — Thu, 10 Sep 2026 07:18:26 +0000

Temperature monitoring is essential for server infrastructure—but it does not tell you everything about the conditions affecting your equipment.

When a server, PSU, storage device, or network component unexpectedly fails, environmental data is usually one of the first things engineers review.

Was the temperature too high?

Was humidity outside the acceptable range?

Was there a cooling problem?

But there is another question worth asking:

Was the electrical supply stable at the time of the incident?

Environmental Data Doesn't Capture Electrical Events

A typical server-room monitoring setup may track:

Temperature
Humidity
Water leakage
Smoke
Cooling conditions

This information is important for maintaining a safe physical environment.

However, electrical events are a different category of risk.

Voltage drops, overvoltage, current abnormalities, and other power-quality events can occur independently of room temperature.

An electrical disturbance may last only briefly.

During that period:

Temperature:      Normal
Humidity:         Normal
Cooling:          Normal
Electrical supply: Abnormal

If the monitoring system only records environmental parameters, the electrical event may not appear anywhere in the historical data.

Add an Electrical Monitoring Layer

A dedicated power-monitoring layer can provide additional visibility into the electrical conditions supplying critical equipment.

A Power Monitoring System can monitor parameters such as voltage and current, depending on the selected configuration.

This data can then be compared with other operational information:

Equipment Alarm
       │
       ├── Environmental Data
       │
       ├── Electrical Data
       │
       └── Maintenance / Event Logs
                │
                ▼
       Incident Investigation

The purpose is not to automatically conclude that a voltage event caused a particular hardware failure.

Instead, electrical measurements provide additional evidence for troubleshooting and root-cause investigation.

Why Historical Electrical Data Matters

Imagine a server unexpectedly shuts down at 14:32.

The environmental monitoring dashboard shows:

Temperature: Normal
Humidity: Normal
Cooling: Normal

Without electrical data, the investigation may focus entirely on the server itself.

With power monitoring, engineers can also check whether an electrical abnormality occurred around 14:32.

That gives the troubleshooting process another important data source.

Practical Benefits for IT and Facility Teams

Faster Troubleshooting

Historical electrical measurements can help engineers correlate equipment incidents with electrical events.

Better Infrastructure Decisions

If abnormal voltage events occur repeatedly, the data can support decisions about UPS capacity, voltage regulation, or other power-protection measures.

Improved Asset Protection

Critical IT infrastructure represents a significant investment. Monitoring both environmental and electrical conditions provides broader visibility into potential risks.

Better Maintenance Records

Historical power data can become part of an incident and maintenance record, helping teams understand recurring infrastructure problems over time.

Environmental Monitoring vs. Power Monitoring

These systems should not be viewed as competing technologies.

They monitor different layers of the infrastructure.

Monitoring Layer	What It Helps You See
Environmental Monitoring	Conditions surrounding the equipment
Power Monitoring	Electrical conditions supplying the equipment
Equipment Monitoring	Server and device operating status

A more complete infrastructure-monitoring strategy can use all three data sources.

For server-room environmental monitoring, you can explore Data Center Monitoring Software:

https://scada-thai.com/products/data-center-monitoring-software?variant=54843700183331

For electrical monitoring, see the Electrical Power Monitoring Solution:

https://scada-thai.com/products/power-monitoring-systems?variant=55206633275683

A More Complete Approach to Server Reliability

Keeping a server room at the correct temperature is necessary—but it is only one part of infrastructure reliability.

When unexpected hardware failures occur, engineers need as much useful historical data as possible.

Environmental data answers one question:

What was happening around the equipment?

Electrical monitoring adds another:

What was happening to the power supplying the equipment?

For critical server rooms and data centers, that additional visibility can make troubleshooting more systematic and infrastructure decisions more data-driven.

Planning a Power Monitoring System?

Share your electrical system, monitoring points, required parameters, and communication requirements with our team to discuss a suitable configuration.

Building a Web-Based SCADA Architecture for Existing PLC Systems

Phuc Bach — Wed, 09 Sep 2026 07:32:04 +0000

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.

Integrating Data Center Infrastructure and Energy Monitoring with AT-DCMS + AT-PMS

Phuc Bach — Tue, 08 Sep 2026 06:37:42 +0000

Modern data centers generate data from many systems: environmental sensors, HVAC, electrical equipment, UPS, power meters, alarms, and other critical infrastructure.

The challenge is not simply collecting this data. The real challenge is turning different data sources into a unified operational view.

A Two-Layer Monitoring Approach

A practical architecture is to combine:

AT-DCMS → Data center infrastructure and environmental monitoring
AT-PMS → Power and energy monitoring

This creates a broader monitoring layer covering both facility conditions and electrical performance.

1. Infrastructure Monitoring with AT-DCMS

AT-DCMS can be used to monitor critical data center conditions such as:

Temperature and humidity
Cooling and HVAC
Server room infrastructure
Water leakage
Safety conditions
Alarm events

Explore AT-DCMS Data Center Monitoring

2. Power and Energy Monitoring with AT-PMS

AT-PMS focuses on electrical and energy information, including:

Voltage and current
Power consumption
Energy consumption
Historical data
Abnormal power conditions
Energy analysis

Explore AT-PMS Power Monitoring

How the Two Solutions Complement Each Other

A simplified architecture can be viewed as:

Environmental / Infrastructure Data
              │
              ▼
          AT-DCMS
              │
              │
              ├──── Centralized Monitoring
              │
              │
Power / Electrical Data
              │
              ▼
           AT-PMS
              │
              ▼
     Analysis + Alarms + Reports

The important point is that these systems address different but connected operational domains.

AT-DCMS helps answer:

What is happening to the data center infrastructure?

AT-PMS helps answer:

How is the facility consuming and using electrical power?

Together, they provide a more complete operational picture.

Practical Benefits

This approach can help engineering and facility teams:

Monitor critical conditions in real time
Identify abnormal infrastructure conditions earlier
Analyze energy consumption
Correlate operational conditions with power usage
Support preventive maintenance
Improve energy efficiency
Reduce unnecessary operational costs
Make decisions based on historical and real-time data

Where Can This Architecture Be Used?

The combination is suitable for environments where both infrastructure reliability and energy visibility are important:

Data centers
Server rooms
Telecom facilities
Banking infrastructure
Enterprise IT facilities
Critical infrastructure facilities

From Monitoring to Optimization

The value of a monitoring system increases when operational data can be used for continuous improvement.

A typical progression is:

Collect → Monitor → Analyze → Detect → Optimize

By combining infrastructure monitoring with power and energy analytics, organizations can move beyond simply watching dashboards toward more informed facility management.

If you are developing a Data Center Monitoring or Energy Management system, ATPro can help evaluate the required monitoring points, existing equipment, communication architecture, and suitable configuration for your project.

Building the Data Layer for Industrial AI: From PLCs to Predictive Analytics

Phuc Bach — Mon, 07 Sep 2026 07:32:07 +0000

Industrial AI is often presented as a Machine Learning problem.

Choose a model, send it historical data, generate predictions, and display the results.

In a real factory, however, the first challenge usually appears before the AI model runs:

How do we reliably move data from industrial devices into the AI system?

A production environment can contain PLCs, sensors, meters, machines, and IoT devices from different vendors. Each device may use a different communication protocol, data structure, or connection method.

This makes the data acquisition layer an important part of the overall AI architecture.

The Industrial Data Flow

A practical architecture can be represented as:

PLC / Sensors / Field Devices
↓
ATDriver Server
↓
SCADA / Industrial Data
↓
AI Predictor
↓
Forecasting & Predictive Insights

The important point is that the AI application does not replace the communication layer.

The AI needs a reliable data source before it can perform meaningful analysis.

Where ATDriver Server Fits

ATDriver Server works as a communication layer between industrial field devices and higher-level applications.

Instead of building a separate data connection for every application, the industrial data can be collected through a dedicated driver and communication layer.

This approach is useful when a factory contains different device types and communication protocols.

For example:

PLC data
Sensor measurements
Machine operating values
Industrial meters
Real-time process parameters

The collected data can then become available to SCADA and other software applications.

You can learn more about the industrial communication and data acquisition layer here:

https://scada-thai.com/products/drivers-collection-atdriver-server?variant=54843992801571

Why Data Quality Matters for AI

Consider a simple time-series forecasting application.

The model may need a continuous sequence such as:

10 → 12 → 13 → 15 → 17 → ?

If the data contains unexpected gaps, incorrect values, or inconsistent timestamps, the forecasting process can become less useful.

This is why industrial AI should not be considered only from the algorithm perspective.

The complete data pipeline matters.

Device connectivity → Data collection → Historical data → AI analysis → Prediction

Each step contributes to the final result.

Adding the AI Layer

After the industrial data is available, AI Predictor can analyze historical and real-time data for time-series forecasting, trend analysis, and anomaly detection.

The AI-powered industrial forecasting software can be used as the analytics layer above the industrial data infrastructure:

https://scada-thai.com/products/ai-predictor?variant=54843960557859

This creates a separation of responsibilities:

ATDriver Server

Connects industrial devices
Collects industrial data
Provides the communication foundation

AI Predictor

Analyzes historical and real-time data
Identifies trends
Generates forecasts
Supports anomaly analysis

This separation can make the overall architecture easier to understand and expand.

Why This Matters for Factory Integration

A factory may start with a few machines and later add new production lines, sensors, or PLCs.

If the data architecture is designed properly from the beginning, new devices can be integrated into the existing data flow without redesigning the entire AI application.

This provides several practical benefits:

Multi-device connectivity

Different industrial devices can be connected through the communication layer instead of creating isolated data paths.

Centralized data flow

Industrial data can be collected before being used by SCADA, analytics, or AI applications.

Easier scalability

Additional machines and sensors can be added as the factory grows.

Better preparation for predictive applications

A stable data foundation can support use cases such as predictive maintenance, production monitoring, process analysis, and industrial forecasting.

The Bigger Picture

The most important lesson is simple:

Industrial AI does not start with the AI model. It starts with the data pipeline.

A powerful forecasting algorithm cannot compensate for missing or unreliable industrial data.

By connecting the physical equipment to a reliable communication and data acquisition layer first, manufacturers can create a stronger foundation for AI-based analytics.

The architecture is therefore not simply:

“AI + Factory”

It is:

“Industrial Devices → Data Infrastructure → SCADA → AI → Predictive Decisions.”

That is the foundation for turning real-time factory data into useful predictive information.

Making AI Vehicle Counting More Reliable in Changing Weather Conditions

Phuc Bach — Sat, 05 Sep 2026 05:59:50 +0000

Why environmental data can be an important context layer for computer vision-based vehicle monitoring

An AI camera can count vehicles continuously and produce stable results for weeks. Then, during a period of heavy rain, the recorded vehicle count suddenly drops.

Is traffic actually lower?

Maybe. But there is another engineering consideration: the conditions under which the camera is collecting visual data have changed.

Outdoor computer vision systems operate in environments where lighting, visibility, rainfall, humidity and other factors can vary significantly. Because vehicle detection relies on image quality, these environmental changes should be considered when evaluating the reliability of the resulting data.

This leads to an interesting approach:

Don't analyze vehicle-counting data independently from its environment.

The Problem with Isolated Vehicle Counts

A conventional traffic-monitoring workflow might look like this:

ONVIF Camera
     ↓
AI Vehicle Detection
     ↓
Vehicle Count
     ↓
Dashboard / Report

This provides a useful operational metric, but the final number contains limited information about the conditions under which it was generated.

Consider a simple example.

A logistics facility normally records approximately 2,000 vehicle movements between 08:00 and 12:00.

One day, the system reports 1,450.

If the dashboard only contains vehicle counts, an operator may conclude that traffic activity has decreased.

However, if heavy rainfall occurred during the same period, environmental conditions become an additional variable worth investigating.

The issue is not that rain automatically makes every vehicle count incorrect.

The issue is that a visual detection system should be evaluated in the context of the environment in which it operates.

Adding an Environmental Context Layer

A more complete architecture can introduce real-time weather information alongside vehicle detection:

                 ┌─────────────────────┐
                 │    ONVIF Camera     │
                 └──────────┬──────────┘
                            ↓
                 ┌─────────────────────┐
                 │ AI Vehicle Detection│
                 └──────────┬──────────┘
                            ↓
                     Vehicle Count
                            │
                            │
                            ▼
                    Data Correlation
                            ▲
                            │
                     Weather Data
                            │
                 ┌──────────┴──────────┐
                 │ Weather Monitoring  │
                 │ Rain / Temp / RH /  │
                 │ Wind / Conditions   │
                 └─────────────────────┘

The important concept here is data correlation, not necessarily direct software integration.

The vehicle detection system produces the counting result.

The weather monitoring system produces environmental observations.

The analytics layer can then associate the two datasets by timestamp, location or monitoring period.

Vehicle Detection + Weather Monitoring

An ONVIF-compatible AI vehicle counting solution can be used to detect and count vehicles from compatible network cameras.

A real-time environmental monitoring system can provide weather-related measurements that help describe the operating environment.

The resulting dataset can conceptually look like this:

Time	Vehicle Count	Rainfall	Environmental Context
08:00	520	0 mm	Normal
09:00	510	0 mm	Normal
10:00	390	Heavy	Review data
11:00	370	Heavy	Review data
12:00	495	Light	Monitor

This does not automatically determine whether the vehicle count is correct or incorrect.

Instead, it gives engineers and operators more information for interpreting the result.

Why This Matters for Data Analytics

Once environmental conditions are associated with traffic data, historical analysis becomes more meaningful.

For example, an analytics system could identify recurring patterns:

Vehicle counts remain stable during normal weather.
Vehicle counts decrease significantly during heavy rainfall.
Detection anomalies repeatedly occur at a specific camera.
Certain monitoring periods require additional validation.
Camera maintenance may be worth investigating after recurring environmental events.

This can be particularly useful when vehicle-counting data becomes an input for other systems.

Examples include:

Traffic analytics

Historical traffic data can be evaluated together with environmental conditions.

Parking management

Operators can distinguish between potentially lower demand and periods affected by unfavorable weather.

Logistics operations

Vehicle movement patterns can be reviewed alongside environmental conditions.

Industrial facilities

Traffic around gates and internal roads can be analyzed with additional operational context.

A Data-Quality Perspective

From an engineering perspective, the biggest benefit is not simply collecting another dataset.

It is improving data observability.

A vehicle-counting value such as:

1,450 vehicles

contains less information than:

1,450 detected vehicles + heavy rainfall + camera ID + timestamp + location

The second record provides additional context for downstream analysis.

This becomes increasingly important when historical data is used for:

Performance reporting
Traffic forecasting
Capacity planning
Parking analysis
Operational optimization
Camera performance investigation

The environmental dataset does not replace the AI detection system.

It complements it.

Designing a More Context-Aware Monitoring System

For organizations deploying outdoor computer vision at scale, a practical architecture can therefore contain three layers:

Layer 1 — Detection

Cameras and AI software generate vehicle detection and counting events.

Layer 2 — Environment

Weather monitoring equipment records environmental conditions in real time.

Layer 3 — Analytics

A SCADA, database or analytics platform correlates both datasets using timestamps and application-specific rules.

This architecture makes it possible to flag periods where environmental conditions may require additional attention during data analysis.

It also creates a foundation for future analytics without requiring the vehicle-counting system itself to be responsible for every environmental variable.

Final Thought

Outdoor AI vision systems do not operate in a vacuum.

The same camera can observe very different conditions throughout a day, and those conditions can become important when evaluating image-based detection results.

That is why a more complete monitoring strategy should consider both:

What did the camera detect?

and

What was happening in the environment when it detected it?

Combining AI vehicle detection with real-time weather information provides a practical way to add this context to outdoor traffic and parking analytics.

Better data is not always about collecting more numbers. Sometimes, it is about understanding the conditions behind the numbers.

📩 If you are planning an outdoor vehicle monitoring project and need to evaluate camera detection together with environmental conditions, contact ATPro to discuss your application, system architecture and RFQ requirements.

Building an Industrial Temperature Monitoring System with RS485 Modbus and SCADA

Phuc Bach — Fri, 04 Sep 2026 07:50:29 +0000

Industrial temperature monitoring often starts with a simple digital display. However, when multiple monitoring points, alarms, historical data, and centralized supervision are required, the system needs to connect field-level devices with SCADA software.

A practical architecture is to combine the AT-TMT-T Industrial Temperature Display with ATSCADA.

Field-Level Temperature Monitoring

The AT-TMT-T provides a clear temperature reading directly at the monitoring location. Operators can see the current value without accessing a computer or SCADA screen.

For applications requiring integration, the device can communicate through RS485 Modbus RTU, allowing temperature data to be transferred to an industrial monitoring system.

👉 Industrial Temperature Display:
https://scada-thai.com/products/at-tmt-t-industrial-led-temperature-display?variant=55271871775011

Connecting the Device to SCADA

The basic communication architecture can be structured as:

Temperature Measurement
↓
AT-TMT-T
↓
RS485 Modbus RTU
↓
ATSCADA
↓
Real-Time Monitoring
↓
Alarm / History / Report

This approach allows the temperature value displayed at the field level to also become part of a centralized monitoring environment.

Centralized Monitoring with ATSCADA

ATSCADA provides the software layer for collecting and visualizing industrial data.

Depending on the application, temperature information can be used for:

Real-time dashboard visualization
High/low threshold monitoring
Alarm management
Historical data storage
Trend analysis
Remote monitoring
Industrial reporting

👉 Factory Monitoring SCADA Software:
https://scada-thai.com/products/atscada-factory-monitoring-software

Why Use Hardware + Software Together?

Using a temperature display alone provides local visibility.

Using SCADA alone without reliable field data does not solve the data acquisition problem.

Combining both creates a complete monitoring workflow:

Field visibility + industrial communication + centralized monitoring

Operators can see the temperature locally, while supervisors can monitor the same information through the SCADA system.

Practical Industrial Applications

This architecture can be considered for:

Manufacturing facilities
Production areas
Warehouses
Equipment rooms
Industrial process monitoring
Temperature-controlled environments

The system can be configured according to the number of monitoring points, communication requirements, temperature range, and required SCADA functions.

The Business Value

The main benefit is not simply displaying temperature data. It is turning field measurements into usable operational information.

With centralized monitoring, teams can identify abnormal temperature conditions faster, review historical trends, and improve visibility across different areas of a facility.

For system integrators and industrial automation teams, this also provides a straightforward architecture for connecting field devices to a SCADA environment.

Conclusion

A temperature monitoring system becomes significantly more useful when field-level measurement is connected to centralized software.

AT-TMT-T + RS485 Modbus RTU + ATSCADA provides a practical architecture for moving from local temperature visualization to centralized industrial monitoring.

📩 Planning a temperature monitoring project?
Share your number of monitoring points, temperature range, communication requirements, and SCADA functions. We can discuss the appropriate configuration and RFQ.

Designing a SCADA Architecture for Real-Time Busbar Temperature Monitoring

Phuc Bach — Thu, 03 Sep 2026 07:23:25 +0000

Electrical panel monitoring is not simply about reading a temperature value. In an industrial environment, the real challenge is collecting field data reliably, processing abnormal conditions, visualizing trends, and making the information available to maintenance teams.

A practical architecture combines busbar temperature monitoring hardware with SCADA software.

The Industrial Monitoring Architecture

A typical architecture can be structured as:

Temperature Sensors → PLC → Gateway → ATSCADA → Dashboard

The field sensors continuously measure busbar temperature. The PLC handles field data processing and control logic, while the gateway provides communication between the field layer and the SCADA system.

At the supervisory layer, ATSCADA collects the data and provides centralized visualization.

The busbar temperature monitoring hardware is designed for monitoring temperature conditions inside electrical panels.

Why Connect Field Data to SCADA?

A local temperature display provides immediate information, but it becomes difficult to manage when a facility has many electrical panels.

SCADA changes the architecture from local observation to centralized monitoring.

With ATSCADA industrial monitoring software, engineers can build monitoring interfaces for:

Real-time temperature values
Alarm conditions
Temperature trends
Historical records
Event monitoring
Reporting
Multiple monitoring locations

This creates a common data layer for electrical-condition monitoring.

From Sensor Data to Actionable Information

The monitoring workflow can be represented as:

1. Measure
Temperature sensors acquire busbar temperature.

2. Collect
The PLC receives and processes field measurements.

3. Communicate
The gateway transfers data to the supervisory system.

4. Visualize
ATSCADA displays current conditions and trends.

5. Alert
Alarm logic identifies abnormal temperature conditions.

6. Analyze
Historical data helps engineers investigate temperature behavior.

This architecture is more useful than simply displaying a number because the data becomes part of the facility's operational workflow.

Example: Multiple Electrical Panels

Consider a manufacturing facility with several distribution panels.

Instead of checking each cabinet individually, the architecture can collect data from multiple monitoring points:

Panel A → Sensors → PLC
Panel B → Sensors → PLC
Panel C → Sensors → PLC

The collected data is then presented through a centralized SCADA interface.

Engineers can quickly identify which panel requires attention and review its temperature history.

Why Historical Data Is Important

A single temperature reading may not reveal much.

A temperature trend can provide significantly more information.

For example, if a monitoring point gradually increases over several days, the maintenance team can investigate the condition before it develops into a larger operational problem.

Historical data can therefore support:

Trend analysis
Maintenance investigation
Event analysis
Equipment comparison
Preventive maintenance planning

Practical Applications

This architecture can be applied to:

Manufacturing plants
Electrical switchgear
MCC panels
Main distribution boards
Industrial electrical rooms
Data centers
Power distribution systems

The number of monitoring points can be scaled according to the electrical infrastructure and project requirements.

Hardware + Software = A Complete Monitoring Solution

The important concept is the separation of responsibilities.

Hardware provides the field data.

PLC/Gateway manages communication and processing.

SCADA provides visualization, alarms, historical data, and reporting.

When these layers work together, temperature monitoring becomes a scalable industrial monitoring system rather than an isolated measurement device.

For facilities where electrical reliability and continuous operation are important, this architecture provides a practical foundation for condition monitoring and preventive maintenance.

Planning a Busbar Monitoring Project?

If you are designing an electrical monitoring system and need to integrate busbar temperature data into a SCADA platform, the system can be configured according to your monitoring points, electrical panels, communication requirements, and application.

Contact ATPro for technical consultation and an RFQ for your industrial monitoring project.

Fire Pump Monitoring Beyond Equipment Status: Adding Environmental Monitoring

Phuc Bach — Mon, 31 Aug 2026 07:41:03 +0000

Fire pump monitoring typically focuses on critical equipment parameters such as pump status, pressure, engine condition, fuel level, and alarms.

But there is another variable that can affect the operating environment of a fire pump system: the temperature and humidity inside the pump room.

For facilities in cold climates, low room temperature can create freezing risks for water-filled components. This makes environmental monitoring a useful addition to conventional fire pump monitoring.

The Monitoring Gap

A fire pump may report normal operating status while the surrounding room is experiencing abnormal environmental conditions.

Without continuous room monitoring, operators may depend on periodic inspections to identify temperature changes. By the time a problem is noticed, the condition may already require immediate attention.

A practical solution is to add an environmental monitoring layer alongside fire pump monitoring.

A Two-Layer Monitoring Approach

The first layer focuses on the fire pump system itself.

ATSCADA Fire Pump Monitoring Software provides centralized monitoring of fire pump operating conditions and key parameters.

The second layer focuses on the environment.

The Industrial Temperature & Humidity Sensor can continuously monitor temperature and humidity inside the pump room.

This creates a broader monitoring view:

Fire Pump → Equipment Status → Alarms → Environmental Conditions

Instead of looking only at whether the pump is operating, facility teams can also monitor the conditions surrounding the equipment.

Key Benefits

1. Early Detection of Abnormal Temperature

Continuous temperature measurement helps operators identify unusual temperature changes before they become a larger operational concern.

2. Continuous Pump Room Monitoring

Environmental conditions can be monitored continuously rather than relying entirely on periodic manual inspections.

3. Historical Data for Maintenance

Recorded temperature and humidity data can provide useful information for maintenance analysis and investigation of abnormal conditions.

4. Centralized SCADA Visibility

Environmental data can complement existing fire pump monitoring, giving operators a more complete view of the pump room.

5. Better Operational Awareness

Monitoring both equipment and environmental conditions helps facility teams understand the overall operating condition of the fire pump room.

Where Can This Approach Be Used?

This monitoring concept is suitable for:

Industrial factories
Commercial buildings
Manufacturing facilities
Critical infrastructure
Facilities with dedicated fire pump rooms
Sites requiring remote equipment and environmental monitoring

It is particularly relevant where seasonal or low temperatures may affect the pump room environment.

From Fire Pump Monitoring to Environmental Awareness

Reliable fire protection monitoring should not necessarily stop at equipment status.

By combining fire pump system monitoring with pump room temperature and humidity monitoring, facility operators can gain additional visibility into the conditions surrounding critical fire protection equipment.

The concept is straightforward:

Monitor the pump. Monitor the room. Improve system readiness.

For projects requiring fire pump monitoring, environmental sensing, SCADA integration, or customized monitoring solutions, contact us to discuss your application and technical requirements.