The Data Collection, Analytics, and Events (DCAE) subystem, in conjunction with other OpenECOMP components, provides FCAPS (Fault Configuration Accounting Performance Security) functionality. DCAE supports closed-loop control and higher-level correlation for business and operations activities. It is the ecosystem component that supports analytics and events: it collects performance, usage, and configuration data; provides computation of analytics; aids in trouble-shooting; and publishes events, data and analytics (for example, to policy, orchestration, and the data lake). DCAE provides the infrastructure for collection of autonomous events from the network and other cloud components, making them available to subscribing applications, including business support system (BSS) and operational support system (OSS) applications.
The DCAE environment forwards usage and other information that can be used by the BSS to generate billable events and other events and records. The BSSs obtain the data from DCAE distribution channels or from the data lake. For example, the billing function in a BSS can support near real-time balance management by receiving streaming analytics from DCAE.
Usage and event management BSSs can be created as applications on top of the DCAE environment as well as applications outside DCAE. These applications can collect customer events and perform mediation of the usage and events to downstream BSSs or OSSs (Operational Support Systems). BSSs can also collect network events such as bill-impacting configuration changes, consumption or any new bill-impacting network product or service. This data can be used for rating, balance management, charge calculations, and so on.
ECOMP Data sources will provide data to BSS for Customer SLA credit processing. SLA Data Sources will collect information needed to perform Customer SLA Management. The ECOMP Data Sources are as follows: DCAE – network measurement, ECOMP Orchestration – service orchestration (activation), Policy – rules/violations, ASDC – SLA Definition, data templates for products. Note that both ECOMP Data sources and BSS will need to be informed about the fields to be gathered for those SLAs by the product definition in ASDC. The actual determination if an SLA has been violated, calculation of credits, and applying those credits to the customer bill will be done by BSS, not ECOMP Data sources. However, if there is an elastic response required based on a SLA violation being approached, the service may require an action by ECOMP to monitor and respond to a defined policy.