Incident management framework can be used to aggregated alarms, KPIs and other anomaly information into incident, and provide standard APIs to manage incident lifecycle. It can reduce the pressure on upper-layer system, improve accuracy of root cause analysis and service impact analysis. Incident lifecycle management APIs can help improve the network automation.

ONAP, as orchestrator, can delegate alarm/performance process to domain controller, domain controller aggregate these information into incident, and report it to ONAP.

Key Contacts - Frank Feng(Huawei), Keguang He (CMCC), Chuanyu Chen (Huawei), GuanyuZhu(Huawei)

Executive Summary - This requirement provides incident management framework and data models to improve the efficiency of fault management.

Business Markets - Incident management provides some functions.

1.Incident detection using AI or preconfigured policies including aggregating anomaly data into incident, and service impact analysis.

2.Provide several APIs to management incident lifecycle, such as incident reporting, querying, diagnosis, resolution, etc.

Funding/Financial Impacts - Incident management can reduce OPEX because less data needs to be processed, more accurate root cause analysis and service impact analysis are performed, and fewer tickets are generated.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

Owners (one of these should be the Assignee - use @ notation):

llly (huawei),   hekeguang  (CMCC)

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

R14: SDNC, CCSDK

R15: DCAE, POLICY, SO

As described in  :

Project (ONAP Component #1 SDNC) IMPACT: C

• Impact Type: C(Test Only/Code)
• Company Engagement: Huawei, CMCC
• Resources: llly
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null

Project (ONAP Component #2 DCAE) IMPACT: T

• Impact Type: T (Test Only/Code)
• Company Engagement: Huawei, CMCC
• Resources: llly
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null

Project (ONAP Component #3 Policy) IMPACT: T

• Impact Type: T (Test Only/Code)
• Company Engagement: Huawei, CMCC
• Resources: llly
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null

Project (ONAP Component #4 So) IMPACT: T

• Impact Type: T (Test Only/Code)
• Company Engagement: Huawei, CMCC
• Resources: llly
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null