Power & Energy Solutions
Wide Area Movement Control Center (WAMCC)
Time Synchronization Solutions for Control Centers, Data Centers, and Telecommunications Rooms
Ensures that dispatch automation systems, servers, network equipment, communication systems, and security logs all share the same time reference. Designed for power dispatch centers, centralized control centers, data centers, and disaster recovery centers at all levels.
Scenario Pain Points
When five different systems record the same power grid event but their timestamps differ, there is no common framework for cross-system alarm prioritization, fault localization, and security forensics. Data center time synchronization serves as a unified time infrastructure that spans business systems, IT facilities, communication networks, and security platforms.
1. Time discrepancy between the SCADA/EMS front-end server and the database
Performance:There is a deviation of a few seconds between the data collection time at the front-end server and the write time to the historical database, causing the order of critical alerts to be scrambled when querying alerts sorted by time.
Solution: The front-end server, real-time database, and historical database all obtain NTP from the same master clock, ensuring that the order of alerts reflects the actual physical sequence.
2. Time discrepancies between servers in different security zones
Performance:The EMS server in Zone I, the electricity energy server in Zone II, and the management server in Zone III are each synchronized to a different time source, resulting in a difference of several seconds in the physical time of cross-zone data snapshots.
Solution: Establish a standardized hierarchical architecture, with each zone obtaining time from the same source via hierarchical NTP, thereby providing a foundation for consistency in cross-zone data correlation.
1. Time discrepancy between the SCADA/EMS front-end server and the database
Performance:There is a deviation of a few seconds between the data collection time at the front-end server and the write time to the historical database, causing the order of critical alerts to be scrambled when querying alerts sorted by time.
Solution: The front-end server, real-time database, and historical database all obtain NTP from the same master clock, ensuring that the order of alerts reflects the actual physical sequence.
2. Time discrepancies between servers in different security zones
Performance:The EMS server in Zone I, the electricity energy server in Zone II, and the management server in Zone III are each synchronized to a different time source, resulting in a difference of several seconds in the physical time of cross-zone data snapshots.
Solution: Establish a standardized hierarchical architecture, with each zone obtaining time from the same source via hierarchical NTP, thereby providing a foundation for consistency in cross-zone data correlation.
3. Security devices operate on different schedules, making it difficult to reconstruct the attack chain
Performance:The timestamps in the logs from the firewall, intrusion detection system, and bastion host are out of sync, making it impossible to reconstruct the complete attack path and resulting in non-compliance with the Grade 3 Security Protection Standards.
Solution: All security devices and log auditing platforms are synchronized, enabling the precise reconstruction of attack chains and operational activity trails.
4. Time Discrepancy Between the Telecommunications Network Management System and Transmission Equipment
Performance:The times of SDH equipment optical port alarms do not match the times they are received by the network management system or the times of SCADA channel anomalies, leading to cross-departmental finger-pointing and buck-passing.
Solution: Communications and IT equipment share a common time source, and alarms are based on a unified timeline, significantly improving the efficiency of cross-disciplinary fault localization.
3. Security devices operate on different schedules, making it difficult to reconstruct the attack chain
Performance:The timestamps in the logs from the firewall, intrusion detection system, and bastion host are out of sync, making it impossible to reconstruct the complete attack path and resulting in non-compliance with the Grade 3 Security Protection Standards.
Solution: All security devices and log auditing platforms are synchronized, enabling the precise reconstruction of attack chains and operational activity trails.
4. Time Discrepancy Between the Telecommunications Network Management System and Transmission Equipment
Performance:The times of SDH equipment optical port alarms do not match the times they are received by the network management system or the times of SCADA channel anomalies, leading to cross-departmental finger-pointing and buck-passing.
Solution: Communications and IT equipment share a common time source, and alarms are based on a unified timeline, significantly improving the efficiency of cross-disciplinary fault localization.
5. The lack of a unified timeline for disaster recovery failover across multiple data centers
Performance:The main data center and the off-site disaster recovery center use different time sources, resulting in inaccurate calculations of the time of failure and the time of switchover during disaster recovery drills.
Solution: Multiple data centers are synchronized to the Beidou system or via hierarchical synchronization over dedicated links, ensuring a unified time base for disaster recovery failover.
6. Time discrepancy between the SCADA/EMS front-end server and the database
Performance:Some servers refer to domain controllers, some to firewalls, and some to the public internet, forming a “spider web”-like hierarchy that poses significant risks of deviation.
Solution: Redesign the standard architecture for the master clock, core NTP, zone NTP, and end devices so that it does not rely on the public internet or the local clock.
5. The lack of a unified timeline for disaster recovery failover across multiple data centers
Performance:The main data center and the off-site disaster recovery center use different time sources, resulting in inaccurate calculations of the time of failure and the time of switchover during disaster recovery drills.
Solution: Multiple data centers are synchronized to the Beidou system or via hierarchical synchronization over dedicated links, ensuring a unified time base for disaster recovery failover.
6. Time discrepancy between the SCADA/EMS front-end server and the database
Performance:Some servers refer to domain controllers, some to firewalls, and some to the public internet, forming a “spider web”-like hierarchy that poses significant risks of deviation.
Solution: Redesign the standard architecture for the master clock, core NTP, zone NTP, and end devices so that it does not rely on the public internet or the local clock.
Typical Systems and Data Center Assets
Dispatch Automation Domain
Data Center Domain
Telecommunications Room Area
Data Center-Level Operations Dashboard
The time synchronization system should be a "permanent metric" on the operations dashboard—visible in real time, with alerts triggered immediately upon any anomaly.
Dispatch Automation Domain
SCADA, EMS, front-end servers, and real-time libraries sort alarms based on the same time reference.
Data Center Domain
Servers, databases, virtualization platforms, and security devices are connected according to the partitioned NTP hierarchy.
Telecommunications Room Area
SDH, PTN, OTN, BITS/SSU: Focus on bit pulses, timing information, and frequency references.
Security and Audit Domain
Fortinet devices, log auditing, and threat intelligence must maintain a time-stamp correlation with the production region.
Primary and Backup Time Sources
Centralized management of primary and backup clocks, BeiDou lock, local time-keeping, and port output status.
Disaster Recovery Link
The main data center, the local backup data center, and the off-site disaster recovery center maintain the same time zone via dedicated lines or independent time sources.
Recommended Overall Architecture
A four-tier architecture design covering IT infrastructure, communication networks, and multiple security zones
End-to-End Monitoring and Alerting Chain
SNMP/Syslog Upload for Data Center Monitoring:
- GNSS Antenna Status
- Number of Satellites Locked On
- Current Time Source
- Switching Between Primary and Backup Roles
- On-Time Status/Out of Tolerance
- NTP Service Status
- PTP/Frequency Output Status
Partitioning and Hierarchical Timing Design
Recommended Time Synchronization Methods and Interface Matrix
NTP / SNTP
It covers SCADA systems, databases, servers, network devices, security devices, and communications network management systems, providing network time synchronization at the millisecond level.
PTP 1588v2
Designed for high-precision data acquisition, core switches, and front-end servers, it provides sub-microsecond network clock capability.
1PPS + TOD
Provides second pulses and absolute time information for SDH/PTN, BITS/SSU, and communications equipment.
10 MHz / E1
Provides a stable frequency reference for transmission equipment and frequency synchronization equipment, reducing the risk of code slippage and bit errors.
IRIG-B / Serial Port
Used for small-scale telecommunications gateways, legacy equipment, or high-precision reference scenarios; it complements NTP/PTP.
SYSLOG / SNMP
Include primary-standby switching, timing deviation, port output, and NTP service anomalies in data center operations and maintenance monitoring.
Value of the Solution
The alarm sequence is accurate and clear
SCADA, the database, and the dispatch workstation are synchronized, ensuring that alarm sequencing reflects the actual physical chronology and preventing misleading dispatch decisions.
Improved Efficiency in Fault Diagnosis
With consistent timestamps in network device logs and time synchronization between the communication network management system and transmission equipment, a common framework has been established for cross-disciplinary joint fault diagnosis.
Cross-region data analysis is reliable
Data snapshots from servers in different security zones are precisely synchronized over time, providing a solid foundation for comprehensive reporting and cross-zone business analysis.
Multi-Data-Center Disaster Recovery Has a Solid Foundation
During disaster recovery switchover drills, the timing of the failure and the switchover can be precisely calculated, and the timing of off-site data synchronization can be precisely defined.
Security, Audit, Compliance, Availability
Firewalls, bastion hosts, and log auditing platforms operate in unison, enabling precise reconstruction of attack chains and meeting the audit requirements of the Grade 2.0 Information Security Certification.
Eliminating NTP-Level Risks
Unify the hierarchical architecture of the planning system, eliminate time drift caused by public network time synchronization and the local clock, and transform the time source from a "wild" state into a "controlled system."
Primary-Standby Redundancy, BeiDou Priority, and Local Time Keeping
Data centers and dispatch centers are the cornerstone of 24/7 continuous operation; the time synchronization system itself must never become a single point of failure in the infrastructure.
1+1 Primary-Standby Redundancy: Deploy primary clocks A and B, with dual-power-supply and dual-antenna redundancy, and multiple network ports operating independently according to security zones. Primary and backup systems continuously monitor each other, and failover occurs automatically and seamlessly in the event of a failure.
Beidou: Independent and Under Chinese Control: Beidou serves as the primary time source, eliminating reliance on external, uncontrollable factors. Configurable multi-mode reception across the entire constellation enhances availability.
Local Time Accuracy Guarantee: In the event of an unexpected loss of satellite signals, the built-in rubidium clock or OCXO maintains the continuous output of NTP/PTP and frequency signals, ensuring that the database timestamps and communication network management logs remain uninterrupted during this period.
Implementation and Delivery Process
What we deliver is not just a piece of equipment, but a time infrastructure that can be tested, accepted, and maintained.
Data Center Deployment
Verify the primary and backup time sources, antennas, racks, power supplies, network, and time-frequency interface conditions.
Three-Domain Access
Connect to the dispatch automation, data center, and communications room equipment, respectively, and implement a unified policy structure.
Output Verification
Verify the output capabilities and deviations of NTP/PTP, 1PPS+TOD, 10 MHz, E1, and other signals.
Disaster Recovery Synchronization
Verify time synchronization among the primary and secondary data centers, the same-city backup data center, and the off-site disaster recovery center.
Alarm Integration
Integrate primary/standby configurations, time synchronization, NTP services, frequency output, and port anomalies into the operations and maintenance platform.
Frequently Asked Questions
How should we choose between NTP and PTP for the dispatch center?
NTP (millisecond-level) is suitable for SCADA/EMS backends, database servers, network devices, and security devices—systems for which millisecond-level time accuracy is sufficient. PTP (nanosecond to microsecond level) is suitable for scenarios requiring high-precision time synchronization, such as the transmission of sample values in digital substations and PMU data synchronization in Wide Area Measurement Systems (WAMS). In dispatch centers, NTP is typically used as the primary protocol for hierarchical distribution, while PTP Grandmasters are deployed at core nodes requiring high precision. Both protocols can coexist within the same time synchronization infrastructure.
How is time synchronization achieved between the multiple security zones in the dispatch center?
Power dispatch centers are typically divided into Security Zone I (real-time control), Zone II (non-real-time monitoring), and Zone III (management information). There is physical isolation between each zone (using forward and reverse isolation devices). Time synchronization generally employs a “centralized source + zone-based relay” approach: after uniformly acquiring the BeiDou/GNSS time reference at the master clock level, independent secondary NTP time servers are deployed within each security zone to obtain time from the master clock via isolation devices. This approach satisfies the isolation requirements for security zones while ensuring the consistency of the time reference across the entire center.
What is the relationship between 10 MHz and E1 frequency synchronization in a telecommunications equipment room and NTP time synchronization?
10 MHz and E1 provide frequency synchronization (ensuring that devices “run at the same speed”), while NTP and 1PPS+TOD provide time synchronization (ensuring that devices “know the current time”). In communications transmission, SDH/PTN/OTN equipment uses 10 MHz or E1 to achieve frequency locking of the network clock, preventing frame slippage and bit errors; meanwhile, NTP or 1PPS+TOD provide absolute timestamps for the network management systems and alarm logs of communications equipment. The two are complementary and work together to ensure the reliable operation of communication networks.
How does the dispatch center verify that the time synchronization system is operating properly?
Use the online time synchronization monitoring platform to continuously collect data on the primary and backup clocks, including GNSS status, number of locked satellites, time-keeping status, NTP/PTP service status, port output status, and power status. Set thresholds for anomaly alerts (e.g., an alert for NTP deviation > 10 ms, or an alert for GNSS loss of lock > 30 min). Conduct periodic (e.g., quarterly) spot checks of time accuracy at critical nodes. In multi-data-center scenarios, it is also necessary to monitor time deviations across data centers and the time status following a disaster recovery switchover.
简体中文 
English