Resource Management System (RMS)
Original Publication Date: 2001-May-01
Included in the Prior Art Database: 2003-Jun-19
AbstractDisclosed is a description of a Resource Management System (RMS) database deployed in an environment such as Lotus Notes. This publication covers typical needs and requirements, and a solution to those needs.
Resource Management System (RMS)
Disclosed is a description of a Resource Management System (RMS) database deployed in an environment such as Lotus Notes. This publication covers typical needs and requirements, and a solution to those needs.
Many organizations have some or all of the following problems, when dealing with resource management issues across an organization. The organization can be small (50 employees), or a large, worldwide corporation (+250,000).
(1) Can you identify all the people within the organization (including other divisions that may be working on your behalf)?
(2) Can you Identify all the people working on specific projects?
(3) Where are these people located?
(4) What skills do these resources have? Which skills are being utilized in their current assignment?
(5) What projects or assignments are they working on?
(6) When will they become available for reassignment?
(7) What are the expense costs incurred by the organization for these projects and assignments?
Often, many problems have to be overcome, to achieve even partial success using a "manual" method to collect this type of data:
(A) Some data was not available to everyone (Projects, Engagements, Skills, Availability, Where located, what organization people work for, etc.)
(B) Some data is scattered across many systems (HR databases, Manager spreadsheets, people head knowledge, etc.)
(C) Too many people & systems needed to get the information (Procurement, HR, Corporate DBs, Payroll, etc.)
(D) No consistent means to get the data (Spreadsheets, Computer applications, Various databases, charts, etc.)
(E) No consistent enforcement to keep the data accurate (required phone calls verification of systems, etc.)
(F) Difficult to track multiple project assignments of individuals through the financial systems
(G) Difficult to track non-headcount project costs consistently
(H) No consistent or repeatable process to track, collect and report this data across the entire organization
The solution to the problems 1-7 stated above is a "Resource Management System (RMS)" database. This RMS database captures and reports all the above data required to solve the original needs (problems 1-7). Proper architecture of the database, the user interface, and feedback from the database, overcomes the problems A-H above of consistency, disparate data systems and the enormous time and effort it takes collect, maintain, review and analyze the data for purposes of management decision making.
RMS solves the above problems with the advantage of being a single database tool that is available worldwide. Because of specific design elements in the database, it became functionally easy to add financial information for analysis, and to extend the capabilities of the system beyond traditional resource management (identify people, location, and reporting chain). For instance, RMS has "Location Documents" that identify every location where development work occurs. Each location may have a different average...