Sub-projects within IDAC
IDAC is organised into a number of sub-projects.
IT and integrations
The technical solution is essential. The project has selected a technical solution, on the basis of standards and modularity and via existing framework agreements, that requires minimal development. MIM (Microsoft Identity Manager) and OMADA will be the backbone of IDAC.
Rules, definitions and processes
This part is incredibly important. KI’s departments decide who is to have access to what information and when. The IT system is to support whatever rules and processes the KI’s operations requires. To ensure that the processes produced are appropriate, they are developed in close consultation with the reference groups.
IDAC is an entirely new system that is based on a different kind of technical platform to the current KIMKAT system but that still supports existing operational processes and user-types.
The system is designed to support three processes – start, change and end of employment or affiliation. Regardless of whether you’re an employee, affiliate or student, you’re required to follow the process appropriate to your user-type.
Valid from 1 juli 2017 KI has updated its rules for affiliating staff to KI, such as master students, post docs or guest researchers. In order to be able to follow the new regulations, a new process for affiliations and how it should be handled in our IT-systems is needed.
All users currently working in KIMKAT need IDAC training, particularly administrators and managers, who will have a new and important role to play in the system. Other people working at KI will be able to get help from a user’s manual and instruction films. Before administrators and managers can work in the system, they will need to complete the mandatory training and certification. The course will be largely produced by the main project, who aims to make the system as intuitive as possible so that people can use it without extensive education.
Other projects affecting NIBS
Several administrative projects at KI can influence NIBS. For example:
- OrgiP – Organisation in Primula. NIBS will have use of the organisational and managerial structures that OrgiP produces and implements. IDAC’s processes and some of its authorisation procedures will be based on OrgiP’s information.
- Ladok – IDAC will gather information on students in the same way as KIMKAT currently does from LADOK. In November 2017 a new Ladok system has been implemented at KI, whose development is still ongoing. More information about Ladok.
- Biomedicum – As NIBS depends on there being similar terms, processes and procedures at the departments to be able to build a relatively generic system, NIBS gains from the Biomedicum HR team’s work on standardising procedures and processes.
- KIIP (Karolinska Institutet Integration Platform) – This project ensures that information will be transferred between systems in the same way and takes care of the integrations currently being handled in KIMKAT and that will need changing when KIMKAT is wound down.