B-Op HR Hub

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 and must be aligned with the b-op data ownership and privacy principles.

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 memberships computed specifically according to target system. This plugins may have specific configuration-uis as well.

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)