terprise. The DOM is necessary for avoiding order fall out and redline situations, because it allows the provisioning process to be completed rapidly and with fewer errors. Telecom consultants such as BoldTech have spent much time in building network inventory DOMs. These DOMs are the starting point for develop- ment efforts in which OSS integrate accurate inventory to add further automation to the provisioning process. Some DOM features include: support across all telecom technology layers fibre, SONET, ATM and IP historical, present and future views of inventory extensibility for adding new types of inventory and their attribution generic applicability regardless of how individual OSS represent inventory logical, physical and spatial schematic views. 10.4 Inventory Load and Reconciliation Without a consistent and accurate view of network inventory between the network and OSS, the current state of the inventory and its percentage utilization cannot be OSS for Telecom Networks maintained accurately. The result is a higher capital expense on incremental network augments. Integrated loading and reconciling of inventory data from network management systems can be done using common data objects. This approach limits the network- specific formats and communication protocols, and allows users and other applica- tions to perform the following functions: inventory loading data retrieval reporting discrepancy checking reconciliation synchronization. 10.5 Inventory Service Architecture The traditional method of using Enterprise Application Integration (EAI) tools to synchronise inventory between inherited silo OSS does not generally provide a com- plete solution. 32 Segmented inventory stores must be consolidated before a carrier is likely to see value from its inventory management system. The value is apparent though automation of the provisioning process, requiring less human intervention and, thus, faster cycle times and more immediate revenue recognition. Inventory is an enterprise-wide resource and must be logically c