Whitepaper · Energy & Environmental Services · Informatica Customer 360
Customers, sites and assets across acquired operations.
Commercial, fleet and residential customers; ship-to and service locations after acquisitions; fuel and lubricant catalogs; and site assets.
01 · Executive summary
The short version
- PDI delivers 15 energy & environmental services use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 5 anonymized account profiles.
- Each use case arrives pre-mapped: the 9 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.
Fuel distribution, waste and environmental-services operators often grow by acquisition. Each acquired operation brings its own customer file, site list and product codes, and the same commercial customer can appear as separate accounts at every delivery location.
The accelerator masters customers, suppliers and fuel and lubricant catalogs, rolls delivery sites up to accounts, and models municipal contracts. Tanks, containers, trucks and permitted land-application fields are modeled as assets tied to the sites they serve.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Person7 use cases
- Organization7 use cases
- Location5 use cases
- Asset3 use cases
- Category3 use cases
- Item3 use cases
- Product3 use cases
- Supplier2 use cases
- Agreement1 use case
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
- 10 enterprise system familiesERP item / customer / vendor master, CRM, IoT / telematics / DCIM / tank monitoring, Fuel ERP / dispatch / route / OPIS feeds, Contract / bid / co-op pricing systems, Field service / dispatch, Market data, Licensing / provisioning / billing…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 7 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
15 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 |
|---|---|---|
| Asset MDM (containers, trucks, landfills, MRFs) | IoT / telematics / DCIM / tank monitoring | Asset |
| Customer & Generator Site 360 (municipal WWTPs, food processors) | ERP item / customer / vendor master, CRM | Person, Organization, Location |
| Customer & Service Location 360 (acquisitions) | Licensing / provisioning / billing, CRM, Salesforce Sales and Service Cloud | Person, Organization, Location |
| Customer & Ship-to Site 360 (roll-up) | ERP item / customer / vendor master, SAP ECC / S/4HANA, Salesforce Sales and Service Cloud | Person, Organization, Location |
| Customer 360 (commercial fleet, farm, residential heating) | ERP item / customer / vendor master, Fuel ERP / dispatch / route / OPIS feeds, CRM | Person, Organization |
| Customer 360 (commercial fuel, heating, cardlock) | ERP item / customer / vendor master, Fuel ERP / dispatch / route / OPIS feeds, CRM | Person, Organization |
| Delivery Site & Tank Asset MDM | Field service / dispatch, IoT / telematics / DCIM / tank monitoring | Asset, Location |
| Hauler / Vendor MDM | ERP item / customer / vendor master, IoT / telematics / DCIM / tank monitoring | Supplier, Organization, Person |
| Land Application Field & Permit Asset MDM | Property management / leasing | Asset |
| Municipal Contract MDM | Contract / bid / co-op pricing systems, ERP item / customer / vendor master | Agreement |
| Product / Fuel & Lubricant Catalog MDM | ERP item / customer / vendor master, Market data | Category, Item, Product |
| Product / Fuel & Lubricant MDM | ERP item / customer / vendor master, Contract / bid / co-op pricing systems | Category, Item, Product |
| Product / Lubricant SKU MDM | ERP item / customer / vendor master | Category, Item, Product |
| Station & Site Location MDM | E-commerce / web accounts | Location |
| Supplier MDM | ERP item / customer / vendor master | Supplier, Organization, 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 energy & environmental services model is already drawn: 9 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 and ship-to site 360 (roll-up)
- Source system 1
- ERP or fuel-industry ERP
- Source system 2
- CRM
- Lands on
- Organization and Person with Location; hierarchy relationships for account-to-site roll-up
- What it proves
- Each commercial customer as one account with its delivery sites beneath it, instead of one account per site.
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.