Skip to main content

BMW US UCP consolidation

BMW US builds five consolidated entities: dealers, models, features, inventory, and rules. Rules resolve references against the existing consolidated model and feature catalogs, supplied by BYO and the configured model sources.

Model keys are (model_code, model_year). Feature keys are (feature_code, model_code, model_year, parent_package_code). The rules-to-models foreign key joins on model code and year, allowing 1% unresolved because UCP publishes model years BYO does not.

Rule enrichment​

These assets resolve rule references against canonical feature ids:

BmwUcpEnrichedRulesComponent reads transformed ucp_private_rules and the consolidated feature catalog for the same partition, and writes enriched ucp_private_rules. Expansion precedes consolidation because it multiplies rows, which a foreign key cannot do. Resolving the codes it produces is left to the consolidated tier.

Expansion is scoped to (model_code, model_year), and the feature catalog decides what a family is. The source flags families neither completely nor consistently: it may flag a reference as a family without publishing that family's members, and it may omit the flag on a code the catalog does group. The flag alone therefore cannot drive the expansion. A positive IF family expands into separate rules for its members, and several positive families produce every combination. A negated IF family contributes all its members to the negative list. A THEN family contributes all its members. Rule validity intervals are not clipped to model intervals.

The family_expansion check reports how many rules referenced a family, how many families the catalog did not cover, and the families responsible. A family the catalog does not group keeps its own code, so the foreign keys above count it as an unresolved reference rather than dropping it silently.

Group rules​

A configuration holds at most one feature from each family and at most one paint and one fabric. UCP states none of these limits as rules. The enriched ucp_private_rules asset writes them as only_one_of rules, one per group with at least two members:

GroupcodeMembers
Familyfamily:<family_code>Features sharing a family_code
Paintcategory:PFeatures with category P, regardless of family_code
Fabriccategory:FFeatures with category F, regardless of family_code

Group members come from the consolidated feature catalog, scoped to (model_code, model_year). A feature whose is_accessory is true belongs to no group.

The enriched ucp_private_rules asset writes group rules only for models that have UCP rules. Each group rule has:

  • the model's vg_code;
  • an empty rule_if;
  • an expansion_index of 0;
  • one validity entry with no date bounds.

A family has its own rule even when the paint or fabric rule already contains all of the family's members.

Consolidated rules​

A rule holds rule_if and rule_then, each a list of feature codes; an IF part also carries negated. Two foreign keys resolve them into rule_if_feature_ids and rule_then_feature_ids and report the references the catalog does not match, as the inventory foreign key does. An id list names the features a clause mentions and states no polarity, and an unresolved reference is absent from it, so rule_if is what states a rule's meaning. Their interpretation follows the standard rule contract. Each validity entry contains valid_from and valid_to dates.

Extraction drops the terms naming codes that a model's UCP catalog does not publish. The foreign keys resolve against the BYO feature catalog, not the UCP catalog. UCP lists options that BYO does not, such as the Individual paints of MY2025 models, and IF parts name those options. The rule_if_feature_ids foreign key therefore allows 10% unresolved, and the rule_then_feature_ids foreign key allows 1%.

A rule is keyed by model_code, model_year, code and expansion_index. Expanding a positive family reference produces one rule per member, and expansion_index numbers those rules so each keeps its own key. Each expanded row keeps the source rule's validity intervals.

Local replay tests materialize the consolidation configuration with captured UCP rules and an explicit test catalog in BYO's structure. They cover:

  • family expansion;
  • group rules;
  • reference resolution;
  • both intervals of rule 8799 for model 26XO.

This test catalog does not measure live BYO coverage.

See source endpoints and rule extraction for the input contracts.