roducts and services in the network cloud. The BSS transformation to support the dynamic network cloud environment is based on the following: 1. Building blocks-BSS migration from monolithic systems to a platform building block architecture that can enable upstream UX changes in how products are sold, ordered, and billed. Catalog-driven-BSSs will become catalog-driven to enable agility, quick time to market, and reduce technology development costs. 3. Improved data repositories-support accuracy and improved access to dynamically changing data (e.g., customer subscriptions). 4. Real-time APIs-BSS platforms must expose functionality via real-time APIs to improve flexibility and reduce cycle time. Building the Network of the Future 5. New usage data and network events-BSSs that have a need to know about network events (e.g., billing) will be retooled to support new information from DCAE and A&AI. 6. Expose BSS functions-provide BSS functions directly to our customers to streamline processes and allow new distribution channels. 7.10.1 BSS SCOPE Figure 7.16 shows the BSS scope that includes customer management, sales and marketing, order lifecycle management, usage and event management, billing, customer finance, UX, and end-to-end BSS orchestration. The BSS scope includes the following areas: 1. Customer management-focuses on customer information, retention of the customer, insight about the customer, managing customer service-level agreements, and building customer loyalty. Key new consolidated data stores of customer information for new vir- tualized services are the customer profile, customer subscription, and customer-interaction history. 2. Sales and marketing-provides all of the capabilities necessary to attract customers to the products and services being offered by a service provider, create solutions that meet customers' specific needs, and contract to deliver specific services. Sales and marketing hands off contracts to billing for implementation and solutions to ordering for service provisioning. 3. Order 