ning, and trouble suspended ticketing systems Single inventory for physical and Systems should know how logical components network is configured at all times; relate services, customers, and physical plant BUILDING THE OSS PLATFORM 6.1 Tackling Implementation and Configuration The typical approach for OSS deployment is a phased-in implementation with quarterly "releases." The OSS implementation approach determines what functions will be available to the enterprise, and thus should be aligned with business priorities. The business requirements define each release's content. To be successful, the IIC must manage the program closely and align it with the business continually by using a formal change management Chapter 5 - The Enterprise OSS Platform process. If the business needs change, or if priorities change, then the impact on the entire program needs to be evaluated and the program adjusted appropriately. Although typically it is less risky at first to deploy a handful of packages in a standalone fashion and then add integration in later phases, most IICs choose to implement systems with some level of integration. Business requirements will drive the order and priority in which packages are implemented, along with the initial level of integration. There will be a mixture of manual and automated interfaces during the deployment period. Business process alignment needs to be revisited at each phase of OSS deployment, as new functionality and automation is rolled-out. Figure 14 illustrates a sample approach to OSS deployment. The approach involves four phases, gradually developing the OSS platform from basic business functions to more sophisticated, differentiating capabilities. Phase 1 typically consists of core functionality, such as order entry, order management, provisioning, inventory management, gateways to high priority suppliers, billing, fault management and performance monitoring, and general ledger/accounts payable. Additional functionality and integration is added in subsequent phases according to busi