Platform and intelligence · Master Data (MDM)

The same person across every module, brought together by one CPF

The same person is a graduate, a financial guarantor, a freelancer and a customer, in records that do not talk to each other. Type the CPF and see where they appear in more than 30 records across the platform, the consolidated record with the source of each field, what they owe and how many tickets they have. Record quality points out invalid CPFs, records without a CPF and names that do not match, and the data subject report answers the LGPD request, with a log of who looked it up.

Le problème et la solution

What changes when Master Data (MDM) works inside the platform

This is connected information about classes, graduates and events across 6 modules, replacing scattered spreadsheets and messages.

Sans la plateforme

Information about Master Data (MDM) lives in separate spreadsheets, and nobody knows which version is current.

Avec Partiu Formatura

6 modules share the same class, graduate and event records.

Sans la plateforme

Demander un chiffre prend du temps, parce qu’il faut croiser des données venues de plusieurs endroits.

Avec Partiu Formatura

Person Profile by CPF and Consolidated Record with Source update together, with figures ready for the next meeting.

Sans la plateforme

Le processus dépend de qui est là ce jour-là, et son historique disparaît.

Avec Partiu Formatura

Tout le monde suit le même circuit, avec des actions consignées et des droits par rôle.

Sans la plateforme

Communiquer avec les autres services suppose d’exporter des tableurs et de resaisir les données.

Avec Partiu Formatura

Master Data (MDM) shares information directly with other areas of the platform.

Comment ça marche

How information moves through Master Data (MDM)

Chaque étape correspond à un module réel de ce domaine. Ce qu’elle produit passe à l’étape suivante sans que personne resaisisse la même information.

À la une

The person's profile built live, with no data copied

The CPF is searched in more than 30 platform records the moment the profile opens. For name, email, phone and date of birth, the consolidated record shows the value that counts and where it came from, and when sources disagree the steward chooses with a reason. Every lookup goes into the access log.

Voir à l’œuvre
  • Links by module and the person's role
  • Installments, tickets, contracts and orders through the app user
  • Invalid CPF, records without CPF and mismatches by source
  • Check up to 500 CPFs at once
  • Data subject report for the LGPD request

Person Profile by CPF

Where the CPF appears, in which role and what it has with the company.

  • Search by CPF with or without punctuation, or by name and email, with candidate CPFs always masked
  • More than 30 sources: graduate, guardians, app and admin users, CRM, employee, freelancer, supplier, contract, legal, ticket, store and others
  • Each link with the module, the person's role and a shortcut to open the source record
  • Open and overdue installments, tickets, contracts and orders through the app users linked to the CPF
  • A CPF with a wrong check digit is still searched, with a warning that it is invalid
  • The CPF never goes into the page address or the browser history
  • Nothing is copied: the profile is read live from each module's records

Consolidated Record with Source

The value that counts for each field, and where it came from.

  • Name, email, phone and date of birth consolidated from every source
  • Survivorship rule: the steward's choice wins; without it, the most trusted source; on a tie, the most recent record
  • Each candidate value shows the source, the date and whether it was chosen
  • Differences only in accents, case, spacing or phone prefix do not count as a mismatch
  • Only the person's own data counts: the graduate's name on the guardian's row does not get mixed in

Stewardship with a Reason

When sources disagree, someone decides, and the decision is recorded.

  • Pin the correct value of a field with a required reason
  • Stewardship history with when, field, value, reason and who
  • Undoing the choice returns the field to the automatic rule
  • Stewardship does not change the source record, which is still corrected in its own module

Record Quality

Where the wrong, missing or conflicting CPFs are.

  • By source: records, with CPF, without CPF, invalid CPF and distinct people, with spreadsheet export
  • Invalid CPF by length, repeated digits or check digit
  • Same CPF with a different name and a different date of birth across modules
  • People who appear in the most modules, as a starting point for review
  • Result cached for 10 minutes and a button to recalculate on the spot

Batch List Check

Paste the spreadsheet and find out who already exists in the company.

  • Up to 500 CPFs pasted at once: the committee spreadsheet, the caterer's list, the guest list
  • CPF by module matrix, with invalid and not found flagged
  • Result as a spreadsheet and a shortcut to each person's profile

LGPD: Data Subject Report and Access Log

The data subject request answered, and every lookup recorded.

  • Data subject report with everything the company holds on the CPF and the issue date, as a spreadsheet and for printing
  • Log of every profile opened, report issued and list checked, with who and when
  • Log filter by CPF to find out who looked up a person
  • Separate permissions to view, pin values and export

Liste de contrôle

Everything included in Master Data (MDM)

All 28 features in this area, grouped by module so you can compare systems item by item.

  • Search by CPF with or without punctuation, or by name and email, with candidate CPFs always masked
  • More than 30 sources: graduate, guardians, app and admin users, CRM, employee, freelancer, supplier, contract, legal, ticket, store and others
  • Each link with the module, the person's role and a shortcut to open the source record
  • Open and overdue installments, tickets, contracts and orders through the app users linked to the CPF
  • A CPF with a wrong check digit is still searched, with a warning that it is invalid
  • The CPF never goes into the page address or the browser history
  • Nothing is copied: the profile is read live from each module's records
  • Name, email, phone and date of birth consolidated from every source
  • Survivorship rule: the steward's choice wins; without it, the most trusted source; on a tie, the most recent record
  • Each candidate value shows the source, the date and whether it was chosen
  • Differences only in accents, case, spacing or phone prefix do not count as a mismatch
  • Only the person's own data counts: the graduate's name on the guardian's row does not get mixed in
  • Pin the correct value of a field with a required reason
  • Stewardship history with when, field, value, reason and who
  • Undoing the choice returns the field to the automatic rule
  • Stewardship does not change the source record, which is still corrected in its own module
  • By source: records, with CPF, without CPF, invalid CPF and distinct people, with spreadsheet export
  • Invalid CPF by length, repeated digits or check digit
  • Same CPF with a different name and a different date of birth across modules
  • People who appear in the most modules, as a starting point for review
  • Result cached for 10 minutes and a button to recalculate on the spot
  • Up to 500 CPFs pasted at once: the committee spreadsheet, the caterer's list, the guest list
  • CPF by module matrix, with invalid and not found flagged
  • Result as a spreadsheet and a shortcut to each person's profile
  • Data subject report with everything the company holds on the CPF and the issue date, as a spreadsheet and for printing
  • Log of every profile opened, report issued and list checked, with who and when
  • Log filter by CPF to find out who looked up a person
  • Separate permissions to view, pin values and export

Want to see Master Data (MDM) in your operation?

Demandez une démonstration sur vos propres chiffres, sans engagement. Un échange vous aidera à juger si le module répond à vos besoins.