Considerations after Customizing a File's Sequence Key Order/Values.

Products

• MICS Resource Management

Issue/Introduction

Considerations after Customizing a File's Sequence Key Order/Values.

 

Resolution

Because summarization based on sequence keys is used to create the higher-than-detail time span files, some data element values in the cycles of these files existing prior to the sequence key change, may not reflect the new changes. This will be true in spite of the fact that a valid retrofit job has been run against these cycles.

For example, if HOUR is an element in the DAYS time span but not a sequence element, the value will be treated as a retained element when summarized. If HOUR is added as a sequence field, some HOUR values will not be correct because the data has already been summarized across the HOUR prior to the sequence change. Hence, the analyst using these file cycles must consider the impact of this situation in his analytical work. Such consideration will prevent obtaining invalid results.

As regards to the to-date files (cycle 00) corresponding to the day when the sequence change is made, these will contain both observations correctly reflecting the new changes and some that may not. This too must be considered.