Authorization concepts take time

Authorization concepts take time
IMS Team Dominique Bellwon
Contributed by: Dominique Bellwon

Dominique holds a Master's degree in Facility Management and has previously completed her FM Bachelor in Dual Studies. Elsewhere, she has a heart for the practice: she also uses customer visits to get to know the places where IMSWARE is being worked. Since her passion for traveling complements well with the profession. This also applies to another hobby of Dominique: running. Even at half marathons and open competitions there are parallels to sales and consulting.

Have you ever tried to develop an authorization concept?

Before I go to IMS I worked for a large facility management service provider and had to do exactly that: to develop authorization concepts.

Well wanted is not well done

Of course everyone wants to make their concept good. So look: what roles are there? Which functions are relevant? Which accesses may who have and under what conditions?

The consequence of this care was foreseeable: If you ask many questions, you will get many answers. And who gets many answers, tries to consider all these answers. This resulted in about 30 roles in the specific case - too many, if they are to be administered over a long time.

And fine differentiation carries a risk that should not be underestimated - there are further requirements and thus additional roles: "If the colleagues of" Property A "get an extra sausage for X, we would like to have an extra sausage for Y from" Property C " . "

Sausage factory?

Now FM is not a sausage factory, and also there one works standardized. This is also the key to a functioning and practicable authorization concept. Standardization, which basically means reduction to relevant basic aspects. These could be represented in our case in only seven roles:

  •   administration
  •   Managing directors
  •   area manager
  •   Objektleiter
  •   coordinating staff
  •   executive employees
  •   Customer

A limitation of these roles exists at the most at the object data level. Thus, one person may only view data from "Object A" and another person only from "Object B". And only if the restriction is really necessary.

Reduction is sometimes barren, but ...

I admit, reduction is often barren. It is much nicer to be able to work in detail. It conveys a sense of transparency, precision, control and security. But at the same time it creates an administrative burden that binds too much time and in the end even limits the operational staff in the field too much.

That's why I always advise my clients to plan and take less time. Because there is not the super solution from the beginning. It develops with the increasing practical experience, through the own dynamic in the daily work routine and it is adapted and adjusted by the growing experience accordingly.

…paying off!

And one more thing is very important: constancy. Those who develop concepts should not exchange employees in the middle of the project. And every project manager needs a deputy at his side, since division of labor means faster progress and thus the knowledge of the authorization concept is not exclusive.

If you take that all to heart, you should make headway and yours CAFM system unfolds its productive benefits earlier.

Not despite, but because of the deliberate reduction.

Best regards

signature DB authorization concepts take time - IMSWARE.de

Your feedback?

average 4 / 5. Number of votes: 1

Great. Thank you very much!

Maybe you want to follow us on ...

We are sorry that you did not like this post so much.

Blog
Zurück
IMSWARE integrates Signotec pads
Weiter
The wide bridge between IFC and CAFM