Organization hierarchies and people relationship models

This topic provides information about models related to organization, people and their relationships to various other configuration items (CIs) and services.


Related topics

Managing-the-common-data-model

Organization and organization hierarchies

Organizations are modeled as instances of the BMC_Organization class. This organization class can be used to represent an internal organization, operating company, business unit, tenant, customer, supplier, vendor, and manufacturer. The BusinessCategory attribute on the BMC_Organization class is used to specify the type business that the organization performs, such as customer, operating company, and so on. In addition to the Name attribute, an organization also has other attributes, such as Email and URI.

Organizations can have hierarchies, such as departments, corporate organizations, support organizations, and support groups. The BMC_MemberOfCollection relationship represents the between the parent organization and the child organization.

Best practice
BMC ITSM defines the following organization hierarchies. We recommend that you keep these hierarchies in tact to preserve the compatibility with ITSM suite of products:

  • Organization > Corporate Organization > Department
  • Organization > Support Organization > Support Group

In the following diagram, Calbro is an operating company having two organizations - Accounts and AppSupport. The relationship from parent organization to child organization is represented by BMC_MemberOfCollection with Name=ORGANIZATIONCOMPOSEDOF.

org hierarchy with person.png


Person and organization

People are modeled as instances of the BMC_Person class. A person CI has several attributes that identify a person, such as FirstName, LastName, MiddleName, and PersonId. 

PersonId is used as a unique identifier for the person such as a social security number or an ITSM generated identifier (such as PPL00000014). There are also other attributes for a person, such as Email, OfficePhone, and MobilePhone.

The relationship between an organization and people is modeled as BMC_MemberOfCollection with Name=PERSONASSOCIATEDTOORGANIZATION where source is the organization CI. 

Person, ownership, and management of computers

Persons have relationships to computers, services and other configuration items.

In the following diagram example, Sandy, the support person, owns two devices - a laptop and a blackberry device where the two devices are represented by BMC_ComputerSystem.

  • The ownership relationship is represented as BMC_Dependency with Name=OWNEDBY and source being the device such as computer system.
  • Sandy supports a linux server called linux1 and this relationship is represented by BMC_Dependency with Name=MANAGEDBY. 

person to org location owned by managedby.png


Person, ownership, and management of computers

Persons have relationships to computers, services and other configuration items.

In the preceding diagram, Sandy the support person, owns two devices - a laptop and a blackberry device where the two devices are represented by BMC_ComputerSystem.

  • The ownership relationship is represented as BMC_Dependency with Name=OWNEDBY and source being the device such as computer system.
  • Sandy supports a linux server called linux1 and this relationship is represented by BMC_Dependency with Name=MANAGEDBY. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*