1. High Level Component Definition and Architectural Relationships (template)

2. Template Component API definitions

Template Component provides the following interfaces:

Interface Name	Interface Definition	Interface Capabilities	Version	Status	Consumed Models
HOLMESE-1	This is a set of rule management interfaces, which is mainly intended for the CRUD actions of the rules of Holmes.	Allows applications to create, update, delete, and query the rule entities.	1.0.0	production	Defined by Holmes
HOLMESE-2	Health check.	Allows other applications to perform healthcheck on Holmes.	1.0.0	production	-

Template Component consumes the following Interfaces:

Interface Name	Purpose Reason For Use	Version(s)
POE-4	To send the closed control loop events to policy to trigger downstream actions.	-
DCAEEXT-7	To retrieve default configurations (e.g. default rules and DMaaP configurations, etc.)	-
DMaaP-2	To retrieve VES events from DMaaP.	-
DMaaP-3	To send closed control loop events to DMaaP.	-
AAIE-1	To query resource information from A&AI.	v19

A more detailed figure and description of the component.

Performance limitation: if it comes to high-performance scenarios, and A&AI happened to be needed for alarm analysis and correlation, there could be a performance bottleneck as all A&AI API calls are based on HTTP requests, which is considerably time-consuming.

MDONS support
AAF integration (stretch goal, because I'm not sure if I could get the necessary help from the AAF team)