Common use of CPU Hours Clause in Contracts

CPU Hours. “CPU Hours” shall be a Resource Unit Category. Resource usage shall be measured as the aggregate number of IBM Application CPU hours (normalized to and quoted in terms of equivalent 2064-1C1 hours) utilized during the measurement period. CPU Hours consists of the following:  Application time;  Authorized User usage;  All time associated with data base management system and transaction system address spaces (for example, DB2, CICS, IMS, TSO);  Authorized User usage of SAS, FOCUS, and other similar Software products; and  Application driven backup time; and  Application development and maintenance time for DIR or a third party hired by DIR. Billable Resource Units for CPU - IBM 2064-1C1 equivalent application hours will not include Resource Units which are attributable to Systems Overhead or system level work, including CPU outage or unavailability; CPU wait time; CPU un-captured time; Service Provider system operations support and administrative personnel usage (including usage for invoice functions and capacity planning studies) and other Service Provider initiated activities; Service Provider caused lost batch time, usage due to a runaway process that does not result in incremental cost to Service Provider, or other usage attributable to reruns which are due to the fault of Service Provider; and the following system services where controlled by Service Provider, including different products (or with different names) providing equivalent function:  Basic operating system components (e.g., JES2, LLA, VLF, GRS, MSTJCL, IEESYSAS, TRACE, RASP, XCFAS, DUMPSRV, CONSOLE, ALLOCAS, CATALOG, MOUNT, IOSAS, PCAUTH);  Service Provider system performance monitor, capacity management, and invoice data collection tools (e.g., MICS, SMF, RMF, OMEGAMON, SLR, DCOLLECT, EREP);  Service Provider system operation and support tools (e.g., SMP/E, JOB SCHEDULER, RERUN MANAGER, CONSOLE MANAGEMENT, SAR, RMDS, GDIF);  Mainframe based network operations, support, access methods, and standard system print drivers (e.g., VTAM, TCP/IP, TCAM, BTAM, NETVIEW, NPM, JES328X, VPS, NETMASTER);  Service Provider system-managed storage tools (e.g., DFSMS, ICKDSF, TAPE MANAGER); and  Service Provider Problem Management and Change Management Software. Mainframe CPU utilization will be measured over applicable usage periods and will include only the TCB and SRB components of Mainframe CPU time logged via System Management Facilities (“SMF”) Type 30 records for MVS systems, Power/VSE facilities for VM systems, or other applicable substitutes at the end of the month. One (1) Application CPU hour equals one (1) RU. Resource usage for Mainframe CPU will be rounded to the nearest whole hour for measurement, tracking and reporting purposes. For invoice purposes, the CPU hour should be rounded to the nearest minute. A more finite measurement may be used if agreed to in writing by DIR and Service Provider.

CPU Hours. “CPU Hours” shall be a Resource Unit Category. Resource usage shall be measured as the aggregate number of IBM Application CPU hours (normalized to and quoted in terms of equivalent 2064-1C1 hours) utilized during the measurement period. CPU Hours consists of the following:  • Application time;  • Authorized User usage;  • All time associated with data base management system and transaction system address spaces (for example, DB2, CICS, IMS, TSO);  • Authorized User usage of SAS, FOCUS, and other similar Software products; and  • Application driven backup time; and  • Application development and maintenance time for DIR or a third party hired by DIR. Billable Resource Units for CPU - IBM 2064-1C1 equivalent application hours will not include Resource Units which are attributable to Systems Overhead or system level work, including CPU outage or unavailability; CPU wait time; CPU un-captured time; Service Provider system operations support and administrative personnel usage (including usage for invoice functions and capacity planning studies) and other Service Provider initiated activities; Service Provider caused lost batch time, usage due to a runaway process that does not result in incremental cost to Service Provider, or other usage attributable to reruns which are due to the fault of Service Provider; and the following system services where controlled by Service Provider, including different products (or with different names) providing equivalent function:  • Basic operating system components (e.g., JES2, LLA, VLF, GRS, MSTJCL, IEESYSAS, TRACE, RASP, XCFAS, DUMPSRV, CONSOLE, ALLOCAS, CATALOG, MOUNT, IOSAS, PCAUTH);  • Service Provider system performance monitor, capacity management, and invoice data collection tools (e.g., MICS, SMF, RMF, OMEGAMON, SLR, DCOLLECT, EREP);  • Service Provider system operation and support tools (e.g., SMP/E, JOB SCHEDULER, RERUN MANAGER, CONSOLE MANAGEMENT, SAR, RMDS, GDIF);  • Mainframe based network operations, support, access methods, and standard system print drivers (e.g., VTAM, TCP/IP, TCAM, BTAM, NETVIEW, NPM, JES328X, VPS, NETMASTER);  • Service Provider system-managed storage tools (e.g., DFSMS, ICKDSF, TAPE MANAGER); and  • Service Provider Problem Management and Change Management Software. Mainframe CPU utilization will be measured over applicable usage periods and will include only the TCB and SRB components of Mainframe CPU time logged via System Management Facilities (“SMF”) Type 30 records for MVS systems, Power/VSE facilities for VM systems, or other applicable substitutes at the end of the month. One (1) Application CPU hour equals one (1) RU. Resource usage for Mainframe CPU will be rounded to the nearest whole hour for measurement, tracking and reporting purposes. For invoice purposes, the CPU hour should be rounded to the nearest minute. A more finite measurement may be used if agreed to in writing by DIR and Service Provider.