7.1.2 ONAP COMPONENT ROLES Orchestration is the function defined via a process specification that is executed by a work flow component. MSO automates a sequence or a set of sequences of activities, tasks, rules, and policies needed for on-demand creation, modification, or removal of network, application, or infrastructure services and resources. The MSO provides workflow orchestration at a very high level, with an end-to-end view of the infrastructure, network, and application scopes. Controllers are applica- tions that are closely associated with cloud and network services and execute the configuration, real-time policies, and control the state of distributed components and services. Rather than using a single monolithic control layer, ONAP has chosen to use three distinct controller types that man- age resources in the execution environment corresponding to their assigned controlled domain such as cloud computing resources (infrastructure controller, typically within the cloud layer), network configuration (network controller), and application (application controller). DCAE and other ONAP components provide Fault Configuration Accounting Performance Security (FCAPS) functionality. "Finished goods" for specific services are created from the plat- form capabilities for specific services and products. DCAE supports closed-loop control and higher- level correlation for business and operations activities. It is the ecosystem component supporting analytics and events: it collects performance, usage, and configuration data; provides computation ONAP Portal ONAP OA&M Controller E-Services BSS / OSS Big Data Design Functions Operations Functions Service Analytic Dashboard External Data Movement & APIs Policy Creation Design & Creation Application Design Manual Action Policy Editor Analytics SDK Inventory Management Design Studio Request Handler Resource Onboarding Policy Rules Reporting KPIs, Alarms, Active 7 Available Entitlements Orchestration Engine Service Catalog Certification Studio Conflict Identification Operato