Informatica MDM SaaS Foundation cheat sheet

Informatica MDM SaaS is delivered on the Informatica Intelligent Data Management Cloud (IDMC); the MDM & 360 applications run as cloud services accessed through IDMC, not as on-premises server installs.

Core 360 applications in the SaaS family: Customer 360, Product 360, Supplier 360, Reference 360 (reference data management), and Business 360 (custom/configurable entity apps).

Business Entity model: each 360 app is built on a business entity (e.g., Customer) with a logical model; fields map to a physical model persisted in the SaaS data store; the model is configured, not code-generated by the customer.

Mastering pipeline stages: ingest/validate source records, standardize and cleanse, match (exact and fuzzy), cluster into best versions, then consolidate and publish to consumers.

Match rules define match columns, match types (exact, fuzzy, mixed), and thresholds; match review resolves ambiguous clusters; trust/validation rules and survivorship rules determine which source value populates each master field.

Reference 360 manages code sets and hierarchies (e.g., industry codes) with versioning and crosswalks; it can supply reference values to other 360 apps instead of duplicating lookup data.

Data quality and cleansing run through Cloud Data Quality (DQ) services invoked in the pipeline; standardization, parsing, and validation mapplets are attached to the entity's cleanse stage.

Consumers access mastered data via published views/APIs and the 360 application UI; downstream systems typically read the published (consolidated) records rather than raw staging records.

Hierarchies and relationships (e.g., parent-child account structures) are modeled as relationship types on the business entity; relationship records link entity instances and can carry their own attributes.

Informatica MDM SaaS is delivered on the Informatica Intelligent Data Management Cloud (IDMC); the MDM & 360 applications run as cloud services accessed through IDMC, not as on-premises server installs.

Core 360 applications in the SaaS family: Customer 360, Product 360, Supplier 360, Reference 360 (reference data management), and Business 360 (custom/configurable entity apps).

Business Entity model: each 360 app is built on a business entity (e.g., Customer) with a logical model; fields map to a physical model persisted in the SaaS data store; the model is configured, not code-generated by the customer.

Mastering pipeline stages: ingest/validate source records, standardize and cleanse, match (exact and fuzzy), cluster into best versions, then consolidate and publish to consumers.

Match rules define match columns, match types (exact, fuzzy, mixed), and thresholds; match review resolves ambiguous clusters; trust/validation rules and survivorship rules determine which source value populates each master field.

Reference 360 manages code sets and hierarchies (e.g., industry codes) with versioning and crosswalks; it can supply reference values to other 360 apps instead of duplicating lookup data.

Data quality and cleansing run through Cloud Data Quality (DQ) services invoked in the pipeline; standardization, parsing, and validation mapplets are attached to the entity's cleanse stage.

Consumers access mastered data via published views/APIs and the 360 application UI; downstream systems typically read the published (consolidated) records rather than raw staging records.

Hierarchies and relationships (e.g., parent-child account structures) are modeled as relationship types on the business entity; relationship records link entity instances and can carry their own attributes.