the policy definitions are also essential ingredients for any closed-loop automation, as orchestration and controllers will be the ONAP components that will execute the recommended actions deriving from a closed-loop automation policy. 7.9.3 ANALYTIC FRAMEWORK The analytic framework ensures that the service is continuously monitored to detect both the anoma- lous conditions that require healing as well as the service demand variations to enable scaling (up or down) the resources to the right level. Once the orchestration and control framework completes the service instantiation, the DCAE analytic framework begins to monitor the service by collecting the various data and listening to events from the VFs and their agents. The framework processes the The Network Operating System data, analyzes the data, stores it as necessary for further analysis (e.g., establishing a baseline, per- form trending, look for a signature), and provides the information to the application controller. The applications in the framework look for specific conditions or signatures based on the analysis. When a condition is detected, the application publishes a corresponding event. The subsequent steps will depend on the specific policies associated with the condition. In the simplest case, the orchestration framework proceeds to perform the changes necessary (as defined by the policy and design for the condition) to alleviate the condition. In more complex cases, the actor responsible for the event would execute the complex policy rules (defined at design time) for determining the response. In other cases, where the condition does not uniquely identify specific response(s), the responsible actor would con- duct a series of additional steps (defined by recipes at design time, e.g., running a test, query history) to further analyze the condition. The results of such diagnosis might further result in publishing of a more specific condition for which there is a defined response. The conditions referred to here could be ones related to the health 