Difference between revisions of "B-Op HR Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
Line 2: Line 2:


To integrate with these HR-systems, B-Op HR Hub was created to integrate seamlessly.
To integrate with these HR-systems, B-Op HR Hub was created to integrate seamlessly.
Please note that this topic has to be observed closely with the [[Dev:Data ownership and possession with b-op|problem of data ownership and possession]].
== Types of personal data ==
There are '''various categories''' of information on natural persons. These categories differ on the timeline how long the person shares its information with the company. The duration of this timeframe depends on ''regional governmental regulations and laws'' <u>and</u> ''on the'' ''permission of the person.''
ZUGSEIL currently supports three categories of personal information
* '''Employment information''' - this is information on the staff member, which is shared with the organization. The organization only has the <u>permission</u> to use and store these data by the staff member during employment.  Example for this information are: Staff number, First Name, Last Name, employment level, birthdate, gender, ...
* '''Private information''' - this is information not permanently required and must not be stored with the employer, but should only temporarily share for specific usecases. This is information which is owned by any person (staff member) and is only temporarily shared for special usecases and not to be stored on the employers information.  Example: Sizes, Body measures, diagnoses, health state documentation, ...


== Top level architecture for company information on staff members ==
== Top level architecture for company information on staff members ==

Revision as of 08:55, 29 June 2023

HR Data importing is required for almost all usage cases of B-Op software, as larger companies typically have a HR system already in place.

To integrate with these HR-systems, B-Op HR Hub was created to integrate seamlessly.

Please note that this topic has to be observed closely with the problem of data ownership and possession.

Types of personal data

There are various categories of information on natural persons. These categories differ on the timeline how long the person shares its information with the company. The duration of this timeframe depends on regional governmental regulations and laws and on the permission of the person.

ZUGSEIL currently supports three categories of personal information

  • Employment information - this is information on the staff member, which is shared with the organization. The organization only has the permission to use and store these data by the staff member during employment. Example for this information are: Staff number, First Name, Last Name, employment level, birthdate, gender, ...
  • Private information - this is information not permanently required and must not be stored with the employer, but should only temporarily share for specific usecases. This is information which is owned by any person (staff member) and is only temporarily shared for special usecases and not to be stored on the employers information. Example: Sizes, Body measures, diagnoses, health state documentation, ...

Top level architecture for company information on staff members

There exists a HR Hub core service, installed

  1. Data acquisition plugins - They are used to accumulate hr base date from multiple systems into one data pool hosted in the HR hub. They are stored locally and encrypted (storage security)
    1. simultaneously (Graph API, Hr-System, AD, picture source, csv, .... )
    2. invoking each other (pictures imported by another plugin)
  2. Transport
    1. with filtering on row level (e.g. External users are not relevant to Klesy)
    2. with filtering on column level (e.g. BKC is non relevant to Print environments)
  3. Import plugins - They are used to import the transported HR information into target digitals:
    1. analyse users and e.g. add user-groups computed specifically according to target system. This plugins may have specific configuration-uis

Privacy regulation and deletion service (RPDS)

  1. A PRDS configuration UI, where each digital is able to
    • define its privacy regulation and time periods (e.g. deletion-periods defined by regional law or company governance)
    • define if data subject to this are anonymized or deleted
  2. A PRDS service, which removes no longer required information as defined in (1)

Access protection layer for personal information of staff members