GeneWorks product suite
geneworks optimize

Optimize processes and performance.

Optimize scores the parts of the platform that quietly degrade — catalog quality, CMDB health, reference data, and upgrade readiness — and turns each finding into a governed change. Four surfaces, one pattern: scan, score, propose, approve.

Run a read-only scan Read the documentation
CMDB assessment · read-onlyone scan · ~12 seconds
health score31 / 100
maturity bandKnow Your Devices
near-term target50 · Federated CMDB
findings8
sequenced toQ1 – Q2
written to instancenothing
Four to five weeks of assessment work, read-only. Every finding is one click from a governed change.
~12s
full CMDB maturity assessment, read-only
974
documented release changes checked in one upgrade scan
~142
score points recoverable on a single catalog item
The pattern

The assessment tool is the remediation tool.

A conventional assessment ends in a slide deck, a roadmap nobody funds, and a second engagement to do the work. Every finding Optimize produces carries its own remedy and a one-click path into the six-stage delivery loop.

The gap between knowing and fixing becomes a button rather than a project.

31→50score, and the target

CMDB Assessment

A full maturity assessment — health score, findings, and a sequenced roadmap — from a read-only scan that takes about twelve seconds rather than the four to five weeks it takes by hand.

  • Completeness — mandatory and recommended attributes scored separately, because a missing mandatory field is a broken process while a missing recommended field is unrealised value.
  • Correctness — stale CIs, orphan CIs, and duplicates, detected with class-aware identification rather than name matching.
  • Compliance — shown only where it can be measured read-only; otherwise flagged as requiring an audit job rather than counted as zero.
Findings → roadmapimpact / effort, sequenced
F1 stale CIs · 60 daysdo first · Q1
F7 CMDB Health never rando first · Q1
F4 no CI ownermed effort · Q1–Q2
F2 not service-awarebig bet · Q2
F3 orphan CIsbig bet · Q2
Sorted by what to do first, not by severity alone. Each carries a one-click Make it a Change.
53a real item score
IAR Configuration CRPneeds attention · score 53
17 customisations, ceiling 2+30 build quality
no fulfilment group+30 governance
published, 0 orders / 30d+20 experience
0 of 44 variables documented+20 governance
all 7 fixes~142 points
Every finding is priced. You can sequence remediation by points recovered per hour of effort.

Catalog Center

Scores every catalog item on three pillars — Build Quality, Experience, Governance — and states exactly what to fix. The composite is the equal-weighted mean of the pillars that could be scored, and every recommended fix carries the points it will recover.

You can also author new items and update existing ones from inside Catalog Center. Two views: Developer and Leadership.

7actual blockers, of 974

UpgradeAssist

Tells you what will break before you upgrade. UpgradeAssist pins the release knowledge for your target version at kickoff, then cross-references every documented change between your current and target release against your live instance, read-only.

Blockers surface first, grouped by app, so remediation is scoped before the upgrade begins. Re-verify re-reads only the unresolved items and leaves settled classifications untouched.

It also reads sys_upgrade_history_log, so customizations skipped in a previous upgrade do not silently re-break in this one.

Zurich → Australia974 changes checked
blockers7
affected41
manual review91
not applicable145
clear150
informational538
Seven of 974. The rest is noise you no longer have to read.
75.7%match rate on first run
core_company · 177 records115 variants → 176 canonical
Apple → Apple Inc.1,453 refs · 99%
Dell Inc. → Dell Technologies644 refs · 99%
Microsoft → Microsoft Corp.370 refs · 99%
auto-accepted84
needs review45
Matching rules, canonical catalog, lifecycle and a replayable run history all stay under your control.

Normalization

Cleans company, vendor, software, and asset data against a GeneWorks-curated global catalog of publishers, products, versions, and lifecycle data — kept current by eighteen dedicated agents.

High-confidence matches auto-accept; the rest enter a review queue where you accept, reject, or escalate each variant. Accepting approves a proposal — your instance data changes only when you apply the accepted candidates.

Governance

Every Optimize surface reads only.

Scores, findings, and roadmaps are produced without writing to the instance. Remediation is always a separate, explicit step: you accept a finding, it enters the six-stage delivery loop, and it passes both human gates before anything is packaged.

Can
Cannot
Score, classify and sequence findings
Apply a fix as part of a scan
Propose a remedy for every finding
Bulk-apply without a named approver
Normalize against the curated catalog
Change instance data before you apply it
One engine. Five products.
Design
Map the instance. Plan the change.
Build
Approved design to working configuration.
Verify
ATF and browser tests, with the evidence.
Optimize
Score catalog, CMDB, data and upgrades.
Ask Gene
Ask the instance anything, in plain English.

Start with a scan, not a project.

Connect a sub-production instance and run CMDB Assessment, Catalog Center, and UpgradeAssist read-only. You will have the scores and the roadmap the same day.

Run a read-only scan
No plugin · no MID Server · no install in your environment