Whitepaper · Business & Professional Services · Informatica Customer 360
One client, one hierarchy, every conflict check.
Client and related-entity hierarchies, consultant and candidate identities, and roll-ups of customer sites after acquisitions.
01 · Executive summary
The short version
- PDI delivers 27 business & professional services use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 9 anonymized account profiles.
- Each use case arrives pre-mapped: the 12 entities it can land on, the 14 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.
In professional services, the commercial record and the risk record are the same record. The client account that sales updates is the one that conflicts, independence and off-limits checks depend on. When it lives separately in the CRM, the practice-management system and finance, each check runs against a partial picture.
The accelerator covers the three motions these firms run: client and related-entity hierarchies; person masters for candidates, consultants and technicians; and consolidation of customer sites after acquisitions. Engagement, project and inspected-equipment masters are modeled as well, so the practice's operating records connect to the same client.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Person15 use cases
- Organization8 use cases
- Location5 use cases
- Legal Entity4 use cases
- Asset3 use cases
- Creative Work3 use cases
- Agreement2 use cases
- Category1 use case
- Item1 use case
- Product1 use case
- +2 moreMaterial, Structure
Source-to-target mappings
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- SAP ECC / S/4HANAColumn-level mappings with page-level evidence
- Dun & BradstreetElement-level mappings, confirmed per implementation
- 11 enterprise system familiesCRM, HCM / payroll, ERP item / customer / vendor master, PSA / project, ATS / VMS, Field service / dispatch, Licensing / provisioning / billing, Computerized Criminal History…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 23 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
24 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 |
|---|---|---|
| Employee Skills & Resource MDM2× | HCM / payroll, PSA / project | Person |
| Equipment / Asset MDM (inspection & compliance)2× | Field service / dispatch | Asset |
| Technician & Branch MDM2× | HCM / payroll, ERP item / customer / vendor master | Person, Location |
| Candidate / Consultant 360 | ATS / VMS, SAP ECC / S/4HANA | Person |
| Candidate / Executive Talent 360 (person MDM) | ATS / VMS, CRM | Person |
| Client & CPA Referral Partner MDM | Salesforce Sales and Service Cloud, CDP / marketing automation | Organization |
| Client & PE Portfolio Hierarchy MDM (conflicts) | Salesforce Sales and Service Cloud, CRM | Hierarchy relationships, Legal Entity |
| Client & Related-Entity MDM (independence / conflicts) | Salesforce Sales and Service Cloud, CRM, Computerized Criminal History | Hierarchy relationships, Person, Organization, Legal Entity |
| Client Account & Hierarchy MDM (off-limits / conflicts) | Salesforce Sales and Service Cloud, CRM, SAP ECC / S/4HANA, ERP item / customer / vendor master | Hierarchy relationships, Person, Organization, Agreement, Legal Entity |
| Client Account 360 (post-acquisition) | PSA / project, CRM | Person, Organization |
| Client Account Hierarchy MDM (commercial + federal) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, HCM / payroll, PSA / project | Hierarchy relationships, Person, Organization, Agreement, Legal Entity |
| Consultant/Employee MDM | HCM / payroll, Licensing / provisioning / billing, ERP item / customer / vendor master | Person |
| Contact & Expert Network MDM | CRM | Person, Organization |
| Customer & Site 360 (roll-up consolidation) | Field service / dispatch, CRM | Person, Organization, Location |
| Customer & Site 360 (roll-up) | CRM | Person, Organization, Location |
| Customer Plant Asset MDM | IoT / telematics / DCIM / tank monitoring | Asset |
| Customer Site 360 | CRM, Contract / bid / co-op pricing systems | Location |
| Employee & Resource MDM | HCM / payroll, Licensing / provisioning / billing | Person |
| Engagement / Project MDM | Confirmed in discovery | Creative Work |
| Engagement MDM | ERP item / customer / vendor master | Creative Work |
| MRO Material / Parts Master MDM | SAP ECC / S/4HANA, ERP item / customer / vendor master | Category, Item, Product, Material |
| Project MDM | PSA / project | Creative Work |
| Property / Study Asset MDM | Confirmed in discovery | Structure |
| Skills & Job Taxonomy MDM | ATS / VMS, HCM / payroll | Data-quality rules |
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 business & professional services model is already drawn: 12 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
- Client account and related-entity hierarchy
- Source system 1
- Salesforce (Sales/Service Cloud)
- Source system 2
- ERP or practice-management system
- Lands on
- Organization with Parent, Child and Ultimate Parent hierarchy relationships; Person and Contact for client contacts
- What it proves
- A single client hierarchy that a conflicts or off-limits check can query, with every survivorship decision traceable to the source record.
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. 11 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.