Connecting PLC information to operational systems

Making Sense of Time in PLC and SCADA Event Records

Plan event timestamps and time conventions so PLC and SCADA records can be interpreted when investigating an operating event.

A hard-hat operator seated at a control-room desk
Illustrative photo.

When two logs show different times, it is tempting to assume one system is wrong. First establish what each timestamp represents. A value recorded when an event occurs is different from one recorded when another system receives it.

Define the meaning of each time field

Identify whether a record uses a source event time, receipt time or another documented convention. Ask the suppliers what the chosen configuration can provide. Keep unsupported requirements visible instead of assuming all devices timestamp events in the same way.

Agree the display convention

Document the timezone and formatting used in operator displays and exports. If records will be compared across locations or systems, explain how that comparison should be made. Avoid leaving an unlabeled local time for a later analyst to interpret.

Consider communication interruptions

Ask how delayed or buffered information will appear after a connection returns. Define what the record can and cannot establish about event order. Have the integration team assess the actual behaviour in the agreed test conditions.

Preserve the explanation with the data

Keep the timestamp definitions alongside the interface documentation. Our PLC information integration overview connects this detail with tag quality and acceptance planning.

Frequently asked questions

Why can event time differ from SCADA receipt time?

The event and its arrival at another system are different moments, particularly when communication is delayed or interrupted.

What should a timestamp description include?

Explain the event represented, the source of the time and the timezone or display convention needed to interpret it.

Can a log always prove the exact order of process events?

Its usefulness depends on timestamp meaning, resolution and system behaviour. Establish those limits before drawing conclusions.