Skip to content

Method

How the accelerators were built, and how they deploy.

Updated September 23, 2026

What the accelerators contain

PDI's accelerators package five things for each industry: a data model, source-to-target mappings, match and merge rules, data-quality rules, and adaptive-card workshops. They are built on Informatica's published Customer 360 and Industry 360 documentation (Business 360 Console documentation set, April and July 2026 releases; 40 PDFs, of which 23 model documents were parsed) and extended for each industry. Each business entity cites its source document, and 6,073 of the 6,330 fields cite a specific documentation page; the other 257 are industry extensions added by the accelerator.

Business-entity definitions / entity types63 / 38
Fields6,330
Relationships / hierarchies147 / 6
Match models / rules20 / 65
Data-quality standardization rules / attribute families35 / 23
Source-system families: public / enterprise18 / 42
Industry use cases / account profiles372 / 124
Adaptive cards / workshops132 / 10

How the use cases were mapped

372 use cases were mapped from 124 anonymized account profiles across fourteen industries. For each use case, the named source systems were assigned to a catalogued source-system family, and each business need was mapped to an attribute family and to the entities it lands on. Account profiles are never named or described. Four use cases are delivered as data-quality rules rather than as a mastered entity. One decision is recorded rather than modeled: user entitlements are not mastered, because they belong to identity and access management.

Source-to-target mappings

  • Column level, with page-level evidence: 364 mappings for NPPES NPI Registry, MedPro Systems, GLEIF LEI, SAP ECC / S/4HANA, Salesforce Sales and Service Cloud and GS1 Global Product Classification.
  • Element level: 53 mappings for HL7 FHIR R4, X12 834 enrollment, X12 837 claims, CMS CCLF claims files, FDA GUDID, NIPR Producer Database, CISAC ISWC / IPI, Dun & Bradstreet, NCES school data, 1EdTech OneRoster / Ed-Fi, GDS property codes and IATA / ARC / CLIA registries, confirmed per implementation.
  • Enterprise systems: 42 system families, such as core banking, policy administration, ERP and EHR, mapped at attribute-family level. Column names are confirmed from the customer's data dictionary.

Adaptive-card workshops

The data-model workshops are sequenced as adaptive cards. Each card asks one decision with two to four mutually exclusive options; the answer is logged in a decision register and becomes a configuration input. Industry card sets extend the core workshops where needed.

Party sub-types15 cards
Field inventory14 cards
Reference data12 cards
System-of-record matrix12 cards
Data-quality dimensions12 cards
Match families15 cards
Survivorship14 cards
Hierarchy13 cards
Publish12 cards
Stewardship13 cards
Total132 cards