Organization Profiles
Analysts can profile an organization when specifying the organization details.
You can define as many profile values as you wish.
Examples of Organization Profiles and Their Use Cases in ITSM Systems
Organization profiles allow you to customize and structure your IT Service Management (ITSM) systems according to the unique needs and hierarchies of your organization. Here are some examples and why you might need them:
IT Departments Profile: This profile can be created to categorize requests, incidents, and changes by specific IT departments (e.g., network, software development, IT support). This ensures that tickets are routed to the correct team, improving response times and resolution efficiency.
Geographical Locations Profile: If your organization operates in multiple geographical locations, profiles can be set up representing each region (e.g., North America, Europe, Asia Pacific). This helps in managing requests and assets based on location, ensuring compliance with regional regulations and policies.
Business Units Profile: For organizations with diverse business units or product lines (e.g., retail, finance, healthcare), creating a profile for each unit helps in segregating data, managing service levels, and customizing workflows according to the specific needs of each unit.
Service Level Agreement (SLA) Profiles: Profiles can be designed to represent different SLAs (e.g., gold, silver, bronze) offering varying levels of service. This aids in ensuring that the ITSM system automatically enforces SLA commitments, prioritizes tickets, and allocates resources accordingly.
Vendor Management Profile: Keeping a profile that tracks all vendors, their services, and performance, can streamline vendor management. This profile can host contracts, service levels, and performance reviews, making it easier to manage vendor relationships directly from the ITSM system.
Asset Management Profile: An asset management profile organizes assets (software, hardware) owned by your organization. This is crucial for tracking asset life cycles, planning purchases or renewals, and ensuring compliance with licensing agreements.
Creating these profiles in your ITSM system enables a structured, efficient way to manage IT services, adapt to organizational changes, and provide high-quality service to end-users.
Creating an Organization Profile
Select the Menu button, then Admin, and then select System Administration. The System Administration window is displayed.
In the Explorer pane expand CMDB.
Select Organization Profiles to open the window. Existing profiles are displayed in alphabetical order.
Select the new icon. A new row is added to the browse table.
In the blank row, type the name of the profile you want to create.
Repeat for each profile you want to create.
Save the changes.
Provide the Change Reasons if prompted to do so.
Once you select to save the table, the browse table displays the entries in alphabetical order.
Renaming an Organization Profile
Select the Menu button, then Admin, and then select System Administration. The System Administration window is displayed.
In the Explorer pane expand CMDB.
Select Organization Profiles to open the window. Existing profiles are displayed in alphabetical order.
Select the profile entry you want to rename.
Type the name you want to assign for the selected profile.
Save the changes.
Provide the Change Reasons if prompted to do so.
Once you select to save the table, the browse table displays the entries in alphabetical order.
Deleting an Organization Profile
You cannot reverse this procedure. If you delete a profile by mistake, you have to re-create the entry by creating a new profile.
Select the Menu button, then Admin, and then select System Administration. The System Administration window is displayed.
In the Explorer pane expand CMDB.
Select Organization Profiles to open the window. Existing profiles are displayed in alphabetical order.
Select the profile entry you want to delete from the list.
Select the delete icon. If you attempt to delete the system default, you will receive a warning message.
Save the changes.
Provide the Change Reasons if prompted to do so.
Last updated