Q

2.0

🗂️ Entity 360 — Identity & Master Data Golden Records Governance · Vigil
Proven at government scale · CalHHS · 25M citizens · 8 programs

One entity. Every system. Always current.

Identity resolution, automated.

Entity 360 resolves people, organizations, accounts, and assets across every system you own. Finds duplicates. Builds golden records. Maintains the source of truth for who is who — continuously, not quarterly.

Built for data stewards, MDM leads, and business owners who've given up trying to get Sales, Support, Billing, and Compliance to agree on which customer is which.

🗂️
Entity 360
Identity · MDM · Golden records
Resolving
MATCH CANDIDATES · 4 SOURCES
CRM Sarah A. Chen · sarah.chen@acme.com · 415-555-0109 0.98
BILLING Sara Chen · s.chen@acme.com · (415) 555-0109 0.96
SUPPORT Sarah Chen · sarahc@acme.com · 4155550109 0.94
MARKETING S. Chen · sarah_c@gmail.com · — 0.81
GOLDEN RECORD
entity_id: CUST_000_24107
Sarah A. Chen · sarah.chen@acme.com · +1 415 555 0109 · 4 sources merged
1 golden record created from 4 source records · lineage preserved · merge reversible.
Entity 360 at scale
One
Customer
One
Record
Every
Source
Fuzzy
Matching
Full
Audit Trail
Why Entity 360 Exists

Same customer. Seven different records.

"Sarah Chen" in the CRM. "Sara Chen" in billing. "S. Chen" in marketing. A support ticket under "sarahc@acme.com". A legacy record with a typo. Four teams, four versions. Nobody agrees. Reporting is a mess.

Entity 360 resolves this — automatically, continuously, with fuzzy matching, confidence scoring, and steward review for the edge cases. Every merge is auditable. Every unmerge is reversible. Every golden record is live.

Identity resolution isn't a migration. It's an operating state.

The old way
One citizen. Five IDs. Zero coordination. An MDM project that takes eighteen months and still isn't current.
01
Fragmented identity. One citizen, one member, one customer — represented five different ways across five different systems. Service gaps. Duplicate benefits. Fraud hiding in plain sight.
02
Repeated data entry. People tell their story five times. Caseworkers, agents, and reps work without context — while data conflicts quietly multiply across every silo.
03
No single truth. Manual merges in spreadsheets. No audit trail. No way to unmerge. Golden records computed once at migration, stale before lunch.
How Entity 360 Resolves

Ingest. Match. Merge. Govern.

A continuous loop — every new record ingested, every duplicate caught, every merge tracked.

1
📥
Ingest & Standardize
Pull records from every source system. Normalize names, phones, addresses, emails to comparable forms.
2
🔗
Match & Score
Fuzzy matching across fields. Confidence scores per candidate pair. Deterministic for exact, probabilistic for the rest.
3
🏆
Merge & Build
High-confidence candidates merge automatically into golden records. Edge cases route to stewards. Lineage is preserved.
4
⚖️
Govern & Publish
Golden records published back to consuming systems. Every change audited. Every merge reversible.
What Entity 360 Does

Identity resolution — continuously.

🔗
Cross-System Entity Resolution
Fuzzy matching across names, addresses, emails, phones, IDs — even when formats, spellings, or transliterations differ. Same person, different systems, one entity.
  • Deterministic and probabilistic matching
  • Multi-field weighted scoring
  • Configurable confidence thresholds
🏆
Golden Record Creation
Best-of-breed merging: latest phone from billing, verified email from marketing, canonical name from the compliance record. Survivorship rules per attribute, per domain.
  • Per-attribute survivorship rules
  • Source authority weighting
  • Continuous re-computation as sources change
🔍
Duplicate Detection
Surface hidden duplicates already living in your systems. Configurable thresholds for auto-merge, steward review, and ignore. Ranked by impact on joins, reporting, and compliance.
  • Rank duplicates by business impact
  • Auto-merge above threshold · review below
  • Scheduled and event-driven scans
↔️
Merge & Unmerge Workflows
Stewards approve, reject, or unmerge. Every decision captured with reason codes. When it turns out two records really were two people, unmerge restores them — with a full audit trail.
  • Reviewer queues with SLA
  • Reason-coded decisions
  • Full merge / unmerge audit history
