state of michigan central procurement services … · this is technical siebel software upgrade to...

STATE OF MICHIGAN

CENTRAL PROCUREMENT SERVICES

Department of Technology, Management, and Budget525 W. ALLEGAN ST., LANSING, MICHIGAN 48913P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 16

to071B2200168Contract Number

[email protected]

William Pemble

Matt Weiss

[email protected]

Kathleen Cawley

Detroit, Michigan 48226

ACCENTURE

CV0062320

859-248-1187

1001 Woodard Avenue, 4th Floor

(517) 256-9895S

TA

TE

Pro

gra

m

Man

ag

er

Co

ntra

ct

Ad

min

istra

tor

CO

NT

RA

CT

OR

DTMB

517-636-4741

DTMB

[email protected]

$43,697,383.41

May 1, 2012 April 30, 2022

CONTACT CENTER SUPPORT

April 30, 2017

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

☐ P-Card ☐ PRC ☐ Other ☐ Yes ☒ NoMINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION REVISED EXP. DATE

☐ ☐ N/A

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$0.00 $43,697,383.41

Effective 3/16/2020, the following amendment is hereby incorporated into the Contract to enable the IIT SAP e-Service web portal to integrate with the Siebel Customer Relationship Management (CRM) system. Total cost will be $55,704.00.

No additional funding is needed at this time; existing funds are adequate to support this change.

All other terms, conditions, specifications, and pricing remain the same. Per contractor, agency and DTMB procurement.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

CONTRACT SUMMARY

Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

SOW-084 Treasury Siebel SAP Web Services

Page 1

Statement of Work (SOW) Number:

SOW-084 Treasury Siebel IIT SAP Web Services

Project Title: Treasury Siebel-SAP IIT Web Services

Release (if applicable):

SOW Summary Description: Provide Siebel Web Services to support Treasury IIT SAP Web Portal

Estimate Submitted By: Jim Piecuch

Date Submitted: 10/02/2019

Requesting Department/Agency

DTMB, Treasury

Agency Service Request

Background Over the years, DTMB has established a shared IT support service center, known as Michigan Enterprise Contact Center (MiECC), to provide centralized support to the State of Michigan (SOM) contact centers across multiple agencies. The purpose of the Contract is for Vendor to provide shared IT services to maintain and enhance MiECC contact centers.

Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW include the following:

1. Provide a Siebel web service(s) Web Service Definition Language (wsdl) to the IIT SAP e-Service web portal.

2. This web service(s) will enable the IIT SAP e-Service web portal to integrate to the Siebel Customer Relationship Management (CRM) system.



Page 2

Scope of Work MiECC will provide the following areas:

1. Provide web service(s) to enable the Treasury IIT SAP e-Services application to provide the following requests:

a. Provide the ability for IIT SAP e-Service to initiate a contact log/service request from a IIT Taxpayer and/or a Tax Practitioner when:

i. Taxpayer’s return status has been checked ii. Taxpayer’s status of correspondence is checked

iii. Taxpayer’s payment history is checked iv. Taxpayer submits specific questions with an

option to attach correspondence v. Taxpayer views inbound and outbound treasury

correspondence vi. Taxpayer reviews Treasury’s answers to

previously submitted questions vii. Taxpayer submits an address change request

2. Provide a Siebel web service(s) to retrieve IIT data that resides in Siebel. 3. Update the MiECC Enterprise Architecture Solution Assessment (EASA) and

include any new firewalls that need to be opened. 4. Provide SEM-0002 EXP component testing document. 5. Provide the SEM-0931 System Maintenance Document for requirements. 6. Provide SEM-0720 installation Plan for Go-Live deployment.

Acceptance Criteria Each System Engineering Methodology (SEM) phase shall have an acceptance form that documents phase deliverable completion, open issues, and implementation considerations. Vendor, DTMB and Agency SOW authorized approvers shall review and sign acceptance according to Acceptance terms identified in Section 2.250 of Contract.

Specific Department Standards MiECC will comply with DTMB Development Standards when performing this work.



Page 3

Expected Contractor Work Hours and Conditions Services provided under this SOW shall be performed Monday through Friday between the hours of 8:00 AM and 5:00 PM.

Contractor Response to Service Request

Work Description The MiECC Accenture Team will provide the services described in this section below. Accenture as part of the DTMB-MiECC team has successfully provided the contact center technical project implementation, documentation and support services for other State of Michigan contact center projects.

Impacts of Not Making Requested Changes The impact of foregoing this Statement of Work would not allow Siebel to interface with the new IIT SAP e-Service web portal.

Deliverables 2. Provide web service(s) to enable the IIT Treasury SAP e-Services application to

provide the following requests: a. Provide the ability for IIT SAP e-Service to initiate a contact log/service

request from a Taxpayer and/or a Tax Practitioner when: i. Taxpayer’s return status has been checked

ii. Taxpayer’s status of correspondence is checked iii. Taxpayer’s payment history is checked iv. Taxpayer submits specific questions with an

option to attach correspondence v. Taxpayer views inbound and outbound treasury

correspondence vi. Taxpayer reviews Treasury’s answers to

previously submitted questions vii. Taxpayer submits an address change request

7. Provide a Siebel web service(s) to retrieve IIT data that resides in Siebel. 8. Update the MiECC Enterprise Architecture Solution Assessment (EASA) and

include any new firewalls that need to be opened. 9. Provide SEM-0002 EXP component testing document. 10. Provide the SEM-0931 System Maintenance Document for requirements.



Page 4

11. Provide SEM-0720 installation Plan for Go-Live deployment.

Responsibilities and Assumptions Vendor, State, and Agency staff responsibilities for work under this SOW are depicted in the table below.

Responsibilities Responsibility MiECC Agency DTMB Completion of Agency Service Request Section of SOW √ √

Completion of Proposal Response Section of SOW √

Sign Statement of Work √ √ √ Issue Purchase Order √ √ Agree Upon Project Resources and Schedule √ √ √

Complete Deliverables as Defined in SOW √

Participate in Deliverable Review as Defined in SOW √ √

Document Phase Review Acceptance in Acceptance √

Review Phase and Overall Project Acceptance Documents and Sign √ √ √

Provide Access to Resources (e.g., Business Experts, Systems, Software, and Hardware) Required to Perform Services

√ √

Assumptions 1. This Statement of Work, SOW-084 Treasury Siebel SAP Web Services ("SOW")

incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and Support– DTMB/(Treasury) (the “Contract”) between Accenture LLP (“Vendor”) and the State of Michigan Department of Management and Budget Acquisition Services (the “State”) effective May 1, 2012.

2. State will provide access to resources (e.g., business experts, software, systems, hardware) required to perform services described in this SOW.

3. Actual services will commence upon execution of this SOW by parties, State purchase order issuance, and confirmed final project plan, roles and responsibility (RACI) and governance structure with State of Michigan and Accenture.

4. Accenture assumes that the requirement and other information provided by or referenced by the State is accurate and complete. If, after the SOW is signed, it is determined that the requirements or other information provided by the State is inaccurate or incomplete in any material manner, the parties will negotiate an adjustment in the project scope and fees, as applicable.



Page 5

5. Changes to the information provided by the State, including additional services, items or equipment the State deems necessary and essential after SOW and Purchase Order issuance; will go through a mutually-agreed upon change control process to address potential impacts to the proposed services that may affect project schedule and/or cost. If the project budget is exceeded for this SOW additional hours may be added with a mutually agreed upon change request.

6. The State will obtain all consents necessary from its third parties (i.e., those not under Agreement with Accenture) required for Accenture to perform its obligations under this SOW. The State will be responsible for the contractual relationship with such third parties and for facilitating their cooperation with Accenture. Accenture will not have any responsibility for the performance of other contractors or vendors engaged by the State or delays caused by them.

7. This is a time and materials SOW, hours that are not consumed will not be billed to the State of Michigan.

8. If there is a resource staffing change by either party that impacts delivery, the parties can mutually agree to re-examine the project plan, cost, and timelines and reserves the right to amend this Statement of Work accordingly.

9. State of Michigan will provide quality testing activities. Testing defects will be logged and managed during the System Test and User Acceptance phases by the State’s Testing team.

10. Siebel is not providing or responsible for user authentication of the Taxpayer and or Tax Practitioner login to the SAP e-Service web site.

11. DTMB System Security Plan (SSP), Key Light security documentation will be completed by Treasury and DTMB Agency Services.

12. DTMB Agency services would be responsible for hosting the web system architecture.

13. SAP e-Services would interface directly with FileNet to pull and push documents. Siebel only provides a FileNet document ID (GUID) through the SEAH process. Siebel will not interface with FileNet for any SAP e-Service customer documents.

14. Project management and infrastructure connectivity would be provided by Treasury. 15. The data provided from Siebel to SAP e-Service application is typically 24-48 hours

behind (nightly batch process) the Mainframe source application. 16. This SOW is for the integration to the SAP IIT eServices. Any business tax self

service will be in Michigan Tax Online (MTO) and is not a part of this SOW. 17. Only tax data that is currently in Siebel will be available for the web services. There

will be no new mainframe data integration required. 18. This Web Service integration is for the current legacy Siebel IP2016 platform. Any

future upgrades to Siebel may require a different statement of work.



Page 6

Project Contacts The Vendor main contacts for this SOW include the following individuals:

Team Member

Role

Email Contact Information

Ryan Sadler Senior Delivery Leadership

[email protected]

Kristine Handy Contract Manager [email protected]

Project Control and Reports Accenture will submit a monthly hour’s report to the DTMB MiECC Program Director throughout the life of this project as part of time and material invoice.

Payment Schedule This is a time and materials SOW for a three-month period. The State of Michigan reserves the option to extend this SOW beyond this six-month period. Additional hours required to complete beyond six months shall be mutually agreed to and added as a change request to this SOW

Resource

Role

Resource Name

Hourly Rate

Total Est Hours

Payment Total

MiECC Team

MiECC Siebel Developer

TBD $116.05/hr. MiECC 480

$55,704

Total PO Amount required

$55,704

Travel and Expenses The State does not pay for travel expenses including hotel, mileage, meals, parking etc.

mailto:[email protected]


STATE OF MICHIGAN






[email protected]

William Pemble

Matt Weiss

[email protected]

Kathleen Cawley

Southfield, MI 48075

ACCENTURE

CV0062320

859-248-1187

3000 Town Center, Suite 2400

(517) 256-9895S

TA

TE

Pro

gra

m

Man

ag

er

Co

ntra

ct

Ad

min

istra

tor

CO

NT

RA

CT

OR

DTMB

517-636-4741

DTMB

[email protected]

$43,697,383.41

May 1, 2012 April 30, 2022


April 30, 2017


BEFORE

5 - 1 Year






☐ ☐ N/A


$0.00 $43,697,383.41

Effective 1/27/2020, the following amendment is hereby incorporated into the Contract to allow DHHS Child Welfare to transition to NICE inContact IVR. This amendment is to bring on Accenture resource Michael Grisinger, who is a Technical NICE-inContact Cloud Specialist. Total cost will be $37,178.00. Service Dates are 12/30/2019 - 12/29/2020


The Federal Provisions Addendum and Byrd Anti-Lobbying Certification are also added to this Contract.



DESCRIPTION

CONTRACT SUMMARY


SOW-083 MiSACWIS NICE-inContact

Page 1

Statement of Work (SOW)

Number:


Project Title: MiSACWIS NICE-inContact


SOW Summary Description: This project will create a cloud-based IVR on

the NICE-InContact Platform.

The IVR will be migrated to a Cloud based

platform and decommission the current IVR

Avaya/Genesys and Windows 2008 servers.



Requesting

Department/Agency

DTMB, Department of Health and Human

Services (DHHS) - MiSACWIS


Background

Over the years, DTMB has established a shared IT support service center, known as Michigan Enterprise Contact Center (MiECC), to provide centralized support to the State of Michigan (SOM) contact centers across multiple agencies. The purpose of the Contract is for Vendor to provide shared IT services to maintain and enhance MiECC contact centers.

The MiSACWIS Interactive Voice Response (IVR) is a phone-based system which allows Foster Care parents to report their hours to the MiSACWIS system. This IVR offers a



Page 2

convenient, quick way to ensure the families receive the funds to care for children in the State of Michigan Foster Care system. The IVR system receives approximately 5,000 calls per month and is an integral part of the MiSACWIS customer service eco-system.

Project Objective/Expected Benefits

The objective(s) and/or expected benefits for the services requested under this SOW include the following:

1. Migrate MISACWIS off the Avaya/Genesys contact center technology. 2. Decommission the outdated Windows 2008 servers. 3. Decommission the current Avaya/Genesys IVR. 4. Provide cost avoidance by using the latest contact center cloud-based technology. 5. Provide a more robust scalable, flexible, resilient cloud-based contact center

platform. 6. Keep the existing phone number by porting to the NICE-inContact platform.

Scope of Work

MiECC will provide services the following scope items:

a. Decommission of Windows 2008 servers and Avaya connectivity.

b. Provide technical guidance throughout the development lifecycle of the MISCAWIS NICE-inContact, contact center project.

c. Prepare and manage technical DTMB Enterprise Architecture Solution Assessment process and documentation.

d. Provide technical project escalation to MISCAWIS management. e. Reuse the existing integration to MiSACWIS database. f. Submit the SOM/DTMB architecture for Enterprise Architecture Solution

Assessment (EASA) approval (DTMB-3569) and create the System

Maintenance Plan (SEM-301).

g. Provide a technical NICE-inContact Cloud Specialist to assist in coordination

between NICE-InContact and MiSACWIS to plan and assist in the migration

and coordinate testing with the MiSACWIS.

h. Provide primary application technical support for the NICE-InContact

solution during the testing and implementation phase of the project

i. Technical liaison to the DTMB infrastructure teams for Cloud Connectivity

(IPSec).



Page 3

j. Provide support escalation for the customer to NICE-InContact.

k. Decommission of Windows 2008 servers and Avaya connectivity.

l. Port the Production phone number (855-643-6783) to the NICE-inContact

platform.

Acceptance Criteria

Each System Engineering Methodology (SEM) phase shall have an acceptance form that

documents phase deliverable completion, open issues, and implementation

considerations. Vendor, DTMB and Agency SOW authorized approvers shall review and

sign acceptance according to Acceptance terms identified in Section 2.250 of Contract.

Specific Department Standards

MiECC will comply with DTMB Development Standards when performing this work.


Work Description

The MiECC Accenture Team will provide the services described in this section below.

Accenture as part of the DTMB-MiECC team has successfully provided the contact

center technical project implementation, documentation and support services for other

State of Michigan contact center projects.

Provide the following services to support the DHHS-MiSACWIS Contact Center IVR Migration Project:

MiECC will provide support for the following areas:

a. Decommission of Windows 2008 servers and Avaya connectivity.

b. Provide technical guidance throughout the development lifecycle of the MISCAWIS NICE-inContact, contact center project.

c. Prepare and manage technical DTMB Enterprise Architecture Solution Assessment process and documentation.



Page 4

d. Provide technical project escalation to MISCAWIS management. e. Reuse the existing integration to MiSACWIS database. f. Submit the SOM/DTMB architecture for Enterprise Architecture Solution

Assessment (EASA) approval (DTMB-3569) and create the System

Maintenance Plan (SEM-301).

g. Provide a technical NICE-inContact Cloud Specialist to assist in coordination

between NICE-InContact and MiSACWIS to plan and assist in the migration

and coordinate testing with the MiSACWIS.

h. Provide primary application technical support for the NICE-InContact

solution during the testing and implementation phase of the project

i. Technical liaison to the DTMB infrastructure teams for Cloud Connectivity

(IPSec).

j. Provide support escalation for the customer to NICE-InContact.

k. Decommission of Windows 2008 servers and Avaya connectivity.

l. Port the Production phone number (855-643-6783) to the NICE-inContact

platform.

Impacts of Not Making Requested Changes

The contact center is a critical delivery channel of DHHS-MiSACWIS services across the

State of Michigan. The requested services are to implement an IVR solution on the

NICE-InContact solution. The MiSACWIS IVR is a critical part of providing customer

service to Michigan citizens and providing DHHS a cost effective, scalable, reliable

customer interaction solution. Not making the requested changes will result in the

following:

1. Increase in Infrastructure costs as a result of old Avaya/Genesys equipment.

2. Increate in Infrastructure costs for Windows 2008 support costs.

3. Degradation of user performance as a result of outdated equipment.

Deliverables

Deliverable Description

State of Michigan Required Documentation

Support DHHS-MiSACWIS with technical guidance required to requirements functionality definition, technical architecture.

Enterprise Architecture Solution Assessment



Page 5

DTMB 3569 (Enterprise Architecture Solution Assessment)

Format: Required State Documentation/ Word Document

DTMB SEM-301 System Maintenance Plan

Format: Required State Documentation/ Word Document

Responsibilities and Assumptions

Vendor, State, and Agency staff responsibilities for work under this SOW are depicted in the table below.

Responsibilities Responsibility MiECC Agency DTMB

Completion of Agency Service Request Section of SOW

√ √

Completion of Proposal Response Section of SOW

√

Sign Statement of Work √ √ √

Issue Purchase Order √ √

Agree Upon Project Resources and Schedule

√ √ √

Complete Deliverables as Defined in SOW

√

Participate in Deliverable Review as Defined in SOW

√ √

Document Phase Review Acceptance in Acceptance

√

Review Phase and Overall Project Acceptance Documents and Sign

√ √ √

Provide Access to Resources (e.g., Business Experts, Systems, Software,

√ √



Page 6

and Hardware) Required to Perform Services

Assumptions

1. This Statement of Work SOW-083 MiSACWIS NICE-inContact ("SOW")

incorporates by reference the terms, conditions and deliverables of Contract No.

071B2200168 for the Enterprise Contact Center Maintenance and Support–

DTMB/(State, MISCAWIS) (the “Contract”) between Accenture LLP (“Vendor”) and

the State of Michigan Department of Management and Budget Acquisition Services

(the “State”) effective May 1, 2012.

2. State will provide access to resources (e.g., business experts, software, systems,

hardware) required to perform services described in this SOW.

3. Actual services will commence upon execution of this SOW by parties, State

purchase order issuance, and confirmed final project plan, roles and responsibility

(RACI) and governance structure with State of Michigan and Accenture.

4. Changes to the information provided by the State, including additional services,

items or equipment the State deems necessary and essential after SOW and Purchase

Order issuance; will go through a mutually-agreed upon change control process to

address potential impacts to the proposed services that may affect project schedule

and/or cost.

5. Performance of this SOW is dependent on the State’s prompt and effective

performance of its responsibilities, including timely decisions and approvals.

6. The State will obtain all consents necessary from its third parties (i.e., those not

under Agreement with Accenture) required for Accenture to perform its obligations

under this SOW. The State will be responsible for the contractual relationship with

such third parties and for facilitating their cooperation with Accenture. Accenture

will not have any responsibility for the performance of other contractors or vendors

engaged by the State or delays caused by them.

7. This SOW assumes one resource across State of Michigan NICE-inContact projects

for a period of three months. Resources may be leveraged on similar State of

Michigan projects for delivery and continuity, this will not impact project timelines.

8. This is time and materials SOW, hours that are not consumed will not be billed to the

State of Michigan.

9. This SOW assumes a technical migration, so it is assumed that no changes to the

current, working IVR solution. The IVR will be migrated as is to the NICE-inContact

platform.



Page 7

10. The State of Michigan is responsible for the procurement of licenses and services

with the NICE-inContact.

11. If there is a resource staffing change, by either party, that impacts delivery, the

parties can mutually agree to re-examine the project plan, cost, and timelines and

reserves the right to amend this Statement of Work accordingly.

12. State of Michigan will provide quality testing activities. Testing defects will be

logged and managed during the System Test and User Acceptance phases by the

State’s Testing team.

13. MiSACWIS will test and verify that the input from the IVR is properly recorded in

the MiSACWIS database.

14. NICE-InContact will complete migration for the project, which includes the build

portion of the project.

15. The current Production phone number (855-643-6783) will be moved (ported) to the

NICE-inContact platform.

Project Contacts

The Vendor main contacts for this SOW include the following individuals:

Team Member

Role



[email protected]


Project Control and Reports

Accenture will submit a monthly hour’s report to the DTMB MiECC Program Director

throughout the life of this project as part of time and material invoice.

Payment Schedule

This is a time and materials SOW. The State of Michigan reserves the option to extend

this SOW. Additional hours required to extend this SOW shall be mutually agreed to

and added as a change request to this SOW.





Page 8

Resource

Role

Resource Name

Hourly Rate

Total Est Hours

Payment Total

MiECC Team

Technical NICE-in Contact Cloud Specialist

Michael Grisinger

$185.89/hr. MiECC (from

Accenture/State of Michigan

Rate card)

200

$37,178

Total PO Amount required

$37,178

Travel and Expenses The State does not pay for travel expenses including hotel, mileage, meals, parking etc

1 Version 4 Revised Date: 1/2019

Federal Provisions Addendum The provisions in this addendum may apply if the purchase will be paid for in whole or in part with funds obtained from the federal government. If any provision below is not required by federal law for this Contract, then it does not apply and must be disregarded. If any provision below is required to be included in this Contract by federal law, then the applicable provision applies and the language is not negotiable. If any provision below conflicts with the State’s terms and conditions, including any attachments, schedules, or exhibits to the State’s Contract, the provisions below take priority to the extent a provision is required by federal law; otherwise, the order of precedence set forth in the Contract applies. Hyperlinks are provided for convenience only; broken hyperlinks will not relieve Contractor from compliance with the law.

1. Federally Assisted Construction Contracts If this contract is a “federally assisted construction contract” as defined in 41 CRF Part 60-1.3, and except as otherwise may be provided under 41 CRF Part 60, then during performance of this Contract, the Contractor agrees as follows: (1) The Contractor will not discriminate against any employee or applicant for employment because of race, color, religion, sex, sexual orientation, gender identity, or national origin. The Contractor will take affirmative action to ensure that applicants are employed, and that employees are treated during employment without regard to their race, color, religion, sex, sexual orientation, gender identity, or national origin. Such action shall include, but not be limited to the following: Employment, upgrading, demotion, or transfer; recruitment or recruitment advertising; layoff or termination; rates of pay or other forms of compensation; and selection for training, including apprenticeship. The Contractor agrees to post in conspicuous places, available to employees and applicants for employment, notices to be provided setting forth the provisions of this nondiscrimination clause. (2) The Contractor will, in all solicitations or advertisements for employees placed by or on behalf of the Contractor, state that all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, or national origin. (3) The Contractor will not discharge or in any other manner discriminate against any employee or applicant for employment because such employee or applicant has inquired about, discussed, or disclosed the compensation of the employee or applicant or another employee or applicant. This provision shall not apply to instances in which an employee who has access to the compensation information of other employees or applicants as a part of such employee's essential job functions discloses the compensation of such other employees or applicants to individuals who do not otherwise have access to such information, unless such disclosure is in response to a formal complaint or charge, in furtherance of an investigation, proceeding, hearing, or action, including an investigation conducted by the employer, or is consistent with the Contractor's legal duty to furnish information. (4) The Contractor will send to each labor union or representative of workers with which he has a collective bargaining agreement or other contract or understanding, a notice to be provided advising the said labor union or workers' representatives of the Contractor's commitments under this section, and shall post copies of the notice in conspicuous places available to employees and applicants for employment. (5) The Contractor will comply with all provisions of Executive Order 11246 of September 24, 1965, and of the rules, regulations, and relevant orders of the Secretary of Labor. (6) The Contractor will furnish all information and reports required by Executive Order 11246 of September 24, 1965, and by rules, regulations, and orders of the Secretary of Labor, or pursuant thereto, and will permit access to his books, records, and accounts by the administering agency and the Secretary of Labor for purposes of investigation to ascertain compliance with such rules, regulations, and orders. (7) In the event of the Contractor's noncompliance with the nondiscrimination clauses of this contract or with any of the said rules, regulations, or orders, this Contract may be canceled, terminated, or suspended in whole or in part and the Contractor may be declared ineligible for further Government contracts or federally assisted construction contracts in accordance with procedures authorized in Executive Order 11246 of September 24, 1965, and such other sanctions may be imposed and remedies invoked as provided in Executive Order 11246 of September 24, 1965, or by rule, regulation, or order of the Secretary of Labor, or as otherwise provided by law.

https://www.law.cornell.edu/cfr/text/41/60-1.3

https://www.law.cornell.edu/cfr/text/41/part-60

https://www.dol.gov/ofccp/regs/statutes/eo11246.htm





(8) The Contractor will include the portion of the sentence immediately preceding paragraph (1) and the provisions of paragraphs (1) through (8) in every subcontract or purchase order unless exempted by rules, regulations, or orders of the Secretary of Labor issued pursuant to section 204 of Executive Order 11246 of September 24, 1965, so that such provisions will be binding upon each subcontractor or vendor. The Contractor will take such action with respect to any subcontract or purchase order as the administering agency may direct as a means of enforcing such provisions, including sanctions for noncompliance: Provided, however, that in the event a Contractor becomes involved in, or is threatened with, litigation with a subcontractor or vendor as a result of such direction by the administering agency, the Contractor may request the United States to enter into such litigation to protect the interests of the United States.

2. Davis-Bacon Act (Prevailing Wage)

a. If applicable, the Contractor (and its Subcontractors) for prime construction contracts in excess of $2,000 must comply with the Davis-Bacon Act (40 USC 3141-3148) as supplemented by Department of Labor regulations (29 CFR Part 5, “Labor Standards Provisions Applicable to Contracts Covering Federally Financed and Assisted Construction”).

b. The Contractor (and its Subcontractors) shall pay all mechanics and laborers employed directly on the site of the work, unconditionally and at least once a week, and without subsequent deduction or rebate on any account, the full amounts accrued at time of payment, computed at wage rates not less than those stated in the advertised specifications, regardless of any contractual relationship which may be alleged to exist between the Contractor or subcontractor and the laborers and mechanics;

c. The Contractor will post the scale of wages to be paid in a prominent and easily accessible place at the site of the work;

d. There may be withheld from the Contractor so much of accrued payments as the contracting officer considers necessary to pay to laborers and mechanics employed by the Contractor or any Subcontractor on the work the difference between the rates of wages required by the Contract to be paid laborers and mechanics on the work and the rates of wages received by the laborers and mechanics and not refunded to the Contractor or Subcontractors or their agents.

3. Copeland “Anti-Kickback” Act

If applicable, the Contractor must comply with the Copeland “Anti-Kickback” Act (40 USC 3145), as supplemented by Department of Labor regulations (29 CFR Part 3, “Contractors and Subcontractors on Public Building or Public Work Financed in Whole or in Part by Loans or Grants from the United States”), which prohibits the Contractor and subrecipients from inducing, by any means, any person employed in the construction, completion, or repair of public work, to give up any part of the compensation to which he or she is otherwise entitled.

4. Contract Work Hours and Safety Standards Act If the Contract is in excess of $100,000 and involves the employment of mechanics or laborers, the Contractor must comply with 40 USC 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5), as applicable.

5. Rights to Inventions Made Under a Contract or Agreement

If the Contract is funded by a federal “funding agreement” as defined under 37 CFR §401.2 (a) and the recipient or subrecipient wishes to enter into a contract with a small business firm or nonprofit organization regarding the substitution of parties, assignment or performance of experimental, developmental, or research work under that “funding agreement,” the recipient or subrecipient must comply with 37 CFR Part 401, “Rights to Inventions Made by Nonprofit Organizations and Small Business Firms Under Government Grants, Contracts and Cooperative Agreements,” and any implementing regulations issued by the awarding agency.

6. Clean Air Act


https://www.law.cornell.edu/uscode/text/40/subtitle-II/part-A/chapter-31/subchapter-IV


https://www.dol.gov/whd/regs/statutes/copeland.htm

https://www.law.cornell.edu/uscode/text/40/3145






If this Contract is in excess of $150,000, the Contractor must comply with all applicable standards, orders, and regulations issued under the Clean Air Act (42 USC 7401-7671q) and the Federal Water Pollution Control Act (33 USC 1251-1387). Violations must be reported to the federal awarding agency and the regional office of the Environmental Protection Agency.

7. Debarment and Suspension A “contract award” (see 2 CFR 180.220) must not be made to parties listed on the government-wide exclusions in the System for Award Management (SAM), in accordance with the OMB guidelines at 2 CFR 180 that implement Executive Orders 12549 (3 CFR part 1986 Comp., p. 189) and 12689 (3 CFR part 1989 Comp., p. 235), “Debarment and Suspension.” SAM Exclusions contains the names of parties debarred, suspended, or otherwise excluded by agencies, as well as parties declared ineligible under statutory or regulatory authority other than Executive Order 12549.

8. Byrd Anti-Lobbying Amendment

If this Contract exceeds $100,000, bidders and the Contractor must file the certification required under 31 USC 1352.

9. Procurement of Recovered Materials Under 2 CFR 200.322, a non-Federal entity that is a state agency or agency of a political subdivision of a state and its

contractors must comply with section 6002 of the Solid Waste Disposal Act, as amended by the Resource Conservation and Recovery Act. The requirements of Section 6002 include procuring only items designated in guidelines of the Environmental Protection Agency (EPA) at 40 CFR part 247 that contain the highest percentage of recovered materials practicable, consistent with maintaining a satisfactory level of competition, where the purchase price of the item exceeds $10,000 or the value of the quantity acquired during the preceding fiscal year exceeded $10,000; procuring solid waste management services in a manner that maximizes energy and resource recovery; and establishing an affirmative procurement program for procurement of recovered materials identified in the EPA guidelines.

https://www.law.cornell.edu/cfr/text/2/180.220

https://www.sam.gov/portal/SAM/?portal:componentId=78d3f342-d23f-424a-a04a-d978528069c2&interactionstate=JBPNS_rO0ABXc0ABBfanNmQnJpZGdlVmlld0lkAAAAAQATL2pzZi9uYXZpZ2F0aW9uLmpzcAAHX19FT0ZfXw**&portal:type=action


https://www.law.cornell.edu/cfr/text/2/200.322

https://www.gpo.gov/fdsys/granule/CFR-2002-title40-vol21/CFR-2002-title40-vol21-part247


Byrd Anti-Lobbying Certification

The following certification and disclosure regarding payments to influence certain federal transactions are made under FAR 52.203‐11 and 52.203‐12 and 31 USC 1352, the “Byrd Anti‐Lobbying Amendment.” Hyperlinks are provided for convenience only; broken hyperlinks will not relieve Contractor from compliance with the law.

1. FAR 52.203‐12, “Limitation on Payments to Influence Certain Federal Transactions” is hereby incorporated by

reference into this certification.

2. The bidder, by submitting its proposal hereby certifies to the best of his or her knowledge and belief that:

a. No federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any agency, a member of Congress, an officer or employee of Congress, or an employee of a member of Congress on his or her behalf in connection with the awarding of any federal contract, the making of any federal grant, the making of any federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment or modification of any federal contract, grant, loan, or cooperative agreement;

b. If any funds other than federal appropriated funds (including profit or fee received under a covered federal transaction) have been paid, or will be paid, to any person for influencing or attempting to influence an officer or employee of any agency, a member of Congress, an officer or employee of Congress, or an employee of a member of Congress on his or her behalf in

connection with this solicitation, the bidder must complete and submit, with its proposal, OMB standard form LLL, Disclosure of Lobbying Activities, to the Solicitation Manager; and

c. He or she will include the language of this certification in all subcontract awards at any tier and require that all recipients of subcontract awards in excess of $150,000 must certify and disclose accordingly.

3. This certification is a material representation of fact upon which reliance is placed at the time of Contract award. Submission of this certification and disclosure is a prerequisite for making or entering into this Contract under 31 USC 1352. Any person making an expenditure prohibited under this provision or who fails to file or amend the disclosure form to be filed or amended by this provision is subject to a civil penalty of not less than $10,000, and not more than $100,000, for each such failure.


https://www.law.cornell.edu/cfr/text/48/52.203-12

https://www.gsa.gov/portal/forms/download/116430

https://www.gsa.gov/portal/forms/download/116430


STATE OF MICHIGAN






[email protected]

William Pemble

Matt Weiss

[email protected]

Kathleen Cawley

Detroit, MI 48226

ACCENTURE

CV0062320

859-248-1187

1001 Woodward Ave. 4th Floor

(517) 256-9895S

TA

TE

Pro

gra

m

Man

ag

er

Co

ntra

ct

Ad

min

istra

tor

CO

NT

RA

CT

OR

DTMB

517-636-4741

DTMB

[email protected]

$43,697,383.41

May 1, 2012 April 30, 2022


April 30, 2017


BEFORE

5 - 1 Year






☐ ☐ N/A


$0.00 $43,697,383.41

Effective 1/13/2020, the following amendment is hereby incorporated into the Contract to upgrade Treasury’s call center to Siebel's 2016 software version. Total cost will be $1,461,408.00.




DESCRIPTION

CONTRACT SUMMARY


SOW-085 Treasury Siebel 2016 Upgrade

Page 1

Statement of Work (SOW) Number:


Project Title: Treasury Siebel 2016 Upgrade


SOW Summary Description: Upgrade Siebel t0 2016 version



Requesting Department/Agency

DTMB, Treasury



Project Objective/Expected Benefits The objective is to move Treasury off the end of life, Windows 2008 servers and move to Windows 2016 servers in the State’s hosted Next Generation Digital Infrastructure (NGDI) hosting center. To achieve this objective, the existing Siebel 2013 version needs to be upgraded and the infrastructure needs to be set up in the State’s NGDI hosting center. Treasury has made the decision to upgrade to the Siebel 2016 version.



Page 2

Treasury has asked MiECC/Accenture to upgrade Siebel to the 2016 version, re-establish the existing integration end points. To assist with this this project, Accenture will provide experienced Oracle consultants that will help with the Siebel upgrade.

The objective(s) and/or expected benefits for the services requested under this SOW include the following:

• Benefits of a newer Siebel version to help improve customer experience. • Application will be loaded to the State’s Next Generation Digital Infrastructure

(NGDI), which will replace the outdated, end-of-life Windows 2008 servers. • Supports TLS 1.2 • No longer uses ActiveX controls and Java JRE plug-in.

Scope of Work MiECC will provide the following:

1. Provide a Siebel upgrade 2016 implementation task plan. 2. Deliver input into the EASA Architecture diagram for the State of Michigan

hosting center to Treasury Agency Services. 3. Deliver server requirements and specifications to Treasury Agency Services for

their input into the State’s Infrastructure Service Request (ISR) tool (DIT-0184). 4. Deliver to Treasury the overview of the Upgrade Release architecture and key

features. 5. Upgrade Siebel CRM to version 2016 to the following environments:

a. Treasury Development b. Treasury Test c. Treasury Production.

6. Integration and Unit testing for Siebel 2016, including: a. FileNet viewer b. Datacap c. Siebel Event Action Handler (SEAH) Connector d. Tidal – daily refresh batch jobs e. SAP Data Translator – Inbound f. SAP PoA - Power of Attorney g. Service Request to SAP - Outbound h. Individual Income Tax (IIT) IVR web service



Page 3

i. Business Tax IVR web service j. Genesys IWS Connector k. Genesys IWD Discovery l. Genesys IWD IIT m. Genesys IWD Business Tax n. IIT Outbound Correspondence o. Siebel Message Broadcast change p. MARCS.

7. Provide installation Plan for Go-Live deployment.


Specific Department Standards MiECC will comply with DTMB Development Standards when performing this work.


Work Description The MiECC Accenture Team will provide the services described in this section below. Accenture, as part of the DTMB-MiECC team has successfully provided the contact center technical project implementation, documentation and support services for other State of Michigan contact center projects.




Page 4

Treasury would continue to incur additional infrastructure and software costs for Windows 2008 extended support.

Deliverables 1. Provide a Siebel upgrade 2016 implementation task plan. 2. Deliver input into the EASA Architecture diagram for the State of Michigan

hosting center to Treasury Agency Services. 3. Deliver server requirements and specifications to Treasury Agency Services for

input into the State’s Infrastructure Service Request (ISR) tool (DIT-0184). 4. Deliver to Treasury the overview of the Upgrade Release architecture and key

features. 5. Upgrade Siebel CRM to version 2016 to the following environments:

a. Treasury Development b. Treasury Test c. Treasury Production.

6. Integration and Unit testing for Siebel 2016, including: a. FileNet viewer b. Datacap c. Siebel Event Action Handler (SEAH) Connector d. Tidal – daily refresh batch jobs e. SAP Data Translator – Inbound f. SAP PoA - Power of Attorney g. Service Request to SAP - Outbound h. Individual Income Tax (IIT) IVR web service i. Business Tax IVR web service j. Genesys IWS Connector k. Genesys IWD Discovery l. Genesys IWD IIT m. Genesys IWD Business Tax n. IIT Outbound Correspondence o. Siebel Message Broadcast change p. MARCS.

7. Provide installation Plan for Go-Live deployment.



Page 5


Responsibilities Responsibility MiECC Agency DTMB Completion of Agency Service Request Section of SOW √ √

Completion of Proposal Response Section of SOW √

Sign Statement of Work √ √ √ Issue Purchase Order √ √ Agree Upon Project Resources and Schedule √ √ √

Complete Deliverables as Defined in SOW √

Participate in Deliverable Review as Defined in SOW √ √

Document Phase Review Acceptance in Acceptance √

Review Phase and Overall Project Acceptance Documents and Sign √ √ √

Provide Access to Resources (e.g., Business Experts, Systems, Software, and Hardware) Required to Perform Services

√ √

Assumptions 1. This Statement of Work, SOW-085 Treasury Siebel 2016 Upgrade ("SOW")

incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and Support– DTMB/(Treasury) (the “Contract”) between Accenture LLP (“Vendor”) and the State of Michigan Department of Management and Budget Acquisition Services (the “State”) effective May 1, 2012.

2. State will provide access to resources (e.g., business experts, software, systems, hardware) required to perform services described in this SOW. Delayed access to SOM resources and SOM resource’s required actions could impact timelines and cost of services.

3. Services will commence upon execution of this SOW by parties and the State’s issuance of a purchase order, and confirmed final project plan, roles and responsibility (RACI) and governance structure with State of Michigan and Accenture. The parties acknowledge that once the SOW is executed and PO issues the Services under this SOW cannot be delayed or placed on hold.

4. Changes to the information related to scope provided by the State, including, but not limited to additional services, items or equipment the State deems necessary and essential after SOW and Purchase Order issuance; will go through a mutually-agreed upon change control process to address potential impacts to the proposed services



Page 6

that may affect project schedule and/or cost. If the project budget is exceeded for this SOW additional hours will be added with a mutually agreed upon change request.

5. The State will obtain all consents and licensing necessary from its third parties (i.e., those not under Agreement with Accenture, reference page 4, item #6) required for Accenture to perform its obligations under this SOW. The State will be responsible for the contractual relationship with such third parties and for facilitating their cooperation with Accenture. Accenture will not have any responsibility for the performance of other contractors or vendors engaged by the State or delays caused by them.

6. This is a “Not To Exceed” SOW for nine months. Costs that are not consumed will not be billed to the State of Michigan.

7. If there is a resource staffing change by either party that impacts delivery, the parties can mutually agree to re-examine the project plan, cost, and timelines and reserves the right to amend this Statement of Work accordingly.

8. State of Michigan will provide quality assurance testing activities, it is the responsibility of the State to coordinate with the Testing team. Testing defects will be logged and managed during the System Test and User Acceptance phases by the State’s Testing team.

9. DTMB System Security Plan (SSP), Key Light security documentation will be completed by Treasury and DTMB Agency Services.

10. This project will run independently from other Treasury projects. It will run per the project schedule as identified in Section A. Other Treasury projects that are dependent on Siebel will align their project schedules with this upgrade.

11. Treasury DTMB Agency Services will manage any infrastructure requirements to support the upgrade including, but not limited to, firewall, database support and Office Automation requests.

12. This SOW assumes that Accenture and Oracle (“Subcontractor”) come to a mutual agreement for subcontracting services. If an agreement between Accenture and Oracle cannot be reached, Accenture reserves the right to terminate this SOW with Treasury.

13. Oracle has identified key resources that are available to start January 15, 2020. Any delays in the start of this project could jeopardize the availability of key Oracle resources and the delivery of the project.

14. This SOW assumes Treasury Agency services will have requisitioned the necessary servers in the NGDI environment for the Oracle team to begin application load. Any delays in this process will delay the project schedule.



Page 7

15. There is no e-Service model for Siebel 2016. There is a separate SOW for the e-Service integration to SAP.

16. This SOW must be approved, and a Purchase Order generated through the State’s Sigma process prior to Accenture and Oracle beginning work. Any delays past January 15, 2020 will delay the project schedule.

17. Integration for Siebel 2016 is dependent on an Oracle database upgrade to 12c. Treasury Agency Services and the DTMB Database Administrators are responsible for the upgrade to 12c. The Database upgrades must be completed prior to their respective regions according to the Siebel upgrade schedule (Section A).

a. Development Oracle 12c prior to 2/1/2020 b. Test Oracle 12c prior to 4/1/2020 c. Production Oracle 12c prior to 6/1/2020

18. The requested NGDI infrastructure and firewalls shall be ready prior to January 15, 2020 for the Oracle resources to begin the upgrade and keep the project on schedule.

19. If this Siebel upgrade project is implemented prior to the Genesys IVR project implementation, the Genesys IVR project vendor will need to consume the updated Siebel 2016 system.

20. Dependent Treasury projects starting after this SOW is approved will follow and adhere to the Siebel 2016 SOW schedule.

21. This SOW is MiECC’s priority for Treasury. MiECC resources can not be pulled off for other Treasury work (e.g. attending meetings, troubleshooting, resolving other vendor project issues).

22. Any other Treasury projects that depend on this Siebel 2016 upgrade for their integration and or testing will need to wait until this project has completed the Build Test Region phase. No resources allocated to this SOW will be pulled off and assigned to other Treasury projects.

23. Once this Siebel 2016 upgrade begins, the current production Siebel environment shall be frozen from making any changes.

24. No new business requirements or functionality will be added as part of this upgrade. This is technical Siebel software upgrade to replace Siebel 2013 with Siebel 2016.

25. No new integrations will be added once the Services of this SOW are started. 26. Siebel product defects are out of scope for purposes of the SOW. 27. Any 3rd party software incompatibilities with Siebel 2016 are outside of the Scope of

this SOW. 28. MiECC team will work with Oracle support for Siebel defects that Oracle does not

deem a known product defect. 29. If any risks to this project become realized, this would likely delay the project

schedule accordingly.



Page 8

30. The MiECC/Accenture and Oracle resources will be located at Capitol Commons Building, 400 S. Pine St. Lansing MI and follow a Monday-Friday, 8:00am-5:00pm schedule.

31. MiECC will provide a bi-weekly status report to the DTMB-MiECC Director. 32. This project will observe the following State of Michigan holiday schedule for 2020.

Resources will not be working or billing against the project on these days:

New Year's Day January 1, 2020 Martin Luther King Jr January 20, 2020 President's Day February 17, 2020 Memorial Day May 25, 2020 Independence Day (observed) July 3, 2020 Labor Day September 7, 2020 Veteran's Day November 11, 2020 Thanksgiving November 26, 2020 Day after Thanksgiving November 27, 2020 Christmas Eve December 24, 2020 Christmas Day December 25, 2020 New Year’s Eve December 31, 2020

33. MiECC and Oracle will support the State’s test team during their system and UAT

testing phase. 34. MiECC will support the Siebel 2016 upgrade after production deployment as part of

the ongoing base team support.



Page 9

Project Schedule – Section A This is the high-level estimated project schedule. Dates may be affected based on other project dependencies that are delayed or have other issues. This project schedule will not be crashed or altered by other Treasury projects.


Team Member

Role



[email protected]






Page 10

Project Control and Reports Accenture will submit a monthly hour’s report to the DTMB MiECC Program Director throughout the life of this project as part of time and material invoice.

Payment Schedule This is a time and materials SOW for a nine-month period. The State of Michigan reserves the option to extend this SOW beyond this nine-month period. Additional hours required to complete beyond nine months shall be mutually agreed to and added as a change request to this SOW.

Resource

Role Hourly

Rate

Total Est

Hours Payment

Total MiECC

Integration Developer

MiECC Integration Developer $116.05/hr.

MiECC 960

$111,408

$111,408

Resource

Role

Monthly Firm Fix

cost (“Not To

Exceed”) Months

Payment

Total Oracle

Consultants (2) Senior Technical

Siebel Consultants

(1) Siebel Project Manager

$150,000 9

$1,350,000

$ 1,350,000

Total SOW PO Amount

required

$ 1,461,408



Page 11

Travel and Expenses The State does not pay for travel expenses including hotel, mileage, meals, parking etc.

ST ATE OF MICHIGAN CENTRAL PROCUREMENT SERVICES Department of Technology, Management, and Budget 525 W. ALLEGAN ST., LANSING, MICHIGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909



to Contract Number 071 B2200168

ACCENTURE


Southfield, Ml 48075 [email protected]

Kathleen Cawley

859-248-1187

[email protected] [email protected]

DTMB

DTMB

Effective with mutual signature the attached documentation {IRS Pub 1075 and Attachment B) is executed and appended to the Contract. Additionally, all references to "Appendix K" in the Contract, including in Section 1.103, shall be replaced with "Exhibit 7 to Pub 1075 and Attachment B." All other terms and conditions remain the same.

Safeguarding Contract Language Exhibit 7

Exhibit 7 Safeguarding Contract Language

CONTRACT LANGUAGE FOR TECHNOLOGY SERVICES

I. PERFORMANCE

In performance of this contract, the contractor agrees to comply with and assume responsibility for compliance by his or her employees with the following requirements:

(1) All work will be done under the supervision of the contractor or the contractor's employees.

(2) The contractor and the contractor's employees with access to or who use FTI must meet the background check requirements defined in IRS Publication 1075.

(3) Any return or return information made available in any format shall be used only for the purpose of carrying out the provisions of this contract. Information contained in such material will be treated as confidential and will not be divulged or made known in any manner to any person except as may be necessary in the performance of this contract. Disclosure to anyone other than an officer or employee of the contractor will be prohibited.

(4) All returns and return information will be accounted for upon receipt and properly stored before, during, and after processing. In addition, all related output will be given the same level of protection as required· for the source material. · ·

(5) The contractor certifies that the data processed during the performance of this contract will be completely purged from all data storage components of his or her computer facility, and no output will be retained by the contractor at the time the work is completed. If immediate purging of all data storage components is not possible, the contractor certifies that any IRS data remaining in any storage component will be safeguarded to prevent unauthorized disclosures.

(6) Any spoilage or any intermediate hard copy printout that may result during the processing of IRS data will be given to the agency or his or her designee. When this Is not possible, the contractor will be responsible for the destruction of the spoilage or any intermediate hard copy printouts, and will provide the agency or his or her designee with a statement containing the date of destruction, description of material destroyed, and the method used.

(7) All computer systems receiving, processing, storing or transmitting FTI must meet the requirements defined in IRS Publication 1075. To meet functional and assurance requirements, the security features of the environment must provide for the managerial, operational, and technical controls. All security features must be available and activated to protect against unauthorized use of and access to Federal Tax Information.

(8) No work involving Federal Tax Information furnished under this contract will be subcontracted without prior written approval of the IRS.

(9) The contractor will maintain a list of employees authorized access. Such list will be provided to the agency and, upon request, to the IRS reviewing office.(10) The agency will have the right to void the contract if the contractor fails to provide the safeguards described above.

(10) (Include any additional safeguards that may be appropriate.)

Publication 1075 (September 2016) Safeguarding Contract Language Exhibit 7

Safeguarding Contract Language Exhlbit7


II. CRIMINAL/CIVIL SANCTIONS

(1) Each officer or employee of any person to whom returns or return information is or may be disclosed will be notified in writing by such person that returns or return information disclosed to such officer or employee can be used only for a purpose and to the extent authorized herein, and that further disclosure of any such returns or return information for a purpose or to an extent unauthorized herein constitutes a felony punishable upon conviction by a fine of as much as $5,000 or imprisonment for as long as 5 years, or both, together with the costs of prosecution. Such person shall also notify each such officer and employee that any such unauthorized further disclosure of returns or return information may also result in an award of civil damages against the officer or employee in an amount not less than $1,000 with respect to each instance of unauthorized disclosure. These penalties are prescribed by IRCs 7213 and 7431 and setforth at 26 CFR 301.6103(n)-1.

(2) Each officer or employee of any person to whom returns or return information is or may be disclosed shall be notified in writing by such person that any return or return information made available in any format shall be used only for the purpose of carrying out the provisions of this contract. Information contained in such material shall be treated as conficjential and shall not be divulged or made known in any manner to any person except as may be necessary in the performance of the contract. Inspection by or disclosure to anyone without an official need-toknow constitutes a criminal misdemeanor punishable upon conviction by a fine of as much as $1,000 or imprisonment for as long as 1 year, or both, together with the costs of prosecution. Such person shall also notify each such officer and employee that any such unauthorized inspection or disclosure of returns or return information may also result in an award of civil damages against the officer or employee [United States for Federal employees] in an amount equal to the sum of the greater of $1,000 for each act of unauthorized inspection or disclosure with respect to which such defendant is found liable or the sum of the actual damages sustained by the plaintiff as a result of such unauthorized inspection or disclosure plus in the case of a willful inspection or disclosure which is the result of gross negligence, punitive damages, plus the costs of the action. These penalties are prescribed by IRC 7213A and 7431 and set forth at 26 CFR 301.6103(n)-1.

(3) Additionally, it is incumbent upon the contractor to inform its officers and employees of the penalties for improper disclosure imposed by the Privacy Act of 1974, 5 U.S.C. 552a. Specifically, 5 U.S.C. 552a(i)(1), which is made applicable to contractors by 5 U.S.C. 552a(m)(1), provides that any officer or employee of a contractor, who by virtue of his/her employment or official position, has possession of or access to agency records which contain individually identifiable information, the disclosure of which is prohibited by the Privacy Act or regulations established thereunder, and who knowing that disclosure of the specific material is prohibited, willfully discloses the material in any manner to any person or agency not entitled to receive it, shall be guilty of a misdemeanor and fined not more than $5,000.

(4) Granting a contractor access to FTI must be preceded by certifying that each individual understands the agency's security policy and procedures for safeguarding IRS information. Contractors must maintain their authorization to access FTI through annual recertification. The initial certification and recertification must be documented and placed in the agency's files for review. As part of the certification and at least annually afterwards, contractors must be advised

Publication 1075 (September 2016) Safeguarding Contract language Exhibit 7

Safeguarding Contract Language Exhibit7


of the provisions of IRCs 7431, 7213, and 7213A (see Exhibit 4, Sanctions for Unauthorized Disclosure, and Exhibit 5, Civil Damages for Unauthorized Disclosure). The training provided before the initial certification and annually thereafter must also cover the incident response policy and procedure for reporting unauthorized disclosures and data breaches. (See Section 10) For both the initial certification and the annual certification, the contractor must sign, either with ink or electronic signature, a confidentiality statement certifying their understanding of the security requirements.

Ill. INSPECTION

The IRS and the Agency, with 24 hour notice, shall have the right to send its inspectors into the offices and plants of the contractor to inspect facilities and operations performing any work with FTI under this contract for compliance with requirements defined in IRS Publication 1075. The IRS' right of inspection shall include the use of manual and/or automated scanning tools to perform compliance and vulnerability assessments of information technology (IT) assets that access, store, process or transmit FTI. On the basis of such inspection, corrective actions may be required in cases where the contractor is found to be noncom pliant with contract safeguards.

Publication 1075 (September 2016) Safeguarding Contract Language Exhibit 7

10-17-18 vs. 1.0

Attachment B

SAFEGUARD REQUIREMENTS OF CONFIDENTIAL TAX DATA

This section sets forth the safeguard requirements for handling, storage, and processing of confidential tax information for a Contractor and their subcontractor(s) and is incorporated as an integral part of the Contract. It will facilitate administration and enforcement of the laws of the State of Michigan in a manner consistent with the applicable statutes, regulations, published rules and procedures or written communication.

I. Authority Authority for the Michigan Department of Treasury to require that this section be included in the Contract is contained in 1941 PA 122, as amended, MCL 205.28(1)(f), which subjects current or former contractors to the same restrictions and penalties imposed upon department employees regarding the treatment of confidential information. A private contractor or its employees are strictly prohibited from disclosing taxpayer information to a third party. The prohibition against disclosure does not bar an employee of a private contractor with whom the State of Michigan (State) contracts that processes tax returns or payments pursuant to the Contract from having access to confidential.information that is reasonably required for the processing or collection of amounts due this State. Private contractors and any subcontractors will follow Treasury guidelines for Authorized representatives.

II. Confidentiality It is agreed that all information exchanged under this section will be kept confidential in accordance with the confidentiality provisions contained in the Revenue Act, MCL 205.28(l)(f)-which states in part;

"Except as otherwise provided in this subdivision, an employee, authorized representative, or former employee or authorized representative of the department or anyone connected with the department will not divulge any facts or information obtained in connection with the administration of a tax or information or parameters that would enable a person to ascertain the audit selection or processing criteria of the department for a tax administered by the department."

Confidential information obtained under this contract will not be disclosed except as required by state law, or in the proper administration of applicable laws, promulgated rules and procedures. In the event, confidentiality statutes are amended, Treasury will notify Contractor of any changes. No employee, agent, authorized representative or legal representative of Contractor will disclose any information obtained by viitue of this section to any other division within their company or any other governmental agency, department or unit within such governmental agency whether local, state, federal or foreign, department or unit within such governmental agency, or any unauthorized third party. No tax returns or tax return information accessed by Contractor will be duplicated or disseminated within or outside the company without the written approval of the Contract Compliance Inspector. Tax returns and tax return information remain the property of Treasury.

1

Contractot· may use a taxpayer's name, address and Social Security number or employer identification number to the extent necessary in connection with the processing and mailing of forms for any report or return required in the administration of any tax in the performance of the Contract. The use of the Social Security number must be in accordance with the state Social Security Number Privacy Act 454 of 2004, as amended.

Confidential information obtained under this agreement will not be disclosed in pmt of a report or document that is subject to FOIA.

The penalties for violating the confidentiality provisions of the Revenue Act are contained in, MCL 205.28(2) and MCL 205.27(4). MCL 205.28(2) states:

"A person who violates subsection (l)(e), (l)(t), (4) or (5) is guilty of a felony, punishable by a fine of not more than $5,000.00, or imprisonment for not more than 5 years, or both, together with the costs of prosecution. In addition, if the offense is committed by an employee of this state, the person will be dismissed from office or discharged from employment upon conviction."

MCL 205.27(4) states:

A person who is not in violation pursuant to subsection (2), but who knowingly violates any other provision of this act, or of any statute administered under this act, is guilty of a misdemeanor, punishable by a fine of not more than $1,000.00, or imprisonment for not more than 1 year, or both.

Information received by Treasury from the U.S. Internal Revenue Service, pursuant to section 6103(d) of the Internal Revenue Code or any other federal agency will not be subject to the exchange.

Ill. Procedure for Security Contractor will safeguard any tax return information obtained under the Contract as follows:

A. Access to the tax returns and tax return information will be allowed only to those authorized employees and officials of Contractor who need the information to perform their official duties in connection with the uses of the information authorized in this Contract.

B. Any records created from tax returns and tax return information will be stored in an area that is physically safe from access by unauthorized persons during duty hours and locked in a secure area during non-duty hours, or when not in use.

C. Any records matched and any records created by the match will be processed under the immediate supervision and control of authorized personnel in a manner in which will protect the confidentiality of the records, and in such a way that unauthorized persons cannot retrieve any such records by means of a computer, remote terminal or other means.

D. All personnel who will have access to the tax returns and tax return information and to any records created by the tax return information will be advised annually of the confidential nature of the information, the safeguards required to protect the information and the civil and

t

I

criminal sanctions for noncompliance contained in MCL 205.28 (2) and MCL 205.27(4) and will sign confidentiality certifications.

E. All confidential information, electronic and paper, will be secured from unauthorized access and with access limited to designated personnel only. State tax return information will not be commingled with other information. All Michigan tax returns and return information will be marked as follows: CONFIDENTIAL - DO NOT DISCLOSE -MICHIGAN TREASURY TAX RETURN INFORMATION

F. Treasury, Office of Privacy and Security or Contract Compliance Inspector may make onsite inspections or make other provisions to ensure that adequate safeguards are being maintained by the Contractor.

G. The Treasury Office of Privacy and Security may monitor compliance of systems security requirements during the lifetime of the Contract or any extension.

H. Contractor will also adopt policies and procedures to ensure that information contained in their respective records and obtained from Treasury and taxpayers will be used solely as stipulated in the Contract.

IV. Computer System Security of Tax Data The identification of confidential tax records and defining security controls are intended to protect Treasury tax return information from unlawful disclosure, modification, destruction of information and unauthorized secondary uses.

Computer system security and physical security of tax data stored and processed by Contractor must be in compliance with the following security guidelines and standards established by Treasury. These guidelines apply to any computer system developed by Contractor, either through its own systems staff, or through a contractor, subcontractor or vendor):

A. Controlled Access Protection All computer systems processing, storing and transmitting Michigan tax information must have computer access protection controls These security standards are delineated in the National Institute of Standards and Technology (NIST) Special Publications number 800-53 "Recommended Security Controls for the Federal Information Systems" at http://csrc.nist.gov/publications/PubsSPs.htrnl. To meet these standards, the operating security features of the system must have the following minimum requirements: a security policy, accountability, assurance, and documentation.

1) Security Policy - A security policy is a written document describing the system in terms of categories of data processed, users allowed access and access rules between the users and the data. Additionally, it describes procedures to prevent unauthorized access by clearing all protected information on objects before they are allocated or reallocated out of or into the system. Further protection must be provided where the computer system contains information for more than one program/project, office, or Agency and that personnel do not have authorization to see all information on the system.

2) Accountability - Computer systems processing Michigan tax information must he secured from unauthorized access. All security features must be available (audit trails,

I I

identification and authentication) and activated to prevent unauthorized users from indiscriminately accessing Michigan tax information. Everyone who accesses computer systems containing Michigan tax information is accountable. Access controls must be maintained to ensure that unauthorized access does not go undetected. Computer programmers and contractors who have a need to access databases, and are authorized under the law, must be held accountable for the work performed on the system. The use of passwords and access control measures must be in place to identify who accessed protected information and limit that access to persons with a need to know.

a) On-line Access -Users will be limited to any Treasury on-line functions, by limiting access through functional processing controls and organization restrictions.

Any employee granted access privileges through the Contractor's Security Administrator will be approved for access and viewing rights to Treasury on-line systems by the Depat1ment of Treasury, Office of Privacy and Security.

b) Operating Features of System Security Contractor must meet the following levels of protection with respect to tax return information. Individual user accountability must be ensured through user identification number and password.

i. Access rights to confidential tax information must be secured through appropriate levels of authorization.

ii. An audit trail must be maintained of accesses made to confidential information.

iii. All confidential and protected information must be cleared from a system before it is used for other purposes not related to the enforcement, collection or exchange of data not covered by this section or by an addendum to this Contract.

iv. Hard copies made of confidential tax return information must be labeled as confidential information.

v. Confidential Treasury tax information will be blocked or coded as confidential on system.

vi. Any computer system in which Michigan tax return information resides must systematically notify all users upon log-in of the following disclosure penalties for improperly accessing or making an authorized disclosure of Michigan tax return information:

NOTICE TO EMPLOYEES AND AUTHORIZED REPRESENTATIVES

This system contains Michigan Department of Treasury tax return information. DO NOT DISCLOSE OR DISCUSS MICIDGAN RELATED TAX RETURN INFORMATION with unauthorized individuals. The Revenue Act at MCL 205.28(l)(f) prohibits such disclosure.

MICIDGAN PENALTIES A person making a willful unauthorized disclosure or inspection (browsing) of tax return information may be charged with the following Michigan penalties:

• Criminal penalties up to $5,000 and/or imprisonment for 5 years, plus costs and dismissal from employment if it is found that a current or f01mer employee or authorized representative has made an unauthorized disclosure of a tax return or tax return information or divulged audit selection or processing parameters, [MCL 205,28(2)]

• A misdemeanor, punishable by a fine of not more than $1,000.00, or imprisonment for not more than 1 year, or both if the person is not in violation pursuant to MCL 205.27(2), but who knowingly violates any other provision of this act, or of any statute administered under this act.

This statement is subject to modification, A confidentiality statement, subject to modification, will be sent as needed by the Security Administrator to all employees, contractors, and legal representatives of Contractor,

3) Assurance - Contractor must ensure that all access controls and other security features are implemented and are working when installed on their computer system. Significant enhancements or other changes to a security system must follow the process of review, independent testing, and installation assurance. The security system must be tested at least annually to assure it is functioning correctly. All anomalies must be corrected immediately,

a) The Contractor must initiate corrective action for all non-confonnities as soon as detected and immediately advise the Contract Compliance Inspector. Notice of the corrective action must be provided to the Contract Compliance Inspector. All nonconformities must be reported to the Contract Compliance Inspector with the following:

a. Duration of non-confo1mity/interruption b. Reason for non-conformity/interruption c. Resolution.

b) All non-conformities to the specifications/tasks of the Contract must be corrected within four (4) hours, The State recognizes there will be instances when adherence to this time frame will not be possible. However, the State will only tolerate this on an exception basis. To request an exception to this time frame, the Contractor must submit a detailed project plan to address the non-conformity within four (4) hours to the Contract Compliance Inspector for approval.

4) Docnmentation - Design and test documentation must be readily available to the state. The developer or manufacturer should initially explain the security mechanisms, how they are implemented and their adequacy (limitations). This information should be passed on to the security officer or supervisor. Test documentation should describe how

I

and what mechanisms were tested and the results. If recognized organizations/tests/standards are used, then a document to that effect will suffice. For example, a system that has been tested and certified as meeting certain criteria may have a document stating this fact, without detailed tests/results of information. Contractor, however, must ensure the documentation covers the exact system and that it includes the specific computer system used by Contractor.

Additionally, documentation must include a security administrator's guide. The security administrator's guide is addressed to the System's Administrator and Security Officer and will describe the protection mechanisms provided by the security system, guidelines on their use and how they interact. This document will present cautions about security functions and describe privileges that should be controlled when running a secure system. The document will be secured and locked at all times with access rights only by the Systems Administrator and Security Officer.

Note: When a security system is designed or purchased for a specific computer or computer system, the security mechanisms must be reviewed by the State to ensure that needed security parameters are met. An independent test should be implemented on the specific computer or computer system to ensure that the security system meets the security parameters within this contract and developed with the computer system. The test may be arranged by the developer but must' be done by an independent organization. Contractor must assign responsible individuals (Security Officers) with knowledge of information technology and applications to overse.e the testing process. These individuals must be familiar with technical controls used to protect the system from unauthorized entry.

Finally, contingency and backup plans must be in place to ensure protection of Michigan tax information.

V, Electronic Transmission of Michigan Tax Information The two acceptable methods of transmitting Michigan tax information over telecommunications devices are encryption and using guided media. Encryption involves altering data objects in a way that the objects become unreadable until deciphered with the appropriate software at the intended destination. Guided media involves transmission of data over twisted pair cable, coaxial cable or end to end fiber optics which are typically used in secure computer networks like ilie state's Local Area Network (LAN), telephone systems, and television distribution.

Cryptography standards have been adopted by the IRS and can be used to provide guidance for encryption, message authentication codes or digital signatures and digital signatures with or without an associated cet1ification infrastructure. For further information, see IRS Publication 1075 at the IRS web site.

Unencrypted cable circuits of fiber optics are an acceptable alternative for transmitting Michigan tax information. Adequate measures must be taken to ensure that circuits are maintained on cable and not converted to unencrypted radio or microwave transmission. Additional precautions should be taken to protect the cable, i.e., burying the cable underground or in walls or floors and providing access controls to cable vaults, rooms and switching centers.

A. Remote Access Accessing databases containing Michigan tax information from a remote location - that is, a location not directly connected to the Local Area Network (LAN) will require adequate safeguards to prevent unauthorized entry.

For remote access, the contractor is required to use an identification security card that requires both PIN and card in possession. The State identified and approved methods for remote vendor access are as follows:

• SecurelD through VPN - State provided SecurelD taken and VPN software in order to access State of Michigan resources. Appropriate Acceptable Use policies and signoffs are required

• Follow-the Sun SecurelD - Vendor is provided with VPN software and a SOM technical resource coordinates with the DTMB Client Service Center to provide secure ID code access to specific State of Michigan resources. Appropriate Acceptable Use Policies and signoffs are required.

B. Portable Computer Devices Any entrusted confidential information collected or accessed during this Contract must be encrypted when stored on all storage devices and media. This includes, but not limited to, disk drives for servers and workstations, and portable memory media (PD As, RAM drives, memory sticks, etc.).

VJ. Record Keeping Requiremeuts for Information Received Each Contractor, requesting and receiving information will keep an accurate accounting of the information received. The audit trail will be required which will include the following information: a. Taxpayer's name b. Identification number c. Information requested d. Purpose of disclosure request e. Date information received f. Name of Division and employee making request g. Name of other employees who may have had access h. Date destroyed i. Method of destruction

The Contractor will adopt and implement formal procedures to:

• Ensure proper handling of tax returns and tax return information;

• Secure and safeguard information from unauthorized use; and

• Ensure appropriate destruction of information and materials retrieved from Treasury.

;-

I

A. Electronic Media Contractor will keep an inventory of magnetic and electronic media received under the Contract.

Contractor must ensure that the removal of tapes and disks and paper documents containing Michigan tax return information from any storage area is properly recorded on charge-out records. Contractor is accountable for missing tapes, disks, and paper documents.

B. Recordkeeping Reqnirements of Disclosure Made to State Auditors When disclosures are made by Contractor to State Auditors, these requirements pertain only in instances where the Auditor General's staff extracts Michigan tax returns or tax information for further review and inclusion in their work papers. Contractor must identify the hard copies of tax records or if the tax information is provided by magnetic tape format or through other electronic means, the identification will contain the approximate number of taxpayer's records, the date of inspection, the best possible description of the records and the name of the Auditor(s) making the inspection.

The Disclosure Officer must be notified, in writing, of any audits done by auditors, internal or otherwise, of Contractor that would involve review of Treasury processing parameters.

VII. Contract Services To the extent the Contractor employs an independent agency, consultant, or agent to process confidential information which includes Michigan tax return information; the Contractor will notify the Treasury Disclosure Officer before the execution of any such agreement. Each agreement will include in the agreement the following recommended safeguard provisions:

A. The identification of confidential tax records and defining security controls are intended to protect Treasury tax return information from unlawful disclosure, modification, destruction of information and unauthorized secondary uses.

B. Definition of Treasury Tax Return Information as defined in Revenue Administrative Bulletin (RAB) 1989-39:

Taxpayer's identity, address, the source or amount of his/her income, payments, receipts, deductions, exemptions, credits, assets, liabilities, net worth, tax liability, tax withheld, deficiencies, over assessments, or tax payments whether the taxpayer's return was, is being or will be examined or subject to their investigation or processing, or any other data, received by, recorded by, prepared by, furnished to or collected by the agency with respect to a return or with respect to the determination of the existence, or liability ( or the amount thereof) of any person under the tax laws administered by the Department, or related statutes of the state for any tax, penalty, interest, fine, forfeiture, or other imposition or offense. The term "tax return information" also includes any and all account numbers assigned for identification purposes.

C. An acknowledgment that a taxpayer has filed a return is known as a "fact of filing" and may not be disclosed. All tax return data made available in any format will be used only for the purpose of carrying out the provisions of the Contract between Contractor and the sub-

contractor. Information contained in such material will be treated as confidential and will not be divulged or made known in any manner to any person except as may be necessary in the performance of the Contract between Contractor and the subcontractor. In addition, all related output will be given the same level of protection as required for the source material.

D. The subcontractor will certify that the data processed during the perfo1mance of the Contract between Contractor and the subcontractor will be completely purged from all data storage components of the subcontractm's computer facility, and no output will be retained by the subcontractor at the time the work is completed.

E. Destruction of tax data, including any spoilage or any inte1mediate hard copy printout which may result during the processing of Michigan tax return information, will be documented with a statement containing the date of destruction, description of material destroyed, and the method used. Destruction parameters must meet the standards of Section IX, Disposal of Tax Information, of this agreement.

F. Computer system security and physical security of tax data stored and processed by the subcontractor must be in compliance with security guidelines and standards established by this contract. See section VI (Record Keeping Requirements for Information Received in Paper Format) for more details.

G. The Contractor will be responsible for maintaining a list of employees authorized to access Michigan tax return information and will provide a copy of such list to Treasury.

H. No work involving info1mation furnished under the contract will be subcontracted without the specific approval of Treasury. Contractor and approved subcontractors handling Michigan tax return information will be required to sign the Vendor, Contractor or Subcontractor Confidentiality Agreement provided by Treasury, (Form 3337, see Attachment A). The original agreements will be returned to the Disclosure Officer for the Department of Treasury and a copy sent to the Contract Compliance Inspector.

VIII. Transport of Tax Information In the event, it is necessary to transport confidential tax return information the Contractor is responsible for holding the carrier responsible for safeguarding the records. The Contractor must obtain a signed Vendor, Contractor or Subcontractor Confidentiality Agreement (Form 3337, see Attachment A) for each carrier employee who has access to Michigan tax return information. The original agreements will be returned to the Depatiment of Treasury, Disclosure Officer and a copy sent to the Contract Compliance Inspector.

If it is necessary to transfer records and responsibility for transport to a third carrier due to a mishap during transpottation, the Contractor is responsible for ensuring safeguard standards remain enforce. This type of incident will be documented in accordance with the incident reporting guidelines in procedure PT-03253, "Incident Repotiing and Handling".

Any such incidents must be repotted to the Contract Administrator immediately.

I ,.

IX. Disposal of Tax Information Materials fumished to Contractor, such as tax returns, remittance vouchers, W-2 reports, correspondence, computer printouts, carbon paper, notes, memorandums and work papers will be destroyed by burning, mulching, pulverizing or shredding. If shredded, destroy paper using cross cut shredders which produce patticles that are 1 mm x 5mm (0.04in x 0.2 in.) in size (or smaller).

Data tracks should be overwritten or reformatted a minimum of three times or running a magnetic strip over entire area of disk at least three (3) times to remove or destroy data on the disk media-Electronic data residing on any computer systems must be purged based on Treasury's retention schedule.

Contractor and its subcontractor(s) will retain all confidential tax infonnation received by Treasury only for the period of time required for any processing relating to the official duties and then will destroy the records. Any confidential tax information that must be kept to meet evidentiary requirements must be kept in a secured, locked area and properly labeled as confidential retum infonnation. See Procedure for Security (Section III of this agreement) for more details.

X. Security Responsibility Contractor will designate a security person who will ensure that each individual having access to confidential tax infonnation or to any system which processes Michigan tax return information is appropriately screened, trained and executes a Vendor, Contractor or Subcontractor Confidentiality Agreement (Fann 3337, see Attachment A) before gaining access or transaction rights to any process and computer system containing Treasury tax return infonnation.

Each Contractor or their subcontractor(s) employees' access and transaction rights will be reviewed periodically to ensure that there is a need to know Treasury tax return infonnation displayed in any media.

Michigan tax return information will be made available only to individuals authorized by the Contract. Contractor will maintain a list of persons authorized to request and receive information and will update the list as necessary. A copy of the list must be furnished to the Michigan Department of Treasury Disclosure Officer and Contract Compliance Inspector.

XI. Security Breach Notification The Contractor is required to report to Treasury, on Form 4000, Incident Reporting (Attachment B) any use or disclosure of confidential information, whether suspected or actual, immediately after becoming aware of the misuse or disclosure. The Contractor may substitute its internal fonn for Fann 4000 if all pertinent infonnation is included.

The Contractor agrees to immediately contain the breach if it is determined ongoing.

Treasury has the right to tenninate the Contract when a breach has occurred, and the Contractor cannot demonstrate proper safeguards were in place to avert a breach. Treasury must approve Contractor's resolution to the breach.

I I

XIII, Certification of Compliance The Contractor will fully protect State Tax fuformation (STI) entrusted to them. Each Contractor or subcontractor who will have access to STI must read and sign a confidentiality agreement. This contract requires that all information obtained from the Michigan Department of Treasury under the Revenue Act, PA 122 of 1941, MCL 205.28 (l)(f) be kept confidential. In the event of a security breach involving STI in the possession of the Contractor, the Contractor agrees to provide full cooperation to conduct a thorough security review. The review will validate compliancy with the Contract, and state laws and regulations.

If, as a 1·esult of the Contractor's failure to perform as agreed, the State is challenged by a govemmental authority or third party as to its conformity to or compliance with State, Federal and local statutes, regulations, ordinances or instructions; the Contractor will be liable for the cost associated with loss of conformity or compliance.

The Contractor understands the cost reflects violation fines identified by the Michigan Social Security Number Privacy Act, 454 of2004 and the Michigan Identity Theft Protection Act, Act 452 of2004 as amended.

XI. Effective Date These Safeguard requirements will be reviewed whenever the Contract modifications include specifications or processes that affect tax data.

l

Miehtgo.11 Departm11nt~fT1easury 3337 (Rev, 10-18)

Attachment A

Vendor, Contractor or Subcontractor Confidentiality Agreement Th.e ,Revenue Act, Publjc Act 122 of 1941, M91... 205.28(1){1), the Cily ln~om~ lax Act, Public Act 204 or 1964, MCI.. '141.674{1.), and lnler~~I ~ev~nue Code (IR.Cl.61Q~(P), make•all lnformatjol'i f!c"q9lred 111 ~dmln!;;~(!rjng Iaxi:is i::onficten.Ual. The Acts. and IR_C h_ofd. .a v:eod.bl'., cOOJractor or s.v_~c,;mµ'aqt_or an~ ;their employee$ wtio s'elt a· Producl or pravlde ij service l<l the Mlch[g6n Department of treas·urY, br'. who ac~esa treasury data·,· tq "l_he _sltfot coofidantlality provlslOfls of the Ads and IRC. ,coond~nllal tax 1nr91mat1on includes, b1,1t ls not llmiles;f to,.lnfonne.11® obtalne.t:f In _coon!3:ctton with lhE! admln!slrijll_or) of a _tax or lnformatlorr .« l?arameters that V<OOlcl_ enable a person to ascertaln"l.he; audit selection « processing criteria of'lhe Michigan Department of Treasury for a tax admlnlstered by lhe department. ·

INsiRUCTJONS. Read this enllre rorm before yo1,.1 slQn II. Uyou do-not.complete lhis.agreement,·you will be denied access to Michlgan._Department.of Tr"asury and federal fox Information, Afteryou and your witness sign and dale thls form, keep a c:Opy-for your records. send the orfglnal to·the address listed below Company Name and Addro:s:.: (Street or RR#, City, State, ZIP Code) last Name Fir~Name

Driver License N1.1mb1111Passport_ Number T..ilephone Number

!ahde orM!chlgan 0111p1utm1mt IQM~lon Subi;onttactor Nwna lf 1',oducVServi~ f.urnl,;h111d to Contractor

Desc1lb8 hare ar 1n·a. s-aparatG-atta,;hment lhe pro duet or s,uvtea being pro'Jlded to tho stale of Michigan Agenc.y (Required}.

ConflcJen.llaJUy Pro\1ls"lons. It fs 1_11091!,l ,ta reVf!,al or browse, ex.capt as authorized; ~ An tax return lnf«malloo obtained In connecllon with the adminislrallon of a. lax. This lnc!1,.1des·informatfon ·from a lax return or audit and any

infom'lallon·a.bout 1he se!ecllon or a return for audit, assessment or ,::olleritlon, or parameters or tolerances for processing returns.

'° AJI Michigan Department of Treasury or federal tax rt:lums or lex return Information made avallable, inc!Udlng ·1nformalion marked "Official Ust> Ot,\y'', Tax returils·or tax-return lnformallon shall nofbe d!vulged or made known In any manner to a:ny persoo except as may be needed to perform officlal ·duties. Access to Trea:sury or federal tax'lnformallon, In paper or eleclronlc form, Is ·allowed on a h8ed.to-know basis only. Before you disclose teJurns Qr ret!,Jm lnfol'matlon to o_\her· employees tn YoUr orgil.htzaUon, th~Y must pe authorlzet1·by Mlc.h!Qan:oepartment of Trea$ury t~ recelv~ the lnfoon_aUoh to pi,rf9flll lhe!r l?fficlal dulles.

• Cohfldet.lllal !hf¢f"mallon Shall Mt be (:lfsclosed by a c;tepartment _employee to coo~rm ·rnfQl"mau~ made pub Ile l?Y a.n61hel' parly or source Which ls ·part of ahy publlc .. recqrd, 1999 AC., R 2005.1004(.1).

Vlolalln~ confidentiality la'o'VS Is a felony, wlih penalties as descrlbai:1;

Michigan Penaltl"es MCL 205.28(1Hf) pro\'ldes ihat you may not willfully· dlsclose or bro.wsa any MlchJgan fax rot urn or Information contained Tn a rat um. Brows!~g Is defined as examining a return or return· Jnrormalloo acquired wlthoot authOi'IZaUon and.without a need to know the lnformallon to perform official duUes. Violators are· gullty of a 1elony and subJecl to flnes:of $5,000 or Imprisonment for five years, ol' both. Stale employees wm be discharged from slate Sej'ylce upon convlc~lbo. Any person who viol ales.any other proviston ofthe Revenue Act, MCL 205,1, et seq., 6t any statute administered under'lhe Revenue Act._ w!II be gulltY. Of a m)sdemeanor '!,nd flf1&d $1,000·or lmpr)$1:inm'!Jnl for one.year, or polh, MCI. 205,.27_(4),

City Penalties MCL 141,'5"/ 4_(2) provides that any person "dl\llJlglng coofldefltlal Clly T-ax lrifotmatlOO Is guilty of a tnlsdemea.n·or end subject to a floe not exceedfn~ $500 or Imprisonment for a period not i;ix_cee!f!ng SO days, or bolh 1 for ea.ch offense,

Federal Penalties ffYO!J w\llfu.l!y d!sclose federa.l !a~ r~twns et h1X rel um infonnalloil toa l!l!~dparty, you are guilty Ofa f1;1loriy with a flni;, o.f $S,OOO Or lr:nprlson1TJehl for five ye_ai-.s, •(ir f:?Oth, plus PrQ~.Oc~tlori coSts'a,,:;cO"r~irig lo.the lntem!}1 ~e_veriue Cod~ (IR~) §721.3, ;26 use 7213.

In add_ltlon, ·fn?Pl:1:Cling, brQwSlng or·looking,at a fyl\'.)eral la~: r~tom or tax re~um inf«m~t!on withOtlt_ tlulhorizati9~ ii:• a· felony_ Violation of !RC _§7';?1_3A sub!ecllnQ lhe vlOlator toe $1,000 fine or lmprlsonm,,mt for one y.ear, or~oth, plus prosecutlon.costs. Taxpayers affected·byvtalatl6ns.c,r §7213Amust be nOtified by the Qov~mrr\~ilt ~nd ·may brirm a ci\1111;\ctlon _against lh'e federal g·overrirrient _8nd lhe viOJatO!' wlthlri two Year·s Qr.the vtd0.tlon. Civil damages ~re the gre:ater-of $1,000 Qr ai;:tuaf damages inourrj:,d jJy t_he taxpayer, plus the cQSll:> associated with bringing lhe action, 26 U{:JC 7431.

!=allur~ to corriPIY with this cooMentliillty aQreemerit 011.wJeopardlze your employer's cllfltract-wllh the Ml~hlga"n Department of Treasury.

ay.!tlgning-this Agreement, 1 certify ihat I have read the above corifidentlallty provisions and understand lhitt fa11ure lo comply Is a 1elony.

Pr_!nt namu of umpfoyae signing this, agre.ontanl

Print '!f'-Atness:N11r-ie (Roqulrad)

S~brnit"yoµr form to·tt,e following address:

Office of Privacy an~ Security/ l;)lsclo=:;ure Unit MIC~lQan Depa.rt~ht ofTreasuty 43(1 W. Alle-ga.n street · LanSing_, M[ 48922

Slgnalure of person nanted above

Signature ofWllne~ (R!)qllir~d)

~Question~, conta.ct the Office of Privacy .and_Se.curity by telepho_ne. 517--836-4239;_ fax1 511..S36-5340; qr email: lreas_Pfsclosure@,mlchlgan.g_ov

Dalofsl.gned

Dal<1 s!gied.

M!~hlg11l'1 Oep~ent ofTreA$\lfY 4000(R11v.os;1-11

Incident Report

Attachment B

INSTRUOilONS: Complete F'ar:ts 1 and 2 ahd immedlate!y .submit Initial Report to Jhe· Offl~ of Priv.acy 8.nd Security. After Incident resolution, su\)mlt Flnal Report {Parts 1, 2 and 3) to the Office or Privacy anq: Securlty. Refer to Prpcedure PT*03253, Incident Reporting and Handlin$,

Full Nome {~11.1;~ Flrf;t, M!ddl11 lnltia!) r OMsloo/OffJee

Fax Numbar I E-MallAddren

Full Name {La.st, Fir!il, Middle lrillhtl) I Oiv~Ol'l/Ol!foe

Telephone Wumber Fax N~mher I E-M;iilAddress

.·.· z'; liVhose lnformallonwns Involved In !lie !ncldeht?

D ll'8\l$UiY D Federal Tax lnfomia!(O(l

Incident Category (selecl a!I thal apply)

0 Other stat~Agency, sped_ty

D Passwords Shared/Slolen

D Misrouted Communfol!lUons

0 Unauthorized A1:~sS

0 FrnudultinlAcllons

D Losl/Stolen Information/Data

D l(?!;ll/Solen Cash/Chet;ks

0 lilaj')proprlate Bufldlflg Ac1=ess

ln1;ident Meci.s D Financial !nformalioo/Resourcl'ls

D Confldennal/senslllve-lnforrnallon

lno.idunl Laca,llon

Datu ortnitlal R11port

0 Compul1;1r \liJlJS/Spam

D Data Destructloo/Delelloo

D Bac~ups.Mlsslrig or-stolen

D Hacking ofNetworl<s/$yslems

0 lmprOf?erly Secured Sys#leb

O-Clrcu_mvenl!on of security Proto1i~s

□ O Personal lnformalloo

(SSN, 0riv:8r lic~se No.:Flnancia! informali_on~ D Human ResOOrces (threat) I 1lina Incident Qcc:um1d

D Paper Archives Compromised

0 Safe/lo,;:l(box/other Compromise

0 0elh,:e·ry of i:;lcx;:timer:its Lost

0 ·inappropriate Destruci;!on Paper

D ·1napproprlata Destruction Media

D Losl/SlolE;ln Equipment

□ □ Unaulholized/Unl~wful Ar:tivtty

0 Other

] liino lncid•rnt Ol~cmin!ld

D0ecs lhls Involve personal ltiJom,allon {fir.St and last name along wllh a SSN, drt'ler ilcense number, or credlVdebit card a·ccount number)?

Oves 0No

.<1000, P~II~ 2·

Full Nam♦ {LIU~ First, Middle lni~alJ

NotiflcoUco Issued to affect'Jd lndMd11a~? How many notificstioM W'Jro sen!?

Ovos 0No Blee.ch NotifloaUon Melhod?

.0 E-mail D Telephone O US Mall ow,.

_Incident Cos.I 0 Check lflnc!d~nl .cools 11re.h~ss lhao-5250, lf$250 Of more, C«n?fe\e U\e dolailed suromnry of c,:,sb l;)el0\1-/. - = Trna,;uiy$, _________________ _ PO!ilngeS, _________________ _

OTMB-OE;~$, ______________ _ Credi! M901l0f!ng $er,1ce $, ___________ _

DTMB--Trelisi./ry Agency Services$, _________ _ _____ $ _______ _

T11ta(Cost of Incident$

MlonTak<in

i

ST ATE OF MICHIGAN CENTRAL PROCUREMENT SERVICES


Change Notice Number 11 to

Contract Number 071 B2200168

William Pemble

3000 Town Center, Suite 2400 517-636-4741

► Kathleen Cawley

859-248-1187

[email protected]

[email protected]

Mike Breen

(517) 249-0428

[email protected]

DTMB

DTMB

Effective with mutal signature the attached documentation is executed. All other terms and conditions remain the. Same

-----•---·

Contr~et .Change ,A-,v, "1£1.'1()d 1,lpan In W 19 .J?,lJYp}lllM P1'<lq,1• ~ t!1:d,qQ,1?:Uif~9~~l''JJj)e.0; lflllVUlca l1O

1'}rthtife~•ti,J:'SOW 63 I:dynti> FQS)'S11i1po1·t (Oi•Dffllg ($~o. gtl11.(i<,1'•pq1 tnoi,t!>l!!I\'l.l B.Q'vj ~71)1):;r~\!dO_o'*.:s}'~ }l-Wr,1 r::l~.\l~O'tt ($ll~

140.0 .P9t,1101\\h) Wl11 ~t\;~OJl:folldtt\l:i& W.to-{IUil ho 1101ialdo(I)(\ lJQlb $'t\'tY!i;i3 (in<\ wlltc.on.tju1,1a \O Qr,

·tnv¢luo6 u1tdc1' tlie:1JMo aotvtcM)10.11J.Jlil t,)~c. (llJg ol \'\l51C()~~mot'(o_t1th .

•\f\f(l!,ltf IO and App,·t)V0<;l 1l:Yl·

''

A\Wtll\ltll'•I MIUl\ll\\)l!?, 1,1, •to, ·

I l . I l l I l l

I I I .

I I I i

~

I I l ! I I

!

~T(j\Jil~ > HJ;{?, ffl O VJ m(Q) Michigan Enterprise Call Center (MiECC) accenture

Statement of Work Authorization SOW _063 County FOC Support for DHHS Cloud IVR

Statement of Work (SOW) Number: SOW _63 County FOC fVR Support

ProjectTiUe: County FOC IVR Support


SOW Summary Description: Michig11n Enterprise Contact Center Support for the FOCJVRl

Estimate Submitted By: Ryan Sadler

Date Submitted; August 17, 2017

Requesting Deparbnent/ Agency Department or Health and Human Services (DHHS} -Office of ChUd Support

Approval Due Date:


Background Over the years, DTMB hes established a shared IT support service center, known as Michigan Enterprise Contact Center (MiECC), to provide centralized support to the State of Michigan (SOM) contact centers across multiple agencies. The purpose of the Contract is for Vendor to provide shared IT services to maintain and enhance MiECC contact centers.

Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW include the following: 1. The County Friend Of the Court {FOC) IVR is a single number to provide critical

communication system for the DHHS Office of Child Support (OCS) customers to contact their respective county for customer case specific information, county information and county call routing. DHHS OCS would like Accenture to provide maintenance and operations support services through the Michigan Enterprise Contact Center for the eighty-three county DHHS - OCS FOC IVR phone system.

Pagel

D'lrft~R accenture ffl:;f,f 8 tf/ UmdV Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

SOW 063 County FOC Support for DHHS Cloud IVR

Scope ofWork Accenture will provide support for the following areas: a. Provide Level Two technical support. b. Perform customer requested changes. c. Technical liaison to the State's FOC IVR and hosting center. d. Day to day application support of the IVR using the FOC IVR vendor

management tools. e. Provide caII message modification for English and Spanish. Provide change

management for the caJler prompts and messages. f. Provide support for system changes such as messages, text to speech and

routing instructions. g. Overall management of the software FOC IVR vendor, Century Link. h. Provide support escalation to CenturyLink. i. Provide DHHS with Technical Assessment Group (TAG) representation for the

FOC IVR system. j. Provide support according to Attachment 1: Service Level Agreement and

Return to Service Goal of Contract No. 071B2200168 •

Acceptance Criteria Each System Engineering Methodology (SEM) phase shall have an acceptance form that documents phase deliverable completion, open issues, and implementation considerations. Vendor, DTMB and Agency SOW authorized approvers sba11 review and sign acceptance according to Acceptance terms identified in Section 2.250 of Contract

Specific Department Standards Accenture wi11 comply with DTMB Development Standards when performing this work.

Location of Where the Work is to be Performed Services provided under this SOW shall be performed in Lansing, Michigan.

Expected Contractor Work Hours and Conditions Services provided under this SOW shaU be performed Monday through Friday between the hours of 8:oo AM and 5:00 PM.

Page2

mrn~~ accenture ffi;Gi aw u~ Michigan Enterprise Call Center {MiECC) Statement of Work Authorization



Work Description The MiECC Accenture Team will provide the services described in this section below.

Impacts of Not Making Requested Changes The FOC IVR system performance, usability and availability would be negativity impacted, lower customer service and response time for DHHS OCS customers.

Project Requirement The State's Remedy ticket system will be used to initiate and manage break/fix and maintenance requests. Remedy tickets may be created by business users or the contractor and will identify the problem to be fixed.

Figure 1. Friend of the Court IVR Problem Management Process Flow

Friend ot Ill• Court IVR Problem Mlnagtm1nl Prvc:111s ---,---------------------------1 11 •, ,.._*'"•""

l- J ••• !::::._ =::s:=1---.r ~~ ::::'=."',. !!I -- ~ ..... ~~ ~~

~tllty

I 1----------------.... poN,111..,.,.

___ 1 __ ------------------------1 l I i

I I :o~ .... 1----+<

I ... I UM•,,U -----T-------- ---- -------------1 I

j : I

, ............ -.. a:~•~aa.,,...-, ·--·'-""--~.a., .. ·................ ·-·•-"'"? .... .. ,_ -___ J. _______ _ ------------------

waa·-·----....... ucaa,.,..._ ~UOUlliQII•

Page3

~(Nllln accenture ~~y D VJ fflfill) Michigan Enterprise Call Center (MiECC) Statement of Work Authorization


Deliverables 1. Voice Watch (per Agency)-Annual call Transaction Monitoring Service: Dials a specified number every 1S minutes and walks thru a single call transaction flow (up to 8 steps}. Voice Watch responds to prompts with touch-tone and/or spoken Input. Voice Watch verifies static and dynamic prompts, recognition rates, and responses times.

Responsibilities and Assun1ptions Vendor, State, and Agency staff responsibilities for work under this SOW are depicted in the table below.

rtcspo nsibiliti es R.csnanalblllt,.• A=t:ntura A11.cnt"Y DTMB

Completion or A;cncy Semce Request Scdlon arsow v ,/

Complc:Uon arPropasul Rcspa115e Secllan al SOW ,J

Slr!n Stalement or Wark ,/ v ..; Issue Pu1d111sc Order .., ,J Agn:c Upon Projetl Resoun:a and Schedule ,/ ,/ ,/

Complc1e Dellvcmblcs as Ddinm In sow ,/

P11rtldpalo In DollYCnlblo Review u Deflnei! In SOW ,J "' Document PhllSC Review Accepl11nce in Acccnlllnce "' Review Ph~ And Over.ill Project Aa:entnnce Documents and Si~n ,/ ,/ v Prvvfde Am:ss lo R.csou~ (c.i;.. Ousblcss Expcr\s, Systems, Softwu~

"' "' and H1rdwun:) Required lo Pcrfonn Scrvii=

Assumptions

1. This Statement of Work SOW _063 County FOC IVR Support ("SOW') incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and Support- DTMB/(Stete, Treasury, Civil Service) (the "Contract") between Accenture LLP (''Vendor") and the State of Michigan Department of Management and Budget Acquisition Services (the "State") effective May 1, 2012.


3. Actual services will commence upon execution of this SOW by parties, State purchase order issuance, and confinned final project with agency, DTMB, and Accenture.

4. Additional hours required to complete the work described in this SOW shall be negotiated as amendment to SOW.

Page4 -

~Jfli\'!R accenture (ll;li:f O VJ Wl!='J Michigan Enterprise call Center (MiECC) Statement of Work Authorization

SOW 063 County FOC Support for DHHS Cloud 1VR

5. The State of Michigan is responsible for the support contract with the FOC IVR vendor.

6. Level 1 and 3 support is out of scope. 7. Agencies must pay for network toll charges if a toll-free phone number is not

provided. 8. Voice Watch subscription for FOC IVR is invoiced separately under SOW-60. 9. In scope for Voice Watch monitoring services under this SOW consist of the following

phone numbers:

Project Contacts The Vendor main contacts for this SOW include the f o11owing individunls:

Email TeamMember Role Contact Information Ran Sadler Kristine Hand

Project Control and Reports Accenture will submit a monthly hours report to the DTMB Project Manager throughout the life of this project as part of the fixed price billing invoice.

Payment Schedule Payment for the MiECC-Accenture Base team will be on fixed fee basis, Vendor will invoice the State monthly in the amount of $20,562.50.

Total Combined

Resource Rola Costs

MiECC-Accenture Base Team FOCIVR $246,750/yr (Fixed October 1, 2017 - September Support Price)/$20,562.50 per month. 20. 2018

Travel and E:-r..1)enscs Costs presented in this SOW are inclusive and contain no estimates for travel and expenses.

Pages

September 20, 2017

arr~B Michigan Enterprise Call Center (MiECC) accenfure Statement of Work Authorization


Agreed to and Approved By:

r Wirtfm

Pratin Trivedi

1ina Mitchell

.. nEA : Office of Child Support, Director of lnformntion Technology and Pa ent O erutions Department of Technology, Management, and Budget Project Manager ______ .......;.;= = ;__-- =------~--

Bill Pemble

Kathleen Cawley

DTMBMJECC Director

Accenture Managing Director

Page6

kristine.handy

Stamp

DT111111nD . accenture YI 11 Michigan Enterprise Call Center (MtECC)

Contents

Statement of Work Authorization SOW-067OCS GENESYS EWM SUPP0RTV2

Background .................................................................................................................................. ............... 2

Project Objective/Expected Benefits ....................................................................................................... 2

Scope of Work ...................................................................... .................................................................... ... 2

Acceptance Criteria ................................................................................................................................. ... 3

Specific Department Standards .............................................................. ............. ..................... ................ 3

Location of Where the Work is to be Performed ............................................... ..................................... 3

Expected Contractor Work Hours and Conditions ................................................................................ 3

Work Description ....................................................................... ................................................................ 4

Impacts of Not Making Requested Changes ........................ .................................. ..................... ........ 4

Project Requirement ............................................................... ....................................................... ........ 4

Responsibilities and Assumptions ....................................................................................................... 4

Responsibilities ...................................................................................................................................... 4

Assumptions .......................................................................................................................................... 5

Project Contacts ...................................................................................................................................... 6

Project Control and Reports ..................................................................................................................... 6

Payment Schedule ..................................................................................................................................... .... 6

Travel and Expenses .............................................................................................................................. 7

Agreed to and Approved By: ................................................. .................................................. ..... ............. 7

Page 1

11:ffft'IR accen1:ure LIi ii Michigan Enterprise Call Center {MiECC) Statement of Work Authorization

SOW-067 OCS GENESYS EWM SUPP0RTV2

Statement of Work (SOW) Number: SOW-067 MIECC Genesys EWM Support

Project Title: Accenture MiECC support for Genesys Workload Distribution

Release (if applicable): - N/A

Enterprise

SOW Summary Description: Accenture MiECC support for Genesys Enterprise Workload Distribution

Estimate Submitted By: Ryan C. Sadler

Date Submitted: March 3, 2018

Requesting Department/ Agency Department of Health and Human Services (DHHS) -Office of Child Support

Approval Due Date: March 27, 2018



Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW include the following: 1. Add Accenture MiECC support and maintenance for the DHHS Office of Child

Support Enterprise Workload Management (EWM) software.

Scope ofWork Accenture will provide support for the following areas:

- ------ - --- ---- Page 2

DTN"1B accenture g1 I · Michigan Enterprise Call Center (MiECC) Statement of Work Authorization


a. Provide technical support as part of the Accenture MiECC team for the Genesys Enterprise Workload Management software.

b. Perform customer requested software configuration changes not requiring the Genesys software vendor.

c. Technical liaison to the DTMB infrastructure teams and the Genesys software vendor.

d. Day to day application support of the Genesys EWM Application and vendor management tools.

e. Provide support escalation to Genesys using their Customer Care Support portal.

f. Provide DHHS with Technical Assessment Group (TAG) representation for the Genesys EWM system.

g. Provide support according to Attachment 1: Service Level Agreement and Return to Service Goal of Contract No. 071B2200168.


Specific Department Standards Accenture will comply with DTMB Development Standards when performing this work.


Expected Contractor Work Hours and Conditions Services provided under this SOW shall be performed Monday through Friday between the hours of 8:oo AM and 5:00 PM.

-------------- Page3

DTftll1DD· accenture l.;11 11 Michigan Enterprise Call Center (MiECC) Statement of Work Authorization




Impacts of Not Making Requested Changes 1. Contact Center production issues would remain unaddressed and customer

service would decrease over time. 2. The software would not be maintained and updated. 3. The agency would be at risk if security updates are not applied. 4. The Genesys EWM software would not have local Accenture MiECC support to

meet the expectations of the agency. 5. The agencies expected employee productivity gains from the software may not be

able to be achieved.

Project Requirement The DTMB Client Service Center (CSC) and Remedy ticket system will be used to initiate and manage break/fix and maintenance requests. Remedy tickets may be created by agency or the contractor and will identify the problem to be fixed.


Responsibilities Rcsnnnsibilitv Accenture Al?enev DTMB

Completion of Agency Service Request Section of SOW ..; ,/ I

I

Completion of Proposal Response Section of SOW ,/

Sim Stntement of Work v ,/ v Issue Purchase Order ,/ ,/ Agree Upon Project Resources and Schedule ,/ ,/ ,/

Complete Deliverables as Defined in v sow ! Participate in Deliverable Review as ,/ ,/ Defined in SOW

--- - ----------- Page4

IDTftlllDD . . . accenture UI If I M1ch1gan Enterprise Call Center (M1ECC) Statement of Work Authorization


Responsibility Accenture Ae:enev DTMB Document Pnase Kl!\'lew Acceptance m v Acceotancc Review Phase and Overall Project v v v Acceptance Documents and Shin Prmide Access to Resources (e.g., v v Business Experts, Systems, Software, and Hardware) Required to Perform

, Services

Assumptions

1. This Statement of Work, SOW-067 OCS Genesys EWM Support ("SOW"), incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and SupportDTMB/(State, Office Of Child Support - OCS) (the "Contract") between Accenture LLP ("Vendor") and the State of Michigan Department of Management and Budget Acquisition Services (the "State") effective May 1, 2012.


3. Actual services will commence upon execution of this SOW by parties, State purchase order issuance, and confirmed final project plan with agency, DTMB, and Accenture.


5. The State of Michigan is responsible for the support contract with the Genesys software vendor.

6. Accenture MiECC provides Tier 2 support. Tier 1 and Tier 3 support is out of scope. Tier 1 support helpdesk services are provided by the DTMB Client Service Center. Tier 3 software product support services are provided by the software vendor Genesys.

7. This SOW would authorize an Accenture/MiECC base team resource will begin assignment on or before April 1, 2018. In the event that the begin dates change, Accenture will pro rate the invoice accordingly only for actual time resources provide services under this Statement of Work.

8. Accenture MiECC will participate in system and UAT testing as part of the transition. 9. During the Genesys warranty period, DHHS OCS the respective Project Control

Office (PCO) and Genesys will document any open production issues. When Genesys warranty period expires, PCO, Genesys, Accenture MiECC will classify open issues according to ownership for resolution (e.g., Genesys production support will maintain ownership and resolution or ownership for resolution will transfer to the

- -------------- Page 5

mnr■o Michigan Enterprise Call Center (MiECC) accenture Statement of Work Authorization


Accenture MiECC team). Prior to Accenture MiECC assuming ownership of open issues, Genesys, Project Control Office, and Accenture MiECC must agree upon transfer of issue ownership after the Genesys warranty period expires.

10. Prior to transition of support to Accenture MiECC, Genesys will conduct a technical handoff meeting in which final architecture, documentation, open issues, and other post-production topics will be discussed. Accenture MiECC will sign a transition complete acceptance form.


Email Team Member Role Contact Information Ryan Sadler Accenture Delivery • :cyan.c.sadl~@>ac~entur~.t;gm

Manae:er Kristine Handy Accenture Contract kristine.handy(a)accenture.com

Manager

Project Control and Reports Accenture will submit a monthly hours report to the DTMB MiECC Program Manager throughout the life of this project as part of the fixed price billing invoice.

Payment Schedule 1. Payment for the MiECC-Accenture Base team will be on fixed fee basis. Vendor

will invoice the agency monthly in the amount of $26,400 per month. 2. After this SOW ends on 9/1/2018, starting Oct t, 2018 the MiECC-Accenture base

team support will be included in the DTMB MiECC annual support PO for the agency.

Resource Role Total Suooort Cost MiECC-Acccnture Base Team - DHHSOCS $158,400 April 1, 2018-Sept3oth, 2018 (6 months) GenesysEWM $26,400 per month.

Sunnnrt

Total S1s8,400

---~----------- Page 6

April 16, 2018

DTft111B acceniure l.;l,I If Michigan Enterprise Call Center (MiECC)

Statement of Work Authorization SOW-067 OCS GENESYS EWM SUPPORTV2

Travel and Expenses Costs presented in this SOW are inclusive and contain no estimates for travel and expenses.


-- - ------ - -- ---

Name Role Signature Date I

Pratin Trivedi

Bill Pemble

Kathleen Cawley

Office of Child Support, Director of Information . Technology and Pa ent O erations Technology Managementanfa • ,,,/-(J Q Budget MiECC · (p / ~- '<--Director _.,,,,? _,,. ~'V'i


--------------- Page 7

kristine.handy

Stamp

~.-... · . ·.- >':¥.

. . STATE OF MICHIGAN CENTRAL PROCUREMENT SERVICES Department of Technology, Management, and Budget 525 W. ALLEGAN ST., LANSING, MICHIGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909



ACCENTURE


Southfield, Ml 48075

Kathleen Cawley

859-248-1187

' [email protected]

CV0062320


[email protected]

[email protected]

DTMB

DTMB

Effective with mutual signature the attached documentation executes three one year options and adds funding to support three additional years of Contact Call Center services. All other terms and conditions remain the same.

Description:

Nature of Change(s): Exercise the three remaining options years, adjust base services fix fee and add major enhancement funding, adjust rate card for the extension years, add supported services, add DHHS sub-agency, add DHHS !SD and DH HS-Office of Child support to base support, and add discounted payment terms.

Base Service Cost (Year 8-101 $ 11,684,445.90

Major Enhancement (Year 8-10) $ 3,922 959.00

Total Contract Funding (Year 8-10) $ 15,607,404.90

Change 1- Effective [Date]

Change 1.1, Update Section 1.002, Background:

The following list will be updated to add DHHS Integrated Service Delivery (DHHS ISD):

Today, MiECC supports contact centers at eight (8) agencies (with respective subsets within agencies as applicable)-

• Civil Service Commission (MCSC) • DTMB-Client Service Center (CSC) • DTMB-Office of Retirement Services (ORS) • Department of Health and Human Services (DHHS) - Integrated Services Delivery • Department of Health and Human Services (DHHS) - MiBridges IVR (terminates April 2019, replaced with

DHHS ISD) • Department of Health and Human Services (DHHS) - Office of Child Support • Department of Health and Human Services (DHHS)-Michigan Statewide Automated Child Welfare Information

System (MiSACWIS) • Talent & Economic Development (TED) - Unemployment Insurance Agency (UIA) • Michigan Department of State (MDOS) • State (MOOS) • Treasury- Collections • Treasury- Tax Processing Bureau • Treasury - Michigan Guaranty Agency • Department of Corrections (Electronic Monitoring Center)

Change 1.2 Update Section 1.0002, Background:

The following list will be updated to add MS Dynamics CRM and AWS cloud services:

The support services currently offered by MiECC are -• Multi-channel support:

• Contact center CRM • Interactive Voice Response (IVR) • Computer Telephony Integration (CTI) • Skills Based Routing • Reporting service • Workforce Management • Web self service • Email service • Web knowledge management • Integration with Document Management • Quality Assurance:

• Call Recording • Call Monitoring • Accenture Virtual Assistant Bots • MS Dynamics CRM • AWS cloud seNices

Change 1.3, Update Section 1.601, subsection B, Base Support Cost, is amended as follows:

Deleted: After providing monthly services, the Contractor shall submit an invoice at the end of the month.

Add: Contractor shall submit a quarterly invoice at the beginning of the month, starting on April 1, 2019, for Base Support Cost.

Change 1 .4, Update section 2.001, Contract Term to read April 30, 2022.

Change 1.5, Update Section 2.044, Invoicing and Payment - In General, subsection c, to add the following:

The Base Support invoice will be pre-billed quarterly, at the beginning of the month. A 1% discount will be provided to the State for payments made within 20 business days of receipt of the quarterly invoice will be provided

Change 1.6, Attachment 3, Table 3, Base Service Cost, shall be deleted in its entirety and replaced with the table in Exhibit 1. . . .

Change 1.7, Attachment 3, Table 4, Rate Card, shall be deleted in its entirety and replaced with the table in Exhibit 2.

Exhibit 1

i(t:~~:::: f[4]•; < Ye~T~ .::i~~~~J:/ (;{ I

::; r!:19_1:'.l_th~_)

Corrmission 'MCSCl DTMB..CJient Service Center (CSC) DTMB-Office Of Retirement Services (ORSl Environmental Quality (OEQ) Huma~es (OHS) ~-Bureau of Hea;lth Professions (BHP) State (MOOS) Treasury

. 'r'rbiiths) .;

Costs .e_eryear I 2,049,763.08 J 2,260,696.41 I 2,±53,549.7~ l2,-re3~3.0812,±83,663~\·,_,

DHHSOCS Support

DHHSISD SU£E:~rt

BASE SUPPORT TOTAL

NullKJerof months in that year Cost .E_er month Quarterly Payment TOtais'ase Service Cost (sum Of total 3 year cost by agen~

12 12 12 12 12

170.!.e1s.sg J 1ss,ssi.~04,462.48 1 2oe.snss 1 2oa!973.ss

2,483,66~.0_8 _ ~3,6_83~2,550,742.5212,619,612.5712,690,342.111,.--, ,.

filS,7721 594,398.86 I 610,447.63

662.0oe.s1 I 679,asz.s-s I ess,239.36

3, 791,522..84] 3,893,893.9613,999,029.10

12 12 12 12 12

2.oe.9:r,3_.59 _l_ ~os,s!_3~~ I_ sJs,sso.24_~!4s1.1s I 33:3,252.42

999.757.27

i 1,684,445.90

• DHHS OCS and DHHS ISD Support in the above table represent services previously contracted under SOW #63, SOW#67 and SOW#66

respectively and does not reflect any other services provided under base support.

Table 4: Rate Card

~!!#8~;f~!f~~~i.l!I •·· :11F:ltmiITiixE!t~.?~rly ••

Project Manager

Systems Architect

Business Analyst

Siebel Lead

Siebel Developer

Computer Telephony Specialist

Genesys Specialist

IVR Developer

NICE Analyst

Tester

Other (Please specify)

TBD

Total Major Enhancement Cost Year 1-7 Total Major Enhancement Cost Year 8-10

$181.00

$145.00

$138.00

$130.00

$113.00

$167.00

$267.00

$113.00

$113.00

$152.00

$150.00

Exhibit2

New Contract Rate for Extension 5-1-2019 to 4-30-2022

$185.89 $190.91 $196.06

$148.92 $152.94 $157.06

$141.73 $145.55 $149.48

$133.51 $137.11 $140.82

$116.05 $119.18 $122.40

$171.51 $176.14 $180.90

$274.21 $281.61 $289.22

$116.05 $119.18 $122.40

$116.05 $119.18 $122.40

$156.10 $160.32 $164.65

$154.05 $158.21 $162.48

$11,751,184.60

$3,922,959

-----------·--------------·-·---~·--·"-""""-~'"----·-----·

> accenture

Accenture LLP

1449 Wood;lrd Avenue

Detroit1 MI 48226

www.accenture.c:om

October 19, 2018

To: Bill Pemble, Director of Michigan Enterprise Contact Center State of Michigan, Depart of Technology, Management, and Budget 400 Pine St. Lansing, MI 48933

Re: Contact Center Support ("MiECC"), Contract# 071B2200168

Dear Mr. Pemble:

On behalf of Accenture, I am pleased that the State of Michigan wishes to retain Accenture to provide services in connection with the Michigan Enterprise Contact Center. Contract # 071B2200168, Change Notice #11 will:

10/29/2018

• Extend Contract# 071B2200168 three (3) years, commencing on May 1, 2019 through April 30, 2022:

• Update Base Support Cost and Rate Card, per Attachment A

Base Servtce Cost (Year 8-10) $ 11,684,445,90

Malor Enhancement (Year 8-10) $ 3,922,959.00

Total Contract Fund Ina /Year 8-1 0) $ 15,607,404.90

• Adds Department of Health and Human Services Integrated Service Delivery (DHHS ISD) as a supported sub-agency

• Adds the suppmt of DHHS ISD and DHHS-Office of Child support to the fixed base support

• Accenture was able to hold the base price firm from 2012-2019 with no cost of living adjustments during the first eight years. The Cost of Living Increase per U.S. Department of Labor has been 15.7% (cumulative) over the contract term*. Accenture competes for the best talent in an extremely competitive environment. As a result, we have updated our fixed price contract with the following cost of living adjustments Year 1: 2.7%, Year 2: 2,7% Year 3; 2.7%

Pagel of2

I I

• The Base Support invoice will be pre-billed quarterly, at the beginning of the month, and a 1% discount will be provided to the State for payments made within 20 business days of receipt of the quarterly invoice

• Adds additional contract funding in the amount of $3,922,959: • Approximately $1,250,000 for future Accenture Health and

Human Services (HHS) Virtual Assistant Bots. • Approximately $1,000,000 for future Statements of Work to

migrate current contact center from Avaya-Genesys and Siebel CRM to Cloud contact center technology.

• Approximately $750,000 for additional desired contact center services for the agencies.

• Add $761,808.27 to DTMB Delivery Order #180000006992 for Contract Year 7 which consolidates SOW 63 and SOW 67 into the base support services. This is required as the existing contract is funded through January 2019.

• Adds additional support services, including: MS Dynamics CRM. and AWS cloud services

All other terms and conditions of Contract #071B92200168 remain unchanged and in full force and effect.

Very truly yours,

ACCENTURE LLP

Kathleen Cawley Managing Director

*The U.S. Department of Labor publishes Employment Cost Index (ECI) for private industry workers, wages and salaries (not seasonally adjusted), as published by the Bureau of labor Statistics, U.S. Department of Labor are athttps://www.bls.gov/eci/.

Page 2 of 4

> accenture

10/29/2018

Civil Service Commission MCSC

DTMB-Client Service Center csc

DTMB-Office of · Retirement Services ORS Environmental Quali (DEQ) Human Services DHS

LARA• Bureau of Health Professions (BHP)

<1zm9nitis> <1irn\lni11s1 (12 rnoniiis> ,., ... : ...... · ... ,.,.--...... ,.,, ..... ,--,.·····.· --········"··· ····,

2,550,742.52 2,619,612.57 2,690,342.11

578,772 594,398.86 610,447.63

ort 662,008.31 679,882.53 BASE SUPPORT

3 1 522 8 8 1 TOTAL ,79 , . 4 3,893, 93.96 3,999,029. o

Number of months In that ear Cost per month

Quarterly Payment . Total Base

12 12 12

Pagel of2

Accenture LLP

1449 Woodard Avenue

Detroit, Ml 48226

www.accenture.com

...... ······················-

;Jial ~2 .. i r2r · Ve~rniiAo•·•

11,684,445.90

> accenture

Table 4: Rate Card .. ·:.: ... ·- ·.·: ·.,•,, ·, Fi.rm Fb(ed Hourly··•

Sl<lffing Categoey • ·• ··,, -- :,. ~:::~·:xn ::.:£.:.. .. -:: ·, __ _. ::.-:· - · ·

Project Manager $181.00

Systems Architect $145.00

Busl ness Analyst $138.00

Siebel Lead $130.00

Siebel Developer $113.00

Computer Telephony $167.00

Snecialist

Genesys Specialist $267,00

IVR Developer $113.00

NICE Analyst $113.00

Tester $152.00

Other (Please specify) $150.00

TBD

Total Major Enhancement Cost Year 1~7 Total Major Enhancement Cost Year 8--10

10/29/2018

Rate Card

Accenture LLP

1'149 Woodard Avenue

Detroit, MI 48226

www.accenhire.com

New Contract Rate for Extension 5-1-2019 to 4-30-2022 ,._._ .. ,: '.:.-· -,-:, ,. '.':-.. ;.- ,:v~~,r· ... · > C

, ... ---

\ • Year.8) i '--;, i\.• •.;Y'1>arto .... . ·-.. .. · .. ·. ',, ..... , .. . _,, .... :., ...

$185.89 $190.91 $196.06

$148.92 $152.94 $157.06

$141.73 $145.55 $149.48

$133.51 $137.11 $140.82

$116.05 $119.18 $122.40

$171.51 $176.14 $180.90

$274.21 $281.61 $289.22

$116.05 $119.18 $122.40

$116.05 $119.18 $122.40

$156.10 $160.32 $164.65

$154.05 $158.21 $162.48

$11,751,184.60

$3,922,959

Page 1 of2

ACCENTURE

STATE OF MICHIGAN CENTRAL PROCUREMENT SERVICES Department of Technology, Management, and Budget 525 W. ALLEGAN ST., LANSING, MICHIGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909



to Contract Number 07182200168

517-636-4741

DTMB



Kathleen Cawley DTMB

859-248-1187

[email protected]

• Effective with mutual signature the attached documentation is executed. All other terms and conditions remain the same.

DTI\IID · > l,;II 1, ID Michigan Entc1•prisc Call Center (MiECC) accenture

Statement of Work Authorization SOW ~063 CouDty FOC Support for DHHS Clot1d IVR and

Sow-063 AND sow-67CcN/ll

Contract Change A'i Ugrced upon in FY 19 P_m·c_hus_c Order #18009oi:lo69!'frl ("Bnse_ Sciviccs PO"),·thefee!lforSOW 63 Criunl.y Fo9·sui>port for DHHS ($20,562.50 per mm,th) and SOW r,7 IvlillCC GcnesYs EWM" S11pp6rt ($29, 400 per month) will 1,ic consolidfltrid into and be considered !lase Servic;es nnd will _continue to be invoiced und'e1· the Base Service:-; JlQ until the end of the Contract Term.

•\[,r(!ed lo and Approved By:

' 'e·, f Role Sh\natu1•c- Dute

l)TMB MlV.CC Dirt:t'ltw

Ai:t'U1\lu1·c Mmwging Dir~CtOI'

----------Pagel

STATE OF MICHIGAN CENTRAL PROCUREMENT SERVICES Department of Technology, Management, and Budget 525 W. ALLEGAN ST., LANSING, MICHIGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909



ACCENTURE ·



Kathleen Cawley

859-248-1187

• [email protected]

CV0062320


William Pemble

517-636-4741

[email protected]

Mike Breen

(517) 249-0428

[email protected]

CONTRACT SUMMARY

DTMB

DTMB

Effective with mutual signature the attached scope will be added to the contract and use existing contract funds per contract owner. All other terms and conditions remain the same.

l··r·na··. · ·e·· ·· > · · , · > ·• accenture . .:.! · ·• ,I · · Michigan Enterprise Call Center (MiECC)

Statement of Work Authorization SOW_71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact

Center, CRM to Cloud

Contents Project Background .................................................................................................................................... 2


Scope ofWork ............................................................................................................................................. 3

Acceptance Criteria .................................................................................................................................... 3

Specific Department Standards ................................................................................................................ 3

Location of Where the Work is to be performed .................................................................................... 3

Work Description .................................................................................................................................. 4

Impacts of Not Making Requested Changes ........................................................................................... 4

ProjectApproach ..................... _. ............ : ................................................................................ , .................... 4

Deliverables ................................................................................................................................................. 6

Work Plan .................................................................................................................................................... 6

Deliverable and Milestone Timetable ...................................................................................................... 6

Resources ...................................................................................................... Error! Bookmark not defined.

Responsibilities andAssumptions ........................................................................................................... 7

Assumptions ................................................................................................................................................ 7

Project Contacts .......................................................................................................................................... 8

Project Control and Reports ...................................................................................................................... 8

Fees and Payment Schedrile ...................................................................................................................... 8

Travel and Expenses ................................................................................................................................. 11

Agreed to and Approved By: ................................................................................................................... 12

--------------~Pagel---------------

"tJKJID accenture 11,rilf l:l,ID Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

SOW _71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact Center, CRM to Cloud

Project Background

SOW-071 Civil Service Contact Center, CRM to Cloud

Civil Service Contact Center, CRM to Cloud Initiative

N/A

Contact and CRM assessment Replacement to Cloud Services

Ryan Sadler

7/27/2018

MCSC

DTMB has an established shared IT support service center, known as Michigan Enterprise Contact Center (MiECC), to provide centralized support to the State of Michigan (SOM) contact centers across multiple agencies. The purpose of the Contract is for Vendor to provide shared IT services to maintain and enhance MiECC contact centers.

Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW :include the fo11owing:

Consult, Assist and Provide Services to Civil Service :in preparation, planning for the deployment of, and migration from on-premise contact center CTI (Genesys) and CRM (Siebe}) to a Cloud based platform. Using a cloud-based platform strategically positions Civil Service to be able to take advantage of the benefits of cloud. Those benefits include increased functionality, cost efficiency, operational flexibility, reduced risk and reliability.

--------------Page2

I

I I I I

I

I I

I I I I I

. . > D accenture l&J. Michigan Enterprise Call Cente1• (MiECC)

Statement of Work Authorization SOW _71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact


Scope ofWork Civil Service is seeking Accenture involvement in the strategic planning and implementation services for the migration of the Civil Service contact center to the cloud.

The planning will encompass analysis, review and solution determination including:

1. Strategy and project plan development coordination and assistance to Civil Service, DTMB, and Cloud vendor for migration from Genesys and CRM (Siebel) to Cloud based CRM and Contact Center services in a phased approach.

2. Providing the Project Management and Analyst/Testing services for the State of Michigan to work in conjunction with the DTMB, vendor (NICE-In Contact) to migrate from on-premise Genesys Contact Center to NICE-InContact Cloud.

3. Assist with comprehensive and strategic planning for the migration of contact center and CRM to Cloud services for the entire Civil Service contact center system.

4, Establishing a strategy and operational process to support an initial Contact Center and related business Disaster/Business Continuity Response.

Acceptance Criteria Each System Engineering Methodology (SEM) phase shall have an acceptance form that documents phase deliverable completion, open issues, and implementation considerations. Contractor, DTMB and Agency SOW authorized approvers shall review and sign acceptance according to Acceptance terms identified in Section 2.250 of Contract.


Location of Where the Wol'lc is to be pe1•formed Services provided under this SOW shall be performed in the State's facilities located in Lansing, Michigan Monday through Friday between the hours of 8:00AM and 5:00 PM.

--------------Page3

1·•1¥·1·~·· n > ~, , > : accenture .fit · :c ' D Michigan Enterprise Call Center (MiECC)

Statement of Work Authorization SOW_71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact



Work Description

Assist Civil Service with the requirements gathering, strategy solution analysis, software selection and providing the integrator and project management services for a Siebel and Genesys migration to Clond. Detel'mine a phased approach with agency approval check points and task order release for the CRM (Siebel) migration to Cloud.

Impacts of Not Making Requested Changes • On Premise contact center servers would need to be replaced and migrated to

NGDI providing marginal functional value to the business. • Oracle is not maldng significant investments in extending the On-Premise Siebel

platform and may not be a long term strategic platform for Civil Service. • The State of Michigan would not be able to take advantage benefits of capabilities

offered in the cloud • Increasing cost of support for on premise hardware and infrastructure

Project Approach Accenture will work with key State of Michigan Stakeholders to provide the following:

Phase o: Project Management Startup and planning: Jointly develop a project plan, assist Civil Service, DTMB, cloud vendor with the move from Genesys and CRM Siebel to Cloud based CRM and Contact Center services in a phased approach.

Phase 1 Base Migration for Ginesys Contact Center to Cloud (estimate 12

weeks): Provide MIBCC Project Manager and Analyst/Tester to lead in the planning, requirements, design, testing, deployment with the NICE-lnContact team to migrate the contact center technology from Genesys to InContact. The Phase 1 base migration would replicate the existing as-is Civil Service MIHR, DMO, DMU contact center IVR, call routing, Siebel screen pop integration and deliver any additional "out of the box"

-------------~ Page4 --------------

·· . · m,,• accenture ·1··.······ ·.. > .\/,la Michigan Enterp1•ise Call Center (MiECC) Statement of Work Authorization

SOW _71_Civil Service Contact Center CRM To Cloud ( 002)071 Civil Service Contact Center, CRM to Cloud

functionality, After deployment the Civil Service Genesys environment would be· decommissioned as appropriate.

Phase 2 *Optional, Contact Center Features (estimate 12 weeks): Provide MiECC Project Manager and Analyst/Tester to lead in the assessment, pl:µming, requirements, design, testing, deployment with the NICE-InContact team for optional features not in the current Genesys environment. Some optional features could include, IVR database integration for self-service, IVR phone survey (Echo), Workforce Management, other enhancements and optimizations as identified by the agency.

Phase 3 *Optional, Siebel CRM Solution assessment, analysis, planning (Estimate 8 weeks)

Provide team (Estimate 2 FI'E) to review current Siebel CRJ\1 environment and provide the assessment, detaHed analysis, costs and resource estimates, plans to consider:

1. Migration of Siebel CRM to a cloud environment (e.g., Salesforce,com, CRM Dynamics, Oracle Cloud, etc). Functionality to consider:

a. CRM Functionality b. Licensing (in conjunction with relevant DTMB Salesforce Center of

Excellence (CoE) customer intake process). c. Document workflow tracldng processes and related requirements (DTS

replacement). 2. Evaluate remaining on current Siebel on-premise environment and upgrade

existing hardware and software. Business case/ Cost-Benefit to consider: a. State of Michigan Next Generation Data Center (NGDI) environment b. Oracle Siebel software updates and support lifecycle.

Phase 4 *Optional, Plan and Implement the Siebel CRM assessment decisions. High level Estimate 6-12 months (estimate is .solution dependent to be updated after Phase 3 completion and release of task order).

*Optional Phases are at the discretion of Civil Service and DTMB. The Parties will mutually agree on the work plan, final scope, updated resources requirements and budget with a Task Order(s) (Attachment A), as incorporated into the Terms and

--------------- Page 5

l l

l I I I I l I I I I i I '

I I

t I

·1---'·r-·-·nvt·--_ · • > . --• ... - -· . ·- accenture . · I . . .. am Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

SOW _71 _ Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact Center, CRM to Cloud

Conditions of the SOW and Agreement. The Task Order(s), allows mutual flexibility and agreement for the parties to execute the next phase and add funding.

Deliverables Below are the specific deliverables that will be developed as output of this SOW:

The deliverables will be determined and mutually defined and agreed upon as part of the project plan for each Phase and would follow appropriate State of Michigan SEM Deliverables or vendor equivalent for the following high-level project areas:

1. Charter 2. Requirements 3. Design 4, Testing 5, Deployment 6, Training 7. Maintenance/Transition Plan

High Level Work Plan The anticipated performance period for this SOW is defined in work plan below.

A detailed work plan would be mutually defined and agreed upon as pait of each Project Phase.

Phased Milestone Timetable Estimated Stal't Estimated

Descriution Finish Phase o September 2018 Oct2018 Project Start un Phase 1 Oct2018 Jan2018 Contact Center to Cloud Optional Phase 2 Jan 2019 Apr2019 Contact Centerto Cloud Optional Phase 3 Nov2019 Feb 2019 CRM Assessment Optiona1 Phase 4 Apr2019 Mar2020 Implement the Siebe1CRM

-------------- Page 6

! i

I I I

I ! I i "

ITAr1B Michigan Enterprise Call Center (MiECC) accenture Statement of Work Authorization

SOW _71_Civi1 Service Contact Center CRM To Cloud (002)071 Civil Service Contact Cente1·, CRM to Cloud

I ass~s~ment deC1s10ns

Responsibilities and Assumptions Contractor, State, and Agency staff responsibilities for work under this SOW are depicted in the table below.

R':-~nonslbilitv . Accenture APencv DTMB

;\~~~w~1~g~~~~~RW~¥~~~r::: <;·:~; .. ~.--~r-~·-~:= :·'•:~·:':~ ·_;1·~:~ · t>:i:Y:3~~~ft COmpletion of ProposnlResjionse Section of SOW

· .;·Sirrn Stlll:13Q:lfliit"of W cif lc,r::~~,j-C:\i,'?:'.('i;;~t<;:::. ·;;:,,f:J;\;_if .'ii,;~,:+.:.- \':~\~::fl/ ?\;t =,~;:·•:':y.::!t:';:;.'. Issue Pu1·chase Order -./ ..,/

~~,~~~~~fr?j_!~t:1i~!o~~~~~f~f¥~~,,(-~:· -~,~>-•11y:.:7<•·: >:T'?!l;·::-·;· ~~;~:\/~'-:F Complete Deliverables as Defined in y sow .

;£~Jl,i'l~1~:iW~f~i~¥1,(~i~~¥;~~i;'-;- :~11ww;rn ,;~,,@;i\?;\ Document Phase Review .Acceptance ../ in Acceptance

i~~~~r~~~~~~~~-~~~~~~t\WU~f{ ,t~~;f.~~~~~i~ii~s- "f[~¾Y,~:t~ }!l~;::~~ii~W Provide Access to Resources (e.g., Business Experts, Systems, Softwat'C1

o.nd Hardware) Required to Pe1form Services

Assumptions

v v

1. This Statement of Work ("SOW") incorporates by reference the terms, conditions and deliverables of Contract No. 071E2200168 for the Enterprise Contact Center Maintenance and Support- DTMB/(State, Treasury, Civil Service) (the "Contract") between Accenture LLP ("Vendor") and the State of Michigan Department of Management and Budget Acquisition Services (the "State") effective May 1, 2012,

2. State will provide access to resources (e.g., business experts, software, systems, hardware, relevant documentation) required to perform services described in this sow.

3. Contractor shall not provide regulatory, legal, accounting advice or analysis, or interpretation of any contractual provisions, laws or regulation of any kind under this SOW.

4, Actual services will commence upon execution of this SOW by the parties and Task Order for Phase(s) 2,3,4, State purchase order issuance, and confirmed final project schedule with agency, DTMB, 3rd Party vendors and Accenture.

--------------- Page7

.. ···a···, > ··_ .- ·.. '._ ,. . . accenture l\l B. Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

SOW_71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact Center, CRM to Cloud

5, State will secure timely involvement of all State of Michigan contributors. Access to these individuals participating on the Project team is critical in order to complete the Deliverables within the defined timeframe and fees,

6. Decisions to be made by the State of Michigan will be made promptly and without unreasonable delay. State understands that any delay may impact project schedule and other estimates provided in this SOW.

7, Accenture will have no responsibility for the performance of other contractors or vendors engaged by State, or delays caused by them, even if Accenture has been involved in recommending or selecting such contractors or vendors.

8, State will be responsible for the contractual relationship with third parties and for ensuring that they cooperate with Accenture.

9, State will be responsible for any third-party license fee and setup costs of tools as required to accomplish the tasks outlined in this SOW.

10, Accenture will jointly work together with the DTMB CoEfor Cloud applications.

P1·oject Contacts The Vendor main contacts for this SOW include the following individuals:

Team Member Role Email Rvan·~ad½r'(· . .,,, : 'l 'Deliv,eWl\iJ:aµaker>,(: Xvan:6safiler'n1~cce\:itwe,'COJ1t,'''·,·•r-.:,<,:,·· 'i•/}: Kristine Bandy Contract Manager [email protected]

Project Control and Reports Accenture will submit a monthly hours report to the Agency and DTMB Project Manager throughout the life of this project as a requisite of the billing invoice,

Fees and Payment Schedule Payment for this SOW will be 'Time and Material and Fixed Fee basis. Vendor will invoice the State monthly for Services based on the payment schedule below. The total SOW value will not exceed the fee schedule below unless agreed upon through contract change management procedures:

Phase o, Phase 1 (T&M)

--------------Page8

. ·.. > ·M··. D' · accenture · .·•. ,,IEJ Michigan Enterp1•ise Call Center (MiECC)

Statement of Work Authorization SOW _71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact


Services Description

Phase 1 12 weeks MiECC Project Base Migration Manager and for Contact Analyst/Tester Center to Cloud

1~1~11«~" .

Phase 2 (T&M)


Contract Estim Rate ated $/hr Hours

Estimated Billings

500 $138 $69,000

':;:;:;.·,',~:)•,~' .:~;::,::,;~;)\:.:;f;;;,.; .. ;'.,;. :·· 159'.'5'0 &;;)\;.

Estim ated

Contract Rate $/hr

Estimated Billillgs

Project Manager ·tAnaCst' '.!'.ester·,; ;,,,,.,,,,,,•;,;,,\,,,,,;,,1h~;,);,,,,:,fe~:,;,,,,)X,~, ,,500.,,,,,,1,. iiJ!13 g,,:,;,,,;~;;fr,,., ,; 69 •oo.o M,,,,,,, Sub Total $1591500

Phase 3 (Fixed Price)

--------------Page9

I

I I I

I I

I l I i l l

l'\Tlltb accenture it;llil .il!IJ Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

SOW _71_ Civil Service Contact Center CRM To Cloud ( 002)071 Civil Service Contact Center, CRM to Cloud

Services Description Contl•act

Estim Rate ated $/hr Hours

Estimated Billings

.~~,,,~l4r:lii111

Phase 4 (tbd)


Page ------------~ 10

Contract Rate $/hr

$146,972

Estimated Billings

.. ' tfltlA accenture · .. a ,i.f.l~. Michigan Enterprise Call Centei• (MiECC)

Statement of Work Authorization SOW _71_ Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact



------------~ Page 11

' ' I I i I

i l ' ' I I I I I I l , I I I I ! !

i ! !

·M•.···e··-. > ·· < · · ·.- ·• accenture

·• • · · · Michigan Enterprise Call Cente1• (MiECC) Statement of Work Authorization

SOW _71_Civil Service Contact Center CRM To Cloud (002)071 Civil Service Contact Center, CRM to Cloud


Susan Wilmore

DTMB Business Relationship Mana er

Bill Pemble DTMBMiECCProgram ~-' /r:_ e~- . Director / / _.. d

p ~72/1 .

Kathleen Cawley

Accenture Managiog Director /(!-1/k.tt, E, /,uef,() - August30,201B

______________ Page

1Z

I !

I

I '

I I

I I

> ·• accenture · Michigan Enterprise Call Center (MiECC)

Statement of Work Authorization SOW _71_ Civil Service Contact Center CRM To Cloud ( 002)071 Civil Service Contact

Cente1·, CRM to Cloud

Attachment A

Task Order (To Be Determined)

------------~ Page 13

I I

I I I I

I I I

. I I l

I

81 ~I ~I al ,:i I

STATE OF MICHIGAN ENTERPRISE PROCUREMENT Department of Technology, Management, and Budget 525 W. ALLEGAN ST., LANSING, MICHIGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909




ACCENTURE William Pemble

517-636-4741 3000 Town Center, Suite 2400


Kathleen Cawley Mike Breen

859-248-1187 (517) 249-0428


CV0062320

CONTRACT SUMMARY

DTMB

DTMB

~t-JTACT CENTER SUPPORT


Effective with mutual signature the attached scope is being added to the contract with the use of existing funds ($158,400.00) to support the engagement. All other terms and conditions remain the same.

l\ftlDn accenture If Michigan Enterprise Call Center (MiECC)

Contents

Statement of Work Authorization SOW-067 OCS GENESYS EWM SUPP0RTV3

Background ................................................................................................................................................. 2


Scope ofWork ............................................................................................................................................. 2


Specific Department Standards ................................................................................................................ 3

Location of Where the Work is to be Performed .................................................................................... 3


Work Description ....................................................................................................................................... 4

Impacts of Not Making Requested Changes ....................................................................................... 4

Project Requirement .............................................................................................................................. 4


Responsibilities ...................................................................................................................................... 4

Assumptlons .......................................................................................................................................... 5


Project Control and Reports ..................................................................................................................... 6

Payment Schedule ......................................................................................................................................... 6

Travel and Expenses .............................................................................................................................. 7

Agreed to and Approved By: ..................................................................................................................... 7

--------------- Page 1

PJIB Michigan Enterprise Call Center (MiECC)

> accenture

Statement of Work Authorization SOW-067 OCS GENESYS EWM SUPPORT V3

'l:ltateriierit'of:Work'(SOW) Numb-er,- SOW-067 MIECC Genesys EWM Support

Project Title:


SOWSU:111.111.aryDeseiiptiori:

EstimateSubni.itte_d By:

Diite'Sulimitted:

Requestingl)epartment/Ageney_

Approval<Dtie,Date:

Accenture MiECC support for Genesys Enterprise Workload Distribution

N/A

Accenture MiECC support for Genesys Enterprise Workload Distribution

Ryan C. Sadler

March 3, 2018

Department of Health and Human Services (DHHS) -Office of Child Support

March 27, 2018



Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW include the following: 1. Add Accenture MiECC support and maintenance for the DHHS Office of Child

Support Enterprise Workload Management (EWM) software.

Scope of Work Accenture will provide support for the following areas:


SOW-067 OCS GENESYS EWM SUPPORTV3

> accenture

a. Provide technical support as part of the Accenture MiECC team for the Genesys Enterprise Workload Management software.

b. Perform customer requested software configuration changes not requiring the Genesys software vendor.

c. Technical liaison to the DTMB infrastructure teams and the Genesys software vendor.

d. Day to day application support of the Genesys EWM Application and vendor management tools.

e. Provide support escalation to Genesys using their Customer Care Support portal.

f. Provide DHHS with Technical Assessment Group (TAG) representation for the Genesys EWM system.

g. Provide support according to Attachment 1: Service Level Agreement and Return to Service Goal of Contract No. 071B2200168.





-------------·-· ·-·-· Page3

> . h. . a1i ) accenture Mic 1gan EnterprISe C Center (MiECC

Statement of Work Authorization SOW-067 OCS GENESYS EWM SUPP0RTV3



Impacts of Not Making Requested Changes 1. Contact Center production issues would remain unaddressed and customer

service would decrease over time. 2. The software would not be maintained and updated. 3. The agency would be at risk if security updates are not applied. 4. The Genesys EWM software would not have local Accenture MiECC support to

meet the expectations of the agency. 5. The agencies expected employee productivity gains from the software may not be

able to be achieved.

Project Requirement The DTMB Client Service Center (CSC) and Remedy ticket system will be used to initiate and manage break/fix and maintenance requests. Remedy tickets may be created by agency or the contractor and will identify the problem to be fixed.


Responsibilities r----,R.:cs=o=ns::;ib;:;i:.,li;:::-----,-.:::==cr==:.-==•

Completion of Proposal Response Sc<llon of SOW

~i · -· StntenicrttOf;Wfrrk;. Issue Purchase Order

Complete Dclivcrable.i as Defined In sow Partici})?te in1DeJiVl:fuble Review: as Defined in SOW

--------- Page 4 ---------------

> . accenture

Michigan Enterprise Call Center (M1ECC) Statement of Work Authorization

SOW-067 OCS GENESYS EWM SUPPORTV3

Document P asc Re1, cw Acceptance m Acee lance

;R_evi~, P_Dll5e _ni]d_-9vef1:1U _'_l~toject Ac' ,, funce Documents and'Si .

Assumptions

Prmide Access to Resources (e.g., Business E.«pcrts1 Systems, Software, and Hardware) Required to Perform Scniccs

Accenture D1MB

1. This Statement of Work, SOW-067 OCS Genesys EWM Support ("SOW"), incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and SupportDTMB/(State, Office Of Child Support - OCS) (the "Contract") between Accenture LLP ("Vendor") and the State of Michigan Department of Management and Budget Acquisition Services (the "State") effective May 1, 2012.


3. Actual services will commence upon execution of this SOW by parties, State purchase order issuance, and confirmed final project plan with agency, DTMB, and Accenture.


5. The State of Michigan is responsible for the support contract with the Genesys software vendor.

6. Accenture MiECC provides Tier 2 support. Tier 1 and Tier 3 support is out of scope. Tier 1 support helpdesk services are provided by the DTMB Client Service Center. Tier 3 software product support services are provided by the software vendor Genesys.

7. This SOW would authorize an Accenture/MiECC base team resource will begin assignment on or before April 1, 2018. In the event that the begin dates change, Accenture will pro rate the invoice accordingly only for actual time resources provide services under this Statement of Work.

8. Accenture MiECC will participate in system and UAT testing as part of the transition. 9. During the Genesys warranty period, DHHS OCS the respective Project Control

Office (PCO) and Genesys will document any open production issues. When Genesys warranty period expires, PCO, Genesys, Accenture MiECC will classify open issues according to ownership for resolution (e.g., Genesys production support will maintain ownership and resolution or ownership for resolution will transfer to the

ftllD accenture If ID Michigan Enterprise Call Center (MiECC) Statement of Work Authorization


Accenture MiECC team). Prior to Accenture MiECC assuming ownership of open issues, Genesys, Project Control Office, and Accenture MiECC must agree upon transfer of issue ownership after the Genesys warranty period expires.

10. Prior to transition of support to Accenture MiECC, Genesys will conduct a technical handoff meeting in which final architecture, documentation, open issues, and other post-production topics will be discussed. Accenture MiECC wilJ sign a transition complete acceptance form.

Project Contacts The Vendor main contacts for this SOW include the fo11owing individuals:

Email Team Member Role Contact Information J.ty~µ,s_~clle~ · · ~-· Accentiire:Delivery •··· · rjiariic.sa:dler@accentifre:coni ·'

:-·::,_.-,.--- -.:::</:·--"-::--):::: - <:i :·;Mana-g·e1:<~~-:-z:L):ti·-':·,_,_::<_-,------\-::: :.,:co· -- __ ,-·.:?,:,:.<- :"

Kristine Handy Accenture Contract Manager

[email protected]

Project Control and Reports Accenture will submit a monthly hours report to the DTMB MiECC Program Manager throughout the life of this project as part of the fixed price billing invoice.

Payment Schedule 1. Payment for the MiECC-Accenture Base team will be on fixed fee basis. Vendor

will invoice the agency monthly in the amount of $26,400 per month. 2. After this SOW ends on 9/30/2018, starting Oct 1, 2018 the MiECC-Accenture

base team support will be included in the DTMB MiECC annual support PO for the agency.

Total Su ort Cost

,Total

· Page 6 ···--~



Pralin Trivcdl

officeofcliifd- · Support, Director or Inrormalion Tei:hnology and Pa ent O . r.1tions ...

Bill Pemble

·Tee nology ·

Managementanfa ~-•_:::> A-/4 Budget MIECC / .· / Director · .,-C/ • · {._.t:;?7,,1,-

Kathleen Cawley Accenture Managing 1{1/km f,,/Atefwy Director K!f O

•----------- Page? ---

April 16, 2018

STATE OF MICHIGAN ENTERPruSEPROCUREMENT Department of Technology, Management, and Budget 525 W. ALLEGAN ST., LANSING, MICHIGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909


Change Notice Number .!l.

ACCENTURE



• Kathleen Cawley

859-248-1187

[email protected]


[email protected]

[email protected]

DTMB

DTMB

Effective with mutual signature the contract is amended to add a scope of work for the DHHS Contact Center Pilot and Phase 1, 2, 3 per attachment. All other terms and conditions remain the same.

. · · I ,,_ -. accenture .. ·--.···a > -~-" · . Michigan Enterprise Call Center (MiECC)

Statement of Work Authorization SOW 066 DHHS ISD Contact Center FY18

~mt'!1'~t~9X~~-c~pm~uw1"~f!i ow _066 DHHS ISD Contact Center FY18 ~: .,:•,.--.~ .. ·/':·.~·--:_.,,~_._::: '.: .; ·:;.-,:~j ;,o~;·:•:-;.:~.L~-' ,,. -\;~ ·/_ : .. .,? -~·"';··< ._:

HHS ISD Contact Center

~~~1f~f~~~ --"~m,~,,,.

um~till~!~11~M~~~{,i;~it;i~f)f \? .. ~~!}.;~:~~~~ :T~~~~:!1:;_~:-?}~~':;:~•::,~:

HHS !SD Cc>ntMt Center

an Sadler

cccmber6, 2017

apartment of Health and Human Services (DHHS)


Backgl'ound Over the years, DTMB has established a shared IT support service center, known as Michigan Enterprise Contact Center (MIECC), to provide centra1ized support to the State of Michigan (SOM) contact centers across multiple agencies, The purpose of the Contract is for Vendor to provide shared IT services to maintain and enhance MiECC contact centers.

Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW Include the following: . 1. Provide the following roles to the ISD Contact Center Project (Pilot and Phase 1,2,3)

a, MiECC Project Manager b. M!ECC Technical Architecture Lead c, MiECC Lead Analyst d MiECC Contact Center Technical SupportAnalyst(s)

·------------ Pagel -··--·-·"··-···-~--- ·------

···M·•·. > · . ·. · . ·. · ;: : . . . accenture If ·· 1B Michigan Enterp1•lse Call Center (MIBCC) Statement of Work Authorization

SOW 066 DHHS ISD Contact Cenre1• FY18

The intent of this SOW is to: 1. Extend the current Accenture project team (SOW_o66) through December 31,

2018 to complete implementation of the Contact Center Pilot and Phase 1,2,3 for the Integrated Services Delivery Project,

2 • To enable the Michigan Enterprise Contact Center (MiECC) Team to provide technical support and maintenance, as defined below, for the State's pilot and Wave 1,2,3 county contact center roll outs through December 31, 2018.

Scope ofW01•k Accenture will provide support for the following areas:

1. Provide technical support with maintenance of the contact center cloud technology.

2. Participate in monthly DTMB led operation meetings as appropriate to determine !SD continuous improvement and program change impact to the contact center application.

3. Provide technical expertise for developing and deploying contact centers fo1• the DHHS !SD project

4. Work closely with the cloud contact center vendor to coordinate and facilitate the ISD Contact Center pilot and rollout requirements, design, testing and deployment activities.

5. Technical liaison to the DHHS ISD Contact Center, 6. Coordinate and facilitate the networl1 connectivity between the cloud

vendor and the State of Michigan for coordinating site readiness for pilot and rollout counties.

7. System and Integration application testing of the DHHS IVR and Contact Center.

8. Overall technical management of the DHHS ISD cloud contact center. 9. Provide technical project escalation to DHHS Business Integration Center

PMO. 10. Work with the Universal Case Load and Customer Portal Delivery Teams.

Acceptance Cl'iteria Each System Engineering Methodology (SEM) phase shall have an acceptance form that docwnents phase deliverable completion, open issues, and implementation considerations. Vendor, DTMB and Agency SOW authorized approvers shall review and sign acceptance according to Acceptance terms identified in Section 2,250 of Contract.

--------- Page2

~T•'IR accenture !&.la i'f 11.IIIW Michigan Enterprise Call Center (M!ECC) Statement of Worlt Authorization

SOW 066 DHHS ISO Contact Center FY18


Location of W11ere the Wol'k is to be Performed Services provided under this SOW shall be perfoi·med In Lansing, Michigan.

Expected Contracto1· Wo1•k Hours and Conditions Services provided under this SOW shall be performed Monday through Friday between the hours of 8:oo AM and 5:00 PM.



Impacts of Not Making Requested Changes The contact center is a critical part of the Integrated Services Deliver project for DHHS.

The integrated contact center application is a critical part of improving the lives of Michigan citizens and providing case worker relief by providing a single number, Interactive Voice Response (IVR) System and caseworker sldlled queue for answering voice calls.

By not making the requested changes for the IVR and contact center DHHS would not be able to achieve the desired customer experience improvements for Michigan citizens and would not be able to provide caseworker relief.

. ' .. · .. . > DTl\111 accenture .~II fl.f IIJ Michigan Enterprise Call Center (MiECC)

Statement ofWorkAuthorization SOW 066 DHHS ISD Contact Center FY18

Project Deliverables

Project Management DQshboard Framework

MIECC Operations Monthly Status Report

___ ........,, ,. ··► ••'"······ ,.. '_•.,,.-.• rJ-'-' .... ,, .•.• ,...,_.

Support DTMB with transformation project management activities:

• Executive Reporting Dasl1board • Jssues/Riaks Management Plan

Format: Changepoint/Email as requested by Business Integration Center (BIC)

Support DTMB with maintenance and operations • Executlve Reporting Dashboard , The report details system uptime, system

issues/tickets and their cause and or status, and planned system updates.

Format: MS Word/ Changepoint/ EmaU/ Other

--------------Page4

■MR Michigan Enterprise Call Center (MiECC) accenture Statement of Work Authorization

SOW _066 DHHS ISD Contact Center FY18

Respousibilities and Assumptions Vendor, State, and Agency staff responsibilities for work under this SOW are depicted in the table below,

,:SJliiiStatcmcnfor.work-:::.;::,:;r:-:;·::.:.:;{.~; ;,:;:.;.j;v,: ·.,;-: ,•·:::-4.:, :_· . .i: :/,,J.:.:· .. [SSUC FU aae O v V

complete Dclivcrablcsas Defined in sow v

Document 'Phnse Review Acceptance -,/ in ,._,...,...,1nm:c

,f

.IIT_· ~ •M._··._. m'!- . . accenture UB · 1U M1clugan Enterprise Call Center (MiECC) .

Statement of Work Authorization SOW 066 DHHS ISD Contact Center FY18

MiECC Responsibilities: Production Maintenance and Support -

Role Organization Responslbllltv

• Overall 1~ponsibility nnd accountability for system performance and data.

• Assigns nnd approves all piojecl activities . • Represents MiECC as U1e single POC for project

assignments. • Appl'Oves the results of Quality Ass urn nee Testing • • Maintains tl1e Maintenance Pinn and obtains the

customel"s agreement to any changes to the plan after Go/Live of the application

• Conducts status meetings with the Project Mnnagement nnd or Business owners.

• Included on communications and involved ns needed on

System DTMB improvements nnd updates

Owner/Support (Michigan • Acts as Test Lead for the MiECC support team for DHHS Point of Contact Enterprise ISO Contact Center, (POC) Contact • Use the business process requirements to drive out product

Center) requirements and metrics. • Assist in defining and reviewing requirements for the

application. • Validate the design with the stakeholders to ensure that the

design satisfies the requirements .. • [nform the project mnnagerofany issues that rnay affect

other areas of the project • Participate in quality management reviews . • Participate In transitioning the deidgns to the developers,

and ensm·e a clear and complete understanding of the designs.

• Point of Contact for DTMB with the Cloud Contact Center Vendor

--------Page6

a,: . . a

Technical Analyst(&)

Assumptions

Michigan Ente1•p1•ise Call Center (MiECC)

> accenture

Statement of Work Authorization SOW _066 DHHS ISD Contact Center FY18

• Assist In defining and reviewing the technical requirements for the application, including security, integration, performance, and qunlity requirements,

• Create, update and maintain the technical designs, based on the business requirements provided Jo the functional designs.

• Confirm the completeness nnd consistency of the technical designs. Resolve any inconsistencies discovered.

• Inform the functional designer and team lead ofuny issues that mny affect other nreas of the project.

• Particlpnte In quality reviews to ensure trnceabillty of the designs to the requirements.

• Ensure the system meets the stated technical design

DTMB requiremente, Validate that the delivered product appears to meet stated functionel design requiremente.

(Michigan • Perform the detailed design of application and technical Enterprise architecture components, Conine! Cente1·) • Configure, build, and test the application 01· technical

1ITchitccturc components, • Work with other developers, designers, and architects to

make sure that the configuration and custom components meetapplieation requirements and performance goals.

• Follow good security coding practices to ensure the application is free of most common coding w)nerabilities.

• Participate ln code reviews . • Inform the technical architect and project manager of any

issues that may nffect nny other areas of the project. • Participate in transitions of the application or teclmical

architecture components to the testers. • Fix any defects and performnnce problems discovered ill

testing, • Document the D""lication to facilitate maintenance

1. This Statement of Work SOW_o66 DHHS ISD Contact Center ("SOW") incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and Support- DTMB/(State, Treasury, Civil Service) (the "Contract") between Accenture LLP ("Vendor") and the State of Michigan Department of Management and Budget Acquisition Services (the "State") effective May 1, 2012.


·· ··a··a· > · · · · . ', ·• . . . accenture .mN, · . .· Michigan Entel'pl'lSe Call Center (M1ECC) Statement of Work Authorization

SOW _066 DHHS ISD Contact Center FY18

3. Actual services will commence upon execution of this SOW by parties, State purchase 01·der issuance, and confirmed final project with agency, DTMB, and Accenture.

4. The scope and hours in this SOW represents a high level estimate through 12/31/2018, additional hours required to complete the work beyond this date described in this SOW shall be negotiated as an amendment to SOW.

5, The State of Michigan is responsible for the procurement of contact center softwa1·e licenses, support and services with the contact center vendor.

6. The State of Michigan will be responsible for any contractual relationship with third parties and for ensuring that such third parties cooperate with Accenture, and Accenture will not be required to sign any agreement with any third party. Accenture will report Issues and escalation to the State but the State will be responsible for engaging the 3rd party vendor for escalations and address outstanding issues.

7. The State of Michigan's Business Integration Center (BIC) will be responsible for managing the Pilot and Wave tlmelines. Should the tlmelines be extended and exceed the term of this SOW, an amendment will be agreed by both parties to extend the services.

8. Accenture will not be held responsible for any delays caused by the State's 3rd party vendors.

9. The MiECC base team members will assist the Accenture Project Manager and Contact Center vendor in the delivery of the project. .As needed, Accenture will backfill a support resource to assist the production support team to maintain current operations for other MiECC supported contact centers during the project.

10. The State of Michigan is responsible for the procurement oflicenses and services with the selected contact center vendor.

11. System and Integration Testing would be performed by the DTMB Testing Center of Excellence (TCOE) worldng with MiECC.


Email Team Member Role Contact Infol'mation

Kristine Handy Accenture Contract [email protected] Manazer

~------ Pages

• ~- . . . accenture IT-· >

. PJla M1ch1gan Enterprise Call Center (M1ECC) Statement of Work Authorization

SOW 066 DHHS ISD Contact Center FY18

Pl'oject Contl'ol and Reports Accenture will submit a monthly hours report to the DTMB•MiECC Project Manager throughout the life of this project as part of the fixed price billing invoice.

Payment Schedule

Pilot and Phase 1,2,3 Roll out Team extension and MillCC Maintenance and Support Totnl

RecoUl'BC Hourly Est n.csou1·cb ltole Name. R.nte Hour.s

MillCCBnso Team

Contact Center Lend Annlyst Adam

Yusko

$150 MIECC Basc l<mm

7'2JJ

· rate

Conta<:t Center DeHvccy Lend

$150 MiECC

l\ynn Daso Sadler team 480

rate

l'av,ncnt Schedule Pnymcnt

Total

$288,ooo

fit ~B~~i )lit t/i ;:~fr~~ I~~~'1:1: }i{j]:, P;"/r~~!~~~\1;~lt4i~~i)vi!\;~1 rj}M:~~-:.-Totul PO $992,124 Amount rcnulred

•MIECC Base Team will be deployed/or 12 months starting in Januaiy 2018 and ending in Decembe1· 2018, through the Pilot and Phase 1,2,3 as requi1•ed.

Travel and Expenses Costs presented in this SOW are inclusive and contain no estimates for tr11Vel and expenses.

-----·-,---------------· Page9

. . .... > Dll'ft,nB;t accenture QI I.JIii Michigan Entc1•prise Call Center (MiBCC)

Statement of Work Authorizntion SOW 066 DHHS ISD Contact Center FY18

Ag1·eed to and Approved By:

Jud Odett

Bill Pemble

Kathleen Cnwlc

Depa1tment of Technology Management and Budget ISD Pl'oject Director Department of

Technology ¼ ~'\ Management and ' • / BudgetMIECC / '/1/ Y-:;;-·-" ,?/ /., 7 / "7 / ~ Dh'ector .,.,c,,...,l,,/' ~n,[ ~.. A, '.-a< ~7

Accenture Managing Dh'ector

--------~---- Page 10



Change Notice Number z to

Contract Number 07182200168

ACCENTURE William Pemble

, 3000 Town Center, Suite 2400 517-636-4741


Mike Breen

859-248-1187 (517) 249-0428


CV0062320

CONTRACT SUMMARY

----

DTMB

DTMB

□ 1-· _____ II □ I April 30, 2019

----- I ' $28,089,978.51 I $0.00 r $28,089,978.51 l

DESCRIPTION

Effective with mutual signature the contract is amended to add two subcontractors Nuance Communications Inc. and Amazon Connect. All other terms and conditions remain the same.

I I

> accenture

March 19, 2018

To: Bill Pemble, Director of Michigan Enterprise Contact Center

Accenture LLP

Suite 2400

3000 Town Center


www.accenture.com

State of Michigan, Depart of Technology, Management, and Budget 7285 Parsons Dr. Dimondale, MI 48821

Re: Contact Center Support ("MiECC"), Contract # 071B2200168

Dear Mr. Pemble:

Accenture is requesting a Change Notice update with mutual authorization to provide services in connection with Michigan Enterprise Contact Center (MiECC). Based on our recent discussions, Contract# 071B2200168 Change Notice will include:

• Update the list of active supported agencies per Attachment A; • Add two additional subcontractor services per Attachment A.

All other terms and conditions of Contract #071B92200168 remain unchanged and in full force and effect.

Very truly yours,

ACCENTURE LLP

Lisa Cawley Managing Director

3/19/2018 Page 1 of2

ATTACHMENT A

Description:

Nature of Change(s): Effective, with mutual authorization, add Department of Corrections as a new supported agency; add supported services and two (2) new Vendor's subcontractors in support of the Michigan Enterprise Contact Center. All other Terms and Conditions remain the same.


Change 1.1, Update Section 1.002, Background:

The following list will be updated to add Department of Corrections:

Today, MiECC supports contact centers at eight (8) agencies (with respective subsets within agencies as applicable)-

• Civil Service Commission (MCSC) • DTMB-Client Service Center (CSC) • DTMB-Office of Retirement Services (ORS) • Department of Health and Human Services (DHHS) - MiBridges IVR • Department of Health and Human Services (DHHS) - Office of Child Support • Department of Health and Human Services (DHHS) - Michigan Statewide Automated

Child Welfare Information System (MiSACWIS) • Talent & Economic Development (TED) - Unemployment Insurance Agency (UIA) • Michigan Department of State (MOOS) • State (MOOS) • Treasury - Collections • Treasury- Tax Processing Bureau • Treasury - Michigan Guaranty Agency • Department of Corrections (Electronic Monitoring Center)

Change 1.2 Update Section 1.0002, Background:

The following list will be updated to add Accenture Virtual Assistant Bots:

The support services currently offered by MiECC are -• Multi-channel support:

• Contact center CRM • Interactive Voice Response (IVR) • Computer Telephony Integration (CTI) • Skills Based Routing • Reporting service • Workforce Management • Web self service • Email service • Web knowledge management • Integration with Document Management • Quality Assurance: • Call Recording • Call Monitoring • Accenture Virtual Assistant Bots

Page 2 of 3

Change 1.3, Update Section 1.201, subsection A, Contractor Staff, is amended to add the following subcontractors: Name of Nuance Subcontractor Address Nuance Communications, Inc.

Worldwide Headquarters 1 Wayside Road Burlington, MA 01803 United States

Contact Person Dawn Dreyfus Epstein Government Account Manager, Central Region 847-716-4818 (office) 1224-213-3952 (mobile)

Work to be Future IVR and Call Center Specialist skill set. Contracted Contractor At Nuance, our people and our technology have pioneered the highest Descriptive functioning speech software in the world, perfecting the ability for machines Information and to recognize and emulate the human voice. We design and deliver Abilities technologies that intuitively link man, machine and the global storehouse of

knowledge to help companies and consumers work seamlessly and intelligently with the world.

Our rich heritage, strong financial background, innovative technology and pervasive solutions are the pillars that form the foundation of Nuance Communications todav.

Name of Amazon Connect Subcontractor Address 410 Terry Ave. North

Seattle, Washini:iton 98109 Contact Person Mike Riley

[email protected]

Work to be Software as a service for cloud contact center Contracted Contractor Amazon Connect is a self-service, cloud-based contact center service that Descriptive makes it easy for any business to deliver better customer service at lower Information and cost. Amazon Connect is based on the same contact center technology Abilities used by Amazon customer service associates around the world to power

millions of customer conversations. The self-service graphical interface in Amazon Connect makes it easy for non-technical users to design contact flows, manage agents, and track performance metrics - no specialized skills required. There are no up-front payments or long-term commitments and no infrastructure to manage with Amazon Connect; customers pay by the minute for Amazon Connect usage plus any associated telephony services.

Page 3 of 3



Change Notice Number§.

ACCENTURE



• Kathleen Cawley

859-248-1187

[email protected]


517-636-4741

[email protected]

[email protected]

DTMB-IT

DTMB

Effective immediately as per Agency request and statement of work additional funding is being added to the contract for enhancements for the ORS Compass solution ($42,248.00). All other terms and condtions reamin the same.

• Michigan Enterprise Call Center (MiECC) Statement of Work Authorization

> accenture

SOW 064 Office of Retirement Services - Intranet Enhancement Services

Contents Background ................................................................................................................................................. 2


Scope of Work ............................................................................................................................................. 3


Specific Department Standards ............................................................................................................... .4

Location of Where the Work is to be Performed .................................................................................... 4


Work Description ....................................................................................................................................... 5

Impacts of Not Making Requested Changes ....................................................................................... 5

Deliverables & Activities ........................................................................................................................ 5

Work Plan ................................................................................................................................................ 6

Deliverable and Milestone Timetable .............................................................................................. 6


Responsibilities ................................................................................................................................... 7

Assumptions .......................................................................................................................................... 7


Project Control and Reports ...................................................................................................................... 8

Payment Schedule ...................................................................................................................................... 9

Travel and Expenses ............................................................................................................................... 9

Agreed to and Approved By: ..................................................................................................................... 9

---------------- Page 1


> accenture


Statement ofWork (SOW}Number: SOW _064 - Office of Retirement Services - Intranet Enhancement Services

Project Title: Office of Retirement Services - Intranet Enhancement Services

Release (if applicable):·

SOW Summary Description:

Estimate Submitted By:

Date Submitted:

Requesting Department/ Agency

Approval Due Date:

Office of Retirement Services - Intranet Enhancement Services

Eya!Darmon

August 23, 2017

Office of Retirement Services

September 4, 2017


Background The State of Michigan Office of Retirement Services (ORS) serves working and retired public servants of five Michigan retirement systems: Public School Employees, State Employees, State Police, Military and Judges. ORS is a division of Michigan's Department of Technology, Management and Budget (DTMB) and has more than 530,000 customers and works with more 800 employers within the State of Michigan.

The purpose of this SOW is for the design and implement enhancements for the ORS Compass solution, an intranet-based content management system (CMS) in SharePoint for ORS. Compass provides immediate access to information for all ORS staff, including customer call agents. The solution has become indispensable for conveying key customer information to staff by:

(1) Preparing staff with questions that are usually expected from members (2) Navigating to answers quickly (3) Having access to the single, right answer for members

The content in Compass is maturing, and ORS staff need both refresher training and support for enhancing the solution.

---------------- Page Z


> accenture

SOW_ 064 Office of Retirement Services - Intranet Enhancement Services

Project Objective/Expected Benefits The objective(s) and/or expected benefits for the services requested under this SOW include the following: 1. Enhancement of the SharePoint functionality

a. Analyze, design, build, test and deploy the following enhancements to the existing Compass solution:

1. Communication Request Intake Tool 11. Easy-to-use poll feature to solicit feedback (App Store Add-On) m. Marquee-style ticker for important news flashes that can be fed from a

list so that no coding changes are required (App Store Add-On) 1v. My Tasks Dashboard - An internal page personalized to each ORS

employee, listing all the tasks that are assigned to them, overdue and completed.

2. Javascript/CSS Training a. Provide hands on training to the Intranet Line of Business Group in:

1. JavaScript: Provide enough training to enable staff to customize special buttons and adding an insurance rate calculator on Compass

n. Cascading Style Sheet ( CSS): Provide enough training to enable staff to update background color, style formatting, color, font, and column size for widgets on SharePoint.

3. SharePoint Issue Resolution Training a. Provide hands on training to identify and troubleshoot issues with SharePoint

in additional to providing lmowledge transfer documentation. Defined scenarios of scenarios to be trained on will be defined in the Deliverable Expectation Document.

4. Implementation of a 6 month pilot ChatBot/Virtual Assistant prototype on the SharePoint technology

a. Improve agent's ability to find procedures, policies and answers by deploying a ChatBot/Virtual Assistant that will allow users to ask a search question to easily locate documents, staff members or other keyword searches

Scope of Work This Statement of Work authorizes Accenture to design and implement the following deliverables in support of enhancements to the ORS Compass solution:

(1) Enhancements to Compass Functionality: Enhance the existing functionality of the solution as defined in the Project Objectives

(2) JavaScript/CSS Training: Provide JavaScript/CSS training to Intranet line of business staff side-by-side training

(3) SharePoint Issue Resolution Training: Provide Intranet line of business staff to identify, triage and fix common SharePoint issues.

--------------~ Page 3


> accenture


(4) SharePoint ChatBot: Implementation of a 6 month pilot ChatBot prototype as a new channel on Compass to find procedures, policies and answers.


Prior to beginning each deliverable, Accenture will create a Deliverable Expectation Document (DED) that explains the structure and content of the deliverable and lists the specific parties responsible for completing each identified activity. The DED would provide sample templates, discuss the approach to creating the deliverable, and explain the level of detail to be included. This benefits ORS and Accenture by clearly defining agreed-upon outcomes for each deliverable.


Additional specific department standards remain unidentified.

Location of Where the Work is to be Performed Services provided under this SOW shall be performed in Lansing, Michigan, with some additional remote subject matter support provided to on-site personnel.


--------------~ Page4

> accenture




Work Description The State of Michigan and Accenture have developed this SOW to document the highlevel approach for the implementation. All deliverables will be coordinated with staff and leadership in ORS Customer Education.


If the changes described in this SOW are not implemented then the ORS Compass solution will not be enhanced to support ORS staff, including call center agents who provide customer service support to ORS members.

Deliverables & Activities

1.Compass Enhancements

2. JavaScript/CSS Training

3. SharePoint Issue Resolution Training

The following are activities that Accenture would complete or support ORS' staff in completion. The specific activities included in the deliverable will be detailed in the Deliverable Expectations Documents (DED) for Deliverable 1: Enhancements to Compass (SharePoint) Functionality Deliverables:

• Communication Request Intake Tool • Easy-to-use poll feature to solicit feedback (App Store

Add-On) • Marquee-style ticker for important news flashes that can

be fed from a list so that no coding changes are required (App Store Add-On)

• My Tasks Dashboard - An internal page personalized to each ORS employee, listing all the tasks that are assigned to them, overdue and completed.

• Provide necessary training for ORS staff and transition intranet administration and internal social media responsibilities.

• Document description and responsibilities of ORS intranet administrators.

• Provide hands on training to identify and troubleshoot issnes with SharePoint in additional to providing knowledge transfer documentation.

---------------~ Page 5

Deliverable 1: Enhancements to Compass Functionality

Deliverable 2:

JavaScript/CSS Training

Deliverable 3: SharePoint Issue Resolution Training

> accenture



4. SharePoint ChatBot Implementation

• Develop and deploy a 6 month pilot for a SharePoint chatbot within SharePoint

Deliverable 4:

• Identify key knowledge-based questions and answers that would be supported in the chatbot solution

SharePoint ChatBot

Work Plan

• Measure the effectiveness and associated metrics of the chatbot on the monthly basis

The anticipated performance period for this SOW is defined in work plan below.

Deliverable and Milestone Timetable Estimated Proposed Proposed

Descriotion Hours Start Finish SharePoint Intranet Enhancement Services Kickoff 1

. . 9/4/2017 9/4/2017

Meeting .

Deliverable 1: .Enhancements to Compass (SharePoint) 212 . .

9/04/2017 10/2/2017 Functionalitv . . .

. . .

Deliverable 2: JavaScriut/CSS Training 40 9/04/2017 10/20/2017 Deliverable 3: SharePointlssue Resolution Trainin2: ' 0/04/2017 10/20/2017 40 Deliverable 4: SharePoint Chatbot 360 9/18/2017 3/18/2018


---------------~ Page 6

> accenture



Responsibilities Resnonsibilitv Accenture ORS DTMB

Completion of Ae:ency Service Reouest Section of SOW ...; ...;· Completion of Proposal Response Section of SOW y Si= Statement of Work . y ...; ...; Issue Purchase Order ...; ...; Agree Uuon Project Resources and Schedule . ... y . . ..,;· ...; Prepare a Deliverable Expectation Document (DED) for each v deliverable Review and agree upon DED . ·.· .

·. v v Complete Deliverables as Defined in SOW y Participate in Deliverable Review as Defined in SOW . ...; ...; Document Phase Review Acceutance in Acceutance y Review Phase and Overall ProjectAcceptance

· .. .

y ...; . ...; Documents and Sign . .· . . . . . Provide Access to Resources (e.g., Business Experts, Systems, Software, and Hardware) Required to Perform y y Services

Assumptions 1. This Statement of Work SOW_o64- Office of Retirement Services - Intranet

Enhancement Services (''SOW") incorporates by reference the terms, conditions and deliverables of Contract No. 071B2200168 for the Enterprise Contact Center Maintenance and Support- DTMB/(State, Treasury, Civil Service) (the "Contract") between Accenture LLP ("Vendor") and the State of Michigan Department of Management and Budget Acquisition Services (the "State") effective May 1, 2012.


3. Actual services will commence upon execution of this SOW by parties, State purchase order issuance, and confirmed final project with agency, DTMB, and Accenture.


5. ORS will assign a dedicated point of contact for Accenture to assist with scheduling ORS resources and expeditious access to information.

6. ORS will provide facilities for up to three Accenture personnel working on this SOW. If additional space is needed, hoteling can be arranged. Facilities include: standard office work space, telephone, wireless (guest) internet access, and LAN connectivity - restricted and determined by ORS.

7. Building access will be controlled by ORS.

--------------~ Page 7

.

.

> accenture n

D Michigan Enterprise Call Center (MiECC) Statement of Work Authorization


8. It is not expected that access to confidential customer information will be needed by any Accenture contractor. Limited access to file sharing repositories will be accommodated.

9. Public access to the Sharepoint site is not required. 10. There is no federal tax information (FTI), Personally Identifiable Information (PII),

or sensitive data requiring secure methods and/or encryption is required. 11. Access to Sharepoint will only be granted to those with LGNET and/or State of

Michigan (SOM) domain access. 12. Agile framework will be used for Deliverable 1 as the method for process and

communication. 13. For Deliverable 1, ORS will provide comments/issues during the sprint review

meeting that will be documented and addressed prior to sign-off; Accenture personnel will be available during the review period for clarification and Sprint will be deemed accepted upon the receipt of written acceptance by ORS. Any item deemed deficient during the sprint review meeting will be corrected by Accenture and revalidated by ORS during the next weekly sprint review meeting.

14. The Chatbot implementation will be completed at no cost to ORS. 15. The Chatbot pilot will be 6 month duration.


[email protected] kristine.hand @accenture.com [email protected]

The Customer main contacts for this SOW include the following individuals:

Project Control and Reports Accenture will submit a monthly hours report to the Agency and DTMB Project Manager throughout the life of this project as part of the billing invoice. Accenture will also submit a weekly status report to the ORS Project POC throughout the life of this project.

---------------- Page 8

Michigan Enterprise Call Center (MiECC)

> accenture

Statement of Work Authorization SOW _064 Office of Retirement Services - Intranet Enhancement Services

Payment Schedule Payment for this SOW will be on a deliverable fixed fee basis. Vendor will invoice the State upon approval of each milestone completion.

Deliverable 1: Enhancements to Compass 10/2/2017 (SharePoint) Functionality 10/9/2017 $29,648

Deliverable 2: JavaScript/CBS Training 10/20/2017 10/27/2017 $6,300

Deliverable 3: SharePoint Issue Resolution Training40 10/20/2017 10/27/2017 $6,300

Deliverable 4: SharePoint Chatbot 3/18/2018 3/25/2018 $0.00

Total $42,248



Laurie Mitchell

Owen Davies

ORS Division Director - Customer Service


---------------- Page 9

STATE OF MICHIGAN

ENTERPRISE PROCUREMENT





$27,779,730.51

May 1, 2012 April 30, 2019


April 30, 2017

INITIAL AVAILABLE OPTIONS EXPIRATION DATE BEFORE

CHANGE(S) NOTED BELOW

5 - 1 Year



☐ P-Card ☐ Direct Voucher (DV) ☐ Other ☐ Yes ☒ NoMINIMUM DELIVERY REQUIREMENTS



☐ ☐ April 30, 2019


$268,000.00 $28,047,730.51

Effective with mutual authorization add funding ($268,000.00) to the existing contract to assist DTMB-ORS in the migration of the Avaya telephone system to the Cisco telephone system. All other terms and condtions remain the same.

[email protected]

Neil Slagle

Mike Breen

[email protected]

Julie Booth


ACCENTURE

*******2904

317-418-5062


(517) 284-7002

STATE

Pro

gra

m

Manager

Contra

ct

Adm

inistra

tor

CO

NTRACTO

R

DTMB-IT

517-636-4741


DTMB

DESCRIPTION

[email protected]

CONTRACT SUMMARY

n 0 z -i


ACCENTURE


Change Notice Number!

to Contract Number 071B2200168

517-636-4741 3000 Town Center, Suite 2400


DTMB-IT

~ - : •• I DTMB

-i 0 ;:a

317-418-5062

[email protected]

*******2904

[email protected]

Effective immediately resource language and person are replaced on the team supporting this engagement (see attached document) All other terms and conditions remain the same.

Description: MiECC is replacing the Siebel Lead Key Personnel role with a Cisco Package Contact Center Enterprise (PCCE) Application Lead and define in scope and out of scope for Cisco Contact Center software. Also, Pam Numerick's name will be removed as the Siebel Lead and as a Key Personnel. The new Cisco PCCE Lead is TBD.

Nature of Change(s):


Change 1.1, Update Section 1.101, In Scope, is hereby clarified:

1.101 In Scope

The contractor shall provide a team to support and enhance the identified eight contact centers. The contractor shall provide the following services:

1. Knowledge transfer from existing contractor. 2. Base Support 3. Major Enhancements (including new functionality or new contact centers) 4. Optional: Software Licenses

The State reserves the right to add contact centers, under this Contract through Contract amendment.

The scope of the agreement will consist of support of the following software components:

i. Siebel ii. Siebel interfaces iii. Sales Force.com (replacing component for retiring Siebel) iv. SalesForce.com Interface v. Scheduled/Ad-hoc reports (SQL). vi. Batch (from Oracle legacy extract to Siebel Base) vii. Genesys (CIM Platform, GVP, CTI - Gplus Adapter, WFM, Genesys reporting, Interaction

Workspace etc.) viii. NUANCE Speech technologies ix. FileNet Capture, FileNet CRM Integration Suite (CIS) x. FileNet Inbound Document Linker (IDL), VB script xi. New implementation of existing in scope technologies that are implemented under this

Contract which shall be agreed upon through SOW. xii. Virtual Hold Technology , only for DTMB/ORS (other Agency VHT deployment would be

considered Major Enhancement, and the base cost for that agency may increase) xiii. NICE recording and monitoring platforms, only for DTMB/ORS xiv. Integration with peripheral software, such as SYMON and Empirix xv. New technologies that are implemented under this Contract xvi. Cisco PCCE External CUCM (read-only) xvii. Cisco CVP Operations Console OAMP xviii. CVP Operations Console OAMP xix. Unified CCE Administration Tool (Administrator) xx. External Historical Data Server xxi. Cisco CUIC OAMP (Administrator) xxii. Presidio Custom Finesse Gadget xxiii. Cisco Package Contact Center Enterprise v11

a. Call Server b. Data Server c. Cisco CVP Voice Portal IVR d. Finesse e. Cisco Unified Intelligent Center (CUIC) f. Courtesy Call Back g. Post Call Survey

Change 1.2, Update Section 1.102, Out of Scope, is hereby clarified:

1.102 Out Of Scope

1. The business operation of the contact centers. 2. The actual operation of the program management office. 3. Purchasing equipment. 4. Infrastructure installation. 5. Purchasing software. 6. Providing customer service representative staff. 7. Providing contact center agent software administration (e.g., new agent setup, etc.) (the Agencies

shall be responsible for this with Contractor available to assist on temporary basis upon request and staff availability).

8. Providing Nice recording and monitoring platforms administration (DTMB shall be responsible for this with Contractor available to assist on temporary basis upon request and staff availability).

The following are excluded from the scope of technical support -

i. Hardware server support including the operating system ii. Desktop support iii. Avaya Switch iv. Data and Voice Connections v. Oracle/SOL Server Database Administration vi. Websphere vii. Xenos viii. Avaya vectors ix. T1 Trunk lines x. FileNet Image Services/PB xi. Cisco Equipment

i. SOM Non Agent CUCM Cluster ii. PCCE External CUCM Cluster iii. Non Agent CUCM and External CUCM Administrative functions iv. Dial Plan v. 3945 Cubes vi. 3945 Voice CVPNXML Ingress Voice Gateway vii. SIP Trunks (Centurylink) viii. Acme Session Border Controller (SBC) ix. SOM Cisco SME Cluster x. SOM Cisco Voice Gateways xi. Cisco IP Hard phones xii. Cisco IP Softphones xiii. Cisco Support Contract xiv. Wallboards xv. Integration to Real time Stats page

xvi. Unified CCE Administration Tool Agent Add, remove, Change, Delete xvii. Desktop Support

Change 1.3, the title "Siebel Lead" will be replaced with "Cisco Lead" throughout the Agreement with the exception

of Table 4, Rate Card.

Change 1.4, Pam Nu me rick to be removed as a Key Personnel and as the Siebel Lead.

Change 1.5, Update Attachment 4: Personnel Requirements is hereby edited/clarify with the following:

Cisco Lead: Experienced in managing Cisco PCCE or UCCE Contact Center Platform. Implementing, Configuring, Deploying & Troubleshooting Cisco ICM (Scripting), Cisco Voice Portal, UCM, Finesse Agent

Desktop, Supervisor Desktop, Call routing/CVP application design & development. ICM and CVP scripting knowledge to develop call routing & IVR application design solutions Trouble shooting Call routing issues,

platform issues etc. • Cisco Call Routing and Scripting 3+ years • Cisco Contact Center 3+ years • Contact Center Infrastructure 3+years

• VoIP 3+ years • Session Initiated Protocol 3+ years

Cisco Lead Task:

• Analyze business requirements, generate project specifications, and convert specifications into code, and develop technical designs in consultation with other technical experts

• Code Solutions following technical design and apply knowledge of computer programming techniques and computer languages.

• Develop unit test plans, test data and scripts for application validation and verification. • Perform extensive analysis and design working on projects of all sizes that require exposure to

all aspects of the project life cycle and creating and maintaining documentation in conformance with established standards.

• Work with application/solution architects to set direction of design and development for application development projects.

• Evaluate user requests for new programs or modified program components to determine feasibility, cost and time required, compatibility with current systems, and computer capabilities.

• Perform peer reviews of developed solutions and code to insure conformity to standards and design best practices.

• Review technical designs and specifications for completeness and conformance to quality standards, especially as a mentor to less experienced developers

Change 1.6, Update Attachment 5: Resume Template is hereby edited/clarify with the following:

Proposed Resource Name: TBD

Proposed Classification: D. Cisco PCCE Application Lead

Key Personnel: Yes □ or No 00

If resource is associated with a NA subcontractor provide name of company:

Percentage of time resource will 100% be allocated to project:

ACCENTURE

STATE OF MICHIGAN ENTERPRISE PROCUREMENT Department of Technology, Management, and Budget 525 W. ALLEGAN ST., WISING, MICl-llGAN 48913 P.O. BOX 30026 LANSING, MICHIGAN 48909


Change Notice Number 003 lo

Contract Number 071 B2200168

Neil Slagle

3000 Town Cent,a,, Suite 2400 (517) 636-4741


Jamie Walker Mike BteAn

517-862-0192 (517) 284-7002


······•2904

DTMB

OTMR

DESCRIPTION: MIECC to exercise two ona year options and add funding for base support and future statements of work, and add Salesforce capability via a rate card for Contact Call Centers. All other terms and conditions remain the same.

Rt.,-is«I 5J.<lf2016

NATURE OF CHANGE(S):

C HANGE 1 -EFFECTIVE J UNE 7 . 2016

Chonge 1.1, the following paragraph or Section 1.002 is hereby edited/clarified with the below:

Replace with: Tod•y, Mi_ECC supports contact centers at six (8) agencies (with respective sllbsets wijh\°n ageocies as

applicable) -1. Civil Service Commission (MCSC) 2. OTMB-Client Service Center tCSC) 3. OTMB-Office of Rotirement Servlcos (ORS) 4. Department of Heatth and Human Servioee (OHHS) - Ml Bridges IVR 5. Department of Health and Human Services (DHHSJ -office or Child Support (OCS) 6. Department or Health and Human Services (DHHS) - Michigan Statewide Automated Child

Welfare Information Syslem (MiSACWIS) 7. Talent & Eco11omic Oewlopment (TED) - Unemployment tnsu'rance Agency (UIA) 8. Michigan Oepanmenl of State (MOOS) 9. Treasury - Collections 10. Ti-easury-Tax Processing Bureau 11. Tre~sury - Michigan Guaranty Ageooy

Change 1.2 Update Section 1.101 In Scope Is horeby clarlfied:

1.101 In Scope The conIraclor shalf provide a team to support and enhane& the identified 11 con.tact cer\t81'$. The contractor shall provide tha following services:

1. Knowledge tram.>fer rrom existing contractor. 2. Base Support 3. Major Enhancemento {including new functionality or .new to11i8C'J ce-nlers) -4, Optional: software _licenses

The State n,$erves the right to add contact tentars, under this Contract through Contract amer1dmant.

Th~ scope of the agreement will consist of support of the foUowJng software com:pooe-nts: I. Siebel fl. Siebel Interfaces Iii. Salesforce.com' (replacement component fo, retiMng SiGbel) iv. Sals:.force.com Interfaces v. Scheduled/Ad-11!)(: reports {SQL). vi. Batch (from Oracle leg~cy e.xtracl lo Siebel Base) vii , Batch (from Oracle legacy extract to Sa!efo<ce.com) viii. Gene•y• (CIM Platform, GVP, CTI - Gplus Adapter, WFM, GeMsys reporting, loteractlon

Wori<space etc.) ix. NUANC~ Speech technologias x. Siebel to FlleNet PS Connector Siebel Event Actlon HOO<i]er (SEAH) xi. New implementation of exlsOng in scope technolcgles that are implemented under this Contract

'l>t1ich shall be agreed upon through SOW. XU. Virtual Hold Technology ' only [or .OTMBIORS (other Agency VHT deployment \'«>Old be

coMldered Major Enhancement. and the base cost tor that agency maY increase) xiii. NICE recording and monito~ng plattorms, only for OTMBIORS x!V. Integration with perlpheral software, such as S'(MON and Emplrix

i l i

I

}(IJ. New technologies lhal ere implemehted under this Contract

Change 1.3, Attachment 9: Agency Environment Information Is clarllled as per this CCN:

FOR THE CONTRACTOR:

Accenture LLP Ft m Name

Authorized Agent 1'8na\ure Jamie O. Walker

Aulhorlzed Agent (Print or Type)

le

Attachment 9-: Agency Envh:o,turuent l.oformation

FOR THE STATE:

Signature William Pomble, IT Division Director

Namemue OTMB Procurement

Divis.ion

Date

Contact Centers ff Technlca1 Descr(ptlon - jn alphabetic.al order TIM:l descriptions represent the applications as they are al Contract exeQ.lt!On.

1. Civil Sorvice Commfs$ion

Overview The MIHR contact center could be described as a mo•tiY •out--of-\he-box' Slobel Coowct center 7 .8 configuration. There 1$ a cus tom-coded Websphere Applicalion Se<Ver (WAS) knowledge base. There are 30 Customer Service Repre'sentaiives on tl1e phones, receiving approximately 500 calls per day, and -up to 5 start who act as tier;? agents .dealing with service requests. In 2015, the CMI Se,vice Ccmmission and OTMB lmple(l1ented an IP based IVR and contact oen.ter. ·n,e contact center solullon was lmplemonted on )l\e OTMB MIECC Enterprise ConlJl,t Centet ewironment in tho State of Michigan hosting center. The teclmology p!attorm used was a Session Initiated Protocol {SIP) based Genesys Contact Center. MiECC services to the CiVU Service Commlssion la suppqrting Jhe on premise G...,esys platfam,.

Sjebel Curre)111Y, lhe Siebel base tables are updated via • se,ies of custom programs on a nightly• bas!• with key d9..ta provided by output ftl"'3 from \he HRMN system. This process updates the Siebel Enterprise Integration Manager (EIM) tables using Perl and Java s,:npt programs. The Qperational Data Marl (ODM) Entorprise Application Is used to store employee, company, location, tran!;laticn, department and Job code In QOM Database and also used to upload data to I)1e EIM tables in lhe Stebel Database. These programs allow only o/langes p,ade to the employ•• data ·1n the post day to be passed through to the Siebel EIM tables. However, ono<I a month, a program comple(ety refreshes an employee data in Siebel. This proce:sG a!so lnclvdeis a dir.ec-t-insert inlo a Slabel base

table.

~novAedge ttase

The content owners en\er content Into a Vigne\le 6 projec-t. Content changes· are migrated through a two-step process to the WAS applicatl0<1 server lhat stores the content In XML fa1mat Content is aocessed through the Internet by St.ate employees. Acccso c,edentials a,e captured by the login page and passed lo a Lightweight Directory Access Protocol (LDAP) drectory for authentication.

Telephony Employees calling Into the contact center a,e initially p<ese,,ted with several telephone menu choices. The contaci center use• computer telephone integration (CTI) wherein employees may enter their employee ID or ooclal seairity riun'1be( and using Gene&yo tl,e information la paosed as a screen pop to lhe CSR In Siebel witt, the empk>yee information .contac1 log auto popuiated. Incoming caters who ldenffl'y them~s as wanting employment vertricaUon, arn in need of sei sennce supp0<1, or are retirees of 01e Stale of Michigan wlll select those options and that v,jll auto populate in Siebt;,I with a predefined c1,.1stomer contact rium~ar.

eMail The Ml HR S..vice Center processes approximately 500 ema)ls lrom three email alias. Auto acknowledgements ore sent and then emails are captured and worked through the Siebel applicaUon using a series of predefined respooses. Contact logs a.re generated in Siebel for each email serit and received.

Hardware There arc 3 hardware environments: production, test and d;-evelo~nt.

~ Management use reports r,om Qwest, lhe Avaya CMS system NICE QA report•, Access and Excel tracking reports and customized (aporls from Siebel.

2. PTMB•Cllent Service Center (CSC) Overview

film The Inbound 1-800 and ioc,,J call• termin•t.• on the Gapltsl swttcll. They are routed to Gane•ys for proces,slng,. As a.n emergency provision. vectors have been written that, if Ge,nesye is no\ working, the calls ~r0 routed to agent$ using ·a aet of Avaya vectors.

Q~nesys Genesys pro1Jkleo the IVR, SC#'eeo pop und coll routing funCtionallty.

The lVR takes call& from the switch and routes via varlous menu options. The caller is asked for his/her employee id ,iA'llch foJm.5 the basis for the sCfElen pop. In one scenario, the caller may choose to perform an automated network passwo«i re~el In ali othet scenarios, the: call IS routed using 6k1Jls-based ro01.tng ~o the rnost appropriately skilled agent Al the same flme, the employee id lool<up occurs In Microsoft Active Directory for the State of Michigan Domain. If a valid eInplo)'<le id has bean provided, th<>n information pertinent to the ID (identifying the caller} is provlde.ci in a 6c«l&O pop to the agent This Information is uGCd by the agent to search Remedy for caller infqrmation, exicSling cases or to &1$11 a oeW cese,

Genesy& creates the virtual call center. Gene:Sys lntera"Ction Workspace (tW) is used as the client appication for the agents. CSC tier 1 agenls are localed p~marjly In Lansing and Detroit. Additional Field Service oga,its use IP Soft phone technology to access the Ge,Jesys system through the Capital switcll. Tl<;r 2 staff Is located ot the Operatlons Center in Dirnom:tale, Ml.

Interfaces Automated nahvork pasS-\VOrd re-sets

When a caller choosas to use ~ automated networl< password re-set option, he/she has 3 chances to do so ,uocessfufly before being rooted to an agenl If routed to an agent, then the agent accesses an eJ<isling Chaiie,,90 RespO<lGC System (CRS) database for questions and _ansviers specific lo the individual whom the cal!er purports to be. If lhe caller answers the questions accur~y, then the agernl uses adequate credenll.als to change tt,4) password on the associated accoonl. A ticket is generated and closed to document the

-tran•acilon. If any oomplications cccut, SllCh as nc data kl available ill the CRS, tllen the agent •NIii refer tho caller to an authorized requestor1or valklatio11.

If • caner has previous.ly registered a PIN in CRS, then automated re-.set can be successful. In Utis case, lh& caller is asked to enter !he numeric 4 digft PIN. The HRMN 10 and PIN are validated in CRS. If valid, tllen the proooss continues with a Positive status being sent wilh the HRMN ID to Active Dire~lory. The netwO<k aocow,t assoctated with that HRMN ID has its pas$word re-set. The catle( is told of the successful transaction and e nG\\' password. Additionally, data Is wnt lo Remedy to document the re-set. Based on the MRMN ID, also slcred in Remedy, the ca~e is opened, documented as a successful netVJork password re.set and resolved. The Remedy syetem automatlcall_y gen1;trates an ~maH to the associated email of the account of tha re--set.

The Genesys system Integrates With the Symon Walll)oard for displaying of corlael center stnlisllcs that includes queue level statistcs.

ttardware There are 2 hardware environmern.s: p(Oduction and test.

~ Genesys CC Pulse will be used for reaJ..tirne viewing of etalistics for all virtlJa1 call queuas, agent statistics, 9roup statistic.s, and queue votume a?erts. Gencsy.s CCAnatyz.er \~fl be used for ht!3lo1ica! reporting for an routing polnts, call queues, v;rtual call queues, agent statistics, group statistics, and Ctistomer per&onaJization can tracking statistics.

other Rapons Th&re are several other solH-eBS used to suppty manag·ement with operational and strategic daja about the contact center. They include Avaya CI\IS, CRS and Remedy queries.

:i. DTMB-Offlco of Retirement Services (ORS)

OveNiew: The ORS contact center has Siebel as the core product with significant functionality also supplied by Genasys. and Avaya components. At peak, there are over 50 customer service ~ente o.n the phontt \!lith ;mother set of agents answering non-real tJme work iletns on Siebel. The currant estimate of <laity call volume that will use the 1-800 numbers is in exeess of 3000 calls.

~ The Siebel appUcation uses mostly the out-of--t:he-box functionality t,001 the Sieb.t,l Enterpri~ Contact center 7.8.2.16 produol. Conrad and Organization iniom,ation In Slebql, refreshed from the C!are.ly every night. Is vsed as the main person identifier and forms the basis for lhe screen pop at the CSRs desk.top when they reC'.eive a coll. Clarety Is the Line of Buslne5'\ (LOB) Web application used by ORS to support Membernhip and Retirement J)t'otessing, Siebel is used by staff to track communications with Members and Organizations. as well as to creato and track lnteraclions/Servlce Requests (AClivltiesmckets). Calls that cannot J>e anowered by a lior 1 agent are transferred to a tier 2 agent.

Siebcl~Claretv GUI Lin~ Siebel has secure connections to view the backend ctaroly system for contact center agents. The type or lnf9<mal1011 Siebel can quory in Clarely Is related lo FlleNet images, benefit Information, demographic and

work$1te infonnation.

As a front-end CRM sySlom, service raque,t may be c,,,ated in Siebel. If tho work requires lransaclions to be comploled In Clore{y, lhese requesls are created In Siebe(.~ work originated In Siebel may also ba enforced with Service Level Agreements, Prioritization Criteria, and/or AasJgnment and Due· dates prior to being passed to Ctarety. Updates to vton< statu$0S are Passed back from Clarety to Siabel in reaMrme.

Siebel \l)rtual Business Comi;-0nenls Additional dafa. elements originated and owned by Clarety are readily avQilable to agents working ir1 S!~bel. This Is accomplished by "'"19 a numbar of mechanisms including Virtual Busi,,es& Com1>0nonts ·and Smart (oontextaware) Links. Toe purpose is net lo replicate all data, but to make ii readily availel:>le in bolh systems. Virtual Bus.lne$S Components are read-only via•HS providiog access to real-time Cfarety data using Siebel.

i I

I

T etephony Call fjow: Calls ooming from the 1-800 Qwest T1 tioos terminate on the General Office Building (GOB) switch. Avaya PBX difecis customer calls to th• Genesys IVR where callers aro provided with self-service opportunities such as the Member A;,plicaUon Status transactions. Callers wlslllng to talk 10 a,, agent can opt o<~ of the IVR and ore askod for their ID, which is used to screen-pop the customer's inforfYllltion on the CSRs desktop when the call is answered,

G&nesys: Computer Telephony integration {CJll ORS' telacommunlcatlun• applications improve Agonl efficiency through the uso of the SlebeHntegroted Genasys CTI and Ge,,,..ys GVP (Genesys Voice Por'.al). When ORS customer~ call, they aro routed through Ille IVR and prompted to enter idenlifying lnfonnalion. This information is tnen procellsed by Genesys (CTI application) and produces a "screen pop" within S~bel, which aGsist the Agent In idenlifying the custorne,. Ag·en{$ are also provided With Oenesys soft phone toolbar capabilities in order to control call activity rrom their

PC desktop.

ORS employs the Genesys 7.6 ERS Framework components In combination with AES, Gplus Adapter, and Slebel communlcaUons Sarver in order to de!iVer •scrcon..pops~ to Contact oenter agent$ using Siebel. This set of functions draws data from the Genesyo GVP (Genesys Voice Portal) 48 PM IVR units conM<>ted to the existing ORS distlibuled Avaya Oefinily PBX/ACO switch.

I/HT ORS Is cL!llently Implementing VHT for the !)Qntacl center operations.

NICE svslem: (Mooltoring and Recording System} ORS U$GS the NICE Perform 3.1 Application Suite as its ~igital multlniooia monitorjng and reGcnding solution. Th1$ hardware lnciudes a NICE Logge.rfor Voice Storage: Screen Capture and Logger for navigation recording; and the NICE Call Logging System (CLS) for storage of call details. The $oftware components include NICE Univ<>rso, Sclleduler, Forms Designer & Lisi Edit0<, Evaluator, Monitor, Web Reporter, and Reco,d on Oemand.

In order to gather busioeos call details 1h•t are not prQvided by the swilch, the NICE Systems are integrated with Gonosys TServer to obtain the oota rrom the IVR.

llYm. The inbound 1-800 co~• terminate on the Avaya PBX switch, They are rooted dep;,ndlng on the Dialed Number ldentllicsfion SW!tcll (ONISJ number to difterenl vedors 81\d then, whore approp11ale, adjunct routed to GenesyO'. How.ever, the vector.. have been written· that, if Genesys does not pJck up the calls In a oertaln period of time, the ca\ls ,are routed to agents using a set of Avaya vectors. ·

Leg:$y !ntertaCO: Slebol EIM- Enterprise 11,,tegralion Manager. EIM is used to t,,;ng data fro1n Legacy "ystems (Clorety) and other sourcas into temporary staging tables, where business rules are applied before the data uploads or updates

Slebei-reaidont data.

EAi - EntetpCise AppUcalion Integration: EAi ls used with ·siebel to U:nd or receive real-time update$ from other applications. At ORS, EAi is used to send and receive r,eal-time updates bet\veen Siebe! and Ctarety.

Micro.son SOL Server TransaclicnaJ Replication.: •A subscriber database U$8S this mect,anlsm to rece-i.ve syoc.hrol1¥2.ed data from Clarety, and the data is then pormati1:ed or de-normalized ·to Siebel'is required format,

·Siebel Wmk.flO'N/Business SeNicea/HTTP l>ost Method: The .oon'lbination of these mechanisms Is currently used to send information Insert• and updates from Siebel to Clarety.

Security Integration: ORS currently uses authenticalion ,n<,chanisms external to 'The $)"$tern" (Clarety and SiebeQ. Both applicati.ons are setup to use a common LOAP (ADSI) server, allowing for common auu,entication. Transactions botweer.i these appllcaUons use header authorlzatlon acquired from the LOAP

server.

0th~ Data Source

V irtual_ Business Components ore read-ohly vieYJS prnviding access to real-lime Clare\y da1a using Siebel. 'VBC :Vie\\/$ In the contacts business object pull Jn/om,ation from an outside source (Ctarely) using a VBC connectioli. vac connoclions are ~o a SQL SeNer database that stores Member information created by lho Clarety System,

Hardware Tll<lro are 3 hardir(are environmenis: production, OR/lest and UAT/developmenl

Reports Ge~e~ys CCPulse ·Is used fO( real--tirne viewing of st~tislie& for all vir1ua1 call queues~ agent statistics, group stabst(cs, and queue volume alerts. Genesys CCAnalyze< will be used for historical repot1ing for aU routing point$, ~ queues, virtual call queues. agent statistict, group statistics, and Customer personalization call tracking staiis11cs. Genoeys VAR is u.ed for IVR reporting.

o u,er Repo1ls There are several other sources used to supply managermmt with operational a.rad strategk: data about the. contact ce,ter. They Include Qwest, Avaya CMS, Siebel Actuate, and SQL Queries.

WOO(fo,ce Management Svslem ORS us.es the Genesys Wolkforce Management ApplioatJon Suite to forec~sting, employee ·scheduling, monitoring of re$.1-tlme agent-adherence and intra-day- contact•center pertormance. The software components Include Genesys Web/Supervisor module and WFM Conligc.-eUon Utility.

4. Department of Health and Human Services (DHHS)· 1111 Bridges IVR

OVervi!O.:CI The lll'Chiteclure of tho Ml Ejridges / IVR system Is an n-tier design that separate• the appli<:atlon into tiers or layers that are architecturally Independent of the other. The Ml Bridges/ IVR system consiols ol a presentation tier, business logic t!er and a persist~nce tier.

Presentation (Web) Tier Also kno\lln as the Web tier, ot presentatk:m layer, this governs what the usem see at their workslation, but In case of th• IVR ii govern• what users expertence on the 1elephone. A HTTP satver hosts the dls,:lay interface. The developed Graphical User lnte!lace (GUI) must be compliant with tile Ame<ieans with.Disabilities Acf (ADA) and is geared to t110se of va,ylng bact<grounds, languages and sklB levels. The Web tier for Ml Bridges and tVR ta Gpocific~lly dev1\oped to capture informatton

1 not prooess it It allows information to pass through it to the

Business Tier~ or application layer, w'here mu!ll-()18 proces-eO<S stacks route the da.ta aod link to data.

t}utiness. ner The Business Tier tS the 1ayer wtw,ra business k>gic is run. The processing for check my benefit$, apply for benefits and report my ch.anges is performed witt1in ttle Business Tier. Thi• layer is 1he most critical to Iha soluli()ll and i• broken apart from the Web lier to allow tho State to grow tha application compone)\t of lhe solution as needed wilhout Jntelforing with, or having to rebuild, the front end-tho

Web tier. Developer tools, SUGh as JBM Rational Software AtohilccVMo<lelcr in combination wilh J2EE oxecu1ilQ on IBM WebSphe<e Application S~rver provide ready-to--uca application component., that would olhetv11sa have Lo be custom built for Integration. Isolation aod integralion a:re key elements of the overal.l &0lution.

Persistence (Database) Tier . Tho first t\lio l ayers of ij1e eolullon act like separate components of I.ho overall 60Iution that <>nable specific actMlies to occur before altovi;i ng the user to acces'!; the database 1tvhero sensitive data resides. The Database Tie<;, designed to provldo the Stal• added security. It.uses port 15:11 for Orecla or as defined.by \he technical requirements and is .hosted in Zone 3 a very highly secured environment. Roles providing access to lhe appljcatio:n are built into the Ml Bridges system. The database environment, wheire data is re~d, updated and proces$ed accordlng to the busines, rules configured for operations. is accessed a:!ter a setios of approvals and processing functions occur within the previous two layen. of the system, Stored procedures and triogers within the Database Tier enab)e rnass updates, deletes and other opa-ratk:5n& to occur quickly v'/llhin thi1> layer. Theoo

are defined as a oom·ponent of the application logic. The oracle database component Is necessary to provide lh8 premium processing capabilaies required by. the State.

Ml Bridges !YB Software ArdjlJ&clµre:

The Ml Bridges IVR app1~cation includes software that resides on standard de,sktops onct servers. Exampfo$ of the desl<top compooents Include:

• Microsoft Windows XP, • Microsoft Internet Explorer v5.5 or later (Secure Socket Layer (SSL) enabled wltll 128-btt encryption) • Compatible wiU•1 FirefJ>x, .Chror:ne and Safari browsers • Adobe Acrobat Rea-der 8.1

Saryef:§ide sortware components include' • sun Solaris 10 Operating System • Microsoll Windows 2003 Server Enterprise Edition Operating System • Ml Bridges IVR application • Genesys GVP application • Oracle Database 11.2g Enterprise Edition • IBM WebSphere Appication Server, v 7;0 • IBM HTTP Server, v 8.0.2.31 • IBM WebSphere Busln~ss hi tegratlon Software, v 7.5.0 • Novell eOirectory, v s.a2 • Informatica Power Center v 8.1.1 • SAP DQ XJ (for address verification)

!221 Support S8JYers Tool support servers tt,at are Windows based have dual 3.4 Grlz/2M8 Cache Xeon proce•sors and 70 GB hard drives. Tho fonowing servers ih the indicated environments reqtdl'~ 2 GS memo,y:

• FAST4J ioo1 Server ror Development • Ralional Tool Server for Development

The following servers In the litdicated environments require 8 GB memory: • Build Woo<stauon attaclled to the SAN

Tl'le Rational data server rMldae in the Developmont environf'nCnl and 1s a Sun Fire \1240 with dual SPARC Ultra Ill proceMors and 32 GB msmory.

~ OTMB and OHS utilize both Dell and the Sun family of ·servers ior Ml Bridges tVR project. For each server, different configuraOOfls of processors and memory are required depending on the environment In which It resldes. /iJ ~ivet& are updated to the rnost recerit patch level requi1ed by the hardware contractcr and conlaR"I the necessary anti .. virus softtA--are as defined by the State. The Sun Flro servers, with lha exception of the X4100, run theSola,is 10 operating system. The X4100 run the Windows op0raling syotern.

Virtuallzation • State's Virtual sewer farm is used to host Virtual Machines (VM's) for Ml 9cldges Web servers a,id Ml

Bridges App!lcatlon servers. • Capacity of VM's In the Virtual SeNer fam, is fed by muttlple ph)'$1Cal servers. • SUSE Linux 10.2 Enterprtse is tlio OS used in the VM's. • VM's tor Web/Application ee,vers reside in Application DMZ Zone 1 .49. • Browser requests for Ml Bridges •ro routed to • CISCO Load Balancer which resides in OMZ Zone 1 fol

Internet Access. • Multiple VM's 1,1sed by Web and Appllcation servers tor both Production and OR to achklve Load

Baianclng/Faik,ver/Oisaster Reoovery. • System upgrades/maintenance dor)e on the feeding physlcal servers one by one in the virtual se,ver

fsnn. No doWTltime ~ue to VM Mmion, • Oompuware Vantage is ueed to monitor VM's in addltion to other Ml B1idges and IVR servers.

• Each of the Web soIver VMs has 1 GB of RAM an,J 1 v<;;PU ("I Virtual CPU Core): this can be incremied based on stress tasting and capacity planning.

• Each of the Applloatlon server VM has 4 GB of RAM and ~ vCPU (2 Virtual CPU Core).

SelfMServtoo and lyR Networking Infrastructure: The Ml Bridges and IVR application ls accessed via a wide-area TCPnP compliant network infrastrue\ur$ lhat Is provldod ond mafntalnod by the State. The Infrastructure includes firewalls, fiber connections, telephony ports, SAN connections, workstation LANs, project me systems, etc.

Ml Bridges and IVR physical e,wlronments housed within Stale faciDlles and use the exisUng State oetwork infrastructure. Thus the archlte<:lure depends on this Infrastructure to be the primary channel to deriver the Ml· Bridges anQ IVR application 1o·usars throughout Iha S)are.

Network monitoring services for the Ml Bridges solution ls provided by lhe State ai>d includes trouble shoollng assistance and reporting ai needed. by the project.

Jelephony Gateway lpfrastructure; Toe T<itephony Gateway Infrastructure consists of:

• TelephQny Provider (Qwest) • Gateway • IVR Servers • IVR Management Se,ve.r • IVR Reporting Server

A call flows from the Telepllony Provider (Qwest) to Ille IVR Server lhroogh the Gateway. IVR servers are controlled by the Management seiver. Reporting server taKes Input,, from the !VR application and the IVR aorvers and reports the eame In ~ user readable format

The MIECC service to DHHS Is 11maed lo maintaining the IVR software (Genesys) architeclu,., and support . the IVR application and the web application are maintained by OTMB With another partner contractor.

6. Department of Health and Human Service, (DHHS)- Office of Child Support (OCS):

In .20·14, ihe Office of ChJd SuppOrt and DTMB Implemented -.n IP ba~ed IVR and oontoct canter. Tile contact center sotutlon was hr,plemehted op. the PTMB MiECC Enterprie.e Contact Center environment in ths State of Michigan hosting center. The technology platform used was Nuance Speech Recognition and Genesys Contact Center. Toe Office of Child support agents aro mosUy re,nolo agents oonnectod to tho State of Michigan virtual -private network, Mi-6:CC services to the Office of Child Support i:s supportiflg the on promise Nuar«-.o and Genesys platiorm.

6. Oepartmenl of Health and Human Services (OHHS) - Michigan Statewide Automated Child Welfare

Information System (MiSACWIS) This solufion Is an IVR being deployed for ih& OHS SACIMS projoc!. The MISAC\1111S IVR is a Nuance developed IVR application deployed on the G""""ys Voice Plattorm. Additionaay, Nuance Vocalizer (TTS}wlll te deploJed for playback of dynamic caller d:ata (i.e. names~ ·rhe existlng·GVP coli\.P.Onents within \he enterprise· platfo,m will be expan(jed to handle the new call volume into the platform. Tho Sf-CWIS IVR project wlJI provide a self-seNice IVR applicallon fo(the roster parents lo '"rifY the date• when fosti,r children were ~, theit care and trigger payment for ihese services.

7. Talent & Economic Oevelopment(TEO)-Unemployment Insurance Agency (ULA) Qverview In 2013, TEO--UIA and DTMB implemented a contact center on thoo MiECC Genesys enterprise pla1lonn hosted in the State of Michigan DTMB t,osttng centc>rs.

Genesys

The Ger"'6ys platform provides interactive voice response (lVR) configured to uiilize prompts and rules to aJJow bacl<end data dlp Integration for self-service. IVR error handling a.1<1 global tw,ctlonallty, utilizing standard numeric operations (press 0, or pre&s 9 to 90 back) Is incorporated into processing. The Genesys platform is also integrated to the TEO·UIA Fast system for CMG creation and account screen pops.

Hardware There -are three hardware environme.nt&: production, test and development.

ft§P..211l TE0-UIA use the MIECC enterprise environment for rej)Ortlng on contact center data. Data such as real time and historical call report• are provided by the MiECC Enterprise environment

MlECC services to 1EO-UIA Is supporting t~e on premise Genesys plattorm.

8. Michigan Department of State (MOOS) Overyiet,: The MOOS contact center has Siebel as the core product wtth significant fllncllonality also oupplled by Gonesys end; Avaya oomponents. At peak, there are over 70 customer service agents on the phone with another 10M15 agents answering non-real lime work 'Items on Slell<ll. The curlef\t ostimate of daily call volume thn\ will use the

, 1 .. 888 m.rnber is in excess of 10,300 calla. 'There may be up to 10 concurrent eServioe users from the branch offices usJng .the sys.{ell"I to a-eate or review service requests.

Siebel The Slobel appllcatlon uso& mostly the out-of-lhe-bo> functionality from tl>e Public SeclOr Contact center 7.6.3 product. Driver and vehicle Information in Siebe~ refreshed from lhe mainframe evory night, is u,ed as the mai,1 account ide1,tff!er and fonns the basis for the screen pop at the CSR~ desktop whe,n they receive a caO. Calls that cannot be answered by a lier 1 agent are transferred io a tler 2 agent and, If u,e call can still not be answered satisfactorUy, a service request ls created. Serulce requests are worked by oonMphone staff and, after eompleUon_ the tier 2 agent calls Iha citizen bacl< with the resolullon.

There is an eSeMCe applicat!oo that allows branch office staff• and other work uni\s in MOOS to login to Siebe\ and create a service request. S'1.ibsequen11y they can also usa the application to review tho Gtatus of their service request.

T e~p!JQOC Call Flow . -cans coming from the 1-888 Qwest T1 lines terminate on the General Olflce Building (GOB) switch. There are two types of calls: one cO<Tling from a cltlten and the other from branch office MOOS staff. Bro~ch office s.lllffs use a 1~77 number and this allo\VS Avaya to differentiate the calla<s.

An Avaya vector directs citize·n calls to the Genesys IVR wtiere cal!e<s are provided with various self-service opportvnities.. Catlers wlshlr.g to talk to an agent can opt out of the IVR and are asked for ttleil Drivers Lk:ansa Number, which is U$ed lo screen-pop the citizen'$ information on the CSR1; desktop when the ca11 ls answered. Note: A sirriilar fl,lf)dionaJity exists for vehicle re,gistration number.; however this funcllollality Is currently turned off in the fVR due to the S)"'lems inability to accurately recognize alpha cl)aracter&,

Calls coming from branch office staff are directly routed to lier 3 agents aft8f using a Vector to caplura Iha employee 10 number and a branch kfenOflar which le u&ed to create a screenMpop o:n to an agent's desktop.

G:9nesye Genesys provides the IVR, soreen pop and caU rouilng functionality.

The IVR takes citizen calls from the switch and routes tho olll2en through vartous selr•servlce options. Thero are many points whe<e lhe caner can opt out to speak to an agent. If the caller chooses to opt out, Genesy~ captures \ih\ere opt out takes placo and makes a detennination, based on 8 series Of business rut.es, ,w.ich tier 1 aoei:it skill level is required to an:;.-wer the call. The call is routed using skills-bM8d routing 10 the most appropriately skilled agent In the process, the caller is asked for their Driv..rs License Number which forms the basls for the screen pop. Scansott speech recognition softwal'EI allows the c:iler to speak this number. At the

same trne, a data dip ta~•• place Into the Siebel database to determine ~the caller alre.ady has an open service request If one exists, G&nosys routes the caller past th& l ier 1 agent s!Jll19ht to~ lier 2 agent queue.

Genesys also picks up the branch office staff calls from a veclor along with the collected employee ID number and routee thG.t:eto a tier 3 agent queue. Tier 3 agentsreceMng the caY get a screeo pop of information related

to that branch office employee.

Genesys creates th& virtual coll center. CSR tier 1 agents •re localed in both Lansing (GOB switch) and Detroit (Delrojt Cadillac Piaoe switch).

~ The inbound 1-888 oalls tem,lnat8' on !he GOB switch. They are ro>Jted depending on lhe Dialed Number ldanllflcation Switch (DNIS) number to dlffernnt veclors and then, where appropriate, adjunct rout•d to Genesys. However, the wctors have been \vritten that( 1f Genesys does not pick up the calls in a cei1ain'period of time, the calls are routed to agents uoing a est of Avaya vectors.

Legacy IQterfaces Mainframe The MOOS mainframe inWface is similar to that used by r reasoiy. The Databricge product is used to extract audit files from \he mainframe and place the data Into Oracle tablas. PL/SOL statements are used to populate Siebel Enterprise Integration Manager (EIM) tables, Finany a Siebel EIM configuration file ,lfb file runo and

populates the Siebel base table,,,

A series of1'o1 keys" h;we been·creatad to tmport specific information from the mahiframe into u Siebel ~pplet using a .Net connector, The lntonnation coming through the connector Is not stored in Siebel

Other Data Sources Some views In the contacts business object pull Information from an outside source using a VBC connection. One V8C connection is to a Microsoft A/Jcess dot~t>ase that- stores a record of letter correspondence generated in MOOS and sent to citizens.

Hardwate There al'u 3 hardware environments: produc!ion, test and devek>pment.

~ Genes-ys CCPulse will be used for rnat .. urne vlevlin_g of statistics fl)r all virtual call queues. agent statislios.. gro1,1p statia&s, and qu8ue volume alerts, Genesys CCAnalyzer wifl be used for hlstorical mporling for all routing points, call queues, virtual call queues, agent statistics, group statistics, and CU!stomer personalization call

tracking stallstt.cs,

Other BePt".lrts There are several other sources used to supply ma1'\agement with opera.Uona.1 and strateg\c data ebout the contact center. They inclµdo Qwe~. Avaya CMS, Siebel Acl1Jate, and SOL Queries.

9. Yroasury - CoUecUons, TalC Processing Bureau and Michigan Guaranty Agency

OvefView' The TreasUry contacl oenter has Siebel Contool conter 'l.8 as the core produol, but slgnificar1I funcUonallty is also supplied by Genesye, Avaya, NICE, FlleN~t. Tidal, Opalis and Xenos components. Although CSR• are on!y on the phones between 8:00 am and 4:45 pm, Monday lhrough Friday, tho IVR and Siebel aServfce for taxpayers is available 24-x 7. At peak, t}lere are over-40 customer servic.e representatives on lh11 phone with pnothor 180 a-faff working non-real Ume work items on Siebel. The annual ci>nttlet volume (all channels) is in excess of 2.2

milllon contacts. The support team provides l>raaklllx response and more romial major &ci»duled reloase updates. The business us:er maintains some administrative tunctions within Siebet

~j~~t~ls fn aU channels {phone, IVR. web, email, VJtijte mail and walk .. ins) are recorrdod in Siebel Contact center 7 .8. Most telephone contact log$ are cre.ated automatically by the system with agents choostng a reason and

resohrtlf,n cede combination rrom a drop down lisl Siebel populates the retison and resotution c.od~s for rvR and scff.secvlce. web contacts.

Non-feal time wotk \teins are created automatica!fy through the Inbound correspondence channel or via the Siebel eSorvioe access by tile taxpayer. Manual service requests can be created by any agent Toe Siebel Communication tool bar control$ the agent's access to real time work items.

Taxpayers can .sign into Siebel eServioa from the web to vfew account status informi:ltlon and create a service request. A secmty adapter has been bunt wllh Ille help of Siebel to racllitate ihe • uthcnlical lon proooos. The Siel)el eService application also has front-end tables built In that allow business user analysts to change <»rtain responses such as the estimated date when a specific taxpayer's reflJll<I will be i~sued.

The contractor is responsible for monitoring Siellel e-<1ervlce site functionality 2417.

FileNel x~nos i$ used to capture print lites an<! enable outbound corTe&pondence to be stored in FileNel. Images are created ror 1,arious classes of docum.ents: lnbOund correspondenoe, outbound cormspondence, tax retum$ and regfetration forms. Treasury staff access FlleNet lt1!'ough Siebel or direc.lly through FlleNet Each document class ls treated differently for creation and routing of service req4ests in CRM.

a. Inbound Correspondence lritlound correspondence Is batclled for different Treasury wOfkgrcups and scanned. Images are Indexed manualy with the account number that ia vorifiod with a look ah<>ad Into the $label database to Insure tl\G aooount exists ln Treasury·e CRM database. Documents that are difficult to code are held open in FileNet and routed for indeJ<ing to separote groups of Subject Maller Expert&. Once all dOCUmento In a batch aro ~xOO, the Images are.then committed to File Net Image services. A Ust of the images goes to the Siebel Event f\cllon Handler (SEAH) component that has been configure<! to create an u,bound Siebel contacl log and, when appropriate, an open Slel:J<!I service request. The Treasllry legacy system requires notification of the receipt of certain classes o/ inbound mail and, the<e!ore, a file is created in FiloNet and sent dlrecUy to thal system. Once Inbound correspandence service ~quests are completed. Siebel creales a doily feedback to several legacy systems including TREAS, MARCS (the colle<:tion system) and

SAP.

b. Ou!llound Correspondence There are two routes for importi119 outboulld co«sspondenca into Siebel. i. Ou,tbound correspandance that is PfOduced by the ta>t legacy systems including SAP has been

identified by the buslness to be stored in AleNet and altached to Siel>el as ~n outbound contact. Xenos is us.ed for this !'oute and It captures the print Hie f01 each type of outbound correspond(l)nce and, bas0d on pfe-built templates, parses out some key data to create an tndex and stores the <Jocument Image as e tnr file. Siebel Event Action Handler (SEAfl) component linl<s the Image to the Siebel account and creates a Closed cootact log.

ii. outbound corre:spondeflce that is in the forrn of a Wo<d document {not generated by legacy sy$tems) can bo attached to the contact togtservfce request 0 1l an individual basi$.

c. Tax Returns The indexes of tax r'$hrms ar& stored in FileNet and m3de available to staff desktops via a RleNel Images Service& look up or through Siebel CRM.

d. Hlstorica\ly Seamed Oocumenjs , Oti1er documents (usually those wijh prlon1y hand~ng) are woti<ed by CSR's Qnd th..n imaged as hlsto!lcal documents tn FlleNet. Siebel wo.rkflow cro~des a closed oontacl: Jc,g !inked to the rels.ted CRM account ,inth the appropriate reason and resolution codes tor hist<>rical lmageo.

Tolophone Call Flow Treasury has two rnarn telephonf,t contact center grou~ lndMduaJ lnooma Tax (UT) and Business Tax:. The caU flow includes 24 x7 eiccess to lhe Geoesys IVR. Several Genesys vtrtual can queues ara created in front of the .agents to allO'o't spec~!lzed customer SE'.rvlce. The Gones~ configuratioo is done by the contractor. The AV!dya ACD vectoring and programming is done by DTMB T eleoom. Tne Avaya ACO m""sages for these vectors ar.,o ll\e IVR are developed and recorded by Treasury business users.

MGA has one telephone call ""1'1ter group, The Genesys IVR for MGA has restricted hO\Jrs due to lhe need to acc.e,;s Same Mae. MGA'• tVR app"""-tion Is available Monday through Fr[day 7:30 AM -9:00 PM and Saturday 9:00 AM • 1 :00 PM.

Ganesys Screen pop, Rou\ino and Untversal Queuing Geneoys Computer Telephony Integration (CTQ Is used to provide basic screen pops for incoming and. transferred tolephooa calls, and manage catl waiting queues (on the switch) for Income Tax and the Business Tax Unes. Account identifying data Is captured in the IVR, and is passed to Genosys CTl, which qµerie• the Slebol database lo determi,,e some pertrnent cllaracte~stics of t)le caller. Ganes'.,'S en then · routes the call through various call treafmenl6 and ultimately lo lhe most appropriate skilled agent. The Genesys Gplus adapter Jo Siebel allows the CSR lo .g&t the taxpayer account Information on their screen in a screen pop w1,en they answer tha call. If Geoosys IVR and CTI are not available the default Avaya vectors have been daaign«I to provide an alternative routing to the agent.

Gene&ys has been configured to route non-real time items, a~though thtS functionanty has currently been turnGd off. For example, Siebe) se1vice req1.186IG would be sel"!t to Genesys and woukl e,ffectively roulo them i!'l muoh lhe same way as telephone calls a,e routed. Agents would hava a work•slale !hat woo1d make !ham available for elthei' real time llems (phone calls) or non-real time (seNlce reque,;ta). To get non-real time items ioday, CSRs sign Into an.AUX code to w01k correeponclence and plcl< service roquests from tho~ group's ~st ol items.

G~pesys Interactive Voice Response llVRl Th• IVR application has 5 production ,;e,vers incl\ldlng !wo GVP servers, Eight T1 circuits behind tile Avaya G:i switch. The test system include$ two servers and one T1.

The IVR provides lh8 taxpayer with sell•seNioe options that require aulhenlicat!ori using shared secrets from the related ~ci:ount's CRM data, Credentials are collected in the lli'R and pasS<ld to Siebel !or verification. This connection Is through an XML request over an HTTP connection to .the Siebel application server. An approwl returns taxpay;,r information in XML format to the IVR, which parses oul the necessary data for tho response to !he taxpayer. Similarly, U1• MGA IVR collecls credentials and passes tho.data to Sallie 'Mae for verificatioo via web services. The wab service passes back data (rorn Same Mae n·eces5qry to oompJete the can. Oata Is exchanged in on XML form.at T exMo~sptech response functionality tooS1s only for playing back. Many sysl'$m res.ponses requires messages, in which case the system pld<s from a number of preMrecorded mes.sages that are played as required. The IVR application alSo ha~ front-end tables built in lh•t allow the busine•• user analysts to change certain responses auch as the estimated date when a specific taxpayer's refund wm be

ls-susd.

Finally at the end <>f the call, when the taxpayer hangs up or pushes oYI lo the ag.,nt call now, a Sio)J<>I contaoi reoord is put Into the Activity log.

Empirlx servioes are used to monitor IVR functionality 24/7. This s,ervice i:s covered under a separate con.tract.

NICE Call Monitoring and Reco(djng n 1e NfCE Perform 3.X application ha$ been configured to provide quality a$S-urance and reoord cm demand funclionalily. II monitors and records agent call•, forming an integral part of Treasury'$ qualltJ. system. The NICE window dlsplays agent aod chaMels, includjng reartime•infomuitloo. Galls recorded conta.ln voice and screen. Screens can be monltoredfrecordedlplayed.

currently any changes or upgrades to this aystom ,.,.. provided direct~/ Wough NICE systems. NICE must connect to Ille Genesys T server via a pre-built connector lnstettcd by NICE,

Interfaces • · Logocy . Siebel re<:eiv"" data each night from the Unisys mainframe. The Oatabridge prod UC! Is used to extract audit

files rrom the mainframe and ptaoe the data into Oracle tabl~. PL/SOL stalementti. are used to populate Siebel E-IM table&. Finally, an IFS process JVns w,d popul~tes the Shabel bas& tab1es.

b. SAP Siebel ·,~ves dala oocll night fro,:n SAP-XI whlcl, Is lnillally loaded Into temporary Or;!cle holding tables. PL/SQL atatcmen.ts am then used to populate Siebel EIM tabJes from there. Fi-nany, an IFB pro~s ru'ne 1:1nd populates lhe Siebel bas.e tables.

c. lnboond Corresponden<:e Legae;y sys:lem and SAP processes require immedlate notification when a taxpayer responds to a Treasury request by submitting a letter or returning a.oompleted fom,. To facilitate U,i• ,equlremenl, a mo is generated In File Net from !he ,magad and indexod ccrrespondence and 8'lnt lo a leg•cy ho-st. ·

d. Security Adapter A detailed program has been croated to capture credentials and authenticate taxpayers accessing the Siebe! syst_om throogh the web. This adal)ler has been ewr~ed and validated by Siebel.

e. Genesys The Genes~'S Gplus adapter fof Siebel is usf)d lo 6upport communicalion be\W&en Gene sys and Stebe:I. This supports many runctioos including screen pop$ and the Siebel communications toot bar ~a1 pro11idet; teleph0<1y control to agents al their desktop, Genesys does access Siebel directly to provide the data (or

routing deois,ions.

f. MARCS lnfoO:nation about inbound corresPonOOnce received in the Collecl:ions/MARCS eystom is loaded Into Siebel using the EIM p(OCGSS, creating Siebel service requests. A daily extract fda Is also created within Siebel containing updates on completed MAR.CS corre,5_pondence. TI,ts extract flle is taken ;:i.::, on Input int9 MARCS.

g. FHeNet CIS This product lacl,tates the oommunicatl0<1 between FileNet and Siebel. It a'l!ow• service requests and contact log$ to bEi created in Siebel And allows CSRs to aeeess FlteNel attachments by clk:kfl'lg on an Icon within a s;ebel window.

h. Scheduling Software Tidal and Opalis are Cltrrently used to sehedule interlace dat~ transfet. In !he daily Treasury CSIP Refresh process, the data Is extracted from the legacy and SAP systems .and sent to tha Slobel EIM tables. Scripts are usod to load dalo !tom EIM tables to !ha Siebel Base tables. All script• and prooessoo nec<ossary 10 refrash the Treasury data through to the Siebel Base tabfe!j, and all other eutom~t~d ecrip(.$ <>T repotts will ba automated to OpalismdaJ job scheduler. OTMB. supports the job scheduling programs.

I. -SalliaMae The MGA IVR authenticates the c~ler and reads information back from the Sallie Mae system via web services. OTMB suppOrls the web service for Sallie Mae.

j. Treasury Ceolr~lized Correspondence system (a.k.a. "the letter wr~er") The MGA IVR offers the caller several options to receive correspondence (ax, paid In full letter, payoff quote, e1c.). When tho caller opts to receive correspondence the tVR generates a request lo the Treasury Centralized Correspondence system via web se<Vlces. OTMB supports this wo,b seivlce.

k. Centralized Eloctrooic Payment Authorixatl(?ll System (CEPAS) . Begilming In August 2011, the MGA IVR Will transfer callers who wish to make a payment to a new CEPAS IVR offered by v~ndor First Data Government SoluUons (FOGS). This Is• straig_htfotward call lransfer to a 1-800 number

H•rdw/lre There are 3 hardware envlronments: production, test and development.

!3$)ortiog Geilesys CCPuloe

Tre'1sury uiilizes the Genesys CCPulse appli<:ation for real-time ,r,ey,ing cl sbliSUcs for all vtrtual call queues, agent statistics, group stalistioo, and queue volume alerts,

Gene'Sys CCAnalyz.er Treasvr.J utilizes 'the (.3enesys CCAnalyzer application for hi'stortcaJ reporting for a.II routing points, call queues, virtual call queues, agent slati$tics, group •ialislics, and Customer pereonall%lllion call tracking $tatislios.

Genesys Voloe Application Raporte< (VAR) Some business users obtain historical and real jime IVR reporting Information from the VAR appUcatlon. This system J)n?Vides information on customer call path Utilization within the JVR ahd success-rates forcails-secvkoo wlt.hln U1e JVR,

Avaya CMS (Call Management System) Some business users still rely on CMS reports. CMS is supported ar,d maintained by DTMB Telecom. If for some reason Genesy$. ;:eporting is lost, CMS can pmvldo some Jeve.1 of back up.

Other Reports There ,ire othar sources used to supply management wilH operetlonal and strategic data about the contact cer,ter. These Include Avaya CMS, and.Siebel and Oracle SOL Que1ies. ·

O§vetopmeot & Jesting S!ebel CRM and eSarvice, Oenegys and FlleNet componeot and sy~tem testing is performed by the contractor. There are.CRM and C-,enesys development environments and a Fil~Net deve-lopm-ent/test envtro·nment. DTMB supports the related servers and $pplicationa for CRM. Oracle databases .and secun'ty access controls for eaci'I

environment

Avaya ACD vectoring, programming and mess39e asstrjnmenl ate supportod by DTMB Telecom.

Dedicated business user team!:I of 2 to 4 analysts identify new enhancements, work w ith lhP. contractor to develop business requirements, create wording for messages, and menus in the Aveya ACD~ Genesys fVR and eServioe web screens. ·rhe business user creates test scripts with the assistanoe of the contractor, maintain the various channels test scrlpt libraries, assle;t in identifying new test dat8. f!;)quirements and lead the user acceptance test to,ims for Slobet CRM, Slabel eServioe, Genesys, Avaya ACD, Geneays IVR, 2nd F l!eNot. This .user team also maintains the CRM adminlstraU'\•e tables .a~ selected Genesys adminie,tra.tfve 1$1es.

TI'8 heavies\ development period occurs during Jt.W\e through December. 01:her Treasury CRM point releases oocur during the rest of the year. Addition of now teams, dasses and document types to file Net ow.1r throughout the year. Bt1sin8$S owner signs off en enhancements J changes in atl channel$ before ·1hey 3re moved to

production,

~ The contractor s11all troat ond handle Department ofTreasuty,Peroonal, confidential or sensitive data It receiVes tn eccordanco with the terms of this .Agreement, State of ~Uehlgan policies and the laws of the State of Michigan and the Uniled $I/lies .

future Qovelopm(int • Treasury haa &tarted ~ans for devek>pmenl of replacement systems for So.sinese Regkstra.Uon JanQ combined

Sales. Use aind Withholding over the ne~t few years. These replacemenl systems will require the rel;luj!d of daily ElM refresh proceeses from these legacy systems and expansion pt busineaa aC'.couot data el&ments

inCRM. • Conskl.eration fO! the development of tive chat and other •social media" contact methods such as text

messaging is In 'the future. Security considerations are paramount, but infrastructure is not currenl!y in place

ror these channels.

• Ability to add additional laXes and intelface with COTS/ERP systems suet\ as SAP. For tho new Corporate Income Tax (C11) and Flow Through Withholding, using the XI component lo query the SAP production data real-time via SlebeVCRM

• Ability to add ·new taxes to IVR •ysiems and provide enhanced lnfom,ation.

• Abiriiy to interface with other telephony systems, including VOiP.

• Replaoe existing scheduling tool ff'9!l'I OPAUS to TIDAl .

• Measortiment of first contact resolution is also a desired outcome of any system enhancements.

Ability to accept and log electronic documents s.ent from customers into FilaNet such as electronlc faxes <IJld ollaohments to eService s""'1oe raques1s.

De5ve~ Lead/Account Lead

Pro•ect Man..,..,

Functional Lead -Senior

FunctiOnal Lead -Junior

•-- •;cation Lead/ Sv$tem Architect

Technical Architect

TechnJcal Lead

Business AnaNst

oeveloner ~ Senior

Develo"'""f - Junior

Tester - Sent or tLesd\

lester - Junior

Trainer - Senior

Trainer - Junior

Technical Writer

ATTACHMENT A

Pricing Schedule

$ 220.00

$ 195.00

$ 195.00

s 180.00

$ 195.00

$ 270.00

" 170.00 ·~·-$ 170.00

• 175.00

., 140.00

s 150.00

$ 135.00

$ 180.00

• 110.00

s 105.00

o-_ .. ,.,.,, ..

NIA N/A

$ 175.00 $ 123.00

$ 165.00 $ 64.00

$ 150.00 $ 53.00

s 165.00 $ 64.00

$ 240.00 s 131.00

$ 135.00 $ 53.00

$ 135.00 $ 53.00

• 120.00 .. $ 32.00

$ 100.00 • 27.00

~ 110 .00 s 32.00

• 100.00 $ 27.00

$ 135.00 $ 32.00

• 90.00 s 27.00

$ 80.00 • 32.00

Form No. DTMB-3521 (Rev. 4/2012) AUTHORITY: Act 431 of 1984 COMPLETION: Required PENALTY: Contract change will not be executed unless form is filed

STATE OF MICHIGAN DEPARTMENT OF TECHNOLOGY, MANAGEMENT AND BUDGET May 8, 2014

PROCUREMENT P.O. BOX 30026, LANSING, MI 48909

OR 530 W. ALLEGAN, LANSING, MI 48933

CHANGE NOTICE NO. 2

to

CONTRACT NO. 071B2200168

between

THE STATE OF MICHIGAN

and

NAME & ADDRESS OF CONTRACTOR: PRIMARY CONTACT EMAIL

Accenture LLP Jamie Walker [email protected]

3000 Town Center, Suite 2400 TELEPHONE CONTRACTOR #, MAIL CODE

South Field, MI 48075 (517) 241-1640

STATE CONTACTS AGENCY NAME PHONE EMAIL

CONTRACT COMPLIANCE INSPECTOR DTMB Mark Lawrence

(517) 241-1640 [email protected]

BUYER DTMB Jarrod Barron (517)284-

7045 [email protected]

CONTRACT SUMMARY:

DESCRIPTION: Contact Center Support

INITIAL EFFECTIVE DATE

INITIAL EXPIRATION DATE

INITIAL AVAILABLE OPTIONS

EXPIRATION DATE BEFORE CHANGE(S) NOTED BELOW

May 1, 2012 April 30, 2017 5, one year April 30, 2017

PAYMENT TERMS F.O.B SHIPPED SHIPPED FROM

N/A N/A N/A N/A

ALTERNATE PAYMENT OPTIONS: AVAILABLE TO MiDEAL PARTICIPANTS

P-card Direct Voucher (DV) Other Yes No MINIMUM DELIVERY REQUIREMENTS:

N/A

DESCRIPTION OF CHANGE NOTICE: EXTEND CONTRACT EXPIRATION DATE

EXERCISE CONTRACT OPTION YEAR(S)

EXTENSION BEYOND CONTRACT OPTION YEARS

LENGTH OF OPTION/EXTENSION

EXPIRATION DATE AFTER CHANGE

No Yes

VALUE/COST OF CHANGE NOTICE: ESTIMATED REVISED AGGREGATE CONTRACT VALUE:

$6,482,560.00 $20,731,375.40 Effective immediately, the Estimated Revised Aggregate Contract Value is INCREASED by $6,482,560.00, to allow for $1,482,560.00 additional funding for Base Support (outlined in attached Addendum to Attachment 3, Tables 1 and 3) and $5,000,000.00 additional funding for Major Enhancements (outlined in attached Addendum to Attachment 3, Table 4). This reduces the remaining balance of funding available in Table 4 of Attachment 3 for Major Enhancements to $2,751,184.60. Updated Cost Tables are attached. All future Statements of Work related to Major Enhancements shall be memorialized in a corresponding future Contract Change Notice prior to the issuance of any purchase orders for said enhancements. All other pricing, terms and conditions remain the same. Per Original Contract Ad Board Approval on 4/3/2012.

ADDENDUM TO Contract 071B2200168, Attachment 3: Cost Tables

Pursuant to CCN # 3 Revisions

Addendum to Table 1: Summary of the Project Cost

Provisions:

1. If, after the Contract is signed, it is determined that information provided by the State of Michigan to the bidders is inaccurate or incomplete in any material manner, the parties will negotiate an adjustment in the project schedule and the fees and expenses, as applicable, per the Contract’s change order process.

2. Contractor’s fixed price is based on delivery of the fixed scope of services in Contract. The scope of the services as documented will remain unchanged, except as the parties may agree in writing. All other work, including schedule extensions not approved by Contractor (or within Contractor’s responsibility per the Contract), will require the parties to agree upon a change order to the Contract.

3. Contractor's performance of the Contract is dependent on the State of Michigan's prompt and effective performance of its responsibilities, including timely decisions and approvals.

4. The State of Michigan will commit resources and management involvement as described in the Contract or as required by the work effort in order to support Contractor’s delivery of the services and to perform the agreed upon acceptance procedures in a timely manner.

5. The State of Michigan will be responsible for its operation and use of Contractor’s deliverables upon acceptance, subject to applicable warranties and indemnities, if any, and for determining whether the services and deliverables provided by Contractor under the Contract, including any revised business processes implemented pursuant to the Contract, meet the State of Michigan's business requirements and applicable internal guidelines.

6. The State of Michigan will obtain all consents necessary from its third parties (i.e., those not under contract with Contractor) required for Contractor to perform its obligations under this Contract. The State of Michigan will be responsible for the contractual relationship with such third parties and for facilitating their cooperation with Contractor. Contractor will not have any responsibility for the performance of other contractors or vendors engaged by the State of Michigan (other than Contractor’s subcontractors) or delays caused by them. There are no third party beneficiaries to this Contract.

7. The State of Michigan will be responsible for obtaining, at no cost to Contractor, consents for Contractor’s use of any State of Michigan Furnished Property necessary to perform its obligations hereunder. Unless otherwise agreed to by the parties in writing, the State of Michigan will provide all software and hardware necessary for Contractor to perform its obligations under the Contract.

8. Each party will retain responsibility for its compliance with any laws, regulations, or other authorities, in effect on the date of submission of our proposal, including those areas on which it relies on the other party’s performance under the Contract.

9. Use of the term "ensure" is defined to mean that both parties will use all reasonable and commercial efforts to accomplish their legal responsibilities under the terms of the Contract.

No. Project Cost(s) Cost ($) Comments

Knowledge Transfer cost

Give breakdown in Table 2

Base Service Cost

Breakdown provided in Table 3

Major Enhancements cost Breakdown provided in Table 4

Total Project Cost $23,482,560.00

C.

$11,751,184.60 5) This is only the provisional 'spend' budget for the nearly 84,000 hours of SoW

work sought by the State 6) Assumed equal spending of this effort over all 5 years of contract term 7) Price absorbs COLA increases so that State is insulated from these variations

A.

0 1) Accenture is supporting all of the Contact centers in scope. No KT costs are

charged to the State for these contact centers.

B.

$ 11,731,375.40 2) Per request, removed NICE support and IVR discretionary enhancement from

scope. This is consistent with the level of support on the current contract.

3) Accenture had absorbed expense increases internally and has offered this

price.

4) Process efficiencies are incorporated in Y2 onwards of the term, to provide net

reduction of base support costs to the State

Addendum to Table 2: Knowledge Transfer Cost – RESERVED. There was never any knowledge transfer cost because Contractor was already supporting the Contact Centers prior to the execution of this contract. Addendum to Table 3: Base Service Cost

No.

Agency

Year 1

(12 months)

Year 2

(12 months)

Year 3

(12 months)

Year 4

(12 months)

Year 5

(12 months)

Total 5 year

cost by agency

Costs per year

2,049,763.08 2,260,696.41 2,453,549.75 2,483,683.08 2,483,683.08

Number of months in that year

12 12 12 12 12

Cost per month

170,813.59 188,391.37 204,462.48 206,973.59 206,973.59

Total Base Service Cost (sum of total 5 year cost by agency

11,731,375.40

Notes: 1. Base Support is provided at the above-listed fixed fees to the following eleven (11) MiECC contact

centers: Civil Service Commission (MCSC) DHS-Michigan Statewide Automated Child Welfare Information System (MiSACWIS) DHS-Office of Child Support (OCS) DTMB-Client Service Center (CSC) DTMB-Office of Retirement Services (ORS) Environmental Quality (DEQ) Human Services (DHS) Licensing and Regulatory Affairs(LARA)-Bureau of Health Professions(BHP) Licensing and Regulatory Affairs(LARA)-Unemployment Insurance Agency (UIA) State (MDOS) Treasury

2. All prices stated in US$.

Addendum to Table 4: Rate Card

No. Staffing Category Firm Fixed Hourly Rate

Est. Hours (5 year total)

Extended Price (hourly rate X estimated hours)

Project Manager $ 181.00 500 $ 90,500.00

Systems Architect $ 145.00 500 $ 72,500.00

Business Analyst $ 138.00 7,500 $ 1,035,000.00

Siebel Lead $ 130.00 5,000 $ 650,000.00

Siebel Developer $ 113.00 16,000 $ 1,808,000.00


$ 167.00 5,500 $ 918,500.00

Genesys Specialist $ 267.00 5,000 $ 1,335,000.00

IVR Developer $ 113.00 14,000 $ 1,582,000.00

NICE Analyst $ 113.00 5,000 $ 565,000.00

Tester $ 152.00 5,000 $ 760,000.00

Other (Please specify) TBD

$ 150.00 19,564.56 $ 2,934,684.60

Total Major Enhancement Cost

$ 11,751,184.60

Notes: 1. Hourly rates quoted are firm, fixed rates for the duration of the contract. Travel and other expenses will

not be reimbursed. “Estimated Hours” and “Extended Price” are non-binding and will be used at the State’s discretion to determine best value to the State. The State will utilize the fully loaded hourly rates detailed above for each staff that will be used as fixed rates for responses to separate statements of work.

2. The State intends to establish funding for up to the estimated hours. Actual funding for enhancements will occur on a yearly basis, and there is no guarantee as to the level of funding, if any, available to the project. On 4/3/2012, the State of Michigan Administrative Board (Ad Board) approved $11,751,184.60 for Major Enhancements. Of that amount, $2,000,000.00 was placed on the original contract’s rate card, leaving $9,751,184.60 that could be added to the contract in the future. On 4/19/2013, pursuant to Change Notice # 1, an additional $2,000,000.00 was placed on the contract’s rate card, leaving $7,751,184.60 that could be added to the contract in the future. At this time, pursuant to Change Notice # 2, an additional $5,000,000.00 is placed on the contract’s rate card, leaving $2,751,184.60 that may be added to the contract in the future via a future Change Notice. All future Statements of Work (SOW’s) related to Major Enhancements shall be memorialized in a corresponding future Contract Change Notice, regardless of whether the corresponding funding supporting such SOW(s) is being added contemporaneously to the contract or has previously been added to the contract.

3. The parties agree that the Services/Deliverables to be rendered by Contractor using the future enhancements/rate card on this Contract will be defined and described in detail in separate Statements of Work. Contractor shall not be obliged or authorized to commence any work to implement a Statement of Work until authorized via a purchase order issued against this Contract.

4. Other skills/roles suggested by the bidder should also show the hourly rate. The bidder can assume 0 hours for these skills for the purpose of computation.

AUTHORITY: Act 431 of 1984 COMPLETION: Required PENALTY: Contract change will not be executed unless form is filed

STATE OF MICHIGAN

DEPARTMENT OF TECHNOLOGY, MANAGEMENT AND BUDGET April 19, 2013 PROCUREMENT

P.O. BOX 30026, LANSING, MI 48909 OR

530 W. ALLEGAN, LANSING, MI 48933

CHANGE NOTICE NO. 1 to

CONTRACT NO. 071B2200168 between

THE STATE OF MICHIGAN

and

NAME & ADDRESS OF CONTRACTOR: PRIMARY CONTACT EMAIL

Accenture LLP Jamie Walker [email protected]

3000 Town Center, Suite 2400 TELEPHONE CONTRACTOR #, MAIL CODE

South Field, MI 48075 (517) 241-1640

STATE CONTACTS AGENCY NAME PHONE EMAIL CONTRACT COMPLIANCE INSPECTOR: DTMB Mark Lawrence (517) 241-1640 [email protected]

BUYER: DTMB Steve Motz (517) 241-3215 [email protected]

CONTRACT SUMMARY: DESCRIPTION: Contact Center Support

INITIAL EFFECTIVE DATE

INITIAL EXPIRATION DATE

INITIAL OPTIONS INCLUDED CURRENT EXPIRATION DATE

May 1, 2002 April 30, 2017 5, One-Year April 30, 2017

PAYMENT TERMS F.O.B SHIPPED SHIPPED FROM

N/A N/A N/A N/A

ALTERNATE PAYMENT OPTIONS: AVAILABLE TO MiDEAL PARTICIPANTS

P-card Direct Voucher (DV) Other YES NO

MINIMUM DELIVERY REQUIREMENTS: N/A

DESCRIPTION OF CHANGE NOTICE: OPTION EXERCISED: NO YES

IF YES, EFFECTIVE DATE OF CHANGE: N/A

NEW EXPIRATION DATE: N/A

Effective immediately, the Estimated Revised Aggregate Contract Value is INCREASED by $2,000,000.00 to allow for additional funding for Major Enhancements as outlined in Table 4 of Attachment 3. This reduces the remaining balance of funding available in Table 4 of Attachment 3 for Major Enhancements to $7,751,184.60. All other pricing, terms and conditions remain the same. Per Original Contract Ad Board Approval on 4/3/2012.

VALUE/COST OF CHANGE NOTICE: $2,000,000.00

ESTIMATED REVISED AGGREGATE CONTRACT VALUE: $14,248,815.40

Form No. DMB 234 (Rev. 1/96) AUTHORITY: Act 431 of 1984 COMPLETION: Required PENALTY: Contract will not be executed unless form is filed

STATE OF MICHIGAN DEPARTMENT OF TECHNOLOGY, MANAGEMENT AND BUDGET PROCUREMENT P.O. BOX 30026, LANSING, MI 48909 OR 530 W. ALLEGAN, LANSING, MI 48933

NOTICE OF

CONTRACT NO. 071B2200168 between THE STATE OF MICHIGAN and Accenture LLP TELEPHONE (517) 862-0192 3000 Town Center Jamie Walker Suite 2400 CONTRACTOR NUMBER/MAIL CODE

South Field, MI 48075 BUYER/CA (517) 241-1640

Email: [email protected] Mark Lawrence Contract Compliance Inspector:

Contact Center Support CONTRACT PERIOD: 5 yrs. + 5 one-year options From: May 1, 2012 To: April 30, 2017 TERMS SHIPMENT N/A N/A F.O.B. SHIPPED FROM N/A N/A ALTERNATE PAYMENT OPTIONS:

P-card Direct Voucher (DV) Other

MINIMUM DELIVERY REQUIREMENTS N/A MISCELLANEOUS INFORMATION: The terms and conditions of this Contract are those of ITB #071I2200001, this Contract Agreement and the vendor's quote dated March 27, 2012. In the event of any conflicts between the specifications, and terms and conditions, indicated by the State and those indicated by the vendor, those of the State take precedence. Estimated Contract Value: $12,248,815.40 THIS IS NOT AN ORDER: This Contract Agreement is awarded on the basis of our inquiry bearing the ITB No. 071I2200001. All terms and conditions of the invitation to bid are made a part hereof.

74Form No. DMB 234 (Rev. 1/96) AUTHORITY: Act 431 of 1984 COMPLETION: Required PENALTY: Contract will not be executed unless form is filed

STATE OF MICHIGAN DEPARTMENT OF TECHNOLOGY, MANAGEMENT AND BUDGET PROCUREMENT P.O. BOX 30026, LANSING, MI 48909 OR 530 W. ALLEGAN, LANSING, MI 48933

CONTRACT NO. 071B2200168 between THE STATE OF MICHIGAN and Accenture LLP TELEPHONE (517) 862-0192 3000 Town Center Jamie Walker Suite 2400 CONTRACTOR NUMBER/MAIL CODE

South Field, MI 48075 BUYER/CA (517) 241-1640

Email: [email protected] Mark Lawrence Contract Compliance Inspector:

Contact Center Support CONTRACT PERIOD: 5 yrs. + 5 one-year options From: May 1, 2012 To: April 30, 2017 TERMS SHIPMENT N/A N/A F.O.B. SHIPPED FROM N/A N/A ALTERNATE PAYMENT OPTIONS:

P-card Direct Voucher (DV) Other

MINIMUM DELIVERY REQUIREMENTS N/A MISCELLANEOUS INFORMATION: The terms and conditions of this Contract are those of ITB #071I2200001, this Contract Agreement and the vendor's quote dated March 27, 2012. In the event of any conflicts between the specifications, and terms and conditions, indicated by the State and those indicated by the vendor, those of the State take precedence. Estimated Contract Value: $12,248,815.40 THIS IS NOT AN ORDER: This Contract Agreement is awarded on the basis of our inquiry bearing the ITB No. 071I2200001. All terms and conditions of the invitation to bid are made a part hereof.

FOR THE CONTRACTOR:

FOR THE STATE:

Firm Name Signature

Jeff Brownlee, Chief Procurement Officer Authorized Agent Signature Name/Title

DTMB Procurement Authorized Agent (Print or Type) Division

Date Date

CONTRACT #071B2200168

25

STATE OF MICHIGAN

Department of Technology, Management and Budget Purchasing Operations

Contract # 071B2200168 Contact Center Support

Buyer Name: Mark Lawrence Telephone Number: 517-241-1640

E-Mail Address: [email protected]


26

Table of Contents

1.000 Project Identification 30 1.001 Project Request 30 1.002 Background 30

1.100 Scope of Work and Deliverables 32 1.101 In Scope 32 1.102 Out Of Scope 34 1.103 Environment 34 1.104 Work and Deliverable 38

1.200 Roles and Responsibilities 78 1.201 Contractor Staff, Roles, And Responsibilities 78 1.202 State Staff, Roles, And Responsibilities 85 1.203 Other Roles And Responsibilities 87

1.300 Project Plan 87 1.301 Project Plan Management 87 1.302 Reports 90

1.400 Project Management 91 1.401 Issue Management 91 1.402 Risk Management 93 1.403 Change Management 96

1.500 Acceptance 98 1.501 Criteria 98 1.502 Final Acceptance 99

1.600 Compensation and Payment 99 1.601 Compensation And Payment 99 1.602 Holdback 100

Article 2, Terms and Conditions 101

2.000 Contract Structure and Term 101 2.001 Contract Term 101 2.002 Options to Renew 101 2.003 Legal Effect 101 2.004 Attachments & Exhibits 101 2.005 Ordering 101 2.006 Order of Precedence 101 2.007 Headings 102 2.008 Form, Function & Utility 102 2.009 Reformation and Severability 102

2.010 Consents and Approvals 102 2.011 No Waiver of Default 102 2.012 Survival 102

2.020 Contract Administration 102 2.021 Issuing Office 102 2.022 Contract Compliance Inspector 102 2.023 Project Manager 103 2.024 Change Requests 103 2.025 Notices 104 2.026 Binding Commitments 105 2.027 Relationship of the Parties 105 2.028 Covenant of Good Faith 105 2.029 Assignments 105

2.030 General Provisions 105 2.031 Media Releases 105 2.032 Contract Distribution 105 2.033 Permits 105 2.034 Website Incorporation 106 2.035 Future Bidding Preclusion 106 2.036 Freedom of Information 106 2.037 Disaster Recovery 106

2.040 Financial Provisions 106


27

2.041 Fixed Prices for Services/Deliverables 106 2.042 Adjustments for Reductions in Scope of Services/Deliverables 106 2.043 Services/Deliverables Covered 106 2.044 Invoicing and Payment – In General 106 2.045 Pro-ration 107 2.046 Antitrust Assignment 107 2.047 Final Payment 107 2.048 Electronic Payment Requirement 107

2.050 Taxes 107 2.051 Employment Taxes 107 2.052 Sales and Use Taxes 107

2.060 Contract Management 108 2.061 Contractor Personnel Qualifications 108 2.062 Contractor Key Personnel 108 2.063 Re-assignment of Personnel at the State’s Request 109 2.064 Contractor Personnel Location 109 2.065 Contractor Identification 109 2.066 Cooperation with Third Parties 109 2.067 Contract Management Responsibilities 109 2.068 Contractor Return of State Equipment/Resources 110

2.070 Subcontracting by Contractor 110 2.071 Contractor full Responsibility 110 2.072 State Consent to delegation 110 2.073 Subcontractor bound to Contract 110 2.074 Flow Down 110 2.075 Competitive Selection 110

2.080 State Responsibilities 111 2.081 Equipment 111 2.082 Facilities 111

2.090 Security 111 2.091 Background Checks 111 2.092 Security Breach Notification 111 2.093 PCI DATA Security Requirements 111

2.100 Confidentiality 111 2.101 Confidentiality 111 2.102 Protection and Destruction of Confidential Information 112 2.103 Exclusions 112 2.104 No Implied Rights 112 2.105 Respective Obligations 112 2.106 State Personal Data and Security Breach Notification 113

2.110 Records and Inspections 113 2.111 Inspection of Work Performed 113 2.112 Examination of Records 113 2.113 Retention of Records 114 2.114 Audit Resolution 114 2.115 Errors 114

2.120 Warranties 114 2.121 Warranties and Representations 114 2.122 Warranty of Merchantability 115 2.123 Warranty of Fitness for a Particular Purpose 115 2.124 Warranty of Title 115 2.125 Equipment Warranty 115 2.126 Equipment to be New 116 2.127 Prohibited Products 116 2.128 Consequences for Breach 116

2.130 Insurance 116 2.131 Liability Insurance 116 2.132 Subcontractor Insurance Coverage 118 2.133 Certificates of Insurance and Other Requirements 118

2.140 Indemnification 118 2.141 General Indemnification 118


28

2.142 Code Indemnification 118 2.143 Employee Indemnification 118 2.144 Patent/Copyright Infringement Indemnification 119 2.145 Continuation of Indemnification Obligations 119 2.146 Indemnification Procedures 119

2.150 Termination/Cancellation 120 2.151 Notice and Right to Cure 120 2.152 Termination for Cause 120 2.153 Termination for Convenience 120 2.154 Termination for Non-Appropriation 121 2.155 Termination for Criminal Conviction 121 2.156 Termination for Approvals Rescinded 121 2.157 Rights and Obligations upon Termination 121 2.158 Reservation of Rights 122

2.160 Termination by Contractor 122 2.161 Termination by Contractor 122

2.170 Transition Responsibilities 122 2.171 122 2.172 Contractor Personnel Transition 122 2.173 123 2.174 123 2.175 123 2.176 State Transition Responsibilities 123

2.180 Stop Work 123 2.181 Stop Work Orders 123 2.182 Cancellation or Expiration of Stop Work Order 123 2.183 Allowance of Contractor Costs 124

2.190 Dispute Resolution 124 2.191 In General 124 2.192 Informal Dispute Resolution 124 2.193 Injunctive Relief 125 2.194 Continued Performance 125

2.200 Federal and State Contract Requirements 125 2.201 Nondiscrimination 125 2.202 Unfair Labor Practices 125 2.203 Workplace Safety and Discriminatory Harassment 125 2.204 Prevailing Wage 125

2.210 Governing Law 126 2.211 Governing Law 126 2.212 Compliance with Laws 126 2.213 Jurisdiction 126

2.220 Limitation of Liability 126 2.221 Limitation of Liability 126

2.230 Disclosure Responsibilities 126 2.231 Disclosure of Litigation 126 2.232 Contact center Disclosure 127 2.233 Bankruptcy 127

2.240 Performance 127 2.241 Time of Performance 127 2.242 Service Level Agreement (SLA) 127 2.243 Liquidated Damages 128 2.244 Excusable Failure 128

2.250 Approval of Deliverables 129 2.251 Delivery of Deliverables 129 2.252 Contractor System Testing 129 2.253 Approval of Deliverables, In General 130 2.254 Process for Approval of Written Deliverables 131 2.255 Process for Approval of Custom Software Deliverables 131 2.256 Final Acceptance 132

2.260 Ownership 132


29

2.261 Ownership of Work Product by State 132 2.262 Vesting of Rights 132 2.263 Rights in Data 132 2.264 Ownership of Materials 133 2.266 General Skills 133

2.270 State Standards 133 2.271 Existing Technology Standards 133 2.272 Acceptable Use Policy 133 2.273 Systems Changes 134

2.280 Extended Purchasing 134 2.281 MiDEAL (Michigan Delivery Extended Agreements Locally 134 2.282 State Employee Purchases 134

2.290 Environmental Provision 134 2.291 Environmental Provision 134

2.300 Deliverables 135 2.301 Software 135 2.302 Hardware 136

2.310 Software Warranties 136 2.311 Performance Warranty 136 2.312 No Surreptitious Code Warranty 136 2.313 Calendar Warranty 136 2.314 Third-party Software Warranty 137 2.315 Physical Media Warranty 137

2.320 Software Licensing 137 2.321 Cross-License, Deliverables Only, License to Contractor 137 2.322 Cross-License, Deliverables and Derivative Work, License to Contractor 137 2.323 License Back to the State 137 2.324 License Retained by Contractor 137 2.325 Pre-existing Materials for Custom Software Deliverables 137

2.330 Source Code Escrow 137 2.331 Definition 137 2.332 Delivery of Source Code into Escrow 137 2.333 Delivery of New Source Code into Escrow 137 2.334 Verification 137 2.335 Escrow Fees 137 2.336 Release Events 137 2.337 Release Event Procedures 138 2.338 License 138 2.339 Derivative Works 138

Attachment 1: Service Level Agreement and Return to Service Goals 143

Attachment 2: Work Requirements 145

Attachment 3: Cost Tables 152

Attachment 4: Personnel Requirements 157

Attachment 5: Resume Template 167

Attachment 6: List of Approved Subcontractors 188

Attachment 7: Preliminary Work Plan 189

Attachment 8: Agency Background Information 190

Attachment 9: Agency Environment Information 200


30

Article 1 – Statement of Work (SOW)

1.000 Project Identification

1.001 Project Request

The purpose of this Contract is to obtain a firm to provide shared IT services to maintain and enhance eight (and possibly more) contact centers at multiple agencies of State of Michigan. The standardized contact center technology at State of Michigan includes Siebel CRM, Oracle RDBMS, Genesys IVR, NICE, FileNet, Avaya Communication Managers PBX(s) and Avaya Application Enablement Services (AES) servers.

1.002 Background

The following background information is provided as baseline and historical reference information only.

The Michigan Department of Information Technology (MDIT) was created in October 2001 by Executive Order No. 2001-3 to achieve a unified and more cost-effective approach for managing information technology among all Executive Branch agencies. MDIT was recently merged with Department of Management and Budget and was named Department of Technology, Management and Budget (DTMB). As a state agency, DTMB is empowered to enact the enterprise use of common information technologies and provide consistent professional management of the state’s Information Technology (IT) resources.

The vision, mission and goals for DTMB are -

Vision: A transformed Michigan—advanced through collaborative, transparent and results-focused services to government, citizens and business.

Mission: Providing leadership and setting the pace for customer service, resource optimization, and the innovative use of information and technology.

Goals: 1. Customer Service Excellence: Provide quality, cost-effective business services through a fully-

integrated, information, communications and technology-infused service organization.

2. Operational Efficiency: Deliver value, efficiency and a “greener” approach across all lines of service, leveraging a modernized state infrastructure.

3. Accountability & Performance: Drive better decision-making and organizational effectiveness through open and consistent use of performance measures.

4. Expertise & Commitment: Attract and retain a highly-skilled and engaged workforce that is equipped with appropriate tools and training opportunities in a supportive environment.

5. Shared Services: Enable cost savings and better government through shared solutions and cross-boundary partnerships.

6. Transformation & Economic Competitiveness: Transform government service and Michigan’s economic vitality through innovation and the depth, breadth and strength of DTMB.

DTMB has the following objectives for this contract: 1. To provide effective support and enhancement to the client agency contact centers. 2. To minimize the total cost of ownership of the customer contact centers. 3. To leverage the same hardware architecture across all contact centers. 4. To keep up to date with new releases of software from the COTS providers. 5. To develop DTMB staff as full partners with the Contractor staff. 6. To minimize the use of custom code and to migrate to “out of the box” functionality. 7. To provide new technology that will allow efficiency and effectiveness gains. 8. To use the same software configurations across all contact centers for the same functions. 9. To provide an entry-level Siebel configuration for new agencies with minimal requirements. 10. To assist DTMB with opportunities to leverage solutions for cross-boundary partnerships. 11. To assist DTMB in helping customer contact centers to enhance/improve their customer service.


31

Over the years, DTMB has established a shared IT support service center, known as Michigan Enterprise Contact Center (MiECC), to provide centralized support to the State of Michigan (SOM) contact centers across multiple agencies. The MiECC goals are - Unified, cost-effective and efficient contact center support services for SOM. Easy access of Government services to Michigan citizens. Excellence in customer service.

Today, MiECC supports contact centers at eight (8) agencies - Civil Service Commission (MCSC) DTMB-Client Service Center (CSC) DTMB-Office of Retirement Services (ORS) Environmental Quality (DEQ) Human Services (DHS) Licensing and Regulatory Affairs(LARA) – Bureau of Health Professions(BHP) State (MDOS) Treasury

All of the above contact centers serve the citizens of Michigan except Civil Service and DTMB-CSC contact centers which primarily support the State’s employee population. The State also has a few contact centers outside of the MiECC, which in the future may require support from the MiECC and this contract. The support services currently offered by MiECC are - Multi-channel support:

Contact center CRM Interactive Voice Response (IVR) Computer Telephony Integration (CTI) Skills Based Routing Reporting service Workforce Management Web self service Email service Web knowledge management Integration with Document Management Quality Assurance: Call Recording Call Monitoring

MiECC is currently working on implementing Virtual Hold Technology for one of its contact centers and the service will soon be offered to other contact centers. MiECC has identified the following standard products currently used to provide contact center functionality:

Telephone Switch – Avaya and Cisco CRM Software - Siebel Computer Telephony Integration – Genesys Call Monitoring and Recording – NICE Interactive Voice Response (IVR) – Genesys Voice Portal Document Management – FileNet IVR Monitoring - Empirix

Most of the contact centers (MCSC, LARA-BHP, DEQ, DTMB-ORS, MDOS, Treasury) have the Siebel product as their core CRM software. The Siebel application at MCSC is out of the box and the infrastructure is currently shared with LARA-BHP and DEQ. Other Siebel solutions were initially implemented as stand-alone customized versions, each separate from the other contact centers and using different integrators.


32

MiECC has also established a shared enterprise database architecture. The Oracle servers are shared among six agencies - MCSC, LARA-BHP, DEQ, DTMB-CSC (Genesys), MDOS and Treasury. There are two production servers (primary and secondary node) and two test servers. MCSC, LARA-BHP and DEQ have one shared Oracle instance. DTMB-CSC is currently undergoing a project to implement a Genesys 8.x IVR solution. This solution uses SIP technology, has built-in redundancy and uses all virtual servers. MiECC envisions the architecture to be shared among other agencies and to be used as an enterprise Genesys platform. MiECC has established an enterprise NICE infrastructure for call recording and monitoring. The enterprise NICE environment is currently shared between MCSC, DTMB-ORS and Treasury. Number of customer contacts for the Calendar Year 2010: (The shaded areas are not currently supported by MiECC)

IVR Self service

Agent Calls

Web self service

Email service

Web / eService request

Paper Channel – Inbound

Paper Channel - Outbound

Civil Service Commission

NA 115,23

2 NA 5,417 NA 40,148 15,000

DTMB-Client Service Center

UPCOMING

190,000

NA 75,000 300 33,900 NA

DTMB-Office of Retirement Services

NA (part year)

285,168

146,062 5,000 NA 145,132 343,700

Environmental Quality

NA 19,000 NA NA NA NA NA

Human Services

705,047 NA 1,701,15

9 NA NA NA NA

LARA-Bureau of Health Professions

NA (New in 2011)

125,000

NA NA NA NA NA

State 1,465,993

1,191,224

NA 31,817 66,791 >100 18,209

Treasury 802,695 349,97

2 715,688 2,741 21,109 307,735 993,976

For Agency Background Information, see Attachment 8. .

1.100 Scope of Work and Deliverables

1.101 In Scope

The contractor shall provide a team to support and enhance the identified eight contact centers. The contractor shall provide the following services:

1. Knowledge transfer from existing contractor. 2. Base Support 3. Major Enhancements (including new functionality or new contact centers)


33

4. Optional: Software Licenses The State reserves the right to add contact centers, under this Contract through Contract amendment. The scope of the agreement will consist of support of the following software components:

i. Siebel ii. Siebel interfaces iii. Scheduled/Ad-hoc reports (SQL). iv. Batch (from Oracle legacy extract to Siebel Base) v. Genesys (CIM Platform, GVP, CTI - Gplus Adapter, WFM, Genesys reporting, Interaction

Workspace etc.) vi. NUANCE Speech technologies vii. FileNet Capture, FileNet CRM Integration Suite (CIS) viii. FileNet Inbound Document Linker (IDL), VB script ix. New implementation of existing in scope technologies that are implemented under this Contract

which shall be agreed upon through SOW. x. Virtual Hold Technology , only for DTMB/ORS (other Agency VHT deployment would be

considered Major Enhancement, and the base cost for that agency may increase) xi. NICE recording and monitoring platforms, only for DTMB/ORS xii. Integration with peripheral software, such as SYMON and Empirix xiii. New technologies that are implemented under this Contract

Treasury has a customized Visual Basic application for scanning/indexing operation that augments with FileNet Capture and IDL (FileNet Inbound Document Linker). State staff does not maintain anything relating to IDL, VB executable, FileNet Capture configurations and the FileNet CIS products at Treasury. The contractor shall be responsible for this work at Treasury and for any other requesting agency in the future, which shall be agreed upon through a SOW.


34

Optional: The State reserves the right to purchase software licenses, training, services, maintenance and support used at the contact centers. Examples of these software are - Genesys, NICE, NUANCE, Virtual Hold and Empirix. These additional purchases will require an amendment to the Contract and may require approval from the State Administrative Board.

A more detailed description of the software, services (work) and deliverables is provided in Article 1, Section 1.104, Work and Deliverables.

1.102 Out Of Scope

1. The business operation of the contact centers. 2. The actual operation of the program management office. 3. Purchasing equipment. 4. Infrastructure installation. 5. Purchasing software. 6. Providing customer service representative staff. 7. Providing contact center agent software administration (e.g., new agent setup, etc.) (the Agencies shall

be responsible for this with Contractor available to assist on temporary basis upon request and staff availability).

8. Providing Nice recording and monitoring platforms administration (DTMB shall be responsible for this with Contractor available to assist on temporary basis upon request and staff availability).

The following are excluded from the scope of technical support - i. Hardware server support including the operating system ii. Desktop support iii. Avaya Switch iv. Data and Voice Connections v. Oracle/SQL Server Database Administration vi. Websphere vii. Xenos viii. Avaya vectors ix. T1 Trunk lines x. Cisco Equipment xi. FileNet Image Services/P8

1.103 Environment

The links below provide information on the State’s Enterprise information technology (IT) policies, standards and procedures which includes security policy and procedures, IT strategic plan, eMichigan web development and the State Unified Information Technology Environment (SUITE).

Contractors are advised that the State has methods, policies, standards and procedures that have been developed over the years. Contractors are expected to provide proposals that conform to State IT policies and standards. All services and products provided as a result of this CONTRACT must comply with all applicable State IT policies and standards.

Enterprise IT Policies, Standards and Procedures: http://www.michigan.gov/dmb/0,1607,7-150-56355---,00.html

All software and hardware items provided by the Contractor must run on and be compatible with the DTMB Standard Information Technology Environment. Additionally, the State must be able to maintain software and other items produced as the result of the Contract. Therefore, non-standard development tools may not be used unless approved by DTMB. The Contractor must request, in writing, approval to use non-standard software development tools, providing justification for the requested change and all costs associated with any change. The DTMB Project Manager must approve any tools, in writing, before use on any information technology project.


35

It is recognized that technology changes rapidly. The Contractor may request, in writing, a change in the standard environment, providing justification for the requested change and all costs associated with any change. The State’s Project Manager must approve any changes, in writing, before work may proceed based on the changed environment. Enterprise IT Security Policy and Procedures: http://www.michigan.gov/dmb/0,1607,7-150-56355-107739--,00.html The State’s security environment includes:

DTMB Single Login. DTMB provided SQL security database. Secured Socket Layers. SecurID (State Security Standard for external network access and high risk Web systems)

DTMB requires that its single - login security environment be used for all new client-server software development. Where software is being converted from an existing package, or a client-server application is being purchased, the security mechanism must be approved in writing by the State’s Project Manager and DTMB Office of Enterprise Security. Please see Appendix K for Department of Treasury’s additional security requirements. IT Strategic Plan: http://www.michigan.gov/itstrategicplan IT eMichigan Web Development Standard Tools: http://www.michigan.gov/documents/Look_and_Feel_Standards_2006_v3_166408_7.pdf The State Unified Information Technology Environment (SUITE): Includes standards for project management methodology (PMM), systems engineering methodology (SEM), and associated forms and templates – must be followed: http://www.michigan.gov/suite Technical Environment

Michigan Enterprise Contact Center

Technology Overview

Technology MCSC DTMB-CSC

DTMB-ORS

DEQ DHS LARA-BHP MDOS Treasury

CRM Siebel CRM Base 7.8 Y Y Y Y Y Y

Siebel eServices Y Y Siebel Tools Y Y Y Y Y Y

Siebel Smartscript Y Y Y Y Y Y

Siebel Reports Y Y Siebel Public Sector option Y

PBX Switch

Avaya PBX 3.1.x Y Y Y Y Y Y Y Y

AES 4.2 Y Y Y Y Y Y Y


36

IVR

GVP 7.6 Y Y Y Y Y Y

GVP 8.x Y

CTI Genesys Gplus Adapter 7.x Y Y Y Y Y

Intelligent Call Routing Genesys skills based routing Y Y Y Y

Reporting

Genesys VAR 7.6 Y Y Y Y Y Y

Genesys CCPulse 7.5 Y Y Y Y Y Work Force Management

Genesys WFM 7.6.1 Y Inbound Call Load Testing

Empirix "Hammer" Y Y

Voice Monitoring

Empirix voice watch Y Y Call Monitoring and Recording

NICE Perform 3.1 Y Y Y Y

Document Management

FileNet 4.x Y Y Y Y Y FileNet Connector to Siebel Y

Note: FileNet is used at many agencies for document management but at this point, only Treasury has FileNet integration with Siebel and a customized VB application for scanning/indexing which are supported by the contractor.

For Agency Environment Information, see Attachment 9.

System/Software What does it do?

Avaya - Avaya provides the telephone "switch". - Automatic Call Distribution (ACD) system - distributes calls from the switch to the appropriate path based on customer selection of options. Provides basic information on calls at various points in the call flow process.


37

- CentreVu Supervisor provides limited "live" status information to supervisors and historical information for monthly reporting by agent and work units. - Once calls are turned over to Genesys, tracking is via CCPulse. - CMS reporting tool.

FileNet Serves to image inbound correspondence service requests, which is then "indexed" to the appropriate account and reason for contact in order to be directed to the appropriate team within CRM. - IDL – Inbound Document Linker, links inbound correspondence images to Siebel Service Requests. - CIS – CRM Integration Suite, provides connection from Siebel to FileNet for viewing of images.

Genesys - Interactive Voice Response (IVR) system. Automated call handling system that provides account specific information (after caller verifies account information) related to refund status, estimated payments, etc. - Provides the Computer Telephony Integration (CTI) functionality within CRM for screen pops (account related to the call appears on the CSR's screen) - CCPulse provides "live" status and historical statistical information on calls routed to agents. Reporting functionality has been developed and is being developed further. Should replace CentrVu supervisor in the future. - VAR - Reporting system for IVR contacts; provides information based on tax type, call path and resolution (either call ended in IVR or transferred to CSR.

NICE Quality assurance software that works in conjunction with Genesys CTI and CRM to provide random recording of calls (and could be email responses) for evaluation and training purposes. Also serves as "on-demand" recording for CSR initiated call recording for irate or threatening calls. The system also provides a variety of reports related to the evaluation of calls and correspondence/web SR's related to CSR, evaluator and group performance

Siebel/CRM Customer Relationship Management System - serves as the basis for call, email (general questions), web service request (account specific info) and correspondence handling. System is updated via interfaces with existing/legacy systems.

Tidal/Opalis Scheduling software used to move data updates from legacy systems (and SAP) into CRM. Data must be in CRM in order for customer access in self-service applications such as the IVR and web self-service actions.

Xenos Interface for outbound correspondence from legacy systems that creates images for loading to FileNet, so that images are available for viewing in Siebel.


38

Enterprise NICE environment: DTMB has established a shared enterprise NICE environment. NICE PERFORM 3.1 Application Suite is used as the digital multimedia monitoring and recording solution. Currently the solution is implemented at MCSC, DTMB-ORS and Treasury. The hardware includes a NICE Logger for Voice Storage; Screen Capture and Logger for navigation recording; and the NICE Call Logging System (CLS) for storage of call details. The software components include NICE Universe, Scheduler, Forms Designer and List Editor, Evaluator, Monitor, Web Reporter, and Record on Demand.

1.104 Work and Deliverable

I. Services and Deliverables To Be Provided

A. Base Support

The Contractor shall provide the following, as part of the Base Support cost: 1. Break-fixes and troubleshooting, 2. Product/software upgrades and patches, 3. Application/Technical Monitoring, 4. Minor Enhancements

a. As agreed upon through Contact Center Strategy, Agency Enhancement Plans, and monthly Operational meetings for in scope software supported

b. Up to 200 total hours annually of IVR enhancements 5. Research and analysis, 6. Testing, 7. Assist in infrastructure planning/upgrades, 8. Training, and 9. Contact Center Strategy.

The state shall buy annual maintenance from the software vendors. The Contractor shall be responsible for contacting the software vendors for problem resolution or research for software under valid maintenance contract.

Minor Enhancements are less than 200 hours and must follow SEM Maintenance process. Product upgrades may require more than 200 hours but considered as part of Base Support.

For product upgrades or application enhancements, the Contractor shall provide the State of Michigan with a detailed project plan (technical work plan) before the Contractor starts working.

a) Requirements for Base Support:

a. Break-fixes and troubleshooting The Contractor shall work with DTMB and agencies to help reduce the number of high priority tickets resulting in more stable, high uptime production environments. Contractor shall meet service level agreements by leveraging the State of Michigan’s Remedy system as the point of entry and status system of record for support issues. The Contractor shall also utilize the DTMB Service Management Center in monitoring State wide incidents and changes. For issues that require in scope software support, the Contractor shall continue to contact the vendors on behalf of the State of Michigan annual support contracts to further triage the issue and execute documented request for change (RFC) procedures that includes obtaining required approvals for software change requests. For issues that require out of scope software, infrastructure and telecommunications support (e.g., server reboots, database administration, firewalls, etc.), DTMB shall execute documented request for change (RFC) procedures that include obtaining required approvals for infrastructure change requests. If the issue cannot be resolved through the normal

Break/Fix

The Break/Fix work type is used if there has been an interruption of a critical service to an agency. An action and a solution are required, even if the solution is temporary. It is required to investigate the problem to determine the root cause. The permanent solution to the problem may result in the initiation of another work type.


39

support channels, the Contractor shall engage the vendor through internal relationship channels to escalate the issues appropriately within the organizations.

Break/fix support shall consist of: “Lights On” support/Break/fix support for production applications Remedy system problem management Production Troubleshooting SLA’s reported and measured

Depending on the nature of the issue break/fix support may involve many different resources for issue resolution and follow-up. The Contractor shall involve necessary skilled resources to resolve break/fix issues.

All production support issues shall be initiated with a Remedy help desk ticket to the support team. The Contractor shall use Remedy for break/fix issue resolution.

The State shall provide vendor support login access (Siebel, Genesys,) as provided by State annual in scope software maintenance agreements and the access to create trouble tickets with these vendors to Contractor Base Support staff.

b. Product/software upgrades and patches The Contractor shall provide the ongoing in scope software upgrades as part of the Base Support team following the State of Michigan Systems Engineering Methodology (SEM) processes. The Contractor Base Support team shall work in conjunction with the agency and DTMB to provide software upgrade and patching services that helps mitigate the risk of application upgrade failure. Contractor also shall work with the software vendors to validate the upgrade path, product of end life, compatibility, review release notes and important configuration details during the SEM processes. Often times, the current version of software products have bugs that are still being reported and fixed. Contractor shall be an agency advocate for aligning the product upgrades with commercially stable products.

c. Application/Technical Monitoring The Contractor shall provide resources familiar with the agencies environment and software configuration, be available and ready to react to proactive alarms that are configured in the system. Contractor shall leverage proactive email, SMS and live monitoring to complement the existing skilled team to reduce the unplanned issues to these critical systems.

Monitoring the applications also involves monitoring the underlying infrastructure, servers, storage, general connectivity, and database. Contractor shall work with the DTMB Infrastructure teams to leverage the various enterprise monitoring tools available for the agencies.

Contractor shall improve the monitoring of applications by working with DTMB and call center agencies to identify monitoring services to add such as Vantage monitoring, proactive alerts, Empirix monitoring, disc (memory and CPU) monitoring, etc. as deemed necessary. Product upgrades and patches are a part of Base Support and the Contractor shall coordinate and plan with the agencies and DTMB using the State of Michigan SEM process.

There are several anticipated major upgrades as part of the contract. The Contractor shall coordinate and plan with the agencies and DTMB the following major upgrades as part of the annual Contact Center Strategy and Agency Enhancement Plan update processes:

Siebel 7.8 to Siebel 8.x Genesys 7.6 to Genesys 8.x Genesys CIM Platform from 7.6 to Siebel 8.x Oracle 10G to Oracle 11g FileNet Image Services 4.0 to FileNet P8 (except as described below) PBX upgrades


40

NICE for DTMB/ORS only Microsoft Server and Desktop upgrades and patches

For the FileNet patch Upgrade (from 4 to P8) from Image Services, the Contractor shall work with the FileNet vendor to determine compatibility and Upgrade path for the Treasury/MGA Scanning Form, FileNet Indexing Form, and FileNet/Siebel Inbound Document Linker. Depending on outcome of analysis, the Contractor shall finalize scope and resources needed to provide comparable functionality as currently exists.

If an Upgrade path exists, services shall be considered in scope of Base Support. If an Upgrade path does not exist and/or different software and/or skill sets are needed, a mutually agreed upon SOW shall be negotiated and issued so that comparable functionality can be provided with the FileNet P8 Upgrade as exists today.

In the event that a software vendor does not support a product Upgrade path or a product Upgrade requires integration with new software solutions not in existing configuration with product suite, the Contractor and State will mutually agree upon course of action which may include a SOW. d. Minor Enhancements As part of Base Support, the Contractor shall provide Minor Enhancement services for in scope software.

Contractor shall work with the agency and DTMB specifically during annual project planning cycle and regular monthly agency operational meetings to collect the Minor Enhancement requests. Contractor shall use the agency tool of preference i.e. Serena and/or the State of Michigan Remedy system to record the Minor Enhancement requests. Minor Enhancements shall be classified as work estimated to be less than 200 hours in effort and shall follow the State of Michigan Maintenance methodology. Depending on the scope, complexity, State and Contractor resource availability, and State desired implementation schedule of the Minor Enhancement Contractor shall work with the DTMB program manager to determine whether a SOW shall be executed and a project manager shall be assigned. Contractor shall also work with the DTMB Program Manager to understand any schedule and resource constraints among the agency, DTMB, Contractor teams to schedule and complete the Minor Enhancement requests. Table 1 indicates the high level responsibilities for each of the participating teams.

DTMB Customer Agency Contractor Communicates Enhancement Requests � � Agency Request Tool updated � � Create Work/Delivery Estimates � � Prioritization � � � Approval � � SUITE Processes Determined � � � Work Begins � � �

Table 1. Minor Enhancement initiation roles

Minor Enhancements shall be included as part of Base Support and a Minor Enhancement shall be less than 200 hours of estimated effort and shall be coordinated and planned with the agencies and DTMB using the State of Michigan SEM process. See Error! Reference source not found..

Project Size (Effort) Methodology To Use

0 – 200 hours System Maintenance process 201 – 1000 hours System Maintenance process 201 – 1000 hours SEM Express (enhancements) 1001 hours or larger SEM

Table 2. Project Size


41

The Contractor shall work with the DTMB Program Manager to determine whether DTMB project manager shall be assigned by the State.


42

e. Research and analysis The Contractor Base Support team shall provide research and analysis services using Contractor internal knowledge stores and vendor alliances. Upon agreement through a SOW, the Contractor may bring industry expertise (e.g., subject matter advisors) to provide global perspective on the challenges facing the State of Michigan Enterprise Call Center.

f. Testing Contractor shall provide component, system, and integration testing services for the in scope software. Contractor shall leverage the State of Michigan’s SEM methodology as it relates to the testing phases of a Product Upgrade, Patch, and Minor/Major Enhancement.

State staff is an integral part of the testing process. State staff shall plan, execute, and validate User Acceptance Test scripts. This provides on-the-job experience that helps "train" the eventual users of the system Contractor will use the existing defect tracking tool or an equivalent State enterprise approved test defect tracking tool, to expedite test defect resolution.

g. Assist in infrastructure planning/upgrades As part of Base Support, the Contractor shall assist in infrastructure planning and upgrade projects as related to the in scope contact center software.

During infrastructure planning activities, Contractor shall look to reduce the physical server footprint and move to virtual servers where appropriate. When appropriate, the Contractor shall also continue to recommend leveraging available server and application capacities in the Enterprise environment.

h. Training The Contractor shall work with the State of Michigan when training is needed for a project, Upgrade or Minor Enhancement. The Contractor shall train agency identified trainers. In turn, trained State trainers shall provide training for State contact center agents.

For formal classroom\online technical software package training, the Contractor recommends attending the software vendors “University” style course and shall assist in recommending the appropriate courses.

Contractor shall provide system administration training for designated State call center agent administrators as part of the Base Support services. The State shall provide day-to-day call center agent administrators who will maintain call center agent set-up for in scope contact center software. The Contractor shall provide training as described below:

Train the trainer Technical training for State personnel who will be working with the Contractor to configure the

applications including establishing databases and interfaces, data conversion, customization, and upgrading the customized software.

System administration training for State personnel who will be responsible for ongoing maintenance and administration of the system, including security.

Mentoring State-assigned DTMB staff enabling them to become full-valued members of this support team.

The Contractor shall provide training in a variety of formats for product installation, use, and administration for a variety of levels (e.g. basic, advanced, refresher, etc.) based upon approach agreed upon with DTMB and agencies documented in the SOW, release plan or project plan. All training manuals, training plans and other documentation provided shall become the property of the State.


43

For Base Support in Scope services, the Contractor shall provide training services as part of Base Support services and hence, the cost of training shall be included in the Base Support cost. For SOW services, the Contractor shall estimate and provide training services as agreed upon in SOW.

a) The Contractor shall provide all requirements listed in this section, and provide detail regarding how they will accomplish these requirements

Train the Trainer The Contractor shall provide “train the trainer” services as required for major SOW project implementations and upgrades, which allows users to focus on content and processes applicable to their job function. Based on training specifications set forth in a SOW, release plan, or project plan, Contractor may provide the following types of “train the trainer”:

Scenario based training that increases skill development through realistic learn-by-doing relevant job-related functions.

Class room training with instructor and training manuals. Audio and video clips to provide real life simulations that are readily available for reuse with end-users. The Contractor Team shall solicit support and review from the Agency business analysts, which

facilitates understanding of the purpose and mechanics of the system skills they are teaching, and enables a focused job-specific training session or module.

Technical Training for State Personnel Who Will Be Working with the Services Contractor to Configure the Applications including Establishing Databases and Interfaces, Data Conversion, Customization, and Upgrading the Customized Software The Contractor shall collaborate with DTMB and Agencies to train staff. This enables high performance and reliable delivery on State-assumed MiECC functions. Contractor shall provide on-the-job training for the State technical personnel who will be working with them to configure the applications. On-the-job training shall consist of State assigned resources shadowing Contractor staff and working on Remedy support tickets.

System Administration Training for State Personnel Who Will be Responsible for Ongoing Maintenance and Administration of the System, Including Security The Contractor shall respond to training requests, direct support staff to train State of Michigan personnel, and work with staff in on-the-job shadowing roles as determined in the Contact Center Strategy, release plan, project plan, or SOW. The Contractor shall support the approved training approach with Base Support team.

Mentoring State-Assigned DTMB Staff Enabling Them to Become Full-Valued Members of this Support Team The Contractor shall provide ideas to proactively assist the State of Michigan in becoming more self-sufficient and improve maintenance efficiency. The Contractor shall use job shadowing and mentoring to help DTMB team members develop technical support skills.

The Contractor shall train new call center agencies that join the MiECC supported agencies through a SOW.

Upgrades and New Versions to the System that Affect End-User Functionality include Training at No Additional Cost (e.g. Classroom or Online Training, Training Flier, Release Features, etc.)/ The State Anticipates that the Base Support Team Shall Provide These Trainings and Hence, the Cost of These Trainings Shall Be Included in the Base Support Cost The Contractor shall provide training for upgrades and enhancements that change user system functionality as part of Base Support services.

Training is Provided in a Variety of Formats for Product Installation, Use, and Administration for a Variety of Levels (e.g. Basic, Advanced, Refresher, etc.) / All Training Manuals, Training Plans and Other Documentation Provided Become the Property of the State The Contractor shall provide training as agreed upon in a SOW, Call Center Strategy, or Agency Enhancement Plan.


44

The Contractor’s training approach shall consist of the following methods: “On-the-job” activities (shadowing) – The Contractor shall pair a State of Michigan resource with a

Contractor resource to “learn-by-doing”. State resources shall make time to observe and to do while the Contractor resource looks on and provides guidance and feedback.

Formal Training Classes – The Contractor shall provide classroom/online Technical User training sessions conducted by a skilled individual from an application software vendor. This type of training is usually associated with specific software packages or tools. The Contractor recommends attending the software vendors “University” style course and shall assist in recommending appropriate courses. For example Oracle University, Genesys University, and NICE Training.

Informal Training Sessions –The Contractor shall provide training that takes place on-the-project, in an informal setting that consists of kick-off or orientation meetings, brown-bag discussions, small group sessions, or other agreed upon information method.

Technical Interchange Meetings – presentations and discussions conducted by a skilled individual from an application software vendor attended by the appropriate technical staff

Training manuals, training plans and other documentation provided by Contractor shall become the property of the State.

i. Contact Center Strategy The Contractor shall assist the State of Michigan in developing strategy with the contact centers. For strategic planning activities and assessments beyond the Base Support team, Contractor shall work with the agencies and DTMB to mutually agree upon a SOW in order to provide additional strategy planning activities. The State shall schedule Contact Center Strategy meetings using the State’s calendaring system.

As the Contact Center Strategy is updated, the Contractor Base Support team shall leverage the internal organization to assist the State of Michigan in planning for their contact centers.

The Contractor Base Support team shall work with DTMB and Agencies to update their Contact Center Strategy and Customer Agency Enhancement Plan annually as part of Base Support services provided.

i. The Contractor shall assist DTMB in devising the strategic plan for multi-channel contact center services across multiple agencies.

ii. The Contractor shall consult/assist about new technologies in the contact center arena and help in evaluating the tools.

iii. The Contractor shall assist the business managers in creating a contact center strategy and annual customer service enhancement plans.

iv. It is anticipated that each contact center will revise/ create its contact center strategy and annual customer service enhancement plans once a year. The Contractor shall provide this assistance on annual basis for a limited number of hours as part of the Base Support price for this contract.

v. Within 90 days of contract start date, the Contractor will work with DTMB to develop a Contact Center Estimation Model, that will be used to help predict future costs for an agency wishing to use this contract to obtain Enterprise Contact Center services.

a) The Contractor indicates how, and with what personnel, this will be accomplished

i. The Contractor must assist DTMB in devising the strategic plan for multi-channel contact center services across multiple agencies The Contractor shall assist with the creation, updating and maintenance of annual contact center strategy and individual agency enhancement plans for agencies within scope of this agreement. The agencies shall participate in planning and improving the investments made in the system. The Contractor shall commit to development and support of enterprise-wide and individual agency contact center strategic plans.


45

The Contractor shall assist in devising the strategic plans for the multi-channel contact center services across multiple agencies. The Contractor shall assist with the annual and monthly strategic planning activities.

ii. The Contractor will consult/assist about new technologies in the contact center arena and help in evaluating the tools The Contractor shall help identify, evaluate and recommend new technologies as they become available in the contact center software arena.

iii. The Contractor will be required to assist the business managers in creating a contact center strategy and annual customer service enhancement plans The Contractor shall work with the business managers to help develop Call Center Strategy and Agency Enhancement Plans. In addition to agency strategic planning activities, the Contractor recommends continuing use of the monthly operational meetings to brainstorm and devise enhancement and strategic plans to present to management teams.

iv. It is anticipated that each contact center will revise/create its contact center strategy and annual customer service enhancement plans once a year. The Contractor will be expected to provide this assistance on annual basis for a limited number of hours as part of the base price for this contract In order to meet the organization's objectives, it is critical that the agencies, DTMB and the Contractor work together on annual/ongoing strategic planning activities. The Contractor shall continue to provide assistance in creating and updating the annual strategy and enhancement plans in harmony with executive level strategy.

v. Within 90 days after contract start, the Contractor, working with DTMB, will develop an Enterprise Contact Center Estimating Model. This model will include applicable estimating factors and criteria that help provides the basis of estimation for determining the level of effort to a) develop a new Contact Center capability for an agency and b) maintain and support a Contact Center on an annual basis.

b) The Contractor indicates the number of annual staff hours (including staff description) that it proposes to make available for this purpose for each contact center

The Contractor shall make the Base Support team key personnel available for these activities. Consistent with prior year levels of involvement, the Contractor annual hours for this purpose shall be up to 80 hours for larger centers (MDOS, ORS Treasury) and up to 40 hours for the smaller contact centers (Civil Service, DEQ, DHS, DTMB-CSC, LARA). The Contractor’s technical and functional expertise shall be provided to the state as per these guidelines. Further assistance can be provided as State need is mutually agreed upon. Error! Reference source not found. further outlines DTMB and Contractor responsibilities associated with Contact Center Strategy.

Roles DTMB Contractor Program management - Organizing/scheduling/facilitate the annual planning meetings

�

Providing input into the planning process � �

Assist business managers in creating annual plans � �

Evaluate, consult and assist with new technologies � �

Table 3. Responsibilities in Contact Center Strategy Planning

b) The Contractor’s understanding of the terms: Break-fix/troubleshooting, Product upgrades/patches and Minor Enhancements.

The Contractor understands break-fix/troubleshooting, Product upgrades/patches and Minor Enhancements to be a part of a broader concept of Service Delivery within an Application Management portfolio as shown in Figure 1.


46

ServiceManagement

Account Management

ServiceManagement

OperationsManagement

Service DeliveryManagement

ServicePlanning

Operations Support

Production Support

Testing Services

Package Installation and Upgrades

Enhancements

Application Development

Application Maintenance

Service Delivery

ADM for Application Management

MI ECC 11.0027

Figure 1. Accenture Delivery Methods for Application Management

c) How the service delivery will be managed

Contractor shall manage service delivery jointly with the agency and DTMB using State’s established governance processes.

d) How the Base Support team will be staffed.

The Contractor shall staff the Base Support team as described in Table 4. Team Staffing.

Team Staffing Resource General Skills Norma Miller Contract Manager Single Point of Contact

Contract Administration

Ryan Sadler** Service Delivery Lead/Project Manager

Delivery lead (Project Management Professional (PMP), SUITE Contact Center Siebel, Genesys, NICE functional and technical acumen

Rajaram Loganathan** System Architect

Technical Lead Siebel and Genesys SUITE, NICE, Windows Server, Networking, Oracle, Workforce Manager, NICE

Pam Numerick** Siebel/Project Manager

Siebel, SUITE, FileNet

Ravi Jaiswal** Genesys Support Specialist

Genesys Framework, NICE, Genesys IVR

Manju Yeddanpalli Siebel Developer

Siebel, SUITE, Contact Centers, Workflow, reporting

Greg Blake Computer Telephony Integration (CTI)

Support

Genesys Framework, SUITE, Genesys IVR, CTI, AES, Avaya

Noel Espiritu Technical Application Administrator

Siebel, Siebel EIM, Oracle, Batch process, workflow

**Denotes Key Personnel Table 4. Team Staffing

With the exception of the Single Point of Contact, the Contractor’s Base Support team shall be dedicated to the MiECC project 100%, full-time of the standard work week (40 hours) taking into consideration holidays and vacation time


47

In the event a Base Support team member leaves the project, Contractor shall bring on a resource with a skill set comparable to the departing team member.

e) Achieving the SLAs (see Attachment 1)

The Contractor shall continue to staff the team appropriately with the right number of resources and skill sets to achieve the SLAs. Many times issues occur beyond the control of the Contractor team. For example, a server is unavailable. In those cases the Contractor shall continue to follow the DTMB issue management processes to route the issue with supporting details to the correct team for expedited resolution. During non-business hours Contractor shall have the right resources “on call” to respond to reported high priority issues. Service Level Agreement The Contractor shall provide support services that meet the agreed upon service level requirements. The State’s Remedy ticket system shall be used to initiate and manage break/fix and maintenance requests.

Standard Response Times Required for Problem Tickets Once a support ticket is assigned, the Contractor Base Support team shall take ownership of the ticket within the agreed upon Service Level Agreement time specified in Attachment 1. The Remedy and Outlook system are setup to enable a phone text message and email notification for the support team. The Contractor Base Support team shall maintain a continuous effort to resolve reported high and medium severity problems. The Contractor shall also work with DTMB support teams to resolve high severity level problems in as short a timeframe as possible. The Contractor shall use commercially reasonable efforts to fix the defect within the agreed upon Service Level Agreement. If the issue cannot be resolved within the service level, the Contractor shall notify and provide status reports as needed to the appropriate DTMB and agency management personnel.

f) The State’s contact centers operate on different schedules with regard to the timing of upgrade and point cycle releases (e.g. Department of Treasury does not upgrade systems during tax season). Managing schedule constraints between multiple contact centers should ensure that all support and enhancement activity occurs in a timely manner

The Contractor shall work with the DTMB program manager, agency services and the agency contact center managers to create a schedule for upgrades, maintenance and enhancement releases on an 18-24 month rolling plan that is acceptable to the agencies. This plan shall be reviewed weekly/monthly and adjusted as needed to confirm that the scheduled project activities are occurring timely as planned.

The Contractor shall staff the support team to enable both support work and new enhancement work be conducted continuously to minimize resource contention.

In the event of a schedule/resource conflict, the Contractor shall continue to work with the DTMB program manager and agency leads to find an agreeable solution.


48

g) DTMB team responsibilities and customer agency responsibilities

Table 5 sets forth the DTMB and Customer Agency responsibilities associated with Base Support.

DTMB Customer Agency

Strategic Planning � �

Operation of Program/Project Management Office �

Operations Oversight � �

Change Control Boards �

Business operation of the contact centers Agency �

User Acceptance Testing �

Application Regression Testing �

Internal administrative forms processing i.e. Secure id, Firewall, Telecom 906, network ID’s

�

Office Facilities �

L1 Help Desk �

Avaya Software �

Desktop support �

Purchasing equipment State of Michigan �

Infrastructure installation �

Purchasing software �

Hardware server support including the operating system

�

Avaya Switch �

Data and Voice Network �

Oracle/SQL Server Database Administration �

Websphere �

Xenos �

T1 Trunk lines �

FileNet �

NICE �

Table 5. DTMB and Customer Agency Base Support responsibilities

h) Monthly support hours report to the DTMB project manager

Base Support is a firm fixed price amount. The Contractor shall provide the breakdown of allocated monthly hours into five (5) areas: Support and Maintenance, Break Fix, Minor Enhancement, Major Enhancement, and Upgrades for the purpose or equitable distribution of relative costs across the agencies supported as part of the firm fixed Base Support.

i) The Contractor shall coordinate operational status meetings with each customer agency

The Contractor shall conduct operational meetings as agreed upon with each customer. The State shall schedule operational meetings using the State’s calendaring system. Some agencies may prefer a less frequent meeting schedule depending on the business and level of current activity.


49

DTMB shall provide (4) full time staff to the team. See Table 6 for the full time and non full time personnel.

Group 1 Full time (providing service) 1 Full Time

DTMB Program Manager – issue escalation, project planning Telephony specialist/Nice Administrator –Avaya, good understand of State of Michigan telecom

voice/data network, deep DTMB telecom processes and knowledge Siebel support staff – Siebel developer Oracle Database Administrator

Group 2 Non Full time (providing service)

Infrastructure Support (hardware, hosting environments) Enterprise Security SQL Database Administrator Avaya PBX/AES support Avaya programming Windows/Linux/UNIX Support Data Network support Desktop support FileNet Support Level 1 Help Desk Building Facilities

Table 6. Full time roles and other services

B. Major Enhancements

The Contractor shall treat Major Enhancements to existing applications or implementing new contact centers as separate projects each with its own SOW. Major enhancements consist of development efforts more than 200 hours. Sometimes, due to budgetary reasons, agencies treat a specific Minor Enhancement (or a group of enhancement requests) as a separate project with a SOW. The contractor shall follow appropriate SEM process (Maintenance, Express or Full) for the project.

For Major Enhancements, the State shall provide the SOW and the Contractor will respond with a proposal. In the proposal, the Contractor shall provide scope of work, assumptions, pricing, roles and responsibilities for Contractor and the State. Contractor shall provide resumes describing previous experience and education for new staff added to provide Major Enhancement services.

The responsibilities for these Major Enhancements project teams include: Work with Base Support Team to implement Major Enhancements beyond the scope of the Support Team. Transition on-going support of new system functionality to Base Support Team. Augment the skill sets of the Base Support Team. Augment the development capacity of the Base Support Team.

For Major Enhancements, the Contractor shall provide the State with a detailed project plan (technical work plan) before the Contractor starts working on Major Enhancements.

b) How the service delivery and Major Enhancement projects will be managed

In prioritizing the discretionary work of the Contractor’s team, the Contractor, DTMB and the agencies shall continue to work together through the established service delivery governance processes described in Section 1.104.I.A Base Support to verify that the teams are working on the right enhancements and issues at the right time in accordance with the goals and objectives of this contract. The Contractor shall work with the State to discuss the enhancement requests determining course of action whether to handle through a process change, current COTS functionality that can be configured, or customization.


50

The State of Michigan shall issue a SOW for any work that falls under the category of major implementation, that upon acceptance of proposal response to SOW and issuance of a purchase order by the State that Contractor shall schedule the enhancement according to the established governance prioritization and scheduling processes, and deploy the enhancement according to DTMB change control processes utilizing the defined Request for Change (RFC) procedures. The Contractor shall provide a rate card for these types of Major Enhancements. For every Major Enhancement, the Contractor shall provide a detailed plan with deliverables, tasks, ownership, dependencies and timelines.

Experience has shown that the Major Enhancement projects benefit when the Base Support and Major Enhancement teams are managed by a single individual, namely the assigned Project Manager as well as when Base Support staff involvement is planned for in the Major Enhancement processes especially the planning and requirements phases. This structure has produced consistency and cohesion for agency staff working with the Contractor team resulting in higher quality and more efficient development of Major Enhancements. The Contractor shall name one Project Manager to oversee the Contractor Base Support and Major Enhancement teams. The Contractor shall plan for Base Support team member involvement in Major Enhancement projects, and when agreed upon in the Major Enhancement SOW with the State. c) Description of the Contractor’s software development methodology specifically for the COTS software products in these contact centers

The Contractor shall use the State’s SUITE methodology and SEM processes. For COTS products, Contractor shall reference the Accenture Delivery Methods – Siebel extensions and CRM Delivery Methodology.

d) How the project team will be staffed

Section 1.201.A Contractor Staff describes standard roles needed to staff the Base Support team. The same standard roles shall be used to staff Major Enhancements. In the event a specific SOW requires additional roles not described in Cost Table 4 – Rate Card Table, the additional role description and rate shall be provided in the SOW.

The Contractor shall provide the necessary staffing of resources to complete the Major Enhancements. Subcontractors may also be utilized on an as-needed basis, depending upon the requirements (e.g., Siebel, IVR, Genesys, FileNet etc.).

The Contractor shall bring staff on to augment the development capability of the Base Support team and to work with the Base Support team to implement Major Enhancements that are out-of-scope for the Base Support team. The Contractor shall involve Base Support staff in the Major Enhancement projects to leverage Contractor Base Support staff's knowledge of the State's technical environment and processes, experience with the SUITE/SEM methodology and delivery of high quality upgrades, maintenance releases, and Minor Enhancement work. Once Major Enhancement work has been completed, the Contractor Major Enhancement staff shall transition on-going support for new system functionality to the Base Support team.

In addition to involving the Base Support team, the Contractor has over 100 resources local to the Lansing area that can be assigned to Major Enhancement work. This cost efficient workforce has technical skills that may support Major Enhancement work effort. As agency strategies are developed and specific enhancements funded, Contractor shall communicate the workforce skills and effort required to our Public Services Human Resources department. The Contractor shall make commercially reasonable efforts to staff Major Enhancement work with local cost effective Contractor employees.

The Contractor also has ten (10) Siebel Delivery Centers in the US. The Contractor team may draw from those centers for off-site use of Siebel development resources as needed to meet the budget and timeframe for Major Enhancements as mutually agreed upon through SOW.


51

e) The Contractor confirms that the appropriate SEM process shall be followed.

As an essential component of SUITE, the Systems Engineering Methodology (SEM) promotes the development of reliable, cost-effective, computer-based solutions. The Contractor shall deliver MiECC major enhancements using the SEM processes. Contractor agrees that enhancements less than 200 hours for which a SOW has been executed shall be delivered under the SEM Maintenance processes. Enhancements between 200 and 1000 hours shall be delivered under the SEM Express processes. Enhancements requiring greater than 1000 hours shall be delivered under the SEM Full processes.

f) Description of Contractor overall project development approach which will be followed for these Major Enhancements

The Contractor shall provide Major Enhancement work using the Accenture Delivery Methods (ADM) and State SUITE/SEM hybrid COTS development methodology. Figure 2 sets forth the development approach model that shall be used for Major Enhancement project work.

Enable Change

AccessDeploymentReadiness

Plan for Deployment

PrepareFor

Migration

AuthorizeDeployment

Set UpDeploymentEnvironment

ConvertData

MigrateTo

Production

Tran

sitionD

eplo

yed A

pp

lication

Ap

plication

Man

agem

ent

DeployAnalyze Design Build Test

Fine Tune Application

Perform Operational

Readiness Test

Support Production Environment

Perform Production Simulation

Prepare forDeployment

Repeat until deployment iscomplete

Confirm

MI ECC 11.0066

Roll OutApplication

PilotApplication

Figure 2. MiECC Project Development Approach

The major components of the Contractor methodology are described below along with the DTMB corresponding SEM lifecycle phases. The Contractor shall adapt ADM practices to SEM because the two methodologies share many similar functions, activities, and deliverables.

Description ADM/Siebel Framework SEM This phase involves the up-front, project-level planning required to select the packaged software, define the delivery approach, and confirm the project scope.

Plan Initiation and Planning

The primary goal of this phase is to gather specific requirements, both business and technology, across all in-scope areas to drive completeness in the breadth of the solution and help prioritize the development and release strategy.

Analyze Requirements Definition

The architecture, functional, and technical design phase takes the requirements from the prior phase and constructs an end-state functional and technical design and all the associated transition components (data conversion, integration design with legacy and vendor applications, etc.).

Design Functional Design and Technical Design

This phase utilizes the designs from Design to configure the application, and develop interfaces and/or conversion programs. Extensive testing of the individual modules and the integrated solution is needed to confirm production readiness and functional accuracy.

Build Construction


52

Description ADM/Siebel Framework SEM This phase utilizes unit- and quality-tested applications from the prior phase in conjunction with representative production data (volumes and breadth/completeness of data) to perform product and performance testing of the integrated applications with real users and subject matter advisors.

Test Testing

This phase includes the tasks and deliverables needed to deploy the application to the users and transition the application management responsibilities to the application management unit.

Deploy Implementation

Major Enhancement work shall be initiated by a request formally submitted in the form of a SOW by DTMB or one of the participating call center agencies. The Contractor shall respond to the SOW with a proposal describing the full scope of work, assumptions, State roles and responsibilities, pricing including ongoing fixed price support, resumes of new, proposed staff where requested, general timeframe, acceptance criteria, and pricing. The Contractor shall use the hybrid COTS project development approach to identify SUITE/SEM processes and deliverables required for work effort and document those in the SOW proposal. After the SOW has been agreed upon and executed, DTMB shall submit the appropriate paperwork for processing a purchase order in the State's MAIN system. Once the purchase order has been issued and received by the Contractor, the Contractor shall update the detailed, project work plan, assumptions, and responsibilities and meet with DTMB and call center agency staff to finalize project delivery schedule and commit resources. The Contractor and the State resources identified in SOW shall complete Major Enhancement work according to terms agreed upon through SOW processes. Once the Major Enhancement has been deployed, Contractor's Major Enhancement staff shall transition support of new functionality to the Base Support team. Final acceptance shall occur when appropriate DTMB and agency call center representatives sign project acceptance form after acceptance criteria identified in SOW have been met. Table 7 sets forth the responsibilities across organizations.

Responsibility DTMB Customer Agency Contractor

Prepare SOW � �

Respond to SOW �

Authorize SOW (signatures) � � �

Process purchase order �

Receive purchase order �

Update work plan and finalize schedule

� � �

Begin Work and Monitor Progress

� � �

Deploy Enhancement(s) � �

Transition support to Base Support Team

�

Obtain SOW final acceptance � � �

Table 7. SOW DTMB, Customer Agency and Contractor Roles and Responsibilities


53

g) The project timesheet and the monthly hours report will be submitted to the project manager

The Contractor shall submit project timesheets for Major Enhancement work with every monthly invoice and the monthly hours report to the State project manager where cost is based on hourly reporting, according to Reporting Requirements specified in Section 1.302 of this Contract. The report will provide detailed hours for each Contractor resource assigned to the mutually agreed upon SOW.

h) The Contractor provides a Sample Project Plan including necessary time frames and deliverables for the various stages of an implementation or change and the responsibilities MS Project plan or equivalent (check the SUITE/PMM standard)

The Contractor shall provide the State with a detailed project plan (technical work plan) before starting to work on any Major Enhancement activity. The Contractor shall work with the DTMB and call center agency to agree upon schedule and resource commitments prior to project initiation. When Major Enhancements involve other State or third party resource commitments or task dependencies, the DTMB project manager shall incorporate Contractor’s project plan into the master project plan.

The Contractor team shall follow the requirements identified and shall incorporate the additional requirements in the following ways:

Description of the deliverables to be provided. Contractor shall provide a description of project deliverables for each phase of work (e.g., Plan, Analyze, Design, Build, Test, etc.) as a standard component of SOW responses.

Timeframes and critical paths for deliverables. Contractor shall document deliverable timeframes and critical path as standard component of SOW responses.

Identification of roles and responsibilities. Contractor shall include a roles and responsibilities matrix as a standard component of SOW responses.

Internal Milestones and Task Durations. Contractor shall add critical path, internal milestones and task durations to the MS Project plan according to the SEM revised standards.

C. Business Requirements

Enhancement requests shall go through a business requirements gathering phase. i. The requirements gathering and analysis stage develops documentation based on the specific project

goals and constraints. Contractor shall be responsible for gathering business requirements for the contact center applications.

ii. The Contractor shall gather feedback from the business owner and other stakeholders, experts, and end users to determine how the application should solve the original business problem. DTMB and the agencies shall assign resources as deemed appropriate to provide feedback on business requirements to Contractor.

iii. The Contractor shall verify and validate requirements for in scope software throughout each phase of the development life cycle.

iv. The Contractor shall prepare a requirements traceability matrix. v. The Contractor shall describe the business requirements with use cases, scenarios, prototypes or other

relevant techniques in requirement gathering and documenting as agreed upon with stakeholders following SEM.

a) The Contractor confirms requirements listed in this section, and provide detail regarding how to accomplish these requirements.

The Contractor shall collect and document the requirements for the project using the SEM Methodology. The Contractor shall involve the agency business owners, DTMB, stakeholders, subject matter experts, and end users to get a clear understanding of the business problem. When using the SEM Methodology, the Contractor shall verify and track requirements using a traceability matrix in order to document the requirements throughout the project lifecycle. The Contractor team shall use scenarios, use cases, prototypes or other tools to help confirm the requirements are documented accurately.


54

b) The Contractor describes their requirements gathering and documentation methodology

Developing product life cycle requirements is important in defining the needs of relevant stakeholders. The Contractor shall develop requirements through collecting, analyzing, validating, communicating, and documenting customer and business needs.

Each phase of the product life cycle builds upon Requirements: The Requirements Gathering and Analysis stage develops documentation based on the specific project

goals and constraints. This stage includes collecting user/client feedback and information on system behaviors. The Contractor shall conduct a Requirements Gathering and Analysis stage based on specifications agreed upon for work efforts in the corresponding SOW or release plan.

The Design stage documents the collected feedback for future approval and validates documented requirements. The Contractor shall conduct Design stage for based on specifications agreed upon for work efforts in corresponding SOW or release plan.

The Development stage uses the approved documented requirements to build functionality into the system. The Contractor shall conduct a Development stage based on specifications agreed upon for work efforts in corresponding SOW or release plan.

The Build/Test stage verifies and validates that the requirements are operating according to documented business requirements. The Contractor shall conduct a Build/Test stage based on specifications agreed upon for work efforts in corresponding SOW.

The Contractor shall follow SEM/Suite methodology, and secure the Stage Exit approvals.

Contractor shall validate Requirements throughout each phase of the product life cycle to verify the goal of the requirements is met. The Contractor shall prepare and maintain requirements traceability matrix to track requirement throughout project life cycle.

The more visibility stakeholders have in the Requirements process, the more assurance the stakeholders have that Requirements are properly identified. Contractor shall involve key stakeholders (internal and external) in the Requirements development and analysis process. Key stakeholders (internal and external) shall participate in the requirements development and analysis process.

Requirements Gathering The Contractor shall complete Requirements gathering and analysis during the Analysis stage of Major Enhancement work efforts according to specifications documented in the SOW. The Contractor shall investigate with DTMB and agencies and document specific project goals and constraints as part of the Requirements gathering and analysis process. The Contractor shall obtain feedback from stakeholders, experts, and end users as specified in the SOW to determine application solution. The Contractor shall maintain requirements traceability matrices that verify changes in requirements throughout the project life cycle.

c) DTMB team responsibilities and customer agency responsibilities.

Resources from DTMB, Client Agency, or other key stakeholders shall participate in the requirements gathering and review process. Depending on the scope of work, the Contractor, DTMB, and Client Agency shall determine specific participants. For example, for a Minor Enhancement in Siebel, the process may only require a few specific Client Agency personnel. If the client wants to add a new document class in FileNet that routes to Siebel, the FileNet systems administrator will also need to participate. The Contractor shall ask DTMB and Client Agencies to participate in requirements gathering sessions, reviewing requirements documentation for accuracy, and providing input by meeting with groups of stakeholders to define requirements as specified in the SOW or release plan. The Contractor shall conduct a requirements review and sign-off at the end of the requirements phase to confirm that participating organizations agree with the requirements. Figure X provides an overview of the DTMB and Customer Agency responsibilities regarding business requirements.


55

Table 8.

Responsibilities of DTMB & Customer Agencies

d) SEM documentation standards will be followed for all projects.

The State of Michigan’s SEM documentation provides a clearly defined set of templates that gives consistency across all DTMB projects. The Contractor shall use the SEM for new work products. The SEM work products provide clients a consistent format presented to them for DTMB work products across vendors. The Contractor shall use the SEM documentation standards including, but not limited to the requirements traceability matrix, functional specification documents, and technical specification documents. D. Infrastructure Planning

i. For implementing new contact centers, the Contractor shall provide a detailed description of the infrastructure requirements.

ii. For adding new functionalities, if new hardware is required, the Contractor shall provide the hardware requirements.

iii. For hardware upgrades or reconfiguring the hardware, the Contractor shall assist in identifying the hardware needs.

iv. For hardware Upgrade projects, the Contractor shall be responsible for installing and configuring the software and deploying the application.

v. Contractor shall identify the issues about software and hardware compatibility. Contractor shall provide the roadmap of the vendor software products and Upgrade plans.

a) The Contractor shall provide detail regarding how Contractor will accomplish requirements listed in this section

i. Infrastructure Requirements for Implementing New Contact Centers During the requirements and design phase of a project, the Contractor shall work with DTMB and agencies to design architecture that maintains, enhances, and satisfies the State’s ongoing needs. The Contractor shall provide the SEM System Design Document to describe the infrastructure architecture plan.

Contractor shall work with DTMB to identify needs for new contact centers. New contact center applications may require new servers or could potentially leverage existing hardware. During the design stage of a project, the Contractor shall provide detailed hardware and software specifications to complete the design and build of the environment and document specifications in the SEM System Design Document.

For implementing new contact centers, Contractor, DTMB and Agency Service teams shall follow the steps listed below:

Initiate SUITE processes with a DTMB PMO office/Project manager

Determine requirements of the solution and confirm the business purpose is collected

Work with DTMB EA (Enterprise Architecture) and ISR (Infrastructure Service Request) teams as part of the architecture solution process to validate the solution fits into the State standards and future direction

Responsibilities DTMB Customer Agency

Participate in Requirements Gathering � �

Review and Provide Feedback to Documented Requirements

� �

Sign-off on Requirements �


56

Below are some of the standard State contact center hardware/software components that Contractor shall work with a new contact center. The number of servers, licenses, voice ports, desktops, redundancy, and security depends on decisions made during the initial assessment taking into consideration the cost, number of users, volume, business needs, and complexity. The solution may also include middleware components such as web/application software. Standard suite proven successful contact center environment components include:

1. Technical Environments Lab Development Staging/UAT Disaster Recovery Production

2. Application Architecture Siebel Web Servers Siebel Gateway Server Siebel Application\Reporting Server Genesys Framework Genesys Universal Routing Server Genesys Voice Portal

3. Software / Middleware Tomcat GPlus Adapter IIS

4. Database Oracle, SQL Server

5. Voice Telephony network Switches / PBX (Avaya) Avaya Application Enablement Services (AES) SIP Enablement Service (SES)

6. Network Infrastructure Load Balancer Firewall Email SMTP Switches

ii. Hardware Requirements if New Hardware is Required for Adding New Functionalities If an enhancement request is made and approved by the agencies or DTMB, the Contractor shall review the request. The Contractor shall first look to leverage the existing enterprise hardware/software to improve efficiencies and reduce costs. If enterprise sharing is not a reasonable option, the Contractor shall look to review and recommend new infrastructure to be established and configured for the new functionality. Contractor shall perform these actions:

Collect requirements for the solution

Review compatibility issues with current hardware

Review performance parameters for the software

Review hardware specifications, e.g. # of CPUs, Memory

Review security requirements with DTMB Office of Enterprise Security (OES)


57

Work with software vendor to understand the software and hardware specifications

Review performance and failover capacity, e.g. Load Balancing, Clustering

Work with DTMB infrastructure and telecom teams to fulfill requirements

iii. Identifying the Hardware Needs for Hardware Upgrades or Reconfiguring the Hardware DTMB uses a host of Intel/Windows family of servers for Enterprise Contact Center as well as Sun Solaris for the enterprise database environment. Different configurations of processors and memory are required depending on the environment in which it resides. Servers are regularly updated to the current patch level required by the hardware\software vendor. Contractor shall work with DTMB and the agencies to plan, upgrade, and maintain the Enterprise Contact Center hardware infrastructure with these goals in mind:

To provide effective support and enhancement to the client agency contact centers

To minimize the total cost of ownership of the customer contact centers

To keep up to date with new releases of software from the COTS providers

To develop DTMB staff as participating MiECC team members with the Contractor staff

To provide new technology that allows efficiency and effectiveness gains

To assist DTMB to with opportunities to leverage solutions for cross-boundary shared services

To assist DTMB in helping customer contact centers to enhance/improve their customer service

Table 9 describes Contractor’s approach for maintaining the technology of the State’s contact center hardware and software infrastructure.

Technology Upgrade Type

Contractor's Process for Supporting Hardware and Software Upgrades

Identify Upgrade Reqts

Business Impact Analysis and Release Plan

Support Proof of Concept

Release Coordination Management

Testing and Issue Management

Implementation Support

Hardware Upgrade Yes Yes Yes Yes Yes Yes Server

Upgrade Yes Yes Yes Yes Yes Yes

Server Reconfiguration

(Memory, CPU, Disk space)

Yes Yes Yes Yes Yes Yes

Software Patches Yes Yes Yes Yes Yes Yes Software Hot

Fix Yes Yes Yes Yes Yes Yes

Software New Release/ Version


New Software Packages


Table 9. Contractor's Process for Supporting Software and Hardware Upgrades


58

iv. Installation/Configuration of the Software and Deploying the Application for Hardware Upgrade Projects

Contractor shall work with DTMB to install and configure in scope software and deploy applications for in scope hardware Upgrade projects as described in the Call Center Strategy and Agency Enhancement plans.

v. Identify the Issues with Software and Hardware Compatibility and Provide the Roadmap of the Vendor Software Products and Upgrade Plans Contractor shall work with DTMB when performing Microsoft, Oracle and server patches on a quarterly or as needed basis. The software patches shall be first applied and tested in the non-production environments. If the tests are successful and change management process/RFC is approved, the patches shall be applied in production and monitored for any issues.

Test Lab Environment

The State intends to provide a dedicated MiECC test lab environment. The State’s inability to provide a dedicated test lab environment may impact the quality and timeliness of Contractor’s services which impacts will be addressed through mitigation plans agreed upon by Contractor and State within Statements of Work, Call Center Strategy, Agency Enhancement Plans, or Agency Operational meetings. When the State proceeds with efforts to provide a dedicated test lab environment, Contractor shall:

Work with DTMB to identify and confirm requirements for a test lab environment.

Use completed test lab environment to regression test and identify compatibility issues between contact center software/PBX and the desktop/phones/SOM M1 image of various agencies.

Figure 3 depicts recommended and proposed test lab environment.

Figure 3. Test Lab Environment


59

Product Roadmap for Call Center Enterprise Application and Upgrade Path

The Contractor shall work with DTMB, agencies, and vendors to maintain and enhance call center infrastructure and document during the annual Call Center and Agency Enhancement Plan update processes.

Contractor resources working in Siebel and Genesys technologies shall also receive monthly email newsletters regarding Siebel/Genesys Technologies to enable them to become well-informed Siebel/Genesys Technology practitioners.

Contractor shall review each vendor's product strategy to determine version applicability for the State's needs. The Contractor shall take into consideration stability, costs, compatibility, functionality and vendor support (statements of direction) between each application interface.

When a request is made for an application Upgrade in order to improve functionality or support new infrastructure architecture, Contractor shall review each vendor's product strategy to determine version applicability for the State's needs. Table 9 below represents an Upgrade path from the current installed version in the State environment. The table is meant to be a representation of the general approach to upgrading a major component of the contact center software. When a major software Upgrade project is considered and authorized, the Contractor shall conduct a more detailed analysis working close with the agency and DTMB to determine the overall benefits, costs, schedule, risks etc.

Table 10. Contractor’s general approach to upgrading a major component of the contact center software

clearly outlines the benefits of the upgrade

Activity Current Upgrade Path/Benefits

Siebel 7.8.2.16 Siebel 8.1.x

Benefits:

1. Minimal system downtime maximizes business continuity.

2. An Upgrade methodology that offers accelerated Upgrade cycle and significant cost advantage

3. Minimize dependency on Infrastructure upgrades by using the Upgrade Factory model

4. Minimal involvement of internal resources.

5. Leverage TCS Upgrade tools, accelerators and preferred practices

Genesys 7.6 Genesys 8.x

Benefits:

1. Interoperates with off-the-shelf hardware and supports open standards such as VoiceXML 2.1, CCXML, as well as Session Initiation Protocol (SIP) and related standards.

2. No rewriting of applications needed as a result of infrastructure changes.

3. Compatible with open or proprietary implementations: TDM, IP, or hybrid.

4. Flexibility to evolve Genesys Voice Platform with changing enterprise deployment needs.

5. Unlimited choices for adding speech technology


60

b) DTMB team responsibilities and customer agency responsibilities

Table 10 below sets forth DTMB and Customer Agency staff responsibilities for supporting infrastructure planning.

Table 11. DTMB and Customer Agency Infrastructure Planning Responsibilities

E. Training


Responsibilities DTMB Customer

Agency Strategic Planning � � Operations Oversight � � Operation of Program/Project Management Office � Business operation of the contact centers Agency � Change Control Boards � User Acceptance Testing � Application Regression Testing � Internal administrative forms processing i.e. Secure id, Firewall, Telecom 906, network ID’s

�

Office Facilities � L1 Help Desk � Avaya Software � Desktop support � Purchasing Equipment � Infrastructure installation � Purchasing software � Hardware server support including the operating system � Avaya Switch � Data and Voice Network � Oracle/SQL Server Database Administration � Websphere � Xenos � T1 Trunk lines � FileNet �


61


Agency

Identify staff and training needs Yes Yes

Identify trainers to be trained and staff attends training sessions for major SOW implementations.

Yes

Attend training sessions conducted by an application software vendor in a classroom setting. Accenture would recommend attending the software vendors “University” style course and would assist in recommending appropriate courses

Yes Yes

Coordinates the training sessions with the agencies and assists in setting up rooms, equipment for training

Yes

Participate in training that occurs on-the-project, in an informal setting, for example brown bag lunch topics

Yes Yes

Participate in presentations and discussions attended by the appropriate technical staff

Yes

Procure 3rd party training Yes

Table 11 includes responsibilities for DTMB and Customer Agencies associated with training State of Michigan Staff.

F. Documentation

i. The Contractor shall follow SUITE documentation standards. ii. The Contractor shall maintain documentation describing the application designs at all the contact

centers in accordance with best practices. iii. The Contractor shall validate the current documentation and where there are inaccuracies or

omissions; the Contractor shall make the appropriate changes. iv. As the Contractor makes changes to the applications, the contractor shall also update

documentation. v. Contractor staff shall create and update SEM required documentation as part of Base Support cost. vi. SEM required documentation shall be available to Contractor, DTMB, and agency staff in a shared

area provided by the State.

a) The Contractor shall provide all requirements listed in this Section and provide detail regarding how they will accomplish these requirements

i. The Contractor must follow all SUITE documentation standards Contractor shall use the State’s Systems Engineering Methodology (SEM) and the State’s Unified Information Technology Environment (SUITE) methodology to support and continuously improve the applications.

The Contractor shall use SEM as a guide to what methodology should be used: Full, Express, or Maintenance. The Contractor shall provide documentation and conduct checkpoints for reviews within the project lifecycle as specified for methodology selected. The Contractor shall use SEM to confirm that requirements and documents are verified as the project progresses.

ii. The Contractor will maintain documentation describing the application designs at all the contact centers in accordance with best practices The Contractor shall maintain SEM required documentation for each supported, agency contact center. The Contractor shall maintain documentation in accordance with leading practices.


62

iii. The Contractor will validate the current documentation and where there are inaccuracies or omissions, the Contractor will make the appropriate changes The Contactor shall update SEM required documentation that is incorrect or may have omissions. Project documentation consists of SEM required documentation and includes:

Application Architecture Diagrams Entity Relationship Diagrams Requirement documentation Project Design documentation Development documentation Support Documentation Training Materials

The DTMB-170 and other security documentation (State Security Documentation) forms shall be completed by the Office of Enterprise Security and Agency Services, with input from Contractor as needed. The State Security Documentation processes, documentation, and approvals are owned by the State of Michigan. The Contractor shall provide input as required such as architectural diagrams and data flows, and as requested, shall facilitate the submittal and approval of the State Security Documentation.

iv. As the Contractor makes changes to the applications, documentation will also be updated With each project release, the Contractor shall submit documentation updates as required by the SEM documentation standards. This shall include updating documentation such as hardware diagrams and Entity Relationship Diagrams when new functionality is added to the applications.

v. These tasks shall be completed as part of the Base Support cost. As part of the management of the Contact Center applications, the Contractor shall consider documentation tasks a part of Base Support services provided.

vi. All documents must be stored in a shared area provided by the state. The Contractor shall provide documentation in a shared area that is provided by the State. The State shall provide a shared area for documentation and grant Contractor staff access to the shared area location.


The Contractor, DTMB and the Customer Agencies shall be responsible for providing input and iteratively reviewing documentation based on acceptance criteria set forth in the Contract. The Contractor shall conduct and DTMB and Customer Agencies shall participate in structured document reviews within the project to help confirm that there is a mutual understanding of what is to be changed. Documentation sign-offs shall take place at the end of Requirements, Design, Testing, and at Delivery. DTMB and the Agencies shall participate in documentation review activities to confirm that parties have similar understanding of system changes. Table 12 sets forth the responsibilities of DTMB and Customer Agency staff.

Table 12. Responsibilities of DTMB and Customer Agencies associated with Documentation

G. Knowledge Transfer/Transition i. There will be Knowledge Transfer Period from the Contractor currently providing these services to the

new Contractor awarded this contract. ii. It is expected that during this transfer period the Contractor will gain a detailed operational

understanding of all the contact centers and the IT systems that support them.

Responsibilities DTMB Customer Agency

Participate in documentation reviews and provide feedback Yes Yes

Provide area to store shared documentation Yes Yes


63

iii. The Contractor will provide sufficient staff with the appropriate skills to undertake this knowledge transfer.

iv. It should not be assumed that the current support team will be free all the time during this period to update the Contractor since they will be engaged in supporting the various contact centers. Therefore a weekly timetable of meetings should be scheduled to facilitate Q&A sessions.

v. This Knowledge Transfer period is not to be used by the Contractor as training for their team in how to configure the various software products employed.

vi. This Knowledge Transfer period is for the on-site transfer of knowledge of the existing configurations in the various technologies of each of the contact centers to personnel of the new Contractor who are already fully skilled and proficient in the various products and their respective integrations.

vii. The Contractor will gain a detailed understanding of the interfaces from/to the various legacy systems connected to Siebel identified earlier in this document and interfaces with products previously identified which are maintained by DTMB.

viii. After the knowledge transfer period, the responsibility for support and identified work and deliverables will pass to the new Contractor.

Activities and Responsibilities

Table 13 below lists the major activities performed during the Transition Phase. Responsibility for some activities may be shared between DTMB and the current Contractor.

Legend: Responsible, Approval, Support, Inform, Consult

# Activities Responsibility New Contractor DTMB Current Contractor

1 Provide existing technical documentation. R S 2 Create a knowledge repository for managing the

documents and tracking the knowledge acquired R A

3 Understand application environments (dev, test, prod) R I 4 Provide demonstration of applications R S 5 Understand business processes and data flows R I S 6 Understand data models R I S 7 Understand call flows R I S 8 Understand architecture of application R I S 9 Review source code R I 10 Study sample past problem tickets of all severity types, and

their resolutions R I S

11 Study development and documentation standards R I S 12 Understand the development and support processes:

change & configuration management, testing, QA, user acceptance, release and problem management

R S S

13 Understand call handling, escalation, and communication procedures and standards

R I S

14 Update/create any missing basic documentation R I

Table 13. Transition Responsibilities by Organization

a) Recommended knowledge transfer period (in months) and start date

The Contractor is the incumbent vendor for the MiECC program; therefore, no knowledge transfer period is required.

b) An overview of the proposed transition plan

The Contractor shall continue operations and critical project work without disruption to the agencies business and resources. The Contractor shall need two weeks (10 business days) with members of the proposed team to accomplish the transition to the new contract.

The Contractor shall collaborate with the State to confirm this approach, capturing the State’s desires and direction regarding our proposed timeframes, content, participants, and speed of transition. The Contractor


64

shall focus on initiating the new contract, which shall include understanding the changes from the old contract as well as the State’s expectations for the new one. The proposed transition items to be completed over the (10) business days shall be:

Update risk management plans Provide suggested improvement on the report formats Update monthly reports process to conform to what is required Review and update the governance model Review and validate with the State project manager(s) the detailed project plan (technical work plan) Continue and complete existing work in progress Update the SOW template and processes to conform to any new requirements. Review and validate the State purchase orders and invoice submission process for the new contract Attend Contract initiation meetings

c) A timeline for the transition, with appropriate milestones. Tasks/Milestones should constitute elements of a successful knowledge transfer. Each task must show the responsibilities for all parties involved

Contractor’s proposed high level transition plan in MSProject is depicted in Figure 4.

ID Task Name Duration Start Finish Resource Names

1 Initiation 5 days Mon 3/5/12 Fri 3/9/12

2 Contract Start Date 0 days Mon 3/5/12 Mon 3/5/12

3 Orientation Meeting 5 days Mon 3/5/12 Fri 3/9/12 Accenture MiECC Team,DTMB

4 Planning 10 days? Mon 3/5/12 Fri 3/16/12

5 Detailed Project Plan (Technical Work Plan) 10 days Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team

6 Contract Transition 10 days? Mon 3/5/12 Fri 3/16/12

7 Organization Chart / Key Personnel Appro 10 days Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team,DTMB

8 Report Templates 10 days Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team,DTMB

9 Project Management Processes 10 days Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team,DTMB

10 Reviewing and updating the governance m 10 days? Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team,DTMB

11 Review and validate the SOM purchase or 10 days? Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team,DTMB

12 Updating risk management plans 10 days? Mon 3/5/12 Fri 3/16/12 Accenture MiECC Team,DTMB

3/5

Accenture MiECC Team,DTMB

Accenture MiECC Team







M T W T F S S M T W T F S S M T W T Fr 4, '12 Mar 11, '12 Mar 18, '12

MI ECC11.0114

Figure 4

d) Identification of risks and mitigation strategies

In Table 13 the Contractor provides several key risks and mitigation strategies.

Risk Mitigation

Treasury's Customer Contact Bureau applications risk support during 2012 tax season

Maintain existing Contractor staff through 2012 tax season.

Existing Enterprise Contact Center agencies risk support post-March 4, 2012

Maintain existing Contractor staff through 2012 tax season.

Table 13

e) A description of the Contractor’s plan for transferring knowledge/work from existing Contractors to new personnel

The Contractor shall staff the new Contract with the experienced resources that have extensive knowledge of the in scope items for the system.

f) The Contractor identifies their knowledge transfer team and provides skills description for knowledge transfer

The Contractor shall not require a separate knowledge transfer team.

g) A description of the roles and responsibilities during this phase for State of Michigan and Contractor responsibilities


65

Table 14 represents key activities and roles.

Table 14. Key Transition Activities and Responsibilities

Roles State of Michigan Contractor Responsibility/High Level Task Initiation Planning Detailed Project Plan (Technical Work Plan) Contract Transition Organization Chart / Key Personnel Approval Report Templates Project Management Processes Reviewing and updating the governance model Review and validate the State purchase orders and invoice submission process for the new contract

Updating risk management plans Execution - Base Support


66

h) Commitment on similar knowledge transfer to the future Contractor when this Contract expires

The Contractor shall be committed to provide the State of Michigan and/or future contractors with the knowledge transfer and transition services to help confirm that the systems are handed off when the Contract expires. The Contractor shall work with DTMB, agencies and the future contractor to validate that there is enough time and resources to effectively complete the knowledge transfer phase prior to the date when the Contract expires. H. RESERVED

I. Meeting DTMB’s Objectives

Contractor shall describe how it will help DTMB to meet all its strategic objectives, identified in Section 1.002.

a) The Contractor shall meet all requirements listed in this section:

1. To provide effective support and enhancement to the client agency contact centers. To provide effective support and enhancement to the client agency contact centers, the Contractor shall:

Work with DTMB and agencies to execute Call Center Strategy and Agency Enhancement plans deploying software releases that support and enhance client agency contact centers.

Use DTMB Remedy to monitoring and resolving support requests from client agency contact centers. Use Contractor’s network professionals, internal knowledge capital and vendor alliances to identify,

discuss, and incorporate CRM trends and leading practices.

2. To minimize the total cost of ownership of the customer contact centers. To reduce the total cost of ownership of customer contact centers, the Contractor shall:

apply the standard, developed methodology when implementing new customer contact centers identify enhancements, upgrades, infrastructure sharing opportunities, procedure changes for

implementation consideration during the Call Center Strategy and Agency Enhancement Plan annual update processes.

3. To leverage the same hardware architecture across all contact centers. The Contractor shall seek opportunities where agencies could share hardware but maintain their individual service levels and performance goals. During the Contract Center Strategy and Agency Enhancement plan annual update processes as well as during infrastructure assessments required for services delivered under a SOW, the Contractor shall assess and make hardware architecture recommendations to leverage existing hardware. Driving total cost of ownership down requires that the State use shared infrastructure environments to the highest extent possible.

4. To keep up to date with new releases of software from the COTS providers The Contractor shall maintain COTS software releases current according to the agreed upon projects prioritized in the annual Contact Center Strategy and Agency Enhancement plans.

Contractor shall provide the ongoing software upgrades as part of the Base Support team following the SEM processes.

5. To develop DTMB staff as full partners with the Contractor staff The Contractor and State teams shall work together to perform project tasks as a collaborative working team.


67

6. To minimize the use of custom code and to migrate to “out of the box” functionality The Contractor team shall work with each contact center agency during Requirements Gathering sessions to educate users on what the capability of the COTS products are - and matching business requirements to those 'out of the box' capabilities. The Contractor shall classify requirements as custom code or out-of- box functionality and work with DTMB and call center agency on work around business process solutions or on approval of custom code solution.

7. To provide new technology that will allow efficiency and effectiveness gains The Contractor shall continuously look for new ideas and validate with Contractor's Customer Relationship Management practice to evaluate new technology and new capabilities that will bring value to the State. The Contractor shall evaluate these innovations not just for technology's sake, but for the efficiency and effectiveness that it will provide to contact center agencies.

8. To use the same software configurations across all contact centers for the same functions As with using functionality 'out of the box', the Contractor recognizes that full benefits of COTS product implementations comes when leveraging products and configurations in a manner that can be shared across multiple agencies. The Contractor shall look for additional opportunities to build common configurations and leverage those across contact center. 9. To provide an entry-level Siebel configuration for new agencies with minimal requirements. The Contractor has created an entry-level Siebel configuration. Agencies that want to deploy call center capability quickly and do not have extensive configuration requirements shall use the Contractor's configuration to do this. Following the SEM methodology requirements, the Contractor shall implement entry-level Siebel configuration for an agency in 2 to3 months, although duration may be longer due to scheduling issues. The configuration shall provide the following, basic capabilities:

Email Response: automatically respond to customer emails Computer Telephony Integration capability: provide caller information to agents automatically Customer Dashboard: present a comprehensive view of critical information about a customer Contact Management: provide agents with a complete history of all interactions with a customer/contact Workflow Management: route and track tasks throughout their life cycle Service Request Management: automatic assignment of service requests to employees based on a

variety of factors, such as employee skills or organization Activity Management: associated activities to service requests to track work between an employee and

a customer/contact Literature Management: Manage and post FAQs, training manuals, and any other publications for

employees or customers Multi-channel support: voice, web, email, web collaboration

10. To assist DTMB to with opportunities to leverage solutions for cross-boundary partnerships The Contractor supports public/private sector and local government collaborations as a way to further enhance and leverage efficiencies that DTMB has in the Enterprise Contact Center solution. Especially with the entry level Siebel configuration, the State has a quick, cost effective way to help other entities 'test the waters' in the call center arena and prove value before making a major investment.

The Contractor shall work with DTMB to market and deploy the Enterprise Call Center solution across Michigan departments and agencies as set forth in SOW specifications.

11. To assist DTMB in helping customer contact centers to enhance/improve their customer service To help improve customer service, the Contractor shall assist agencies in identifying, collecting, and measuring the data points that define customer satisfaction for the agency. For some agencies, it may be the total time to process a request while for other agencies it may be measuring how the answer was delivered to the customer.


68

The Contractor shall: Support service level agreements defined herein, Work to reduce defect rates, Deliver project within timelines set forth in agreed upon project plans and statements of work, Deliver projects within budgets set forth in agreed upon project plans and statements of work


The DTMB team and the customer agencies play a significant role in meeting the strategic objectives for this contract. Together DTMB, customer agencies and the Contractor form a team sharing common goals for the Michigan Enterprise Call Center initiative.

DTMB plays many roles in helping support this contract. From management of the infrastructure such as the voice and data network, database servers to the project management office, and contract and procurement. DTMB is a critical team member for this contract's objectives. For the everyday projects and support, DTMB shall provide a program manager, telephony specialist, NICE specialist, Siebel developer and database administrator. The program manager plays as important role in the governance of the contract, communication and team activities. The telephony and NICE specialists provide the deep knowledge in the State voice and data networks and applies this knowledge to successfully deliver projects and support with the Contractor team. The Siebel developer role shall be critical in effective support and enhancement to the client agency contact centers and keeping up to date with new releases of software from the COTS providers. The DTMB database administrator shall keep the foundation of the application database secure and running effectively 24/7. The customer agency businesses are why DTMB and the Contractor set objectives in providing technology services. The customer agencies play a critical role in meeting their annual objectives and the objectives for this contract. The agency contact centers are the front line for providing services to the State of Michigan citizens. By communicating their challenges and requirements to the DTMB and the Contractor, the Contractor can work together to design solutions that meet requirements. The agencies also provide vital daily system user administrative functions for their contact center agents. By providing user acceptance, regression testing and approving system changes, the agencies help validate that the changes to the systems are what is expected. Table 15 provides key State responsibilities in meeting the objectives of this contract.

Area of Responsibility DTMB Customer Agency

Infrastructure Support (voice data network, servers, firewall, database)

�

Program Management �

Software user/agent administration �

User acceptance and application regression testing �

Proactive communication � �

IT standards �

Project and support Governance � �

Annual Strategic planning � �

Weekly MiECC meetings �

Monthly support operations meeting � �

Quarterly performance meetings � �

Telephony and Siebel State specialists �

License management �

Annual software vendor support renewals �

Contract management � �

Table 15. DTMB and Customer agency responsibilities for Contract objectives


69

J. Solution Center The Contractor:

i. Identifies their own center of excellence for contact center implementation and support. ii. The center of excellence will have the contact center technologies, as used in State of Michigan,

implemented in a test environment. iii. The Contractor’s centers of excellence will act as a knowledge source for the on-site Contractor staff

when complex problems arise. a. On-site Contractor staff shall be able to reach out to experts at these centers to help in problem

solving without extra cost to the State. b. It may also host examples of all new versions of the software applications and give guidance to

on-site Contractor staff. iv. The Contractor will describe any Contractor resources that shall be made available to on-site

Contractor staff

a) The Contractor confirms that they will provide all requirements listed in this Section and provides detail regarding how they will accomplish these requirements

i. Identify their own center of excellence for contact center implementation and support The Contractor shall provide requirements listed in this section. The Contractor team shall leverage the assets, skills, processes and technology in the entire Contractor network of professionals.

ii. The center of excellence will have the contact center technologies, as used in State of Michigan, implemented in a test environment The Contractor’s Global Delivery network, which includes Innovation Centers, Centers of Excellence, Infrastructure Outsourcing projects and Contractor supported clients, has an extensive number of contact center technologies including those used in the State of Michigan. The Contractor has Siebel, Genesys, Avaya, and Cisco environments implemented and supported in lab, development, test and production environments within its Global Delivery Center Network.

iii. The Contractor’s centers of excellence will act as a knowledge source for the on-site Contractor staff when complex problems arise The Contractor shall leverage resources available including the Contractor Global Delivery network in supporting the State of Michigan in meeting the Enterprise Call Center objectives. a. On-site Contractor staff shall be able to reach out to experts at these centers to help in problem solving without extra cost to the State

The Contractor shall look to support the State of Michigan in cost effective ways. As part of Base Support services, the Contractor shall leverage Contractor’s network of alliances, resources and internal knowledge assets to support the State of Michigan. The Contractor shall leverage all resources available including the Contractor’s Global Delivery network as in supporting the State of Michigan in meeting the objectives of this Agreement.

b. It may also host examples of all new versions of the software applications and give guidance to on-site Contractor staff

The Contractor Global Delivery network shall be the environment where new versions of industry software are available, tested and knowledge assets made available to the Contractor professionals working globally including Contractor’s local Lansing, Michigan based team.

iv. The Contractor describes Contractor resources that shall be made available to on-site Contractor staff The Contractor maintains global alliance agreements with Genesys, Oracle, and Empirix. Resources from these organizations shall be available to the local team. In addition, as needed, the Contractor local team


70

shall provide independent Contractors specialized in contact center technologies on a project basis which may result in increased costs as documented in a mutually agreed upon SOW.

b) The Contractor describes their own contact centers of excellence, the supporting team skills and what access the onsite Contractor staff will have to the Contact center of excellence team

The Centers of Excellence described above are a part of the Contractor Delivery Network. The Base Support team shall have access to Contractor global colleagues and contact center knowledgeable professionals in support of the MiECC program which may result in increased costs as documented in a mutually agreed upon SOW.

c) DTMB team responsibilities and customer agency responsibilities.

Other than awareness as listed in Table 16, DTMB and agency shall have no other responsibilities regarding Contractor Solution Centers.

Area of Responsibility DTMB Customer Agency

Awareness of the Accenture Delivery Network � �

Table 16. Solution Center Responsibilities

K. Encryption Since not all contact center agencies use sensitive data requiring encryption, Contractor shall work with DTMB and call center agencies to determine and document data encryption requirements and deploy an encryption solution for sensitive data in transit and at rest. After services described in this Section are completed, full data encryption of sensitive data shall be included in Base Support. Genesys software transmits sensitive data over the State supported network infrastructure. To ensure transmission of sensitive data is encrypted, the State’s Network Communication Infrastructure team shall enable and configure (e.g., use of SSL) data transmission for encryption based on data encryption requirements identified in encryption analysis completed by Contractor, DTMB, and call center agencies.

Client Data Protection Controls and Standards

The Contractor acknowledges that its clients, as data controllers / data owners, shall be primarily responsible for compliance with applicable data privacy laws. The Contractor, as data processor/service provider, is responsible to use client data only for specified purpose and in accordance with client instructions and client contracts. In addition, the Contractor shall have responsibility to keep client data secure and work with the State to help comply with its obligations under data privacy laws. To help clients protect their data, the Contractor has implemented its Client Data Protection Program which is focused on meeting our client’s security and privacy needs.

As part of our program, each Contractor service delivery team works very closely with the client to understand precisely what sort of data shall be exposed to and how that data should be handled. The Contractor shall implement controls to provide security in handling client data, and to implement any client-specified rule sets, policies or compliance measures. These controls include the following:

Allocation of senior level responsibility for client data protection for every project appointment of a dedicated data protection steward to support compliance with the client’s data protection requirements.

Clear documentation and communication of the client’s requirements to Contractor personnel with access to client data


71

Data protection training for all Contractor personnel on a client project (this can be client specific where this is stipulated)

Procedures for managing security incidents with full client involvement

Standards for secure transmission, storage, back up and destruction of client data

Technical, organizational and physical security controls including hard drive encryption for laptops and other removable media, physical and logical access controls and employee background checking.

Periodic audits by our Data Privacy Compliance Team of service delivery teams to confirm compliance with the client’s instructions and data privacy policies as well as the standards and controls set out above.

MiECC Data Protection

Contractor piloted its data protection compliance program at MiECC in the fall of 2007. Staff was trained in January 2008 and has received refresher training annually since that time. In addition, each employee is provided a Client Data Protection Reference Guide that answers frequently asked questions and provides strict guidance on data transmission and storage methods when dealing with all types of client data including highly confidential personally identifiable information.

The data protection program at MiECC complies with the strict global protocols Contractor requires. The Global Data Protection Group travels every 18-24 months to review projects, including the MiECC initiative.

DTMB requires that encryption be utilized when moving or storing protected information including resident's privacy information or Personally Identifying Information (PII) such as social security numbers, regulated health information, or financial data including credit card numbers. Through encryption methods the objective is to minimize the likelihood that sensitive or confidential State information is inadvertently disclosed or accessed during the transmission or storage of sensitive and/or confidential data. The link given below contains the policy which identifies the requirements for the encryption methods when data is transmitted and when data is stored in permanent or removable electronic media. http://www.michigan.gov/documents/1315_162707_7.10_Encryption_Policy.pdf

DTMB would like to implement encryption of all sensitive data at rest and in transmission. The Contractor should use functionality from the existing COTS software, the Oracle Advanced Security Option and where necessary custom code.

Depending on the amount of work involved for individual agencies, this work may be part of Base Support or State may consider this as Major Enhancement.

a) The Contractor shall provide all requirements listed in this section, and provide detail regarding how they will accomplish each of the above tasks

Contractor understands the State's intent to implement encryption of all sensitive data at rest and in transmission in the State enterprise. Sensitive data consists of Personally Identifying Information (PII) such as social security numbers, regulated health information or financial data such as credit card numbers. Encrypting sensitive PII data at rest and in transmission lessens the likelihood that State data will be compromised. The Contractor shall review and document MiECC requirements for DTMB standard Standard 1315.10 that specifies requirements to meet minimum protection through the use of encryption.

As part of the Contractor’s scope for this contract, Contractor shall assist agencies and DTMB in evaluating the contact center applications with the objective of identifying and implementing a contact center data encryption plan to have all of the sensitive data encrypted. The Contractor shall document the contact center data encryption plan as part of the Call Center Strategy and Agency Enhancement plan update activities.


72

Requirements of data encryption vary between agencies, like source of data, sensitivity of the data, how the data is handled, means of data transit that should be secured, should encryption be real-time for large amounts of data during transmission or is it 'batch' where data should be encrypted before it enters persistent storage (DB), etc., Contractor shall document data encryption scope requirements prior to starting work on deploying an encryption solution. Contractor staff, DTMB, Siebel and Oracle/SQL server knowledge resources shall study and document scope, verifying the assumptions made on scope, data volume and mechanism to be employed. Depending on the amount of work involved for individual agencies, this work may be part of Base Support or Contractor and State may consider this as Major Enhancement through a mutually agreed upon SOW.

Data encryption scope shall consist of:

Storage of data in Oracle DB - selective data, granularity at table level

Siebel in-memory or online data - selective data, granularity at field, report level

Transmission channels of web access to be secured for all contact centers

Access to CSRs, field staff if any over State's network

Access to data over PSTN not included in scope

Contact Center Software Vendor Data Encryption Capabilities The Contractor shall review the Siebel data encryption capabilities described below and map to documented requirements in the call center data encryption plan.

Siebel End-to-End Encryption for Data Confidentiality Stored data can be selectively encrypted at the field level, and access to this data can be secured. In

addition, data can be converted into an encrypted form for transmission over a network. Encrypting communications safeguards such data from unauthorized access. Transmitted data shall be protected from intrusive techniques (such as sniffer programs) that can capture data and monitor network activity. Data encryption is a method of encoding data for security purposes. Siebel Business Applications support industry standards for secure Web communications and encryption of sensitive data such as passwords. End-to-end encryption protects confidentiality along the entire data path: from the client browser, to the Web server, to the Siebel Server, to the database, and back. Figure 5 shows the types of encryption available for communications within the Siebel environment


73

Figure 5. Encryption of Communications in the Siebel Environment

Client Browser to Web Server Siebel Business Applications run using the Siebel Web Client in a standard Web browser. When a user accesses Siebel Business Applications, a Web session is established between the browser and the Siebel Server, with the Web server in between. Secure Sockets Layer (SSL) protects against session hijacking when sensitive data is transmitted. Siebel Business Applications support 128-bit SSL data encryption, an extremely secure level of protection for Internet communications. Customers using SSL can configure which Web pages (known as views) within Siebel Business

Applications use SSL in the following scenarios:

Use SSL only on the login view to protect password transmission

Use SSL for additional specific views

Use SSL for the entire application

Web Server to Siebel Server Siebel Business Applications components communicate over the network using a Siebel TCP/IP based protocol called SISNAPI (Siebel Internet Session API). Customers have the option to secure SISNAPI using Secure Sockets Layer (SSL) or embedded encryption from RSA or Microsoft Crypto APIs. These technologies allow data to be transmitted securely between the Web server and the Siebel Server.

Siebel Server to Database For secure transmission between the database and the Siebel Server, data can be encrypted using the Oracle Advanced Security network encryption for Oracle and/or SSL encryption for SQL server. Since it is required to use a minimum 128-bit vs. 56-bit encryption Contractor shall work to install and configure the Siebel Strong Encryption package on the Siebel Web and Application servers. This is a package that is available from Siebel without any additional licensing.

Siebel Business Applications by default use the RC4 encryption. RC4 encrypts all the server passwords which writes the encrypted password to the Siebel Gateway server .dat file.


74

RC4 encryption: Siebel Business Applications use RC4 encryption to encrypt passwords stored in the siebns.dat file and to encrypt the Auto-Login Credential Cookie. The siebns.dat file stores information required by the Siebel Gateway Name Server

Contractor uses the below Algorithm in order to directly access to the database.

RSA SHA-1 password hashing: Siebel administrators can enable password hashing. Hashing uses a one-way hashing algorithm. The default password hashing method is RSA SHA-1. (The previous mangle algorithm is still available for existing customers.) Password hashing invalidates the password to unauthorized external applications and prevents direct SQL access to the data by anything other than Siebel Business Applications. Database Storage

Transparent Data Encryption (TDE) technologies exists both for the Oracle and SQLServer environments. TDE technologies allow full databases and/or columns to be encrypted with no application code changes.

b) The Contractor describes their overall approach to implement the encryption. The encryption projects will be considered part of Major Enhancements

Contractor's approach to protecting sensitive data shall consist of working with the agency and DTMB to effectively inventory the sensitive contact center data both at rest and in transit. Contractor shall identify approaches to protect this data through the latest industry acceptable methods that meet the standards of the State. Contractor shall leverage its experience in data privacy and data encryption to help guide the project by reducing risks. The Contractor high-level planning approach shall be as follows:

Inventory the candidate data - category, volumes, nature of data, locations

Identify transit mechanisms to be secured - web, dedicated network, intra-application or intra-server transits

Performance, testability, maintainability and other non-functional considerations of data security

High level execution approach shall be:

o Assist in documenting the approach as part of the State SEM processes in detail and review with the stakeholders including the agency, DTMB and Office of Enterprise Security.

o Consult State Security, DB Admin team and functional stakeholders and finalize functional requirements

o Seek planning and budgeting approvals after estimation confirmation

o Design implementation plan

o Implementation and roll-out

Contractor shall leverage its experience in data privacy and data encryption to help guide the project by reducing risks. As part of the project, the Contractor shall assist in documenting the approach as part of the State SEM processes in detail and review with the stakeholders including the agency, DTMB and Office of Enterprise Security. As part of Contractor approach, Contractor shall consult with State security experts and the database administrators.

c) The Contractor details out each movement and storage areas for all sensitive data, and describe how the encryption requirements will be met for each agency solution. This includes the software that will be used and whether it will require configuration or custom code

Contractor shall work closely with the agency and DTMB to confirm that sensitive data is included in data encryption plans for the contact center. Table 17 represents a high-level initial view of the applications in the contact centers that shall be candidates at storage/transit points for sensitive data. This view is subject to change upon a further analysis with the agency and DTMB but it is Contractor’s initial view of the data scope for the contact center. Contractor shall look to reduce and eliminate configuration or coding to encrypt the


75

data. Contractor shall look to transparently encrypt the data at rest with the use of Oracle and SQL Server built in encryption packages that use Transparent Data Encryption (TDE).

Sensitive Data items considerd (SSN, DLN, CC, Regulated Health Information)

Agency Genesys Storage

Genesys Transit

Siebel Storage

Siebel Transit

NICE Storage

NICE Transit

Civil Service NO

DHS IVR NO N/A N/A N/A N/A

DTMB-CSC NO --- N/A N/A N/A N/A

DEQ N/A N/A NO NO N/A N.A

LARA-BHP NO

MDOS NO

ORS NO

Treasury NO

Table 17. High Level possible sensitive data areas

The Contractor shall review the database data encryption capabilities described below and map to documented requirements in the call center data encryption plan.

Transparent Data Encryption with Oracle Advanced Security Transparent Data Encryption (TDE) enables users to encrypt data within a database. When an application such as Siebel accesses the data, Oracle Database transparently decrypts the relevant data for the application. Encryption is a very important tool for applications. The State can use Oracle Advanced Security TDE to address PCI-DSS requirements and can use TDE to safeguard social security numbers and other sensitive information. Encryption plays an especially important role in safeguarding data in transit. Oracle Advanced Security network encryption protects data in transit on the intranet from network sniffing and modification. Oracle Advanced Security TDE protects sensitive data on disk drives and backup media from unauthorized access, helping reduce the impact of lost or stolen media. Transparent Data Encryption encrypts entire tables of data at the table space level in the database. Table space encryption does not require the complicated database triggers and views commonly associated with other database encryption solutions. This means that no Siebel application changes are required to take advantage of this feature. Data for existing Siebel applications can be encrypted with minimal performance impact.

Microsoft SQL server has similar transparent data encryption options that could be enabled without the need for application changes. For MSSQL server you can enable encryption of an entire database (all data files and log files) without the need for application changes. For example, the Database Administrator can encrypt the entire Siebel database with no changes needed on the Siebel Server(s), Siebel Tools, and so on. Note that encryption may be enabled for the entire database, but not for selective tables or columns. The database pages are decrypted once read into SQL Server memory, and encrypted any time a page is written to disk. Moreover, backups are encrypted once encryption is enabled on the Siebel database. Contractor shall work with the DTMB database administrators to confirm which options of TDE exists for the versions of the database that we are currently operating.


76

d) The Contractor identifies whether additional software licenses are required and their estimated cost (purchase price and maintenance)

As part of contact center data encryption plan, the Contractor shall confirm what additional software licensing, if any, shall be required to implement data encryption.

e) The Contractor identifies whether additional hardware is required to cover the overhead involved with encryption /decryption and their estimated cost

As part of the contact center data encryption plan, the Contractor shall confirm what additional, if any, hardware shall be required to implement data encryption.

f) The Contractor provides an estimated cost for its involvement to configure/custom code all components for the encryption requirements. The Contractor provides the required skill sets and hours required to complete the work. Service cost estimates should be based on the Table 4: Rate Card in Attachment 3A - Cost Tables

The Contractor's approach shall be to leverage the network encryption and storage encryption technologies to accomplish the objective of further protecting sensitive data. As part of the contact center data encryption plan, the Contractor shall document what configuration/custom application code changes to the in scope applications, if any, shall be required.

Contractor, under the data encryption plan, shall recommend Siebel, Oracle, and other call center software capabilities be used to meet the State’s encryption requirements.

For example, Siebel Applications also allow customers to encrypt sensitive information stored in the Siebel database (for example, credit card numbers, Social Security numbers, birth dates, and so on) so that it cannot be viewed without access to Siebel Business Applications. Customers can configure Siebel Business Applications to encrypt a column’s data before it is written to the database and decrypt the same data when it is retrieved. This encryption prevents attempts to view sensitive data directly from the database. Sensitive data can be encrypted by using AES (Advanced Encryption Standard) or RC2 encryption, at various key lengths. Encryption can be enabled using Siebel Tools. This as an alternative to the native database TDE encryption but Contractor’s preliminary recommendation shall be to use the TDE encryption.

g) The Contractor describes the provisions made for preparing the response

The Contractor has following provisions to the encryption requirements:

Oracle 11G shall be available for table level TDE Oracle 10G shall be available for column level TDE SQLServer 2008 shall be available for TDE The Contractor team does not have administrative rights on the servers. Data Encryption in transit shall

be in scope for DTMB to generate and install SSL encryption certificates on the appropriate servers as defined by the Contractor MiECC team in the call center data encryption plan.

The Contractor team shall be in a consult and assist role and shall work closely with agency, OES, DTMB teams to validate the encryption assumptions and test the final encryption configurations for usability and performance considerations.

The State shall provide a project manager. Agencies shall request data encryption projects through the annual Call Center Strategy and Agency

Enhancement Plan update work efforts. Current data reports that agency management receive on a daily, weekly and monthly basis do not

contain sensitive data and still need to be included in regression testing to validate that data is presented the same after data encryption is applied to the environment.

h) The Contractor identifies any underlying risk for implementing or not implementing the solution

The Contractor sees more risks for not encrypting sensitive data than in encrypting the data. The main risks in not encrypting the sensitive data are that data at rest or in transit data could be compromised putting the


77

citizens at risk for unauthorized use of personal information. The main risk to implement a full data encryption environment affects the application performance. From Contractor’s experience, the risk of performance degradation is low and could be mitigated through proper testing, database configuration and expectations management.

i)

High-Level Cost Estimate

The Contractor provided high-level cost estimate for Encryption in Contractor’s Price Proposal.

L. Licenses/Training Services

Reserved

M. Other Contact Center Services The Contractor may provide extra contact center services. The state shall provide an SOW and the Contractor shall respond with a proposal. The proposal shall include all possible skills/ services that may be required in the contact center space. Approach Working with the State of Michigan agencies to identify additional contact center services, Contractor shall follow the accepted SOW process described in Section 1.403 Change Management.

b) Bidder must specify the DTMB team responsibilities and customer agency responsibilities

Contractor shall work with DTMB and agency contacts to identify and document staffing requirements. Contractor shall then search for and secure appropriate third-party staff. Contractor shall prepare and submit a SOW response to DTMB and agency contacts as needed. The agency contact(s) shall approve the SOW and DTMB prepare/submit the purchase order request for approval and processing. Upon issuance of a purchase order, Contractor, DTMB, and agency contact(s) shall work within in the existing service delivery model to prioritize and schedule work completion approved in the SOW. Table 18 sets forth the responsibilities of each party.

Area of Responsibility DTMB Agency Contractor

Identify staffing requirements � � � Prepare requirements documentation

�

Search and secure appropriate staff

�

Prepare SOW � Approve SOW � Issue purchase order � Monitor SOW delivery � � �

Table 18. DTMB, Customer Agency and Contractor Responsibilities associated with providing Other Contact Center Services

II. Requirements A. Work Requirements See Attachment 2


78

1.200 Roles and Responsibilities

1.201 Contractor Staff, Roles, And Responsibilities

A. Contractor Staff The Contractor’s team's years of experience with the State of Michigan, MiECC, project management, and the MiECC systems and technologies is illustrated in Table 27.

Table 19. The

Contractor MiECC Team’s Experience at a Glance

Contractor’s team members in key personnel positions meet or exceed the minimum skills and experience directly related to the assigned job functions. Contractor commits the staff identified in the Contract to the MiECC project. In anticipation of future staffing changes and SOW work that requires staffing from third parties, Contractor shall enlist the support of a Global Alliance member or Contractor Exchange supplier to provide the specialized skill set, including:

Name of Subcontractor

Genesys Telecommunications Laboratories, Inc.

Address 2001 Junipero Serra Blvd, Daly City, CA 94014 Contact Person Dave Kregness, Account Executive for State of Michigan

[email protected] William Grabner, Director of US Sales, [email protected]

Work to be Contracted Future Genesys Specialist skill set. Contractor Descriptive Information and Abilities

Genesys is the world’s largest software only contact center company. Genesys has locations across the US and 80 countries globally. Industry organizations such as Gartner, Forrester, Datamonitor and others consistently rank Genesys products and platforms as best in class. Specific to the State of Michigan, Genesys is currently installed at eight (8) Agencies including Treasury, DTMB CSC, Office of Retirement Services, DHS, Community Health, Civil Service, DNR and Department of State.

State of Michigan

MiECC

Project Mgmt

Siebel

Oracle/ SQL

Genesys

IVR NICE

Jamie Walker 7 6 20+

Ryan Sadler 8 8 13+ 8 13+ 8 8 3

Norma Miller 4 2 20+

Rajaram Loganathan

9 8 9 12+ 12 8 8 7+

Pam Numerick 4 4 11 11+ 14 1 1

Ravindra Jaiswal 3 3 4 2 6 6 6 3

Noel Espiritu 2 2 12 11 4 1

Manju Yeddanapalli 3 3 4 7 9 1 1

Greg Blake 3 2 1 3 2 2 1


79

Genesys offers a broad array of software products, consulting, professional services and training that can have a positive effect on State and Local government entities as they seek to be more effective and efficient within and across their organization as well as with their citizens and other key stakeholders.

Name of Subcontractor

Actium Consulting, www.actium-consulting.com

Address P.O. Box 4631, El Dorado Hills, CA 95762 Contact Person Gus Exarchos, Managing Director; 314-378-5317 Work to be Contracted Future Business Analyst, System Architect, Seibel Lead, Siebel Developer, Computer

Telephony Specialist, Genesys Specialist, IVR Developer, NICE Analyst skill sets. Contractor Descriptive Information and Abilities

Actium Consulting has over 18 years of experience in the development, implementation and support of large public sector systems and is an Accenture Preferred Contractor Exchange supplier. Actium Consulting's experience includes 9 years collaborating with Accenture on the State of Michigan Child Support Enforcement (MiCSES) project serving as an integral part of MiCSES in the production support effort providing training, technical writing, and advanced Oracle development skill sets. They also provide computer telephony specialists and Genesys specialists for the State of California Child Support call center. They are able to provide the MiCSES project with Business Analyst, System Architect, Seibel Lead, Siebel Developer, Computer Telephony Specialist, Genesys Specialist, IVR Developer, NICE Analyst skill sets.

The Contractor has identified a Single Point of Contact (SPOC), Norma Miller. The duties of the SPOC shall include, but not be limited to:

supporting the management of the Contract, facilitating dispute resolution, and advising the State of performance under the terms and conditions of the Contract.

With extensive program management experience and her current experiences as the contract manager for the Michigan Child Support Enforcement System project and the existing Michigan Enterprise Call Center project, she has familiarity with Contractor’s contractual responsibilities.

The State reserves the right to require a change in the current SPOC if the assigned SPOC is not, in the opinion of the State, adequately serving the needs of the State. The Contractor shall provide, and update when changed, an organizational chart indicating lines of authority for personnel involved in performance of this Contract and relationships of this staff to other programs or functions of the firm. This chart must shall show lines of authority to the next senior level of management and indicate who within the Company will have prime responsibility and final authority for the work. Figure 6 displays the organizational chart, which indicates the lines of authority with Contractor personnel responsible for the performance of this contract.


80

Jamie WalkerSenior Executive

Cindy HielscherQuality Assurance

Director

Ryan SadlerService Delivery

Lead

Norma MillerContract Manager

Rajaram LoganathanSystem Architect

Pam NumerickSiebel Lead

Ravindra JaiswalGenesys Specialist

Noel EspirtuSiebel Systems

Architect

Ian GoudieSystem Support

Manju YeddanapalliSiebel LeadDeveloper

Greg BlakeGenesys Support

Hien NguyenIVR Developer

MI ECC 11.0072

Figure 6. The Contractor MiECC Team brings highly skilled and qualified individuals with demonstrated experience in the MiECC environment

Jamie Walker, the MiECC Client Account Lead, will sign the MiECC Contract and have final authority for the work. All Key Personnel may be subject to the State’s interview and approval process. Any key staff substitution must have the prior approval of the State. The State has identified the following as key personnel for this project:

Project Manager - Service Delivery System Architect Siebel Lead Genesys Specialist

The Project Manager – Service Delivery is Ryan Sadler. The System Architect is Rajaram Loganathan. The Siebel Lead is Pam Numerick. The Genesys Specialist is Ravindra Jaiswal. The Contractor shall identify whether the key personnel will perform any secondary roles. The key personnel are expected to be available on site during normal state working hours (see B2 below) unless remote work arrangements have been agreed upon with DTMB Project Manager. The Contractor will provide a project manager (service delivery) to interact with the designated personnel from the State to insure a smooth transition to the new system. The project manager (service delivery) will coordinate all of the activities of the Contractor personnel assigned to the project and create all reports required by State. The Contractor will provide sufficient qualified staffing to satisfy the deliverables of this SOW. For all role descriptions, please refer to Attachment 4: Personnel Requirements


81

The Enterprise Contact Center Base Support team shall include six different groups of personnel.

a. Contractor staff who will be on the support team. b. DTMB staff who will be on the support team for full time. c. DTMB staff who will provide necessary services to the support team. d. Business staff who will perform system administration e. Business staff who will product test the system. f. DTMB project oversight

The Contractor shall show a resource plan for the five years identifying all Contractor personnel involved in this project, their skills and the tasks that they will be allocated. The Contractor has included representative resumes of all non-key personnel in the Base Support team. The Contractor will describe any other Contractor resources that will be made available to on-site Contractor staff. The Contractor will designate specific skill sets for their personnel permanently assigned to the team. The Contractor will describe the experience of all personnel listed in their response along with any relevant qualifications. The State, with multiple contact centers, has a complex environment often requiring the ability to manage a number of maintenance and support related activities concurrently. The Contractor shall leverage their resource bench to support any of the operational activities (including for key personnel) on short notice in the event that such action is required. Further it is recognized that designated State staff may leave the team and seek employment elsewhere. The Contractor may be required by DTMB temporarily to provide Contractor staff with at least the same knowledge and skill levels while the State seeks a replacement. The Contractor shall provide costs for this when required. The State will provide the Contractor a SOW and the Contractor will respond with a proposal using the rate card in cost tables, if possible. Likewise, Contractor staff may leave the team and seek employment elsewhere. The Contractor may be required by DTMB to temporarily provide Contractor staff with at least the same knowledge and skill levels while the Contractor seeks an equivalently skilled replacement. In the event that Contractor need to bring on a new member to its team, either to replace a departing Contractor team member or support the State after departure of a key State staff member, Contractor shall use global network of professional as described in the Bench Strength Section below.

In addition to our highly qualified employees, Contractor maintains Global Alliances and teams with Contractor Exchange suppliers. Contractor shall enlist the support of a Global Alliance member or Contractor Exchange supplier to provide the specialized skill set in the event of future staffing changes and SOW work that shall require staffing from third parties. Potential team members include but are not limited to the following:

Genesys Empirix Oracle VMWare IBM-ECM (formerly FileNet) Actium Consulting

The Contractor understands that the State may wish to create additional SOWs for an increase in services over the duration of the five-year Base Support contract. The Contractor shall work with the State to pursue the appropriate Contract modifications at that time to increase staff above the proposed staffing plan as appropriate to meet the requested services.


82

Table 20. Contractor proposes a consistent team to deliver MiECC Base Support over the duration of the Contract

Additional Contractor Resources

During the Contract term, Contractor may be required to reach out to additional resources when needed. Those resources may be Contractor employees, subcontractors, or software vendors on an as needed and/or requested basis. The Contractor Delivery Network provides the local Contractor MiECC Team and the State with global knowledge assets. Contractor shall use the Contractor Delivery Network to bring the right skilled resources at the right time to provide the required support. The Contractor has a global resource management organization that could be used to locate and schedule a skilled resource to assist the Michigan team.

Specific Skill Sets and Experience

The Contractor Base Support team performed similar roles under the previous MiECC contract. These personnel have demonstrated their knowledge, experience and ability to perform their responsibilities in the MiECC environment. Table 21 provides a high-level view of the skills and experience Contractor team provides.

Personnel Type / Skill In Scope Services Planned Resource FTE Hours By Year Year 1 Year 2 Year 3 Year 4 Year 5 Mr. Sadler Service Delivery Knowledge Transfer 0 0 0 0 0 Base Support Tasks 1,260 1,260 1,080 1,080 1,080 Major Enhancements 540 540 720 720 720

Ms. Miller Contract Management

SPOC, Contract Administration

90 90 90 90 90

Mr. Loganathan Systems Architect Knowledge Transfer 0 0 0 0 0 Base Support Tasks 1,440 1,440 1,440 1,440 1,440 Major Enhancements 360 360 360 360 360 Ms. Numerick Siebel Lead Knowledge Transfer 0 0 0 0 0 Base Support Tasks 1,440 1,440 1,440 1,440 1,440 Major Enhancements 360 360 360 360 360 Mr. Jaiswal Genesys Specialist Knowledge Transfer 0 0 0 0 0 Base Support Tasks 1,440 1,440 1,440 1,440 1,440 Major Enhancements 360 360 360 360 360 Ms. Yeddanapalli Siebel Developer Knowledge Transfer 0 0 0 0 0 Base Support Tasks 1,620 1,620 1,620 1,620 1,620 Major Enhancements 180 180 180 180 180

Mr. Espiritu Technical Administrator Knowledge Transfer

0 0 0 0 0

Base Support Tasks 1,800 1,800 1.620 1,620 1,620 Major Enhancements 0 0 180 180 180 Mr. Nguyen IVR Developer Knowledge Transfer 0 0 0 0 0 Base Support Tasks 0 0 0 0 0 Major Enhancements 1,800 1,800 1,800 1,800 1,800

Mr. Blake Genesys Support Specialist Knowledge Transfer

0 0 0 0 0

Base Support Tasks 1,800 1,800 1,800 1,800 1,800 Major Enhancements 0 0 0 0 0

Ian Goudie Support Specialist (NICE, Siebel, L1) Knowledge Transfer

0 0 0 0 0

Base Support Tasks 0 0 0 0 0 Major Enhancements 1,800 1,800 1,800 1,800 1,800 Total FTE by Period

9.05 9.05 9.05 9.05 9.05


83

Name IT Classification General Skills Norma Miller Project Manager Contract Administration

Project Management Contact Center Administration

Ryan Sadler Project Manager (Service Delivery)

Contractor Lead Project Management Professional (PMP) SUITE Contact Center Siebel, Genesys, and NICE Functional and

Technical Acumen Rajaram Loganathan

System Architect Technical Lead Siebel and Genesys SUITE NICE Windows Server Networking Oracle Workforce Manager

Pam Numerick Siebel Lead Siebel SUITE FileNet

Ravi Jaiswal Genesys Specialist Genesys Framework NICE Genesys IVR

Manju Yeddanapalli Siebel Developer Siebel SUITE Contact Centers Workflow Reporting

Greg Blake Computer Telephony Specialist

Genesys Framework SUITE Genesys IVR CTI AES Avaya

Noel Espiritu Siebel Developer Siebel Siebel EIM Oracle Batch Process Workflow

Table 21. The Contractor MiECC Team has demonstrated the skills and experience needed to support the DTMB and the State of Michigan agency customer contact centers

Ongoing Team Management

Bench Strength

The Contractor has a robust process to pull from their experienced and skilled resource pool of approximately 236,000 employees across the globe. Many of these employees currently possess the specific skills requested by this contract. In the event a Contractor resource can no longer work on the project, Contractor shall work with its dedicated Human Resource Staffing Coordinators to identify a suitable replacement for the departing individual based on the skills and qualifications needed for the role. Ryan Sadler, the Project Manager - Service Delivery, shall be responsible for finding the right candidates and Jamie Walker, the MiECC Client Account Lead, shall be responsible for helping the Project Manager and solving escalated staffing issues.

B. On Site Work Requirements

1. Location of Work


84

The work is to be performed, completed, and managed at the following locations: General vicinity of Lansing, Michigan

Knowledge transfer and Base Support team members must be on site. The Major Enhancements project team members may be off site as agreeable by state’s project manager on a case by case basis.

2. Hours of Operation: a. Normal State working hours are 8:00 a.m. to 5:00 p.m. EST, Monday through Friday. However,

contact center business hours are 7 AM to 7:30 PM Monday through Friday and 9 AM to 12:30 PM on Saturdays. Work may be performed as necessary and with proper approval after those hours to meet project deadlines or service levels as defined in Attachment 1. No overtime will be authorized or paid.

b. The State is not obligated to provide State management of assigned work outside of normal State working hours. The State reserves the right to modify the work hours in the best interest of the project.

c. Contractor shall observe the same standard holidays as State employees. The State does not compensate for holiday pay.

3. Travel: a. No travel or expenses will be reimbursed. This includes travel costs related to training provided

to the State by Contractor. b. Travel time will not be reimbursed.

4. Additional Security and Background Check Requirements: Contractor must present certifications evidencing satisfactory Michigan State Police Background checks ICHAT and drug tests for all staff identified for assignment to this project.

In addition, proposed Contractor personnel will be required to complete and submit an RI-8 Fingerprint Card for the National Crime Information Center (NCIC) Finger Prints, if required by project.

Contractor will pay for all costs associated with ensuring their staff meets all requirements.

The Contractor shall perform work in the general vicinity of Lansing, Michigan. The Contractor shall provide support resources during the normal State working hours. The Contractor shall continue to look to staff the Base Support team with local resources that shall work on-site during business hours and also be available on call should a high priority remedy ticket be received. Portions of the contact center support requires 24/7 support. Contractor shall coordinate to have work completed during core business hours to reduce the impact on State and Contractor resources after hours. However, in the event that an issue occurs, resources may be required to work after hours to troubleshoot and confirm system availability. The Contractor shall continue to work with DTMB and agencies to complete server maintenance, product upgrades, executed batch jobs, release migrations, and regression testing after normal State working hours to reduce the impact on State and MiECC resources. This work is consistently validated and approved confirming that the contact center applications are available the next business day. These events are coordinated with the Agency requesting the assistance. These production activities are communicated in the monthly status meetings to the agencies and to the DTMB project manager.

The Contractor team shall work with the State project manager if project working hours are to be modified. The Contractor team may complete a FileNet, Siebel or Genesys Upgrade after-hours or over a weekend to reduce the business impact. In these cases, the Contractor shall coordinate with the State to provide the requested support outside of normal business hours.

The Contractor team shall observe the same holidays as State employees as needed.


85

The Contractor team shall not expect the State to reimburse for Travel or Expenses. The Contractor team also shall not have travel time reimbursed.

The Contractor shall continue to fully comply with the requested State background checks.

1.202 State Staff, Roles, And Responsibilities

The State will provide the following resources for the Contractor’s use on this project: Co-located Contractor team Work space Minimal clerical support Desk Telephone PC workstation with hard drive encryption Printer Access to copiers and fax machine

The State project team will consist of Executive Subject Matter Experts (SME’s), project support, and a DTMB and Agency project manager: Executive Subject Matter Experts The Executive Subject Matter Experts representing the business units involved will provide the vision for the business design and how the application shall provide for that vision. They shall be available on an as needed basis. The Executive SME’s will be empowered to:

Resolve project issues in a timely manner Review project plan, status, and issues Resolve deviations from project plan Provide acceptance sign-off Utilize change control procedures Ensure timely availability of State resources Make key implementation decisions, as identified by the Contractor’s project manager, within 48-hours

of their expected decision date. List of Business and Technical SME from each agency -

Name Agency/Division Title Michelle Suchner Civil Service Business Manager Anne Brys DTMB-MCSC Agency Services Manager Phat Tran DTMB-Client Service Center Business Manager Dan Conlin DTMB-Client Service Center DTMB-CSC Director Sean Bodell ORS Business Manager Mike Bilek DTMB ORS Agency Services Manager Christine Grossman DEQ Business Manager Jeff Beasley DTMB DEQ Agency Services PM Tess Layman DTMB DHS Leveraged Services Director Joe Campbell LARA-BHP Business Manager Celeste Sickles DTMB LARA Agency Services Manager Bud Diver MDOS Business Manager Tiziana Galeazzi DTMB MDOS Agency Services Manager Patricia Cotter Treasury Business Manager Randy Leyrer DTMB Treasury Agency Services Manager

State Project Manager- (DTMB and Agency)


86

DTMB will provide a Project Manager who will be responsible for the State’s infrastructure and coordinate with the Contractor in determining the system configuration. The State’s Project Manager shall provide the following services:

Provide State facilities, as needed Coordinate the State resources necessary for the project Facilitate coordination between various external contractors Facilitate communication between different State departments/divisions Provide acceptance and sign-off of deliverable/milestone Review and sign-off of timesheets and invoices Resolve project issues Escalate outstanding/high priority issues Utilize change control procedures Conduct regular and ongoing review of the project to confirm that it meets original objectives and

requirements Document and archive all important project decisions Arrange, schedule and facilitate State staff attendance at all project meetings.

The DTMB Project Manager shall approve any Major Enhancements. Name Agency/Division Title Abhijit Sarkar DTMB Project Manager DTMB shall provide a Contract Administrator whose duties shall include, but not be limited to, supporting the management of the Contract. Name Agency/Division Title Mark Lawrence DTMB Contract Administrator The support team will consist of DTMB staff, business staff and Contractor staff providing services to the contact centers. DTMB will be responsible for the State’s infrastructure and work together with the Contractor in determining the system configuration. The State currently has two technical team members at MiECC – a Computer Telephony/Genesys Specialist and a trainee Siebel developer. DTMB staff who will provide necessary services to the support team The State currently has staff in the following support roles: a. Database Administrator b. NICE administration specialist c. Telecom division technical employees for Telephony programming, troubleshooting and order processing. d. Telecom staff to maintain the telephony environment components including T-API’s. e. Server hosting staff to maintain all hardware and operating systems. This includes the Cisco switches that

act as load balancers. f. State programmers who will maintain the legacy data load to Siebel repository tables f. EMichigan staff who will review and approve all external facing websites. g. FileNet technical administrator (and back up) who maintains the hardware infrastructure, the basic FileNet

software configurations and all security for files and users. State staff does not maintain anything relating to the IDL, VB script, FileNet Capture configurations and the FileNet CIS products at Treasury.


87

Business staff who will perform system/business administration Each agency will have one employee who will be responsible for business administration. This includes adding new users and list of values (LOV’s). Business staff who will product test the system Each agency will provide a testing team that will complete users’ acceptance testing for system changes. They will also identify the data necessary to test the new functionality.

1.203 Other Roles And Responsibilities

RESERVED

1.300 Project Plan

1.301 Project Plan Management

Project Plan Management Approach Accenture Delivery Methods (ADM) is central to the Contractor’s approach to managing the MiECC project work. ADM aligns with both industry standards and the State’s Project Management Methodology (PMM).

The Contractor’s methods and tools are not strictly Contractor-centric; they use project management industry preferred practices from external sources as well, promoting a high level of quality and completeness. For example, ADM incorporates industry standards from the Software Engineering Institute‘s (SEI) Capability Maturity Model Integrated (CMMI), the Project Management Institute‘s Body of Knowledge (PMBOK), Institute of Electrical and Electronics Engineers (IEEE), and IT Infrastructure Library (ITIL).

CMMI Process Maturity - Delivering Quality Standards, Practices and Processes Knowing and practicing well-defined and proven standards and processes from the start of the project can produce higher quality deliverables in less time. The Contractor’s team is part of Contractor's Public Service USA group. The USA Public Service group as a whole is CMMI Level 4 assessed.


88

PMBOK Project Management Industry Standards The Contractor’s project management methodology is consistent with the Project Management Institute (PMI) Project Management Body of Knowledge (PMBOK). PMI is the world‘s leading not-for-profit membership association for the project management profession. PMI‘s global standards provide widely accepted guidelines, rules, and characteristics for project management.

Alignment with State PMM and SEM Methodologies

Contractor's ADM aligns with the State's SEM. Both encourage consistent use of process and templates, detailed planning, and multiple checkpoints. Both methodologies include verification of the completion of phase activities before moving to the next phase. This helps prevent problems from moving to later project phases when they are more costly to resolve.

The Contractor Team shall bring knowledge, experience, and discipline provided through ADM and manage the project in accordance with the State’s PMM and System Engineering Methodology (SEM), processes, and templates.

Contractor shall use Capability Maturity Model Integration (CMMI) Level 4 practices, Quantitative Project Management, Organizational Process Performance, and ADM knowledge base for estimating and project planning. This helps the team develop estimates and schedules that are achievable and meet the State’s goals and objectives for each release and system patch/upgrade.

Ongoing Management

The Contractor team shall use the process to manage new or modified project work that was proven to be successful under the prior MiECC contract. In this process, as new requests are submitted to the joint MiECC DTMB and Contractor Teams, work shall be categorized as either: 1) break-fix, 2) support or maintenance, 3) Minor Enhancements, 4) Upgrades, or 5) Major Enhancements.

Break-fix and support and maintenance work shall be scheduled and completed \in accordance with the SLA's and communicated through the State's Service Request Management system. Changes to the production system shall first be developed and tested in the non-production environments. Once the changes have passed internal and user acceptance testing, the release deployment shall be scheduled and communicated as a Request for Change. This request shall be reviewed by the local/enterprise change control boards prior to migration into production.

Minor Enhancement, Upgrades, and Major Enhancements may require more resources within the organization. These resources are often agency, DTMB, Telecom Teams, Infrastructure Teams, or PMO resources. These efforts thus include more detailed tasks within the project plan.

The Contractor shall use annual project planning and monthly Business Operations Status Meetings to discuss Minor/Major Enhancement and Upgrade projects. Discretionary enhancement (non-software upgrade) requests greater than 200 hours shall result in a SOW request from the Contractor. This SOW, once approved, generates a purchase order from the funds available on the master Contract that are separate from the annual Base Support purchase order.

For discretionary, non-upgrade work, agencies shall submit requests through the Remedy System or to the DTMB PMO Program Manager directly. The DTMB Project Manager shall work with the Contractor and DTMB teams to create cost, schedule, and resource estimates as part of the SUITE initiation and planning process. Agencies and DTMB Client Service Directors (CSD) shall obtain work request approval from their own project/budget office. Once the work is approved, the DTMB PMO Program Manager and the Contractor Delivery Lead shall work together to schedule the project taking into account resources available and other work constraints. The Contractor Delivery Lead shall assign a Project Manager, if required, and Functional Leads and other key resources for the work. The assigned lead is responsible for creating the project plans and following the applicable SUITE methodology processes to guide a successful project.


89

Preliminary Project Plan The Contractor’s Preliminary Project Plan is in Attachment 7.

Note: A Final Project Plan will be required as stated in Article 1, Section 1.301 (C) Project Control.

1. Preliminary Project Plan Components A. Deliverables

Effective deliverable management is critical to managing activities and work products outlined in the Preliminary Project Plan. The Contractor shall use the State’s SUITE and SEM tools, processes, and templates to drive the successful management of Contract deliverables, tracing all work back to its requirements and verifying the end product meets the success criteria for each requirement. The Contractor shall provide weekly status reports for the DTMB, monthly status reports for the eight state agencies, and quarterly reports for the quarterly Performance Review Meetings. Monthly Project Portfolio Status Report and Monthly Breakdown of Support Hours deliverables shall be used for payment and provided within 10 business days of the end of the month in the format requested by the State. For additional information on reports provided by the Contractor, see Section 1.302.

For minor and Major Enhancements, the Contractor Team shall provide the following documentation in accordance with the SEM documentation:

State of Michigan System Maintenance Documents Requirements, Design, and Test Artifacts Release Notes

B. Timeframes and Critical Path, E. Task Durations, and F. Internal Milestones

The Contractor Team and the DTMB Program Manager shall develop and maintain a Project Work Plan in Microsoft Project to outline the target dates, critical path, task durations, and internal milestones associated with project work and deliverables. Contractor and State shall work jointly and mutually agree upon proposed work plan timeframes.

C. Matrix of Roles and Responsibilities

The Contractor, DTMB, and Agency staff shall jointly complete the preliminary project work plan with roles and responsibilities outlined in Table 26. Preliminary Project Work Plan Roles and Responsibilities Matrix.

Responsibilities DTMB Customer Agency Contractor Provide overall management and strategic direction for the MiECC project

�

Approve all Contract deliverables � Provide business requirements � � Develop training materials � Manage the change control process � Create project schedule � Manage project schedule � Provide technical infrastructure support � � Track project progress � Perform configuration management � Provide release management � Propose innovation � � � Perform application maintenance � Integration testing � Administer project staff � � � Provide knowledge of current system functionality � Develop level of effort estimates � Participate in Change Control � � �

Table 22. Preliminary Project Work Plan Roles and Responsibilities Matrix


90

2. Payment Deliverables The Preliminary Project Plan includes the monthly Project Portfolio Status Report and Monthly Breakdown of Support Hours deliverables for which payment shall be made. Contractor shall produce these deliverables to the State within 10 business days of the end of the month in the formats agreed upon by the State and Contractor. The Contractor shall provide payment deliverables on time.

For additional information on these reports provided by the Contractor MiECC Team, see Section 1.302

Final Project Plan The Contractor shall provide a Final Project Plan within 10 business days of the Contract award.

Orientation Meeting 1. Upon 10 business days from execution of the Contract, the State shall schedule and the Contractor

shall attend an orientation meeting to discuss the content and procedures of the Contract. 2. The meeting will be held in general vicinity of Lansing, Michigan, at a date and time mutually

acceptable to the State and the Contractor. 3. The State shall bear no cost for the time and travel of the Contractor for attendance at the meeting.

Performance Review Meetings 1. The State shall schedule and the Contractor shall attend quarterly meetings, at a minimum, to review

the Contractor’s performance under the Contract. 2. The meetings will be held in general vicinity of Lansing, Michigan, or by teleconference, as mutually

agreed by the State and the Contractor. 3. The State shall bear no cost for the time and travel of the Contractor for attendance at the meeting.

Project Control 1. The Contractor will carry out this project under the direction and control of DTMB. 2. Within 10 business days of the work approval, the Contractor shall submit to the State project

manager(s) for final approval of the detailed project plan (technical work plan). This project plan must be in agreement with Article 1, Section 1.104 Work and Deliverables, and must include the following: The Contractor’s project organizational structure. The Contractor’s staffing table with names and title of personnel assigned to the project. This must

be in agreement with staffing of accepted proposal. Necessary substitutions due to change of employment status and other unforeseen circumstances may only be made with prior approval of the State.

The project work breakdown structure (WBS) showing sub-projects, activities and tasks, and resources required and allocated to each.

The time-phased plan in the form of a graphic display, showing each event, task, and decision point in the WBS.

2. Detailed Project Plan (Technical Work Plan) Within the first 10 business days of the work approval, Contractor shall submit a final plan to the State that directs Contractor MiECC Team efforts throughout the duration of the new MiECC contract. This plan shall include an approved work breakdown structure (WBS) and a graphic depiction of planned project work that shows the tasks and decision points identified in the WBS.

The Contractor shall discuss project organizational structure and staffing table with DTMB before being finalized. Staffing represented in the staffing table shall be in agreement with the staffing approved as part Contract negotiations. Contractor shall work with the State to gain approval of any necessary substitutions due to change of employment status and other unforeseen circumstances that may occur.

1.302 Reports

Once both parties have agreed to the format of the report, it shall become the standard to follow for the duration of the contract. The State and Contractor will follow the same process for requesting additional reports.


91

The Contractor shall provide any suggested improvement on the report formats for approval within 10 business days after the Contract orientation meeting.

Weekly Program and Project status report – due every week Monthly Operational Status for business agencies – due 3 business days prior to the monthly

operational meeting with the agency. Monthly Project Portfolio Status report – due within 3 business days after month end. Individual Project Status (Achievements, Milestones, Issues, Risks) every other week. Action Item status every other week. Monthly Maintenance Activity/Hours Report – due within 10 business days after month end.

1.400 Project Management

1.401 Issue Management

An issue is an identified event that if not addressed may affect schedule, scope, quality, or budget. The Contractor shall maintain an issue log for issues relating to the provision of services under this Contract. The Contractor shall communicate issue management log to the State’s Project Manager on an agreed upon schedule, with email notifications and updates. The Contractor shall update the issue log and updates shall contain the following minimum elements:

Description of issue Issue identification date Responsibility for resolving issue. Priority for issue resolution (to be mutually agreed upon by the State and the Contractor) Resources assigned responsibility for resolution Resolution date Resolution description

Issues shall be escalated for resolution from level 1 through level 3, as defined below:

Level 1 – Subject Matter Experts (SME’s) Level 2 – DTMB Project Manager Level 3 – DTMB Executive Manager

Level 1 Help Desk includes initial documentation and routing of reported issue.

Issue Management Approach

Project management spans the entire life cycle of the project and includes iterative processes and activities, including Issue Management. The Contractor shall apply a disciplined, rigorous, and control-based methodology to this important management function. The Contractor’s issue management approach includes interaction and coordination with the State and the Contractor team, improves the quality of the Contractor's work, and lowers delivery risk.


92

MI ECC 11.0093

Step 1: Issue Detected

Step 2: Document Issue

(New)

Step 3:Review

New Entries

Step 8:Deferred (on hold)

Step 4: Assign “Person

Responsible”(in progress)

Step 5: Propose

Resolution(in progress)

Step 7: Close Issue

(closed)

Step 9:Review Deferred

Issue

Step 6:Review

Solution

Not Resolved

Resolved

Deferred Deferred

Previously Deferred

Rejected or

DeferredValid Issue

Figure 7. Issue Management.

The Contractor shall provide timely and accurate tracking, control, monitoring, and reporting of issues as defined by SLAs. Several discrete process steps make up the issue management process, leading to a repeatable, well-understood and functioning process as shown in Figure 7. The process includes identifying and tracking an issue, as well as attaining a resolution.

The Contractor team shall view issue management as an iterative, collaborative, and ongoing process to identify and respond timely to project issues. Open and honest communication about project issues and potential action plans further promotes collaboration. The Contractor team shall be involved throughout the process and supports the Agencies initiation of the issue to its successful resolution. See Table 23 Issue Management Responsibilities of the parties.

Table 23. DTMB, Customer Agency and Contractor Responsibilities for issue management

The Contractor team shall distinguish between issues and risks. An issue is an identified event that may affect schedule, scope, quality or budget. Risks are a proactive look to identify possible events that could negatively affect the project. Once realized, a risk may become an issue. As issues are resolved and closed, the resulting situation may introduce a new risk, may result in change controls, or result in new initiatives or plans.

As issues are reviewed, discussed, and managed at various levels within the project, some may need to be escalated to the next management level to gain appropriate guidance and to reach decisions. The Contractor shall discuss issues at the monthly operational meetings where many issues are resolved. If the issue is not resolved at Level 2, it shall be escalated to Level 3. This process continues up through the levels. An example of the escalation process is illustrated in Figure 8. When an issue travels through the multiple levels of state-defined escalation levels, the Contractor shall support every step so that issues are resolved in a timely manner. The Contractor team shall work closely with the various levels of management and leadership supporting expedient issue escalation and resolution. Issues are formally tracked and escalated for resolution from Level 1 through Level 3, as defined below:


Agency Contractor

Monitor Issues for timely resolution and minimal impact � � � Track Issues in the Issue Tracker Tool � Issue Resolution � � Issue Escalation � � � User Acceptance Testing during issue resolution � Application Regression Testing during issue resolution � Communication through project meetings � � � Issue and Change Control meetings � � �


93

Deputy Director

Director

Functional Owner

EscalationResolution

Functional ManagerBusiness Analyst

MiECC Project Manager

MDIT Program Manager

Project Technical Lead

Expert Programmer AnalystSenior Programmer Analyst

Business Issues Technical Issues

MI ECC 11.0095

Figure 8. Issue Escalation.

Issue Tool Usage

The Contractor shall use the Issue Tracker Tool to identify, document, manage, resolve, and report issue status and resolution. The Contractor shall work collaboratively with the State to proactively identify issues and thoroughly document each issue. Each issue shall contain the following information:

Issue Subject Description of the issue Start date Due date Assignee Status Priority (to be mutually agreed upon by the State and the Contractor)

Contractor shall use a DTMB-approved tool to track issues.

The issue management log is kept up to date for input to the weekly Contractor project management and status meetings. Proactive issue management and reporting is essential to understanding project status, increasing project quality, and reducing risk. The Contractor shall report status and issues weekly to the State. The Contractor shall perform issue management through collaboration with the State.

1.402 Risk Management

A risk is an unknown circumstance or event that, if it occurs, may have a positive or negative impact on the project.

The Contractor is responsible for establishing a risk management plan and process, including the identification and recording of risk items, prioritization of risks, definition of mitigation strategies, monitoring of risk items, and periodic risk assessment reviews with the State.

A risk management plan format shall be submitted to the State for approval within twenty (20) business days after the effective date of the Contract. The risk management plan will be developed during the initial planning phase of the project, and be in accordance with the State’s PMM methodology. Once both parties have agreed to the format of the plan, it shall become the standard to follow for the duration of the contract. The plan must be updated bi-weekly, or as agreed upon.


94

The Contractor shall use a DTMB-approved tool to track risks. The Contractor shall work with the State and allow input into the prioritization of risks. The Contractor is responsible for identification of risks for each phase of the project. Mitigating and/or eliminating assigned risks will be the responsibility of the Contractor. The State will assume the same responsibility for risks assigned to them.

Risk Management Approach

The MiECC project requires diligent risk management to proactively identify and mitigate risks. Contractor’s risk management approach shall focus on identifying and reducing potential risks so that the Contractor can achieve project objectives throughout the project lifecycle. Risk management shall be performed as part of normal delivery. Contractor shall use a standard, repeatable risk management process for all of its projects. The Contractor shall work closely and collaborate with DTMB, to proactively manage known risks and react rapidly to unanticipated risks.

The Contractor Risk Management Plan shall be used by the State to provide an effective risk management framework for the project. The plan shall discuss where risks are identified, recorded, prioritized, mitigated, monitored, and reviewed. This comprehensive risk management approach yields many benefits, as illustrated in Table 24.

Table 24.

Contractor shall use the existing plan as a starting point to develop and deliver a revised Risk Management Plan during the initial planning phase of the project. Contractor’s ability to maintain the project’s momentum by modifying the existing plan and continuing with an integrated Contractor and risk process results in no program disruption, continued focus on release management, and high quality application maintenance services.

Table 25 sets forth s DTMB, Customer Agency and Contractor responsibilities regarding Risk Management.

appropriate direction without jeopardizing the progress of concurrent work efforts

Steps to Managing Risk Benefits to the Customer Step 1 – Proactively Classify Risks Our approach identifies and classifies risks from a

variety of sources early before they become issues. This serves to reduce the risk of scheduled delays, cost overruns, and performance problems

We document risks in the Risk Tracker Tool providing complete visibility and access to risks by the State and PMO

Step 2 – Analyze and Prioritize Risk We document areas where the consequences ofrisk are most severe in order to direct our efforts at addressing high priority risks before they become issues. We assess impact and probability to assist with prioritization and effective monitoring

Step 3 – Determine Risk Response Approach If a risk could affect the achievement of project dates, the project leadership team works to identifyand evaluate potential courses of action. The State, PMO, and Accenture weighs the pros and cons of various mitigation actions, identify the appropriate course of action, and move toward applying adecision

Step 4 – Monitor and Control Risks By capturing all risks through the Tracking Tool, the State and PMO can easily view the information relating to any risk. Thi s access assists the project leadership to provide


95

Table 25. DTMB, Customer Agency and Contractor Responsibilities for Risk Management

Risks and Assumptions

In a project sense, an assumption is something Contractor establishes as true for the purposes of allowing project work to proceed, usually during the planning and estimating phase. Assumptions enable the project to move forward without absolutely certain information. For example, when performing the project planning for a server replacement project, the Contractor may assume that it shall have access to the new servers at a certain time to configure required applications and software, even though at the early planning stage Contractor is dependent on the State for procuring the servers and on the State's server team to complete their activities on time. The Contractor monitors records in the risk tracker tool as a risk, tracks and manages assumptions using the risk management process.

Risk Tracking

The Contractor shall detail the comprehensive risk processes in the Risk Management Plan. The Contractor shall delineate discrete steps and processes that serve to communicate risk status. The Contractor MiECC Risk Management Plan calls out four major steps used by Contractor and the State to identify, monitor, manage and track project risks.

The Contractor shall develop the initial plan in concert with the State using the State’s PMM methodology and our Risk Management Plan template as a starting point. Contractor shall use the project documents from the State Unified Information Technology Enterprise (SUITE) templates for the development of a new Risk Plan.

Identify and Classify Risk

The Contractor shall approach risk identification as an iterative and collaborative process with the State focusing on identifying risk events and subsequently monitoring them throughout the project lifecycle. The Contractor shall identify risks during the ongoing project management process, which includes Weekly Status Meetings and release planning meetings.

The Contractor shall work with project team members, subject matter experts, stakeholders, and project management to identify risks as early as possible and continue monitoring them throughout the project. The Contractor shall document and add risks to the risk tracker tool. The Contractor Project Manager shall meet with DTMB Program Manager weekly to identify, review, or discuss project operational or organizational risks.

Analyze Risk

The Contractor shall analyze new risks. The outputs of risk analysis are the assessment of the impact and probability of identified risks.


Agency Contractor

Identify, Monitor and Mitigate Risks � � �

Track Risks in the Risk Tracker Tool �

Analyze Risk and Determine Risk Response Approach � � �

Control Risks �

Communication through project meetings � � �

Risk and Change Control meetings � � �


96

Determine Risk Response Approach

The Contractor shall work with the State to identify options that shall turn risk information into decisions and actions. The Contractor shall document actions in the Risk Management tool.

Risk Monitoring and Control

During risk monitoring and control, the Contractor and the other members of the Project Management Team keep track of identified risks, monitor residual risks, execute the risk plans, and monitor their effectiveness in reducing risk. Risk tracking is essential to effective action plan implementation.

The Contractor shall devise risk metrics and triggering events to monitor and gauge effectiveness of planned risk actions. The Contractor shall accomplish this through regular and frequent reporting.

The Contractor shall continue to build and update the present risk list using the project leadership team’s experience and knowledge. The Contractor shall, as the project proceeds, continue to identify risks in each project phase and actively work each risk, eliminating and mitigating those risks assigned to Contractor. For those risks assigned to the State, Contractor shall collaborate with State to reach closure. Contractor shall review the initial risk list with the State to confirm its accuracy and to identify additional risks. Contractor shall continue to identify risks throughout the project, adding risks to the list, and reporting on risks in accordance with the project’s governance structure.

Tool Usage

Contractor shall use a risk tracker tool and methodology, to manage risks. The Contractor shall provide a weekly risk log that provides input to the weekly Contractor MiECC project management and status meeting.

1.403 Change Management

Change management is defined as the process to communicate, assess, monitor, and control all changes to system resources and processes. The State also employs change management in its administration of the Contract. If a proposed Contract change is approved by the Agency, the Contract Administrator will submit a request for change to the Department of Technology, Management and Budget, Purchasing Operations Buyer, who will make recommendations to the Director of Purchasing Operations regarding ultimate approval/disapproval of change request. If the DTMB Purchasing Operations Director agrees with the proposed modification, and all required approvals are obtained (including State Administrative Board), the Purchasing Operations Buyer will issue an addendum to the Contract, via a Contract Change Notice. Contractors who provide products or services prior to the issuance of a Contract Change Notice by the DTMB Purchasing Operations, risk non-payment for the out-of-scope/pricing products and/or services. The Contractor shall employ change management procedures to handle such things as “out-of-scope” requests or changing business needs of the State while the migration is underway. The Contractor shall employ the change control methodologies to justify changes in the processing environment, and to ensure those changes will not adversely affect performance or availability.

Change Management Approach

The Contractor team's approach to managing changes on the project allows us to identify potential impacts of proposed changes, develop mitigation strategies to minimize negative impacts, and control the outcome. Strong collaboration with the State shall facilitate the Change Control Process, providing continuous support through the delivery of detailed estimates and impact analyses to aid the decision to accept or deny a change. Contractor team shall employ change management methodologies and processes that provide the State with the ability to remain proactive, deliberate in its assessment of impacts and estimates, and avoid costly program risk.


97

In a project environment, positive changes can have unintended impacts. There are two types of changes that impact project processes. Each type of change requires a different management approach:

Changes that impact planned releases that are within the scope of the Contract but require change decisions

Out-of-Scope changes that go beyond the Contract and require a Contract modification

Contractor shall use a proactive, collaborative approach in the change control and contract change processes to promote synergy and drive our successful release delivery and Contract compliance. This approach involves proactively identifying, assessing, responding to, and determining the disposition of the change request. The Contractor shall be responsible for analyzing change control requests and out-of-scope requests to estimate the level of effort it takes to accommodate the change, assess its impact on release/project cost, schedule, and quality, and recommend the appropriate course of action. The team shall use this information to work with the appropriate stakeholders to facilitate a quick and informed decision to approve or deny the request for change.

The project shall handle changes within scope via the MiECC Change Control process to assess requested changes, and to verify the changes do not adversely affect system performance or availability. For example, production changes are scheduled outside of the normal operating hours to allow for the least amount of impact to the system users. The in scope changes shall follow the documented process complete with client sign-offs, deployment plans, and dry run examples. For example, when Contractor implements new hardware, the Contractor may plan to test new hardware\ one night and then implement a full cutover another night. This cutover test allows the system to be tested before allowing users access on the system therefore, lowering the risk. The parties shall handle out-of-scope change requests and changing business needs of the State through the MiECC Contract Control process which assesses the level of effort required to accommodate the request and acquire the State’s approval to modify the contract.

The State’s Change Control process and the Contract Change Control process are established processes. The Contractor shall work with the State in the Change Control Process. Contractor’s team shall support the State in instituting the necessary change management procedures and methodologies to enable release delivery and compliance with the MiECC contract.

Tool Usage

The Contractor team shall use the State’s System Engineering Methodology (SEM) and Project Management Methodology (PMM) processes, templates, and tools for change control across the MiECC system development and maintenance efforts and MiECC Contract change control efforts. The Contractor project team shall log and track change controls for in scope software changes via the RFC website.

The Contractor team shall use the ADM knowledge base for estimation and configuration management to develop the level of effort estimates and assess the impact of each change. This shall help the Contractor to make recommendations that reduce risk and negative impacts to cost, quality, and schedule of the services delivered in the planned release. Contractor shall take the estimates and provide them in the format as prescribed by SEM and PMM.

MiECC Release Change Control Process

Change controls are critical to planned MiECC releases. The goal of change control is to have consistent and controlled handling of all requests for changes to the release scope, deliverables, timeframes, or resources, in order to avoid negatively influencing services the release delivers to MiECC users. Other change controls shall be necessary in order to document deviations from the standard process.

Change controls build rigor into the process and verify that proposed changes not negatively influence the cost, schedule, and quality associated with the release. Drivers such as “removing a unit of work from a release” or “moving the release date” are significant changes. The management team shall take into consideration significant changes with the local and enterprise control board.


98

The Contractor team shall work collaboratively with the Agencies and members of the Change Control Boards (CCB’s) to support the MiECC Change Control Process. The Contractor team shall be involved throughout the process and support the Agencies and the Change Control Board’s from initiation of the request through implementation. See Table 26 for Change Management Responsibilities.

Table 26. DTMB, Customer Agencies, and Contractor Responsibilities for changes impacting operations

Contractor shall provide complete Request For Change (RFC) required information to the Agency before the Change Control Board (CCB) review to allow them to review the request and enable the CCB to make a quick and informed decision about the change.

MiECC Contract Change Process

The State employs a formal process to handle requests that trigger changes to the services and support delivered through the contract. The Contractor’s Contract Administrator shall maintain a Contract compliance matrix and a scope control document that helps the Contractor team assess work they perform and determine whether a particular request is in the current scope of the Contract or not. Contractor shall monitor changes from two vantage points:

Is the change within the scope of services for our contract?

Is the change within the budget of our contract?

If the answer to either of these is ‘No,’ then Contractor team initiates the Contract change process.

The Contractor shall work with DTMB and the Agencies through the Contract Change Control process. The State shall authorize new enhancements through the SOW process and pursue without a formal change to the Contract if:

The enhancements are within the budgeted SOW amount for the Contract and

Do not require services outside of those contemplated in Contractor’s base contract

Any change deemed outside the budget for the project or the originally contemplated scope of services requires a formal Contract change. All such Contract changes are pursued first by DTMB and, if approved, are submitted to the MiECC Contract Administrator. The Contract Administrator then shall submit a request for change to the Department of Technology Management and Budget (DTMB), Purchasing Operations Buyer, who shall make recommendations to the Director of Purchasing Operations regarding ultimate approval/disapproval of change request. If the DTMB Purchasing Operations Director agrees with the proposed modification, and all required approvals are obtained (including State Administrative Board), the Purchasing Operations Buyer shall issue an addendum to the Contract, via a Contract Change Notice.

1.500 Acceptance

1.501 Criteria

Acceptance is tied to meeting the defined acceptance criteria and performance service levels.


Agency Contractor

Identify changes that could impact operations Yes Yes Yes Communicate changes to agencies Yes Yes Create RFC's for production changes Yes Attend CCB meeting Yes Communicate status of approval of RFC to Contractor Yes Communicate status of Contractor created RFC's Success/Failure of RFC to DTMB and Agencies

Yes


99

1.502 Final Acceptance

Final Acceptance is tied to performance of required Services and delivery of identified deliverables during the term of the Contract.

1.600 Compensation and Payment

1.601 Compensation And Payment

Method of Payment The project will be paid as a combination of fixed price and rate card as detailed below. The Costs Table(s) attached must be used as the format for submitting pricing information.

A. Knowledge Transfer Cost There is no Knowledge Transfer cost.

B. Base Support Cost A total fixed cost by year includes all of the tasks as described in Section 1.104 I A (Base Support).

For future implementation/support of additional contact centers, the increase in the Base Support cost will be mutually agreed upon with a SOW. See Attachment 10: Cost of Additional Contact Centers.

After providing monthly services, the Contractor shall submit an invoice at the end of the month.

C. Major Enhancement and Other Contact Center Services Costs In Table 4 Rate Card. the Contractor confirmed the personnel, skills and rates that they shall use to complete the Major Enhancements. The pricing approach is based on leveraging the existing Base Support team fort change orders that arrive when appropriate. This approach is intended to reduce the cost of each change order as fewer hours are required, and allows for improved quality and speeds delivery.

Major Enhancements may be paid on either of two cost models – fixed price, deliverable based or time and materials (hourly rate).

For fixed price proposals, the Contractor shall identify the skill sets and anticipated number of hours used by each skill set to justify the cost. For payment, the Contractor shall send the invoice after the deliverable is accepted.

For time and materials, the Contractor shall use the rates set forth in Attachment 3A - Cost Tables, Table 4 - Rate Card, unless lower rates are negotiated. For payment, the Contractor shall send the invoice after the end of the month. This invoice must be supported by timesheet for each consultant showing days and hours worked on the project.

The rate card (Attachment 3A, Table 4) details hourly rates for skills for this Contract. During the Contract period, the Contractor shall provide cost quotes for detailed statements of work that will be created by the State for Major Enhancements. If these costs are accepted, a change order shall be made to the Contract to allow these implementations to proceed.

Travel The State will not pay for any travel expenses, including hotel, mileage, meals, parking, etc. Travel time will not be reimbursed.

Statements of Work and Issuance of Purchase Orders

Unless otherwise agreed by the parties, each SOW will include: 1. Background 2. Project Objective 3. Scope of Work 4. Deliverables 5. Acceptance Criteria


100

6. Project Control and Reports 7. Specific Department Standards 8. Payment Schedule 9. Travel and Expenses

10. Project Contacts 11. Agency Responsibilities and Assumptions 12. Location of Where the Work is to be performed 13. Expected Contractor Work Hours and Conditions

The parties agree that the Services/Deliverables to be rendered by Contractor pursuant to this Contract (and any future amendments of it) will be defined and described in detail in Statements of Work or Purchase Orders (PO) executed under this Contract. Contractor shall not be obliged or authorized to commence any work to implement a SOW until authorized via a PO issued against this Contract. Contractor shall perform in accordance with this Contract, including the Statements of Work/Purchase Orders executed under it. Invoicing Contractor will submit properly itemized invoices to

DTMB – Financial Services Accounts Payable P.O. Box 30026 Lansing, MI 48909 or [email protected]

. Invoices must provide and itemize, as applicable:

Contract number; Purchase Order number Contractor name, address, phone number, and Federal Tax Identification Number; Description of any commodities/hardware, including quantity ordered; Date(s) of delivery and/or date(s) of installation and set up; Price for each item, or Contractor’s list price for each item and applicable discounts; Maintenance charges; Net invoice price for each item; Shipping costs; Other applicable charges; Total invoice price; and Payment terms, including any available prompt payment discount.

The State may pay maintenance and support charges on a monthly basis, in arrears. Payment of maintenance service/support of less than one (1) month’s duration shall be prorated at 1/30th of the basic monthly maintenance charges for each calendar day. Incorrect or incomplete invoices will be returned to Contractor for correction and reissue.

1.602 Holdback

RESERVED


101

Article 2, Terms and Conditions

2.000 Contract Structure and Term 2.001 Contract Term This Contract is for a period of 5 years beginning May 1, 2012 through April 30, 2017. All outstanding Purchase Orders must also expire upon the termination for any of the reasons listed in Section 2.150 of the Contract, unless otherwise extended under the Contract. Absent an early termination for any reason, Purchase Orders issued but not expired, by the end of the Contract’s stated term, shall remain in effect for the balance of the fiscal year for which they were issued.

2.002 Options to Renew

This Contract may be renewed in writing by mutual agreement of the parties not less than 30 days before its expiration. The Contract may be renewed for up to 5 additional 1 year periods.

2.003 Legal Effect

Contractor accepts this Contract by signing two copies of the Contract and returning them to the Purchasing Operations. The Contractor shall not proceed with the performance of the work to be done under the Contract, including the purchase of necessary materials, until both parties have signed the Contract to show acceptance of its terms, and the Contractor receives a contract release/purchase order that authorizes and defines specific performance requirements. Except as otherwise agreed in writing by the parties, the State shall not be liable for costs incurred by Contractor or payment under this Contract, until Contractor is notified in writing that this Contract or Change Order has been approved by the State Administrative Board (if required), signed by all the parties and a Purchase Order against the Contract has been issued.

2.004 Attachments & Exhibits

All Attachments and Exhibits affixed to any and all Statement(s) of Work, or appended to or referencing this Contract, are incorporated in their entirety and form part of this Contract.

2.005 Ordering

The State must issue an approved written Purchase Order, Blanket Purchase Order, Direct Voucher or Procurement Card Order to order any Services/Deliverables under this Contract. All orders are subject to the terms and conditions of this Contract. No additional terms and conditions contained on either a Purchase Order or Blanket Purchase Order apply unless they are specifically contained in that Purchase Order or Blanket Purchase Order's accompanying Statement of Work. Exact quantities to be purchased are unknown; however, the Contractor will be required to furnish all such materials and services as may be ordered during the Contract period. Quantities specified, if any, are estimates based on prior purchases, and the State is not obligated to purchase in these or any other quantities.

2.006 Order of Precedence

The Contract, including any Statements of Work and Exhibits, to the extent not contrary to the Contract, each of which is incorporated for all purposes, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior agreements, whether written or oral, with respect to the subject matter and as additional terms and conditions on the purchase order must apply as limited by Section 2.005. In the event of any inconsistency between the terms of the Contract and a Statement of Work, the terms of the Statement of Work shall take precedence (as to that Statement of Work only); provided, however, that a Statement of Work may not modify or amend the terms of the Contract. The Contract may be modified or amended only by a formal Contract amendment.


102

2.007 Headings

Captions and headings used in the Contract are for information and organization purposes. Captions and headings, including inaccurate references, do not, in any way, define or limit the requirements or terms and conditions of the Contract.

2.008 Form, Function & Utility

If the Contract is for use of more than one State agency and if the Deliverable/Service does not meet the form, function, and utility required by that State agency, that agency may, subject to State purchasing policies, procure the Deliverable/Service from another source.

2.009 Reformation and Severability

Each provision of the Contract is severable from all other provisions of the Contract and, if one or more of the provisions of the Contract is declared invalid, the remaining provisions of the Contract remain in full force and effect.

2.010 Consents and Approvals Except as expressly provided otherwise in the Contract, if either party requires the consent or approval of the other party for the taking of any action under the Contract, the consent or approval must be in writing and must not be unreasonably withheld or delayed.

2.011 No Waiver of Default

If a party fails to insist upon strict adherence to any term of the Contract then the party has not waived the right to later insist upon strict adherence to that term, or any other term, of the Contract.

2.012 Survival

Any provisions of the Contract that impose continuing obligations on the parties, including without limitation the parties’ respective warranty, indemnity and confidentiality obligations, survive the expiration or termination of the Contract for any reason. Specific references to survival in the Contract are solely for identification purposes and not meant to limit or prevent the survival of any other section.

2.020 Contract Administration

2.021 Issuing Office

This Contract is issued by the Department of Technology, Management and Budget, Purchasing Operations. DTMB-Procurement is the sole point of contact in the State with regard to all procurement and contractual matters relating to the Contract. The DTMB-Procurement Contract Administrator for this Contract is: Mark Lawrence Buyer Procurement Department of Technology, Management and Budget Mason Bldg, 2nd Floor PO Box 30026 Lansing, MI 48909 Email: [email protected] Phone: 517-241-1640

2.022 Contract Compliance Inspector

The Director of DTMB-Procurement directs the person named below, or his or her designee, to monitor and coordinate the activities for the Contract on a day-to-day basis during its term. Monitoring Contract activities does not imply the authority to change, modify, clarify, amend, or otherwise alter the prices, terms, conditions and specifications of the Contract. DTMB-Procurement is the only State office authorized to


103

change, modify, amend, alter or clarify the prices, specifications, terms and conditions of this Contract. The Contract Compliance Inspector for this Contract is:

Mark Lawrence, Buyer DTMB-Procurement Department of Technology, Management and Budget Mason Bldg., 2nd Floor PO Box 30026 Lansing, MI 48909 Email: [email protected] Phone: 517-241-1640

2.023 Project Manager

The following individual will oversee the project:

Abhijit Sarkar Department of Technology, Management and Budget Operations Center – 2nd Floor 7285 Parsons Dr. Dimondale, MI Email: [email protected] Phone: 517-636-5058

2.024 Change Requests

The State reserves the right to request from time to time any changes to the requirements and specifications of the Contract and the work to be performed by the Contractor under the Contract. During the course of ordinary business, it may become necessary for the State to discontinue certain business practices or create Additional Services/Deliverables. At a minimum, to the extent applicable, Contractor shall provide a detailed outline of all work to be done, including tasks necessary to accomplish the Additional Services/Deliverables, timeframes, listing of key personnel assigned, estimated hours for each individual per task, and a complete and detailed cost justification.

If the State requests or directs the Contractor to perform any Services/Deliverables that are outside the scope of the Contractor’s responsibilities under the Contract (“New Work”), the Contractor must notify the State promptly before commencing performance of the requested activities it believes are New Work. If the Contractor fails to notify the State before commencing performance of the requested activities, any such activities performed before the Contractor gives notice shall be conclusively considered to be in-scope Services/Deliverables and not New Work.

If the State requests or directs the Contractor to perform any services or provide deliverables that are consistent with and similar to the Services/Deliverables being provided by the Contractor under the Contract, but which the Contractor reasonably and in good faith believes are not included within the Statements of Work, then before performing such Services or providing such Deliverables, the Contractor shall notify the State in writing that it considers the Services or Deliverables to be an Additional Service/Deliverable for which the Contractor should receive additional compensation. If the Contractor does not so notify the State, the Contractor shall have no right to claim thereafter that it is entitled to additional compensation for performing that Service or providing that Deliverable. If the Contractor does so notify the State, then such a Service or Deliverable shall be governed by the Change Request procedure in this Section.

In the event prices or service levels are not acceptable to the State, the Additional Services or New Work shall be subject to competitive bidding based upon the specifications.

(1) Change Request at State Request If the State requires Contractor to perform New Work, Additional Services or make changes to the

Services that would affect the Contract completion schedule or the amount of compensation due


104

Contractor (a “Change”), the State shall submit a written request for Contractor to furnish a proposal for carrying out the requested Change (a “Change Request”).

(2) Contractor Recommendation for Change Requests: Contractor shall be entitled to propose a Change to the State, on its own initiative, should Contractor

believe the proposed Change would benefit the Contract. (3) Upon receipt of a Change Request or on its own initiative, Contractor shall examine the implications of the

requested Change on the technical specifications, Contract schedule and price of the Deliverables and Services and shall submit to the State without undue delay a written proposal for carrying out the Change. Contractor’s proposal shall include any associated changes in the technical specifications, Contract schedule and price and method of pricing of the Services. If the Change is to be performed on a time and materials basis, the Labor Rates set forth in Attachment 3 shall apply to the provision of such Services. If Contractor provides a written proposal and should Contractor be of the opinion that a requested Change is not to be recommended, it shall communicate its opinion to the State but shall nevertheless carry out the Change as specified in the written proposal if the State directs it to do so.

(4) By giving Contractor written notice within a reasonable time, the State shall be entitled to accept a Contractor proposal for Change, to reject it, or to reach another agreement with Contractor. Should the parties agree on carrying out a Change, a written Contract Change Notice must be prepared and issued under this Contract, describing the Change and its effects on the Services and any affected components of this Contract (a “Contract Change Notice”).

(5) No proposed Change shall be performed until the proposed Change has been specified in a duly executed Contract Change Notice issued by the Department of Technology, Management and Budget, Purchasing Operations.

(6) If the State requests or directs the Contractor to perform any activities that Contractor believes constitute a Change, the Contractor must notify the State that it believes the requested activities are a Change before beginning to work on the requested activities. If the Contractor fails to notify the State before beginning to work on the requested activities, then the Contractor waives any right to assert any claim for additional compensation or time for performing the requested activities. If the Contractor commences performing work outside the scope of this Contract and then ceases performing that work, the Contractor must, at the request of the State, retract any out-of-scope work that would adversely affect the Contract.

2.025 Notices

Any notice given to a party under the Contract must be deemed effective, if addressed to the party as addressed below, upon: (i) delivery, if hand delivered; (ii) receipt of a confirmed transmission by facsimile if a copy of the notice is sent by another means specified in this Section; (iii) the third Business Day after being sent by U.S. mail, postage pre-paid, return receipt requested; or (iv) the next Business Day after being sent by a nationally recognized overnight express courier with a reliable tracking system. State: State of Michigan Procurement Attention: Mark Lawrence PO Box 30026 530 West Allegan Lansing, Michigan 48909 Contractor: Accenture LLP Name: Jamie Walker Address: 3000 Town Center, Suite 2400, Southfield, Mi. 48075 Either party may change its address where notices are to be sent by giving notice according to this Section.


105

2.026 Binding Commitments Representatives of Contractor must have the authority to make binding commitments on Contractor’s behalf within the bounds set forth in the Contract. Contractor may change the representatives from time to time upon giving written notice.

2.027 Relationship of the Parties The relationship between the State and Contractor is that of client and independent contractor. No agent, employee, or servant of Contractor or any of its Subcontractors shall be deemed to be an employee, agent or servant of the State for any reason. Contractor shall be solely and entirely responsible for its acts and the acts of its agents, employees, servants and Subcontractors during the performance of the Contract.

2.028 Covenant of Good Faith Each party shall act reasonably and in good faith. Unless stated otherwise in the Contract, the parties shall not unreasonably delay, condition or withhold the giving of any consent, decision or approval that is either requested or reasonably required of them in order for the other party to perform its responsibilities under the Contract.

2.029 Assignments Neither party may assign the Contract, or assign or delegate any of its duties or obligations under the Contract, to any other party (whether by operation of law or otherwise), without the prior written consent of the other party; provided, however, that the State may assign the Contract to any other State agency, department, division or department without the prior consent of Contractor and Contractor may assign the Contract to an affiliate so long as the affiliate is adequately capitalized and can provide adequate assurances that the affiliate can perform the Contract. The State may withhold consent from proposed assignments, subcontracts, or novations when the transfer of responsibility would operate to decrease the State’s likelihood of receiving performance on the Contract or the State’s ability to recover damages.

Contractor may not, without the prior written approval of the State, assign its right to receive payments due under the Contract. If the State permits an assignment, the Contractor is not relieved of its responsibility to perform any of its contractual duties and the requirement under the Contract that all payments must be made to one entity continues.

If the Contractor intends to assign the Contract or any of the Contractor's rights or duties under the Contract, the Contractor must notify the State in writing at least 90 days before the assignment. The Contractor also must provide the State with adequate information about the assignee within a reasonable amount of time before the assignment for the State to determine whether to approve the assignment.

2.030 General Provisions

2.031 Media Releases News releases (including promotional literature and commercial advertisements) pertaining to the RFP and Contract or project to which it relates shall not be made without prior written State approval, and then only in accordance with the explicit written instructions from the State. No results of the activities associated with the RFP and Contract are to be released without prior written approval of the State and then only to persons designated.

2.032 Contract Distribution Purchasing Operations retains the sole right of Contract distribution to all State agencies and local units of government unless other arrangements are authorized by DTMB-Procurement.

2.033 Permits Contractor must obtain and pay any associated costs for all required governmental permits, licenses and approvals for the delivery, installation and performance of the Services. The State shall pay for all costs and expenses incurred in obtaining and maintaining any necessary easements or right of way.


106

2.034 Website Incorporation The State is not bound by any content on the Contractor’s website, even if the Contractor’s documentation specifically referenced that content and attempts to incorporate it into any other communication, unless the State has actual knowledge of the content and has expressly agreed to be bound by it in a writing that has been manually signed by an authorized representative of the State.

2.035 Future Bidding Preclusion

Contractor acknowledges that, to the extent this Contract involves the creation, research, investigation or generation of a future RFP; it may be precluded from bidding on the subsequent RFP. The State reserves the right to disqualify any Bidder if the State determines that the Bidder has used its position (whether as an incumbent Contractor, or as a Contractor hired to assist with the RFP development, or as a Vendor offering free assistance) to gain a competitive advantage on the RFP.

2.036 Freedom of Information

All information in any proposal submitted to the State by Contractor and this Contract is subject to the provisions of the Michigan Freedom of Information Act, 1976 Public Act No. 442, as amended, MCL 15.231, et seq (the “FOIA”).

2.037 Disaster Recovery

Contractor and the State recognize that the State provides essential services in times of natural or man-made disasters. Therefore, except as so mandated by Federal disaster response requirements, Contractor personnel dedicated to providing Services/Deliverables under this Contract shall provide the State with priority service for repair and work around in the event of a natural or man-made disaster.

2.040 Financial Provisions

2.041 Fixed Prices for Services/Deliverables Each Statement of Work or Purchase Order issued under this Contract shall specify (or indicate by reference to the appropriate Contract Exhibit) the firm, fixed prices for all Services/Deliverables, and the associated payment milestones and payment amounts. The State may make progress payments to the Contractor when requested as work progresses, but not more frequently than monthly, in amounts approved by the Contract Administrator, after negotiation. Contractor shall show verification of measurable progress at the time of requesting progress payments.

2.042 Adjustments for Reductions in Scope of Services/Deliverables If the scope of the Services/Deliverables under any Statement of Work issued under this Contract is subsequently reduced by the State, the parties shall negotiate an equitable reduction in Contractor’s charges under such Statement of Work commensurate with the reduction in scope.

2.043 Services/Deliverables Covered The State shall not be obligated to pay any amounts in addition to the charges specified in this Contract for all Services/Deliverables to be provided by Contractor and its Subcontractors, if any, under this Contract.

2.044 Invoicing and Payment – In General (a) Each Statement of Work issued under this Contract shall list (or indicate by reference to the appropriate

Contract Exhibit) the prices for all Services/Deliverables, equipment and commodities to be provided, and the associated payment milestones and payment amounts.

(b) Each Contractor invoice shall show details as to charges by Service/Deliverable component and location at a level of detail reasonably necessary to satisfy the State’s accounting and charge-back requirements. Invoices for Services performed on a time and materials basis shall show, for each individual, the number of hours of Services performed during the billing period, the billable skill/labor category for such person and the applicable hourly billing rate. Prompt payment by the State is contingent on the Contractor’s invoices showing the amount owed by the State minus any holdback amount to be retained by the State in accordance with Section 1.600.


107

(c) Correct invoices shall be due and payable by the State, in accordance with the State’s standard payment procedure as specified in 1984 Public Act No. 279, MCL 17.51 et seq., within 45 days after receipt, provided the State determines that the invoice was properly rendered.

(d) All invoices should reflect actual work done. Specific details of invoices and payments shall be agreed upon between the Contract Administrator and the Contractor after the proposed Contract Agreement has been signed and accepted by both the Contractor and the Director of Purchasing Operations, Department of Management & Budget. This activity shall occur only upon the specific written direction from DTMB-Procurement.

The specific payment schedule for any Contract(s) entered into, as the State and the Contractor(s) shall mutually agree upon. The schedule should show payment amount and should reflect actual work done by the payment dates, less any penalty cost charges accrued by those dates. As a general policy, statements shall be forwarded to the designated representative by the 15th day of the following month.

The Government may make progress payments to the Contractor when requested as work progresses, but not more frequently than monthly, in amounts approved by the Contract Administrator, after negotiation. Contractor must show verification of measurable progress at the time of requesting progress payments.

2.045 Pro-ration To the extent there are Services that are to be paid for on a monthly basis, the cost of such Services shall be pro-rated for any partial month.

2.046 Antitrust Assignment The Contractor assigns to the State any claim for overcharges resulting from antitrust violations to the extent that those violations concern materials or services supplied by third parties to the Contractor, toward fulfillment of this Contract.

2.047 Final Payment The making of final payment by the State to Contractor does not constitute a waiver by either party of any rights or other claims as to the other party’s continuing obligations under the Contract, nor shall it constitute a waiver of any claims by one party against the other arising from unsettled claims or failure by a party to comply with this Contract. Contractor’s acceptance of final payment by the State under this Contract shall constitute a waiver of all claims by Contractor against the State for payment under this Contract, other than those claims previously filed in writing on a timely basis and still unsettled.

2.048 Electronic Payment Requirement Electronic transfer of funds is required for payments on State Contracts. Contractors are required to register with the State electronically at http://www.cpexpress.state.mi.us. As stated in Public Act 431 of 1984, all contracts that the State enters into for the purchase of goods and services shall provide that payment shall be made by electronic fund transfer (EFT).

2.050 Taxes

2.051 Employment Taxes Contractor shall collect and pay all applicable federal, state, and local employment taxes, including the taxes.

2.052 Sales and Use Taxes

Contractor shall register and remit sales and use taxes on taxable sales of tangible personal property or services delivered into the State. Contractors that lack sufficient presence in Michigan to be required to register and pay tax must do so as a volunteer. This requirement extends to: (1) all members of any controlled group as defined in § 1563(a) of the Internal Revenue Code and applicable regulations of which the company is a member, and (2) all organizations under common control as defined in § 414(c) of the Internal Revenue Code and applicable regulations of which the company is a member that make sales at retail for delivery into the State are registered with the State for the collection and remittance of sales and use taxes. In applying


108

treasury regulations defining “two or more trades or businesses under common control” the term “organization” means sole proprietorship, a partnership (as defined in § 701(a) (2) of the Internal Revenue Code), a trust, an estate, a corporation, or a limited liability company.

2.060 Contract Management

2.061 Contractor Personnel Qualifications All persons assigned by Contractor to the performance of Services under this Contract must be employees of Contractor or its majority-owned (directly or indirectly, at any tier) subsidiaries (or a State-approved Subcontractor) and must be fully qualified to perform the work assigned to them. Contractor must include a similar provision in any subcontract entered into with a Subcontractor. For the purposes of this Contract, independent contractors engaged by Contractor solely in a staff augmentation role must be treated by the State as if they were employees of Contractor for this Contract only; however, the State understands that the relationship between Contractor and Subcontractor is an independent contractor relationship.

2.062 Contractor Key Personnel (a) Key Personnel

(i) In discharging its obligations under this Contract, Contractor shall provide the named Key Personnel on the terms indicated. Section 1.201 Contractor Staff, Roles, and Responsibilities provides an organization chart showing the roles of certain Key Personnel, if any.

(ii) Key Personnel shall be dedicated as defined in Section 1.201 Contractor Staff, Roles, and Responsibilities to the Project for its duration in the applicable Statement of Work with respect to other individuals designated as Key Personnel for that Statement of Work.

(iii) The State will have the right to recommend and approve in writing the initial assignment, as well as any proposed reassignment or replacement, of any Key Personnel. Before assigning an individual to any Key Personnel position, Contractor will notify the State of the proposed assignment, will introduce the individual to the appropriate State representatives, and will provide the State with a resume and any other information about the individual reasonably requested by the State. The State reserves the right to interview the individual before granting written approval. In the event the State finds a proposed individual unacceptable, the State will provide a written explanation including reasonable detail outlining the reasons for the rejection. Additionally, the State’s request shall be based on legitimate, good-faith reasons. Proposed alternative for the individual denied, shall be fully qualified for the position.

(iv) Contractor shall not remove any Key Personnel from their assigned roles or the Contract without the prior written consent of the State. If the Contractor does remove Key Personnel without the prior written consent of the State, it shall be considered an unauthorized removal (“Unauthorized Removal”). It shall not be considered an Unauthorized Removal if Key Personnel must be replaced for reasons beyond the reasonable control of Contractor, including illness, disability, leave of absence, personal emergency circumstances, resignation or for cause termination of the Key Personnel’s employment. It shall not be considered an Unauthorized Removal if Key Personnel must be replaced because of promotions or other job movements allowed by Contractor personnel policies or Collective Bargaining Agreement(s) as long as the State receives prior written notice before shadowing occurs and Contractor provides thirty (30) days of shadowing unless parties agree to a different time period. The Contractor with the State shall review any Key Personnel replacements, and appropriate transition planning will be established. Any Unauthorized Removal may be considered by the State to be a material breach of the Contract, in respect of which the State may elect to exercise its rights under Section 2.150.

(v) It is acknowledged that an Unauthorized Removal will interfere with the timely and proper completion of the Contract, to the loss and damage of the State, and that it would be impracticable and extremely difficult to fix the actual damage sustained by the State as a result of any Unauthorized Removal. Therefore, Contractor and the State agree that in the case of any Unauthorized Removal in respect of which the State does not elect to exercise its rights under Section 2, the State may assess liquidated damages against Contractor as provided for in Section 2.243. (b) Re-assignment of non-Key Personnel. Prior to re-deploying to other projects, at the completion of their assigned tasks on the Project, teams of its non-Key Personnel who are performing Services on-


109

site at State facilities or who are otherwise dedicated primarily to the Project, Contractor will give the State at least ten (10) Business Days notice of the proposed re-deployment to give the State an opportunity to object to the re-deployment if the State reasonably believes such team’s Contract responsibilities are not likely to be completed and approved by the State prior to the proposed date of re-deployment.

2.063 Re-assignment of Personnel at the State’s Request

The State reserves the right to require the removal from the Project of Contractor personnel found, in the judgment of the State, to be unacceptable. The State’s request must be written with reasonable detail outlining the reasons for the removal request. Additionally, the State’s request must be based on legitimate, good faith reasons. Replacement personnel for the removed person must be fully qualified for the position. If the State exercises this right, and the Contractor cannot immediately replace the removed personnel, the State agrees to an equitable adjustment in schedule or other terms that may be affected by the State’s required removal. If any incident with removed personnel results in delay not reasonably anticipatable under the circumstances and which is attributable to the State, the applicable SLAs for the affected Service shall not be counted for a time as agreed to by the parties.

2.064 Contractor Personnel Location

All staff assigned by Contractor to work on the Contract shall perform their duties either primarily at Contractor’s offices and facilities or at State facilities. Without limiting the generality of the foregoing, Key Personnel shall, at a minimum, spend at least the amount of time on-site at State facilities as indicated in the applicable Statement of Work. Subject to availability, selected Contractor personnel may be assigned office space to be shared with State personnel.

2.065 Contractor Identification

Contractor employees must be clearly identifiable while on State property by wearing a State-issued badge, as required. Contractor employees are required to clearly identify themselves and the company they work for whenever making contact with State personnel by telephone or other means.

2.066 Cooperation with Third Parties

Contractor agrees to cause its personnel and the personnel of any Subcontractors to cooperate with the State and its agents and other contractors including the State’s Quality Assurance personnel. As reasonably requested by the State in writing, the Contractor shall provide to the State’s agents and other contractors reasonable access to Contractor’s Project personnel, systems and facilities to the extent the access relates to activities specifically associated with this Contract and shall not interfere or jeopardize the safety or operation of the systems or facilities. The State acknowledges that Contractor’s time schedule for the Contract is very specific and agrees not to unnecessarily or unreasonably interfere with, delay or otherwise impede Contractor’s performance under this Contract with the requests for access.

2.067 Contract Management Responsibilities

Contractor shall be responsible for all acts and omissions of its employees, as well as the acts and omissions of any other personnel furnished by Contractor to perform the Services. Contractor shall have overall responsibility for managing and successfully performing and completing the Services/Deliverables, subject to the overall direction and supervision of the State and with the participation and support of the State as specified in this Contract. Contractor’s duties shall include monitoring and reporting the State’s performance of its participation and support responsibilities (as well as Contractor’s own responsibilities) and providing timely notice to the State in Contractor’s reasonable opinion if the State’s failure to perform its responsibilities in accordance with the Project Plan is likely to delay the timely achievement of any Contract tasks.

The Contractor shall provide the Services/Deliverables directly or through its affiliates, subsidiaries, subcontractors or resellers. Regardless of the entity providing the Service/Deliverable, the Contractor shall act as a single point of contact coordinating these entities to meet the State’s need for Services/Deliverables. Nothing in this Contract, however, shall be construed to authorize or require any party to violate any applicable law or regulation in its performance of this Contract.


110

2.068 Contractor Return of State Equipment/Resources

The Contractor shall return to the State any State-furnished equipment, facilities and other resources when no longer required for the Contract in the same condition as when provided by the State, reasonable wear and tear excepted.

2.070 Subcontracting by Contractor

2.071 Contractor full Responsibility

Contractor shall have full responsibility for the successful performance and completion of all of the Services and Deliverables. The State shall consider Contractor to be the sole point of contact with regard to all contractual matters under this Contract, including payment of any and all charges for Services and Deliverables.

2.072 State Consent to delegation

Contractor shall not delegate any duties under this Contract to a Subcontractor unless the Department of Technology, Management and Budget, Procurement has given written consent to such delegation. The State shall have the right of prior written approval of all Subcontractors and to require Contractor to replace any Subcontractors found, in the reasonable judgment of the State, to be unacceptable. The State’s request shall be written with reasonable detail outlining the reasons for the removal request. Additionally, the State’s request shall be based on legitimate, good faith reasons. Replacement Subcontractor(s) for the removed Subcontractor shall be fully qualified for the position. If the State exercises this right, and the Contractor cannot immediately replace the removed Subcontractor, the State shall agree to an equitable adjustment in schedule or other terms that may be affected by the State’s required removal. If any such incident with a removed Subcontractor results in delay not reasonably anticipatable under the circumstances and which is attributable to the State, the applicable SLA for the affected Work shall not be counted for a time agreed upon by the parties.

2.073 Subcontractor bound to Contract

In any subcontracts entered into by Contractor for the performance of the Services, Contractor shall require the Subcontractor, to the extent of the Services to be performed by the Subcontractor, to be bound to Contractor by the terms of this Contract and to assume toward Contractor all of the obligations and responsibilities that Contractor, by this Contract, assumes toward the State. The State reserves the right to receive copies of and review all subcontracts, although Contractor may delete or mask any proprietary information, including pricing, contained in such contracts before providing them to the State. The management of any Subcontractor shall be the responsibility of Contractor, and Contractor shall remain responsible for the performance of its Subcontractors to the same extent as if Contractor had not subcontracted such performance. Contractor shall make all payments to Subcontractors or suppliers of Contractor. Except as otherwise agreed in writing by the State and Contractor, the State shall not be obligated to direct payments for the Services other than to Contractor. The State’s written approval of any Subcontractor engaged by Contractor to perform any obligation under this Contract shall not relieve Contractor of any obligations or performance required under this Contract. A list of the Subcontractors, if any, approved by the State as of the execution of this Contract, together with a copy of the applicable subcontract is attached as Attachment 6 – List of Approved Subcontractors.

2.074 Flow Down

Except where specifically approved in writing by the State on a case-by-case basis, Contractor shall flow down the obligations in Sections 2.031, 2.060, 2.100, 2.110, 2.120, 2.130, and 2.200 in all of its agreements with any Subcontractors.

2.075 Competitive Selection

The Contractor shall select subcontractors (including suppliers) on a competitive basis to the maximum practical extent consistent with the objectives and requirements of the Contract.


111

2.080 State Responsibilities

2.081 Equipment

The State shall provide only the equipment and resources identified in the Statement of Work and other Contract Exhibits.

2.082 Facilities

The State must designate space as long as it is available and as provided in the Statement of Work, to house the Contractor’s personnel whom the parties agree will perform the Services/Deliverables at State facilities (collectively, the “State Facilities”). The Contractor shall have reasonable access to, and unless agreed otherwise by the parties in writing must observe and comply with all rules and regulations relating to each of the State Facilities (including hours of operation) used by the Contractor in the course of providing the Services. Contractor agrees that it shall not, without the prior written consent of the State, use any State Facilities or access any State information systems provided for the Contractor’s use, or to which the Contractor otherwise gains access in the course of performing the Services, for any purpose other than providing the Services to the State.

2.090 Security

2.091 Background Checks

On a case-by-case basis, the State may investigate the Contractor's personnel before they may have access to State facilities and systems. The scope of the background check is at the discretion of the State and the results shall be used to determine Contractor personnel eligibility for working within State facilities and systems. The investigations shall include Michigan State Police Background checks (ICHAT) and may include the National Crime Information Center (NCIC) Finger Prints. Proposed Contractor personnel may be required to complete and submit an RI-8 Fingerprint Card for the NCIC Finger Print Check. Any request for background checks shall be initiated by the State and shall be reasonably related to the type of work requested.

All Contractor personnel shall also be expected to comply with the State’s security and acceptable use policies for State IT equipment and resources. See http://www.michigan.gov/dit. Furthermore, Contractor personnel shall be expected to agree to the State’s security and acceptable use policies before the Contractor personnel shall be accepted as a resource to perform work for the State. It is expected the Contractor shall present these documents to the prospective employee before the Contractor presents the individual to the State as a proposed resource. Contractor staff shall be expected to comply with all Physical Security procedures in place within the facilities where they are working.

2.092 Security Breach Notification

If the Contractor breaches this Section, the Contractor must (i) promptly cure any deficiencies and (ii) comply with any applicable federal and state laws and regulations pertaining to unauthorized disclosures. Contractor and the State shall cooperate to mitigate, to the extent practicable, the effects of any breach, intrusion, or unauthorized use or disclosure. Contractor must report to the State in writing any use or disclosure of Confidential Information, whether suspected or actual, other than as provided for by the Contract within 10 days of becoming aware of the use or disclosure or the shorter time period as is reasonable under the circumstances.

2.093 PCI DATA Security Requirements Reserved

2.100 Confidentiality

2.101 Confidentiality Contractor and the State each acknowledge that the other possesses and will continue to possess confidential information that has been developed or received by it. As used in this Section, “Confidential Information” of Contractor shall mean all non-public proprietary information of Contractor (other than Confidential Information


112

of the State as defined below) which is marked confidential, restricted, proprietary or with a similar designation. “Confidential Information” of the State shall mean any information which is retained in confidence by the State (or otherwise required to be held in confidence by the State pursuant to applicable federal, state and local laws and regulations) or which, in the case of tangible materials provided to Contractor by the State pursuant to its performance under this Contract, is marked as confidential, proprietary or with a similar designation by the State. In the case of information of either Contractor or the State “Confidential Information” shall exclude any information (including this Contract) that is publicly available pursuant to the Michigan FOIA. The respective rights and obligations for the Contractor and State regarding the handling and treatment of State Personal Data will be governed by Section 2.106 of this Contract.

2.102 Protection and Destruction of Confidential Information

The State and Contractor shall each use at least the same degree of care to prevent disclosing to third parties the Confidential Information of the other as it employs to avoid unauthorized disclosure, publication or dissemination of its own confidential information of like character, but in no event less than reasonable care. Neither Contractor nor the State shall (i) make any use of the Confidential Information of the other except as contemplated by this Contract, (ii) acquire any right in or assert any lien against the Confidential Information of the other, or (iii) if requested to do so, refuse for any reason to promptly return the other party's Confidential Information to the other party. Each party shall limit disclosure of the other party’s Confidential Information to employees and Subcontractors who must have access to fulfill the purposes of this Contract. Disclosure to, and use by, a Subcontractor is permissible where (A) use of a Subcontractor is authorized under this Contract, (B) the disclosure is necessary or otherwise naturally occurs in connection with work that is within the Subcontractor's scope of responsibility, and (C) Contractor obligates the Subcontractor in a written Contract to maintain the State’s Confidential Information in confidence. At the State's request, any employee of Contractor and of any Subcontractor having access or continued access to the State’s Confidential Information may be required to execute an acknowledgment that the employee has been advised of Contractor’s and the Subcontractor’s obligations under this Section and of the employee’s obligation to Contractor or Subcontractor, as the case may be, to protect the Confidential Information from unauthorized use or disclosure. Promptly upon termination or cancellation of the Contract for any reason, Contractor must certify to the State that Contractor has destroyed all State Confidential Information.

2.103 Exclusions

Notwithstanding the foregoing, the provisions in this Section shall not apply to any particular information which the State or Contractor can demonstrate (i) was, at the time of disclosure to it, in the public domain; (ii) after disclosure to it, is published or otherwise becomes part of the public domain through no fault of the receiving party; (iii) was in the possession of the receiving party at the time of disclosure to it without an obligation of confidentiality; (iv) was received after disclosure to it from a third party who had a lawful right to disclose the information to it without any obligation to restrict its further disclosure; or (v) was independently developed by the receiving party without reference to Confidential Information of the furnishing party. Further, the provisions of this Section shall not apply to any particular Confidential Information to the extent the receiving party is required by law to disclose the Confidential Information, provided that the receiving party (i) promptly provides the furnishing party with notice of the legal request, and (ii) assists the furnishing party in resisting or limiting the scope of the disclosure as reasonably requested by the furnishing party.

2.104 No Implied Rights

Nothing contained in this Section must be construed as obligating a party to disclose any particular Confidential Information to the other party, or as granting to or conferring on a party, expressly or impliedly, any right or license to the Confidential Information of the other party.

2.105 Respective Obligations

The parties’ respective obligations under this Section must survive the termination or expiration of this Contract for any reason.


113

2.106 State Personal Data and Security Breach Notification

“State Personal Data” or “personally identifiable information” means data and/or information which is provided by or on behalf of the Client and which consists of information or data naming or identifying a natural person such as: (a) personally identifying information that is explicitly defined as a regulated category of data under a data privacy or data protection laws applicable to the State or its customers; (b) non-public information, such as a national identification number, passport number, social security number, driver’s license number; (c) health or medical information, such as insurance information, medical prognosis, diagnosis information or genetic information; (d) financial information, such as a policy number, credit card number and/or bank account number; and/or (e) sensitive personal data, such as mother’s maiden name, race, marital status, gender or sexuality. The term “State Personal Data” shall not mean to include information or data that is anonymized, aggregated, de-identified and/or compiled on a generic basis and which does not name or identify a specific individual or person. Contractor shall maintain procedures to detect and respond to an unauthorized acquisition of or a security breach affecting the State’s Personal Data while such data is in its possession or control. Contractor shall promptly notify the Client of an unauthorized acquisition or misuse of the unencrypted State Personal Data in Contractor’s possession when it becomes aware of it. Contractor shall promptly furnish to the State appropriate details of the unauthorized acquisition or misuse and shall use commercially reasonable efforts to assist the State in investigating or preventing the recurrence of an unauthorized acquisition or misuse of the State Personal Data. Each Party shall cooperate, as is commercially reasonable, with the other Party to correct an unauthorized acquisition, misuse or other security breaches, and with the other Party in any litigation and investigation deemed necessary by the other Party. Each Party shall use commercially reasonable efforts to prevent a recurrence of an unauthorized acquisition or misuse of the State Personal Data. The State shall determine whether and when to notify any individuals or persons (including governmental authorities) regarding any security breach affecting Personal Data. Notwithstanding the foregoing, Contractor is permitted to comply with all applicable laws to which it is subject. As defined by data privacy laws, the State shall be the data controller/owner of the data and the Contractor shall be the data processor. The Contractor shall comply with all laws and regulations applicable to the State Personal Data. However, the State shall be solely responsible for determining compliance with data privacy laws. In no event, shall Contractor be required to monitor or advise on the data privacy laws. In the event that there are any changes to (including changes in interpretation of) any of the data privacy laws which require a change to the provision of all or any part of the deliverables or services or a method of delivery of such deliverables or services in use by Contractor, prior to such change the parties shall make appropriate adjustments to the terms of this Contract and the services or deliverables (and corresponding fees) in accordance with the change control process.

2.110 Records and Inspections

2.111 Inspection of Work Performed

The State’s authorized representatives shall at all reasonable times and with 10 days prior written request, have the right to enter Contractor’s premises, or any other places, where the Services are being performed, and shall have access, upon reasonable request, to interim drafts of Deliverables or work-in-progress. Upon 10 Days prior written notice and at all reasonable times, the State’s representatives shall be allowed to inspect, monitor, or otherwise evaluate the work being performed and to the extent that the access will not reasonably interfere or jeopardize the safety or operation of the systems or facilities. Contractor shall provide all reasonable facilities and assistance for the State’s representatives.

2.112 Examination of Records

For seven years after the Contractor provides any work under this Contract (the "Audit Period"), the State may examine and copy any of Contractor’s books, records, documents and papers pertinent to establishing Contractor’s compliance with the Contract and with applicable laws and rules. The State shall notify the Contractor 20 days before examining the Contractor's books and records. The State does not have the right to review any information deemed confidential by the Contractor to the extent access would require the


114

confidential information to become publicly available. This provision also applies to the books, records, accounts, documents and papers, in print or electronic form, of any parent, affiliated or subsidiary organization of Contractor, or any Subcontractor of Contractor performing services in connection with the Contract.

2.113 Retention of Records

Contractor shall maintain at least until the end of the Audit Period all pertinent financial and accounting records (including time sheets and payroll records, and information pertaining to the Contract and to the Services, equipment, and commodities provided under the Contract) pertaining to the Contract according to generally accepted accounting principles and other procedures specified in this Section. Financial and accounting records shall be made available, upon request, to the State at any time during the Audit Period. If an audit, litigation, or other action involving Contractor’s records is initiated before the end of the Audit Period, the records shall be retained until all issues arising out of the audit, litigation, or other action are resolved or until the end of the Audit Period, whichever is later.

2.114 Audit Resolution

If necessary, the Contractor and the State shall meet to review each audit report promptly after issuance. The Contractor shall respond to each audit report in writing within 30 days from receipt of the report, unless a shorter response time is specified in the report. The Contractor and the State shall develop, agree upon and monitor an action plan to promptly address and resolve any deficiencies, concerns, and/or recommendations in the audit report.

2.115 Errors

If the audit demonstrates any errors in the documents provided to the State, then the amount in error shall be reflected as a credit or debit on the next invoice and in subsequent invoices until the amount is paid or refunded in full. However, a credit or debit may not be carried for more than four invoices. If a balance remains after four invoices, then the remaining amount shall be due as a payment or refund within 45 days of the last quarterly invoice that the balance appeared on or termination of the contract, whichever is earlier. In addition to other available remedies, the difference between the payment received and the correct payment amount is greater than 10%, then the Contractor shall pay all of the reasonable costs of the audit.

2.120 Warranties

2.121 Warranties and Representations

The Contractor represents and warrants: (a) It is capable in all respects of fulfilling and must fulfill all of its obligations under this Contract. The

performance of all obligations under this Contract must be provided in a timely, professional, and workman-like manner and must meet the performance and operational standards required under this Contract.

(b) The Contract Appendices, Attachments and Exhibits identify the equipment and software and services necessary for the Deliverable(s) to perform and Services to operate in compliance with the Contract’s requirements and other standards of performance.

(c) It is the lawful owner or licensee of any Deliverable licensed or sold to the State by Contractor or developed by Contractor under this Contract, and Contractor has all of the rights necessary to convey to the State the ownership rights or licensed use, as applicable, of any and all Deliverables. None of the Deliverables provided by Contractor to the State under neither this Contract, nor their use by the State shall infringe the patent, copyright, trade secret, or other proprietary rights of any third party.

(d) If, under this Contract, Contractor procures any equipment, software or other Deliverable for the State (including equipment, software and other Deliverables manufactured, re-marketed or otherwise sold by Contractor under Contractor’s name), then in addition to Contractor’s other responsibilities with respect to the items in this Contract, Contractor must assign or otherwise transfer to the State or its designees, or afford the State the benefits of, any manufacturer's warranty for the Deliverable.

(e) The Contract signatory has the power and authority, including any necessary corporate authorizations, necessary to enter into this Contract, on behalf of Contractor.


115

(f) It is qualified and registered to transact business in all locations where required. (g) Neither the Contractor nor any Affiliates, nor any employee of either, has, must have, or must acquire, any

contractual, financial, business, or other interest, direct or indirect, that would conflict in any manner or degree with Contractor’s performance of its duties and responsibilities to the State under this Contract or otherwise create an appearance of impropriety with respect to the award or performance of this Agreement. Contractor must notify the State about the nature of the conflict or appearance of impropriety within two days of learning about it.

(h) Neither Contractor nor any Affiliates, nor any employee of either has accepted or must accept anything of value based on an understanding that the actions of the Contractor or Affiliates or employee on behalf of the State would be influenced. Contractor must not attempt to influence any State employee by the direct or indirect offer of anything of value.

(i) Neither Contractor nor any Affiliates, nor any employee of either has paid or agreed to pay any person, other than bona fide employees and consultants working solely for Contractor or the Affiliate, any fee, commission, percentage, brokerage fee, gift, or any other consideration, contingent upon or resulting from the award or making of this Contract.

(j) The prices proposed by Contractor were arrived at independently, without consultation, communication, or agreement with any other Bidder for the purpose of restricting competition; the prices quoted were not knowingly disclosed by Contractor to any other Bidder; and no attempt was made by Contractor to induce any other person to submit or not submit a proposal for the purpose of restricting competition.

(k) All financial statements, reports, and other information furnished by Contractor to the State as part of its response to the RFP or otherwise in connection with the award of this Contract fairly and accurately represent the business, properties, financial condition, and results of operations of Contractor as of the respective dates, or for the respective periods, covered by the financial statements, reports, other information. Since the respective dates or periods covered by the financial statements, reports, or other information, there have been no material adverse changes in the business, properties, financial condition, or results of operations of Contractor.

(l) All written information furnished to the State by or for the Contractor in connection with this Contract, including its bid, is true, accurate, and complete, and contains no untrue statement of material fact or omits any material fact necessary to make the information not misleading.

(m) It is not in material default or breach of any other contract or agreement that it may have with the State or any of its departments, commissions, boards, or agencies. Contractor further represents and warrants that it has not been a party to any contract with the State or any of its departments that was terminated by the State or the department within the previous five years for the reason that Contractor failed to perform or otherwise breached an obligation of the contract.

(n) If any of the certifications, representations, or disclosures made in the Contractor’s original bid response change after Contract award, the Contractor is required to report those changes immediately to the Department of Technology, Management and Budget, Purchasing Operations

THE FOREGOING EXPRESS WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES AND EACH PARTY EXPRESSLY DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, BY OPERATION OF LAW OR OTHERWISE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

2.122 Warranty of Merchantability

Reserved

2.123 Warranty of Fitness for a Particular Purpose

Reserved

2.124 Warranty of Title

Reserved

2.125 Equipment Warranty


116

To the extent Contractor is responsible under this Contract for maintaining equipment/system(s), Contractor represents and warrants that it will maintain such equipment/system(s) in good operating condition and will undertake all repairs and preventive maintenance in accordance with the applicable manufacturer's recommendations for the period specified in this Contract. The Contractor represents and warrants that the equipment/system(s) shall be in good operating condition and shall operate and perform to the requirements and other standards of performance contained in this Contract, when installed, at the time of Final Acceptance by the State, and for a period of one (1) year commencing upon the first day following Final Acceptance. Within three (3) business days of notification from the State, the Contractor shall adjust, repair or replace all equipment that is defective or not performing in compliance with the Contract. The Contractor shall assume all costs for replacing parts or units and their installation including transportation and delivery fees, if any.

The Contractor shall provide a toll-free telephone number to allow the State to report equipment failures and problems to be remedied by the Contractor.

The Contractor agrees that all warranty service it provides under this Contract shall be performed by original equipment manufacturer (OEM) trained, certified and authorized technicians. The Contractor shall act as the sole point of contact for warranty service. The Contractor warrants that it shall pass through to the State any and all warranties obtained or available from the original equipment manufacturer, including any replacement, upgraded, or additional equipment warranties. All warranty work shall be performed on the State of Michigan worksite(s).

2.126 Equipment to be New

If applicable, all equipment provided under this Contract by Contractor shall be new where Contractor has knowledge regarding whether the equipment is new or assembled from new or serviceable used parts that are like new in performance or has the option of selecting one or the other. Equipment that is assembled from new or serviceable used parts that are like new in performance is acceptable where Contractor does not have knowledge or the ability to select one or other, unless specifically agreed otherwise in writing by the State.

2.127 Prohibited Products

The State will not accept salvage, distressed, outdated or discontinued merchandise. Shipping of such merchandise to any State agency, as a result of an order placed against the Contract, shall be considered default by the Contractor of the terms and conditions of the Contract and may result in cancellation of the Contract by the State. The brand and product number offered for all items shall remain consistent for the term of the Contract, unless Purchasing Operations has approved a change order pursuant to Section 2.024.

2.128 Consequences for Breach

In addition to any remedies available in law, if the Contractor breaches any of the warranties contained in this section, the breach may be considered as a default in the performance of a material obligation of this Contract.

2.130 Insurance

2.131 Liability Insurance

The Contractor must provide proof of the minimum levels of insurance coverage as indicated below. The insurance must protect the State from claims that may arise out of or result from the Contractor’s performance of services under the terms of this Contract, whether the services are performed by the Contractor, or by any subcontractor, or by anyone directly or indirectly employed by any of them, or by anyone for whose acts they may be liable.


117

The Contractor waives all rights against the State of Michigan, its departments, divisions, agencies, offices, commissions, officers, employees and agents for recovery of damages to the extent these damages are covered by the insurance policies the Contractor is required to maintain under this Contract.

All insurance coverage provided relative to this Contract/Purchase Order is PRIMARY and NON-CONTRIBUTING to any comparable liability insurance (including self-insurances) carried by the State.

The insurance must be written for not less than any minimum coverage specified in this Contract or required by law, whichever is greater.

The insurers selected by Contractor must have an A.M. Best rating of A or better, or as otherwise approved in writing by the State, or if the ratings are no longer available, with a comparable rating from a recognized insurance rating agency. All policies of insurance required in this Contract must be issued by companies that have been approved to do business in the State. See www.michigan.gov/dleg.

Where specific limits are shown, they are the minimum acceptable limits. If Contractor’s policy contains higher limits, the State must be entitled to coverage to the extent of the higher limits.

The Contractor is required to pay for and provide the type and amount of insurance checked below:

1. Commercial General Liability with the following minimum coverage: $2,000,000 General Aggregate Limit other than Products/Completed Operations $2,000,000 Products/Completed Operations Aggregate Limit $1,000,000 Personal & Advertising Injury Limit $1,000,000 Each Occurrence Limit

The Contractor must list the State of Michigan, its departments, divisions, agencies, offices, commissions, officers, employees and agents as ADDITIONAL INSUREDS on the Commercial General Liability certificate. The Contractor also agrees to provide evidence that insurance policies contain a waiver of subrogation by the insurance company.

2. If a motor vehicle is used to provide services or products under this Contract, the Contractor must have vehicle liability insurance on any auto including owned, hired and non-owned vehicles used in Contractor‘s business for bodily injury and property damage as required by law.

The Contractor must list the State of Michigan, its departments, divisions, agencies, offices, commissions, officers, employees and agents as ADDITIONAL INSUREDS on the vehicle liability certificate. The Contractor also agrees to provide evidence that insurance policies contain a waiver of subrogation by the insurance company.

3. Workers’ compensation coverage must be provided according to applicable laws governing the employees and employers work activities in the state of the Contractor’s domicile. If a self-insurer provides the applicable coverage, proof must be provided of approved self-insured authority by the jurisdiction of domicile. For employees working outside of the state of qualification, Contractor must provide appropriate certificates of insurance proving mandated coverage levels for the jurisdictions where the employees’ activities occur.

Any certificates of insurance received must also provide a list of states where the coverage is applicable.

The Contractor also agrees to provide evidence that insurance policies contain a waiver of subrogation by the insurance company. This provision must not be applicable where prohibited or limited by the laws of the jurisdiction in which the work is to be performed.

4. Employers liability insurance with the following minimum limits: $100,000 each accident $100,000 each employee by disease $500,000 aggregate disease


118

5. Employee Fidelity, including Computer Crimes, insurance naming the State as a loss payee, providing coverage for direct loss to the State and any legal liability of the State arising out of or related to fraudulent or dishonest acts committed by the employees of Contractor or its Subcontractors, acting alone or in collusion with others, in a minimum amount of one million dollars ($1,000,000.00) with a maximum deductible of fifty thousand dollars ($50,000.00).

2.132 Subcontractor Insurance Coverage

Except where the State has approved in writing a Contractor subcontract with other insurance provisions, Contractor must require all of its Subcontractors under this Contract to purchase and maintain the insurance coverage as described in this Section for the Contractor in connection with the performance of work by those Subcontractors. Alternatively, Contractor may include any Subcontractors under Contractor’s insurance on the coverage required in this Section. Subcontractor(s) must fully comply with the insurance coverage required in this Section. Failure of Subcontractor(s) to comply with insurance requirements does not limit Contractor’s liability or responsibility.

2.133 Certificates of Insurance and Other Requirements

Before the Contract is signed by both parties or before the purchase order is issued by the State, the Contractor must furnish to the Director of Purchasing Operations, certificate(s) of insurance verifying insurance coverage (“Certificates”). The Certificate must be on the standard “accord” form or equivalent. THE CONTRACT OR PURCHASE ORDER NO. MUST BE SHOWN ON THE CERTIFICATE OF INSURANCE TO ASSURE CORRECT FILING. All Certificate(s) are to be prepared and submitted by the Insurance Provider. All Certificate(s) shall contain a provision indicating that coverages afforded under the policies WILL NOT BE CANCELLED, MATERIALLY CHANGED, OR NOT RENEWED without THIRTY (30) days prior written notice, except for ten (10) days for non-payment of premium, having been given to the Director of Purchasing Operations, Department of Management and Budget. The notice must include the Contract or Purchase Order number affected and be mailed to: Director, Purchasing Operations, Department of Management and Budget, P.O. Box 30026, Lansing, Michigan 48909. Failure to provide evidence of coverage, may, at the State’s sole option, result in this Contract’s termination.

2.140 Indemnification

2.141 General Indemnification

To the extent permitted by law, the Contractor must indemnify, defend and hold harmless the State from liability, including all claims and losses, and all related costs and expenses (including reasonable attorneys’ fees and costs of investigation, litigation, settlement, judgments, interest and penalties), accruing or resulting to any person, firm or corporation that may be injured or damaged by the Contractor in the performance of this Contract and that are attributable to the negligence or tortious acts of the Contractor or any of its subcontractors, or by anyone else for whose acts any of them may be liable.

2.142 Code Indemnification

To the extent permitted by law, the Contractor shall indemnify, defend and hold harmless the State from any claim, loss, or expense arising from Contractor’s breach of the No Surreptitious Code Warranty.

2.143 Employee Indemnification

In any claims against the State of Michigan, its departments, divisions, agencies, sections, commissions, officers, employees and agents, by any employee of the Contractor or any of its subcontractors, the indemnification obligation under the Contract must not be limited in any way by the amount or type of damages, compensation or benefits payable by or for the Contractor or any of its subcontractors under worker’s disability compensation acts, disability benefit acts or other employee benefit acts. This indemnification clause is intended to be comprehensive. Any overlap in provisions, or the fact that greater specificity is provided as to some categories of risk, is not intended to limit the scope of indemnification under any other provisions.


119

2.144 Patent/Copyright Infringement Indemnification

To the extent permitted by law, the Contractor must indemnify, defend and hold harmless the State from and against all losses, liabilities, damages (including taxes), and all related costs and expenses (including reasonable attorneys’ fees and costs of investigation, litigation, settlement, judgments, interest and penalties) incurred in connection with any action or proceeding threatened or brought against the State to the extent that the action or proceeding is based on a claim that any Service (excluding the provision of third-party products) supplied by the Contractor or its subcontractors infringes any United States patent, copyright, trademark or trade secret of any person or entity, which is enforceable under the laws of the United States. In addition, should the Service become or in the State’s or Contractor’s opinion be likely to become the subject of a claim of infringement, the Contractor must at the Contractor’s sole expense (i) procure for the State the right to continue using the Service or, if the option is not reasonably available to the Contractor, (ii) replace or modify to the State’s satisfaction the same with Service of equivalent function and performance so that it becomes non-infringing, or, if the option is not reasonably available to Contractor, (iii) accept its return by the State with appropriate credits to the State against the Contractor’s charges and reimburse the State for any losses or costs incurred as a consequence of the State ceasing its use and returning it. Notwithstanding the foregoing, the Contractor has no obligation to indemnify or defend the State for, or to pay any costs, damages or attorneys’ fees related to, any claim based upon (i) Services developed based on written specifications of the State; (ii) use of the Services in a configuration other than implemented or approved in writing by the Contractor, including, but not limited to, any modification of the equipment by the State; or (iii) the combination, operation, or use of the Services with Services not supplied by the Contractor under this Contract.

2.145 Continuation of Indemnification Obligations

The Contractor’s duty to indemnify under this Section continues in full force and effect, notwithstanding the expiration or early cancellation of the Contract, with respect to any claims based on facts or conditions that occurred before expiration or cancellation.

2.146 Indemnification Procedures

The procedures set forth below must apply to all indemnity obligations under this Contract. (a) After the State receives notice of the action or proceeding involving a claim for which it shall seek

indemnification, the State must promptly notify Contractor of the claim in writing and take or assist Contractor in taking, as the case may be, any reasonable action to avoid the imposition of a default judgment against Contractor. No failure to notify the Contractor relieves the Contractor of its indemnification obligations except to the extent that the Contractor can prove damages attributable to the failure. Within 10 days following receipt of written notice from the State relating to any claim, the Contractor must notify the State in writing whether Contractor agrees to assume control of the defense and settlement of that claim (a “Notice of Election”). After notifying Contractor of a claim and before the State receiving Contractor’s Notice of Election, the State is entitled to defend against the claim, at the Contractor’s expense, and the Contractor will be responsible for any reasonable costs incurred by the State in defending against the claim during that period.

(b) If Contractor delivers a Notice of Election relating to any claim: (i) the State is entitled to participate in the defense of the claim and to employ counsel at its own expense to assist in the handling of the claim and to monitor and advise the State about the status and progress of the defense; (ii) the Contractor must, at the request of the State, demonstrate to the reasonable satisfaction of the State, the Contractor’s financial ability to carry out its defense and indemnity obligations under this Contract; (iii) the Contractor must periodically advise the State about the status and progress of the defense and must obtain the prior written approval of the State before entering into any settlement of the claim or ceasing to defend against the claim and (iv) to the extent that any principles of Michigan governmental or public law may be involved or challenged, the State has the right, at its own expense, to control the defense of that portion of the claim involving the principles of Michigan governmental or public law. But the State may retain control of the defense and settlement of a claim by notifying the Contractor in writing within 10 days after the State’s receipt of Contractor’s information requested by the State under clause (ii) of this paragraph if


120

the State determines that the Contractor has failed to demonstrate to the reasonable satisfaction of the State the Contractor’s financial ability to carry out its defense and indemnity obligations under this Section. Any litigation activity on behalf of the State, or any of its subdivisions under this Section, must be coordinated with the Department of Attorney General. In the event the insurer’s attorney represents the State under this Section, the insurer’s attorney may be required to be designated as a Special Assistant Attorney General by the Attorney General of the State of Michigan.

(c) If Contractor does not deliver a Notice of Election relating to any claim of which it is notified by the State as provided above, the State may defend the claim in the manner as it may deem appropriate, at the cost and expense of Contractor. If it is determined that the claim was one against which Contractor was required to indemnify the State, upon request of the State, Contractor must promptly reimburse the State for all the reasonable costs and expenses.

2.150 Termination/Cancellation

2.151 Notice and Right to Cure

If the Contractor breaches the contract, and the State in its sole discretion determines that the breach is curable, then the State shall provide the Contractor with written notice of the breach and a time period (not less than 30 days) to cure the Breach. The notice of breach and opportunity to cure is inapplicable for successive or repeated breaches or if the State determines in its sole discretion that the breach poses a serious and imminent threat to the health or safety of any person or the imminent loss, damage, or destruction of any real or tangible personal property.

2.152 Termination for Cause

(a) In the event that Contractor breaches any of its material duties or obligations under this Contract, which are either not capable of or subject to being cured, or are not cured within the time period specified in the written notice of breach provided by the State (such time period not to be less than thirty (30) days), or pose a serious and imminent threat to the health and safety of any person, or the imminent loss, damage or destruction of any real or tangible personal property, the State may, having provided written notice of termination to Contractor, terminate this Contract in whole or in part, for cause, as of the date specified in the notice of termination.

(b) In the event that this Contract is terminated for cause, in addition to any legal remedies otherwise available to the State by law or equity, Contractor shall be responsible for all costs incurred by the State in terminating this Contract, including but not limited to, State administrative costs, reasonable attorneys’ fees and court costs, and any reasonable additional costs the State may incur to procure the Services/Deliverables required by this Contract from other sources. Re-procurement costs shall not be considered by the parties to be consequential, indirect or incidental damages, and shall not be excluded by any other terms otherwise included in this Contract.

(c) In the event the State chooses to partially terminate this Contract for cause, charges payable under this Contract will be equitably adjusted to reflect those Services/Deliverables that are terminated and the State shall pay for all Services/Deliverables provided up to the termination date. Services and related provisions of this Contract that are terminated for cause shall cease on the effective date of the termination.

(d) In the event this Contract is terminated for cause pursuant to this Section, and it is determined, for any reason, that Contractor was not in breach of contract pursuant to the provisions of this section, that termination for cause shall be deemed to have been a termination for convenience, effective as of the same date, and the rights and obligations of the parties shall be limited to that otherwise provided in this Contract for a termination for convenience.

2.153 Termination for Convenience

The State may terminate this Contract for its convenience, in whole or part, if the State determines that a termination is in the State’s best interest. Reasons for the termination must be left to the sole discretion of the State and may include, but not necessarily be limited to (a) the State no longer needs the Services or products specified in the Contract, (b) relocation of office, program changes, changes in laws, rules, or regulations make implementation of the Services no longer practical or feasible, (c) unacceptable prices for Additional Services or New Work requested by the State, or (d) falsification or misrepresentation, by inclusion or non-inclusion, of


121

information material to a response to any RFP issued by the State. The State may terminate this Contract for its convenience, in whole or in part, by giving Contractor written notice at least 30 days before the date of termination. If the State chooses to terminate this Contract in part, the charges payable under this Contract must be equitably adjusted to reflect those Services/Deliverables that are terminated. Services and related provisions of this Contract that are terminated for convenience must cease on the effective date of the termination.

2.154 Termination for Non-Appropriation

(a) Contractor acknowledges that, if this Contract extends for several fiscal years, continuation of this Contract is subject to appropriation or availability of funds for this Contract. If funds to enable the State to effect continued payment under this Contract are not appropriated or otherwise made available, the State must terminate this Contract and all affected Statements of Work, in whole or in part, at the end of the last period for which funds have been appropriated or otherwise made available by giving written notice of termination to Contractor. The State must give Contractor at least 30 days advance written notice of termination for non-appropriation or unavailability (or the time as is available if the State receives notice of the final decision less than 30 days before the funding cutoff).

(b) If funding for the Contract is reduced by law, or funds to pay Contractor for the agreed-to level of the Services or production of Deliverables to be provided by Contractor are not appropriated or otherwise unavailable, the State may, upon 30 days written notice to Contractor, reduce the level of the Services or change the production of Deliverables in the manner and for the periods of time as the State may elect. The charges payable under this Contract shall be equitably adjusted to reflect any equipment, services or commodities not provided by reason of the reduction.

(c) If the State terminates this Contract, eliminates certain Deliverables, or reduces the level of Services to be provided by Contractor under this Section, the State must pay Contractor for all Work-in-Process performed through the effective date of the termination or reduction in level, as the case may be and as determined by the State, to the extent funds are available. This Section shall not preclude Contractor from reducing or stopping Services/Deliverables or raising against the State in a court of competent jurisdiction, any claim for a shortfall in payment for Services performed or Deliverables finally accepted before the effective date of termination.

2.155 Termination for Criminal Conviction

The State may terminate this Contract immediately and without further liability or penalty in the event Contractor, an officer of Contractor, or an owner of a 25% or greater share of Contractor is convicted of a criminal offense related to a State, public or private Contract or subcontract.

2.156 Termination for Approvals Rescinded

The State may terminate this Contract if any final administrative or judicial decision or adjudication disapproves a previously approved request for purchase of personal services under Constitution 1963, Article 11, § 5, and Civil Service Rule 7-1. In that case, the State shall pay the Contractor for only the work completed to that point under the Contract. Termination may be in whole or in part and may be immediate as of the date of the written notice to Contractor or may be effective as of the date stated in the written notice.

2.157 Rights and Obligations upon Termination

(a) If this Contract is terminated by the State for any reason, Contractor shall (a) stop all work as specified in the notice of termination, (b) take any action that may be necessary, or that the State may direct, for preservation and protection of Deliverables or other property derived or resulting from this Contract that may be in Contractor’s possession, (c) return all materials and property provided directly or indirectly to Contractor by any entity, agent or employee of the State, (d) in the event that the Contractor maintains title in Deliverables that is intended to be transferred to the State at the termination of the Contract, Contractor will transfer title in, and deliver to, the State, unless otherwise directed, all Deliverables intended to be transferred to the State at the termination of the Contract and which are resulting from the Contract (which shall be provided to the State on an “As-Is” basis except to the extent the amounts paid by the State in respect of such items included compensation to Contractor for the provision of warranty services in respect of such materials), and (e) take any action to mitigate and limit any potential damages, or requests for Contractor adjustment or


122

termination settlement costs, to the maximum practical extent, including terminating or limiting as otherwise applicable those subcontracts and outstanding orders for material and supplies resulting from the terminated Contract.

(b) In the event the State terminates this Contract prior to its expiration for its own convenience, the State shall pay Contractor for all charges due for Services provided prior to the date of termination and, if applicable, as a separate item of payment pursuant to this Contract, for Work In Process, on a percentage of completion basis to be mutually agreed upon. All completed or partially completed Deliverables prepared by Contractor pursuant to this Contract shall, at the option of the State, become the State’s property, and Contractor shall be entitled to receive equitable fair compensation for such Deliverables. Regardless of the basis for the termination, the State shall not be obligated to pay, or otherwise compensate, Contractor for any lost expected future profits, costs or expenses incurred with respect to Services not actually performed for the State.

(c) Upon a good faith termination, the State shall have the right to assume, at its option, any and all subcontracts and agreements for services and deliverables provided under this Contract, and may further pursue completion of the Services/Deliverables under this Contract by replacement contract or otherwise as the State may in its sole judgment deem expedient.

2.158 Reservation of Rights

Any termination of this Contract or any Statement of Work issued under it by a party must be with full reservation of, and without prejudice to, any rights or remedies otherwise available to the party with respect to any claims arising before or as a result of the termination.

2.160 Termination by Contractor

2.161 Termination by Contractor

If the State breaches the Contract, and the Contractor in its sole discretion determines that the breach is curable, then the Contractor will provide the State with written notice of the breach and a time period (not less than 30 days) to cure the breach. The Notice of Breach and opportunity to cure is inapplicable for successive and repeated breaches. The Contractor may terminate this Contract if the State (i) materially breaches its obligation to pay the Contractor undisputed amounts due and owing under this Contract, (ii) breaches its other obligations under this Contract to an extent that makes it impossible or commercially impractical for the Contractor to perform the Services, or (iii) does not cure the breach within the time period specified in a written notice of breach. But the Contractor must discharge its obligations under Section 2.160 before it terminates the Contract.

2.170 Transition Responsibilities

2.171

Reserved

2.172 Contractor Personnel Transition

In the event this Contract is terminated, for convenience or cause, dissolved, voided, rescinded, nullified, expires or is otherwise rendered unenforceable, the Contractor agrees to comply with direction provided by the State to assist in the orderly transition of equipment, services, software, leases, etc. to the State or a third party designated by the State. In the event of termination or the expiration of this Contract, the Contractor agrees to make all reasonable efforts to effect an orderly transition of services within a reasonable period of time that in no event will exceed ninety (90) days. These efforts shall include, but are not limited to, the following:

(a) Personnel - The Contractor shall work with the State, or a specified third party, to develop a transition plan setting forth the specific tasks and schedule to be accomplished by the parties, to effect an orderly transition. The Contractor shall allow as many personnel as practicable to remain on the job to help the State, or a specified third party, maintain the continuity and consistency of the services required by this Contract. In addition, during or following the transition period, in the event the State requires the Services of the Contractor’s subcontractors or vendors, as necessary to meet its needs, Contractor agrees to reasonably,


123

and with good-faith, work with the State to use the Services of Contractor’s subcontractors or vendors. Contractor will notify all of Contractor’s subcontractors of procedures to be followed during transition.

(b) Information - The Contractor agrees to provide reasonable detailed specifications for all Services/Deliverables needed by the State, or specified third party, to properly provide the Services/Deliverables required under this Contract. The Contractor will provide the State with asset management data generated from the inception of this Contract through the date on which this Contractor is terminated in a comma-delineated format unless otherwise requested by the State. The Contractor will deliver to the State any remaining owed reports and documentation still in Contractor’s possession subject to appropriate payment by the State.

(d) Software. - The Contractor shall reasonably assist the State in the acquisition of any Contractor software required to perform the Services/use the Deliverables under this Contract. This shall include any documentation being used by the Contractor to perform the Services under this Contract. If the State transfers any software licenses to the Contractor, those licenses shall, upon expiration of the Contract, transfer back to the State at their current revision level. Upon notification by the State, Contractor may be required to freeze all non-critical changes to Deliverables/Services.

(e) Payment - If the transition results from a termination for any reason, reimbursement shall be governed by the termination provisions of this Contract. If the transition results from expiration, the Contractor will be reimbursed for all reasonable transition costs (i.e. costs incurred within the agreed period after Contract expiration that result from transition operations) at the rates specified by Attachment 3 – Cost Tables Table 4 – Rate Card. The Contractor will prepare an accurate accounting from which the State and Contractor may reconcile all outstanding accounts.

2.173

Reserved

2.174

Reserved

2.175

Reserved

2.176 State Transition Responsibilities

In the event that this Contract is terminated, dissolved, voided, rescinded, nullified, or otherwise rendered unenforceable, the State agrees to reconcile all accounts between the State and the Contractor, complete any pending post-project reviews and perform any others obligations upon which the State and the Contractor agree. (a) Reconciling all accounts between the State and the Contractor; (b) Completing any pending post-project reviews.

2.180 Stop Work

2.181 Stop Work Orders

The State may, at any time, by written Stop Work Order to Contractor, require that Contractor stop all, or any part, of the work called for by the Contract for a period of up to 90 calendar days after the Stop Work Order is delivered to Contractor, and for any further period to which the parties may agree. The Stop Work Order must be identified as a Stop Work Order and must indicate that it is issued under this Section. Upon receipt of the stop work order, Contractor must immediately comply with its terms and take all reasonable steps to minimize incurring costs allocable to the work covered by the Stop Work Order during the period of work stoppage. Within the period of the stop work order, the State must either: (a) cancel the stop work order; or (b) terminate the work covered by the Stop Work Order as provided in Section 2.182.

2.182 Cancellation or Expiration of Stop Work Order


124

The Contractor shall resume work if the State cancels a Stop Work Order or if it expires. The parties shall agree upon an equitable adjustment in the delivery schedule, the Contract price, or both, and the Contract shall be modified, in writing, accordingly, if: (a) the Stop Work Order results in an increase in the time required for, or in Contractor’s costs properly allocable to, the performance of any part of the Contract; and (b) Contractor asserts its right to an equitable adjustment within 30 calendar days after the end of the period of work stoppage; provided that, if the State decides the facts justify the action, the State may receive and act upon a Contractor proposal submitted at any time before final payment under the Contract. Any adjustment will conform to the requirements of Section 2.024.

2.183 Allowance of Contractor Costs

If the Stop Work Order is not canceled and the work covered by the Stop Work Order is terminated for reasons other than material breach, the termination shall be deemed to be a termination for convenience under Section 2.153, and the State shall pay reasonable costs resulting from the Stop Work Order in arriving at the termination settlement. For the avoidance of doubt, the State shall not be liable to Contractor for loss of profits because of a Stop Work Order issued under this Section.

2.190 Dispute Resolution

2.191 In General

Any claim, counterclaim, or dispute between the State and Contractor arising out of or relating to the Contract or any Statement of Work must be resolved as follows. For all Contractor claims seeking an increase in the amounts payable to Contractor under the Contract, or the time for Contractor’s performance, Contractor must submit a letter, together with all data supporting the claims, executed by Contractor’s Contract Administrator or the Contract Administrator's designee certifying that (a) the claim is made in good faith, (b) the amount claimed accurately reflects the adjustments in the amounts payable to Contractor or the time for Contractor’s performance for which Contractor believes the State is liable and covers all costs of every type to which Contractor is entitled from the occurrence of the claimed event, and (c) the claim and the supporting data are current and complete to Contractor’s best knowledge and belief.

2.192 Informal Dispute Resolution

(a) All disputes between the parties shall be resolved under the Contract Management procedures in this Contract. If the parties are unable to resolve any dispute after compliance with the processes, the parties must meet with the Director of Purchasing Operations, DTMB, or designee, to resolve the dispute without the need for formal legal proceedings, as follows: (1) The representatives of Contractor and the State must meet as often as the parties reasonably deem necessary to gather and furnish to each other all information with respect to the matter at issue which the parties believe to be appropriate and germane in connection with its resolution. The representatives shall discuss the problem and negotiate in good faith in an effort to resolve the dispute without the necessity of any formal proceeding. (2) During the course of negotiations, all reasonable requests made by one party to another for non-privileged information reasonably related to the Contract shall be honored in order that each of the parties may be fully advised of the other’s position. (3) The specific format for the discussions shall be left to the discretion of the designated State and Contractor representatives, but may include the preparation of agreed upon statements of fact or written statements of position. (4) Following the completion of this process within 60 calendar days, the Director of Purchasing Operations, DTMB, or designee, shall issue a written opinion regarding the issue(s) in dispute within 30 calendar days. The opinion regarding the dispute must be considered the State’s final action and the exhaustion of administrative remedies. (b) This Section shall not be construed to prevent either party from instituting, and a party is authorized to institute, formal proceedings earlier to avoid the expiration of any applicable limitations period, to preserve a superior position with respect to other creditors, or under Section 2.193. (c) The State shall not mediate disputes between the Contractor and any other entity, except state agencies, concerning responsibility for performance of work under the Contract.


125

2.193 Injunctive Relief

The only circumstance in which disputes between the State and Contractor shall not be subject to the provisions of Section 2.192 is where a party makes a good faith determination that a breach of the terms of the Contract by the other party is that the damages to the party resulting from the breach shall be so immediate, so large or severe and so incapable of adequate redress after the fact that a temporary restraining order or other immediate injunctive relief is the only adequate remedy.

2.194 Continued Performance

Each party agrees to continue performing its obligations under the Contract while a dispute is being resolved except to the extent the issue in dispute precludes performance (dispute over payment must not be deemed to preclude performance) and without limiting either party’s right to terminate the Contract as provided in Section 2.150, as the case may be.

2.200 Federal and State Contract Requirements

2.201 Nondiscrimination

In the performance of the Contract, Contractor agrees not to discriminate against any employee or applicant for employment, with respect to his or her hire, tenure, terms, conditions or privileges of employment, or any matter directly or indirectly related to employment, because of race, color, religion, national origin, ancestry, age, sex, height, weight, and marital status, physical or mental disability. Contractor further agrees that every subcontract entered into for the performance of this Contract or any purchase order resulting from this Contract will contain a provision requiring non-discrimination in employment, as specified here, binding upon each Subcontractor. This covenant is required under the Elliot Larsen Civil Rights Act, 1976 PA 453, MCL 37.2101, et seq., and the Persons with Disabilities Civil Rights Act, 1976 PA 220, MCL 37.1101, et seq., and any breach of this provision may be regarded as a material breach of the Contract.

2.202 Unfair Labor Practices

Under 1980 PA 278, MCL 423.321, et seq., the State shall not award a Contract or subcontract to an employer whose name appears in the current register of employers failing to correct an unfair labor practice compiled under Section 2 of the Act. This information is compiled by the United States National Labor Relations Board. A Contractor of the State, in relation to the Contract, shall not enter into a contract with a Subcontractor, manufacturer, or supplier whose name appears in this register. Under Section 4 of 1980 PA 278, MCL 423.324, the State may void any Contract if, after award of the Contract, the name of Contractor as an employer or the name of the Subcontractor, manufacturer or supplier of Contractor appears in the register.

2.203 Workplace Safety and Discriminatory Harassment

In performing Services for the State, the Contractor shall comply with the Department of Civil Services Rule 2-20 regarding Workplace Safety and Rule 1-8.3 regarding Discriminatory Harassment. In addition, the Contractor shall comply with Civil Service regulations and any applicable agency rules provided to the Contractor. For Civil Service Rules, see http://www.mi.gov/mdcs/0,1607,7-147-6877---,00.html.

2.204 Prevailing Wage

Wages rates and fringe benefits to be paid each class of individuals employed by the Contractor, its subcontractors, their subcontractors, and all persons involved with the performance of this Contract in privity of contract with the Contractor shall not be less than the wage rates and fringe benefits established by the Michigan Department of Licensing and Regulatory Affairs, Wage and Hour Division, schedule of occupational classification and wage rates and fringe benefits for the local where the work is to be performed. The term Contractor shall include all general contractors, prime contractors, project managers, trade contractors, and all of their contractors or subcontractors and persons in privity of contract with them. The Contractor, its subcontractors, their subcontractors and all persons involved with the performance of this Contract in privity of contract with the Contractor shall keep posted on the work site, in a conspicuous place, a copy of all wage rates and fringe benefits as prescribed in the Contract. Contractor shall also post, in a


126

conspicuous place, the address and telephone number of the Michigan Department of Labor and Economic Development, the agency responsible for enforcement of the wage rates and fringe benefits. Contractor shall keep an accurate record showing the name and occupation of the actual wage and benefits paid to each individual employed in connection with this contract. This record shall be available to the State upon request for reasonable inspection.

If any trade is omitted from the list of wage rates and fringe benefits to be paid to each class of individuals by the Contractor, it is understood that the trades omitted shall also be paid not less than the wage rate and fringe benefits prevailing in the local where the work is to be performed.

2.210 Governing Law

2.211 Governing Law The Contract shall in all respects be governed by, and construed according to, the substantive laws of the State of Michigan without regard to any Michigan choice of law rules that would apply the substantive law of any other jurisdiction to the extent not inconsistent with, or pre-empted by federal law.

2.212 Compliance with Laws Contractor shall comply with all applicable state, federal, and local laws and ordinances (“Applicable Laws”) in providing the Services/Deliverables.

2.213 Jurisdiction Any dispute arising from the Contract shall be resolved in the State of Michigan. With respect to any claim between the parties, Contractor consents to venue in Ingham County, Michigan, and irrevocably waives any objections it may have to the jurisdiction on the grounds of lack of personal jurisdiction of the court or the laying of venue of the court or on the basis of forum non conveniens or otherwise. Contractor agrees to appoint agents in the State of Michigan to receive service of process.

2.220 Limitation of Liability

2.221 Limitation of Liability The Contractor’s liability for damages to the State shall be limited to one times the value of the Contract or $200,000 whichever is higher. The foregoing limitation of liability shall not apply to claims for infringement of United States patent, copyright, trademarks or trade secrets; to claims for personal injury or damage to property caused by the gross negligence or willful misconduct of the Contractor; to claims covered by other specific provisions of this Contract calling for liquidated damages; or to court costs or attorney’s fees awarded by a court in addition to damages after litigation based on this Contract.

The State’s liability for damages to the Contractor shall be limited to the value of the Contract.

Neither the Contractor nor the State shall be liable to each other, regardless of the form of action, for consequential, incidental, indirect, or special damages. This limitation of liability shall not apply to claims for infringement of United States patent, copyright, trademark or trade secrets; to claims for personal injury or damage to property caused by the gross negligence or willful misconduct of the Contractor; to claims covered by other specific provisions of this Contract calling for liquidated damages; or to court costs or attorney’s fees awarded by a court in addition to damages after litigation based on this Contract.

2.230 Disclosure Responsibilities

2.231 Disclosure of Litigation Contractor must disclose to the State on an annual basis, within ten (10) days after the public availability of Contractor’s Form 10-K (Annual Report) on file with the U.S. Securities and Exchange Commission, any material legal proceedings arising out of Contractor’s business dealings with governmental or public entities (“Proceedings”), as such Proceedings are set forth in such Form 10-K.

If any Proceeding disclosed to the State under this Section, or of which the State otherwise becomes aware, during the term of this Contract would cause a reasonable party to be concerned about:


127

(a) the ability of Contractor (or a Subcontractor) to continue to perform this Contract according to its terms and conditions, or

(b) whether Contractor (or a Subcontractor) in performing Services for the State is engaged in conduct which is similar in nature to conduct alleged in the Proceeding, which conduct would constitute a breach of this Contract or a violation of Michigan law, regulations or public policy. Then, the Contractor must provide the State all reasonable assurances requested by the State to demonstrate that: (1) Contractor and its Subcontractors will be able to continue to perform this Contract and any Statements

of Work according to its terms and conditions, and (2) Contractor and its Subcontractors have not and will not engage in conduct in performing the Services

which is similar in nature to the conduct alleged in the Proceeding. (c) Contractor will notify State regarding the change in ownership to Accenture LLP and/or its Affiliates that are directly engaged on the project.

2.232 Contact center Disclosure

Contractor and/or all subcontractors involved in the performance of this Contract providing call or contact center services to the State shall disclose the location of its call or contact center services to inbound callers. Failure to disclose this information is a material breach of this Contract.

2.233 Bankruptcy

The State may, without prejudice to any other right or remedy, terminate this Contract, in whole or in part, and, at its option, may take possession of the “Work in Process” and finish the Works in Process by whatever appropriate method the State may deem expedient if: (a) the Contractor files for protection under the bankruptcy laws; (b) an involuntary petition is filed against the Contractor and not removed within 30 days; (c the Contractor becomes insolvent or if a receiver is appointed due to the Contractor's insolvency; (d) the Contractor makes a general assignment for the benefit of creditors; or (e) the Contractor or its affiliates are unable to provide reasonable assurances that the Contractor or its

affiliates can deliver the services under this Contract. Contractor will fix appropriate notices or labels on the Work in Process to indicate ownership by the State. To the extent reasonably possible, materials and Work in Process shall be stored separately from other stock and marked conspicuously with labels indicating ownership by the State.

2.240 Performance

2.241 Time of Performance

(a) Contractor shall use commercially reasonable efforts to provide the resources necessary to complete all Services and Deliverables according to the time schedules contained in the Statements of Work and other Exhibits governing the work, and with professional quality.

(b) Without limiting the generality of Section 2.241, Contractor shall notify the State in a timely manner upon becoming aware of any circumstances that may reasonably be expected to jeopardize the timely and successful completion of any Deliverables/Services on the scheduled due dates in the latest State-approved delivery schedule and must inform the State of the projected actual delivery date.

(c) If the Contractor believes that a delay in performance by the State has caused or will cause the Contractor to be unable to perform its obligations according to specified Contract time periods, the Contractor must notify the State in a timely manner and must use commercially reasonable efforts to perform its obligations according to the Contract time periods notwithstanding the State’s failure. Contractor will not be in default for a delay in performance to the extent the delay is caused by the State.

2.242 Service Level Agreement (SLA)

(a) SLAs will be completed with the following operational considerations: (1) SLAs will not be calculated for individual Incidents where any event of Excusable Failure has been

determined; Incident means any interruption in Services.


128

(2) SLAs will not be calculated for individual Incidents where loss of service is planned and where the State has received prior notification or coordination.

(3) SLAs will not apply if the applicable Incident could have been prevented through planning proposed by Contractor and not implemented at the request of the State. To invoke this consideration, complete documentation relevant to the denied planning proposal must be presented to substantiate the proposal.

(4) Time period measurements will be based on the time Incidents are received by the Contractor and the time that the State receives notification of resolution based on 24x7x365 time period, except that the time period measurement will be suspended based on the following: (i) Time period(s) will not apply where Contractor does not have access to a physical State Location

and where access to the State Location is necessary for problem identification and resolution. (ii) Time period(s) will not apply where Contractor needs to obtain timely and accurate information or

appropriate feedback and is unable to obtain timely and accurate information or appropriate feedback from the State.

(b) Chronic Failure for any Service(s) will be defined as three unscheduled outage(s) or interruption(s) on any individual Service for the same reason or cause or if the same reason or cause was reasonably discoverable in the first instance over a rolling 30 day period. Chronic Failure will result in the State’s option to terminate the effected individual Service(s) and procure them from a different vendor for the chronic location(s) with Contractor to pay the difference in charges for up to three additional months. The termination of the Service will not affect any tiered pricing levels.

(c) Root Cause Analysis will be performed on any Business Critical outage(s) or outage(s) on Services when requested by the Contract Administrator. Contractor will provide its analysis within two weeks of outage(s) and provide a recommendation for resolution.

(d) All decimals must be rounded to two decimal places with five and greater rounding up and four and less rounding down unless otherwise specified.

2.243 Liquidated Damages

Unauthorized Removal of any Key Personnel It is acknowledged that an Unauthorized Removal will interfere with the timely and proper completion of the Contract, to the loss and damage of the State, and that it would be impracticable and extremely difficult to fix the actual damage sustained by the State as a result of any Unauthorized Removal. Therefore, Contractor and the State agree that in the case of any Unauthorized Removal in respect of which the State does not elect to exercise its rights under Section 2.152, the State may assess liquidated damages against Contractor as specified below.

For the Unauthorized Removal of any Key Personnel designated in the applicable Statement of Work, the liquidated damages amount is $25,000.00 per individual if the Contractor identifies a replacement approved by the State under Section 2.060 and assigns the replacement to the Project to shadow the Key Personnel who is leaving for a period of at least 30 days before the Key Personnel’s removal.

If Contractor fails to assign a replacement to shadow the removed Key Personnel for at least 30 days, in addition to the $25,000.00 liquidated damages for an Unauthorized Removal, Contractor must pay the amount of $833.33 per day for each day of the 30 day shadow period that the replacement Key Personnel does not shadow the removed Key Personnel, up to $25,000.00 maximum per individual. The total liquidated damages that may be assessed per Unauthorized Removal and failure to provide 30 days of shadowing must not exceed $50,000.00 per individual.

2.244 Excusable Failure

Neither party will be liable for any default, damage or delay in the performance of its obligations under the Contract to the extent the default, damage or delay is caused by government regulations or requirements (executive, legislative, judicial, military or otherwise), power failure, electrical surges or current fluctuations, lightning, earthquake, war, water or other forces of nature or acts of God, delays or failures of transportation, equipment shortages, suppliers’ failures, or acts or omissions of common carriers, fire; riots, civil disorders; strikes or other labor disputes, embargoes; injunctions (provided the injunction was not issued as a result of


129

any fault or negligence of the party seeking to have its default or delay excused); or any other cause beyond the reasonable control of a party; provided the non-performing party and its Subcontractors are without fault in causing the default or delay, and the default or delay could not have been prevented by reasonable precautions and cannot reasonably be circumvented by the non-performing party through the use of alternate sources, workaround plans or other means, including disaster recovery plans. If a party does not perform its contractual obligations for any of the reasons listed above, the non-performing party will be excused from any further performance of its affected obligation(s) for as long as the circumstances prevail. But the party must use commercially reasonable efforts to recommence performance whenever and to whatever extent possible without delay. A party must promptly notify the other party in writing immediately after the excusable failure occurs, and also when it abates or ends. If any of the above-enumerated circumstances substantially prevent, hinder, or delay the Contractor’s performance of the Services/provision of Deliverables for more than 10 Business Days, and the State determines that performance is not likely to be resumed within a period of time that is satisfactory to the State in its reasonable discretion, then at the State’s option: (a) the State may procure the affected Services/Deliverables from an alternate source, and the State is not be liable for payment for the unperformed Services/ Deliverables not provided under the Contract for so long as the delay in performance continues; (b) the State may terminate any portion of the Contract so affected and the charges payable will be equitably adjusted to reflect those Services/Deliverables terminated; or (c) the State may terminate the affected Statement of Work without liability to Contractor as of a date specified by the State in a written notice of termination to the Contractor, except to the extent that the State must pay for Services/Deliverables provided through the date of termination. The Contractor will not have the right to any additional payments from the State as a result of any Excusable Failure occurrence or to payments for Services not rendered/Deliverables not provided as a result of the Excusable Failure condition. Defaults or delays in performance by Contractor which are caused by acts or omissions of its Subcontractors will not relieve Contractor of its obligations under the Contract except to the extent that a Subcontractor is itself subject to an Excusable Failure condition described above and Contractor cannot reasonably circumvent the effect of the Subcontractor’s default or delay in performance through the use of alternate sources, workaround plans or other means.

2.250 Approval of Deliverables

2.251 Delivery of Deliverables

A list of the Deliverables to be prepared and delivered by Contractor including, for each Deliverable, the scheduled delivery date and a designation of whether the Deliverable is a document (“Written Deliverable”) or a Custom Software Deliverable is attached, if applicable. All Deliverables shall be completed and delivered for State review and written approval and, where applicable, installed in accordance with the State-approved delivery schedule and any other applicable terms and conditions of this Contract. Prior to delivering any Deliverable to the State, Contractor will first perform all required quality assurance activities, and, in the case of Custom Software Deliverables, System Testing to verify that the Deliverable is complete and in conformance with its specifications. Before delivering a Deliverable to the State, Contractor shall certify to the State that (1) it has performed such quality assurance activities, (2) it has performed any applicable testing, (3) it has corrected all material deficiencies discovered during such quality assurance activities and testing, (4) the Deliverable is in a suitable state of readiness for the State’s review and approval, and (5) the Deliverable/Service has all Critical Security patches/updates applied. In discharging its obligations under this Section, Contractor shall be at all times (except where the parties agree otherwise in writing) in compliance with Level 3 of the Software Engineering Institute’s Capability Maturity Model for Software (“CMM Level 3”) or its equivalent.

2.252 Contractor System Testing


130

Contractor will be responsible for System Testing each Custom Software Deliverable in Contractor’s development environment prior to turning over the Custom Software Deliverable to the State for User Acceptance Testing and approval. Contractor’s System Testing shall include the following, at a minimum, plus any other testing required by CMM Level 3 or Contractor’s system development methodology:

Contractor will be responsible for performing Unit Testing and incremental Integration Testing of the components of each Custom Software Deliverable.

Contractor’s System Testing will also include Integration Testing of each Custom Software Deliverable to ensure proper inter-operation with all prior software Deliverables, interfaces and other components that are intended to inter-operate with such Custom Software Deliverable, and will include Regression Testing, volume and stress testing to ensure that the Custom Software Deliverables are able to meet the State’s projected growth in the number and size of transactions to be processed by the Application and number of users, as such projections are set forth in the applicable Statement of Work.

Contractor’s System Testing will also include Business Function Testing and Technical Testing of each Application in a simulated production environment. Business Function Testing will include testing of full work streams that flow through the Application as the Application will be incorporated within the State’s computing environment. The State shall participate in and provide support for the Business Function Testing to the extent reasonably requested by Contractor. Within ten (10) days before the commencement of Business Function Testing pursuant to this Section, Contractor shall provide the State for State review and written approval Contractor’s test plan for Business Function Testing.

Within five (5) Business Days following the completion of System Testing pursuant to this Section, Contractor shall provide to the State a testing matrix establishing that testing for each condition identified in the System Testing plans has been conducted and successfully concluded. To the extent that testing occurs on State premises, the State shall be entitled to observe or otherwise participate in testing under this Section as the State may elect.

2.253 Approval of Deliverables, In General

All Deliverables (Written Deliverables and Custom Software Deliverables) require formal written approval by the State, in accordance with the following procedures. Formal approval by the State requires that the Deliverable be confirmed in writing by the State to meet its specifications which, in the case of Custom Software Deliverables, will include the successful completion of State User Acceptance Testing, to be led by the State with the support and assistance of Contractor. The parties acknowledge that the approval process set forth herein will be facilitated by ongoing consultation between the parties, visibility of interim and intermediate Deliverables and collaboration on key decisions.

The State’s obligation to comply with any State Review Period is conditioned on the timely delivery of Deliverables being reviewed. If Contractor fails to provide a Deliverable to the State in a timely manner, the State will nevertheless use commercially reasonable efforts to complete its review or testing within the applicable State Review Period.

Before commencement of its review or testing of a Deliverable, the State may inspect the Deliverable to confirm that all components of the Deliverable (e.g., software, associated documentation, and other materials) have been delivered. If the State determines that the Deliverable is incomplete, the State may refuse delivery of the Deliverable without performing any further inspection or testing of the Deliverable. Otherwise, the review period will be deemed to have started on the day the State receives the Deliverable and the applicable certification by Contractor in accordance with Section 2.080.

The State will approve in writing a Deliverable upon confirming that it conforms to and, in the case of a Custom Software Deliverable, performs in accordance with, its specifications without material deficiency. The State may, but shall not be required to, conditionally approve in writing a Deliverable that contains material deficiencies if the State elects to permit Contractor to rectify them post-approval. In any case, Contractor will be responsible for working diligently to correct within a reasonable time at Contractor’s expense all deficiencies in the Deliverable that remain outstanding at the time of State approval.


131

If, after three (3) opportunities (the original and two repeat efforts), Contractor is unable to correct all deficiencies preventing State approval of a Deliverable, the State may: (i) demand that Contractor cure the failure and give Contractor additional time to cure the failure at the sole expense of Contractor; or (ii) keep this Contract in force and do, either itself or through other parties, whatever Contractor has failed to do, in which event Contractor shall bear any excess expenditure incurred by the State in so doing beyond the Contract price for such Deliverable and will pay the State an additional sum equal to ten percent (10%) of such excess expenditure to cover the State’s general expenses without the need to furnish proof in substantiation of such general expenses; or (iii) terminate this Contract for default, either in whole or in part by notice to Contractor (and without the need to afford Contractor any further opportunity to cure). Notwithstanding the foregoing, the State shall not use, as a basis for exercising its termination rights under this Section, deficiencies discovered in a repeat State Review Period that could reasonably have been discovered during a prior State Review Period.

The State, at any time and in its own discretion, may halt the UAT or approval process if such process reveals deficiencies in or problems with a Deliverable in a sufficient quantity or of a sufficient severity as to make the continuation of such process unproductive or unworkable. In such case, the State may return the applicable Deliverable to Contractor for correction and re-delivery prior to resuming the review or UAT process and, in that event, Contractor will correct the deficiencies in such Deliverable in accordance with the Contract, as the case may be.

2.254 Process for Approval of Written Deliverables

The State Review Period for Written Deliverables will be the number of days set forth in the applicable Statement of Work following delivery of the final version of the Written Deliverable (failing which the State Review Period, by default, shall be five (5) Business Days for Written Deliverables of one hundred (100) pages or less and ten (10) Business Days for Written Deliverables of more than one hundred (100) pages). The duration of the State Review Periods will be doubled if the State has not had an opportunity to review an interim draft of the Written Deliverable prior to its submission to the State. The State agrees to notify Contractor in writing by the end of the State Review Period either stating that the Written Deliverable is approved in the form delivered by Contractor or describing any deficiencies that must be corrected prior to approval of the Written Deliverable (or at the State’s election, subsequent to approval of the Written Deliverable). If the State delivers to Contractor a notice of deficiencies, Contractor will correct the described deficiencies and within five (5) Business Days resubmit the Deliverable in a form that shows all revisions made to the original version delivered to the State. Contractor’s correction efforts will be made at no additional charge. Upon receipt of a corrected Written Deliverable from Contractor, the State will have a reasonable additional period of time, not to exceed the length of the original State Review Period, to review the corrected Written Deliverable to confirm that the identified deficiencies have been corrected.

2.255 Process for Approval of Custom Software Deliverables

The State will conduct UAT of each Custom Software Deliverable in accordance with the following procedures to determine whether it meets the criteria for State approval – i.e., whether it conforms to and performs in accordance with its specifications without material deficiencies.

Within thirty (30) days (or such other number of days as the parties may agree to in writing) prior to Contractor’s delivery of any Custom Software Deliverable to the State for approval, Contractor shall provide to the State a set of proposed test plans, including test cases, scripts, data and expected outcomes, for the State’s use (which the State may supplement in its own discretion) in conducting UAT of the Custom Software Deliverable. Contractor, upon request by the State, shall provide the State with reasonable assistance and support during the UAT process.

For the Custom Software Deliverables provided as part of Section 1.104 Base Support and Major Enhancement services , the State Review Period for conducting UAT will be as indicated in the applicable project plan for Base Support services or SOW for Major Enhancements. For any other Custom Software Deliverables, the State Review Period shall be the number of days agreed in writing by the parties (failing which it shall be forty-five (45) days by default). The State Review Period for each Custom Software Deliverable will begin when Contractor has delivered the Custom Software Deliverable to the State


132

accompanied by the certification required by Section 2.250 and the State’s inspection of the Deliverable has confirmed that all components of it have been delivered.

The State’s UAT will consist of executing test scripts from the proposed testing submitted by Contractor, but may also include any additional testing deemed appropriate by the State. If the State determines during the UAT that the Custom Software Deliverable is not working according to specifications, the State will notify Contractor of the deficiency by making an entry in an incident reporting system available to both Contractor and the State. Contractor will modify promptly the Custom Software Deliverable to correct the reported deficiencies, conduct appropriate System Testing (including, where applicable, Regression Testing) to confirm the proper correction of the deficiencies and re-deliver the corrected version to the State for re-testing in UAT. Contractor will coordinate the re-delivery of corrected versions of Custom Software Deliverables with the State so as not to disrupt the State’s UAT process. The State will promptly re-test the corrected version of the Software Deliverable after receiving it from Contractor.

Within three (3) business days after the end of the State Review Period, the State will give Contractor a written notice indicating the State’s approval or rejection of the Custom Software Deliverable according to the criteria and process set out in this Section 2.080.

2.256 Final Acceptance

“Final Acceptance” shall be considered to occur when the Custom Software Deliverable to be delivered has been approved by the State and has been operating in production without any material deficiency for fourteen (14) consecutive days. If the State elects to defer putting a Custom Software Deliverable into live production for its own reasons, not based on concerns about outstanding material deficiencies in the Deliverable, the State shall nevertheless grant Final Acceptance of the Project.

2.260 Ownership

2.261 Ownership of Work Product by State

The State owns all Deliverables, as they are work made for hire by the Contractor for the State. The State owns all United States and international copyrights, trademarks, patents or other proprietary rights in the Deliverables.

2.262 Vesting of Rights

The Contractor shall assign, and upon creation of each Deliverable automatically assigns, to the State, ownership of all United States and international copyrights, trademarks, patents, or other proprietary rights in each and every Deliverable, whether or not registered by the Contractor, insofar as any such Deliverable, by operation of law, may not be considered work made for hire by the Contractor for the State. From time to time upon State’s request, the Contractor and/or its personnel shall confirm such assignment by execution and delivery of the assignments, confirmations of assignment, or other written instruments as the State may request. The State shall have the right to obtain and hold in its own name all copyright, trademark, and patent registrations and other evidence of rights that may be available for Deliverables.

2.263 Rights in Data

The State is the owner of all data made available by the State to the Contractor or its agents, Subcontractors or representatives under the Contract. The Contractor will not use the State’s data for any purpose other than providing the Services, nor will any part of the State’s data be disclosed, sold, assigned, leased or otherwise disposed of to the general public or to specific third parties or commercially exploited by or on behalf of the Contractor. No employees of the Contractor, other than those on a strictly need-to-know basis, have access to the State’s data. Contractor will not possess or assert any lien or other right against the State’s data. Without limiting the generality of this Section, the Contractor must only use personally identifiable information as strictly necessary to provide the Services and must disclose the information only to its employees who have a strict need-to-know the information. The Contractor must comply at all times with all laws and regulations applicable to the personally identifiable information.


133

The State is the owner of all State-specific data under the Contract. The State may use the data provided by the Contractor for any purpose. The State will not possess or assert any lien or other right against the Contractor’s data. Without limiting the generality of this Section, the State may use personally identifiable information only as strictly necessary to utilize the Services and must disclose the information only to its employees who have a strict need to know the information, except as provided by law. The State must comply at all times with all laws and regulations applicable to the personally identifiable information. Other material developed and provided to the State remains the State’s sole and exclusive property.

2.264 Ownership of Materials

State and Contractor will continue to own their respective proprietary technologies developed before entering into the Contract. Any hardware bought through the Contractor by the State, and paid for by the State, will be owned by the State. Any software licensed through the Contractor and sold to the State, will be licensed directly to the State. Notwithstanding the forgoing or any provision of this Contract to the contrary, any preexisting work or materials including, but not limited to, any routines, libraries, tools, methodologies, processes or technologies (collectively, the “Development Tools”) created, adapted or used by the Contractor in its business generally, including any and all associated intellectual property rights, shall be and remain the sole property of the Contractor, and the State shall have no interest in or claim to such preexisting work, materials or Development Tools, except as necessary to exercise its rights in the Deliverables created under this Agreement. If any pre-existing work or materials are incorporated into any Deliverables, the State shall receive an irrevocable, nonexclusive, worldwide, royalty-free license to (1) use, execute, reproduce, display, perform, distribute internally and prepare derivative works based upon the preexisting works, and (2) authorize or sublicense others from time to time to do any or all of the foregoing to other governmental agencies. 2.265 Standard Software If applicable and necessary, all Standard Software used in performing the Services shall be provided to the State under a separate license agreement between the State and the owner (or authorized licensor) of such software.

2.266 General Skills

The Contractor and its subcontractors shall be free to use and employ their general skills, knowledge and expertise, and to use, disclose, and employ any generalized ideas, concepts, knowledge, methods, techniques or skills gained or learned during the course of performing the services under this Contract, so long as the Contractor or its subcontractors acquire and apply such information without disclosure of any confidential or proprietary information of the State, and without any unauthorized use or disclosure of any Work Product resulting from this Contract.

2.267 Contractor License in Deliverables The State grants to the Contractor, a royalty-free, world-wide, non-exclusive right and license under any Deliverable and/or Derivative Work now or in the future owned by the State, or with respect to which the State has a right to grant such rights or licenses, to the extent required by the Contractor to market the Deliverables and/or Derivative Work and exercise its full rights in the Deliverables and/or Derivative Work, including, without limitation, the right to make, use and sell products and services based on or incorporating such Deliverables and/or Derivative Work.

2.270 State Standards

2.271 Existing Technology Standards

The Contractor will adhere to all existing standards as described within the comprehensive listing of the State’s existing technology standards at http://www.michigan.gov/dit.

2.272 Acceptable Use Policy


134

To the extent that Contractor has access to the State computer system, Contractor must comply with the State’s Acceptable Use Policy, see http://www.michigan.gov/ditservice. All Contractor employees must be required, in writing, to agree to the State’s Acceptable Use Policy before accessing the State system. The State reserves the right to terminate Contractor’s access to the State system if a violation occurs.

2.273 Systems Changes

Contractor is not responsible for and not authorized to make changes to any State systems without written authorization from the Project Manager. Any changes Contractor makes to State systems with the State’s approval must be done according to applicable State procedures, including security, access and configuration management procedures.

2.280 Extended Purchasing

2.281 MiDEAL (Michigan Delivery Extended Agreements Locally

Public Act 431 of 1984 permits DTMB to provide purchasing services to any city, village, county, township, school district, intermediate school district, non-profit hospital, institution of higher education, community, or junior college. A current listing of approved program members is available at: www.michigan.gov/buymichiganfirst. Unless otherwise stated, the Contractor must ensure that the non-state agency is an authorized purchaser before extending the Contract pricing.

The Contractor will supply Contract Services and equipment to these local governmental agencies at the established State of Michigan Contract prices and terms to the extent applicable and where available. The Contractor must send its invoices to, and pay the local unit of government, on a direct and individual basis.

To the extent that authorized local units of government purchase quantities of Services and/or equipment under this Contract, the quantities of Services and/or equipment purchased will be included in determining the appropriate rate wherever tiered pricing based on quantity is provided.

Please Visit Mi DEAL at www.michigan.gov/buymichiganfirst under MiDeal.

Estimated requirements for authorized local units of government are not included in the quantities shown in this RFP.

2.282 State Employee Purchases RESERVED.

2.290 Environmental Provision

2.291 Environmental Provision Energy Efficiency Purchasing Policy: The State seeks wherever possible to purchase energy efficient products. This includes giving preference to U.S. Environmental Protection Agency (EPA) certified ‘Energy Star’ products for any category of products for which EPA has established Energy Star certification. For other purchases, the State may include energy efficiency as one of the priority factors to consider when choosing among comparable products.

Environmental Purchasing Policy: The State of Michigan is committed to encouraging the use of products and services that impact the environment less than competing products. The State is accomplishing this by including environmental considerations in purchasing decisions, while remaining fiscally responsible, to promote practices that improve worker health, conserve natural resources, and prevent pollution. Environmental components that are to be considered include: recycled content and recyclables; energy efficiency; and the presence of undesirable materials in the products, especially those toxic chemicals which are persistent and bioaccumulative. The Contractor should be able to supply products containing recycled and environmentally preferable materials that meet performance requirements and is encouraged to offer such products throughout the duration of this Contract. Information on any relevant third party certification (such as Green Seal, Energy Star, etc.) should also be provided.


135

Hazardous Materials: For the purposes of this Section, “Hazardous Materials” is a generic term used to describe asbestos, ACBMs, PCBs, petroleum products, construction materials including paint thinners, solvents, gasoline, oil, and any other material the manufacture, use, treatment, storage, transportation or disposal of which is regulated by the federal, state or local laws governing the protection of the public health, natural resources or the environment. This includes, but is not limited to, materials the as batteries and circuit packs, and other materials that are regulated as (1) “Hazardous Materials” under the Hazardous Materials Transportation Act, (2) “chemical hazards” under the Occupational Safety and Health Administration standards, (3) “chemical substances or mixtures” under the Toxic Substances Control Act, (4) “pesticides” under the Federal Insecticide Fungicide and Rodenticide Act, and (5) “hazardous wastes” as defined or listed under the Resource Conservation and Recovery Act. (a) The Contractor shall use, handle, store, dispose of, process, transport and transfer any material

considered a Hazardous Material according to all federal, State and local laws. The State shall provide a safe and suitable environment for performance of Contractor’s Work. Before the commencement of Work, the State shall advise the Contractor of the presence at the work site of any Hazardous Material to the extent that the State is aware of the Hazardous Material. If the Contractor encounters material reasonably believed to be a Hazardous Material and which may present a substantial danger, the Contractor shall immediately stop all affected Work, notify the State in writing about the conditions encountered, and take appropriate health and safety precautions.

(b) Upon receipt of a written notice, the State will investigate the conditions. If (a) the material is a Hazardous Material that may present a substantial danger, and (b) the Hazardous Material was not brought to the site by the Contractor, or does not result in whole or in part from any violation by the Contractor of any laws covering the use, handling, storage, disposal of, processing, transport and transfer of Hazardous Materials, the State shall order a suspension of Work in writing. The State shall proceed to have the Hazardous Material removed or rendered harmless. In the alternative, the State shall terminate the affected Work for the State’s convenience.

(c) Once the Hazardous Material has been removed or rendered harmless by the State, the Contractor shall resume Work as directed in writing by the State. Any determination by the Michigan Department of Community Health or the Michigan Department of Environmental Quality that the Hazardous Material has either been removed or rendered harmless is binding upon the State and Contractor for the purposes of resuming the Work. If any incident with Hazardous Material results in delay not reasonable anticipatable under the circumstances and which is attributable to the State, the applicable SLAs for the affected Work will not be counted in a time as mutually agreed by the parties.

(d) If the Hazardous Material was brought to the site by the Contractor, or results in whole or in part from any violation by the Contractor of any laws covering the use, handling, storage, disposal of, processing, transport and transfer of Hazardous Material, or from any other act or omission within the control of the Contractor, the Contractor shall bear its proportionate share of the delay and costs involved in cleaning up the site and removing and rendering harmless the Hazardous Material according to Applicable Laws to the condition approved by applicable regulatory agency(ies).

Labeling: Michigan has a Consumer Products Rule pertaining to labeling of certain products containing volatile organic compounds. For specific details visit http://www.michigan.gov/deq/0,1607,7-135-3310_4108-173523--,00.html

Refrigeration and Air Conditioning: The Contractor shall comply with the applicable requirements of Sections 608 and 609 of the Clean Air Act (42 U.S.C. 7671g and 7671h) as each or both apply to this contract.

Environmental Performance: Waste Reduction Program - Contractor shall establish a program to promote cost-effective waste reduction in all operations and facilities covered by this contract. The Contractor's programs shall comply with applicable Federal, State, and local requirements, specifically including Section 6002 of the Resource Conservation and Recovery Act (42 U.S.C. 6962, et seq.).

2.300 Deliverables

2.301 Software Reserved


136

2.302 Hardware

Reserved

2.310 Software Warranties

2.311 Performance Warranty

The Contractor represents and warrants that Deliverables, after Final Acceptance, will perform and operate in compliance with the requirements and other standards of performance contained in this Contract (including all descriptions, specifications and drawings made a part of the Contract) for a period of ninety (90) days. In the event of a breach of this warranty, Contractor will promptly correct the affected Deliverable(s) at no charge to the State.

2.312 No Surreptitious Code Warranty

The Contractor represents and warrants that no copy of licensed Software provided to the State contains or will contain any Self-Help Code or any Unauthorized Code as defined below. This warranty is referred to in this Contract as the “No Surreptitious Code Warranty.” As used in this Contract, “Self-Help Code” means any back door, time bomb, drop dead device, or other software routine designed to disable a computer program automatically with the passage of time or under the positive control of a person other than the licensee of the software. Self-Help Code does not include Software routines in a computer program, if any, designed to permit an owner of the computer program (or other person acting by authority of the owner) to obtain access to a licensee’s computer system(s) (e.g. remote access via modem) for purposes of maintenance or technical support. As used in this Contract, “Unauthorized Code” means any virus, Trojan horse, spyware, worm or other Software routines or components designed to permit unauthorized access to disable, erase, or otherwise harm software, equipment, or data; or to perform any other such actions. The term Unauthorized Code does not include Self-Help Code. Unauthorized Code does not include Software routines in a computer program, if any, designed to permit an owner of the computer program (or other person acting by authority of the owner) to obtain access to a licensee’s computer system(s) (e.g. remote access via modem) for purposes of maintenance or technical support. In addition, Contractor will use up-to-date commercial virus detection software to detect and remove any viruses from any software prior to delivering it to the State.

2.313 Calendar Warranty

The Contractor represents and warrants that all software for which the Contractor either sells or licenses to the State of Michigan and used by the State prior to, during or after the calendar year 2000, includes or shall include, at no added cost to the State, design and performance so the State shall not experience software abnormality and/or the generation of incorrect results from the software, due to date oriented processing, in the operation of the business of the State of Michigan. The software design, to insure calendar year rollover compatibility, shall include, but is not limited to: data structures (databases, data files, etc.) that provide 4-digit date century; stored data that contain date century recognition, including, but not limited to, data stored in databases and hardware device internal system dates; calculations and program logic (e.g., sort algorithms, calendar generation, event recognition, and all processing actions that use or produce date values) that accommodates same century and multi-century formulas and date values; interfaces that supply data to and receive data from other systems or organizations that prevent non-compliant dates and data from entering any State system; user interfaces (i.e., screens, reports, etc.) that accurately show 4 digit years; and assurance that the year 2000 shall be correctly treated as a leap year within all calculation and calendar logic.


137

2.314 Third-party Software Warranty

The Contractor represents and warrants that it will disclose the use or incorporation of any third-party software into the Deliverables. At the time of Delivery, the Contractor shall provide in writing the name and use of any Third-party Software, including information regarding the Contractor’s authorization to include and utilize such software. The notice shall include a copy of any ownership agreement or license that authorizes the Contractor to use the Third-party Software.

2.315 Physical Media Warranty

Contractor represents and warrants that each licensed copy of the Software, excluding, however, third party Software, provided by the Contractor is free from physical defects in the media that tangibly embodies the copy. This warranty does not apply to defects discovered more than thirty (30) days after that date of Final Acceptance of the Software by the State. This warranty does not apply to defects arising from acts of Excusable Failure. If the Contractor breaches this warranty, then the State shall be entitled to replacement of the non-compliant copy by Contractor, at Contractor’s expense (including shipping and handling).

2.320 Software Licensing

2.321 Cross-License, Deliverables Only, License to Contractor

Reserved

2.322 Cross-License, Deliverables and Derivative Work, License to Contractor

Reserved

2.323 License Back to the State

Reserved

2.324 License Retained by Contractor

Reserved

2.325 Pre-existing Materials for Custom Software Deliverables

Reserved

2.330 Source Code Escrow

2.331 Definition

Reserved

2.332 Delivery of Source Code into Escrow

Reserved

2.333 Delivery of New Source Code into Escrow

Reserved

2.334 Verification

Reserved

2.335 Escrow Fees

Reserved

2.336 Release Events

Reserved


138

2.337 Release Event Procedures

Reserved

2.338 License

Reserved

2.339 Derivative Works

Reserved


139

Glossary Days Means calendar days unless otherwise specified.

24x7x365 Means 24 hours a day, seven days a week, and 365 days a year (including the 366th day in a leap year).

Additional Service Means any Services/Deliverables within the scope of the Contract, but not specifically provided under any Statement of Work, that once added will result in the need to provide the Contractor with additional consideration.

Audit Period See Section 2.110

Business Day Whether capitalized or not, shall mean any day other than a Saturday, Sunday or State-recognized legal holiday (as identified in the Collective Bargaining Agreement for State employees) from 8:00am EST through 5:00pm EST unless otherwise stated.

Blanket Purchase Order

An alternate term for Contract as used in the States computer system.

Business Critical Any function identified in any Statement of Work as Business Critical. Chronic Failure Defined in any applicable Service Level Agreements. Deliverable Physical goods and/or commodities as required or identified by a Statement of Work DTMB Michigan Department of Technology, Management and Budget

Environmentally preferable products

A product or service that has a lesser or reduced effect on human health and the environment when compared with competing products or services that serve the same purpose. Such products or services may include, but are not limited to, those that contain recycled content, minimize waste, conserve energy or water, and reduce the amount of toxics either disposed of or consumed.

Excusable Failure See Section 2.244.

Hazardous material Any material defined as hazardous under the latest version of federal Emergency Planning and Community Right-to-Know Act of 1986 (including revisions adopted during the term of the Contract).

Incident Any interruption in Services.

ITB A generic term used to describe an Invitation to Bid. The ITB serves as the document for transmitting the RFP to potential bidders

Key Personnel Any Personnel designated in Article 1 as Key Personnel.

New Work Any Services/Deliverables outside the scope of the Contract and not specifically provided under any Statement of Work, that once added will result in the need to provide the Contractor with additional consideration.

Ozone-depleting substance

Any substance the Environmental Protection Agency designates in 40 CFR part 82 as: (1) Class I, including, but not limited to, chlorofluorocarbons, halons, carbon tetrachloride, and methyl chloroform; or (2) Class II, including, but not limited to, hydro chlorofluorocarbons

Post-Consumer Waste

Any product generated by a business or consumer which has served its intended end use, and which has been separated or diverted from solid waste for the purpose of recycling into a usable commodity or product, and which does not include post-industrial waste.

Post-Industrial Waste

Industrial by-products that would otherwise go to disposal and wastes generated after completion of a manufacturing process, but do not include internally generated scrap commonly returned to industrial or manufacturing processes.

Recycling

The series of activities by which materials that are no longer useful to the generator are collected, sorted, processed, and converted into raw materials and used in the production of new products. This definition excludes the use of these materials as a fuel substitute or for energy production.

Deleted – Not Applicable

Section is not applicable or included in this RFP. This is used as a placeholder to maintain consistent numbering.

Reuse Using a product or component of municipal solid waste in its original form more than once.


140

RFP Request for Proposal designed to solicit proposals for services Services Any function performed for the benefit of the State.

Source reduction Any practice that reduces the amount of any hazardous substance, pollutant, or contaminant entering any waste stream or otherwise released into the environment prior to recycling, energy recovery, treatment, or disposal.

State Location Any physical location where the State performs work. State Location may include state-owned, leased, or rented space.

Subcontractor A company Contractor delegates performance of a portion of the Services to, but does not include independent contractors engaged by Contractor solely in a staff augmentation role.

Unauthorized Removal

Contractor’s removal of Key Personnel without the prior written consent of the State.

Waste prevention Source reduction and reuse, but not recycling.

Waste reduction and Pollution prevention

The practice of minimizing the generation of waste at the source and, when wastes cannot be prevented, utilizing environmentally sound on-site or off-site reuse and recycling. The term includes equipment or technology modifications, process or procedure modifications, product reformulation or redesign, and raw material substitutions. Waste treatment, control, management, and disposal are not considered pollution prevention, per the definitions under Part 143, Waste Minimization, of the Natural Resources and Environmental Protection Act (NREPA), 1994 PA 451, as amended.

Work in Progress A Deliverable that has been partially prepared, but has not been presented to the State for Approval.

Work Product Refers to any data compilations, reports, and other media, materials, or other objects or works of authorship created or produced by the Contractor as a result of an in furtherance of performing the services required by this Contract.

List of Acronyms

Acronym Description

ACD Automatic Call Distribution

ADA Americans with Disabilities ACT

ASA Average Speed of Answer

BAFO Best and Final Offer

CMM Capability Maturity Model

CMS Call Management System

COTS Commercial Off The Shelf

CRM Customer Relationship Management System

CRS Challenge Response System

CSC DTMB Client Service Center

CSR Customer Service Representative

CTI Computer Telephone Integration

DEQ Department of Environmental Quality

DHS Department of Human Services

DNR Department of Natural Resources

DTMB Department of Technology, Management and Budget

EAC Environmental Assistance Center

EAP Environmental Assistance Program

EIM Enterprise Integration Manager


141

Acronym Description

EPA Environmental Protection Agency

FAP Food Assistance Program

FOIA Michigan Freedom of Information Act

GVP Genesys Voice Portal

ICHAT Michigan State Police Background checks

IDL Inbound Document Linker

IT Information Technology

IVR Interactive Voice Response

IW Interaction Workspace

JRS Judges Retirement System LARA - BHP Licensing and Regulatory Affairs - Bureau of Health Professionals

LDAP Lightweight Directory Access Protocol

LOV List of Values

MARCS The Treasury Collection System

MCSC Michigan Civil Service Commission

MDIT Michigan Department of Technology

MDOS Michigan Department of State

MGA Michigan Guaranty Agency

MI HR Michigan Human Resources

MiDEAL Michigan Delivery Extended Agreements Locally

MiECC Michigan Enterprise Contact Center

MPSERS Michigan Public Schools Retirement System

MS Microsoft

NCIC National Crime Information Center

ODM Operational Data Mart

OEM Original Equipment Manufacturer

OPPCA Office of Pollution Prevention and Compliance Assistance

ORS DTMB Office of Retirement Services

PCI Payment Card Industry

PCS Hazardous Materials

PIN Personal Identification Number

PM Project Manager

PO Purchase Order

RFP Request for Proposal

SEM Systems Engineering Methodology

SER State Emergency Relief

SERS State Employee Retirement System

SLA Service Level Agreement

SME Subject Matter Expert

SOW Statement of Work

SPOC Single Point of Contact

SPRS State Police Retirement System


142

Acronym Description

SSL Secure Socket Layer

SUITE State Unified Information Technology Environment

TTS Text to Speech

UAT User Acceptance Testing

URL Uniform Resource Locator

VAR Voice Application Reporter

VB Visual Basic

WAS Websphere Application Server


143

Attachment 1: Service Level Agreement and Return to Service Goals

The State’s Remedy ticket system will be used to initiate and manage break/fix and maintenance requests. Remedy tickets may be created by business users or the contractor and will identify the problem to be fixed. Tickets will be classified as follows, with the following Service Level Agreement (“SLA”):

Classification Service Level Standard

HIGH The problem renders the product inoperable for a majority of the users of a specific (or multiple) contact centers. For example, the Siebel eService application for Treasury is not accessible by the taxpayers. Level High problems are assigned the highest priority and are considered to be a business emergency situation. Mission Critical to the business as the application is critical to the organization's operation. Criteria: (1) Affects end customers' or agency’s revenue base (2) server down; (3) Critical infrastructure components; (4) Network outage affects users; (5) Application unavailable/down; (6) Downtime leads to non-recoverable consequences.

Acknowledged within 15 minutes from time of receipt of ticket during contact center business hours and within 30 minutes during non-business hours. First status report within 2 hours of receipt of ticket, usually with a workaround. Resolution dependent upon the nature of the issue. Additional Progress Reports have a 1 hour interval or as agreed upon by the agency. Return to Service Goal of 4 business hours 90% of the time.

Medium The problem has a significant impact to the system’s ability to perform, but a workaround is available or operations can continue in a degraded state. For example, the data retrieval to a Siebel screen is slow for a large number of users. A Medium problem reflects a situation where many users and/or customers are directly impacted. Considered Mission Important/ Process Critical to the business as the application is critical to the organization's operations, but the impact to the customer may not be visible. Criteria: (1) Affects end customers' or agency’s revenue base, (2) Application unavailable/down; (3) Several users down; (4) Downtime is recoverable.

Acknowledged within 1 business hour(s) from time of receipt of ticket during contact center business hours and within 2 hours during non-business hours. First status report within 4 hours of receipt of ticket, usually with a workaround. Resolution dependent upon the nature of the issue. Additional Progress Reports as agreed upon by the agency. Return to Service Goal of 8 business hours 90% ofthe time


144

Classification Service Level Standard

Low The problem slightly impacts the system’s ability to perform. For example, a Siebel password needs to be reset or single user related issues or ad-hoc query requests. A Low problem reflects a situation where one or more users are affected. Problems are Process Important to the business as the application is critical to the business operations but the impact to the customer is not visible. Criteria: (1) Single User Down; Processing can still exist without impacting data integrity; (3) Downtime has internal consequences only.

Acknowledged within 8 business hour(s) from time of receipt of ticket during contact center business hours. First status Report within 2 days of receipt of ticket. Additional Progress Reports as agreed upon by the agency. Return to Service Goal of 16 business hours 90% of the time.


145

Attachment 2: Work Requirements Section 1 through 8 is part of Base Service. Section 9 is part of Major Enhancements.

1. General requirements

# Detailed Requirement Comments G1 The contractor must follow State’s SUITE

methodology and SEM process which includes deliverables.

Contractor agrees.

G2 The contractor must follow State’s Enterprise IT Policies, Standards and Procedures.

Contractor agrees.

G3 The contractor must follow State’s Enterprise IT Security Policy and Procedures and Treasury’s additional security requirements as described in Appendix K.

Contractor agrees.

G4 The Contractor shall provide ongoing technical system support.

Contractor agrees to provide technical support for in scope software. See (G8)

G5 The Contractor shall provide online technical system documentation in a location designated and accessible by State staff.

Contractor agrees.

G6 The Contractor shall provide on-site technical support.

Contractor agrees.

G7 The Contractor must provide an escalation process for technical support.

For software technical support, Contractor shall escalate through the vendors support channels via the State maintenance contracts. Contractor shall continue to follow the SOM/DTMB escalation process for day to day technical issues as needed.

G8 The contractor must provide technical support in the following tools -

a. Siebel Contractor agrees. b. Siebel interfaces Contractor agrees to support the in scope Siebel

Interfaces. c. Batch (from Oracle legacy extract to

Siebel Base) Contractor agrees to support the Siebel Batch jobs from the History tables to Siebel Base through Siebel EIM tables.

d. Genesys GVP Contractor agrees. e. Genesys CTI-Gplus Adapter Contractor agrees. f. Genesys WFM Contractor agrees. g. Virtual Hold (VHT) Contractor agrees. h. NICE Contractor agrees to provide backup system

administration functions for NICE environment. i. FileNet Capture. Contractor agrees to support the Scan and Index Form.

The Capture product installations on desktops in the Treasury Scanning room shall continue to be supported by DTMB.

j. FileNet CIS Contractor agrees to provide technical support for the FileNet CIS connectors.

k. Opalis Contractor agrees to run and modify Opalis jobs in scope for the Treasury contact center, but shall not provide Opalis software technical support.


146

# Detailed Requirement Comments l. Tidal Contractor agrees to request Tidal job updates to DTMB.

DTMB shall provide the Tidal software technical support. m. Real Time (MDOS Hotkey) Contractor agrees to provide technical support for

HotKeys. DTMB shall support the web service. G9 The contractor must communicate with the

DTMB Program Manager and the business areas about problems that may affect operation of the agency’s call center.

Contractor agrees.

G10 All maintenance shall be performed by qualified personnel who are familiar with the systems.

Contractor agrees.

G11 The Contractor shall provide backup resources.

Contractor agrees.

G12 The Contractor shall provide one point of contact to report system malfunction whether malfunction is due to software or is of unknown origin. The Contractor shall be responsible for providing the appropriate remedy to the issue.

Contractor agrees.

G13 The contractor must provide a one-year (or 18 months) rolling plan for each call center identifying activities being carried out, and activities to be carried out, by the team.

Contractor agrees.

G14 The contractor must conduct separate monthly meetings with each agency’s business managers to discuss the technical performance of the call center. A summary of all maintenance activity must be provided as a part of monthly status reports

Contractor agrees.

G15 Individual agencies have certain periods in the year when functionality is frozen and no releases are implemented. For example, Treasury prefers not to implement during income tax filing season. The contractor will learn about these timelines during knowledge transfer period. The contractor must adhere to individual agency timelines for application changes.

Contractor agrees.

G16 Different agencies have different maintenance windows. For example, DTMB-ORS is 3rd Sunday of the month, 6AM to noon. DHS is every Sunday 7:30 AM to 12:30 PM. The contractor must adhere to individual agency maintenance windows for application changes.

Contractor agrees.

G17 Assist the program management office for all contact center implementations in the State.

Contractor agrees.


147

2. Break fix and Troubleshooting requirements

# Detailed Requirement Comments B1 Respond, with DTMB assistance, to

problems in 24 X 7 customer self-service channels as defined in Attachment 1 SLA.

Contractor agrees.

B2 The Contractor will provide fixes of bugs and breaks meeting requirements for Service Level Agreement and return to service goals as detailed in Attachment 1.

Contractor agrees.

B3 Once support is assigned, the Contractor must maintain a continuous effort to resolve reported high and medium severity problems. The Contractor shall commit sufficient resources to resolve any high severity level problems in as short a timeframe as possible.

Contractor agrees.

B4 If the Contractor determines it cannot correct the problem within the return to service goals as defined in Attachment 1 SLA, the Contractor shall promptly initiate an escalation procedure to assign sufficiently skilled personnel to resolve the problem. Additionally: Contractor staff shall notify senior Contractor management and DTMB IT/agency management that a reported problem has not been corrected. Status reports shall be provided as identified by the State on problem correction activities

Contractor agrees.

B5. Contractor shall utilize State’s Remedy system to record/log all maintenance services performed.

Contractor agrees.

B6. For HIGH priority tickets, the Contractor must fill out a Root Cause Analysis report in State’s prescribed format. The report must be submitted to the State’s project manager and customer agency’s business manager.

Contractor agrees.

3. Product/Software Upgrades and Patches requirements

# Detailed Requirement Comments P1 The contractor must identify the known

problems and compatibility issues for the product Upgrades and report it to the business units so that the business can decide on Upgrades.

Contractor agrees.


148

# Detailed Requirement Comments P2 The contractor must keep all software in

sync with state’s standard of current software versions by upgrading the software as needed.

Contractor agrees.

P3 DTMB is expecting the following Upgrades in next 2-3 years; the contractor must be able to perform these Upgrades.

Contractor shall work with DTMB and agencies to schedule Upgrades as part of the Contact Call Center and Agency Enhancement Plan update processes.

a. Siebel 7.8 to Siebel 8.x Contractor agrees. b. GVP 7.6 to GVP 8.x Contractor agrees. c. Genesys CIM Platform 7.6 to 8.x Contractor agrees. d. Genesys T Server 7.x to 8.x Contractor agrees. e. Oracle 10g to Oracle 11g

(Consult/Assist) Contractor agrees.

f. FileNet 4.0/Image Services/Capture/Inbound Document Linker (IDL) to P8 platform. Scanning/Indexing application, which is currently in VB custom code on FileNet Capture, may require a rewrite, which the contractor will be responsible for as part of Base Support.

Contractor agrees as defined in Section 1.104.

g. PBX switch Upgrade – Avaya 3.1 to 5.x /6.x, AES 4.2 to 6.x (Consult/Assist)

Contractor agrees.

P4 All Upgrades and patches must be communicated using state’s change management process.

Contractor agrees.

4. Application/Technical monitoring requirements

# Detailed Requirement Comments A1 Contractor must be able to monitor

application performance. Contractor agrees.

A2 Contractor must be able to monitor the volume of application usage.

Contractor agrees.

A3. Contractor must actively participate in monitoring SAN space usage.

Contractor agrees.

5. Minor Enhancement requirements

# Detailed Requirement Comments E1. All Minor Enhancements will be prioritized

by the business managers. The Contractor must use a release planning process. The contractor should seek to bundle a number of enhancements that fit logically together into a new point release for each contact center that can be implemented within a 3 or 4 month time period. The contractor must describe their release planning process.

Contractor agrees.

E2. The contractor will produce a detailed project plan showing requirements, design, development and testing.

Contractor agrees.


149

# Detailed Requirement Comments E3 The contractor must get sign off from the

business manager on the high level requirements.

Contractor agrees.

E4 The contractor must record all Minor Enhancement requests the State’s Remedy ticket system.

Contractor agrees.

E5 Contractor shall provide minor application enhancements to the system each year. For any major implementation of new functionality, the contractor must submit a separate SOW.

Contractor agrees.

E6 The business managers from each call center will prioritize the tasks to be completed in their own work plan. Contractor shall define a process to maintain agreed upon support levels in the event of competing priorities and resource contention from the task that the business managers have prioritized. Include a description of the prioritization and contention resolution process in your response.

Contractor agrees.

6. Research and analysis requirements

# Detailed Requirement Comments R1 Contractor must be able to research and

suggest solution to customer needs or work request as it relates to contact center IT services.

Contractor agrees.

R2 Contractor must be able to perform data analysis, study the trend and use predictive modeling to offer pro-active solutions for business issues.

Contractor agrees to be able to perform data analysis, study the trend and use predictive modeling. Depending on level of effort and SEM guidelines, contractor may provide this service as part of mutually agreed upon SOW.

R3 Often problems are not frequently repeatable or happening only for a small set (1-3) of users. Contractor must be able to research issues related to these hard to find problems.

Contractor agrees.

R4 Sometimes other vendors implement specific contact center technologies which are later supported by MiECC. Contractor must be able to consult and assist in evaluating proposals from other vendors for implementation of new technologies.

Contractor agrees.

R5 At the request of DTMB, assist/advise other State contact centers on joining enterprise contact center support from MiECC.

Contractor agrees.


150

7. Testing Requirements

# Detailed Requirement Comments T1 Contractor shall perform complete and

comprehensive system tests in accordance with the COTS software installation manuals and recommendations.

Contractor agrees.

T2 Contractor must be able to do regression testing and system integration testing to ensure the system operations.

Contractor agrees.

T3 Contractor must be able to perform volume testing and IVR load testing.

Contractor agrees to be able to perform volume testing and IVR load testing. Depending on level of effort and SEM guidelines, contractor may provide this service as part of mutually agreed upon SOW.

T4 Contractor will conduct a Performance Readiness Review (PRR), which is to commence a minimum of two weeks prior to any cut-over to a new production ready system, providing a period of overlap with the existing system. The PRR must demonstrate and simulate the full production environment.

Contractor agrees.

T5 Any deficiencies or defects found during the PRR must be corrected by Contractor prior to cut-over, unless otherwise accepted in writing by the State.

Contractor agrees.

8. Assistance of Infrastructure Upgrades Requirements

# Detailed Requirement Comments H1 Contractor must be able to assist in

replacing or upgrading existing hardware. Contractor agrees.

H2 Contractor must be able to port the application to the new hardware.

Contractor agrees.

H3 Contractor must be able to leverage the existing hardware to create enterprise hardware infrastructure.

Contractor agrees.

9. Major Enhancement requirements

# Detailed Requirement Comments N1 For major implementation requests during

the Contract period, the contractor will be provided a detailed statement of work by the agency and the contractor will provide a separate cost quote for each major implementation. The contractor will ensure that they identify the skilled resources and rate cards that would be used to complete these implementations.

Contractor agrees.

N2 Contractor must capture and document the contact center business requirements with input from State business and technical Subject Matter Experts.

Contractor agrees.


151

# Detailed Requirement Comments N3 Contractor must provide a detailed

description of the infrastructure requirements for the software proposed.

Contractor agrees.

N4 Contractor must assist with any infrastructure redesign effort.

Contractor agrees.

N5 Contractor must build the application design documents.

Contractor agrees.

N6 Contractor ensures the contact center software is developed meeting the business needs.

Contractor agrees.

N7 Contractor must provide training to the end users for new applications or changes in existing application

For SOW services, contractor agrees as agreed upon in SOW. For Base Support services, contractor agrees as mutually agreed upon with agency.

N8 Contractor will identify the need of training for COTS software applications.

Contractor agrees.


152

Attachment 3: Cost Tables The Project Cost summary, and all associated tables, Identify all information related, directly or indirectly, to the Contractor’s proposed charges for services and deliverables including, but not limited to, costs, fees, prices, rates, bonuses, discounts, rebates, or the identification of free services, labor or materials.

Table 1: Summary of the Project Cost No. Project Cost(s) Cost ($) Comments

Knowledge Transfer costGive breakdow n in Table 2

Base Service Cost

Breakdow n provided in Table 3

Major Enhancements costBreakdow n provided in Table 4

Total Project Cost $22,000,000.00C.

$11,751,184.60 5) This is only the provisional 'spend' budget for the nearly 84,000 hours of SoW work sought by the State6) Assumed equal spending of this effort over all 5 years of contract term7) Price absorbs COLA increases so that State is insulated from these variations

A.

0 1) Accenture is supporting all of the Contact centers in scope. No KT costs are charged to the State for these contact centers.

B.

$ 10,248,815.40 2) Per request, removed NICE support and IVR discretionary enhancement from scope. This is consistent with the level of support on the current contract. 3) Accenture had absorbed expense increases internally and has offered this price.4) Process efficiencies are incorporated in Y2 onwards of the term, to provide net reduction of base support costs to the State

Provisions:

10. If, after the Contract is signed, it is determined that information provided by the State of Michigan to the bidders is inaccurate or incomplete in any material manner, the parties will negotiate an adjustment in the project schedule and the fees and expenses, as applicable, per the Contract’s change order process.

11. Contractor’s fixed price is based on delivery of the fixed scope of services in Contract. The scope of the services as documented will remain unchanged, except as the parties may agree in writing. All other work, including schedule extensions not approved by Contractor (or within Contractor’s responsibility per the Contract), will require the parties to agree upon a change order to the Contract.

12. Contractor's performance of the Contract is dependent on the State of Michigan's prompt and effective performance of its responsibilities, including timely decisions and approvals.

13. The State of Michigan will commit resources and management involvement as described in the Contract or as required by the work effort in order to support Contractor’s delivery of the services and to perform the agreed upon acceptance procedures in a timely manner.

14. The State of Michigan will be responsible for its operation and use of Contractor’s deliverables upon acceptance, subject to applicable warranties and indemnities, if any, and for determining whether the services and deliverables provided by Contractor under the Contract, including any revised business processes implemented pursuant to the Contract, meet the State of Michigan's business requirements and applicable internal guidelines.

15. The State of Michigan will obtain all consents necessary from its third parties (i.e., those not under contract with Contractor) required for Contractor to perform its obligations under this Contract. The State of Michigan will be responsible for the contractual relationship with such third parties and for facilitating their cooperation with Contractor. Contractor will not have any responsibility for the performance of other contractors or vendors engaged by the State of Michigan (other than Contractor’s subcontractors) or delays caused by them. There are no third party beneficiaries to this Contract.

16. The State of Michigan will be responsible for obtaining, at no cost to Contractor, consents for Contractor’s use of any State of Michigan Furnished Property necessary to perform its obligations hereunder. Unless otherwise agreed to by the parties in writing, the State of Michigan will provide all software and hardware necessary for Contractor to perform its obligations under the Contract.


153

17. Each party will retain responsibility for its compliance with any laws, regulations, or other authorities, in effect on the date of submission of our proposal, including those areas on which it relies on the other party’s performance under the Contract.

18. Use of the term "ensure" is defined to mean that both parties will use all reasonable and commercial efforts to accomplish their legal responsibilities under the terms of the Contract.


154

Table 2: Knowledge Transfer cost There is no knowledge transfer cost as Contractor is already supporting this contract.

No.

Agency

Month 1

Month 2

Month 3

Total by agency

A. Civil Service Commission (MCSC)

$0 $0 $0 $0

D. DTMB-Client Service Center (CSC)

$0 $0 $0 $0

C. DTMB-Office of Retirement Services (ORS)

$0 $0 $0 $0

D. Environmental Quality (DEQ)

$0 $0 $0 $0

E. Human Services (DHS)

$0 $0 $0 $0

F.

LARA - Bureau of Health Professions (BHP)

$0 $0 $0 $0

G. State (MDOS)

$0 $0 $0 $0

H. Treasury

$0 $0 $0 $0

Total by month

$0 $0 $0 $0

Total Knowledge Transfer Cost, for 3 months (the sum of the column, Total by Agency)

$0 $0 $0 $0


155

Table 3: Base Service Cost

No.

Agency

Year 1

( 12 months)

Year 2

(12 months)

Year 3

12 months

Year 4

(12 months)

Year 5

(12 months)

Total 5 year

cost by agency

A. Civil Service Commission (MCSC)

D. DTMB-Client Service Center (CSC)

C.

DTMB-Office of Retirement Services (ORS)

D. Environmental Quality (DEQ)

E. Human Services (DHS)

F.

LARA - Bureau of Health Professions (BHP)

G. State (MDOS)

H. Treasury

Costs per year

2,049,763.08

2,049,763.08

2,049,763.08

2,049,763.08

2,049,763.08

Number of months in that year

12 12 12 12 12

Cost per month

170,813.59 170,813.59 170,813.59 170,813.59 170,813.59

Total Base Service Cost (sum of total 5 year cost by agency

10,248,815.4

0

Note: All prices are in US$.


156

Table 4: Rate Card

No. Staffing Category Firm Fixed

Hourly Rate Est. Hours (5 year total)

Extended Price (hourly rate X estimated hours)

Project Manager $ 181.00 500 $ 90,500.00

Systems Architect $ 145.00 500 $ 72,500.00

Business Analyst $ 138.00 7,500 $ 1,035,000.00

Siebel Lead $ 130.00 5,000 $ 650,000.00

Siebel Developer $ 113.00 16,000 $ 1,808,000.00


$ 167.00 5,500 $ 918,500.00

Genesys Specialist $ 267.00 5,000 $ 1,335,000.00

IVR Developer $ 113.00 14,000 $ 1,582,000.00

NICE Analyst $ 113.00 5,000 $ 565,000.00

Tester $ 152.00 5,000 $ 760,000.00

Other (Please specify) TBD

$ 150.00 19,564.56 $ 2,934,684.60

Total Major Enhancement Cost

$ 11,751,184.60

Notes: 5. Hourly rates quoted are firm, fixed rates for the duration of the contract. Travel and other expenses will

not be reimbursed. “Estimated Hours” and “Extended Price” are non-binding and will be used at the State’s discretion to determine best value to the State. The State will utilize the fully loaded hourly rates detailed above for each staff that will be used as fixed rates for responses to separate statements of work.

6. The State intends to establish funding for up to the estimated hours. Actual funding for enhancements

will occur on a yearly basis, and there is no guarantee as to the level of funding, if any, available to the project. The initial rate card funding will be $2 million, with additional amounts added as funding and needs are defined.

7. The parties agree that the Services/Deliverables to be rendered by Contractor using the future

enhancements/rate card on this Contract will be defined and described in detail in separate Statements of Work. Contractor shall not be obliged or authorized to commence any work to implement a Statement of Work until authorized via a purchase order issued against this Contract.

8. Other skills/roles suggested by the bidder should also show the hourly rate. The bidder can assume 0

hours for these skills for the purpose of computation.


157

Attachment 4: Personnel Requirements IT Classifications/Skills Sets & Tasks A complete list of the required IT Classification and skill sets is defined below. The overriding requirement is that the individual must possess the skills, knowledge, and experience required to perform the duties effectively and efficiently at the level specified in the contract. It is anticipated that the required experience and skill requirements will changed over the course of the contract. The contractor(s) will be notified in writing of these changes and will be required to provide personnel satisfying the experience and skill requirements, as modified, which includes skills sets which identifies knowledge of any future versions of software. Since it is anticipated that the skill sets will change over the course of the contract, additional skills sets may be defined and added to the contract. Assigned tasks will vary according to the specific project needs that exist at any time during the term of this contract. The number of development and maintenance projects will vary throughout the Contract period, as will the required tasks. The task to be performed by the Contract personnel include, but are not limited to those identified with each classification. Resources must comply with:

Regular reporting requirements Track time against project plans Ensure that all work conforms to State Uniform Information Technology Environment (SUITE), project

management, systems engineering methodology, and other IT standards in effect for DTMB agency services personnel.

The table below lists the IT classifications to be provided under this RFP.

IT Classification Project Manager (Service Delivery) Project Manager Systems Architect Business Analyst Siebel Lead Siebel Developer Computer Telephony Specialist Genesys Specialist IVR Developer NICE Analyst

IT Classification/Skill Sets Project Manager (Service Delivery)

Minimum 5 year experience of service delivery in shared IT services for multiple contact centers. Minimum 5 years experience in project management skills utilizing formal methodologies, including

change management, risk identification/mitigation, issue escalation and status reporting. PMP certification highly desired. 5 years experience in contact center IT projects, using Siebel and Genesys. 3-5 years experience with project management tools such as MS Project, NIKU/Clarity. Experience with CMM project methodologies Considerable knowledge of structured programming methodology and techniques. Must have experience with development projects utilizing Oracle or SQL Server


158

Ability to effectively make oral and written reports and presentations and prepare clear and concise metrics graphs and charts.

Ability to maintain records, prepare reports a conduct correspondence related to the work. Ability to communicate technical terminology at a level appropriate to the audience.

Project Manager (Service Delivery) Tasks: Manage all defined Contractor responsibilities in this Scope of Services. Manage and integrate end-to-end service delivery across all in-scope service lines. Monitor service delivery against predefined SLA and Return to Service goals listed in Attachment 1 Manage Contractor’s subcontractors, if any Develop the project plan and schedule, and update as needed Serve as the point person for all project issues Coordinate the design and delivery of system enhancements Coordinate and oversee the day-to-day project activities of the project team Assess and report project feedback and status Escalate project issues, project risks, and other concerns Review all project deliverables and provide feedback Proactively propose/suggest options and alternatives for consideration. Recommend enhancements

and identify value opportunities for the agencies. Utilize change control procedures Prepare project documents and materials Manage and report on the project’s budget

Project Manager

Minimum 5 years experience in project management skills utilizing formal methodologies, including change management, risk identification/mitigation, issue escalation and status reporting.

3-5 years experience with project management tools such as NIKU/Clarity, MS Project. PMP certification highly desired. Experience with CMM project methodologies Considerable knowledge of structured programming methodology and techniques. Experience desired in contact center IT projects, preferably Siebel and Genesys. Experience with development projects utilizing Oracle or SQL Server Ability to effectively make oral and written reports and presentations and prepare clear and concise

metrics graphs and charts. 2 years experience in verbal and written communication with clients in English Ability to maintain records, prepare reports a conduct correspondence related to the work. Ability to communicate technical terminology at a level appropriate to the audience.

Project Manager Tasks:

Define and develop integrated project plans for all aspects of assigned projects including scope, time, cost, communication, risk, procurement, quality and human resource areas, to meet the project goals and objectives.

Coordinate and direct the project team and the project team’s activities to deliver on-time, on-budget projects that meet customer requirements.

Practice Change Management, maintaining project scope and manage project changes to ensure changes are beneficial to the project and that the quality of the IT product meets customer requirements.

Apply configuration management and quality assurance techniques to assure correctness and completeness of project deliverables, including all project related documentation.

Communicate and coordinate with business clients, team members, external DTMB partners, vendors to meet project goals and objectives.


159

Assure project and product deliverable quality by adhering to standards, maintaining change control, providing quality control measurements, participating in quality audits and managing work results acceptance, including acceptance of vendor deliverables.

Provide project management products, i.e., information, status reports, presentations, etc., as required to business clients, team members and others.

Provide leadership to the project team, including development of team member roles and responsibilities, development of team members’ technical abilities where appropriate, and evaluation of team members’ performance.

Manage the introduction of the project’s product into implementation and provide support for transition into maintenance.

Manage and coordinate project close-out activities, including post-project implementation review, financial close-out, Contract close-out, records retention, etc.

System Architect

5 years experience in the Siebel administration.

Certified Oracle Siebel Consultant Expert highly desired.

5 years experience in technical design and implementation of Siebel solutions including architecture, infrastructure, interfaces, data architecture, access control, and security compliance.

Understanding of the fundamentals of various hardware components in a server based environment (servers, switches, routers, SAN, NAS) and communication protocols.

5 years experience with Oracle/SQL Server.

3 year experience of Genesys IVR implementation.

3 year experience in Siebel interfaces (Genesys CTI, FileNet etc.)

Experienced in centralized enterprise call recording and monitoring - 2 years experience in administration of NICE Perform 3.1 or above.

Experience in Java.

Experience in logical program and system design, project management methodology and change management methodology is desirable.

Ability to read, comprehend, and write technical documents related to the above technologies.

2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment

System Architect Tasks:

Design the solution and build the system architecture. Consult/assist in developing the solution. Develop, maintain and upgrade automated test scripts and architectures for application products. Document testing status – write test documentation, including test plans, test defects, and defect logs Configuration management of multiple development environments, Provide definition of support processes, technical documentation, 3rd party SW Upgrade management.

Define\maintain appropriate processes for the customer agency’s Infrastructure and Operations Support Services.

Suggest areas where process improvements and quality controls could be implemented, designed and documented.

Create\maintain clear and usable documentation for technical support activities performed by DTMB


160

Business Analyst 5 years experience analyzing business requirements for Siebel CRM, generating project specifications,

converting specifications into code, and applying knowledge of computer programming techniques and computer languages.

Oracle Siebel CRM Business Analyst certification highly desired. 5 years experience performing extensive analysis and design working on projects of all sizes that

require exposure to all aspects of the project life cycle and creating and maintaining documentation in conformance with established standards.

5 years experience working with application/solution architects to set direction of design and development for application development projects.

5 years experience evaluating user requests for new programs or modified program components to determine feasibility, cost and time required, compatibility with current systems, and computer capabilities.

5 years experience performing peer reviews of developed code to insure conformity to standards and design best practices.

5 years experience reviewing technical designs and specifications for completeness and conformance to quality standards, especially as a mentor to less experienced developers.

5 years experience analyzing business requirements, generating project specifications and converting them into code, and applying knowledge of computer programming techniques and computer languages.

5 years experience working with System Development Life Cycle (SDLC) concepts 5 years experience conducting system test 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment Experience in troubleshooting, problem solving and debugging. Ability to work under pressure and in tight dead lines.

Business Analyst Tasks: Analyze business requirements in Siebel CRM, generate project specifications, and develop technical

designs in consultation with other technical experts. Model Business Processes (As-Is and To-Be), Use Cases, Activity Diagrams, User and Functional

Requirements, Non-Functional Requirements; for requests related to Siebel CRM and CTI. Develop unit test plans, test data and scripts for application validation and verification. Perform extensive analysis and design working on projects of all sizes that require exposure to all

aspects of the project life cycle and creating and maintaining documentation in conformance with established standards.

Work with programmer analysts/developers to set direction of design and development for application development projects.

Evaluate user requests for new programs or modified program components to determine feasibility, cost and time required, compatibility with current systems, and computer capabilities.

Perform peer reviews of developed solutions and code to insure conformity to standards and design best practices.

Review technical designs and specifications for completeness and conformance to quality standards, especially as a mentor to less experienced developers.

Siebel Lead

5 years experience analyzing business requirements, generating project specifications, converting specifications into code, and applying knowledge of computer programming techniques and computer languages.

Certified Oracle Siebel Consultant Expert highly desired.


161


5 years experience developing technical designs in consultation with other technical experts. 5 years development experience in Siebel (including eServices) and Genesys CTI. 3 years development experience in one or more of the following areas:

Java/.NET/VB Web services Siebel FileNet interfaces.

5 years experience on one or more of the following development and design tools or equivalent; Serena Prototype Composer Microsoft Visio

5 years experience in RDBMS developing data model database triggers, procedures, packages and functions in a combination of any of the following: Oracle Microsoft SQL Server

5 years experience developing unit and system test plans, test data and scripts for application validation and verification.

5 years experience performing extensive analysis and design working on projects of all sizes that require exposure to all aspects of the project life cycle and creating and maintaining documentation in conformance with established standards.




5 years experience reviewing technical designs and specifications for completeness and conformance to quality standards, especially as a mentor to less experienced developers.


5 years experience working with System Development Life Cycle (SDLC) concepts 5 years experience conducting system test 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment Experience in troubleshooting, problem solving and debugging. Ability to work under pressure and in tight deadlines.

Siebel Lead Tasks:

Analyze business requirements, generate project specifications, and convert specifications into code, and develop technical designs in consultation with other technical experts

Code Solutions following technical design and apply knowledge of computer programming techniques and computer languages.

Develop unit test plans, test data and scripts for application validation and verification. Perform extensive analysis and design working on projects of all sizes that require exposure to all

aspects of the project life cycle and creating and maintaining documentation in conformance with established standards.

Work with application/solution architects to set direction of design and development for application development projects.


162

Evaluate user requests for new programs or modified program components to determine feasibility, cost and time required, compatibility with current systems, and computer capabilities.

Perform peer reviews of developed solutions and code to insure conformity to standards and design best practices.

Review technical designs and specifications for completeness and conformance to quality standards, especially as a mentor to less experienced developers.

Siebel Developer


3 years experience developing technical designs in consultation with other technical experts. 1 year development experience in Siebel. 1 year development experience in one or more of the following areas:

Genesys CTI Java/.NET/VB Web services Siebel FileNet interfaces


3 years experience in RDBMS developing data model database triggers, procedures, packages and functions in a combination of any of the following: Oracle Microsoft SQL Server

3 years experience developing and following unit test plans, test data, and scripts for application validation and verification.

3 years experience performing extensive analysis and design by working on projects of all sizes that require exposure to all aspects of the project life cycle and creating and maintaining documentation in conformance with established standards.



3 years experience developing solutions, following design documents and use cases 3 years conducting unit test 3 years experience performing peer reviews of developed code to insure conformity to standards and

design best practices. 3 years experience reviewing technical designs and specifications for completeness and conformance

to quality standards. 3 years experience working with System Development Life Cycle (SDLC) concepts 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment Experience in trouble shooting, problem solving and debugging Ability to work under pressure and tight deadline


163

Computer Telephony Specialist 2 year experience working with Avaya PBX API’s most notably AES.

Understanding of the fundamentals of the telephone switches and communication protocols.

Experience with both Avaya and Cisco PBX components, programming and general telephony feature capabilities.

Understanding of Avaya Vector Programming CTI commands. Education and experience working with Telephony Time Division Multiplexing (TDM) facilities and their

integration to Dialogic interface boards. Education and experience working with Session Initiation protocol (SIP), SIP Trunks and their interface

to IVR Servers, and/or Media Gateway Servers. Education and Experience working with Cisco Telephony API’s for CTI




Computer Telephony Specialist Tasks:

Design the solution and build the system architecture. Develop, maintain and upgrade design documents, test scripts, test documentation and architectures

for application products Provide definition of support processes, technical documentation, 3rd party SW upgrade management.



Create\maintain clear and usable documentation for technical support activities performed by DTMB Genesys Specialist

5 years experience in Genesys solutions planning, implementation, configuration and maintenance. Understanding of Genesys T-Server messaging and its integration to the Telephony environment.

5 years experience in the Genesys IVR implementation.

Genesys Certified System Consultant (Inbound voice routing or GVP) highly desired.

Understanding of the fundamentals of the telephone switches and communication protocols.

3 year of development experience in the following areas: Genesys Enterprise Routing Strategy development, implementation, troubleshooting,

maintenance and optimization. Genesys Framework configuration, modification and maintenance. Genesys Reporting solutions and their specific configuration to a customer’s routing solution

and IVR application.

3 years experience in one or more of the following areas. Java/.NET Web services VXML

Education and Experience in the integration of Genesys solutions components to different customer premise telephony equipment (CPE) and media types. Strong emphasis on Avaya and Cisco (CPE).


164

Experience with both Avaya and Cisco PBX components, programming and general telephony feature capabilities.

1 year experience working with Avaya PBX API’s most notably AES. Strong skills and knowledge in utilization of Time Division Multiplexing (TDM), Session Initiation

Protocol (SIP), SIP trunks and their interface to IVR Servers, and/or Media Gateway Servers.




Genesys Specialist Tasks:

Design the solution and build the system architecture. Develop, maintain and upgrade design documents, test scripts, test documentation and architectures

for application products Configuration management of multiple development environments, Provide definition of support processes, technical documentation, 3rd party SW upgrade management.



Create\maintain clear and usable documentation for technical support activities performed by DTMB IVR Developer


3 years experience developing technical designs in consultation with other technical experts. 1 year experience of developing call flow diagrams and building IVR solutions. 1 year development experience in Genesys and its reporting tools. 1 year development experience in one or more of the following areas:

Java/.NET Web services VXML






3 years experience developing solutions, following design documents and use cases 3 years conducting unit test


165


3 years experience reviewing technical designs and specifications for completeness and conformance to quality standards.

3 years experience working with System Development Life Cycle (SDLC) concepts 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment Experience in trouble shooting, problem solving and debugging Ability to work under pressure and tight deadline.

NICE Analyst


3 years experience developing technical designs in consultation with other technical experts. 3 year experience in centralized enterprise call recording and monitoring. 1 year experience of NICE Perform 3.1 or above. 3 years experience on one or more of the following development and design tools or equivalent:

Serena Prototype Composer Microsoft Visio





3 years experience developing solutions, following design documents and use cases 3 years conducting unit test 3 years experience performing peer reviews of developed code to insure conformity to standards and

design best practices. 3 years experience reviewing technical designs and specifications for completeness and conformance

to quality standards. 3 years experience working with System Development Life Cycle (SDLC) concepts 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment Experience in trouble shooting, problem solving and debugging Ability to work under pressure and tight deadline

NICE Analyst Tasks:

Manage, coordinate and administer where necessary the implementation of NICE Recording platforms, their expansion and any programming modifications associated with telephony interface changes.


166

Develop, maintain and upgrade design documents, test scripts, test documentation and architectures for application products

Provide System Administrative programming and design support for new user IP address, stations and CTI interfaces.

Provide System Administrative programming and design support for database integration additions, modifications and removals.

Provide definition of support processes, technical documentation, 3rd party SW upgrade management.



Create\maintain clear and usable documentation for technical support activities performed by DTMB


167

Attachment 5: Resume Template The Contractor must complete and submit Résumés for:

Single Point Of Contact (SPOC) Project Manager - Service Delivery System Architect Siebel Lead Genesys Specialist Non Key Personnel

The Contractor must use the Résumé Summary Templates provided in this attachment. Résumés for these Personnel should not exceed four (4) pages each in length. Resumes for all key positions must be provided with relevant skills, experience, and references provided. The State may evaluate such criteria as time spent by the personnel directly supporting the proposed solution, and comparable size, scope and complexity of implementations accomplished. The Contractor must submit a Letter of Commitment for the key personnel who will be assigned to the Contract, signed by the identified resource, stating their commitment to work for the contractor on this project contingent. If the identified personnel are currently assigned to a State project the contractor must provide a letter signed by the State Program Manager releasing the individual from the project upon execution of the contract


168

Proposed Resource Name:

Proposed Classification: A. Single Point of Contact

Key Personnel: Yes or No

If resource is associated with a subcontractor provide name of company:

Percentage of time resource will be allocated to project:

Bidder: List the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role. Provide the name of the project(s) and the year(s) the experience was obtained. The experience requirements detailed in Attachment 4 are restated as follows:

Required Skills Bidder’s Response 5 years supporting customers and contractual obligations, facilitating dispute resolution, and advising clients of performance under the terms and conditions of the Contract.

Does resource have this required skill: Yes or No Description of skills and experience: Example: 10 yrs. exp with (vendor name) implementing multimillion-dollar, statewide implementations of intelligence management and analysis systems Name of project(s) and year(s) experience was obtained: Example: Michigan Infinity Project – 1995 to 1998 Ohio Intelligence Center Project – 1998 to present

At least 5 years experience in reviewing project plans, reporting on status and issues of projects, coordinating access to facilities and necessary resources needed for delivery of services, facilitate coordination between various external contractors departments/divisions, escalate outstanding/high priority issues and

document and archive all important project decisions.

Does resource have this required skill: Yes or No Description of skills and experience: Name of project(s) and year(s) experience was obtained:

Education: BS degree Computer Science or equivalent work experience

Does resource have this required skill: Yes or No If education is based on previous work experience, please elaborate that work experience.


169

List client references for work performed to meet the requirements stated above, and all projects the proposed resource has worked on in the last three (3) years. A minimum of three (3) references are required. By submission of this information, the bidder and identified key person authorize the State of Michigan to contact references and previous employers provided to verify the accuracy of the information. Provide the identified information for each: Start Date: date started on project End Date: date rolled off project Client/Project: Client, with contact information (i.e.: address, phone #s , and email address), and project name Employer: identify employer at the time of experience Title/Percentage of time: title of role on project and percentage of time spent on project Description: brief description of responsibilities for the project. Include software version Start Date: End Date: Client/Project: Employer: Title/Percentage of time: Description: Start Date: End Date: Client/Project: Employer: Title/Percentage of time: Description: EDUCATION

Education Degree (i.e. PhD, Master’s, Bachelors)

Example: Master in Engineering Year Completed: 1998

Program Major(s) area of study: Computer Science

University (include address)Example: MSU – East Lansing, Michigan

Additional Education Degree (i.e. PhD, Master’s, Bachelors)

Example: Bachelors’ in Business Administration

Year Completed: 1994

Program Major(s) area of study: Example: Management

Minor area of study: Example: Economics

University (include address) Example: Central MI University, Mt. Pleasant, MI TRAINING – Provide any relevant technical or professional training related to the role resource will be providing on this project.

Technical or Professional Training Course Name Topic (include credit hours if applicable) Date taken

Certifications/Affiliations Name Topic/Description Date completed


170

The Bidder must submit a letter of commitment for Key Personnel, signed by the identified resource, stating their commitment to work for the bidder/subcontractor on this project contingent on award of the bid. If the identified personnel are currently assigned to a State project the bidder must provide a letter signed by the State Project Manager releasing the individual from the project.


171


Proposed Classification: B. Project Manager - Service Delivery




Bidder: List the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role. Provide the name of the project(s) and the year(s) the experience was obtained.

The experience requirements detailed in Attachment 4 are restated as follows:

Required Skills Bidder’s Response Minimum 5 years experience in Seibel/Genesys project management skills utilizing formal methodologies, including change management, risk identification/mitigation, issue escalation and status reporting.

Does resource have this required skill: Yes or No

Description of skills and experience: Example: 5 yrs exp with (vendor name) implementing multimillion-dollar, statewide implementations of Siebel/Genesys call center.

Name of project(s) and year(s) experience was obtained: Example: Michigan CSIP project 2003-2008.

3-5 years experience with project management tools such as NIKU/Clarity, MS Project, and experience with CMM project methodologies.


5 years supporting customers and contractual obligations, facilitating dispute resolution, and advising clients of performance under the terms and conditions of the Contract. Ability to effectively make oral and written reports and presentations, and prepare clear and concise metrics graphs and charts.


Experience with development projects utilizing Oracle, DB2 or SQL Server database. Considerable knowledge of structured programming methodology and techniques.


Education: BS degree in Computer Science or equivalent work experience.


Desired Certification: Project Management Professional (PMP)

Does resource have this desired skill: Yes or No If yes, provide copy of certification.


172















173



174


Proposed Classification: C. System Architect





Required Skills Bidder’s Response

5 years experience in the Siebel administration. 5 years experience in technical design and implementation of Siebel solutions including architecture, infrastructure, interfaces, data architecture, access control, and security compliance. Understanding of the fundamentals of various hardware components in a server based environment (servers, switches, routers, SAN, NAS) and communication protocols. 5 years experience with Oracle/SQL Server.


3 year experience of Genesys IVR implementation. 3 year experience in Siebel interfaces (Genesys CTI, FileNet etc.) Experienced in centralized enterprise call recording and monitoring - 2 year’s experience in administration of NICE Perform 3.1 or above.


Experience in Java. Experience in logical program and system design, project management methodology and change management methodology is desirable.



175

Ability to read, comprehend, and write technical documents related to the above technologies. 2 year’s experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications. Experience working with project management tools such as MS Project or NIKU Experience working in a team environment


Education: BS degree in Computer Science or equivalent work experience


Desired Certification: Certified Oracle Siebel Consultant Expert.

Does resource have this desired skill: Yes or No If yes, provide copy of certification


176















177



178


Proposed Classification: D. Siebel Lead





Required Skills Bidder’s Response 5 years experience analyzing business requirements, generating project specifications, converting specifications into code, and applying knowledge of computer programming techniques and computer languages. 5 years experience developing technical designs in consultation with other technical experts.


5 years development experience in Siebel (including eServices) and Genesys CTI. 3 years development experience in one or more of the following areas:

Java/.NET/VB Web services Siebel FileNet interfaces.

5 years experience on one or more of the following development and design tools or equivalent:

Serena Prototype Composer Microsoft Visio

5 years experience in RDBMS developing data model database triggers, procedures, packages and functions in a combination of any of the following:



179

Oracle/Microsoft SQL Server 5 years experience developing unit and system test plans, test data and scripts for application validation and verification. 5 years experience performing extensive analysis and design working on projects of all sizes that require exposure to all aspects of the project life cycle and creating and maintaining documentation in conformance with established standards. 5 years experience working with application/solution architects to set direction of design and development for application development projects.


5 years experience evaluating user requests for new programs or modified program components to determine feasibility, cost and time required, compatibility with current systems, and computer capabilities. 5 years experience performing peer reviews of developed code to insure conformity to standards and design best practices. 5 years experience reviewing technical designs and specifications for completeness and conformance to quality standards, especially as a mentor to less experienced developers. 5 years experience analyzing business requirements, generating project specifications and converting them into code, and applying knowledge of computer programming techniques and computer languages.


5 years experience working with System Development Life Cycle (SDLC) concepts. 5 years experience conducting system test. 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies




Desired Certification: Certified Oracle Siebel Consultant Expert

Does resource have this desired skill: Yes or No If yes, provide copy of certification


180















181



182


Proposed Classification: E. Genesys Specialist





Required Skills Bidder’s Response 5 years experience in Genesys solutions planning, implementation, configuration and maintenance. Understanding of Genesys T-Server messaging and its integration to the Telephony environment. 5 years experience in the Genesys IVR implementation.


Understanding of the fundamentals of the telephone switches and communication protocols. 3 year of development experience in the following areas: Genesys Enterprise Routing

Strategy development, implementation, troubleshooting, maintenance and optimization.

Genesys Framework configuration, modification and maintenance.

Genesys Reporting solutions and their specific configuration to a customer’s routing solution and IVR application.

3 years experience in one or more of the following areas.

Java/.NET Web services VXML



183

Education and Experience in the integration of Genesys solutions components to different customer premise telephony equipment (CPE) and media types. Strong emphasis on Avaya and Cisco (CPE). Experience with both Avaya and Cisco PBX components, programming and general telephony feature capabilities. 1 year experience working with Avaya PBX API’s most notably AES. Strong skills and knowledge in utilization of Time Division Multiplexing (TDM), Session Initiation Protocol (SIP), SIP trunks and their interface to IVR Servers, and/or Media Gateway Servers. Experience in logical program and system design, project management methodology and change management methodology is desirable.


Ability to read, comprehend, and write technical documents related to the above technologies. 2 years experience in verbal and written communication with clients in English Experience working with mature CMM or CMMI project methodologies Experience working with MS Office applications Experience working with project management tools such as MS Project or NIKU Experience working in a team environment




Desired Certification: Genesys Certified System Consultant (Inbound voice routing or GVP).

Does resource have this desired skill: Yes or No If yes, provide copy of certification.


184















185



186


Proposed Classification: Non-Key Personnel (Specify Role)





Skills Bidder’s Response

<<Bidders should fill in the skills required from Attachment 4>>







Certification: Does resource have this skill: Yes or No If yes, provide copy of certification


187















188

Attachment 6: List of Approved Subcontractors

The following represent the list of Subcontractors approved by State for use under this Contract:

Empirix, Genesys, and Actium Consulting.


189

Attachment 7: Preliminary Work Plan

The Contractor submits the following Preliminary Work Plan per requirements set forth in Section 1.301 Project Plan Management:


190

Attachment 8: Agency Background Information

Agency Background – in alphabetical order Civil Service Commission Background This service center has approximately 30 Customer Service Representatives (CSRs) and was established in August 2004 to service State employees with specific Human Resource (HR) issues. It consists of a 1-800 telephone service center receiving up to 500 calls per day and an Internet knowledge base. CSRs answer telephone inquiries by guiding the employee to relevant pages on the knowledge base or by accessing the Civil Service HRMN legacy system. If the CSR is unable to resolve the inquiry on the phone, a detailed service request is created which is then passed to a Subject Matter Expert (SME). The SME will work the case and call the employee back with the resolution. Operation a. Phone CSRs staff the contact center Monday to Friday 7.00am to 6.00pm. Employees calling into the contact center are initially presented with several telephone menu choices. The contact center uses computer telephone integration (CTI) wherein employees may enter their employee ID or social security number and using Genesys the information is passed as a screen pop to the CSR in Siebel with the employee information contact log auto populated. Incoming callers who identify themselves as wanting employment verification, are in need of self service support, or are retirees of the State of Michigan will select those options and that will auto populate in Siebel with a predefined customer contact number. The CSR records the primary and secondary reason for the inquiry and, if necessary, creates a Siebel Service Request before closing the call. CSRs can also access the web knowledge base during the phone call to help answer the employee’s inquiry. b. Web Employees access the knowledge base site using the Internet and login by entering their user name and password, which has been supplied to them through a separate process. The resultant displayed content has been tailored to match the specific details of the employee’s bargaining group or agency. c. Paper Channel - Inbound CSRs in the contact center process up to 400 inbound documentation and correspondence items per day when not answering the phones. This is currently a manual process in which correspondence is batched and distributed to CSRs who answer the inquiries and where necessary update the legacy system. Completed transactions are tracked using a Microsoft (MS) Access database that in turn is used to automatically generate an email to State of Michigan employees notifying them that their paper transaction was received and completed. Documentation and correspondence are sent out for scanning, and uploaded for viewing by CSR’s in FileNet. d. Paper Channel - Outbound MI HR Service Center sends several hundred outbound letters per day. Using several different methods of generation these letters provide benefit enrollment or document compliance information to employees. e. Email The MI HR Service Center processes approximately 500 emails from three email sites. Auto acknowledgements are sent and then emails are captured and worked through the Siebel application using a series of predefined responses. Contact logs are generated in Siebel for each email sent and received. Quality Assurance Call monitoring and quality assurance is provided by the NICE software which captures and archives both voice and screen data. Calls are statistically sampled, evaluated and reviewed with staff by a supervisor. A


191

series of quality assurance reports are run by team, question and CSR to trend short and long range performance and to identify areas where training may be required. CSRs also have the option of recording calls on demand. Data entry on transactions is audited manually by quality assurance analysts. Each day a standard percentage of each CSR’s batch work is pulled audited and reviewed. Statistical reports are run by week, month year to identify areas of concern and improvement. Customer Satisfaction MI HR Service center utilizes the Siebel activity log to generate an email to employees immediately following contact with the service center. This email requests that employees take the time complete a brief customer satisfaction survey by clicking on the embedded link. Satisfaction scores, comments, and reports are generated monthly and provide information by employee, CSR, and over response rate. Reports Management reports in MS Excel are produced using extracted data from the Avaya CMS system and the Qwest 1-800 provider web site. Key metrics used by management include the Average Speed of Answer (ASA), Abandon Rate in the queue and Average Talk Time. In addition, there are several manual spreadsheet reports that track a variety of contact center statistics on productivity, accuracy and completion rates. Future Strategy a. Utilize Siebel and FileNet workflow to route, work, and track transaction documentation throughout their

lifecycles. b. Leverage technology to generate automated reminders to employees who need to submit supporting

documentation. c. Leverage the current implementation of electronic document management capacity to enable the

agency to handle additional paper based processes and correspondence with a greater level of efficiency both within MIHR and across the Commission.

d. The current system uses basic implementations of IVR and CTI. Civil Service would like to expand and enhance implementation of these technologies where cost benefit analysis indicates increased value.

e. Upon request, resources able to perform a cost/benefit analysis for extending the Siebel application to other groups within Civil Service should be included as a part of in-scope Minor Enhancements (see Section 1.104 I A - Base Support). This may be classified as a major implementation depending on the scope.

DTMB-Client Service Center (CSC) Background This service center has approximately 30 Customer Service Technicians/Representatives and was established at the creation of MDIT to service State employees with IT issues. It consists of a 1-800 telephone contact center receiving between 600 and 1,800 calls per day. Technicians answer telephone inquiries by first verifying Client information and entering the nature of the call in the Remedy system. Technicians leverage a SharePoint site to adhere to procedures and established analysis techniques. If a technician is unable to resolve the inquiry on the phone, a transfer to a Subject Matter Expert (SME) may be appropriate prior to the call ending. If the nature of the call warrants a visit from an onsite technician, then the detailed work order is assigned to Field Services for follow-up. DTMB-CSC is presently implementing a Genesys CTI solution with IVR self-service, CTI routing and soft phone equipment. Operation a. Phone Technicians staff the contact center 7 days a week, 24 hours a day. Employees calling into the contact center are initially presented with several telephone menu choices, one of which provides a self-service


192

opportunity for Network Password re-sets. The menu choices define the nature of the call, which is then routed to an available technician with the corresponding skill set. This contact center has computer-telephone integration screen pops, so the technician on receiving the call is presented with the State employee’s identification number and can retrieve the employee’s contact information based on the employee id. The technician records the primary reason for the inquiry and, if able remediates the incident, and creates a Remedy Service Request before resolving the call or transferring it to an SME. Technicians can also access the SharePoint knowledge base during the phone call to help answer the employee’s inquiry. b. Intranet Employees access the SharePoint knowledge base site using the Intranet. Automated Password Re-sets The caller can choose selections which allow for automated password re-set of the caller’s network password. Verification occurs via a previously arranged PIN number held in a secure Challenge Response System, CRS. If the caller successfully enters the PIN, then authorization to re-set the password is sent to Active Directory for the re-set and the transaction is recorded in a Remedy Service Request. Quality Assurance Calls are statistically sampled, evaluated and reviewed with staff by a supervisor. A series of quality assurance reports are run by team and long range performance areas are identified where departmental training may be required. Customer Satisfaction Phone customers are emailed a link to a customer satisfaction survey on the State of Michigan web site where they are asked to answer some questions. Responses are analyzed by the service center management and a quality report created. Reports Management reports in MS Excel are produced using extracted data from the Avaya CMS system, only at this writing. Key metrics used by management include the Average Speed of Answer (ASA), Abandon Rate in the queue and Average Talk Time. In addition, there are several manual spreadsheet reports that track a variety of contact center statistics on productivity, accuracy and completion rates. DTMB – Office of Retirement Services (ORS) Background The Michigan Office of Retirement Services has approximately 54 Customer Service Representatives (CSRs) that field approximately 250,000 calls per year. The contact center services members of 4 Retirement Systems – Michigan Public Schools Retirement System (MPSERS), State Employees Retirement System (SERS), State Police Retirement System (SPRS) and the Judges Retirement System (JRS). Calls are routed through a 1-800 number to the consolidated contact center. Operations a. Phone CSRs staff the contact center Monday to Friday 8:30am through 5:00pm. Customers calling the contact center are prompted to enter member identification and are then presented with several menu choices through the Genesys IVR. The choices selected, in combination with the type of account represented by their entry, then determine how that call is routed to agents through Genesys Skills Based Routing. Skills Based Routing allows for the assignment of agent availability for several Genesys virtual queues. As agents receive appropriate training, they are assigned skill levels for each virtual queue. When a caller is routed based on the criteria listed above, the Genesys strategy then routes the call to the next available agent with the highest skill level in that queue area.


193

b. Web Currently there is no direct link between the contact center applications. CSR staff use the state website to assist with answering customer questions. c. Paper Channel CSRs can initiate tickets between the Siebel application and the retirement main line of business application known as Clarety. Unrelated to the contact center technology, CSRs also process inbound correspondence and transactions that are generated in Clarety and FileNet. d. Message Board CSRs also respond to message board requests through the member self-service application known as miAccount. This is a secure message board that allows authenticated users to get specific account information securely through the web. This information is not currently linked to the Siebel implementation, but this is a future enhancement that ORS would like to implement. Quality Assurance Call monitoring and quality assurance is provided by the NICE software. Calls are statistically sampled, evaluated and reviewed with staff by a quality analyst or supervisor. While screen capture calls are randomly sampled, audio is captured for every call. Environment Quality Background The Department of Environmental Quality, Office of Environmental Assistance (OEA) has three customer service representatives in the Environmental Assistance Center (EAC) which serve collectively as a single point of contact into the Department of Environmental Quality (DEQ) and the Department of Natural Resources (DNR). The public can contact the DEQ and DNR via a toll free telephone number and/or electronic mailbox. The EAC provides fast, direct, one-on-one assistance and, if needed, referral to an OEA program specialists or DEQ/DNR program staff within the regulatory divisions. The contact center provides critical navigation support and is an integral component of the DEQ day to day compliance assistance and pollution prevention efforts. The EAC offers a direct pubic resource by linking callers to the correct DEQ and DNR staff and resources to answer their questions, facilitate voluntary compliance and pollution prevention activities, and enhance natural resource use and management decisions geared at maintaining, enhancing, protecting and preserving the environment and human health. The contact center averages about 19,000 calls per year and the peak “season” is March through October. Operation Customer service representatives within the EAC are available Monday through Friday from 8:00 am to 4:30 pm. People calling into the contact center are presented directly to a customer service representative unless all lines are in use, in which case they hear a recorded message for 2 minutes and are prompted to leave voice mail if desired. The EAC staff log in caller inquiry information and search system program, contact, and county assignments to direct inquiries to the DEQ and DNR staff assigned to handling the topic or program in the caller’s geographic area. The system also serves to track resolution of the call and has a knowledge base that is provides a knowledge resource for system users to answer frequently asked questions. The system has two tiers of users: the EAC customer service representatives and the OEA program specialists. The EAC can resolve or assign inquiries to OEA specialists. When a call is directed to regulatory program staff person, EAC staff closes and resolves the inquiry. Quality Assurance Due to the small size of the contact center, computerized call monitoring is not necessary for evaluating the quality of the service. System reports are generated to evaluate the quality of the services provided and the quality of data entry. Customer Satisfaction


194

Inquiries prompting an e-mail response provide customers with a link to complete a customer satisfaction survey. The system also allows system users to enter in positive or negative feedback for all inquiries along with specific details regarding the customer’s feedback on the level of service provided. Reports Management reports are scheduled monthly and are used to generate DEQ metrics. The reports identify the type and number of inquiries, whether the DEQ response was timely, positive and negative customer feedback received, and the sectors serviced through the contact center. Human Services Background The Michigan Department of Human Services (DHS) provides client self-service capability that supports online application for the Food Assistance and Low Income Home Energy Assistance Program (LIHEAP) State Emergency Relief. This web front-end (MI Bridges) captures client information and posts to the Bridges eligibility system for processing and final determination. Clients can also use a telephone based Interactive Voice Response (IVR) system to check on the status of a food assistance filing, and other details like their upcoming appointments, Case Worker information, pending verification details. In summary, Michigan currently offers these online services as part of the Bridges self-service module in both English and Spanish. Currently Interactive Voice Response system (IVR) receives 4,500 plus calls daily. Michigan Department of Human Services is expanding existing MI Bridges functionality both online and IVR functionality by adding more programs like Cash Assistance, Medical Assistance, Child Development and Care and State Emergency Relief (SER) (Energy and Non Energy) assistance programs by the end of September 2011 in English and Spanish. IVR system will also be available in Arabic by the end of March 2012. It is expected that daily call volumes will go up at least by two to three folds.

Vision Provide timely and accurately program benefit status along with other details to their users. Values Customer Focus Continuous Service Improvement Service and Proficiency

Operation a. Telephony Gateway Infrastructure: Users can call 1-800 telephone number to access the MiBridges IVR system. Using Genesys 8.1 Integration and Reporting and advanced routing IVR is capable of handling 84 concurrent calls. The maximum number of consecutive calls is limited to the eight inbound T1’s. It also uses Nuance TTS to convert text to speech; for example the benefit amount of an individual is always dynamic in nature and differs person to person. This amount is retrieved from the database and converted to a sound for playback.

The Telephony Gateway Infrastructure consists of: I. Telephony Provider (Qwest)

II. Gateway III. IVR Servers IV. IVR Management Server V. IVR Reporting Server

A call flows from the Telephony Provider (Qwest) to the IVR Server through the Gateway. IVR Servers are controlled by the Management Server. Reporting Server takes inputs from the IVR Application and the IVR Servers and reports the same in a user readable format. b. Web Channel


195

Michigan Department of Human Services Clients can log on to the MiBridges Internet website and can create their login accounts and password to view their benefits and other details like pending verifications, upcoming appointments, status of their submitted applications, previous two months and one future month benefit details, their available correspondences (expected September 2011), also they can report any changes (expected December 2011) related to address, income etc. Quality Assurance Since this is a complete automated process, these calls are not handled through any contact centers or customer service representatives. No features like call sampling and recording. Reports Management reports in PowerPoint are produced daily using extracted data from Genesys Reporting server. During the expansion process these reports will be generated automatically using existing Bridges Reporting procedure. Licensing and Regulatory Affairs - Bureau of Health Professions Background: The Department of Licensing and Regulatory Affairs – Bureau of Health Professions Licensing Division operates a contact center for Health Professionals. The contact center staff has approximately five (5) agents and is primarily responsible for issuing Health Professionals licenses. The customer inquiries can originate from a variety of channels (phone, internet, email, and white mail correspondence). The contact center services approximately 500 calls per day. Operations: Phone- Basic Siebel Contact center Application with Genesys Voice Portal (GVP) Interactive Voice Response System (IVR) using a 1-800 telephone service. Quality Assurance (Future): Call monitoring and quality assurance as provided by the NICE software. Customer Satisfaction (Future): Provide email link to a customer satisfaction survey on the State of Michigan web site with responses analyzed by service center management and creation of a quality report. Reports (Future): The contact center will use Genesys CCPulse for real time reporting. State (MDOS) Background The Michigan Department of State has approximately 70 CSRs and began a project in August 2005 to consolidate their telephone contact centers. By the end of September 2006, public calls made to branch offices, regional contact centers or the information center all route through a 1-888 number to a consolidated contact center. Calls from branch office staff route through a separate 1-877 number. The public line is staffed from 8:30AM to 5:00PM, Monday through Friday. The branch office line is staffed from 8:00am to 5:30pm, Monday, Tuesday, Thursday and Friday; 9:00am to 7:30pm on Wednesday; and 9:00am to 12:30pm on Saturday. Operations a. Phone Channel The contact center receives an average of 11,000 calls a day and utilizes customer service representatives located in two geographically separate locations. Citizens are offered an opportunity for self-service


196

through the IVR and also have the option of speaking to a CSR. The CSRs are divided into three main groups: tier 1, tier 2 and tier 3, with each agent having a specific skill set stored in Genesys. Calls are routed to agents based on that skill set. However, in the main, tier 1 agents will get all initial calls from citizens unless there is a pre-existing service request on file or the customer is identified as a driver assessment customer by the IVR, in which case the citizen will be immediately directed to a tier 2 agent. Tier 2 agents also get all calls that cannot be answered by a tier 1 agent. Tier 3 agents solely handle phone calls from staff at the branch offices. There is a separate phone channel for staff located at branch offices allowing these calls to by-pass the main IVR and be routed directly to a tier 3 CSR. All citizens wishing to speak to an agent will be asked for their Drivers License Number in the IVR and this is used to screen pop their personal identification information from the Siebel database and their contact log history on to the CSRs screen when the call is connected. The IVR and Genesys CTI determine the nature of the call and route the caller to the most appropriate, available, skilled agent using call routing strategies. Note: A similar screen pop function is also in place for vehicle registrations; however this functionality is currently turned off due to the inability of the speech recognition application to reliably and accurately identify alpha characters spoken by the caller.

All branch office staff will enter their employee number as well as a branch identifier at an Avaya prompt and this will be used by Genesys to screen pop the appropriate records when a tier 3 agent answers the call.

b. Web Channel Branch office employees can log on to a Siebel eService application through an Intranet connection. They will login with a user name and password allowing them to create a service request or review progress on previous service requests. New service requests will result in receipt of an auto-acknowledgement and an instruction to visit the web site in a specified number of days for an answer. This service has also been made available to the MDOS Traffic Safety Division/Admin Hearing Section in the MDOS Legal and Regulatory Services Administration.

Reports The contact center will use Genesys CCPulse for real time reporting. Monthly Siebel Actuate reports show the Service Request performance of the contact center. However, the Siebel Actuate reports are not currently being used by MDOS contact center management.

Future Strategy a. Quality Assurance The contact center would like to implement NICE call monitoring and quality assurance. In order to minimize costs, the agency would like to look at the possibility of leveraging the existing State NICE implementations.

b. Enhanced IVR When MDOS implemented a Genesys-based IVR menu on its toll-free public line, the contractor at the time recommended that MDOS move the old Octel based menu structure into the IVR as is and then revamp/rewrite the menu system at a later date. The rewrite was never done and current menu structure is cumbersome for customers causing many to opt out of the system and speak with a customer service representative. Enhancing the IVR to make it more streamlined and user friendly is needed. Additionally, MDOS would like to explore incorporating the Record Lookup Unit ECP into the IVR to provide for a more efficient and cost effective system

c. Citizen Self Service over the Web MDOS would like to consider the possibility of opening up web access for citizens. This might include allowing citizens to create their own service requests and then be able to revisit the site to retrieve the responses.

d. Expansion of Siebel to Other Divisions in Agency


197

There may be opportunities for other divisions to use the Siebel product. This could include other contact centers that could use the current application with the addition of some new roles and responsibilities and other areas where a new configuration is required.

e. White Mail MDOS would like to consider enhancement of the system for the addition of a white mail channel for managing incoming correspondence the same as other customer contacts, utilizing an imaging component such as FileNet. This was a feature that MDOS wanted to have included in its original contact center design but was postponed for budgetary reasons. However, MDOS is currently scanning some of the white mail and attaching to Siebel service requests.

f. Knowledge Management Base MDOS wants to expand and build upon the knowledge base being built into its initial contact center design, to add searchable documents and other resources and content, for its CSRs and other agency employees as well.

g. Virtual Hold MDOS would like to consider incorporation of Virtual Hold technology (or a similar application) to improve the customer’s experience when wait times become high. This technology would allow a customer to hang up the phone while still maintaining their place in the phone queue. When the caller gets near the top of the queue the system places an outbound call to the individual and directs them to the next available service representative.

The MDOS Consolidated Contact Center has primary goals of maximizing customer service with the use of a single toll-free line for channeling all incoming calls, while reducing wait times, and providing more timely, accurate information with a higher rate of first call resolution. A secondary goal is to provide this better service in an efficient and cost-effective manner, offering convenient options for customer self-service wherever possible. MDOS is also looking toward continuous improvement, with an eye toward adding future enhancements that will improve the customer’s experience when contacting MDOS by phone.

Treasury

Background The Treasury Customer Contact Division provides the contact point for taxpayers seeking account specific information and answers to Michigan tax questions. The division has a vision and values statement:

Vision Provide superior customer service to taxpayers.

Values Customer Focus Continuous Service Improvement Staff Quality, Service and Proficiency

Treasury has over 200 users. The Customer Contact Division operates a multi-channel contact center managing phone, IVR, email, web, inbound correspondence and certain outbound correspondence. It includes an on-site imaging and indexing operation. Customers are business and individual income taxpayers

The Michigan Guaranty Agency (MGA), also part of the Department of Treasury, administers the Federal Family Education Loan Program (FFELP) which includes the Subsidized Federal Stafford Loan Program, the Unsubsidized Federal Stafford Loan Program, the Federal PLUS Loan Program, and the Federal Consolidation Loan Program. It does so by guaranteeing the purchase of defaulted loans from FFELP lenders across Michigan. During its nearly 45-year history with the FFELP, MGA has guaranteed over $14 billion in loans. Beginning July 1, 2010, no new loans are guaranteed under the FFELP, however, MGA has $4 billion in outstanding loans that must be monitored, claims processed, or default payments collected. MGA also provides services to postsecondary institutions that include outreach activities aimed at


198

postsecondary students, technical support, workshops and other training opportunities. Services to borrowers are done through borrower information programs, financial literacy training, and customer assistance with all aspects of repayment.

Operation a. Phone Channel A combination of Avaya vector routing, Genesys IVR and Genesys CTI work to determine the nature of the call and route the caller to the most appropriate service, either with self-service or an agent. The peak call volume during tax filing season is in excess of 20,000 per day. The maximum number of consecutive calls is limited to the eight inbound T1’s, but during 2010 this was never exceeded. The Genesys IVR platform is capable of handling 192 concurrent calls, and currently supports three separate IVR operations (business taxes, income tax and MGA). The IVR includes a system to verify account specific information for Michigan Business Tax, Sales, Use and Withholding Taxes and Individual Income Tax and student loan collection status. Information such as the status of correspondence, refunds and returns, expected refund date, estimated payment verification, prior year return information, requests for copies of forms and licenses, copies of completed returns and paid refund checks is available. The IVR functions 24 x 7 and routes calls to agents during business hours.

There are three phone numbers in effect for customer use, one number for all business taxes, one for Individual Income tax customers and a separate number for MGA customers.

b. Web Channel Business and Individual taxpayers log on to the Siebel eService application through a link from Treasury’s web site. They enter a user name and shared secrets (i.e. account information specific to the return period) allowing them to access detailed account information. The web self-service feature allows them to create a Service Request, which will result in receipt of an auto-acknowledgement and an instruction to visit the web site when their answer is ready.

Taxpayer Siebel eService includes information similar to that found in the IVR application, including refund or return status, expected refund date, estimated payments, prior year returns status, status of correspondence, request address changes and request copies of forms, completed returns, and paid refund checks. Taxpayers can also ask account specific questions.

This channel has experienced rapid growth since its establishment, with 35% year to date increases between 2010 and 2011.

c. Paper Channel - Inbound Inbound correspondence and some tax returns are batched, scanned and indexed using a FileNet Capture and IDL (Inbound Document Linker) applications augmented with a custom Visual Basic (VB) program written and supported by the current MiECC contractor. Documents are grouped into types and classes prior to scanning. Images are then loaded into the FileNet Image Servers. A look ahead into Siebel is made during indexing to ensure the account number entered manually for the image is a valid number in Siebel. All images create Siebel contacts and, in the case of inbound correspondence, open service requests are created. In addition, Collection Division billing correspondence indexes are electronically transferred to CRM, where a contact log and service request linked to the related CRM account are created through an Enterprise Integration Manager (EIM) Process. All service requests are routed to the appropriate CRM work groups.

d. Paper Channel – Outbound Selected outbound mail is imaged by taking a copy of the print file from the print queue. The Xenos product is used to convert the print file into a tiff image and indexes, such as the key account number, are created by extracting this data automatically from the print file. The subsequent images are loaded to FileNet, then Siebel contacts are created for each account.

e. Email


199

Emails are received into various email boxes by tax type. The taxpayers receive auto-acknowledgements from the email software and the emails become work items in Siebel CRM that are routed to various work groups. In general, email is a channel experiencing declining volumes largely due to the security issues around sending account specific information via email. See above b., Web Channel.

Universal Queue Genesys Universal Queuing has been configured to workflow inbound phone calls and Siebel service requests. This includes skills based routing to determine the attributes of telephone callers, selecting various call handling options and routing the call to the most appropriate agent. Currently only phone calls are actually pushed to the agents’ desktops. Siebel service requests are categorized by different areas and are then selected manually by staff within their respective teams using queries.

Quality Assurance Call and outbound correspondence quality assurance is supported by NICE software. Calls are randomly recorded then scored for adherence to quality standards by a pool of evaluators. Customer Service Representatives (CSR’s) also have the option of recording calls on demand. NICE is also used by Customer Contact to evaluate outbound correspondence. Reports The contact center uses Genesys CCPulse for real time reporting of inbound calls. Avaya’s CMS (Call Management System), which is supported by DTMB Telecom, is used for some weekly and monthly reporting although the agency would like to consider replacing these CMS reports with reporting from CCPulse to eliminate the additional costs of CMS.

Monthly Siebel and Oracle SQL reports show the Service Request performance of the contact center. Ad hoc SQL reports have been created by the contractor to analyze data recorded in Siebel. Reports are run and e-mailed out by the Opalis and Tidal schedulers


200

Attachment 9: Agency Environment Information Contact Centers IT Technical Description – in alphabetical order The descriptions represent the applications as they are at Contract execution.

1. Civil Service Commission Overview The MIHR contact center could be described as a mostly “out-of-the-box” Siebel Contact center 7.8 configuration. There is a custom-coded Websphere Application Server (WAS) knowledge base. There are 30 Customer Service Representatives on the phones, receiving approximately 500 calls per day, and up to 5 staff who act as tier 2 agents dealing with service requests.

Siebel Currently, the Siebel base tables are updated via a series of custom programs on a nightly basis with key data provided by output files from the HRMN system. This process updates the Siebel Enterprise Integration Manager (EIM) tables using Perl and Java script programs. The Operational Data Mart (ODM) Enterprise Application is used to store employee, company, location, translation, department and job code in ODM Database and also used to upload data to the EIM tables in the Siebel Database. These programs allow only changes made to the employee data in the past day to be passed through to the Siebel EIM tables. However, once a month, a program completely refreshes all employee data in Siebel. This process also includes a direct insert into a Siebel base table. Knowledge base The content owners enter content into a Vignette 6 project. Content changes are migrated through a two-step process to the WAS application server that stores the content in XML format. Content is accessed through the Internet by State employees. Access credentials are captured by the login page and passed to a Lightweight Directory Access Protocol (LDAP) directory for authentication. Telephony Employees calling into the contact center are initially presented with several telephone menu choices. The contact center uses computer telephone integration (CTI) wherein employees may enter their employee ID or social security number and using Genesys the information is passed as a screen pop to the CSR in Siebel with the employee information contact log auto populated. Incoming callers who identify themselves as wanting employment verification, are in need of self service support, or are retirees of the State of Michigan will select those options and that will auto populate in Siebel with a predefined customer contact number. eMail The MI HR Service Center processes approximately 500 emails from three email sites. Auto acknowledgements are sent and then emails are captured and worked through the Siebel application using a series of predefined responses. Contact logs are generated in Siebel for each email sent and received. Hardware There are 3 hardware environments: production, test and development. Reports Management use reports from Qwest, the Avaya CMS system NICE QA reports, Access and Excel tracking reports and customized reports from Siebel. 2. DTMB-Client Service Center (CSC) Overview

Avaya The inbound 1-800 and local calls terminate on the Capital switch. They are routed to Genesys for processing. As an emergency provision, vectors have been written that, if Genesys is not working, the calls are routed to agents using a set of Avaya vectors.


201

Genesys Genesys provides the IVR, screen pop and call routing functionality.

The IVR takes calls from the switch and routes via various menu options. The caller is asked for his/her employee id which forms the basis for the screen pop. In one scenario, the caller may choose to perform an automated network password re-set. In all other scenarios, the call is routed using skills-based routing to the most appropriately skilled agent. At the same time, the employee id lookup occurs in Microsoft Active Directory for the State of Michigan Domain. If a valid employee id has been provided, then information pertinent to the ID (identifying the caller) is provided in a screen pop to the agent. This information is used by the agent to search Remedy for caller information, existing cases or to start a new case.

Genesys creates the virtual call center. Genesys Interaction Workspace (IW) is used as the client application for the agents. CSC tier 1 agents are located primarily in Lansing and Detroit. Additional Field Service agents use IP Soft phone technology to access the Genesys system through the Capital switch. Tier 2 staff is located at the Operations Center in Dimondale, MI.

Interfaces Automated network password re-sets

When a caller chooses to use the automated network password re-set option, he/she has 3 chances to do so successfully before being routed to an agent. If routed to an agent, then the agent accesses an existing Challenge Response System (CRS) database for questions and answers specific to the individual whom the caller purports to be. If the caller answers the questions accurately, then the agent uses adequate credentials to change the password on the associated account. A ticket is generated and closed to document the transaction. If any complications occur, such as no data is available in the CRS, then the agent will refer the caller to an authorized requestor for validation.

If a caller has previously registered a PIN in CRS, then automated re-set can be successful. In this case, the caller is asked to enter the numeric 4 digit PIN. The HRMN ID and PIN are validated in CRS. If valid, then the process continues with a Positive status being sent with the HRMN ID to Active Directory. The network account associated with that HRMN ID has its password re-set. The caller is told of the successful transaction and a new password. Additionally, data is sent to Remedy to document the re-set. Based on the HRMN ID, also stored in Remedy, the case is opened, documented as a successful network password re-set and resolved. The Remedy system automatically generates an email to the associated email of the account of the re-set.

The Genesys system integrates with the Symon Wallboard for displaying of contact center statistics that includes queue level statistics.

Hardware There are 2 hardware environments: production and test.

Reports Genesys CCPulse will be used for real-time viewing of statistics for all virtual call queues, agent statistics, group statistics, and queue volume alerts. Genesys CCAnalyzer will be used for historical reporting for all routing points, call queues, virtual call queues, agent statistics, group statistics, and Customer personalization call tracking statistics.

Other Reports There are several other sources used to supply management with operational and strategic data about the contact center. They include Avaya CMS, CRS and Remedy queries.

3. DTMB-Office of Retirement Services (ORS)

Overview:


202

The ORS contact center has Siebel as the core product with significant functionality also supplied by Genesys and Avaya components. At peak, there are over 50 customer service agents on the phone with another set of agents answering non-real time work items on Siebel. The current estimate of daily call volume that will use the 1-800 numbers is in excess of 3000 calls.

Siebel The Siebel application uses mostly the out-of-the-box functionality from the Siebel Enterprise Contact center 7.8.2.16 product. Contact and Organization information in Siebel, refreshed from the Clarety every night, is used as the main person identifier and forms the basis for the screen pop at the CSRs desktop when they receive a call. Clarety is the Line of Business (LOB) Web application used by ORS to support Membership and Retirement processing. Siebel is used by staff to track communications with Members and Organizations, as well as to create and track Interactions/Service Requests (Activities/Tickets). Calls that cannot be answered by a tier 1 agent are transferred to a tier 2 agent.

Siebel-Clarety GUI Links Siebel has secure connections to view the backend Clarety system for contact center agents. The type of information Siebel can query in Clarety is related to FileNet images, benefit information, demographic and worksite information.

As a front-end CRM system, service request may be created in Siebel. If the work requires transactions to be completed in Clarety, these requests are created in Siebel. The work originated in Siebel may also be enforced with Service Level Agreements, Prioritization Criteria, and/or Assignment and Due dates prior to being passed to Clarety. Updates to work statuses are passed back from Clarety to Siebel in real-time.

Siebel Virtual Business Components Additional data elements originated and owned by Clarety are readily available to agents working in Siebel. This is accomplished by using a number of mechanisms including Virtual Business Components and Smart (context-aware) Links. The purpose is not to replicate all data, but to make it readily available in both systems. Virtual Business Components are read-only views providing access to real-time Clarety data using Siebel.

Telephony Call Flow: Calls coming from the 1-800 Qwest T1 lines terminate on the General Office Building (GOB) switch. Avaya PBX directs customer calls to the Genesys IVR where callers are provided with self-service opportunities such as the Member Application Status transactions. Callers wishing to talk to an agent can opt out of the IVR and are asked for their ID, which is used to screen-pop the customer’s information on the CSRs desktop when the call is answered.

Genesys: Computer Telephony Integration (CTI) ORS’ telecommunications applications improve Agent efficiency through the use of the Siebel-integrated Genesys CTI and Genesys GVP (Genesys Voice Portal). When ORS customers call, they are routed through the IVR and prompted to enter identifying information. This information is then processed by Genesys (CTI application) and produces a “screen pop” within Siebel, which assist the Agent in identifying the customer. Agents are also provided with Genesys soft phone toolbar capabilities in order to control call activity from their PC desktop.

ORS employs the Genesys 7.6 ERS Framework components in combination with AES, Gplus Adapter, and Siebel Communications Server in order to deliver “screen-pops” to Contact center agents using Siebel. This set of functions draws data from the Genesys GVP (Genesys Voice Portal) 48 Port IVR units connected to the existing ORS distributed Avaya Definity PBX/ACD switch.

VHT ORS is currently implementing VHT for the contact center operations.

NICE System: (Monitoring and Recording System) ORS uses the NICE Perform 3.1 Application Suite as its digital multimedia monitoring and recording solution. This hardware includes a NICE Logger for Voice Storage; Screen Capture and Logger for navigation recording; and the NICE Call Logging System (CLS) for storage of call details. The software components include NICE


203

Universe, Scheduler, Forms Designer & List Editor, Evaluator, Monitor, Web Reporter, and Record on Demand.

In order to gather business call details that are not provided by the switch, the NICE Systems are integrated with Genesys TServer to obtain the data from the IVR.

Avaya The inbound 1-800 calls terminate on the Avaya PBX switch. They are routed depending on the Dialed Number Identification Switch (DNIS) number to different vectors and then, where appropriate, adjunct routed to Genesys. However, the vectors have been written that, if Genesys does not pick up the calls in a certain period of time, the calls are routed to agents using a set of Avaya vectors.

Legacy Interface: Siebel EIM- Enterprise Integration Manager: EIM is used to bring data from Legacy systems (Clarety) and other sources into temporary staging tables, where business rules are applied before the data uploads or updates Siebel-resident data. EAI – Enterprise Application Integration: EAI is used with Siebel to send or receive real-time updates from other applications. At ORS, EAI is used to send and receive real-time updates between Siebel and Clarety. Microsoft SQL Server Transactional Replication: A subscriber database uses this mechanism to receive synchronized data from Clarety, and the data is then normalized or de-normalized to Siebel’s required format. Siebel Workflow/Business Services/HTTP Post Method: The combination of these mechanisms is currently used to send information inserts and updates from Siebel to Clarety. Security Integration: ORS currently uses authentication mechanisms external to “The System” (Clarety and Siebel). Both applications are setup to use a common LDAP (ADSI) server, allowing for common authentication. Transactions between these applications use header authorization acquired from the LDAP server. Other Data Source Virtual Business Components are read-only views providing access to real-time Clarety data using Siebel. VBC views in the contacts business object pull information from an outside source (Clarety) using a VBC connection. VBC connections are to a SQL Server database that stores Member information created by the Clarety System. Hardware There are 3 hardware environments: production, DR/test and UAT/development. Reports Genesys CCPulse is used for real-time viewing of statistics for all virtual call queues, agent statistics, group statistics, and queue volume alerts. Genesys CCAnalyzer will be used for historical reporting for all routing points, call queues, virtual call queues, agent statistics, group statistics, and Customer personalization call tracking statistics. Genesys VAR is used for IVR reporting. Other Reports There are several other sources used to supply management with operational and strategic data about the contact center. They include Qwest, Avaya CMS, Siebel Actuate, and SQL Queries. Workforce Management System ORS uses the Genesys Workforce Management Application Suite to forecasting, employee scheduling, monitoring of real-time agent-adherence and intra-day contact-center performance. The software components include Genesys Web/Supervisor module and WFM Configuration Utility. 4. Environment Quality Overview


204

The DEQ-EAC contact center is mostly “out-of-the-box” Siebel CRM Base 7.8 configuration Siebel The Standard Siebel Call Center Application with the following capabilities is used - service requests, solutions (knowledge base), program contacts, staff, home page and administration. The knowledge base provides a knowledge resource for system users to answer frequently asked questions. The system has two tiers of users: the EAC customer service representatives and the OEA program specialists. Telephony There is no Genesys call routing used for DEQ-EAC Email DEQ uses an Outlook email mailbox to track and assign in coming tasks for in-coming calls; emails are only attached to Siebel records as a source reference to ticket/case Hardware There are three hardware environments: Production, QA, and Development Reports Siebel pre-built reports are used for reporting and these are exported to MS Excel file. 5. Human Services Overview The architecture of the MI Bridges / IVR system is an n-tier design that separates the application into tiers or layers that are architecturally independent of the other. The MI Bridges / IVR system consists of a presentation tier, business logic tier and a persistence tier.

Presentation (Web) Tier Also known as the Web tier, or presentation layer, this governs what the users see at their workstation, but in case of the IVR it governs what users experience on the telephone. A HTTP server hosts the display interface. The developed Graphical User Interface (GUI) must be compliant with the Americans with Disabilities Act (ADA) and is geared to those of varying backgrounds, languages and skill levels. The Web tier for MI Bridges and IVR is specifically developed to capture information, not process it. It allows information to pass through it to the Business Tier, or application layer, where multiple processors stacks route the data and link to data.

Business Tier The Business Tier is the layer where business logic is run. The processing for check my benefits, apply for benefits and report my changes is performed within the Business Tier.

This layer is the most critical to the solution and is broken apart from the Web tier to allow the State to grow the application component of the solution as needed without interfering with, or having to rebuild, the front end—the Web tier.

Developer tools, such as IBM Rational Software Architect/Modeler in combination with J2EE executing on IBM WebSphere Application Server provide ready-to-use application components that would otherwise have to be custom built for integration. Isolation and integration are key elements of the overall solution.

Persistence (Database) Tier The first two layers of the solution act like separate components of the overall solution that enable specific activities to occur before allowing the user to access the database where sensitive data resides. The Database Tier is designed to provide the State added security. It uses port 1521 for Oracle or as defined by the technical requirements and is hosted in Zone 3 a very highly secured environment. Roles providing access to the application are built into the MI Bridges system. The database environment, where data is read, updated and processed according to the business rules configured for operations, is accessed after a series of approvals and processing functions occur within the previous two layers of the system. Stored procedures and triggers within the Database Tier enable mass updates, deletes and other operations to occur quickly within this layer.


205

These are defined as a component of the application logic. The Oracle database component is necessary to provide the premium processing capabilities required by the State. MI Bridges IVR Software Architecture:

The MI Bridges IVR application includes software that resides on standard desktops and servers. Examples of the desktop components include:

Microsoft Windows XP, Microsoft Internet Explorer v5.5 or later (Secure Socket Layer (SSL) enabled with 128-bit encryption) Compatible with Firefox, Chrome and Safari browsers Adobe Acrobat Reader 8.1

Server-side software components include: Sun Solaris 10 Operating System Microsoft Windows 2003 Server Enterprise Edition Operating System MI Bridges IVR application Genesys GVP application Oracle Database 11.2g Enterprise Edition IBM WebSphere Application Server, v 7.0 IBM HTTP Server, v 6.0.2.31 IBM WebSphere Business Integration Software, v 7.5.0 Novell eDirectory, v 8.8.2 Informatica Power Center v 8.1.1 SAP DQ XI (for address verification)

Tool Support Servers Tool support servers that are Windows based have dual 3.4 GHz/2MB Cache Xeon processors and 70 GB hard drives. The following servers in the indicated environments require 2 GB memory:

FAST4J Tool Server for Development Rational Tool Server for Development

The following servers in the indicated environments require 8 GB memory: Build Workstation attached to the SAN

The Rational data server resides in the Development environment and is a Sun Fire V240 with dual SPARC Ultra III processors and 32 GB memory.

Servers DTMB and DHS utilize both Dell and the Sun family of servers for MI Bridges IVR project. For each server, different configurations of processors and memory are required depending on the environment in which it resides. All servers are updated to the most recent patch level required by the hardware contractor and contain the necessary anti-virus software as defined by the State. The Sun Fire servers, with the exception of the X4100, run the Solaris 10 operating system. The X4100 run the Windows operating system.

Virtualization State's Virtual server farm is used to host Virtual Machines (VM’s) for MI Bridges Web servers and MI

Bridges Application servers. Capacity of VM’s in the Virtual Server farm is fed by multiple physical servers. SUSE Linux 10.2 Enterprise is the OS used in the VM’s. VM’s for Web/Application servers reside in Application DMZ Zone 1.49. Browser requests for MI Bridges are routed to a CISCO Load Balancer which resides in DMZ Zone 1

for Internet Access. Multiple VM’s used by Web and Application servers for both Production and DR to achieve Load

Balancing/Failover/Disaster Recovery.


206

System upgrades/maintenance done on the feeding physical servers one by one in the virtual server farm. No downtime due to VM Motion.

Compuware Vantage is used to monitor VM’s in addition to other MI Bridges and IVR servers. Each of the Web server VMs has 1 GB of RAM and 1 vCPU (1 Virtual CPU Core); this can be

increased based on stress testing and capacity planning. Each of the Application server VM has 4 GB of RAM and 2 vCPU (2 Virtual CPU Core).

Self-Service and IVR Networking Infrastructure: The MI Bridges and IVR application is accessed via a wide-area TCP/IP compliant network infrastructure that is provided and maintained by the State. The infrastructure includes firewalls, fiber connections, telephony ports, SAN connections, workstation LANs, project file systems, etc.

MI Bridges and IVR physical environments housed within State facilities and use the existing State network infrastructure. Thus the architecture depends on this infrastructure to be the primary channel to deliver the MI Bridges and IVR application to users throughout the State.

Network monitoring services for the MI Bridges solution is provided by the State and includes trouble shooting assistance and reporting as needed by the project.

Telephony Gateway Infrastructure: The Telephony Gateway Infrastructure consists of:

Telephony Provider (Qwest) Gateway IVR Servers IVR Management Server IVR Reporting Server

A call flows from the Telephony Provider (Qwest) to the IVR Server through the Gateway. IVR servers are controlled by the Management server. Reporting server takes inputs from the IVR application and the IVR servers and reports the same in a user readable format.

The MiECC service to DHS is limited to maintaining the IVR software (Genesys) architecture and support - the IVR application and the web application are maintained by DTMB with another partner contractor.

6. Licensing and Regulatory Affairs - Bureau of Health Professions Overview The LARA-BHP contact center has Siebel as the core product with additional functionality provided by Genesys and NICE. Siebel The Siebel application uses out-of-the-box functionality. Telephone contact logs are created automatically by the system. User and backend interfaces are utilized to allow LARA-BHP to electronically log call activities and service requests. A data interface from backend systems is used to populate customer demographics data into the Siebel contact center database. Genesys Genesys provides interactive voice response (IVR) configured to utilize prompts and rules to allow backend data dip integration for self service. IVR error handling and global functionality, utilizing standard numeric operations (press 0, or press 9 to go back) is incorporated into processing. NICE NICE Perform has been configured to monitor and record agent calls. Hardware There are three hardware environments: production, test and development.

Reports


207

Future requirements to be determined. 7. State Overview The MDOS contact center has Siebel as the core product with significant functionality also supplied by Genesys and Avaya components. At peak, there are over 70 customer service agents on the phone with another 10-15 agents answering non-real time work items on Siebel. The current estimate of daily call volume that will use the 1-888 number is in excess of 10,300 calls. There may be up to 10 concurrent eService users from the branch offices using the system to create or review service requests. Siebel The Siebel application uses mostly the out-of-the-box functionality from the Public Sector Contact center 7.5.3 product. Driver and vehicle information in Siebel, refreshed from the mainframe every night, is used as the main account identifier and forms the basis for the screen pop at the CSRs desktop when they receive a call. Calls that cannot be answered by a tier 1 agent are transferred to a tier 2 agent and, if the call can still not be answered satisfactorily, a service request is created. Service requests are worked by non-phone staff and, after completion, the tier 2 agent calls the citizen back with the resolution.

There is an eService application that allows branch office staff and other work units in MDOS to login to Siebel and create a service request. Subsequently they can also use the application to review the status of their service request.

Telephone Call Flow Calls coming from the 1-888 Qwest T1 lines terminate on the General Office Building (GOB) switch. There are two types of calls: one coming from a citizen and the other from branch office MDOS staff. Branch office staffs use a 1-877 number and this allows Avaya to differentiate the callers.

An Avaya vector directs citizen calls to the Genesys IVR where callers are provided with various self-service opportunities. Callers wishing to talk to an agent can opt out of the IVR and are asked for their Drivers License Number, which is used to screen-pop the citizen’s information on the CSRs desktop when the call is answered. Note: A similar functionality exists for vehicle registration number; however this functionality is currently turned off in the IVR due to the systems inability to accurately recognize alpha characters.

Calls coming from branch office staff are directly routed to tier 3 agents after using a vector to capture the employee ID number and a branch identifier which is used to create a screen-pop on to an agent’s desktop.

Genesys Genesys provides the IVR, screen pop and call routing functionality.

The IVR takes citizen calls from the switch and routes the citizen through various self-service options. There are many points where the caller can opt out to speak to an agent. If the caller chooses to opt out, Genesys captures where opt out takes place and makes a determination, based on a series of business rules, which tier 1 agent skill level is required to answer the call. The call is routed using skills-based routing to the most appropriately skilled agent. In the process, the caller is asked for their Drivers License Number which forms the basis for the screen pop. Scansoft speech recognition software allows the caller to speak this number. At the same time, a data dip takes place into the Siebel database to determine if the caller already has an open service request. If one exists, Genesys routes the caller past the tier 1 agent straight to a tier 2 agent queue.

Genesys also picks up the branch office staff calls from a vector along with the collected employee ID number and routes these to a tier 3 agent queue. Tier 3 agents receiving the call get a screen pop of information related to that branch office employee.

Genesys creates the virtual call center. CSR tier 1 agents are located in both Lansing (GOB switch) and Detroit (Detroit Cadillac Place switch).

Avaya


208

The inbound 1-888 calls terminate on the GOB switch. They are routed depending on the Dialed Number Identification Switch (DNIS) number to different vectors and then, where appropriate, adjunct routed to Genesys. However, the vectors have been written that, if Genesys does not pick up the calls in a certain period of time, the calls are routed to agents using a set of Avaya vectors.

Legacy Interfaces Mainframe The MDOS mainframe interface is similar to that used by Treasury. The Databridge product is used to extract audit files from the mainframe and place the data into Oracle tables. PL/SQL statements are used to populate Siebel Enterprise Integration Manager (EIM) tables. Finally a Siebel EIM configuration file .ifb file runs and populates the Siebel base tables.

A series of “hot keys” have been created to import specific information from the mainframe into a Siebel applet using a .Net connector. The information coming through the connector is not stored in Siebel.

Other Data Sources Some views in the contacts business object pull information from an outside source using a VBC connection. One VBC connection is to a Microsoft Access database that stores a record of letter correspondence generated in MDOS and sent to citizens.

Hardware There are 3 hardware environments: production, test and development.

Reports Genesys CCPulse will be used for real-time viewing of statistics for all virtual call queues, agent statistics, group statistics, and queue volume alerts. Genesys CCAnalyzer will be used for historical reporting for all routing points, call queues, virtual call queues, agent statistics, group statistics, and Customer personalization call tracking statistics.

Other Reports There are several other sources used to supply management with operational and strategic data about the contact center. They include Qwest, Avaya CMS, Siebel Actuate, and SQL Queries.

8. Treasury Overview The Treasury contact center has Siebel Contact center 7.8 as the core product, but significant functionality is also supplied by Genesys, Avaya, NICE, FileNet, Tidal, Opalis and Xenos components. Although CSRs are only on the phones between 8:00 am and 4:45 pm, Monday through Friday, the IVR and Siebel eService for taxpayers is available 24 x 7. At peak, there are over 40 customer service representatives on the phone with another 180 staff working non-real time work items on Siebel. The annual contact volume (all channels) is in excess of 2.2 million contacts.

The support team provides break/fix response and more formal major scheduled release updates. The business user maintains some administrative functions within Siebel.

Siebel Contacts in all channels (phone, IVR, web, email, white mail and walk-ins) are recorded in Siebel Contact center 7.8. Most telephone contact logs are created automatically by the system with agents choosing a reason and resolution code combination from a drop down list. Siebel populates the reason and resolution codes for IVR and self-service web contacts.

Non-real time work items are created automatically through the inbound correspondence channel or via the Siebel eService access by the taxpayer. Manual service requests can be created by any agent. The Siebel Communication tool bar controls the agent’s access to real time work items.

Taxpayers can sign into Siebel eService from the web to view account status information and create a service request. A security adapter has been built with the help of Siebel to facilitate the authentication process. The


209

Siebel eService application also has front-end tables built in that allow business user analysts to change certain responses such as the estimated date when a specific taxpayer’s refund will be issued. .

The contractor is responsible for monitoring Siebel e-service site functionality 24/7.

FileNet The FileNet Capture and IDL (Inbound Document Linker) software is configured and augmented with a custom VB program (written and supported by the contractor) to support the scanning and indexing operation. Xenos is used to capture print files and enable outbound correspondence to be stored in FileNet. Images are created for various classes of documents: inbound correspondence, outbound correspondence, tax returns and registration forms. Treasury staff access FileNet through Siebel or directly through FileNet. Each document class is treated differently for creation and routing of service requests in CRM.

a. Inbound Correspondence Inbound correspondence is batched for different Treasury work groups and scanned. Images are indexed manually with the account number that is verified with a look ahead into the Siebel database to insure the account exists in Treasury’s CRM database. Documents that are difficult to code are held open in FileNet and routed for indexing to separate groups of Subject Matter Experts. Once all documents in a batch are indexed, the images are then committed to FileNet Image services. A list of the images goes to the FileNet IDL product that has been configured and augmented with a custom VB program to create an inbound Siebel contact log and, when appropriate, an open Siebel service request. The Treasury legacy system requires notification of the receipt of certain classes of inbound mail and, therefore, a file is created in FileNet and sent directly to that system. Once inbound correspondence service requests are completed, Siebel creates a daily feedback to several legacy systems including TREAS, MARCS (the collection system) and SAP.

b. Outbound Correspondence There are two routes for importing outbound correspondence into Siebel. i. Outbound correspondence that is produced by the tax legacy systems including SAP has been

identified by the business to be stored in FileNet and attached to Siebel as an outbound contact. Xenos is used for this route and it captures the print file for each type of outbound correspondence and, based on pre-built templates, parses out some key data to create an index and stores the document image as a tiff file. FileNet IDL links the image to the Siebel account and creates a closed contact log.

ii. Outbound correspondence that is in the form of a Word document (not generated by legacy systems) can be attached to the contact log/service request on an individual basis.

c. Tax Returns The indexes of tax returns are stored in FileNet and made available to staff desktops via a FileNet Images Services look up or through Siebel CRM.

d. Historically Scanned Documents Other documents (usually those with priority handling) are worked by CSR’s and then imaged as historical documents in FileNet. Siebel workflow creates a closed contact log linked to the related CRM account with the appropriate reason and resolution codes for historical images.

Telephone Call Flow Treasury has two main telephone contact center groups: Individual Income Tax (IIT) and Business Tax. The call flow includes 24 x7 access to the Genesys IVR. Several Genesys virtual call queues are created in front of the agents to allow specialized customer service. The Genesys configuration is done by the contractor. The Avaya ACD vectoring and programming is done by DTMB Telecom. The Avaya ACD messages for these vectors and the IVR are developed and recorded by Treasury business users.

MGA has one telephone call center group. The Genesys IVR for MGA has restricted hours due to the need to access Sallie Mae. MGA’s IVR application is available Monday through Friday 7:30 AM -9:00 PM and Saturday 9:00 AM - 1:00 PM.


210

Genesys Screen Pop, Routing and Universal Queuing Genesys Computer Telephony Integration (CTI) is used to provide basic screen pops for incoming and transferred telephone calls, and manage call waiting queues (on the switch) for Income Tax and the Business Tax lines. Account identifying data is captured in the IVR, and is passed to Genesys CTI, which queries the Siebel database to determine some pertinent characteristics of the caller. Genesys CTI then routes the call through various call treatments and ultimately to the most appropriate skilled agent. The Genesys Gplus adapter to Siebel allows the CSR to get the taxpayer account information on their screen in a screen pop when they answer the call. If Genesys IVR and CTI are not available the default Avaya vectors have been designed to provide an alternative routing to the agent.

Genesys has been configured to route non-real time items, although this functionality has currently been turned off. For example, Siebel service requests would be sent to Genesys and would effectively route them in much the same way as telephone calls are routed. Agents would have a work state that would make them available for either real time items (phone calls) or non-real time (service requests). To get non-real time items today, CSRs sign into an AUX code to work correspondence and pick service requests from their group’s list of items. Genesys Interactive Voice Response (IVR) The IVR application has 5 production servers including two GVP servers, Eight T1 circuits behind the Avaya G3 switch. The test system includes two servers and one T1. The IVR provides the taxpayer with self-service options that require authentication using shared secrets from the related account’s CRM data. Credentials are collected in the IVR and passed to Siebel for verification. This connection is through an XML request over an HTTP connection to the Siebel application server. An approval returns taxpayer information in XML format to the IVR, which parses out the necessary data for the response to the taxpayer. Similarly, the MGA IVR collects credentials and passes the data to Sallie Mae for verification via web services. The web service passes back data from Sallie Mae necessary to complete the call. Data is exchanged in an XML format. Text-to-speech response functionality exists only for playing back. Many system responses requires messages, in which case the system picks from a number of pre-recorded messages that are played as required. The IVR application also has front-end tables built in that allow the business user analysts to change certain responses such as the estimated date when a specific taxpayer’s refund will be issued. Finally at the end of the call, when the taxpayer hangs up or pushes out to the agent call flow, a Siebel contact record is put into the Activity log. Empirix services are used to monitor IVR functionality 24/7. This service is covered under a separate contract. NICE Call Monitoring and Recording The NICE Perform 3.X application has been configured to provide quality assurance and record on demand functionality. It monitors and records agent calls, forming an integral part of Treasury’s quality system. The NICE window displays agent and channels, including real time information. Calls recorded contain voice and screen. Screens can be monitored/recorded/played. Currently any changes or upgrades to this system are provided directly through NICE systems. NICE must connect to the Genesys T server via a pre-built connector installed by NICE. Interfaces a. Legacy

Siebel receives data each night from the Unisys mainframe. The Databridge product is used to extract audit files from the mainframe and place the data into Oracle tables. PL/SQL statements are used to populate Siebel EIM tables. Finally, an IFB process runs and populates the Siebel base tables.

b. SAP


211

Siebel receives data each night from SAP-XI which is initially loaded into temporary Oracle holding tables. PL/SQL statements are then used to populate Siebel EIM tables from there. Finally, an IFB process runs and populates the Siebel base tables.

c. Inbound Correspondence

Legacy system and SAP processes require immediate notification when a taxpayer responds to a Treasury request by submitting a letter or returning a completed form. To facilitate this requirement, a file is generated in FileNet from the imaged and indexed correspondence and sent to a legacy host.

d. Security Adapter

A detailed program has been created to capture credentials and authenticate taxpayers accessing the Siebel system through the web. This adapter has been approved and validated by Siebel.

e. Genesys The Genesys Gplus adapter for Siebel is used to support communication between Genesys and Siebel. This supports many functions including screen pops and the Siebel communications tool bar that provides telephony control to agents at their desktop. Genesys does access Siebel directly to provide the data for routing decisions.

f. MARCS

Information about inbound correspondence received in the Collections/MARCS system is loaded into Siebel using the EIM process, creating Siebel service requests. A daily extract file is also created within Siebel containing updates on completed MARCS correspondence. This extract file is taken as an input into MARCS.

g. FileNet CIS This product facilitates the communication between FileNet and Siebel. It allows service requests and contact logs to be created in Siebel and allows CSRs to access FileNet attachments by clicking on an icon within a Siebel window.

h. Scheduling Software Tidal and Opalis are currently used to schedule interface data transfer. In the daily Treasury CSIP Refresh process, the data is extracted from the legacy and SAP systems and sent to the Siebel EIM tables. Scripts are used to load data from EIM tables to the Siebel Base tables. All scripts and processes necessary to refresh the Treasury data through to the Siebel Base tables, and all other automated scripts or reports will be automated to Opalis/Tidal job scheduler. DTMB supports the job scheduling programs.

i. Sallie Mae The MGA IVR authenticates the caller and reads information back from the Sallie Mae system via web services. DTMB supports the web service for Sallie Mae.

j. Treasury Centralized Correspondence system (a.k.a. “the letter writer”) The MGA IVR offers the caller several options to receive correspondence (ex, paid in full letter, payoff quote, etc.). When the caller opts to receive correspondence the IVR generates a request to the Treasury Centralized Correspondence system via web services. DTMB supports this web service.

k. Centralized Electronic Payment Authorization System (CEPAS)

Beginning in August 2011, the MGA IVR will transfer callers who wish to make a payment to a new CEPAS IVR offered by vendor First Data Government Solutions (FDGS). This is a straightforward call transfer to a 1-800 number

Hardware There are 3 hardware environments: production, test and development.


212

Reporting Genesys CCPulse Treasury utilizes the Genesys CCPulse application for real-time viewing of statistics for all virtual call queues, agent statistics, group statistics, and queue volume alerts. Genesys CCAnalyzer Treasury utilizes the Genesys CCAnalyzer application for historical reporting for all routing points, call queues, virtual call queues, agent statistics, group statistics, and Customer personalization call tracking statistics. Genesys Voice Application Reporter (VAR) Some business users obtain historical and real time IVR reporting information from the VAR application. This system provides information on customer call path utilization within the IVR and success rates for calls serviced within the IVR. Avaya CMS (Call Management System) Some business users still rely on CMS reports. CMS is supported and maintained by DTMB Telecom. If for some reason Genesys reporting is lost, CMS can provide some level of back up. EDMS Metrics There is a database that consists of a custom read-only MS Access application built to provide supervisors with statistical reports on FileNet imaged documents. This allows business users to confirm that all inbound and outbound correspondence put into the document imaging is ultimately received into Siebel and stored correctly in FileNet. Other Reports There are other sources used to supply management with operational and strategic data about the contact center. These include Avaya CMS, and Siebel and Oracle SQL Queries. Development & Testing Siebel CRM and eService, Genesys and FileNet component and system testing is performed by the contractor. There are CRM and Genesys development environments and a FileNet development/test environment. DTMB supports the related servers and applications for CRM, Oracle databases and security access controls for each environment. Avaya ACD vectoring, programming and message assignment are supported by DTMB Telecom. Dedicated business user teams of 2 to 4 analysts identify new enhancements, work with the contractor to develop business requirements, create wording for messages, and menus in the Avaya ACD, Genesys IVR and eService web screens. The business user creates test scripts with the assistance of the contractor, maintain the various channels test script libraries, assist in identifying new test data requirements and lead the user acceptance test teams for Siebel CRM, Siebel eService, Genesys, Avaya ACD, Genesys IVR, and FileNet. This user team also maintains the CRM administrative tables and selected Genesys administrative tables. The heaviest development period occurs during June through December. Other Treasury CRM point releases occur during the rest of the year. Addition of new teams, classes and document types to FileNet occur throughout the year. Business owner signs off on enhancements / changes in all channels before they are moved to production.

Security The contractor shall treat and handle Department of Treasury personal, confidential or sensitive data it receives in accordance with the terms of this Agreement, State of Michigan policies and the laws of the State of Michigan and the United states.

Future Development


213

Treasury has started plans for development of replacement systems for Business Registration and combined Sales, Use and Withholding over the next few years. These replacement systems will require the rebuild of daily EIM refresh processes from these legacy systems and expansion of business account data elements in CRM.

Consideration for the development of live chat and other “social media” contact methods such as text messaging is in the future. Security considerations are paramount, but infrastructure is not currently in place for these channels.

Ability to add additional taxes and interface with COTS/ERP systems such as SAP. For the new Corporate Income Tax (CIT) and Flow Through Withholding, using the XI component to query the SAP production data real-time via Siebel/CRM

Ability to add new taxes to IVR systems and provide enhanced information.

Ability to interface with other telephony systems, including VOIP.

Replace existing scheduling tool from OPALIS to TIDAL.

Measurement of first contact resolution is also a desired outcome of any system enhancements. Ability to accept and log electronic documents sent from customers into FileNet such as electronic faxes

and attachments to eService service requests.