It depends on what kpi's and what connections the Collector elements require. In our instance with the standard solution, ideally the customer may configure everything themselves. The steps required per level are as follows:

Collector Element: Establish all necessary connections to retrieve the device data and topology information, usually just the endpoints when creating the element and possibly credentials to access endpoint.

Backend Elements: Assign which Collector elements will be aggregated by the current element in the Collector registration table.

Frontend Element: Add all Collector and Backend elements to the Collector and Backend registration tables that you would like to be included in the solution.

All Elements: Ensure that all import and export directories are pointing to the correct location so they are able to transfer the files correctly for the ID assignment. This directory simply needs to be a root directory, the driver will handle any subfolders in that directory internally.

Once again, if there are missing kpi's then there would have to be some tweaking to be done on our end in both the collectors and EPM managers to get them to show and aggregation to be done correctly.