🕸️
Relationship Mapping
Entities don't live alone. Households, organizations, beneficiaries, account holders, signatories — Entity 360 captures the graph, not just the nodes.
  • Household, org, and beneficiary graphs
  • Relationship type and direction
  • Query across relationships with Cezu
Qualix-Scored Identity Data
Entity 360 plugs into Qualix — every golden record gets a quality score across completeness, accuracy, and timeliness. Identity data gets the same rigor as every other dataset.
  • Per-entity quality scoring
  • Drift alerts on key fields
  • Trust-weighted consumption downstream
Golden Records · Live

Best of every source. One canonical truth.

A golden record isn't the winner of a matching round. It's a composite — the best verified email from one system, the most recent phone from another, the canonical legal name from compliance. Entity 360 computes it continuously, updates it as sources change, and publishes it back to the systems that need it.

  • Per-attribute survivorship with source authority
  • Lineage preserved — every value traced to its source record
  • Continuous re-computation as source systems update
  • Published back via API, reverse ETL, or direct connector
📥 FOUR SOURCE RECORDS
CRM Sarah A. Chen · sarah.chen@acme.com · 415-555-0109 latest edit
BILL Sara Chen · s.chen@acme.com · (415) 555-0109 typo
SUPPORT Sarah Chen · sarahc@acme.com · 4155550109 alt email
MKTG S. Chen · sarah_c@gmail.com · — personal
✓ GOLDEN CUST_000_24107
NAMESarah A. Chen ← CRM (authority)
EMAILsarah.chen@acme.com ← CRM
PHONE+1 415 555 0109 ← latest verified
ALT EMAILSs.chen@acme.com, sarahc@acme.com
SOURCES4 merged · 0 flagged
Beyond the Entity

Identity is a graph. Not a row.

Entity 360 captures relationships — who belongs to whom, what accounts belong to whom, who signs for whom.

🏠
Households
Group individuals by address, billing relationship, or family unit. Critical for financial services offers, pension beneficiaries, and healthcare member households.
🏢
Organizations
Parent / subsidiary / division hierarchies. Legal entities and operating units. Employer of record for members. The org graph that makes B2B reporting sane.
👥
Beneficiaries & Signatories
Account holders, beneficiaries, authorized signers, power of attorney. Critical for pension, benefits, estate, and financial services domains.
Case Study · Government Scale

One citizen. One record. Every program.

The California Central Citizen Registry (CCR) runs on Entity 360 — resolving one citizen across every health and human services program in the state. Eight systems. Tens of millions of records. One identity that follows the citizen, not the form.

25M
Total Entities
21M
Golden Records
87%
Data Quality Score
8
Source Programs
⚠ The Member Identity Crisis
Disconnected data. Disconnected care. Disconnected accountability.
Fragmented identity = fragmented care. One citizen, five IDs, zero coordination across programs.
Disconnected systems = disconnected services. Caseworkers can't see the full picture — service gaps and duplicative interventions.
Repeated data entry = repeated frustration. Citizens tell their story five times while conflicts persist across silos.
No single truth = no accountability. Duplicate benefits, compliance blind spots, fraud vulnerabilities — costing taxpayers millions.

Three records come in. Three outcomes go out.

Every incoming record routes to the right path — automatically.

✓ AUTO-MERGE · 94%
High-Confidence Match
Nickname variation · Michael vs Mike
MEDI-CAL Michael A Johnson · DOB 1982-02-18 · SSN 567-89-1234
CalSAWS Mike A Johnson · DOB 18-02-1982 · SSN 567-89-1234
94%
100 SSN+DOB · 89 Name · 95 Addr
Auto-merged · UCI CCR-2024-1234567
⚠ STEWARD REVIEW · 73%
Ambiguous Match
Different surname · shared SSN & DOB
MEDI-CAL Bob David Martinez · SSN 123-45-9876 · Miami FL
HOUSING Robert David Anderson · SSN 123-45-9876 · San Francisco
73%
Below 85% threshold · review required
Routed to steward · reason coded
+ NEW MASTER · 0%
No Match · First-Time Enrollment
Net-new citizen · no prior record
CalHEERS Jennifer Lin Chen · DOB 1992-11-08 · SSN ***-**-9854
CCR No match · SSN, DOB, name, phonetic, address all searched
96%
DQ score · all fields complete
+ New UCI created · CCR-2024-8765432

What makes the CCR defensible.

The technical decisions that turn a matching service into a registry of record — auditable, reversible, privacy-preserving.

