Whitepaper · Real Estate, Construction & Hospitality · Informatica Customer 360
Property, owner and guest, one record per relationship.
Property, unit and space masters; tenant, owner, buyer and guest 360; investor and fund legal entities; and trade, installer and channel partners.
01 · Executive summary
The short version
- PDI delivers 21 real estate, construction & hospitality use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 7 anonymized account profiles.
- Each use case arrives pre-mapped: the 12 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.
Real estate, homebuilding and hospitality businesses sell a place to a person through several systems: property management, reservations, sales and warranty, and channel partners. The same guest, owner or buyer appears in each, and the same property is described differently in each.
Tenant, owner, guest and buyer 360 land on the Customer 360 core model; investor and fund entities land on Legal Entity 360 for Banking. Property, unit and room inventory are configured on the Structure entity. Parcel identifiers, dock equipment and community-lot-home assets are modeled as well.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Person13 use cases
- Organization12 use cases
- Structure6 use cases
- Location2 use cases
- Asset2 use cases
- Supplier2 use cases
- Legal Entity1 use case
- Household1 use case
- Category1 use case
- Item1 use case
- +2 moreProduct, Agreement
Source-to-target mappings
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- 11 enterprise system familiesProperty management / leasing, ERP item / customer / vendor master, CRM, Field service / dispatch, CDP / marketing automation, E-commerce / web accounts, PLM / CAD-PDM, Fund administration / investor portal / loan admin…. 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.
- Gaming and hospitality player model15 source structures mapped to the model: party, names and contact points, identifiers, source cross-reference, loyalty account, online account, property affiliation, player value, card media, wallet account, host assignment, responsible-gaming restriction, KYC verification, consent preference, relationships and household.
04 · Use-case accelerator map
21 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 |
|---|---|---|
| Buyer / Customer 360 (lead → closing → warranty) | Salesforce Sales and Service Cloud, CRM, Field service / dispatch | Person, Organization |
| Channel / OTA Partner MDM | Property management / leasing | Organization |
| Community, Lot & Home Asset MDM | ERP item / customer / vendor master | Asset, Structure |
| Customer & Site 360 (national multi-location accounts) | Field service / dispatch, CRM | Person, Organization, Location |
| Customer / Household 360 across brands | Salesforce Sales and Service Cloud, CDP / marketing automation, Contract / bid / co-op pricing systems | Hierarchy relationships, Organization, Person, Household |
| Customer 360 (lawyers, lenders, realtors) | CRM, Licensing / provisioning / billing | Person, Organization |
| Door & Dock Equipment Asset MDM | Field service / dispatch | Asset |
| Guest 360 (luxury personalization) | Property management / leasing, Salesforce Sales and Service Cloud, CRM, E-commerce / web accounts | Person, Organization |
| Installer & Branch MDM | Field service / dispatch, HCM / payroll | Location |
| Investor / Fund Legal Entity MDM | Fund administration / investor portal / loan admin, ERP item / customer / vendor master | Hierarchy relationships, Legal Entity, Person |
| Lead / Prospect De-duplication MDM | E-commerce / web accounts, CDP / marketing automation | Person |
| Owner & Guest 360 | Property management / leasing, ERP item / customer / vendor master, Salesforce Sales and Service Cloud, CDP / marketing automation | Person, Organization |
| Owner & Residence Client MDM | CRM, ERP item / customer / vendor master | Organization, Person, Structure |
| Parts & Vendor MDM | ERP item / customer / vendor master | Category, Item, Product, Supplier, Organization |
| Party / Owner MDM | Confirmed in discovery | Organization, Person |
| Property & Unit Inventory MDM | Property management / leasing | Structure |
| Property / Asset & Space MDM | Property management / leasing, PLM / CAD-PDM | Structure |
| Property / Parcel MDM (PIN) | Confirmed in discovery | Structure |
| Property, Room & Rate MDM | Property management / leasing | Structure, Agreement |
| Tenant & Customer 360 | Salesforce Sales and Service Cloud | Person, Organization |
| Vendor / Trade Partner MDM | 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 real estate, construction & hospitality 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
- Owner and guest 360
- Source system 1
- Property-management or reservation system
- Source system 2
- Salesforce (Sales/Service Cloud)
- Lands on
- Person and Organization from the core model; Structure for the property where in scope
- What it proves
- One guest or owner record across the operating system and the CRM, ready for personalization and service.
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.