How Are You Using Organization Objects?
Recently we have started using Organization object. I have created an Organization object per department and related the user to the proper Department/Organization object. I did this so that when I relate a Department/Organization object to a business service or change request, I can see what user are affected.
I also keep the organization object updated automatically by running a night job/script that
- Gets all of the user
- Groups users by department
- Created new organization object if one is not found (This would mean that a new department has been created)
- Compares currently related user and add or removed relationships as needed
How are you guys using Organization Objects?
Best Answer
-
Nicholas_Velich Cireson Consultant Ninja IT Monkey ✭✭✭✭
Hi German,
The most common use of the Organization object I see is to represent Departments. This is especially true in small-to-medium sized companies where there are unlikely to be multiple organizations within a single company. The other-but-less-common-scenario I've seen is to use Organization to represent companies that might have been acquired.
I really like your approach of being able to determine users impacted by a Service outage; that is really useful information, and plays nicely into Change Management. In fact, Business Services as a whole I find to be an underrated feature of the SCSM CMDB. After you put the effort in to map Services and components, you get a lot of info about how all the different pieces of your IT infrastructure fit together. Adding users/departments into that mix is a neat idea that adds even more value.
Thanks,
Nick
5
Answers
Hi German,
The most common use of the Organization object I see is to represent Departments. This is especially true in small-to-medium sized companies where there are unlikely to be multiple organizations within a single company. The other-but-less-common-scenario I've seen is to use Organization to represent companies that might have been acquired.
I really like your approach of being able to determine users impacted by a Service outage; that is really useful information, and plays nicely into Change Management. In fact, Business Services as a whole I find to be an underrated feature of the SCSM CMDB. After you put the effort in to map Services and components, you get a lot of info about how all the different pieces of your IT infrastructure fit together. Adding users/departments into that mix is a neat idea that adds even more value.
Thanks,
Nick
Thank you