Search

Scope: Core (OPC-10000-*) All specs

14 result(s) for Time

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.13.1.1 Overview

EventType that will be contained in the Event such as EventId , EventType , SourceNode , Time and Description . OPC 10000-3 describes the Event model and the base EventTypes . The Properties
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.2 BaseEventType

HasProperty Variable SourceNode NodeId PropertyType Mandatory HasProperty Variable SourceName String PropertyType Mandatory HasProperty Variable Time UtcTime PropertyType Mandatory HasProperty Variable ReceiveTime UtcTime PropertyType Mandatory HasProperty Variable LocalTime TimeZoneDataType PropertyType Optional ... server, if the Event is specific to a Node, or some server-specific notation. Time provides the time the Event occurred. This value is set as close to the event
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.3 AuditEventType

using an EventFilter consisting of Event fields from the core AuditEventTypes . ActionTimeStamp identifies the time the user initiated the action that resulted in the AuditEvent being generated. It differs from ... Time Property because this is the time the server generated the AuditEvent documenting the action. Status identifies whether the requested action could be performed (set Status to TRUE
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.3 Condition and branch instances

Condition and branch instances Conditions are Objects which have a state which changes over time. Each Condition instance has a ConditionId as an identifier which uniquely identifies it within ... once a Condition is created in a system that does not expose instances, any time that Condition is active it shall always have the same ConditionId . This allows higher level
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.4.3 HistoricalEventConfigurationType

When it is present it shall include at least the event fields Time , SourceName and Severity of the BaseEventType Type defined
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.2.2 Insert data functionality

entries at the specified timestamps, e.g., the insertion of lab data to reflect the time of data collection. If the Time does not fall within range that can be stored
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.2.4 Update data functionality

should use Good_EntryInserted or Good_EntryReplaced to return that information. If the Time does not fall within range that can be stored then the related operationResults entry shall indicate
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.3.3 Insert functionality

already exists at the specified parameters the StatusCode shall indicate Bad_EntryExists . If the Time does not fall within range that can be stored then the related operationResults entry shall
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.3.5 Update functionality

replaced or inserted an entry then the StatusCode shall be Good. If the Time does not fall within range that can be stored then the related operationResults entry shall indicate
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.4.2 Insert event functionality

empty. The selectClause shall, as a minimum, provide the following Event fields: EventType, and Time . It is also recommended that the SourceNode and the SourceName fields are provided ... source for Events then the related operationResults entry shall indicate Bad_SourceNodeIdInvalid. If the Time does not fall within a range that can be stored then the related operationResults entry
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.2 LogRecord EventType Mapping

LogEntryConditionClass . The following describes fields in BaseEventType that are mapped to a LogRecord : Time - the time associated with this event. EventType - as defined in BaseEventType in OPC 10000-5 SourceNode
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.4.1 Overview

Components , include industrial automation applications, Remote Management , and other applications or services such as Time Synchronisation or Topology Discovery . IA-station functions can reside in a single or multiple
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.4.2.1 Overview

gPTP as defined in IEEE Std 802.1AS‑2020 for the time synchronisation of UAFX Stations . Figure 19 illustrates an exemplary time-synchronised network with two gPTP domains ... UAFX Station 3. UAFX Station 2 and IA-station support the forwarding of corrected time information in both gPTP domains via PTP Relay Instances (see 7.4.2.1.2 ). NOTE The extent
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.4.2.1.1 gPTP domains

domain. UAFX supports the following two types of gPTP domains: Working Clock domain Global Time domain Working Clock domain maintains a common sense of time for use cases such ... enhancements for scheduled traffic (see IEEE Std 802.1Q ). Global Time domain (e.g. wall clock) maintains a common sense of time across an industrial automation network for use cases such