he neces- sary automation to proactively respond to network and service conditions without human interven- tion. A high-level schematic of the "closed-loop automation" and the various phases within the service lifecycle using the automation is depicted in Figure 7.14. The various phases shown in the service lifecycle above are supported by the design, orchestra- tion, and analytic frameworks described below. 7.9.1 DESIGN FRAMEWORK The service designers and operations users must, during the design phase, create the necessary reci- pes, templates, and rules for instantiation, control, data collection, and analysis functions. Policies and their enforcement points (including those associated with the closed-loop automation) must also be defined for various service conditions that require a response, along with the actors and their roles in orchestrating the response. This upfront design ensures that the logic/rules/metadata is codified to describe and manage the closed-loop behavior. The metadata (recipes, templates, and policies) is then distributed to the appropriate orchestration engines, controllers, and DCAE components. 7.9.2 ORCHESTRATION AND CONTROL FRAMEWORK Closed-loop automation includes the service instantiation or delivery process. The orchestration and control framework provides the automation of the configuration (both the initial and subsequent changes) necessary for the resources at the appropriate locations in the network to ensure smooth operation of the service. For closed-loop automation to occur during the lifecycle management phase of the service, the instantiation phase must ensure that the inventory, monitoring, and control functions are activated, including the types of closed-loop control related to the participating VFs and the overall service health. Building the Network of the Future Customers E-Services Portal Placement Function Infrastructure Controller Network Controller Application Controller Controller Framework AIC Cloud FIGURE 7.15 Service instantiation use case on a network cloud 