Figure An.02 - Anomaly Management Entity Relationship With Other SID Entities

<font color="#29313b">This figure shows how the Anomaly Management entities are related to domain entities such as Service, Resource, etc. Note that Anomaly can be associated with any SID Entity and not limited to Service or Resource.</font><br/><font color="#29313b">Currently the association between ServiceAnomalySpecification and ServiceSpecification are shown to represent the incorporation of anomaly management details for ServiceSpecification. However, this association can also be used for composing Anomaly management related items and characteristics for a particular Service specified using ServiceSpecification. So in the latter case ServiceSpecification may contain ServiceAnomalySpecification as one of the composed item. Similar views are applicable for Resource and other domain entities specifications.</font><br/><font color="#29313b">The diagram shows an example of how Product, Service , Resource domain entities associate with Anomaly Management entities. While  the above diagram does not differentiate the Anomaly Management entities associations across domains , in practical scenarios operators may prioritize operationalization of Anomaly Management(AM) at particular domain based on the business value that can be derived. For example since the number of AM use cases are relatively more on the Service and Resource domains, there may be an inclination to incorporate AI Closed Loop AM for these domains. But from an IM point of view this does not eliminate the need for AI Closed Loop AM at other domains. Hence, the readers are advised to keep in mind the repeatability pattern possible with AI Closedloop AM. </font><br/><br/>