Special Cases

In some of the cases, support ancillaries can be separated into multiple sub-configurations (for example, A,B,C,D) within the SupportConfiguration.xml file. It is important to ensure that any MDU based copies of such standards adhere to the naming convention of the original. For example, if a copy of AT145 is made to AT690, additional representations of AT690A and AT690B must be created in the supports configuration file because AT145 has an A and B representation.

<Mapping name="AT145A" representationId="at03"/>

<Mapping name="AT690A" representationId="at03"/>

<Mapping name="AT510A" representationId="at03"/>

<Mapping name="AT697A" representationId="at03"/>

<Mapping name="AT145B" representationId="at140"/>

<Mapping name="AT690B" representationId="at140"/>