Template:Iterations rga

Iterations
When recording modes for transfer from the Multiple Systems with Event Codes to a Crow Extended -Continuous Evaluation equivalent single system, it is recommended to consider using an iteration method to name subsequent recurrences of the same mode. This will help alleviate any issues with the conversion of the definitions of the modes from the Crow Extended model to the Crow Extended - Continuous Evaluation model. For example, if the first occurrence of a mode is BC25, then the second occurrence is suggested to be named as BC25.1. The reasoning behind this recommendation is that in the case that BC25 in the Multiple Systems with Event Codes data sheet has received implemented fixes (I events) at the same time that the failure occurred, in all systems, then this mode will be translated as a BC mode in the Crow Extended - Continuous Evaluation equivalent single system. The next recurring failure would also be treated as a BC mode but in reality it did not have an implemented fix (I event) at the time of failure. Example 7 Consider the example shown in Figure iterationsithout, that represents one system only for simplicity. Notice that the modes BC25, BC35 and BC45 received implemented fixes at the time of failure. Based on that, when they get transferred to the Crow Extended - Continuous Evaluation equivalent single system, they will be considered as BC modes. The subsequent failures of the modes 25, 35, and 45 will also be converted to BC modes, when in reality they had implemented fixes (I events) at a later time. Figure iterationsarning shows a warning when trying to convert this data sheet without using iterations.

$$$$

Solution Figure iterationsith shows the same data sheet with the use of iterations for the modes 25, 35 and 45. The subsequent failures are named as BC25.1, BC35.1 and BC45.1.



This way, the conversion to the Crow Extended - Continuous Evaluation model occurs in a valid fashion, since although the original BC modes are converted to BC25, BC35 and BC45, the subsequent failures are converted to BD25.1, BD35.1 and BD45.1 together with their respective implemented fixes (I events). This is shown in Figure iterationsHASES. Note that the use of iterations is recommended only when transferring to the Crow Extended - Continuous Evaluation equivalent single system, it is not necessary when using the Multiple Systems with Event Codes data sheet that is calculated with the Crow Extended model.