Compression Details

This topic describes in more detail the steps performed by the Compression process.

1. Select all applications for a Base Vehicle / Part Type (or Part Type + MfrLabel if Compress to MfrLabel is checked).

2. Determine the attribute types used to express the applications. (For example, Body Type and Drive Type.)

3. Attempt to find a single attribute type that can be used to express the applications completely. If it doesn’t find a single attribute, it looks for combinations of two attribute types, three attribute types and so on.

4. Applications must “fan-out” naturally. Within the set of applications being compressed, it is not possible to express some applications in terms of one single attribute type and other applications in terms of a different single attribute type. If an attribute type was used on one application of the group, it will be included on all applications in the group.

   Suppose, for example, that some applications are written originally in terms of Submodel and others in terms of Aspiration. If Submodel alone is sufficient to define the applications, applications with Aspiration will be rewritten to use Submodel. If neither Submodel nor Aspiration are sufficient, all applications will be rewritten to use both Submodel and Aspiration. (Aspiration might be dropped if it doesn’t matter for a particular submodel.) An application that originally has just Aspiration is rewritten to include Submodel.

Note: This method of compression may result in your ACES applications being written differently than your source applications. This “translation” does not change the accuracy of your data and is necessary to maintain consistency for catalog lookup systems (where a natural fan-out is usually expected). Notes, Qualifiers and MfrLabels are never translated or dropped in this way.