Difference between revisions of "B-Op HR Hub"
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 1: | Line 1: | ||
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. | 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 3rd party HR systems, b-op HR Hub was created as a standard tool to integrate seamlessly with any system landscape. | ||
Please note that this topic has to be observed closely and must be aligned with the [[Dev:B-Op data ownership and privacy principles|''b-op data ownership and privacy principles'']]'''.''' | |||
== Features == | |||
* '''Standard integrations''' - connect to any 3rd party software landspace (like S4HANA or SAR HR, Azure AD, Active Directory, ...) | |||
* '''Easy connectivity''' - If you are bound to a non-standard HR data provider (CSV, Excel, ... ) you can integrate these data sources easiliy by creating HR Hub data acquisition plugins. | |||
* '''Peer-to-peer HR propagation''' - if required you may push your HR data to thrird parties without using central data brokers | |||
* '''b-op multi-realm setups''' - In large enterprises separate applications into multiple realms hosted at separate locations. Propagate HR data seamlessly by standard HR Hub data-acquisition and HR Hub data-push plugins. | |||
==Architecture == | |||
Each b-op digital may host a HR Hub Core. This HR Hub core holds a local copy of all HR data and can synchronize it with the local b-op digital. This HR data can be acquired by | |||
* local data acquisition (from the local digital) or | |||
* a master digital through b-op HR Hub data propagation or | |||
* 3rd party systems through data-acquisition plugins. | |||
or 3rd party systems and can propagate these to the local digital or other digitals (slave digitals) | |||
There exists a HR Hub core service, installed | |||
#'''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) | |||
##simultaneously (Graph API, Hr-System, AD, picture source, csv, .... ) | |||
##invoking each other (pictures imported by another plugin) | |||
#'''Transport''' | |||
##with filtering on row level (e.g. External users are not relevant to Klesy) | |||
##with filtering on column level (e.g. BKC is non relevant to Print environments) | |||
#'''Import plugins''' - They are used to import the transported HR information into target digitals: | |||
== Related articles == | == Related articles == | ||
Revision as of 17:50, 8 July 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 3rd party HR systems, b-op HR Hub was created as a standard tool to integrate seamlessly with any system landscape.
Please note that this topic has to be observed closely and must be aligned with the b-op data ownership and privacy principles.
Features
- Standard integrations - connect to any 3rd party software landspace (like S4HANA or SAR HR, Azure AD, Active Directory, ...)
- Easy connectivity - If you are bound to a non-standard HR data provider (CSV, Excel, ... ) you can integrate these data sources easiliy by creating HR Hub data acquisition plugins.
- Peer-to-peer HR propagation - if required you may push your HR data to thrird parties without using central data brokers
- b-op multi-realm setups - In large enterprises separate applications into multiple realms hosted at separate locations. Propagate HR data seamlessly by standard HR Hub data-acquisition and HR Hub data-push plugins.
Architecture
Each b-op digital may host a HR Hub Core. This HR Hub core holds a local copy of all HR data and can synchronize it with the local b-op digital. This HR data can be acquired by
- local data acquisition (from the local digital) or
- a master digital through b-op HR Hub data propagation or
- 3rd party systems through data-acquisition plugins.
or 3rd party systems and can propagate these to the local digital or other digitals (slave digitals)
There exists a HR Hub core service, installed
- 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)
- simultaneously (Graph API, Hr-System, AD, picture source, csv, .... )
- invoking each other (pictures imported by another plugin)
- Transport
- with filtering on row level (e.g. External users are not relevant to Klesy)
- with filtering on column level (e.g. BKC is non relevant to Print environments)
- Import plugins - They are used to import the transported HR information into target digitals: