01
Every engagement has stated phases, stated deliverables, and a stated duration. What gets measured is agreed and baselined before the work starts.
Scoping is not free-form. If your problem does not fit one of these, the first conversation is about whether it fits us at all.
02
The three with the most depth. Each has its own page describing phases, deliverables, and what gets measured.
01
Credentials, MID Server placement, scheduling, and the identification rules that decide where what you find actually lands.
02
Entry points, top-down discovery, and application service maps your incident process can actually trust.
03
Class hierarchy, identification and reconciliation rules, duplicate resolution, and health dashboards someone is accountable for.
03
04
Turning monitoring noise into a small number of actionable alerts bound to the right configuration item.
05
Asset lifecycle from receiving through disposal, reconciled against what Discovery independently finds on the network.
06
Normalization, entitlement modelling, and a license position that survives a publisher true-up.
07
Ongoing platform health review and remediation after the implementation is done, scoped to agreed hours.
04
Turning monitoring noise into a small number of actionable alerts bound to the right configuration item.
05
Asset lifecycle from receiving through disposal, reconciled against what Discovery independently finds on the network.
06
Normalization, entitlement modelling, and a license position that survives a publisher true-up.
07
Ongoing platform health review and remediation after the implementation is done, scoped to agreed hours.
That is a normal place to start. Describe what is going wrong and we will tell you which piece is actually broken — often it is the CMDB underneath rather than the thing that appears to be failing.