 view based on configurable metadata definitions for each activity that determine what is relevant to the A&AI inventory. A&AI provides standard APIs to enable queries from various clients regarding inventory and topology. Queries can be supported for a specific asset or a col- lection of assets. The A&AI global view of relationships is necessary for forming aggre- gate views of detailed inventory across the distributed master data sources within this environment. Administration-A&A also performs a number of administrative functions. Given the model driven nature of ONAP, metadata models for the various catalog items are stored, updated, applied, and versioned dynamically, as needed, without taking the system down for maintenance. Given the distributed nature of A&AI as well as the relationships with other ONAP components, audits are periodically run to assure that A&AI is in sync with the inventory masters such as controllers and MSO. Adapters allow A&AI to interoperate with legacy systems as well as third-party cloud providers. 3. Reporting and notification-consistent with other ONAP applications, A&AI produces canned and ad hoc reports, integrates with the ONAP dashboards, publishes notifications other ONAP components can subscribe to, and performs logging consistent with configu- rable framework constraints. 7.9 CONTROL LOOP SYSTEMS: WORKING TOGETHER Given the network cloud vision described in this section, network elements and services will be instantiated by customers and providers in a significantly dynamic process with real-time response to actionable events. In order to design, engineer, plan, bill, and assure these dynamic services, there are three major requirements: 1. A robust design framework that allows specification of the service in all aspects-model- ing the resources and relationships that make up the service, specifying the policy rules that guide the service behavior, specifying the applications, analytics, and closed-loop events needed for the elastic management of the service. 2. An orchest