Whitepaper · Education · Informatica Customer 360
Institution hierarchies and rostering identities, reconciled.
State-district-school hierarchies, educator and learner identities from rostering feeds, and product and license entitlements.
01 · Executive summary
The short version
- PDI delivers 9 education use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 3 anonymized account profiles.
- Each use case arrives pre-mapped: the 8 entities it can land on, the 9 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.
Education providers sell to one hierarchy and deliver to another. Contracts are signed at the state or district level, usage happens at the school and classroom, and identities arrive through rostering feeds that change every term. A product and license record ties them together.
The accelerator lands institution hierarchies and rostering identities on Customer 360, anchored to public reference sources where they exist, such as NCES institution identifiers and the OneRoster standard. Content and license entitlements are modeled alongside, so contracts, schools and usage resolve to one hierarchy.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Organization4 use cases
- Person4 use cases
- Category3 use cases
- Item3 use cases
- Product3 use cases
- Legal Entity2 use cases
- Agreement2 use cases
- Creative Work2 use cases
Source-to-target mappings
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- NCES school dataElement-level mappings, confirmed per implementation
- 1EdTech OneRoster / Ed-FiElement-level mappings, confirmed per implementation
- 6 enterprise system familiesERP item / customer / vendor master, E-commerce / web accounts, Licensing / provisioning / billing, PIM, CRM, Contract / bid / co-op pricing systems. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 11 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
9 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 |
|---|---|---|
| Course & Product Catalog MDM | E-commerce / web accounts | Category, Item, Product |
| Educator & Student Rostering Identity | 1EdTech OneRoster / Ed-Fi | Person |
| Educator & Student identity (rostering) | 1EdTech OneRoster / Ed-Fi | Person |
| Institution 360 (district/school hierarchy) | Salesforce Sales and Service Cloud, NCES school data, ERP item / customer / vendor master | Hierarchy relationships, Legal Entity, Organization |
| Institution 360 (state → district → school hierarchy) | Salesforce Sales and Service Cloud, NCES school data, ERP item / customer / vendor master, E-commerce / web accounts | Hierarchy relationships, Legal Entity, Organization |
| Learner 360 (course → certification) | E-commerce / web accounts | Person, Organization |
| Organization / Employer Account MDM (incl. DoD & federal) | CRM, Contract / bid / co-op pricing systems | Organization, Person |
| Product & License Entitlement MDM | Licensing / provisioning / billing, ERP item / customer / vendor master, E-commerce / web accounts | Category, Item, Product, Agreement, Creative Work |
| Product, Content & License Entitlement MDM | Licensing / provisioning / billing, ERP item / customer / vendor master, PIM | Category, Item, Product, Agreement, Creative Work |
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 education model is already drawn: 8 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
- Institution 360 (state, district and school hierarchy)
- Source system 1
- Salesforce (Sales/Service Cloud)
- Source system 2
- NCES public institution reference data
- Lands on
- Organization with Parent/Child hierarchy relationships; Contact for institutional buyers
- What it proves
- A contract-to-school hierarchy anchored to a public institution identifier rather than to free-text account names.
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. 6 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.