Whitepaper · Software & Technology · Informatica Customer 360
Accounts, entitlements and partners, one customer truth.
Subscription customer 360, product and pricing catalogs, partner and reseller masters, legal-entity hierarchies, and entitlement and asset masters.
01 · Executive summary
The short version
- PDI delivers 39 software & technology use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 13 anonymized account profiles.
- Each use case arrives pre-mapped: the 17 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.
Software and technology companies bill, provision and support the same customer from separate systems. The account in the CRM, the subscription in billing and the entitlement in the provisioning platform drift apart with every renewal, merger and partner-sourced deal.
Customer and partner masters land on the Customer 360 core model, product and offer catalogs on the product model, and customer legal-entity hierarchies on Legal Entity 360 for Banking. Subscription and usage entitlements and hardware and network assets are modeled as well. User entitlements are deliberately not mastered: they belong to identity and access management, and the accelerator records that decision.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Organization19 use cases
- Person16 use cases
- Category9 use cases
- Item9 use cases
- Product9 use cases
- Agreement7 use cases
- Legal Entity6 use cases
- Asset4 use cases
- Creative Work3 use cases
- Supplier3 use cases
- +7 moreBond, Equity, Location, Structure, Medicinal Product, Packaged Medicinal Product, Pharmaceutical Product
Source-to-target mappings
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- GLEIF LEIColumn-level mappings with page-level evidence
- 12 enterprise system familiesLicensing / provisioning / billing, ERP item / customer / vendor master, CRM, Contract / bid / co-op pricing systems, Network / circuit inventory, monitoring-centre software, Property management / leasing, CDP / marketing automation, E-commerce / web accounts…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 32 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
39 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 |
|---|---|---|
| Allocator Firm & Contact MDM | Confirmed in discovery | Legal Entity, Hierarchy relationships, Person, Category, Item |
| Brand / Manufacturer Hierarchy MDM | Salesforce Sales and Service Cloud | Hierarchy relationships, Legal Entity, Supplier, Organization, Person |
| Channel / Reseller MDM (core processors) | Contract / bid / co-op pricing systems | Organization |
| Client & Legal Entity Hierarchy MDM (FCMs, prop firms, banks) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, Licensing / provisioning / billing, GLEIF LEI | Hierarchy relationships, Legal Entity |
| Customer & Contract 360 | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, Licensing / provisioning / billing | Person, Organization, Agreement |
| Customer & Service Location MDM (address / serviceability) | Licensing / provisioning / billing, CRM, Network / circuit inventory, monitoring-centre software | Person, Organization, Location |
| Customer & Subscription 360 | Salesforce Sales and Service Cloud, Licensing / provisioning / billing, CRM | Person, Organization, Agreement |
| Customer 360 | Salesforce Sales and Service Cloud, ERP item / customer / vendor master | Person, Organization |
| Customer 360 (banks, fintechs) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, Licensing / provisioning / billing | Person, Organization |
| Customer 360 (investment manager subscribers) | Salesforce Sales and Service Cloud, CDP / marketing automation, Licensing / provisioning / billing | Person, Organization |
| Customer 360 (law firms, corporate legal) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, CRM | Person, Organization, Agreement |
| Customer 360 (merged predecessor firms) | Salesforce Sales and Service Cloud, PSA / project | Person, Organization |
| Customer 360 (subscription accounts) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, CRM, Licensing / provisioning / billing | Person, Organization, Agreement |
| Customer Legal Entity Hierarchy MDM (banks, trading firms) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, GLEIF LEI | Hierarchy relationships, Person, Organization, Legal Entity |
| Data Syndication to Client CRMs | Salesforce Sales and Service Cloud, CRM | Data-quality rules |
| Fund & Security Reference Data MDM | Confirmed in discovery | Bond, Equity |
| Guest Profile Data (product-embedded) | CDP / marketing automation, CRM, Property management / leasing | Data-quality rules |
| Hardware Asset MDM (GPUs, servers, data center sites) | IoT / telematics / DCIM / tank monitoring, ERP item / customer / vendor master | Asset |
| Hotel Property & Chain Hierarchy MDM | Salesforce Sales and Service Cloud, Property management / leasing, ERP item / customer / vendor master, Licensing / provisioning / billing | Hierarchy relationships, Legal Entity, Structure |
| Installed Asset & Circuit Inventory MDM | Network / circuit inventory, monitoring-centre software | Asset |
| Instrument / Exchange Reference Data MDM | Market data | Bond, Equity |
| Issuer & Fund Legal Entity MDM (CIK, LEI) | GLEIF LEI | Hierarchy relationships, Legal Entity |
| Network Asset & Circuit Inventory MDM | Network / circuit inventory, monitoring-centre software, Licensing / provisioning / billing | Asset |
| Partner / Channel MDM | Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud | Organization |
| Partner / Reseller MDM | Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud | Organization |
| Product & Offer Catalog MDM | Licensing / provisioning / billing | Category, Item, Product |
| Product & Pricing Catalog MDM | Licensing / provisioning / billing, ERP item / customer / vendor master | Category, Item, Product |
| Product & Retail Channel MDM | ERP item / customer / vendor master, E-commerce / web accounts | Category, Item, Product, Organization |
| Product & Service Catalog MDM | ERP item / customer / vendor master, Licensing / provisioning / billing | Category, Item, Product |
| Product & Subscription Entitlement MDM | Licensing / provisioning / billing | Category, Item, Product, Agreement, Creative Work |
| Product & Usage Entitlement MDM | Licensing / provisioning / billing | Category, Item, Product, Agreement, Creative Work |
| Product / Item Attribute MDM (UPC taxonomy) | E-commerce / web accounts | Category, Item, Product |
| Product / OEM SKU Catalog MDM | ERP item / customer / vendor master | Category, Item, Product |
| Retailer & Store Location MDM | Confirmed in discovery | Location, Organization |
| Serialized Device / Asset MDM | Confirmed in discovery | Medicinal Product, Packaged Medicinal Product, Pharmaceutical Product, Asset |
| Subscriber / Consumer 360 | Licensing / provisioning / billing, Salesforce Sales and Service Cloud | Person, Organization |
| Supplier & Data Center Partner MDM | ERP item / customer / vendor master | Organization, Supplier, Person |
| User / Trader Identity & Entitlements | BSA/AML platform, Licensing / provisioning / billing | Person, Agreement, Creative Work |
| Vendor / OEM Partner MDM | Contract / bid / co-op pricing systems, ERP item / customer / vendor master | Organization, Supplier, Person |
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 software & technology 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
- Customer 360 (subscription accounts)
- Source system 1
- Salesforce (Sales/Service Cloud)
- Source system 2
- ERP or billing system
- Lands on
- Organization, Person and Contact from the core model with Parent/Child hierarchy relationships
- What it proves
- One customer account across CRM and billing, with the hierarchy needed for renewals and partner attribution.
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. 12 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.
- Entitlements. User entitlements are deliberately not mastered. They stay in the identity and access-management system of record.
- 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.