Whitepaper · Manufacturing · Informatica Customer 360
Material, supplier and channel masters that survive the ERP program.
Product and material masters from PLM to ERP to commerce, supplier and co-packer masters, dealer and distributor 360, and serialized install base.
01 · Executive summary
The short version
- PDI delivers 42 manufacturing use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 14 anonymized account profiles.
- Each use case arrives pre-mapped: the 15 entities it can land on, the 12 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.
Manufacturers describe the same product in PLM, the ERP, the PIM and the dealer portal, and buy from the same supplier under several vendor numbers. ERP consolidations and acquisitions expose those differences at the worst moment: during cutover.
The accelerator puts product, material and supplier masters on Material 360, the product model and Supplier 360 with its SAP extension, and dealer and distributor views on the Organization model. Installed equipment, bills of material and utility test data are modeled as well. SAP and Salesforce sources arrive with column-level mappings.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Organization25 use cases
- Person21 use cases
- Category14 use cases
- Item14 use cases
- Product14 use cases
- Supplier8 use cases
- Material4 use cases
- Asset4 use cases
- Location2 use cases
- Legal Entity2 use cases
- +5 moreBond, Equity, Medicinal Product, Packaged Medicinal Product, Pharmaceutical Product
Source-to-target mappings
- SAP ECC / S/4HANAColumn-level mappings with page-level evidence
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- 10 enterprise system familiesERP item / customer / vendor master, PLM / CAD-PDM, E-commerce / web accounts, PIM, Contract / bid / co-op pricing systems, IoT / telematics / DCIM / tank monitoring, Field service / dispatch, CRM…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 21 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
38 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 |
|---|---|---|
| Supplier MDM3× | ERP item / customer / vendor master, SAP ECC / S/4HANA | Supplier, Organization, Person |
| Product / Item (GTIN/UPC) MDM2× | ERP item / customer / vendor master, PIM | Category, Item, Product |
| Supplier & Co-Packer MDM2× | ERP item / customer / vendor master | Supplier, Organization, Person |
| Channel Partner 360 (dealers, distributors, integrators) | Salesforce Sales and Service Cloud, Contract / bid / co-op pricing systems, E-commerce / web accounts | Organization |
| Consumer & Product Registration 360 | E-commerce / web accounts | Person, Organization, Category, Item, Product |
| Consumer 360 (DTC stores, e-commerce, resale) | E-commerce / web accounts, Casino loyalty / CMS | Person, Organization, Location |
| Customer & Dealer 360 | Salesforce Sales and Service Cloud, CDP / marketing automation, ERP item / customer / vendor master | Person, Organization |
| Customer & Dealer 360 (big-box, distributors) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master | Person, Organization |
| Customer & Distributor 360 | CRM, ERP item / customer / vendor master | Person, Organization |
| Customer & Distributor 360 (design registration) | Salesforce Sales and Service Cloud, E-commerce / web accounts, Contract / bid / co-op pricing systems | Person, Organization |
| Customer & Distributor 360 (distributors, utilities) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, E-commerce / web accounts | Person, Organization |
| Customer / Utility 360 | Salesforce Sales and Service Cloud, ERP item / customer / vendor master | Organization, Person |
| Customer 360 | CRM, ERP item / customer / vendor master | Person, Organization |
| Customer 360 (distributors, fabricators, A&D specifiers) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master | Person, Organization |
| Customer, Retailer & Distributor Hierarchy MDM | E-commerce / web accounts | Hierarchy relationships, Person, Organization, Legal Entity |
| Dealer & Customer 360 | Salesforce Sales and Service Cloud, CRM, Contract / bid / co-op pricing systems | Person, Organization |
| Installed Device / Asset MDM (smart meters, leak detection) | IoT / telematics / DCIM / tank monitoring, Field service / dispatch | Asset |
| Instrument Install Base MDM | ERP item / customer / vendor master | Bond, Equity, Asset |
| OEM & Dealer 360 | Salesforce Sales and Service Cloud, Contract / bid / co-op pricing systems | Organization |
| Parts & Product MDM | SAP ECC / S/4HANA, ERP item / customer / vendor master | Category, Item, Product |
| Product & Material MDM | SAP ECC / S/4HANA, PLM / CAD-PDM | Category, Item, Product, Material |
| Product & Specification MDM (UN ratings, linings) | ERP item / customer / vendor master | Category, Item, Product |
| Product (Decor, Color & Finish) MDM + PIM | SAP ECC / S/4HANA, ERP item / customer / vendor master, PIM | Category, Item, Product |
| Product / Material MDM | ERP item / customer / vendor master, PLM / CAD-PDM, PIM | Category, Item, Product, Material |
| Product / Material MDM (PLM → ERP → PIM/e-commerce) | SAP ECC / S/4HANA, ERP item / customer / vendor master, PLM / CAD-PDM, PIM | Category, Item, Product, Material |
| Product / Material MDM (global SKUs) | PLM / CAD-PDM | Category, Item, Product, Material |
| Product / Part & BOM MDM (multiple brands) | SAP ECC / S/4HANA, ERP item / customer / vendor master, PLM / CAD-PDM, PIM | Category, Item, Product |
| Product / Part MDM (part numbers, compliance data) | SAP ECC / S/4HANA, ERP item / customer / vendor master, PLM / CAD-PDM | Category, Item, Product |
| Product / Style-Color-Size MDM | PLM / CAD-PDM, SAP ECC / S/4HANA, ERP item / customer / vendor master, PIM | Category, Item, Product |
| Product Configuration & BOM MDM | ERP item / customer / vendor master, PLM / CAD-PDM | Category, Item, Product |
| Retailer & Distributor Hierarchy MDM | E-commerce / web accounts, ERP item / customer / vendor master | Hierarchy relationships, Legal Entity, Organization |
| Rider / Consumer Registration 360 | Field service / dispatch | Person, Organization |
| Serialized Equipment / Install Base MDM | SAP ECC / S/4HANA, IoT / telematics / DCIM / tank monitoring, Field service / dispatch | Medicinal Product, Packaged Medicinal Product, Pharmaceutical Product, Asset |
| Store & Wholesale Partner MDM | ERP item / customer / vendor master | Location, Organization |
| Supplier / Chassis MDM | ERP item / customer / vendor master | Supplier, Organization, Person |
| Supplier / Foundry MDM | ERP item / customer / vendor master | Supplier, Organization, Person |
| Supplier MDM (steel coil, resin) | ERP item / customer / vendor master | Supplier, Organization, Person |
| Utility Asset & Test Data MDM (transformers, breakers) | IoT / telematics / DCIM / tank monitoring | Asset |
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 manufacturing model is already drawn: 15 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
- Supplier master
- Source system 1
- SAP (vendor master)
- Source system 2
- Second ERP or procurement system
- Lands on
- Supplier with Sub-Supplier and Supplier-to-Contact relationships, using the accelerator's SAP column mappings
- What it proves
- One supplier record per legal supplier across two ERPs, ready for spend, risk and ESG reporting.
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. 10 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.