Skip to content

Guides

Master data vs. project data

Some data is shared by many projects, other data belongs to exactly one project. This distinction shows you where to maintain something.

Whatever you will need again in the next project is master data. Whatever applies only to this one project is project data.

Master data is the shared reference data of your organization. It lives in the Master data app and exists independently of any project. Project data is created in the project and belongs to it, for example tasks, budgets or risks.

Master data Project data that builds on it
Employee (person with skills and cost rate) Project member (role of this person in the project, with its own hourly rate)
Skill in the skill catalog Skill requirement of a role in the project
Material in the material catalog (material type, variant, specifications) Material in the technical structure, procurement request, purchase
Equipment in the equipment catalog Equipment use on a task
Department –
Project type (in Projekt & Portfolio › Projekttypen) Project of this type

An employee is created once in master data, with their skills. In the project this becomes a project member: the role of this person in exactly this project, with role description and hourly rate. A role can also be unfilled at first. Then its skills describe what is needed, and you look for a suitable employee later. See Assemble the team.

  • Maintenance in one place: If you change master data, for instance an employee’s skills, it takes effect in all projects that reference it.
  • Care when removing: Master data that is used in projects should not be deleted lightly. Aligia shows which data is affected before deleting.
  • Analyses across projects: Because all projects use the same catalogs, workload or material demand, for example, can be viewed across projects.