Guide - Database
Guide - Database
Version 2.6
KPMG LLP
99 High Street
Boston, MA 02110
(617) 988-1000
(617) 988-1860 FAX
Software
Mainframe
Remote Servers
Personnel
Technical DBAs Operations Management and
Support Administration
List your costs and sizes for a single relational database vendor's engine. This would include all
instances of the engines across platforms. Examples would include 1) all DB2 production engines but not
all IBM engines (e.g., not IMS), 2) all Oracle production engines, 3) all Microsoft SQL servers but not all
PC DBMSes. You may choose to restrict the number of instances; however, the data would then
measure only a portion of your total resources. In addition, you may decide to cover only the database
instances at a particular site (e.g., the primary corporate data center). This would then produce the costs
and sizing information for that site reflecting that it is only a portion of the total resources. When you
begin to collect system data, please be sure to review the definitions. Do not include any development
projects (new, redo or functional enhancement) that you are evaluating during the year of the analysis
that are not put into production.
Database Workbook
The workbook is comprised of one Database spreadsheet. In this Database spreadsheet we will collect
information pertaining to the database files in your organization including one major relational database
system.
The database workload spreadsheet will define the workload component of your analysis. This will be
used to select the comparison group and will be balanced against your costs to determine your overall
efficiency metrics. Identify the currency for the costs you are entering on the Currency line at the top of
the spreadsheet.
Report the name of the database engine selected for analysis in Row 1, Column B (e.g., DB2,
Oracle, Sybase, etc.).
Report the number of sites supported for the selected database engine in Row 2, Column B. A site is
defined as a physical location or a logical grouping of platforms, services or business units.
Report the number of tables and indexes used for the selected database engine in Row 3, Column B.
Report the total size of the database in gigabytes for the selected database engine in Row 4, Column
B.
Report the total number of active users of the selected database engine in Row 5, Column B.
Report the total number of processors running the selected database engine in Row 6, Column B.
Report the availability of the selected database engine in Row 7, Column B. Use the format days by
hours, i.e., 7x24.
Report the percentage of the environment being analyzed that is composed of each of the platform
types in rows 8 – 12, Column B. These numbers should include all database engines being analyzed
in the enterprise. The total must add to 100%. They are grouped into four categories:
Mainframe A mainframe is a "large" computer that serves at the highest level of platform
size used. It does not link "upwards" to "larger" computers. It is not
common to have PC / workstations linked directly into a mainframe.
File Server A file server is a computer that is connected to multiple PC / workstations via
LAN technologies (e.g., Token-Ring, Ethernet). It can be any size / type of
computer serving this function. It may be linked to larger computers and / or
to similar PC / workstation database or file servers.
PC / Workstation A base level "small" computer that generally has no other units linked into it.
It may be linked frequently to a larger computer such as a file server, as
described above.
KPMG LLP uses fully burdened costs when defining costs for the consensus cost models. Include
the lease, maintenance and depreciation costs of all hardware, software or shared hardware and
software used by the database staff for the analysis time period. In all cost categories, include all
applicable taxes (federal, state and local). Include value-added taxes (VAT); only exclude VAT when
it is recovered or refunded to the organization. All costs are reported in thousands.
The depreciation schedule used and the tax rates borne by your organization are reported in the
ITOA Project Definition and Information Questionnaire.
Report the actual monetary expense for the analysis period related to software for the selected
database engine in Row 13, Column B.
Report the actual monetary expense related to software tools for the selected database engine in Row
14, Column B. The specific categories to be included for database software tools are as follows:
Database Monitors Software, not packaged with the engine, to monitor the
internals of the DBMS, e.g., Omegamon, DB2, DB
General and TMON.
DBA Support Includes Migrate, Explain Plan Analyzer and other tools
used by DBM.
Distributed Database Support Includes the tools to monitor and control events centrally
in a distributed DBMS environment such as PATROL,
ECCOTools or DBVision.
Report the actual monetary expense related to occupancy for the database group in Row 15, Column
B. Occupancy costs should include fully burdened costs for the facility. Some examples would be:
office space, furniture, electricity, maintenance, property taxes, security, office supplies, etc.
KPMG LLP uses the Full Time Equivalent (FTE) concept in defining staff resources. Do not count
the physical staff but count the logical staff by looking at the functions that the physical staff perform
and for which they are responsible. FTEs should be measured in calendar time, that is, if an
individual works full-time on an assignment for a full year, that is one FTE. You would not subtract
vacation time, sick days, administration time, etc. If your labor-tracking system shows, for example,
220 days actually worked, that represents one FTE in your organization. The conversion factor you
use to go from hours or days into FTEs depends upon the amount of overhead time, how you record
overtime, and the way you enter data into your tracking system. Do not count any one physical
person as more than one logical person (due to overtime, etc.) However, you may count less than
one logical person for a physical person when not all of that individual’s time falls within the scope of
this analysis.
Report all staffing levels within the organization from managers and project leaders to daily
operations personnel. Report summarized data for all categories to show the average staff level,
adjusting for timing. This is best done by totaling the person-months for staff employed during the
year and then dividing by 12.
Report the actual monetary expense related to in-house staff, contractors and consultants utilized
during the analysis time period for all of the staff functions reported.
For in-house staff, in addition to salary include bonuses and paid holidays and vacation. Also include
benefits such as costs for medical / dental coverage, life and accident insurance, retirement plans,
stock plans, disability, social security, unemployment compensation, dependent care, tuition
reimbursement and employee assistance programs (physical exams, exercise programs and similar
costs). In all cost categories, include all applicable taxes (federal, state and local). Include value-
added taxes (VAT); only exclude VAT when it is recovered or refunded to the organization.
Do not include the costs related to human resource department staff allocations, early retirement
incentive bonuses, internal "cross-charges" for corporate overhead such as for the chairman's salary
or the human resources department.
For contractors and consultants, include all compensation that was paid directly to the individual or
agency.
14. Staff Definition – Management (Row 16; Column A for FTE Count and B for FTE Cost)
Report the total FTEs in Row 16, Column A and the annual monetary expense for management of
the selected database engine in Row 16, Column B.
15. Staff Definition – Database Support (Row 17; Column A for FTE Count and B for FTE Cost)
Report the total FTEs in Row 17, Column A and the annual monetary expense for support of the
selected database engine in Row 17, Column B. Include the database technical support, production
applications support, development applications support as well as Research and Development /
advanced technologies functions.
Database Technical Support personnel have responsibility for tasks such as installation of new
database software, toning DBMS internal parameters and other technical activities.
Production Applications Support personnel have responsibility for all functions in support of ongoing
applications such as maintenance of the database files, e.g., COPY, LOAD, UNLOAD, REORG;
migration from test to production as well as timing of the applications database-related functions.
Development Applications Support personnel have responsibility for the actual design, development
and testing of new or enhanced applications.
Research and Development / Advanced Technologies personnel have responsibility for the Research
and Development process to locate, evaluate and test new software.
16. Staff Definition – Administration and Clerical (Row 18; Column A for FTE Count and B for FTE
Cost)
Report the total FTEs in Row 18, Column A and the annual monetary expense related to
administrative support, secretarial and data entry which support functions of the selected database
engine in Row 18, Column B.
17. Staff Definition – Contractors (Row 19; Column A for FTE Count and B for FTE Cost)
Report the total FTEs in Row 19, Column A and the annual monetary expense related to contract
programmers used during the year in Row 19, Column B. A part-time employee who does not
receive benefits should be classified as a contract programmer.
Report the annual monetary expense in Row 20, Column B for outsourced functions for the database
environment. This is supplemental staff not managed on a day-to-day basis by the organization;
control of individual function(s) is given to a third party for database environment functions.