Difference between revisions of "B-Op HR Hub"

From ZUGSEIL Wiki
Jump to navigation Jump to search
Line 9: Line 9:
* '''Peer-to-peer HR data supply chains''' - if required you may push your HR data to thrird parties without using central data brokers  
* '''Peer-to-peer HR data supply chains''' - 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 can be run in multiple realms hosted at separate locations. Propagate HR data in this scenario seamlessly by standard HR Hub data-acquisition and HR Hub data-push plugins.
* '''b-op multi-realm setups''' - In large enterprises separate applications can be run in multiple realms hosted at separate locations. Propagate HR data in this scenario seamlessly by standard HR Hub data-acquisition and HR Hub data-push plugins.
==Architecture ==
==== Local HR Hub Core ====
Each b-op digital may host its local HR Hub Core instance. This HR Hub core holds a local copy of all HR data in its local ''HR Hub data store''.
The HR data stored in the  can be acquired from many sources 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.
HR data can be pushed from the local HR Hub data store to the local digital through data-push plugins.


==== HR Hub Core data propagation ====
==== HR Hub Core data propagation ====
Each HR Hub Core can configured to be a master hob and propagate its HR information to slave HR Hub. The communication happens over b-op message transport services.
Each HR Hub Core can configured to be a master hob and propagate its HR information to slave HR Hub. The communication happens over b-op message transport services.
== Related articles ==
== Related articles ==



Revision as of 19:57, 9 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 data supply chains - 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 can be run in multiple realms hosted at separate locations. Propagate HR data in this scenario seamlessly by standard HR Hub data-acquisition and HR Hub data-push plugins.

HR Hub Core data propagation

Each HR Hub Core can configured to be a master hob and propagate its HR information to slave HR Hub. The communication happens over b-op message transport services.

Related articles