Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

[Contents][Glossary][Index][Back][Next]

3.4.2 Example of consolidation processing of repeated events

The following figure shows an example of consolidation processing of repeated events.

Figure 3-28 Consolidation processing of repeated events

[Figure]

The flow of processing described below, following the numbers in the figure:

  1. JP1/IM - View receives JP1 event A1 and begins consolidation. JP1 event A1 becomes a consolidation start event.
    Information about consolidation start event A1 appears in the Event Console window.
  2. JP1/IM - View receives JP1 event A2 and compares its contents with the consolidation start event A1. Because A2 and A1 have identical contents, JP1 event A2 is judged to be a repeated event and is aggregated into A1.
    Information about consolidation start event A1 and the repeat count (2) appears as A1[2] in the Event Console window.
  3. JP1/IM - View receives JP1 event A3 and compares its contents with the consolidation start event A1. Because A3 and A1 have identical contents, JP1 event A3 is judged to be a repeated event and is aggregated into A1.
    Information about consolidation start event A1 and the repeat count (3) appears as A1[3] in the Event Console window.
  4. JP1/IM - View receives JP1 event B1 and compares its contents with the consolidation start event A1. Because B1 and A1 do not have identical contents, aggregation into consolidation start event A1 ends and aggregation into JP1 event B1 begins. Thus, B1 becomes the current consolidation start event.
    Information about B1 and the previous consolidation event A1 appears in the Event Console window.
  5. JP1/IM - View receives JP1 event B2 and compares its contents with the consolidation start event B1. Because B2 and B1 have identical contents, JP1 event B2 is judged to be a repeated event and is aggregated into B1.
    Information about B1 and its repeat count (2), and about the previous consolidation event A1, appears in the Event Console window. (The former appears as B1[2].)
  6. JP1/IM - View receives JP1 event A4 and compares its contents with the consolidation start event B1. Because A4 and B1 do not have identical contents, aggregation into consolidation start event B1 ends and aggregation into JP1 event A4 begins. Aggregation into the earlier consolidation start event A1 has already ended; therefore JP1 event A4 cannot be aggregated into A1. Thus, A4 becomes the new consolidation start event.
    Information about the earlier event A1, previous event B1, and current consolidation event A4 appears in the Event Console window.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.