Browse Prior Art Database

Use of job roles as a primary organization of business process and data

IP.com Disclosure Number: IPCOM000013283D
Original Publication Date: 2000-Oct-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 2 page(s) / 52K

Publishing Venue

IBM

Abstract

Disclosed is a way to organize business processes around business roles instead of organizing around individuals for collaborative business-to-business software. This leads to a much more efficient way to handle changes occurring in business. A business entity or organization tends to be built around roles. A CEO is the chief executive officer and this person tends to direct the entire organization that we call a business. Working for the CEO are a number of other roles typically in a hierarchy. As one travels down the hierarchy, roles become much more defined in what they do. These roles tend to pertain to collections of data used in the performance of the role. As an example, the role of a customer service representative uses a unique collection of data in their job performance. Some of this data is related to the person fulfilling the role but the majority of it is related to the role itself. Data about a specific customer, action items dealing with a particular customer situation or project, electronic discussions, quote requests, new business opportunities, or in the case of the electronics industry a registered design win all are data objects that deal with this role called a customer support representative. Each role or job function will have unique collections of data but never the less they are collections based on the role within the company organization. Inevitably changes occur within the business organization, people leave, get promoted, change job responsibilities and very often businesses reorganize. Once this happens the collection of data often gets lost or never re-surfaces in the new organization. This causes all sorts of delays and inefficiencies which ultimately leads to lost opportunity for the business. This is where the use of collaborative software based on roles becomes a critical benefit. Once collaborative data is accumulated by the roles that are collaborating, any changes that are introduced can be handled quickly and accurately. As an example, a person leaves the role of Eastern customer service representative and a new person is assigned to that role. All the collaborative objects data like opportunities, quotes, sample request, action items, and discussions threads can be re-assigned to a new person when that new person is now assigned to the Eastern customer service representative role. This all occurs instantly with collaborative software and the real benefit is that the new person has immediate access to all the important information that is currently active for this role. The new person can become much more productive in their new job or role almost immediately. This becomes even more critical when the business decides that not only do we have a new person in this role but we also want to re-assign customer responsibilities at the same time. This is where role based collaborative software really shines. All one has to do is change the role assigned to the customer and automatically customer accounts can be re-assigned to the new person just assigned to the role. So the business can also gain by very quickly changing their organization, as it needs to.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Use of job roles as a primary organization of business process and data

Disclosed is a way to organize business processes around business roles instead of organizing around individuals for collaborative business-to-business software. This leads to a much more efficient way to handle changes occurring in business.

    A business entity or organization tends to be built around roles. A CEO is the chief executive officer and this person tends to direct the entire organization that we call a business. Working for the CEO are a number of other roles typically in a hierarchy. As one travels down the hierarchy, roles become much more defined in what they do. These roles tend to pertain to collections of data used in the performance of the role. As an example, the role of a customer service representative uses a unique collection of data in their job performance. Some of this data is related to the person fulfilling the role but the majority of it is related to the role itself. Data about a specific customer, action items dealing with a particular customer situation or project, electronic discussions, quote requests, new business opportunities, or in the case of the electronics industry a registered design win all are data objects that deal with this role called a customer support representative. Each role or job function will have unique collections of data but never the less they are collections based on the role within the company organization.

    Inevitably changes occur within the business organization, people leave, get promoted, change job responsibilities and very often businesses reorganize. Once this happens the collection of data often gets lost or never re-surfaces in the new organization. This causes all sorts of delays and inefficiencies which ultimately leads to lost opportunity for the business.

    This is where the use of collaborative software based on roles becomes a cr...