🧮 Intelligent Matching
  • Fellegi-Sunter probabilistic scoring
  • Phonetic match · Soundex & Metaphone
  • Configurable thresholds & blocking
  • Multi-field composite scoring
📋 Complete Audit Trail
  • Full merge / unmerge lineage
  • Field-level change history
  • SCD patterns for point-in-time
  • Compliance-ready documentation
🔒 Privacy-First Design
  • Federated architecture
  • Demographics only · no eligibility
  • Program-level correlation IDs
  • UCI correlates · never centralizes
Performance Optimized
  • Hash-based entity lookup
  • Recursive CTE for merge chains
  • Intelligent blocking strategy
  • Cached Entity 360 views
UCI correlates program IDs — demographics stored once, linked many times
Medi-Cal
CIN · M123…
CalSAWS
CID · C987…
CalHEERS
EID · E777…
Housing
HID · H555…
✓ UCI
CA-7829431
Use Cases

Where Entity 360 earns its keep.

🏛️
Citizen 360 · HHS Programs
Medicaid · benefits · housing · enrollment
One citizen, one UCI, every program. Fragmented identity across Medicaid, SNAP, TANF, housing, and exchange systems becomes a single correlated record — without centralizing eligibility. Duplicate benefits surface. Fraud patterns surface. Coordinated care becomes possible.
✓ One citizen, one identity, every program
🎯
Customer 360
Sales · Marketing · Support · Billing
One customer identity across every system. Sales sees support tickets. Support sees billing history. Marketing stops sending three emails to the same person. Reporting stops overcounting.
✓ A customer view every team trusts
🏦
Pension & Beneficiary Resolution
Public pension · benefits programs
Members and their beneficiaries across legacy retirement, health, and payroll systems. Duplicate SSNs resolved. Household relationships preserved. Benefits paid to the right person.
✓ Every beneficiary, uniquely identified
⚕️
Patient / Member Identity
Payers · providers · claims networks
Same patient across EMR, claims, eligibility, and pharmacy feeds. Same member across every plan year. Duplicate patient safety risks surfaced before a claim is denied for the wrong reason.
✓ Longitudinal records, accurately stitched
🛡️
AML / KYC & Risk
Banks · asset managers · insurers
One identity for every accountholder across every product. Beneficial ownership graphs. Sanctioned-party screening on the golden record, not on each source copy. Cleaner risk, cleaner audits.
✓ KYC on one entity · across every product
Why Entity 360

Not another MDM tool.

Entity 360 is a governance module in a unified platform — not a two-year migration project that needs its own catalog, quality engine, and semantic layer.

Continuous · not batch
Resolves identity as records land. No overnight merge job. No eighteen-month migration. The master is current by lunchtime.
Fuzzy by default
Names misspelled. Phones reformatted. Emails aliased. Entity 360 handles the messy 90% without hand-written rules.
Reversible merges
Every merge decision has a reason and a timestamp. When it turns out two records really were two people, unmerge restores them.
Same semantic layer
"Customer" is defined once, in xAQUA's shared semantic layer. Entity 360 resolves that definition — not an MDM-specific one.
Plugs into Qualix
Every golden record gets a 7-dimension quality score. Drift on key fields alerts stewards. Identity data held to the same bar.
Relationships · not just records
Households. Orgs. Beneficiaries. Signatories. Graph-native from day one, not a feature bolted on.
Entity 360 + Vigil

Entity 360 resolves. Vigil governs.

Entity 360 is the resolution engine. Vigil — xAQUA's AI Data Governance Agent — turns stewardship work into something conversational, triages merge queues, and keeps the human-in-the-loop fast.

Ask Vigil: "find duplicate customers across CRM and billing." Vigil runs the resolution, returns the ranked duplicates, opens the steward queue, and reports back when it's clean.

Meet Vigil · The AI Data Governance Agent →
Ask Vigil Governance Agent
👤
Find duplicate customers across CRM and billing.
Scanned 284K CRM records and 261K billing records.

· 1,847 high-confidence duplicates (score > 0.95) · auto-merged
· 312 candidates (0.80–0.95) · routed to stewards
· 26 golden records updated downstream

Report #ER-3391 logged. CRM and billing now agree on 99.3% of shared identities.

Stop arguing about who's who.

See Entity 360 resolve a live set of records across four source systems, build golden records with preserved lineage, and publish them back — in under fifteen minutes.