The HistoryUpdate Servicedefined in OPC 10000-4can perform several different functions. The historyUpdateDetailsparameter is an Extensible Parameterthat specifies which function to perform and the details that are specific to that function. See OPC 10000-4for the definition of Extensible Parameter. Table 31lists the symbolic names of the valid Extensible Parameterstructures. Some structures will perform different functions based on the setting of its associated parameters. For simplicity a functionality of each structure is listed. For example text such as ‘using the Replace data functionality’ refers to the function the HistoryUpdate Serviceperforms using the Extensible Parameterstructure UpdateDataDetailswith the performInsertReplace enumeration parameter set to REPLACE_2.
Table 31– HistoryUpdateDetails parameter TypeIds
Symbolic Name |
Functionality |
Description |
UpdateDataDetails |
Insert data |
This function inserts new values into the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateDataDetails |
Replace data |
This function replaces existing values into the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateDataDetails |
Update data |
This function inserts or replaces values into the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateStructureDataDetails |
Insert data |
This function inserts new Structured History Dataor Annotationsinto the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateStructureDataDetails |
Replace data |
This function replaces existing Structured History Dataor Annotationsinto the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateStructureDataDetails |
Update data |
This function inserts or replaces Structured History Dataor Annotationsinto the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateStructureDataDetails |
Remove data |
This function removes Structured History Dataor Annotationsfrom the history database at the specified timestamps for one or more HistoricalDataNodes. The Variable’s value is represented by a composite value defined by the DataValuedata type. |
UpdateEventDetails |
Insert events |
This function inserts new Eventsinto the history database for one or more HistoricalEventNodes. |
UpdateEventDetails |
Replace events |
This function replaces values of fields in existing Eventsinto the history database for one or more HistoricalEventNodes. |
UpdateEventDetails |
Update events |
This function inserts new Eventsor replaces existing Eventsin the history database for one or more HistoricalEventNodes. |
DeleteRawModifiedDetails |
Delete raw |
This function deletes all values from the history database for the specified time domain for one or more HistoricalDataNodes. |
DeleteRawModifiedDetails |
Delete modified |
Some historians may store multiple values at the same Timestamp. This function will delete specified values and qualities for the specified timestamp for one or more HistoricalDataNodes. |
DeleteAtTimeDetails |
Delete at time |
This function deletes all values in the history database for the specified timestamps for one or more HistoricalDataNodes. |
DeleteEventDetails |
Delete event |
This function deletes Eventsfrom the history database for the specified filter for one or more HistoricalEventNodes. |
The HistoryUpdate Serviceis used to update or delete, DataValues, Annotationsor Events. For simplicity the term “entry” will be used to mean either DataValue, Annotation,or Eventdepending on the context in which it is used. Auditing requirements for History Servicesare described in OPC 10000-4. This description assumes the user issuing the request and the Serverthat is processing the request support the capability to update entries. See OPC 10000-3for a description of Attributesthat expose the support of Historical Updates.
If the HistoryUpdate Serviceis called with two or more of DataValues, Eventsor Annotationsin the same call the Serveroperational limits MaxNodesPerHistoryUpdateDataandMaxNodesPerHistoryUpdateEvents(See OPC 10000-5) may be ignored. The Servermay return the service result code Bad_TooManyOperationsif it is not able to handle the combination of DataValues, Events or Annotations. It is recommended to call the HistoryUpdate Serviceindividually with DataValues, EventsorAnnotations.