The following steps are necessary:

1. Download the ACDI client from the OpenText support portal (included in your Business Support)
2. Installing of ACDI on one of your servers
3. Configuration of the data collection of ACDI (e.g. for eDirectory, IDM, driver monitoring)
4. Data gets stored and historized and is available for later evaluations and audits
5. Evaluation of the available data with custom dashboards and reports (using the 90 day trial license of the PRO Version)

If you need further help with this, please feel free to contact the ACDI product team:

• Christian Karch – ACDI Product Manager – ckarch@opentext.com
• Enno Hoffmann – ACDI sales consultant – ehoffmann2@opentext.com

perhaps you're also interested in the time you have to invest in these activities?

Yes indeed, that would be also good to know, thank you

Necessary time to spend:

• For installation and configuration in your environment (steps 2 and 3): approx. 1-2 days
• For data collection: 4-6 weeks (as a representative start)
• For a workshop to define the dashboards and reports: approx. 0.5-1 day

ACDI is a little bit confusing as you can collect data a number of different ways.

1) Via a ACDI driver IDM that catches all events in the filter for the tree.

2) A new package for ACDI to add to each driver you want to instrument to collect more specific info. (i.e. #1 tells you an event happened. #2 tells you it was the AD driver).

3) Add ons to instrument the Workflows you might have.  I would love to see a discussion of what the options here are.  Will depend on use cases as always.

All 3 though send their data back to the same backend.  So first you need the backend database/graphing/webserver. Then an IDM driver to collect generic events.  Then contemplate if it makes sense to instrument your drivers or not.