Pages
Every claim cited to the record
Ultra
CMDB

A CMDB assessment with the evidence attached.

Ask about your CMDB in your own words — Phyllis analyses the live estate, from duplicate and stale CIs to broken references and reconciliation rules, and returns findings cited back to the records they came from — staged for your approval.

author testimonial
customets image
customets image 1
Want a walkthrough?
Thousands of tools. Every ServiceNow product.
Contact us

A quick scroll through what Phyllis can do

Scan CMDB health

Show me where the CMDB is unhealthy — duplicates, stale records, orphans and broken references.
ServiceNowSonnet 5 Low

Duplicate CIs

Find duplicate server CIs in cmdb_ci_server and stage de-duplication tasks for review.
ServiceNowSonnet 5 Low

Stale CIs

Flag CIs no discovery source has updated in the last 90 days as stale.
ServiceNowSonnet 5 Low

Broken references

List relationships in cmdb_rel_ci that point at missing or retired CIs.
ServiceNowSonnet 5 Low

Orphaned CIs

Show me CIs with no relationships and no owning service, grouped by class.
ServiceNowSonnet 5 Low

Identification rules

Review our CI identification rules and flag classes matching on weak identifiers.
ServiceNowSonnet 5 Low

Reconciliation rules

Set data source precedence so Discovery wins over manual edits on hardware attributes.
ServiceNowSonnet 5 Low

Discovery sources

Which sources in sys_object_source are writing to the CMDB, and which CIs have none?
ServiceNowSonnet 5 Low

CSDM alignment

Map our services and applications against CSDM and show me where the model drifts.
ServiceNowSonnet 5 Low

Remediation backlog

Turn the health findings into a sequenced remediation backlog my team can pick up.
ServiceNowSonnet 5 Low

Health reporting

Build reporting that tracks CMDB completeness, correctness and compliance over time.
ServiceNowSonnet 5 Low

Post-build scan

Scan the staged CMDB remediation and stage anything that can be safely healed.
ServiceNowSonnet 5 Low

Scan CMDB health

Show me where the CMDB is unhealthy — duplicates, stale records, orphans and broken references.
ServiceNowSonnet 5 Low

Duplicate CIs

Find duplicate server CIs in cmdb_ci_server and stage de-duplication tasks for review.
ServiceNowSonnet 5 Low

Stale CIs

Flag CIs no discovery source has updated in the last 90 days as stale.
ServiceNowSonnet 5 Low

Broken references

List relationships in cmdb_rel_ci that point at missing or retired CIs.
ServiceNowSonnet 5 Low

Orphaned CIs

Show me CIs with no relationships and no owning service, grouped by class.
ServiceNowSonnet 5 Low

Identification rules

Review our CI identification rules and flag classes matching on weak identifiers.
ServiceNowSonnet 5 Low

Reconciliation rules

Set data source precedence so Discovery wins over manual edits on hardware attributes.
ServiceNowSonnet 5 Low

Discovery sources

Which sources in sys_object_source are writing to the CMDB, and which CIs have none?
ServiceNowSonnet 5 Low

CSDM alignment

Map our services and applications against CSDM and show me where the model drifts.
ServiceNowSonnet 5 Low

Remediation backlog

Turn the health findings into a sequenced remediation backlog my team can pick up.
ServiceNowSonnet 5 Low

Health reporting

Build reporting that tracks CMDB completeness, correctness and compliance over time.
ServiceNowSonnet 5 Low

Post-build scan

Scan the staged CMDB remediation and stage anything that can be safely healed.
ServiceNowSonnet 5 Low
ServiceNow
Phyllis
Jira
Solutions

Works with the stack you already run

Questions?

We’re glad you asked.

What does a Phyllis CMDB assessment actually tell me?

Where your model has drifted from CSDM and why — subclass mismatches, services with no owning application, technology-derived names, orphaned offerings — each finding backed by the actual records it came from and a confidence rating, so you're triaging evidence, not opinions.

Does she change my CMDB?

No. The assessment is read-only. She walks your live CI records and surfaces what's wrong with the modelling and how to fix it; any remediation is proposed and staged for your approval — she never edits CIs behind your back.

How is this different from the health dashboards we already have?

Completeness dashboards score fields; she reasons about the model. She looks at how services, applications and offerings actually relate in your data and flags the structural problems a field-level score can't see.

What do you need to run it?

Read access to the instance. She reads the CMDB tables, relationships and classes directly, grounds every finding in a real record and cites it — nothing is inferred from a sample.

Can she help us prioritise the fixes?

Yes. Findings come rated by confidence and impact, so you start with the modelling errors that break service mapping and reporting rather than chasing every cosmetic discrepancy.

Ready to 10× the team you already have?


Cancel anytime.