Exhibit 3.2.2 - Service Level Definitions - Payment Services.docx

State of South Carolina State Fiscal Accountability Authority (SFAA)

Request for Proposal Exhibit 3.2.2 Service Level Definitions – Payment Services

RFP Solicitation No. 5400021069

OTIS-PMNT-

RFP Solicitation No. 5400021069 Page i of ii

TABLE OF CONTENTS

Offeror Guidelines This Exhibit 3.2.2 (Service Level Definitions - Payment Services) contains specific functional requirements that the Offeror must meet in order to successfully perform the requested Services. The response must address all requirements contained in this Exhibit according to the instructions below and be in the prescribed format.

Offeror Instructions

1. The Offeror’s response to the RFP should reflect and comply with the information contained in this Exhibit 3.2.2 (Service Level Definitions - Payment Services).

2. If the Offeror wishes to suggest changes to content or requirements contained in this Exhibit 3.2.2 (Service Level Definitions - Payment Services), these suggestions should be summarized and submitted separately as detailed in Attachment D (Exception to Requirements). Any notation of objections or issues associated with this Exhibit 3.2.2 (Service Level Definitions - Payment Services) content does not eliminate or modify the requirements of this Exhibit 3.2.2 (Service Level Definitions - Payment Services) or this RFP, and the Offeror’s proposal must not assume any incorporation of the Offeror’s suggested changes.

The Offeror should not view the possibility of requesting changes as an opportunity to re-write the entire RFP. OTIS expects the Offeror to comply with the requirements as written, and changes should only be made for minor clarifications or if a Offeror will not comply with the requirement as written.

The Offeror will complete the highlighted sections [Service Provider to Complete] in each of the Critical Services Levels and Key Measurements by the following methods:

1. Metric Exclusions: Offeror to include in Attachment D (Exception to Requirements).

2. Collection Process: Not required for initial RFP response, this will be completed at a later stage in the procurement.

3. Reporting Tools: Offeror to include in Section 1.15 Service Level Management of Exhibit 2.1.4 (Cross-Functional Services Solution).

4.

RFP Solicitation No. 5400021069 Page i of ii Critical Service Levels – Payment Services This Section sets forth qualitative descriptions of the Critical Service Levels. The numerical Minimum Service Levels, Expected Service Levels and commencement of obligations associated with such Critical Service Levels are set forth in Exhibit 3.1 (Service Level Matrix).

A.1 Application Availability – Tier 1

SERVICE LEVEL NAME

Application Availability – Tier 1 (Payment Services)

If Downtime occurs for a Tier 1 Application, the Outage is counted against the Application, and the Application is considered unavailable for purposes of this Service Level.

Available hours = the total number of hours in a month (24 hours x number of days in the month) for each service.

Unscheduled Downtime = the total number of available hours (to the quarter hour) in which a service is not available for reasons outside of metric exclusions and solely due to the fault of the Service Provider.

METRIC OWNER

|_| Quarterly |_| Semi Annual

A.2 Payment Transaction Accuracy Rate

SERVICE LEVEL NAME

Payment Transaction Accuracy Rate

Transactions that cause reconciliation problems include the following:

1. Transactions missing detail,

2. Duplicate Transactions,

3. Reported Transactions not matching transactions processed through credit card processor, and

4. All other transactions that cause reconciliation problems for agencies.

METRIC OWNER

Key Measurements - Payment Services This Section sets forth qualitative descriptions of the Key Service Levels. The numerical Minimum Service Levels, Expected Service Levels and commencement of obligations associated with such Key Service Levels are set forth in Exhibit 3.1 (Service Level Matrix).

A.3 Change Management Effectiveness

SERVICE LEVEL NAME

Change Management Effectiveness

Changes are not successfully implemented if they: (i) do not comply with the Change Management procedures (including the Change Control Process), the SMM and, except as specified in clause (iii) to this sentence, any associated project plan, (ii) cause either a Severity 1 Incident or Severity 2 Incident, (iii) exceeded the change window, (iv) are backed out, or (v) partial success of change is backed out or unsuccessful.

METRIC OWNER

A.4 Charge Dispute Resolution

Charge Dispute Resolution

For purposes of clarity, note the following:

(a) if a dispute is initiated within the current Measurement Window, but the twenty Business Days extends beyond the end of the current Measurement Window, then it is excluded from the current Measurement Window’s calculation (unless such dispute is actually resolved in the current Measurement Window, in which case it is included in the current Measurement Window’s calculation)

(b) an open dispute that has exceeded the committed timeframe is also carried forward into subsequent Measurement Windows as a breach until resolved; if it is resolved within twenty-eight (28) days following its relevant committed timeframe, it is excluded from the subsequent Measurement Window; otherwise, it is counted as failed to meet the committed timeframes in each subsequent Measurement Window’s calculation until resolved.

METRIC OWNER

A.5 Root Cause Analysis Delivery

Root Cause Analysis Delivery

Service Provider will provide Root Cause Analyses on the most business-critical events, as maintained in the SMM, and as reasonably requested by OTIS Customers for all other Incidents.

If the Service Provider misses one (1) delivery of an RCA, then the performance for this Service Level will either be calculated using the standard algorithm, or deemed to equal the Minimum Service Level target (e.g., reported at 96%), whichever is higher.

METRIC OWNER

A.6 Key Transaction Response Time

Key Transaction Response Time

METRIC OWNER

A.7 Corrective Actions

Corrective Actions

For purposes of clarity, note the following:

(a) if a Corrective Action is opened within the current Measurement Window, but its relevant committed timeframe extends beyond the end of the current Measurement Window, then it is excluded from the current Measurement Window’s calculation (unless such Corrective Action is actually closed in the current Measurement Window, in which case it is included in the current Measurement Window’s calculation).

