Avoid inventory duplication — federate rather than replicate

Overview

When multiple teams independently maintain inventories that cover the same or overlapping item types, the result is inventory duplication: multiple lists of the same items, maintained independently, typically with different schemas, different levels of quality, and different update frequencies. Duplicated inventories contradict each other, consume redundant maintenance effort, and prevent the formation of a coherent Enterprise Model because the same item type has multiple, inconsistent representations.

Best Practice

When a new inventory initiative is proposed, audit the existing inventory landscape to determine whether an inventory of the proposed type already exists. If it does, invest in improving the existing inventory to serve the new use case rather than creating a competing inventory. If the existing inventory cannot serve the new use case without modification, determine whether federated contribution to the existing inventory is feasible before concluding that a separate inventory is necessary. Federate rather than replicate: distribute contribution while centralizing governance.

Benefit(s)

Avoiding inventory duplication concentrates maintenance effort on a single authoritative inventory rather than distributing it across multiple competing inventories. The Enterprise Model reflects a single, coherent view of each item type rather than multiple contradictory views. Decision-makers know which inventory to consult for each type of information and can trust that the answer they get is consistent with what other decision-makers are seeing. The organization’s inventory investment delivers higher value because it is concentrated rather than fragmented.