The majority of organisations have a payroll system. Many larger organisations also have a rostering system that tracks time and attendance. In certain industries it is common to find an elearning system as well. Let alone all of the client management and administration systems used by modern organisations.
Unfortunately, the majority of these systems cannot connect and share information.
What does that mean for the organisation?
Overall, it means higher time and costs in workforce management and increased risk.
The key to solving the above issues is by developing a connected workforce management system that connects your HRIS, payroll, rostering, elearning, etc systems so that they can all connect and easily share data with the other platforms in the system.
In today’s world, anything short of API connected systems is not true connectivity. Certainly there are older ways to share data but they are usually limited in functionality. An API is a connector, or gateway, that allows the platform to send and receive data with another platform that also has an API. The setup still needs an actual system between the two API connections that provides the “orchestration” of the information sharing.
If you thought of the APIs as interchanges to a highway, someone still has to build and maintain the highway. The interchanges just give the driver the access to the highway.
Simply put, there are two types of API connectivity. They are:
A direct connection is between two platforms such as payroll and rostering. In the direct connection model:
This situation makes it difficult to change platforms as you are typically locked into your current IT setup. Not only in the choice of platforms used, but also the rate at which some IT vendors will upgrade their functionality versus others. In order to connect your payroll, you might need to stay on an older version of the payroll system because your rostering system does not connect to more modern versions.
Each circle represents a platform in your IT system. They connect point to point to other platforms and need to “know” the other party.
The alternative connection type is where each platform has a single connection that connects them to a central system. None of the platforms connect directly to any other platform and therefore do not need to know what other platforms are in the IT system.
Instead, each platform publishes and subscribes to events. All connecting through a single event management interface. So each platform only needs to integrate once.
For example the HR system publishes events such as a new hire, or a promotion, which needs to be read by the payroll system. In turn, the payroll system would subscribe to events that are relevant to it. Such as the above example of new staff or a promotion.
The difference to point to point is that none of these platforms know any other platform. Making it easy to make changes and add or subtract platforms to the IT system.
Why is this a better way to connect?
OnePassport’s system includes a JSON API powered middleware platform called ConnectHQ. It is designed for small and medium businesses for both ease of use and pricing. Allowing the smaller end of town to have integrated workforce management similar to corporate enterprises.