Factory Digitalization Ver15. _ Structural Barriers in On Premises Factory Data Visualization and Practical Solutions
- Shigenori Tanaka
- 7月8日
- 読了時間: 3分
Jul 08, 2026
Thank you for reading.
This article summarizes three unavoidable challenges encountered when visualizing factory data in an on‑premises environment—time drift, UI limitations, and lack of external visibility—along with the actual issues observed on the shop floor and practical countermeasures.
■ Introduction: On‑Premises Is Not “Safe Because It’s Closed,” but “Difficult Because It’s Closed”
In manufacturing sites, on‑premises data visualization systems are still widely used. However, unlike cloud systems, on‑premises environments are closed networks, which creates unique challenges in how data is handled, how time is managed, and how external access is provided. This article explains these fundamental issues and their solutions step by step.
■ Challenge 1: Time Drift Causes Integrated Manufacturing Data to Break Down
● Overview of the Problem
In an on‑premises environment, data loggers, PLCs, and PCs are not connected to the internet, meaning each device maintains its own internal clock. As a result, the following issues arise:
The logger’s timestamp drifts from actual time
PLCs and PCs each have different internal times
Time series alignment collapses during data integration, making analysis impossible
Manufacturing data requires a correct time axis. Once this collapses, improvement activities cannot be executed properly.
● Countermeasure: Make the Logger the “Master Clock”
Install time‑correction software on the logger to adjust its internal clock
Standardize timestamps to “the time the logger collected the data”
Do not use PLC or PC internal time
This ensures consistent time series data even in an on‑premises environment.
■ Challenge 2: Limited Flexibility of Logger‑Integrated Visualization UI
● Overview of the Problem
In many factories, the data logger serves both as a database and as a simple visualization tool. This architecture has the following limitations:
Widgets cannot be freely edited
Graph types and layouts are fixed
Visualization cannot be flexibly adapted to shop‑floor improvement needs
In other words, “You can visualize data, but you cannot use the visualization effectively.”
● Countermeasure: Install an Application Server Between the Logger and Client PCs
Logger: dedicated to data collection and time unification
Application server: provides data processing, APIs, and flexible visualization UI
Client PC: freely edits graphs via browser
This enables cloud‑level flexibility even in an on‑premises environment.
■ Challenge 3: Loggers Cannot Be Viewed Externally, Preventing Managers from Monitoring Factory Status
● Overview of the Problem
Because the logger is isolated inside the factory LAN, managers cannot check the factory status from:
Hotels
Home
Business trips
There is no way to confirm whether equipment has stopped or abnormalities have occurred, increasing the burden on factory management.
■ Two Options for Enabling External Visualization
This is the core topic of this article.
① Recommended: Dock a Mirror Server to the Logger and Connect via VPN
A mirror server is not merely a data replication device—it also functions as an external‑access application server.
● Architecture
Logger → Mirror server (data synchronization)
Mirror server → VPN → External PC
Flexible visualization UI provided on the mirror server
● Advantages
Logger is not exposed externally → safer
Logger load does not increase
UI can be freely customized
Works even if the logger is old
Stable external visualization
● Summary
This architecture offers the best balance of safety, flexibility, and scalability, and is widely adopted in real manufacturing environments.
② Not Recommended: Connect Directly to the Logger via VPN
● Disadvantages
Exposes the logger externally → high security risk
UI remains limited
Logger load increases
Impossible if the logger does not support external access
If the logger fails, external visualization also stops
● Summary
Although simple, this architecture is rarely adopted in manufacturing sites.
■ Conclusion
The core challenges of on‑premises factory data visualization are:
Time drift causing data breakdown
Limited flexibility of logger‑integrated UI
Logger not visible externally, preventing remote monitoring
To solve these issues, the most practical architecture is:
Logger time correction
Unified timestamps
Application server installation
Mirror server + VPN for external visualization
This enables cloud‑level flexibility and safety even in an on‑premises environment.
■ Contact
We can tailor the concepts in this article to your factory environment and propose concrete system architectures. If needed, we can also prepare mirror‑server diagrams, network diagrams, and implementation steps. Please feel free to reach out.
TAGS
コメント