of the virtualized function (e.g., blade down, software hung, service table overflow, etc.) that require healing. The conditions could be related to the overall service (not a specific VF, e.g., network congestion) that requires healing (e.g., reroute traffic). The conditions could also relate to capacity conditions (e.g., based on service demand variation, congestion) result- ing in a closed-loop response that appropriately scales up (or down) the service. In the cases where anomalous conditions are detected, but specific responses are not identifiable, the condition will be represented in an operations portal for additional operational analysis. The analytic framework includes applications that analyze the history of the service lifecycle to discern patterns governing usage, thresholds, events, policy effectiveness, etc. and enable the feedback necessary to effect changes in the service design, policies, or analytics. This completes the service lifecycle and provides an iterative way to continuously evolve the service to better utiliza- tion, better experience, and increased automation. 7.10 LEGACY BSSs INTERACTIONS WITH ONAP Network cloud offers/products will be designed, created, deployed, and managed in near real time, rather than requiring software development cycles. ONAP is the framework that provides service creation and operational management of the network cloud; this software automation plat- form enables significant reductions in the time and cost required to develop, deploy, operate, and retire products, services, and network elements. The BSSs, which care for such capabilities as sales, ordering, and billing, will interact with ONAP in new network cloud architectures, thus will need to pivot to this new paradigm. While BSSs exist for today's network, they will need to be enhanced in order to work and inte- grate with ONAP. These enhancements will need to be made with the assumption that the BSSs must also support existing products (perhaps in a new format) and enable faster time-to-market for new p