Fokker Services Group uses AFAS as the source for accounts in Active Directory and Entra ID. Staff at the Singapore entity are kept in Unit4 HR; a second integration puts them into AFAS, so they get an account through the same route.
Connected systems: AFAS → Active Directory and Entra ID, Unit4 HR → AFAS
Category: Identity and access management
The situation
Fokker Services Group maintains aircraft and components, with entities in the Netherlands and abroad. The Dutch organisations work in AFAS. The Singapore entity has its own HR system, Unit4 HR. IT wanted a single source for all accounts, without managing Singapore separately.
What the integration does
AFAS to Active Directory and Entra ID
- Joiners. A new employee in AFAS gets an account in time for the first working day.
- Movers. When something changes in AFAS, such as job or department, the account follows.
- Leavers. After the leave date the account is deactivated.
- Fixed conventions. Usernames and domains follow Fokker's own conventions, so accounts look the same everywhere and are not created twice.
- Back to AFAS. The work email address goes back to AFAS, so HR can see which address someone uses.
Unit4 HR to AFAS (Singapore)
- Employees. New employees and changes in Unit4 HR reach AFAS, with job, department and contract type translated into what AFAS knows.
- Only real employees. Test and service accounts are left out.
- Recognisable as Singapore. Staff from Singapore are recognisable in AFAS and Active Directory as colleagues of that entity.
- Out of scope. Salary data, and writing back to Unit4.
What it changed
For IT, AFAS is the single source of truth, Singapore included. A new colleague in Singapore gets an account the same way as a colleague in the Netherlands. Leavers lose their access without anyone having to remember it.
Systems
- Sources: AFAS Profit, Unit4 HR (Singapore)
- Targets: Active Directory and Entra ID, AFAS Profit
- Direction: Unit4 HR → AFAS → Active Directory and Entra ID, with the email address back to AFAS