Time Synchronization in Industrial Automation: Emerson Ovation and Foxboro NTP and PTP Setup

Why Every Plant Needs One Truth About Time?

Every controller, historian, and safety system stamps events with its own clock. If those clocks disagree, your event records lie. A trip investigation then reads like a shuffled deck. Engineers waste days arguing about which record is correct. First, accept the core principle. A plant needs one trusted time source. Second, choose a protocol that matches your accuracy needs. I maintain an Emerson Ovation network and a Foxboro I/A Series island at the same site. Both now take time from one GPS-disciplined source. Getting there taught me every lesson below.

What are the Differences in Accuracy Between NTP, SNTP, and PTP?

NTP is the workhorse of plant networks. A master server holds reference time. Clients poll it at regular intervals over Ethernet using port 123. NTP compensates for network delay, reaching about 10 ms accuracy on a healthy LAN. SNTP is the simplified version. It skips delay calculations and just accepts the delivered time. Accuracy drops to about 50 ms. PTP, defined by IEEE 1588, beats both. The grandmaster pushes timestamps to slaves continuously. Slaves correct offset in real time. However, PTP needs capable switches and NICs with hardware timestamping to reach its potential.

• Step 1 — Classify your systems by need. Operator displays and historians accept NTP at 10 ms.
• Step 2 — Use PTP where sequence-of-events recording demands sub-millisecond resolution.
• Step 3 — Reserve SNTP for simple devices that only need approximate time, such as standalone HMIs.

How to Build the GPS-Referenced Master Time Source?

Internet time servers have no place in a control network. They open outbound paths that security policies should block. A GPS time server solves this. It receives UTC from satellites and serves time entirely inside the plant network. Moreover, it removes dependency on corporate IT infrastructure. My site uses a dual-antenna GPS clock feeding two redundant NTP servers. Both the Ovation drop network and the Foxboro node take time from it.

• Step 1 — Install the GPS antenna with a clear sky view. Keep the antenna cable run within vendor limits.
• Step 2 — Assign the time server a static IP in the control network, on stratum 1, isolated from plant IT.
• Step 3 — Configure a second server as backup. Clients must fail over without operator action.
• Step 4 — Lock the UTC offset and daylight saving rules in the server, not in each client.

How to Configure Ovation and Foxboro as NTP Clients?

The Emerson Ovation controller takes time configuration through its network settings. Point each controller at the GPS server pair. Verify the offset after one hour of settling. The Foxboro I/A Series station works the same way through its time service. Therefore, always configure clients, never let controllers free-run. A free-running controller drifts seconds per week. That drift quietly corrupts every alarm timestamp it stamps. During one investigation, we found a Foxboro station 4 seconds ahead of the Ovation system. The event sequence looked impossible until we checked clock offset.

• Step 1 — Configure both primary and secondary NTP server addresses on every controller and station.
• Step 2 — Set the polling interval between 64 and 1024 seconds per the NTP specification.
• Step 3 — Log in to each controller and record its reported offset. Anything above 100 ms needs attention.
• Step 4 — Reboot or restart the time service after configuration changes, then recheck offsets.

Why PTP Needs Hardware to Deliver on Its Promise?

PTP promises sub-microsecond accuracy. Software-only implementations deliver far less. The grandmaster and every boundary switch must support hardware timestamping. Otherwise, software jitter swamps the correction field. However, the payoff justifies the cost for turbine controls and high-speed sequence recording. My site reserves PTP for the rotating equipment train. Everything else runs NTP.

• Step 1 — Select switches that support IEEE 1588 transparent clock or boundary clock mode.
• Step 2 — Configure exactly one grandmaster. All other PTP devices must be slave-capable only.
• Step 3 — Measure the final offset with a PTP monitoring tool. Target under 1 microsecond on the local segment.

Conclusion & Action Advice

Time synchronization is cheap insurance for incident analysis. First, install a GPS time server inside the control network. Second, configure every Ovation and Foxboro node as an NTP client with a defined backup. Moreover, reserve PTP for the applications that truly need sub-millisecond resolution, and buy the hardware to support it. Therefore, add a clock-offset check to your monthly routine, and archive the readings. Finally, before your next trip investigation starts, verify that all clocks agree. One trusted time source turns a shuffled event log into a clear narrative, and it costs less than a day of engineering time per year.

Author: Wu Jianming is an industrial automation engineer with over 10 years of experience in PLC, DCS, and control systems.