GeneWorks product suite
geneworks design

Plan with clarity.

Design makes an instance legible and a change into a plan. It reads everything, traces what connects to what, and answers the question nobody can answer by hand: if I change this, what breaks?

Map your instance Read the documentation
Command Center · instance mapread-only · 2d ago
tables168
shared foundations46
connections traced8,634
since last map+0 −0 · 1 busier
queryadd a field to Incident
objects impacted15
SLAs, notifications, business rules, and two integrations. Found before anyone touched the form.
8,634
connections traced in a typical mid-size instance
15 of 8,634
objects a single field change actually touched
96.2%
of a scanned Incident app was untouched baseline
The problem

Most ServiceNow estates have outgrown the people who understand them.

The original architects have moved on. The documentation describes an instance that no longer exists. The only reliable way to find out what a change will break is to make it and see what stops working on Monday.

Design replaces that with a current, read-only picture you can interrogate before anyone writes a line. It is the entry point for every other product, because nothing should be built against a platform nobody can see.

168tables mapped

Command Center

Reads your entire instance and renders it as one graph — every application, table, and shared foundation, and the connections between them. It opens on the map and adds four more lenses over the same data.

  • Collisions — ask what happens if you change something, and the agents trace the blast radius across everything it connects to.
  • Dead weight — unused, orphaned, and duplicated configuration, ranked as retirement candidates.
  • Activity — what changed recently, and where the platform is getting busier.
  • Upgrade — a fast read on release exposure, feeding UpgradeAssist for the full analysis.
Ask the mapplain English · live graph
What stands on sys_user?37 objects
Impact of mandatory priority?9 objects
Sketch a returns appdraft design
No query language, no schema knowledge. Tracing 8,634 connections to find the 15 that matter is not hand work.
741artifacts catalogued
Incident ManagementZurich · 7/7 areas scanned
baseline (out-of-the-box)713
customized28
custom (added here)0
automations147
relationships1,043
96.2% baseline. Customizations concentrate in Security & access (15) and Process & automation (6) — the upgrade heat map.

Application Explorer

An x-ray of a single application. Explorer reads an app end to end and shows how it is actually built — out-of-the-box versus modified versus net-new — and where the customizations concentrate.

It is the fastest way to understand an app you did not build, and the foundation for any upgrade review. When the instance shifts underneath you, Explorer prompts a re-scan.

11document types

Document Builder

Every delivery document, written from live instance state rather than a blank template. Pick a type, answer a short set of questions, and the agents produce a complete, sectioned document you can download.

Because the content comes from what is actually there, it is accurate the day it is written — and it stays accurate as long as you regenerate it.

GroupDocuments
AssessHealth Check Report · Upgrade Assessment Report
DeliverAs-Built Documentation · Data Dictionary · Integration Specification · Runbook · Security & Access Design · Standard Operating Procedure · Statement of Work · Technical Design Document · Test Plan
8risk dimensions scored
Impact analysisruns before the design gate
H1 Business rules & logicelevated
H2 SLA timersclear
H4 Approval workflowsclear
H7 Integration pointselevated
H8 Security & ACLsclear
MEDIUM — the build pauses mid-execution for review. HIGH does not start at all until you rescope or authorise it.

From picture to plan

Design ends where the delivery loop begins. A requirement — a story, a CSV, plain English, or a finding exported from Optimize — becomes a structured, versioned specification, then a full solution design: data model, dependencies, ACL implications, integration shape, exact artifacts, and an explicit list of assumptions.

Impact analysis runs in parallel across eight health dimensions. Your architect signs off before anything is built, and a named approver is recorded.

Governance

Design never writes.

Every scan reads system tables, the dictionary, audit records, and configuration to build a map, a score, or a set of findings — and writes nothing back. The first write in any workflow happens in Build, after a named human approves the design.

Can
Cannot
Read the instance to map, score, classify
Write anything during a scan
Trace dependencies read-only, on demand
Change a record to find out what breaks
Produce a design and a named approver record
Proceed to build without that approval
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.

See your instance as it actually is.

Connect a sub-production instance and Command Center maps it the same day. Bring the app nobody wants to touch.

Map your instance
No plugin · no MID Server · no install in your environment