n be built on top of DCAE and that depend on the timely collection of detailed data and events by DCAE: a. Analytics-these will be the most common applications that are processing the col- lected data and deriving interesting metrics or analytics for use by other applications or operations. These analytics range from very simple ones (from a single source of data) that compute usage, utilization, latency, etc. to very complex ones that detect specific conditions based on data collected from various sources. The analytics could be capac- ity indicators used to adjust resources or could be performance indicators pointing to anomalous conditions requiring response. b. Fault/event correlation-this is a key application that processes events and thresholds published by managed resources or other applications that detect specific conditions. Based on defined rules, policies, known signatures, and other knowledge about the network or service behavior, this application would determine root cause for various conditions and notify interested applications and operations. Performance surveillance and visualization-this class of application provides a window to operations notifying them of network and service conditions. The notifications could include outages and impacted services or customers based on various dimensions of interest to operations. They provide visual aids ranging from geographic dashboards, virtual information model browsers, detailed drilldown, to specific service or customer impacts. Capacity planning-this class of application provides planners and engineers the abil- ity to adjust forecasts based on observed demands as well as plan-specific capacity augments at various levels, for example, cloud infrastructure level (technical plant, racks, clusters, etc.); network level (bandwidth, circuits, etc.); service or customer levels. e. Testing and trouble-shooting-this class of application provides operations the tools to test and trouble-shoot specific conditions. They could range from simple health checks for 