A CMDB that discovers, de-duplicates, and keeps itself trustworthy.

She stands up the configuration that keeps your CMDB clean and your monitoring actionable — the discovery, health, and correlation setup that lets the platform find, dedupe, and route work on its own. Everything is grounded in your live instance and proposed for your approval before anything is built.

No. The collection agent is customer-installed software on a host inside your network, and turning Discovery on is a vendor request. Phyllis configures what runs once that's in place — she doesn't provision the infrastructure itself.

She sets up the matching and health rules that stop duplicate and low-quality records before they pile up, and stages them for you to validate before they go live. The result is a CMDB you can trust — built from how your estate actually looks today, not out-of-box assumptions.

Nothing. Phyllis discovers, proposes a plan, and only builds on your explicit approval — every change lands in one scoped, reviewable package you can roll back. Sensitive rules are staged inactive so you can validate them before switching them on.

Every finding is cited back to your own live instance, not a generic model — so the plan reflects your actual estate, class coverage, and Discovery posture. You see the evidence behind each recommendation before you approve it.