Percentage of business entity IT FTEs who perform the process group "deploy information technology solutions"

This measure calculates the percentage of IT full-time equivalent employees (FTEs) who are dedicated to the "deploy information technology solutions" process group, which introduces new, enhanced, or improved functionality into the environment with minimal or no disruption to the services schedules; ensures consideration of appropriate security and contractual constraints; and properly balances business benefit with technical and business risk. It is part of a set of Supplemental Information measures that help companies evaluate additional variables not covered elsewhere for the "deploy information technology solutions" process.

Benchmark Data

Lock

Sorry! Not all users have access to all of our resources.

Want to unlock access to all of our resources?

Learn about Membership Arrow with stem

Measure Category:
Supplemental Information
Measure ID:
104555
Total Sample Size:
1,953 All Companies
Performers:
25th Median 75th
- - -
Key Performance Indicator:
No

Sample image showing interactive filters for more detailed measure peer group data and an interactive graph.

Compute this Measure

Units for this measure are percent.

Back to Top

Percentage of IT FTEs performing the process group "deploy information technology solutions"

Key Terms

Back to Top

To calculate the number of full-time equivalents employed during the year for each respective process or activity, you must prorate the number of employees and the hours spent performing each process/activity. Assume that a full-time worker represents 40 hours per week. Provide the average number of full-time equivalents employed during the year for each respective process. Include full-time employees, part-time employees, and temporary workers hired during peak demand periods. Allocate only the portion of the employee's time that relates to or supports the activities identified for an applicable process. Prorate management and secretarial time by estimating the level of effort in support of each activity, by process.

For example, a part-time secretary in the finance department for XYZ, Inc. charges all of his time to finance department activities. He works 20 hours per week. The secretary splits his time evenly supporting employees working in the general accounting process and the financial reporting process. Thus, his time should be allocated by process. So, if he works throughout the year and supports these two processes, his time would be split evenly as:

20hrs/40hrs = .5FTE * 50% for general accounting = .25FTE for general accounting

20hrs/40hrs = .5FTE * 50% for financial reporting = .25FTE for financial reporting

Supplemental information is data that APQC determines is relevant to decision support for a specific process, but does not fit into the other measure categories such as cost effectiveness, cycle time, or staff productivity.

For survey purposes, a business entity is defined as an entity that:

  1. performs significant aspects of the processes for the surveys identified, or
  2. is part of a cost or revenue center within the company.

Within your organization, diverse departments may be geographically co-located, with closely integrated operations that form part of one "business entity" which may be a great distance apart. When trying to determine if related parts of your operation should be considered a single business entity, look for the following characteristics:

  • Do they operate closely together?
  • Do they serve many of the same customers?
  • Do they support the same region or product group?
  • Do they share any performance measures?
  • Is data meaningful at a consolidated level?

Examples of business entity definition:

  1. A general ledger accounting unit located in Germany has two groups. One performs general ledger accounting for the corporate headquarters, which has three business units. The other group does general ledger accounting for one of the three business units. In spite of their geographic co-location, their roles are substantially different and consolidating their data into a single response would make it less meaningful. Each group should be treated as a separate business entity.
  2. Three business units within a corporation use a shared services center for accounts payable and expense reimbursement, but are self-supporting for the other financial processes. The best approach is to make the shared services centre a separate business entity for accounts payable and expense reimbursement, and to retain the three original business units for the other financial processes.
  3. A global manufacturing company has five plant locations, each manufacturing product and each with its own logistics operations. For purposes of completing a manufacturing and logistics survey, they should be treated as five separate business entities.

Measure Scope

Back to Top

Cross Industry (7.1.0)

  • 8.6.1 - Develop the IT deployment strategy (10592) - Creating and implementing a strategy for the deployment of IT solutions. Define all of the activities that make the IT function available for use. Establish the change policies for IT services and solutions. Define the deployment process, procedures, and tools. Select the most feasible and practical methodologies for the deployment process.
    • 8.6.1.1 - Establish IT services and solutions change policies (10686) - Defining policies regarding changes in IT services and solutions. Manage changes in a rational and predictable manner so that employees can plan accordingly. Reduce the negative impact to the user community. Increase the value of IT services and solutions.
    • 8.6.1.2 - Define deployment process, procedures, and tools standards (10687) - Outlining standards processes, methods, and equipment for deployment of IT solutions. Manage the subversion server, production server, development server etc. to make the IT services and solutions available for internal/client use.
    • 8.6.1.3 - Select deployment methodologies and tools (10688) - Assessing the tools and techniques for deploying IT solutions in order to choose the most appropriate options. Evaluate the pros and cons of all the methodologies available. Choose the most efficient and effective methodology.
  • 8.6.2 - Plan and implement changes (10593) - Strategizing and executing changes in IT solutions and services. Create a plan for deploying the changes. Communicate with stakeholders about the changes. Administer and implement the changes. Train the resources who will be affected by these changes. Install changes and verify their effect.
    • 8.6.2.1 - Plan change deployment (10689) - Creating plans for deploying the change in IT services and solutions. Define the changes. Implement a plan.
    • 8.6.2.2 - Communicate changes to stakeholders (10690) - Coordinating the changes in IT services and solutions with stakeholders. Communicate with creditors, directors, employees, owners (shareholders), suppliers, unions, and the community from which the business draws its resources.
    • 8.6.2.3 - Administer change schedule (10691) - Managing the schedule for implementation of change. Plan and carry out a process or procedure to implement the predefined changes.
    • 8.6.2.4 - Train impacted users (10692) - Preparing users for changes in IT solutions. Conduct training sessions and engagement activities to familiarize users with the new changes.
    • 8.6.2.5 - Distribute and install change (10693) - Administering and implementing the changes in place for the new strategies to take effect. Install new components, software, hardware, etc. onto the systems of the affected users.
    • 8.6.2.6 - Verify change (10694) - Confirming that the changes to the IT function have met expectations.
  • 8.6.3 - Plan and manage releases (10594) - Managing, planning, scheduling, and controlling an IT software or service build through different stages and environments, including testing and deploying its release. Understand the release design and acceptance. Plan the release rollout. Distribute and install the release. Verify the release.
    • 8.6.3.1 - Understand and coordinate release design and acceptance (10695) - Coordinating the deployment of new IT services and understanding the traction and level of approval for the same. Administer and synchronize the release of IT service packages. Manage version control and the uptake and level of acceptance.
    • 8.6.3.2 - Plan release rollout (10696) - Creating a plan for introducing the IT services and solutions provided by the organization in the market.
    • 8.6.3.3 - Distribute and install release (10697) - Distributing and implementing the release of changed IT solutions. Administer, implement, and install the releases onto internal systems. Provide methods for installing releases on client users.
    • 8.6.3.4 - Verify release (10698) - Confirming that the release has met expectations.