(b) an open Corrective Action that has exceeded the committed timeframe is also carried forward into subsequent Measurement Windows as a breach until closed; if it is closed within twenty-eight (28) days following its relevant resolution timeframe, it is excluded from the subsequent Measurement Window; otherwise, it is counted as failed to meet the committed timeframes in each subsequent Measurement Window’s calculation until closed.

METRIC OWNER

A.8 Incident Resolution Time – Level 2 & Level 3 (Severity 1 - 4)

Incident Resolution Time – Level 2 & Level 3 (Severity 1 - 4)

If an Incident is escalated to a higher Severity Level, then the Resolution Time clock restarts upon escalation to the higher Severity Level. Upon escalation, a new ticket will be created and the original ticket will be cancelled. The cancelled ticket will be related to the new ticket.

The applicable resolution timeframes are listed below.

Severity 1 Incidents:

· < 4 hours Severity 2 Incidents:

· < 6 hours

Severity 3

· The Incident will be Resolved within 3780 minutes (i.e. 63 hours or 7 Business Days) where such minutes will be measured only between 8:00 AM and 5:00 PM inclusive on Business Days.

Severity 4

· The Incident will be Resolved within 4860 minutes (i.e. 81 hours or 9 Business Days) where such minutes will be measured only between 8:00 AM and 5:00 PM inclusive on Business Days.

For purposes of clarity, note the following:

(a) if an Incident is opened within the current Measurement Window, but its relevant resolution timeframe extends beyond the end of the current Measurement Window, then it is excluded from the current Measurement Window’s calculation (unless such Incident is actually Resolved in the current Measurement Window, in which case it is included in the current Measurement Window’s calculation)

(b) an open Incident that has exceeded the relevant resolution timeframe is also carried forward into subsequent Measurement Windows as a breach until Resolved; if it is resolved within twenty-eight (28) days following its relevant resolution timeframe, it is excluded from the subsequent Measurement Window; otherwise, it is counted as failed to meet the resolution timeframes in each subsequent Measurement Window’s calculation until Resolved.

METRIC OWNER

A.9 Chronic Incidents

Chronic Incidents

METRIC OWNER

A.10 Service Request Fulfillment

Service Request Fulfillment

Specific target timeframes are maintained in the SMM.

For purposes of clarity, note the following:

(a) if a Service Request is opened within the current Measurement Window, but its relevant committed timeframe extends beyond the end of the current Measurement Window, then it is excluded from the current Measurement Window’s calculation (unless such Service Request is actually resolved in the current Measurement Window, in which case it is included in the current Measurement Window’s calculation)

(b) an open Service Request that has exceeded the committed timeframe is also carried forward into subsequent Measurement Windows as a breach until resolved; if it is resolved within twenty-eight (28) days following its relevant resolution timeframe, it is excluded from the subsequent Measurement Window; otherwise, it is counted as failed to meet the committed timeframes in each subsequent Measurement Window’s calculation until resolved.

METRIC OWNER

A.11 Data Quality

Data Quality

“Key processes” mean those processes that are foundational to the delivery of services (e.g., Major Incident Management, Refresh), as defined in the SMM.

“Critical attributes” mean the attributes associated with the Configuration Items for which quality data is necessary to successfully operate the key processes (e.g. operating system, operating system version), as defined in the SMM.

“Business rules” mean the set of checks that will be performed to on an attribute to determine quality, as defined in the SMM.

METRIC OWNER

A.12 Solution Proposal Delivery

Solution Proposal Delivery

Requests are worked in the approved prioritization order of the OTIS Customers. Following validation of requirements by Service Provider, the Service Provider will deliver a proposal for each request within the timeframes as listed below:

· Small – within 11 Business Days

· Medium – within 22 Business Days

· Large – within 33 Business Days

· Very Large – within 44 Business Days When a proposal is delivered, it must include a committed timeframe for project implementation specified as Business Days from the time the project is assigned to the project pool to the implementation completion. This committed number of Business Days will be used in the “Solution Implementation” Service Level.

Specific size criteria and guidelines will be maintained in the SMM.

For purposes of clarity, note the following:

(a) if a solution proposal request is opened within the current Measurement Window, but its relevant committed timeframe extends beyond the end of the current Measurement Window, then it is excluded from the current Measurement Window’s calculation (unless such request is actually delivered in the current Measurement Window, in which case it is included in the current Measurement Window’s calculation)

(b) an open solution proposal request that has exceeded the committed timeframe is also carried forward into subsequent Measurement Windows as a breach until delivered; if it is delivered within twenty-eight (28) days following its relevant committed timeframe, it is excluded from the subsequent Measurement Window; otherwise, it is counted as failed to meet the committed timeframes in each subsequent Measurement Window’s calculation until delivered.

METRIC OWNER

A.13 Solution Implementation

Solution Implementation

Projects will be reported in the Measurement Window in which the associated Change ticket is closed, allowing sufficient time to determine if the project was successful.

For purposes of clarity, note the following:

(a) if a project is assigned within the current Measurement Window, but its relevant committed timeframe extends beyond the end of the current Measurement Window, then it is excluded from the current Measurement Window’s calculation (unless such project is actually implemented in the current Measurement Window, in which case it is included in the current Measurement Window’s calculation)

(b) an uncompleted project is also carried forward into subsequent Measurement Windows as a breach until implemented; if it is implemented within twenty-eight (28) days following its relevant committed timeframe, it is excluded from the subsequent Measurement Window; otherwise it is counted as failed to meet the committed timeframes in each subsequent Measurement Window’s calculation until implemented.

METRIC OWNER

RFP Solicitation No. 5400021069 Page 1 of 20

RFP Solicitation No. 5400021069 Page 1 of 20