ness needs. The Ultimate Guide to Building and Delivering OSS/BSS An example of a detailed, phased, OSS deployment program approach follows: Table 70. Example Of Phased OSS Deployment Program Approach Customer Order v1.0 - Deploy order entry capabilities within CRM package and order management/provisioning solution, and implement integration to enable new services/features, new customers, disconnect, change profile and cancel orders v2.0 - Deploy sales force automation (SFA) to enhance order capture and add integration to support supplemental orders Pre-Order Deploy application to check facility availability, perform customer qualification and perform the credit check Billing Order Deploy billing applications Completion Enable order complete information passed automatically to billing Enable customer record and product information synchronization between CRM and billing Internal Service v1.0 - Deploy network inventory management tool and some Activation limited capabilities for activation in terms of certain network elements or products v2.0 - Implement and integrate automated activation for the full set of network elements and products with testing capabilities enabled External Service v1.0 - Deploy and integrate an interconnection gateway to Activation enable the LSR/ASR process (typically limited based on high priority interfaces and/or trading partners) v2.0 - Full set of electronically enabled trading partners, integrated with the order management application Building/Network Automate workflow to manage internal "orders" for network Deployment deployment Trouble Ticketing Integrate with SFA tool for "building" sales process v1.0 - Deploy trouble management package and enable customer-facing trouble ticketing and network trouble ticketing through a GUI v2.0 - Add integration of customer and network troubles SO that network alarms can be correlated with customer troubles automatically The implementation program's overall size will vary depending on the number of packages, level of integration and the amount of