The URL can be used to link to this page

Home My WebLink Aboutresolution.council.072-18 RESOLUTION #72 (Series of 2018) A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF ASPEN, COLORADO, APPROVING A CONTRACT AMENDMENT BETWEEN THE CITY OF ASPEN AND CHERRYROAD TECHNOLOGIES, INC AUTHORIZING THE CITY MANAGER TO EXECUTE SAID CONTRACT AMENDMENT ON BEHALF OF THE CITY OF ASPEN, COLORADO. WHEREAS, there has been submitted to the City Council a contract amendment for additional support hours for the Oracle Enterprise Resource Planning (ERP) application between the City of Aspen and CherryRoad Technologies Inc, a true and accurate copy of which is attached hereto as Exhibit «A,>. NOW, THEREFORE, BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF ASPEN, COLORADO, That the City Council of the City of Aspen hereby approves that Contract Amendment for additional support hours for the Oracle Enterprise Resource Planning (ERP) application between the City of Aspen and CherryRoad Technologies, INC a copy of which is annexed hereto and incorporated herein, and does hereby authorize the City Manager to execute said agreement on behalf of the City of Aspen. INTRODUCED, READ AND ADOPTED by the:City Council of the City of Aspen on the 301n day of April 2018. IL St ven S a ron, Mayor I, Linda Manning, duly appointed and acting City lerk do certify that the foregoing is a true and accurate copy of that resolution ad pted by the City Council of the City of Aspen, Colorado, at a meeting held pril 30`h, 2018. �o Linda Manning, City Cler CITY OF ASPEN ENTERPRISE RESOURCE PLANNING PROJECT PROJECT WYATT CHANGE REQUEST #7 Prepared for: City of Aspen 130 S. Galena Street Aspen,.CO 81611 Prepared by: CherryRoad Technologies Inc. 301 Gibraltar Dr. Suite 2C Morris Plains, NJ 07950 Change Request#7 -4 CherryRood tedtWoy a Date Version Description4/17/2018 1 1.0 Initial Draft Mike Rubilotta 4/17/2018 12.0 Pricing Update, Paul Nielsen Review and Approval Date Version Approval Page 2 of 12 Change Request q7 Chert yROOd R' wn"wog� SECTION 1 —CHANGE REQUEST INFORMATION Change This Change Request, with an effective date of 05/01/2018 will serve Description: as a change in terms to the Services Agreement and Statement of Work, Exhibit A, entered into on November 9, 2015 by and between the City of Aspen and CherryRoad Technologies Inc. ("CherryRoad"). Except as expressly amended herein, all other terms and conditions of the Agreement shall remain in full force and effect. ' Reasons for This•change request will serve to provide the following: Requesting Change: Provide additional hours for 2018 Production support. This Change Request will increase the existing support bucket by 400 hours. Page 3 of 12 Change Request#7 u1 . CherryRoad (PI' tech SECTION 2—IMPACT ANALYSIS Change Complexity Classification: ❑ High ❑ Medium ® Low Cost Impact: Original Contract Value for $1,105,180.00 Implementation Services Additional Cost of Change Request#1 $ 0.00 Additional Cost of Change Request#2 $ 4,500.00 One-time ADP Implementation Fee Additional Cost of Change Request#3 $ 0.00 Additional Cost of Change Request#4 $24,490.00 Taleo extension Additional Cost of Change Request#5 $91,250.00 — Extended Support Additional Cost of Change Request#6 $136,875 — Extended Support Additional Cost of Change Request#7 $44,000 — Extended Support New Contract Value for Implementation $1,406,295.00 Services Details on additional cost of amendment: CherrvRoad On-Going Support On—Going support focuses on two distinct areas: • Incident-based support. • Release Management for Oracle Cloud. Incident-Based Support Incident-based support covers the management and resolution of Level (or Tier) 2, 3 and 4 support for Application and Technical issues. Beyond normal break-fix incidents, we recognize the special care that is required for release management for the Cloud solution. A key component to meeting the City of Aspen requirements is ensuring issues or incidents are properly recorded, managed, and resolved. Our aim is to restore Aspen as quickly as possible while finding and addressing the root cause of the problem, as summarized below. Page 4 of 12 Change Request a71_ CherryRoad �1'. feChnobgia Problem • Detection and Recording Problem Control Create and Review Request for • Classification and Support Error Control Change • Investigation and Diagnosis Proactive Management • Evaluate Change • Resolution and Recovery Major Incident/Problem • Authorize and Schedule Change • Incident Closure Review ( ; • Prepare and Implement Monitoring I • Review and dose • Oracle SR Tracking - - — -- -- I I_ Knowledge . • . Stapdard CherryRoad's.Help Desk approach is a tiered approach. The following defines the various tierstlevels of the support services and responsible party throughout the support time frame. Tiered Approach to Support Levellrier 1 Support (Aspen) The level 1 support staff will consist minimally of two support resources. A security administrator, will be needed to handle all application security related service requests and a level 1 support analyst, with knowledge of the application, will be needed to resolve non-complex issues such as account lock outs, re-setting passwords, issues accessing the system and questions regarding how to use the application. Leveller 2 Support (CherryRoad) Level 2 support will be provided by CherryRoad Managed Services, with assistance from the Aspen support team. When a service request requires more in-depth analysis, it will be routed to the level.2 support staff either by phone, email, or via ServiceNow. The level 2 support staff, consisting of experienced cloud generalists,will complete an initial triage of the request, determine the cause and begin developing a solution. In the cases where a full code analysis is needed, or actual coding changes are required, the service request will be routed to level 3. Please Note: Aspen will be required to complete the final testing of all implemented solutions and sign off on deployment,to the production environment. Leveller 3 Support (CherryRoad) Level 3 support will be provided by CherryRoad Managed Services. If, during the analysis by the level 2 support staff, it is determined that further detailed technical analysis is required, the level 3 support staff will take over the service request. The level 3 support staff,fully equipped to resolve the most complex of service requests, will include both experienced functional and technical resources with expertise in covering a wide range of system issues. Level 3 support Page 5 of 12 Change Request#71 CherryRoad tt= '' tin, will complete any remaining analysis and will find, implement and unit test the solution. If required, Level 3 resources will work with Oracle as needed to facilitate resolution. Please Note: Aspen will be required to complete the final testing of all implemented solutions . and sign off on deployment to the production environment. Level/Tier 4 Support(Oracle) If during the analysis it is determined that the issue needs to be escalated to Oracle support, CherryRoad will log the service request with Oracle and manage all communication with them regarding the service request. Once Oracle provides a solution, CherryRoad will supply details of the solution to the Aspen and then move forward to implement and test the solution as part of Level 4 support. Help Desk Ticket Lifecycle All service requests will flow through one or more of the following steps during its lifecycle. Initiation Whether the contact is to request documentation or to report a problem, the first stage of the process is to create the Service Request (SR) and capture all the relevant information necessary to either service the request, resolve the problem or escalate it to the next tier with sufficient information to resolve the problem. Assignment If the SR is not resolved on the initial call, the SR is then assigned to the appropriate tier/team/resource for Aspen with the expertise of the effected application or module. Resolution Since an SR can range from a simple request with a documented resolution to an Oracle bug, the various tasks, the timeframe and even the tier producing the resolution will vary with each SR. However, in general, this stage involves the analysis, research and the action taken to fix the root cause of a problem or to identify a suitable workaround until.the problem can be resolved. Testing Depending on the resolution, significant testing and even regression testing may be required before receiving approval to implement the solution. Most typically, it involves a functional analyst testing the solution in a non-production environment followed by Subject Matter Experts (SMEs) and/or end-user testing in another non-production environment to ensure the original problem is resolved and no new problems have been introduced. Page 6 of 12 Change Request t17. 31 . CherryRoad tt?'` tahrrolog�es Approval Approval for the SR can be entered by Aspen as a comment in the ServiceNow SR or via email to the assigned CherryRoad resource. Approval of an SR indicates the solution has been tested and can now be scheduled for deployment to the production environment. Implementation This step represents the actual resolution. Examples would be the documented steps being executed, configurations deployed to production or the deployment of a vendor patch, code modification, etc. Closure After the resolution has been provided and Aspen confirms, the SR is closed. From initiation to closure, each SR within ServiceNow will be updated with relevant notes and status changes. In addition, email messages will be sent upon initiation and at each status change during the process. At any time, Aspen can log into the system or call the CherryRoad help desk to get the current status on the SR. The CherryRoad help desk ticket process flow below (Figure 1) illustrates the stages and support levels involved during the lifecycle of an SR. Page 7 of 12 Change Request#7 parr CherryRoad \�' [echnobgies CherryRoad Help Desk Ticket Process Flow Diagram CherryRoad Managed Service Center Help Desk Service Request Process Flour client End User 6 SMEs C 0 c �.N O.estivrRequstlCanmcnu em Nater 44 {IGryf1ll11 �' - �AOPIItnIm MN {(tea--c—__� V Icdutlen' N 4Jh—.BeNvMmdtmn i mem NeID Desk Tier 1 Other — Support Teams hupJ/Wisdenraad.c ye, dCYpAg"R N-*R-wm- /��AN�[jp/�,} vE Fumenmmcaed ReIDlWm MSCHelp Desk ServiceRequest .�Mb � rnahidM.�PpbUori 'C�AprradoreT/Sa1up Y" WNIrRvµev rest 6 Drde'r rnrdpuraum Duryer �nsoMd trrSyumrDtr VIMTed Deg"Ppdr Dofe�'PW6 NDOIr Rrqueep Ne M Ovt R _ OmeReq"& Nonfl R[pener . DepWWuWn No re Grade Support Servlw Request SaksM wewdee Figure 1 Page 8 of 12 Change Request#7 }t! CherryRoad whnda& Release Management for Cloud The cloud model is different from on-premise and this is by design. For less cost, some independence is given up. While historically, with an on-premise ERP solution, the user could wait long periods of time to apply releases. In the cloud, managing the release schedule is critical. There area few key concepts our team will be sure to enforce and is uniquely qualified to deliver. Release Schedule—With the Oracle Cloud, a flexible but prescribed release schedule is enforced. Familiarity and a cadence with this schedule is necessary. Our team will bring these aspects to Aspen. Integration with Cloud— Integration with the Cloud has more constraints than a traditional on- premise solution and our Team brings the tools, methods and experience to work effectively with the constraints. Our Team also brings experience with integration from the Cloud to other systems. Oracle Tickets—It is important to understand the Oracle Cloud ticket process and what levers are available to escalate if needed. Our team brings this knowledge as well. Summary In each area above, our team brings unmatched experience working with Oracle's Cloud solutions and team to ensure your application is updated while not impacting day-to-day activities. This long-term support includes: • One seat license to CherryRoad Cloud Success Platform for ticket management is included with the proposed annual SaaS subscription fees. One release management service (upgrade to next software release) • Incident based support Please Note: additional seat licenses, release management services or incident-based support hours may be added at an additional fee. In addition, CherryRoad is able to provide Level 1 support if desired by Aspen at an additional cost. Please Note: The above support would follow the same process as outlined in the on-going support above. Additional seat licenses, release management services or incident-based support hours may be added at an additional fee. Page 9 of 12 Change Request#7 A . CherryRoad' �'' trchrioloyi« Costs This long-term support includes: • One seat license to CherryRoad Cloud Success Platform for ticket management • Includes a 'bucket' of 400 hours of remote support to be used by the City at their discretion for Release Management and Incident based support Invoices will be billed monthly over an 8-month period for a total amount of$44,000.00 Month Amount May 2018 $5,500 June 2018 $5,500 July 2018 $5,500 August 2018 $5,500 September 2018 $5,500 October 2018 $5,500 November 2018 $5 500 December 2018 $5,500 TOTAL 1 $44,000 Please Note: Additional seat licenses, release management services or incident-based support hours may be added at an additional fee (see below). In addition, CherryRoad is able to provide Level 1 support if desired by the City. Page 10 of 12 Change Request#7 = „ CherryRoad t' tedlVu Discounted Support Costs The City can supplement the 1095 hours provided in the baseline support with the following discounted 'buckets' of support hours. These hours can be used at the City's discretion. o - Time Fed 200 Support Hours for Oracle ERP and HCM Cloud ($120 per hour) $24,000.00 300 Support Hours for Oracle ERP and HCM Cloud ($115 per hour) $34,500.00 400 Support Hours for Oracle ERP and HCM Cloud ($110 per hour) $44,000.00 Taleo TBE Support ($125 per hour needed) Assumptions 1. Invoices will be submitted with supporting documentation providing detailed explanations of hours worked in the month. 2. Pre-Approval for any SR over 10 hours of work is required by Aspen Management in advance 3. Aspen can request specific CherryRoad resources to work on open SRs. Every attempt will'be made to make the requested resources available but specific resources cannot be guaranteed 4. All change requests for reports and security will be counted against the extended support hours Due to the inability to estimate technical retrofit changes from one release to another we have Section 3—Impact to Scope of Services 1) There are no changes to the scope of services. Page 11 of 12 Change Request#7 .-A CherryRoad ' ted—kgs Section 4—Non-Collusion and Acceptance. The undersigned attests under penalties of perjury that he is the representative, agent, member or officer of the contracting party, that he has not, nor has any other member, employee, representative, agent or officer of the firm, company, corporation or partnership represented by him, directly or indirectly, to the best of his knowledge, entered into or offered to enter into any combination, collusion or agreement to receive or pay, and that he has not received or paid, any sum of money or other consideration for the execution of this Change Request other than that which appears upon the face of the Change Request. Approved by: � on: CherryRoad Technol gies Inc. Date Approved by: City of Aspen Date Comments: None or— ❑ See below: Page 12 of 12