Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

Merge an event with an adjacent event

  • Last UpdatedNov 01, 2024
  • 2 minute read

If you determine that an event is actually a continuation of the event before or after it, you can merge the two events by making their utilization reasons match.

Merge an event with an adjacent event

  • In the Edit Event side sheet, select the reason that matches the next or previous event. The events will be merged when the event is saved. The duration of the merged event will equal the duration of the two source events, as shown in the following diagram.

    A flow diagram showing the result of merging adjacent events on the duration and classification of the resulting event.

    If the system is configured so that the comments of the events must be the same to enable the merge to occur, you must edit an event's comment so that it matches the comment of the other event prior to merging events. Note that you must apply any new comments after merging the events.

    If the system is configured so that the raw reason codes of the events being merged must match to allow the merge to occur, you can edit an event's reason code so that it matches the reason code of the other event prior to merging events.

    For a complete explanation of the restrictions regarding when events can be merged, see Merging Events.

    Note: Merging events with the same reasons, comments, and raw reason codes means that if a utilization reason is split, and nothing about it is changed, the new event will automatically be merged with the event from which it was split when saved and it will appear as if the split did not happen. To avoid this, when splitting the event, you should change the reason (or possibly the comments) of the new event before saving it.

Related Links
TitleResults for “How to create a CRG?”Also Available in