Whitepaper · Insurance · Informatica Customer 360
Policyholder, producer and property in one governed view.
Customer and household views across products, insured property and location, producer and agency masters, and partner networks.
01 · Executive summary
The short version
- PDI delivers 24 insurance use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 8 anonymized account profiles.
- Each use case arrives pre-mapped: the 17 entities it can land on, the 17 source-system families it draws from, and the match and data-quality rules for those entities.
- Design decisions are captured in adaptive-card workshops: 132 cards across 10 data-model workshops, so every answer becomes a configuration input.
- The entry point is a $50,000 fixed-fee MDM implementation for any two source systems. Informatica licensing is procured separately.
02 · The master-data problem
Where the records disagree.
Carriers see the same customer through policy administration, claims, billing and the agency channel. Each system holds a different slice: the household, the insured property, the producer who wrote the business. A cross-product view needs all of them to resolve to the same parties and places.
The accelerator lands these use cases on Customer 360 for Insurance, with Agreement, Structure, Land Vehicle, Household and Product Specification. Producer and agent masters carry licensing, carrier appointment and E&O data, including the NIPR public producer source, and parcel identifiers extend Structure for insured property.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Organization20 use cases
- Person17 use cases
- Agreement10 use cases
- Location3 use cases
- Structure2 use cases
- Household1 use case
- Legal Entity1 use case
- HCP1 use case
- HCO1 use case
- Practitioner Role1 use case
- +7 moreLand Vehicle, Category, Item, Product, Payer, Member, Contract
Source-to-target mappings
- X12 837 claimsElement-level mappings, confirmed per implementation
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- NIPR Producer DatabaseElement-level mappings, confirmed per implementation
- NCES school dataElement-level mappings, confirmed per implementation
- 13 enterprise system familiesPolicy administration, Contract / bid / co-op pricing systems, Claims platform / TPA feeds, Agency management, Licensing / provisioning / billing, MGA bordereaux feeds, ERP item / customer / vendor master, CRM…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 42 match rulesIn the library for the entity types in play, ranked from exact keys to fuzzy name-and-address matching.
- 35 standardization rulesAcross 23 attribute families: names, addresses, phones, emails, identifiers and more.
- 132 adaptive cards10 data-model workshops, from party sub-types to stewardship.
04 · Use-case accelerator map
23 patterns, each with a landing.
Every pattern below is delivered on Informatica Customer 360 with PDI's accelerators. Patterns are anonymized from account profiles; a count such as 3× means the pattern recurs across profiles. Source systems are shown as system families.
| Use case pattern | Typical source systems | Lands on |
|---|---|---|
| Agent / Producer MDM2× | Agency management, NIPR Producer Database | Hierarchy relationships, Organization, Person |
| Account Rep & Agent MDM | Agency management, NIPR Producer Database | Hierarchy relationships, Organization, Person |
| Agent / Agency MDM | Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud | Hierarchy relationships, Organization, Person |
| Agent / Broker MDM | Agency management, Contract / bid / co-op pricing systems, NIPR Producer Database | Hierarchy relationships, Organization, Person |
| Carrier & Reinsurer Partner MDM | MGA bordereaux feeds, ERP item / customer / vendor master | Organization |
| Contract Holder / Consumer 360 | X12 837 claims, Claims platform / TPA feeds | Person, Organization, Agreement |
| Contractor / Technician Network MDM | Field service / dispatch, Contract / bid / co-op pricing systems | Person, Organization, Agreement |
| Customer / Household 360 | Salesforce Sales and Service Cloud, Policy administration, CDP / marketing automation | Hierarchy relationships, Organization, Person, Household |
| Dealer & Agent MDM | Contract / bid / co-op pricing systems, Dealertrack / RouteOne, Salesforce Sales and Service Cloud | Organization, Hierarchy relationships, Person |
| Employer Group Account MDM (school districts) | CRM, Health-plan core admin, NCES school data | Payer, Hierarchy relationships, Organization, Person, Member |
| Health Provider Network MDM | X12 837 claims, Claims platform / TPA feeds | HCP, HCO, Practitioner Role, Organization |
| Insured & Policy Party MDM | MGA bordereaux feeds, Policy administration, X12 837 claims, Claims platform / TPA feeds | Hierarchy relationships, Person, Legal Entity, Agreement |
| Insured Location MDM | Policy administration, Regulatory / registry feeds | Hierarchy relationships, Location, Agreement |
| Insured Property / Location MDM | Policy administration, Regulatory / registry feeds | Hierarchy relationships, Structure, Location, Agreement |
| Multinational Policyholder 360 (Spanish-name matching) | Policy administration, X12 837 claims, Claims platform / TPA feeds, Salesforce Sales and Service Cloud | Hierarchy relationships, Person, Organization, Agreement |
| Policyholder & Account 360 | Policy administration, Licensing / provisioning / billing, X12 837 claims, Claims platform / TPA feeds | Hierarchy relationships, Person, Organization, Agreement |
| Policyholder & Property Location MDM (geocoding) | Confirmed in discovery | Hierarchy relationships, Person, Organization, Structure, Location |
| Policyholder / Employee 360 across products | Policy administration, Health-plan core admin, Salesforce Sales and Service Cloud | Hierarchy relationships, Person, Organization, Category, Item |
| Policyholder / Ministry 360 | Policy administration, Licensing / provisioning / billing, X12 837 claims, Claims platform / TPA feeds | Hierarchy relationships, Person, Organization, Agreement |
| Producer / Agent MDM | NIPR Producer Database, Agency management | Hierarchy relationships, Organization, Person |
| Program / MGA Partner MDM | MGA bordereaux feeds, Contract / bid / co-op pricing systems, Policy administration | Organization, Agreement |
| Utility & Municipal Affinity Partner MDM | Contract / bid / co-op pricing systems, Licensing / provisioning / billing, ERP item / customer / vendor master | Organization |
| Vehicle (VIN) Asset MDM | Contract / bid / co-op pricing systems | Land Vehicle |
05 · How it deploys
Five steps, each already built.
The accelerator replaces blank-page design with decisions, a drawn model and pre-built mappings.
- Decide
Adaptive-card workshops capture the design. 10 data-model workshops, 132 cards. Each card asks one decision with two to four mutually exclusive options, and each answer is logged as a configuration input.
- Model
The insurance model is already drawn: 17 entities, with their relationships and hierarchies, selected for the use cases in this paper.
- Map
The two sources arrive pre-mapped. 364 column-level mappings cover NPPES, MedPro, GLEIF, SAP, Salesforce and GS1, and 60 source-system families are catalogued in all.
- Match
Match, merge and quality rules start from a library: 20 match models with 65 rules, and 35 standardization rules across 23 attribute families.
- Prove
Tenant checks and acceptance. 80 documentation discrepancies are confirmed on the tenant before configuration is generated, and the acceptance measures agreed in discovery are tested.
This Customer 360 industry entry offer is distinct from the separately scoped Informatica MDM MVP.
06 · The two-source entry point
How a $50K MVP lands here.
A fixed-fee MDM implementation for two source systems. The model, the mappings, the match and data-quality rules and the workshop cards exist before the engagement starts.
- Starting pattern
- Policyholder and household 360
- Source system 1
- Policy administration system
- Source system 2
- Salesforce (Sales/Service Cloud)
- Lands on
- Person, Organization and Household with Agreement from Customer 360 for Insurance
- What it proves
- One household and one policyholder across policy administration and the CRM, ready for cross-product views.
The $50,000 covers PDI professional services only. Informatica licensing is procured separately through Informatica. Additional sources, domains or scope changes after configuration begins are estimated separately. The example sources are illustrative; any two source systems qualify, and the pair is confirmed in discovery.
07 · Confirmed in discovery
What each engagement settles first.
- The two source systems. 13 enterprise system families appear in this industry. Their column names are confirmed from the customer's data dictionary before mappings are finalized.
- The tenant. 80 documentation discrepancies across the model are confirmed on the customer's tenant before configuration is generated, including field-group internal IDs that are read from tenant metadata.
- Package order. Industry packages are imported before any customization, because importing an industry package overwrites existing Customer 360 customization.
- Acceptance. Acceptance measures are agreed in discovery, before the fee is committed.
08 · Method
How this paper was built.
The use-case map, data model, mappings and rules come from PDI's accelerator, built on Informatica's published Customer 360 and Industry 360 documentation (April and July 2026 releases) and extended for each industry. Use cases are anonymized from 124 account profiles; no account is named. Adaptive-card counts come from PDI's Customer 360 data-model workshop set. The paper states no project durations or outcome figures; those are set as acceptance measures in discovery.