Understanding effective and expiration date calculations for design consumption - HxGN EAM - 12.0.1 - Help - Hexagon

When entering multiple design consumption records on the Design Consumption page of the Assets, Positions, or Systems forms, the Commodity specified for a record is tied to a Date Effective and Date Expired. This association establishes the valid date ranges for the energy efficiency specifications established for the Commodity. By necessity, these date ranges must be flexible in the ways in which they connect the equipment and the Commodities to which they are linked. Therefore, if you must specify multiple design consumption records on the Design Consumption page for same Commodity, the system must calculate the date ranges for Date Effective and Date Expired based on the existing record(s) and the Date Effective specified for an additional record when there is an overlap between the Date Effective of the existing record and the Date Effective of the additional record(s). Likewise, the same is true for the expiration dates of the existing and additional records. See the following examples for more information.

Example 1

In this example, there are two existing design consumption records, and you are inserting a new record. At the time of insert, the date information for the design consumption records is as follows:

Date Expired is protected. The system defaults 12/31/2199 as the Date Expired for the record to be inserted.

The record to be inserted shares the same Commodity as the existing records, and the Date Effective of the record to be inserted overlaps with the Date Effective and Date Expired of the existing records. The system locates the existing record with the same Commodity based on the Date Effective and updates the Date Expired for the second existing record with a new Date Effective as follows:

Example 2

In this example, there are two existing design consumption records, and you are inserting a new record. At the time of insert, the date information for the design consumption records is as follows:

Date Expired is protected. The system defaults 12/31/2199 as the Date Expired for the record to be inserted.

The record to be inserted shares the same Commodity as the existing records, and the Date Effective of the record to be inserted overlaps with the Date Effective of the existing records. The system locates the existing record with the same Commodity based on the Date Effective and updates the Date Expired of existing record one and the Date Effective of existing record two and the data inserted is as follows: