Scan3
01 · A scan after every task.
Instance Scan runs after every build — hundreds of checks — so debt is caught while the context is fresh.
Maintain
Maintain — Tested, scanned, self-healed — shipped on your approval.
ATF runs attach to the build and every dev task ends with an Instance Scan. Phyllis stages the fix for findings you approve — nothing promotes without your sign-off.
14.2%
Run a health scan on acme-prod and fix what you can.@ for records · / for commands
Build
acmedevProject
acmedevProject Instance ScanHundreds of checks · 3 findingsRead
Query in a loopRouting business rule · line 14High
Fixes staged for your approval3 findings · rescan afterProposed
Built for the platform
3,000+typed ServiceNow tools~230expert skill packsHundredsof health checks8acceleratorsISO 27001 certifiedPer-user OAuthApproval on every changeLands in your update setsATF on every build
What you can ask Maintain to do.
Speed up delivery, reduce review friction, and make the platform understandable for every stakeholder — not just the person who built it.
Read · sync business rule3 steps
Explain the Sync to CMDB rule
Runs after update when the asset state changesafter · u_asset_returnWhen
Looks up the matching CI by serial numberreads · cmdb_ci_hardwareStep 1
Updates the CI’s install status and ownerwrites · cmdb_ci_hardwareStep 2
Maintain
See the story behind every change
Instead of staring at dense functions and multi-branch flows, Chat breaks them into steps, highlights the key decisions, and shows how data moves through the system.
Insights · this estate3 suggested
41% of P3 incidents reassigned twiceAssignment rules miss 2 categoriesInsight
Knowledge articles unused for 12 months318 articles · candidates to retireInsight
Change failure rate up after Fridays7 of 9 failed changes · Friday deploysInsight
Turn these into stories?3 suggested fixes, sizedCreate Story
Maintain
Give engineers context without meetings
Every explanation includes missing assumptions, performance notes, side effects, and business logic clues — exactly what senior engineers normally explain out loud.
Instance Scan · finding → fixinstance scan
GlideRecord in client scriptIncident form · 3 instancesHigh
→ Moved to a GlideAjax script includediff ready · ATF 6 / 6 passedFixed
Apply the fix?Staged in an update set · nothing ships without youApprove fix
Maintain
Who’s going to fix all this?
Findings don’t just pile up. Approve a fix and Phyllis stages the remediation in a scoped update set — deprecated calls rewritten, orphaned artefacts removed — then re-scans, so the instance heals on your sign-off instead of waiting for a war room.
How Maintain works. Step by step.
Query in a loop · line 14
02 · Findings, cited to the record.
Each finding links to the record and line it came from, with the fix that resolves it.
FixedRescan clean
03 · Self-healed, on your approval.
Phyllis stages the fix, you approve it, and the scan runs again to prove it’s gone.
See what Phyllis delivered. In consulting days, not tokens.
Value & usage · last 90 daysOwners & admins
Delivered148changes across 3 instances
Consulting effort≈ 212 daysestimated by size and complexity
S74
M48
L21
XL5
CMDB healthAccelerator · run 3 timesAdopted
Upgrade readinessAccelerator · run onceAdopted
Licence optimisationAccelerator · not yet runAvailable
Owners and admins see what was delivered across every instance, sized by complexity and estimated as the consulting effort it replaced — plus which accelerators the team is using.
What’s included
Delivered changes across instances
Consulting-effort estimate by size and complexity
Accelerator adoption
Live credit counter while Phyllis works
Maintain, across the platform.
Re-scan — self-heal on the staged remediationFixes staged
sys_scriptthe reworked rule now hits the new index — the slow query is resolved
sys_security_aclone write ACL was missed alongside the new read ACLs
write ACL alongside the new read ACLsUS-IH21Staged
move the stray record to its own update setUS-IH22Staged
Extend the index review to related tables2 ptsStory
Health
Instance health & self-heal
Hundreds of checks across every category — and unlike the native engine, Phyllis self-heals findings on your approval.
Read the use caseCMDB health remediationFixes staged
Reconciliation rulesone rule omits the SCCM source — manual edits could still win
Identification rulesan identifier entry left inactive — the rule would not fire
add SCCM source to reconciliation ruleUS-CMDB21Staged
activate serial identifier entryUS-CMDB22Staged
Review remaining orphaned CIs2 pts · CMDBStory
CMDB
CMDB health assessment
Ask why the CMDB is drifting — get evidence-backed findings and remediation stories, not a slide deck.
Read the use caseCreative Cloud licensingFixes staged
Entitlementsentitlement start date empty — maintenance cover won't compute
Reclamation rulesrule missing an assignment group — reclaimed seats won't route
backfill entitlement start dateUS-SAM12Staged
set reclamation assignment groupUS-SAM13Staged
Add SaaS spend integration for Adobe5 ptsStory
Asset & Ops
ITAM, ITOM & EAM
The same loop across asset and operations domains — discovery-grounded plans, staged builds, evidence attached.
Read the use caseMaintain, answered.
How often does Phyllis scan?
After every task she completes, so issues are caught while the change is fresh. You can also ask for a health scan at any time.
Does she fix things on her own?
Only with your approval. Fixes are staged, you approve them, and the scan runs again to prove the finding is gone.
What does the scan cover?
Hundreds of checks across security, performance, upgradability and more — including ServiceNow’s Scan Engine rules and MID Servers.
Can we see the value delivered?
Yes — the Value & Usage dashboard shows delivered work and the estimated consulting effort it replaced, for owners and admins.
The rest of the lifecycle.
One teammate from the first question to a promoted, tested change.
CMDB health scorecardcmdb_ci · 48,213
68of 100
CriticalDuplicate servers across SCCM and Discovery2,114 CIsFix with Phyllis
Analyze
Ask your instance anything
Phyllis grounds herself in the full context of your ServiceNow instance — its tables, ACLs, flows, update sets, configurations, and dependencies. Every answer is evidence-backed and traceable to the records it came from.
Explore AnalyzeImplement ITSM · 24 storiesITSM-101
ITSM-102Incident categories & assignment rulesDone5
ITSM-103Major incident workflowReady8
ITSM-104Change CAB approvals by riskReady5
ITSM-105Problem → known error handoffPlanned3
ITSM-106SLA definitions for P1–P4Draft3
Plan
From a sentence to a sprint-ready backlog
Say “I want to implement ITSM” and Phyllis returns sequenced stories with priorities, points, and acceptance criteria — synced both ways with Jira or ServiceNow Agile 2.0.
Explore Plansys_script · P1 network auto-assign+6 −0
1(function executeRule(current, previous) {
2 if (current.priority != '1') return;
3 var onCall = new OnCallResolver().forGroup('Network Ops');
4 if (!onCall) return;
5 current.assigned_to = onCall.user;
6 gs.eventQueue('network.p1.page', current, onCall.user);
7})(current, previous);
Update setFeature: P1 network auto-assign
ATF12 / 12 passed
Develop
The whole change, built in your instance
Phyllis develops on the platform — from tables, business rules, flows, and ACLs to the records behind them — then verifies and tests every change.
Explore Develop
