The URL can be used to link to this page

Backup Documents 05/09/2023 Item #16J4 ORIGINAL DOCUMENTS CHECKLIST & ROUTING SLIP TO ACCOMPANY ALL ORIGINAL DOCUMENTS SENT TO THE BOARD OF COUNTY COMMISSIONERS OFFICE FOR SIGNATU Ub J 4 Print on pink paper. Attach to original document. The completed routing slip and original documents are to be forwarded to the County Attorney Office at the time the item is placed on the agenda. All completed routing slips and original documents must be received in the County Attorney Office no later than Monday preceding the Board meeting. **NEW** ROUTING SLIP Complete routing lines#1 through#2 as appropriate for additional signatures,dates,and/or information needed. If the document is already complete with the exception of the Chairman's signature,draw a line through routing lines#1 through#2,complete the checklist,and forward to the County Attorney Office. Route to Addressee(s) (List in routing order) Office Initials Date 1. Risk Risk Management • 2. County Attorney Office County Attorney Office af2.- 5 �y ) 4. BCC Office Board of County 7 �� Commissioners RL ly /1z // S//o/23 4. Minutes and Records Clerk of Court's Office / )1 6/16/93 ho; 5. Procurement Services Procurement Services PRIMARY CONTACT INFORMATION Normally the primary contact is the person who created/prepared the Executive Summary. Primary contact information is needed in the event one of the addressees above,may need to contact staff for additional or missing information. Name of Primary Patrick 0'Quinn/PROCUREMENT Contact Information 239-252-6020 Staff Contact/ Department Agenda Date Item MAY 9TH, 2023 Agenda Item Number 16.J.4. was Approved by the BCC Type of Document FIRST AMENDMENT Number of Original 1 Attached Documents Attached PO number or N/A 21-7936 PHOENIX account number if PROFESSIONAL BUSINESS INC. document is to be SERVICES FOR DBA PHOENIX recorded SAP S/4 HANA BUSINESS IMPLEMENTATION CONSULTING INSTRUCTIONS & CHECKLIST Initial the Yes column or mark"N/A"in the Not Applicable column,whichever is Yes N/A(Not appropriate. (Initial) Applicable) 1. Does the document require the chairman's original signature STAMP OK N/A 2. Does the document need to be sent to another agency for additional signatures? If yes, N/A provide the Contact Information(Name;Agency;Address;Phone)on an attached sheet. 3. Original document has been signed/initialed for legal sufficiency. (All documents to be PRO signed by the Chairman,with the exception of most letters,must be reviewed and signed by the Office of the County Attorney. 4. All handwritten strike-through and revisions have been initialed by the County Attorney's N/A Office and all other parties except the BCC Chairman and the Clerk to the Board 5. The Chairman's signature line date has been entered as the date of BCC approval of the PRO document or the final negotiated contract date whichever is applicable. 6. "Sign here"tabs are placed on the appropriate pages indicating where the Chairman's PRO signature and initials are required. 7. In most cases(some contracts are an exception),the original document and this routing slip N/A should be provided to the County Attorney Office at the time the item is input into SIRE. Some documents are time sensitive and require forwarding to Tallahassee within a certain time frame or the BCC's actions are nullified. Be aware of your deadlines! 8. The document was approved by the BCC on 05/09/2023 and all changes made during N/A is not the meeting have been incorporated in the attached document. The County an option for Attorney's Office has reviewed the changes,if applicable. this line. 9. Initials of attorney verifying that the attached document is the version approved by the N/A is not BCC, all changes directed by the BCC have been made,and the document is ready for the an option for Chairman's signature. this line. t6J4 FIRST AMENDMENT TO AGREEMENT #21-7936 FOR PROFESSIONAL SERVICES FOR SAP S/4 HANA IMPLEMENTATION THIS AMENDMENT, made and entered into on this t day of I\A ct y 2023, by and between Phoenix Business, Inc. d/b/a Phoenix Business Consulting (the "Consultant") and Collier County, a political subdivision of the State of Florida, (the "County" or "Owner") (collectively, the "Parties"): WHEREAS, on April 12, 2022, Item 11 .C, the County, in partnership with the Clerk of Courts and Comptroller's Office entered into an Agreement with Consultant (the "Agreement") to implement required upgrades to the current SAP Financial Management System; WHEREAS, the Parties desire to amend the Agreement to add Task 10 to the Scope of Services relating to SAP Success Factors Employee Central and Workforce Time Management and reflected in the attached Schedule A-2 Statement of Work with an additional cost of$1 ,768,251 to be reflected on the revised Schedule B Basis of Compensation attached hereto. NOW, THEREFORE, in consideration of the mutual promises and covenants herein contained, it is agreed by the Parties as follows: 1. The above recitals are hereby incorporated into this First Amendment as if fully set forth herein. 2. Schedule A-2 Statement of Work for SAP Success Factors Employee Central and Workforce Time Management as attached is hereby incorporated into the Agreement. 3. Schedule B is hereby deleted in its entirety and replaced by the attached Schedule B-1 . 4. All other terms and conditions of the Agreement, as previously amended, shall remain the same. **Remainder of this page left blank intentionally** SIGNATURE PAGE TO FOLLOW Page 1 of 2 CAO t6J4 3 IN WITNESS WHEREOF, the Parties hereto, have each, respectively, by an authorized person or agent, have executed this Amendment on the date and year first written above. ATTEST: Crystal K. Ki el, Clerk of Circuit Court BOARD OF COUNTY COMMISSIONERS and Co tr II r COLLIES / Y, F ORIDA By: By: j �• airman's Rick LoCastro, Chairman Dated: :f' Q 3 signature only (SEAL) Contractor's Witnesses: CONTRACTOR: Phoenix Business, Inc, dlbla Phoenix Business Consulting First Witness By: Derik Simovart Sign 1'Typ e/print witness nameT Hanif Sarangi, President TType/print signature and titleT of itn Sara ckuly Mw y I� ao23 TTypeirint witness nameT Date Ap d as to For nd Le lity: Deputy County Attorney S co Q tat Print Name Page 2 or2 1 I KO 1 11 I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I •V. • 1 6 J 4 • PHOENIX BUSINESS CONSULTING Phoenix Business Consulting SAP SuccessFactors Exhibit A-2 Statement of Work for Collier County, Florida Ccre-r County Aprill8th , 2023 CAO IFF4i' ' 4410 ;"6 410 111111.11111111111111.1111111111111.11IL*AL h i6 SAP PHOENIX Table of Contents Our Commitment 3 1 Overview 4 2 Understanding and Recommendation 4 3 SAP SuccessFactors Scope 5 3.1 Employee Profile 5 3.2 Employee Central 5 3.3 Data Migration Scope for Employee Central 9 3.4 SAP Time and Attendance by Workforce Software Scope 10 3.5 SAP Time and Attendance by Workforce Software General Assumptions 11 3.6 SAP Time and Attendance by Workforce Software Implementation Assumptions 12 2.4 Integration Scope 12 3.5 Single Sign-On 13 3.6 Training and Change Management 14 4 Project Approach 15 4.1 Schedule SAP SuccessFactors 15 Table 1: High Level Project Schedule 15 4.2 Activities 16 4.3 Deliverables 18 4.3.1 Acceptance Procedure 18 4.4 Assumptions 19 5 Project Structure, Roles& Responsibilities 20 5.1 Roles and Responsibilities 20 5.1.1 Project Team Roles 20 5.1.2 Project Activity RASCI 21 5.1.3 Client Resource Committments 22 6 Commercial 23 6.1 Implementation Costs 23 6.2 Total Costs and Cash Flow 23 6.3 Standard Rate Card for On-Demand Services 24 6.4 Invoicing and Banking Info 24 6.5 Signatures 25 Collier County:SOW for SAP SuccessFactors Page 12 CAO Implementation Services 1 b J 4 PHOENIX Our Commitment 03/8/2023 Attn: Collier County Clerk of the Circuit County Finance Department 3299 Tamiami Trail East, Ste. 403 Naples, Florida 34112-5746 Dear Collier County, Phoenix Business, Inc., DBA Phoenix Business Consulting (Phoenix) is pleased to present to Collier County our Statement of Work (SOW) for your Human Experience Management (HXM) project. Phoenix offers world-class implementation, integration, and on-going support services for SAP SuccessFactors. The Phoenix Team is excited at the opportunity to deliver your project. Phoenix brings a perfect blend of value, experience, and expertise to implement the functionality/scope requested. Choosing Phoenix as your implementation partner, Collier dramatically reduces implementation risk and takes advantage of our extensive implementation experience and capabilities in SAP. You have my personal assurance that I will do everything possible to make certain that your initiative is an immediate and long-term success. Please do not hesitate to contact me at (512) 557-4731 if you have any questions or require any further assistance. We look forward to working with you and partnering together to achieve your goals. Respectfully, .". ----. 07,4„,.1,77 Hanif Sarangi, President, Phoenix Business Consulting rfpteam@phoenixteam.com Collier County:SOW for SAP SuccessFactors Page 1 3 �� Implementation Services SAPt6J4 .* PHOENIX 1 Overview This Statement of Work ("SOW") is prepared by Phoenix Business, Inc dba Phoenix Business Consulting of 6021 Midnight Pass Rd., Suite 3 Sarasota, FL 34242 ("we", "Phoenix Business Consulting" or "Phoenix") for Collier County with a principal of business at 3299 Tamiami Trail East Ste.403 Naples, FL 34112-5746, or also collectively known as ("you", "Client", "Customer"). The Client is seeking the assistance of Phoenix to implement the SAP SuccessFactors ("SuccessFactors") HXM system ("Project"). This SOW defines the services, schedule, and cost for this Project. 2 Understanding and Recommendation Collier County is currently undertaking a significant transition with their HRIS strategy. Collier County is currently utilizing SAP ECC for HR and Payroll which is comprised of manual processes, and limited Employee and Manager self-service. Collier is in the process of contracting SAP SuccessFactors as the HR software of choice moving forward to streamline and enhance their HRIS landscape. This transition will promote quantitative benefits for Human Resources, Managers, and Employees. Collier County will begin their HRIS journey with the implementation of Employee Central for core HR and Workforce Software for time and attendance. Phoenix is pleased to have the opportunity to continue our partnership for this project and beyond. After having the opportunity to meet with the Collier team our recommendation is to start with Employee Central and Workforce Software which will benefit Client by providing a strong leading practice starting solution for the implementation. With the technology solution in place, Phoenix will also provide Collier County with knowledge transfer, and testing services to digitally enable and promote awareness within the business.We look forward to continuing our partnership with the County for this exciting new phase. Collier County:SOW for SAP SuccessFactors Page 14 CAO Implementation Services • PHOENIX 3 SAP Success Factors Scope 3.1 Employee Profile Item In Scope Comment/Characteristics/ Outcomes Employee Profile • Configure employee profile standard fields along with fifteen (15) custom fields • Configure additional custom fields using extended user data so as not to be limited to the standard 15 custom fields • Configure standard background elements (portlets) based on modules being configured • Configure People Profile blocks • One Live Profile: Standard Views and applicable Role Based Permission (RBP) settings to govern different access levels per user population • Default company system &logo settings • Default password policy&login settings as well as SSO • Enable standard mobile settings • Client will provide a color palate; Login background image and system background image and Phoenix will draft an initial theme. Phoenix will conduct up to a 1 hour walk through of the theme manager tool and Client draft theme. Client will be responsible for configuring the theme after the walkthrough. • Upload one(1)company logo • Configure standard homepage tiles (based on module being configured) • Enable directory to allow searching for employees • Activation of standard dashboards and tile-based dashboards. Phoenix will conduct up to a 1 hour walk through of the construction of a simple custom dashboard and how to publish. Client will be responsible for configuring and maintaining any custom dashboards added. 3.2 Employee Central Item In Scope Comment/Characteristics/ Outcomes Collier County:SOW for SAP SuccessFactors page 15 CAO Implementation Services 6JSAP PHOENIX Data Models • Corporate Data Model • Country Specific Field Corporate Data Model • Succession Data Model • Country Specific Field Succession Data Model Picklists • Standard Picklists including additional custom picklists as required • Enablement and configuration of the Picklist Center Metadata Framework(MDF) • Standard MDF Objects ✓ • Up to fifteen (15) Custom MDF Objects including workflows(if applicable)and related RBP permissions as defined by Customer. Business Rules • Up to thirty(30)custom Business Rules(Medium complexity) • Up to twenty(20) custom transaction workflow rules/Transaction workflow rules will also come ✓ with standard notifications. • Ten (10)event-based alerts with standard notification alerting users Events • Up to thirty(30)Standard HR Events ✓ • Up to fifty(50) Event Reasons including configuring associated workflow rules(see Business rules above) Collier County:SOW for SAP SuccessFactors page 16 CAO Implementation Services PHOENIX Position Management • Position Org Chart • Company Structure Overview • Standard Position object fields and up to fifteen ✓ (15)custom fields. • Position to Job Information synchronization • Position copy • Position management settings One(1)Position management specific approval workflowPersonal information Section • Biographical Information • Personal Information • Country Information • Contact Information • Home Address • Additional Employee Information • National ID • Emergency Contacts • Payment Information • Dependents • Work Permit Employment information Section • Job Information • Compensation Information • Employment Details • Employment Details(Termination) • Job Relationships • Additional Payments and Deductions Collier County:SOW for SAP SuccessFactors ° Page 17 CA® Implementation Services 4 PHOENIX Additional items • The SuccessFactors Mobile App will be activated with the following features: o Organizational Chart and people search o Employee Profile(as per role-based permissions) o Employee Self Service o Manager Self Service o Workflow approvals ✓ o Employee data changes o Client will provide a color palate and logo for the Mobile application. Phoenix will draft an initial Mobile theme within what capability SAP SuccessFactors provides. Client will be responsible for configuring the theme after initial setup. Contingent Workforce • Enable Contingent Workforce. • Complete configurations related to Contingent Workforce. Clientwill be responsible for defining any additional fields needed for the Work Order ✓ object,vendor information, and any additional fields that are required to support the business needs within the portlets available for Contingent Workforce. Phoenix will configure the additional fields defined. • Set up the contingent worker field and the dynamic group filter. • Provide knowledge transfer on required import templates for data migration as well as support the tasks to upload the data Collier County:SOW for SAP SuccessFactors Page 18 cAO Implementation Services SIP io ,! a * � PHOENIX 3.3 Data Migration Scope for Employee Central For data conversion to Employee Central, pre-formatted CSV files for Employee data migration will be provided to load the relevant employee data into SuccessFactors HCM from SAP S/4 HANA. Phoenix will facilitate technical workshop(s)to determine the information/fields to be migrated in detail. Please note that there are load order dependencies, and complex dating requirements around transforming SAP S/4 HANA data into SAP SuccessFactors Employee Central data for the initial loads. Phoenix will provide Client with the required templates/format of the data required,to enable Client to populate for data loads into SuccessFactors. Please note,templates will be adjusted during the implementation to allow for configuration changes. Client will be responsible for undertaking the required data extract,cleanse, and conversion activities to allow upload into SuccessFactors. Phoenix will upload the data load via SFTP or Admin Tools, monitoring load jobs and troubleshoot any issues encountered. The high level SuccessFactors Employee Central data migration process is shown in the diagram below: Client will allow sufficient internal resources to prepare for: • Data extracts from the legacy system/s • Field mapping • Transformation of legacy data into required format and mapping • Population of data load templates • Error handling during load process • Validation of data post load Client will be responsible for: • Providing the legacy data in the correct format to load into the SuccessFactors system • Reconciliation of migrated data for each migration run • Client business owners will be responsible for sign-off of the data prior to initiation of any business processes or transactional processing within Employee Central. Phoenix will provide Client with the SuccessFactors standard file templates/formats for modules in scope of this SOW. Phoenix and Client teams will discuss business rules and data mapping requirements so that Client can deliver flat file(s) in SuccessFactors-specified standard CSV format. It will be Client's responsibility to supply the data required in the correct format. Client will be responsible for data extraction,verification and cleansing during all phases of the project and on- going. Phoenix will train Client on how to perform future file uploads. Collier County:SOW for SAP SuccessFactors page 19 Implementation Services AO SAP 16J4 1 • PHOENIX Item In Scope Comment/Characteristics/ Outcomes Employee data: • Current records only for active employees • 12 months of terminated employees (including any terminated employees who have received a paycheck or W2C in the last 12 months) Current and historical (as in scope above)employee data will be uploaded to SuccessFactors Employee Central using Standard SuccessFactors Admin Tools. 3.4 SAP Time and Attendance by Workforce Software Scope Item In Scope Comment/Characteristics I Outcomes Regulations Standards: • Federal regulations • State Regulations Florida 11( Policy Profile Group • Timesheets frequency, pay frequency Policy Profile and Roles • The policy profile links an employee's job to the business rules governing that job. Every assignment is connected to one and only one policy profile. Policy profiles also group employees for payroll processing. • Four(4) policy profile included • Additional roles to the standard ones. Which defines what a user can do personally (edit own timesheet, login) and what a user can do to other employees' data in the system (edit employee's timesheet, approve employee's time off request). 2 Additional roles included Collier County:SOW for SAP SuccessFactors Page 110 CAO Implementation Services 6J4 PHOENIX Time Off Banks Nt- o Additional Custom Time Off Banks Time off banks calculate and track accruals of leave time and usage of that leave time.A time off bank tracks the hours an employee has available to use. o Five(5) additional custom time-off banks included Messages o Additional Custom Exception Messages/ Notifications(16) o Informational message that appears on the timesheet. o Additional Custom Pay Premiums Custom Pay Premiums o 16 Additional Custom Pay Premiums o Extra pay/entitlement for working specific conditions or situations o FMLA/FLSA(if applicable) 3.5 SAP Time and Attendance by Workforce Software General Assumptions • County of Collier will allocate the key project team members, from the HR, Finance, Scheduling, and Business • Operations to actively participate throughout the project phases. However, the project could be at risk if • contributions are insufficient.This may comprise the timeline, scope and end goal of the project as the • resources do not meet the assumptions made during project planning. • Any effort estimates based on provided documentation. • Any extension to project activities at the request of County of Collier will be at an additional cost. • Project team members from County of Collier and Phoenix will be available throughout the project lifecycle. • Project Team will identify delegates if they are unable to attend workshops or approve deliverables. • Phoenix will have access to County of Collier project team members throughout the project lifecycle. • Services will be a blended approach or on-site and virtual delivery. • Data mapping, data extraction and data cleansing is County of Collier's responsibility. • All relevant information (e.g., collective agreements, policies, etc.) and historical information (e.g., reports, etc.) needed will be obtained and available to be used when conducting the project. Collier County:SOW for SAP SuccessFactors page 111 CAO Implementation Services SAS � b � � , PHOENIX 3.6 SAP Time and Attendance by Workforce Software Implementation Assumptions 1. On-site requirements workshops will be based on the pre-filled BRD documented based on CBA's and County Provided Documentation a. Follow up workshop to review the CBA analysis. b. County of Collier to review the requirements and consult internally during the time between the Requirements Workshops. 2. Realize phase will be comprised of 2 Iterations by which the goal of the iterations is to provide County of Collier with greater visibility into the configured environment in order to clarify any missed requirements prior to the start of User Acceptance Testing (UAT). a. Iteration 1 (4 week period) will provide a walkthrough of the functionality and configuration, by which County of Collier will then develop test scenarios. b. Configuration for Iteration 2 will occur simultaneously as County of Collier reviews functionality during Sprint 1 as part of the test scenario development. c. Iteration 2 (4 week period) will provide a walkthrough of the functionality and configuration, by which County of Collier will then develop test scenarios. 3. Test Approach, in the Validate Phase, will be comprised of the following phases: a. Business Scenarios tests: County of Collier to execute test scenarios based on their business realities. The purpose of this process is to validate key business rules and core functionality. b. Integrated tests: perform end-to-end tests based on the employee lifecycle(i.e.,from input in schedule to time &attendance to output in payroll), by which integrations will also be validated. c. Parallel test:Time day from a prescribed pay period is simulated in WFS for a significant sample size. This will allow for a comparison of the results between Workforce and the incumbent solution. 4. Solution and Requirements documentation:The solution as designed and agreed is comprised of three documents officially approved by County of Collier before the go-live and which describes the Solution: a. Business Requirements Document (BRD) b. Solution Design Document(SDD) c. Integration Solution Design (ISDD) 2.4 Integration Scope Comment/Characteristics/ Source System Target System Outcomes SuccessFactors Employee Central SAP S/4 HANA Replication; OM/PA SuccessFactors Employee Central Workforce Software Demographic,Time Objects, HR master data Workforce Software SAP Payroll Payroll export Single Sign-On to SAP Single Sign-On OAuth 2.0 SAML Azure Active Directory Provider SuccessFactors Collier County:SOW for SAP SuccessFactors page 112 CAO Implementation Services SAP1. 6J4 PHOENIX Integration Scope Pre-requisites I Assumptions • SAP Cloud Platform Integration (CPI)will be the middleware tool for developing the integrations. Integration Center can be used to expedite development where the business requirements allow.This option will be explored once the integration requirements are defined. • Standard functionality/content delivered by integration packs will be used where they are available at the time of development.This will be reconfirmed during detailed design. • Client will be responsible for providing subject matter experts, record layouts and business requirements for each integration. Legacy/Vendor specifications and sample files are required for each integration • Client is responsible to expedite the business requirements gathering. The Phoenix Technical Lead assigned to the project will request information and meetings associated with each of the integrations listed. It's important that the meetings and information requests be addressed quickly as to not delay development and negatively impact the project timeline. • All integrations that produce a file will produce a file in the provided record layout.The file will be placed on the provided FTP server. It is assumed that standard SFTP as provided by SAP SuccessFactors will be used.. It will be the responsibility of Client to process the file into the receiving system using the provided utilities/ import processes • Each integration above identifies an interface to a single instance of the software. If any integration requires a connection to multiple versions of the software indicated, that has not been included in the estimate • Client is responsible for any Infrastructure or deployment changes required to support he implementation of SuccessFactors within their existing systems infrastructure landscape. • Phoenix is not responsible for any defects in the middleware or any standard integration • For all integrations&enhancements, detailed requirements will be gathered during the Prepare and Explore phases of the implementation. Client will need to review and sign off on the requirements document before commencement of any development. Integrations and Enhancements may require enablement of standard business objects by SAP to be consumed by partners such as Phoenix. Phoenix does not have any control over this process and consequently,the timeline.The timelines provided in this proposal are based on estimates and are subject to change based on the actual time taken by SAP for this process. Client is responsible for installation of add-on software and implementation of OSS Notes to the existing S/4 HANA application to facilitate integration. 3.5 Single Sign-On • SAP SuccessFactors supports multiple methods to facilitate Single Sign On with external applications. As part of the implementation, Phoenix will implement an IdP (Identity Provider) initiated SSO where SuccessFactors will be configured as the Service Provider to support SSO using SAML 2.0 (the preferred option for implementing SSO). Client would be responsible for configuring the Identity Provider (IdP)to Collier County:SOW for SAP SuccessFactors Page 113 CAO Implementation Services 1 v J 4 F AP 6 PHOENIX facilitate the SSO with SuccessFactors using SAML 2.0 and also publish the necessary links to direct the user to SuccessFactors. • For the implementation of SSO, SuccessFactors will provide Client with: o Company ID o X509 Digital Certificate (used to send encrypted message to SF and verify the signed message from SF) o SF Entity ID o Consumer Service URL o Global Logout Response Handler URL • Client will provide SuccessFactors with: o X509 Digital Certificate (used to verify the SAML message sent to SF) o IdP Entity ID (SAML Issuer) o Global Logout Service URL • If SSO needs to be implemented using any other method (in lieu of SAML 2.0), it would constitute a change request and an assessment on the effort (time and cost) would need to be conducted along with Client. 3.6 Training and Change Management 11111111111111111111:1111111111111In Scope Comment/Characteristics/ Outcomes Train the Trainer Approach • Phoenix Team will provide a train the trainer ✓ approach for core Collier County training team. • Phoenix will provide module specific SAP training material and enablement on SAP training applications to include SAP ALC and SuccessFactors Customer Community. Organizational Change Management ✓ • Stakeholder Analysis • Communication templates • PROSCI methodology to change Collier County:SOW for SAP SuccessFactors Page 114 CAO Implementation Services 1 b 14 ' 6 PHOENIX 4 Project Approach 4., Schedule SAP SuccessFactors Based on a tentative start date of February 2023 the Phoenix Team in mutual agreement with Collier County proposes a kickoff of SAP SuccessFactors Implementation for modules Employee Central and Workforce Software Time and Attendance with an estimated go-live date of January 1st, 2024. Each module specific deployment will include 1 month of post go live support known as Hypercare. Collier Counties populations will go-live based on a phased approach depicted in the table below. Solution Population Estimated Go-live SAP SuccessFactors Employee Central ll Clerk 10 months January 2024 SAP SuccessFactors Employee Central Board 10 months January 2024 SAP SuccessFactors Time and Attendance by I µ Clerk 10 months , January 2024 11 Workforce Software i,l I Ir SAP SuccessFactors Time and Attendance by Board 13 months April 2024 !, i+ Workforce Software 'I Table 1: High Level Project Schedule x✓"t i1� t ' Fr § .,, m ,ips. 9 �a , �t, � s k �� , ii , � '" , '' ,- ,,. ",. .., ,� ° ,«, . . .M 00 zYY Project Start Project Go live Project Go live ) H Y P t R C a a t Teator e'llU'r Aexoptance Tertin�(UAT)-End To '; End Kick-,Off/Workshops Iteration Playback iteration Playback iteration Playback I Oata.Atemnon ►eeNlkd Taatleit Training Project bb rOrr r.. ,, .r ;max e ix Collier County:SOW for SAP SuccessFactors 1 Page 115 CAO Implementation Services l SAP 1bJa PHOENIX 4.2 Activities As seen in the table below,the following table outlines the key activities that will occur and the work products that will be delivered for each phase of the implementation. Table 1:Key Project Activities by Phase Project Plan Key Activities Work Products PHASE: PREPARE • Project kickoff • Finalized project plan • Finalize project plan • Provisioned test tenant Accelerators: p j • Project plan template • Allocate resources • Data migration scope& • Data migration scope and • Verify project scope plan planning template • Organization structure workshop • Solution design document— • SAP best practice • Data migration workshop scope, organization processes&diagrams • Business scenario reviews structure, business process • Solution design document • Integration requirements gathering documentation template • Conduct Project Verification checkpoint • Integration design document MILESTONE: Solution Walkthrough and High-Level Demo Goal: Client signs off agreeing to the scope to be delivered during implementation of SAP SuccessFactors. When necessary, a change order may be executed for out-of-scope items. For the avoidance of doubt, the acceptance procedures outlined in this SOW shall apply to this "Project Verification Milestone." PHASE: Explore • Create and activate organization • Solution acceptance Accelerators: structure document • Solution walkthrough plan • Conduct iterative workshops • Key User Training plan template • Configure test system • Standard solution test cases • Issue, Action & Risk log • Migrate/setup sample data • Documentation& • Key User Knowledge • Conduct Solution walkthrough Knowledge Transfer of Transfer Training plan • Gap identification & resolution system configurations made template • Conduct Solution Acceptance • Standard test plan • Develop/configure integrations • Prepare Key User Knowledge Transfer Training plan MILESTONE: System Readiness Acceptance for Testing Goal: Client signs off agreeing that the business scenarios demonstrated meet the requirements to be delivered during the project and that all configuration questions have been addressed. For the avoidance of doubt, the acceptance procedures outlined in this SOW shall apply to this"Solution Acceptance Milestone." Collier County:SOW for SAP SuccessFactors Page 116 CAO Implementation Services t J 4 PHOENIX PHASE: Realize (TEST) • Assist in data migration testing • Recordings of Key User Accelerators: • Conduct key user training Training (if available) • End User Training plan • Conduct solution walkthrough for • Finalized cutover plan guides integrations • Provisioned production • Work Center User List • Assist in end-to-end process testing and tenant template integrations testing • Documented test plan, test • Transition plan template • Conduct cutover workshop cases& test results • Prepare cutover plan • Perform mock cutover • Conduct Readiness Acceptance checkpoint • Request production tenant MILESTONE: Cutover Goal: Client signs off agreeing that the systems, data, and people are ready to execute the cutover to the production environment. For the avoidance of doubt,the acceptance procedures outlined in this SOW shall apply to this "Readiness Acceptance Milestone." PHASE: DEPLOY • Facilitate end user training (conducted • Cutover to live production Accelerators: by key users) system • Handover to support • Deploy integrations to production • Solution Launch checklist system • Migrate master data • Assist in validation of cutover • Conduct the handover to support • Application Go-live MILESTONE: Live system Goal: Client signs off agreeing that the cutover is complete, and the organization is prepared to use and support the new solution. For the avoidance of doubt,the acceptance procedures outlined in this SOW shall apply to this "Go Live" process. PHASE: SUPPORT • Live production system Issue Resolution Accelerators: • User Support • Phoenix Premium • Monitoring Transactions and Support • Operations o See project schedule MILESTONE: Project Completion Goal: Ensure the system is working as designed. The table below shows the tentative key meetings and durations during the implementation for planning purposes. The actual meetings will be determined after project kickoff upon Client's written approval. These meetings may be conducted onsite or remotely at Clients discretion. Collier County:SOW for SAP SuccessFactors Page 117 CAO Implementation Services 16J4 SAP 5 - PHOENIX Table 2: Key Meetings and Durations Project Activity* Duration Project Kickoff& Business Process Workshops 10 days Solution Walkthrough 5 days Key User Training 7 days Go-Live and Support 60 days *The above duration times are estimates only. As part of the Fixed-Bid, Phoenix will work with Client to ensure adequate time is allocated for each activity's successful completion. 4.3 Deliverables The following table identifies the deliverables for this Project: Table 3: Project Deliverables ID# Deliverables Project Phase 1 Project Schedule Prepare Phase 2 Project Standards and Procedures Prepare Phase 3 Preliminary System Design Document Prepare Phase 4 Integration Specification Prepare Phase 5 Key User Training Plan Explore Phase 6 Risk, Issue, Action & Defect log Explore Phase 7 Production Cutover Plan Realize Phase 8 Training Documentation Realize Phase 9 Configuration Signoff Documentation Realize Phase 10 Final System Design Document Deploy Phase 11 Fully Functional SuccessFactors system Deploy (Go-Live) 12 Project Closure Report Deploy (Go-Live) 4.3.1 Acceptance Procedure Any documentation that will require Client's review and approval will be completed within five (5) business days after submission by Phoenix. In the case of milestones/deliverables, if Client does not respond within five (5) business days of the submission of milestone/deliverable(s), the milestone/deliverable will be deemed complete. Phoenix may raise invoice after this date for a milestone-based billing (as applicable). Any changes to the deliverable (document) after this date will be mutually agreed to by both parties. Collier County:SOW for SAP SuccessFactors Page 118 CAO Implementation Services • F PHOENIX 4.4 Assumptions The schedule and implementation services for this project are based on the following assumptions: Organization Alignment • Assumes client will adopt SAP SuccessFactors leading practices, customer will present pragmatic mindset to cloud development, configuration and deployment not requiring custom code development of SF solution. • Client will be responsible for providing appropriate workspace and internet connectivity while onsite, to ensure that work products are met according to the project timeline.This includes key milestones of the project, including but not limited to kickoff, solution design workshops and user acceptance testing. • Customer will assign an internal,SAP SuccessFactors Project Manager with adequately allocated time and authority to assign project tasks and ensure timely completion. • Client will make available any employees from IT, or 3 parties such as contractors, bank representatives etc. in a timely manner, if required. • It will be Customer's responsibility to perform testing and provide feedback on test results in a timely manner. Failure to test and provide test result feedback in a timely manner may jeopardize the overall project timeline and target Go-Live date. Excessive delays in performing testing may result in a change order due to excessive project timeline overrun. Implementation Methodology • Phoenix is not responsible for gaps in product functionality resulting from required customer processes. Client understands these items may require submission of enhancement request with SAP. • Assumes a 12-month timeline • Customer agrees to onsite presence for key milestones (e.g., project kickoff, user acceptance testing and go-live) • Phoenix will provide sample test scripts to Client. Client is responsible for updating, managing, and maintaining all test scripts related to project deliverables across the project lifecycle. • Project will follow Train the Trainer (TTT) methodology for project team members only, training outside of project team administrators is out of scope. Phoenix can provide additional training services at an additional cost through the change order process. • All data migration activities including, but not limited to determination of strategy, extraction, cleansing, population of migration templates and loading of data will be Client's responsibility. • Client will be responsible for accuracy of data and for any errors that arise during the data migration process. • Migration of Employee Master data and company foundation data will be loaded into SAP SuccessFactors through the SAP SuccessFactors .csv files or integration. • Client is responsible for all data migration activities from non-SAP applications. May require additional PMO alignment internally with CLIENT and considerations on project timeline and subject to change request process. • Client is responsible for installing any add-ons required on existing SAP S/4 HANA applications to facilitate the SuccessFactors integration. • Client is responsible for setting up all cloud connections and related configurations for interfacing with legacy S/4 HANA application. • People Analytics and associated stories are out of scope for this engagement. • Integration with 3rd party need additional scoping. • Customer responsible for all configuration on legacy systems and applications. • Custom processes to support legacy applications or external processes are out of scope. • SAP SuccessFactors scope assumes 2,500 Employees in United States. Collier County:SOW for SAP SuccessFactors Page 119 CA® Implementation Services SAPt6J4 , PHOENIX • Assumes deployment of SAP SuccessFactors in US English only. • Assumes three (3) iterations of design for Employee Central. • Unit testing is expected to be completed within one(1) business week. Unit testing is not user acceptance and designed to test individual configuration changes during each iteration. • Data extraction for downstream processing requires further scoping • Additional changes after solution design acceptance/signoff are subject to change request and additional costs incurred by the customer. • Custom reporting, analytics or processing for related downstream systems is out of scope. • Customer agrees that any timeline or project extension resulting from CLIENT will be subject to change control process and additional cost. • Areas not explicitly called out above are to be considered out of scope for this engagement. Integrations & Enhancements: • For all integrations & enhancements, detailed requirements will be gathered during the Prepare and Explore phases of the implementation. Client will need to review and sign off on the requirements document before commencement of any development. • Assumes two bi-directional demographic interfaces only. • Client will provide subject matter expert and technical SAP project resources for legacy systems development. All configuration or development relating internal or legacy systems is responsibility of the client.This includes custom developed applications. • Integrations and enhancements may require enablement of standard business objects by SAP to be consumed by partners such as Phoenix. Phoenix does not have any control over this process and consequently,the timeline.The timelines provided in this proposal are based on estimates and are subject to change based on the actual time taken by SAP for this process. • This project references processes and requirements provided by client through the detailed RFP process. Any processes or requirements not specifically called out as yes or custom are not expected to be in scope for this engagement. • Additional costs incurred with staffing or legacy providers are client's responsibility. • Client is responsible for installation of add-on software and implementation of OSS Notes to the existing S/4 HANA application to facilitate integration. • Client agrees to follow basic SAML configuration on legacy network provider through SAP IAS (Identity Authentication Service). Acceptance Procedure Any documentation that will require Client's review and approval will be completed within five (5) business days after submission by Phoenix. In the case of milestones/deliverables, if Client does not respond within five (5) business days of the submission of milestone/deliverable(s), the milestone/deliverable will be deemed accepted. Phoenix may raise invoice after this date for a milestone-based billing (as applicable). Any changes to deliverable documentation after this date will be mutually agreed to by both parties. 5 Project Structure, Roles & Responsibilities 5.1 Roles and Responsibilities 5.1.1 Project Team Roles The following table describes the roles and responsibilities of the key stakeholders in this project. Collier County:SOW for SAP SuccessFactors P a g e 20 CAO Implementation Services SAP J PHOENIX Table/I: Project Team Roles/Responsibilities Role Primary Responsibilities I Phoenix Project Executive • Makes critical business decisions • Approves change requests • Participates in Steering Committee meetings ri Client Project Manager ■ Owns and drives the project,jointly with the Phoenix Project Manager • Coordinates Key Users Phoenix Project Manager ■ Owns and drives the project,jointly with Client Project Manager • Coordinates with Consultants • Manages communication with other parties (SAP Support, Service Center) Client Business Process • Provide business process expertise and make decisions Owners ■ Perform required data migration activities • Perform the fine-tuning, testing and cutover activities,jointly with Phoenix Consultants Phoenix Consultants • Conduct workshops • Perform the fine-tuning, testing and cutover activities,jointly with the Key Users • Gather requirements, develop customizations/integrations, and test jointly with the Key Users 5,1.2 Project Activity RASCI The following table describes the roles and responsibilities of the project team mapped to each project activity: Table 5: Project Activity RASCI Matrix Key Work Activity Client Phoenix Business Scenario Review Sessions R/S/C A/R Solution Design Document C/S/I A/R Business Requirement Document (T&A) A/R C/S/I Integration Solution Design Document A/R C/S/I (T&A) Project Verification A/R C Fine-tuning &Solution Walkthroughs C/S A/R Solution Acceptance Document C/S/I A/R Solution Acceptance A/R C Key User Training C/S/I A/R Test Scripts A/R/S C/S/I User Acceptance Testing (UAT) A/R/S C/S/I Readiness Acceptance A/R C End User Training A/R/S C/S Collier County:SOW for SAP SuccessFactors Page 121 CAO implementation Services 16J4 SAP 6 PHOENIX Key Work Activity .IIIEMIIIIII- ,. ,. Phoenix_ Data Migration A/R/S R/C Go Live A R R= Responsible, more than one team can be Responsible; but only one can be Accountable A=Accountable, only one party can be accountable S=Support C=Consulted I = Informed 5.1.3 Client Resource Committments Based on our experience with similar projects, we believe that the Client resource commitments, at a minimum, should include: Table 6: Client Resource Commitments Resource Time Comment Prepare Gather data requirements for migration Key Users/ Business Process Key user (decision maker) per templates Owners functional area for 5 days Data Analysis, cleansing and template Key Users/ Business Process Ongoing effort. Client needs to population for data loads Owners assign a person (50%) depending on how much cleansing is required 11 Provide Test Data -Small data sets for Key Users/ Business Process Subset of products, Clients, and I! demonstration Owners supplier(8 hrs. per data set) 1 Integration requirements gathering Key Users/ Business Process Technical SME; workshop identifying Owners technical landscape and system requirements. (12 hrs) d Review Deliverables Project Manager/ Business Approximately 1.5 hrs. for each l Process Owners deliverable E Explore i Preliminary Training Documentation Key Users/ Business Process Approximately 4-8 hrs. per il Owners functional area. I' Conduct Iterative Workshops KeyUsers/ Business Process Keyuser/decision makers per �. Owners functional area; module specific 8hrs per session. Review Deliverables Project Manager/ Key Users Approximately 1.5 hrs. for each / Business Process Owners deliverable Realize Conduct testing and document test Key Users/ Business Process Phoenix will deliver approximately scripts pass Owners 20 key processes per workstream. Client should allocate approximately 5-20 hrs. per process Collier County:SOW for SAP SuccessFactors Page 122 " ,,.) Implementation Services " 1 b J 4 • PHOENIX Task Resource Time Comment Provide mock HR cutover data Key Users/Business Process Client needs to provide data on EE Owners master data,future effective dated EE transaction data Finalize master and HR cutover data Key Users/Business Process Client needs to provide supporting Owners foundation data and EE master data. Review Deliverables Project Manager/ Key Users Approximately 1.5 hrs.for each / Business Process Owners deliverable Launch Go Live Entire joint Project Team Full time use of system. 6 Commercial 6.1 Implementation Costs Table 10: Implementation Costs for SAP SuccessFactors SAP SuccessFactors Implementation Costs SAP SuccessFactors and Workforce Software Phase 1 Fixed Bid Implementation Costs* $1,768,251 Integration Costs Included TOTAL Due $1,768,251 6.2 Total Costs and Cash Flow Table 11: Table of Cash flows *Travel costs have been included in this agreement in the amount of$100,000. If additional travel is requested, it will be mutually agreed upon during course of implementation. Table 12:Implementation Services and Payment Schedule Phase 1 and 2 Milestone Deliverable Payment M1 Project Kick-Off $166,825 M2 Iteration 1 Completion $417,063 M3 Iteration 2 Completion $417,063 M4 Iteration 3 Completion $417,063 M5 User Acceptance Testing Completion $166,825 M6 Go-Live $83,412 M7 M8 Estimated Travel Costs $100,000 TOTAL Due $1,768,251 *Milestones to be billed after completion and sign-off where required. 123-PRC-05133/1785774/1J Collier County:SOW for SAP SuccessFactors Page I 23 Implementation Services C� O SSAP 1 bJ4 PHOENIX 6.3 Standard Rate Card for On-Demand Services Table 15: Phoenix Standard Rate Card Role Hourly Rate * (USD) Project Executive 150 Project Director/ Manager 150 Technical Solutions Architect 150 Integration Architect 150 Functional Consultant 140 Transformation Architect 285 Transformation Lead 220 SAP Fiori Developer 80 Sr. Basis Consultant (Security) 120 Technical Developer 80 OCM Lead (Change Management) 120 * Note that our published rates are exclusive of travel, taxes, and duties. Travel must be approved by the Client. 6.4 Invoicing and Banking Info Phoenix accepts only wire transfers with online wire transfer. Confirmation Information may be sent to invoices@phoenixteam.com. Account Name: Phoenix Business, Inc. Bank Name: Wells Fargo Account Number: 5104180004 Routing Number: 121000248 Swift Code: WFBIUS6S Collier County:SOW for SAP SuccessFactors Page 124 Implementation Services C40 � 6J4 ti 00-1 1 PHOENIX 6.5 Signatures IN WITNESS WHEREOF, the parties have caused this SOW to be executed and entered Into by their respective duly authorized representatives as of the date set forth in our Master Services Agreement. Phoenix Business Inc. Collier County,Florida By: it Name: Hanff Sarangi Name: Rick LoCastro Title: President Title: Chairman ATTEST: Crystal K.Kin •I,Clerk of Courts ? &Comptroll By: t Dated: (SEAL) . .es as o airman's signature only Approve s to formQL l By: Scott R.Teach Deputy County Attorney (23-PRC•05:t33/d785774/1J Collier County;SOW for.SA1,.Successructors Page 125 o implenrcntatiorr Services 16J4 SCHEDULE B-1 BASIS OF COMPENSATION 1. MONTHLY STATUS REPORTS B.1.1. As a condition precedent to payment, CONSULTANT shall submit to the COUNTY as part of its monthly invoice a progress report reflecting the Project status, in terms of the total work effort estimated to be required for the completion of the Basic Services and any authorized Additional Services, as of the last day of the subject monthly billing cycle. Among other things, the report shall show all Service items and the percentage complete of each item. 2. COMPENSATION TO CONSULTANT B.2.1. For the Basic Services provided for in this Agreement, the COUNTY agrees to make the payments to CONSULTANT in accordance with the terms stated below. Payments will be made in accordance with the following Schedule; however, the payment of any particular line item noted below shall not be due until services associated with any such line item have been completed or partially completed to the COUNTY's reasonable satisfaction. Lump sum payments will be made upon the percentage complete. In no event shall such Time and Materials compensation exceed the amounts set forth in the table below. Tasks/Item Description Lump Sum Time and Materials Not-To-Exceed 1 Prepare Phase Completed $ $ 151,813.44 2 Design Completed $ $ 303,626.88 3 Custom Development Unit Testing completion $ $ 151,813.44 4 Integration Test (Cycle 1 & 2) completion $ $ 303,626.88 5 User Acceptance Test completion $ $ 151,813.44 6 Training Execution completion $ $ 151,813.44 7 Go-Live (Production Cut-over) $ $ 151,813.44 8 1 Month Hyper-care Stabilization Support $ $ 151,813.44 9 Reimbursables (Travel Costs) $ $ 140,111.20 $ $ 10 SAP Success Factors $ $1,768,251.00 $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ Total Lump Sum Fee $ Total Time and Materials Fee $3,426,496.60 GRAND TOTAL FEE $3,426,496.60 Page 18 of 30 PSA Single Project Agreement[2022 Ver I] CAO ' 6JI B.2.2. [UI* Time and Material Fees: The fees noted in Section B.2.1. shall constitute the amounts to be paid to CONSULTANT for the performance of the Basic Services. Direct Labor Costs mean the actual salaries and wages (basic, premium and incentive) paid to CONSULTANT's personnel, with respect to this Project, including all indirect payroll related costs and fringe benefits, all in accordance with and not in excess of the rates set forth in the Attachment 1 to this Schedule B. With each monthly Application for Payment, CONSULTANT shall submit detailed time records, and any other documentation reasonably required by the COUNTY, regarding CONSULTANT's Direct Labor Costs incurred at the time of billing, to be reviewed and approved by the COUNTY. There shall be no overtime pay without the COUNTY's prior written approval. B.2.2.1. Notwithstanding anything herein to the contrary, in no event may CONSULTANT'S monthly billings, on a cumulative basis, exceed the sum determined by multiplying the applicable not to exceed task(s) limits by the percentage the COUNTY has determined CONSULTANT has completed such task as of that particular monthly billing. n El* • . . be-pamd e- NS L�ANT-49f-4-14e peffer- a B.2.3.1 CONSULTANT shall submit, with each of the monthly status reports provided for under Section B.1.1 of this Schedule B, an invoice for fees earned in the performance of Basic Services and Additional Services during the subject billing month. B.2.4. For Additional Services provided pursuant to Article 2 of the Agreement, if any, the COUNTY agrees to pay CONSULTANT a negotiated total fee and Reimbursable Expenses based on the services to be provided and as set forth in the Amendment authorizing such Additional Services. The negotiated fee shall be based upon the rates specified in Attachment 1 to this Schedule B and all Reimbursable Expenses shall comply with the provision of Section 3.4.1 below. There shall be no overtime pay on Additional Services without the COUNTY's prior written approval. B.2.5. The compensation provided for under Section B.2.1 of this Schedule B, shall be the total and complete amount payable to CONSULTANT for the Basic Services to be performed under the provisions of this Agreement, and shall include the cost of all materials, equipment, supplies and out- of-pocket expenses incurred in the performance of all such services. B.2.6. Notwithstanding anything in the Agreement to the contrary, CONSULTANT acknowledges and agrees that in the event of a dispute concerning payments for Services performed under this Agreement, CONSULTANT shall continue to perform the Services required of it under this Agreement, as directed by the COUNTY, pending resolution of the dispute provided that the COUNTY continues to pay to CONSULTANT all amounts that the COUNTY does not dispute are due and payable. 3. SCHEDULE OF PAYMENTS B.3.1. Notwithstanding anything herein to the contrary, the CONSULTANT shall submit no more than one invoice per month for all fees earned that month for both Basic Services and Additional Services. Invoices shall be reasonably substantiated, identify the services rendered and must be submitted in triplicate in a form and manner required by the COUNTY. B.3.1.1 Payments will be made for services furnished, delivered, and accepted, upon receipt and approval of invoices submitted on the date of services or within six (6) months after completion of contract. Any untimely submission of invoices beyond the specified deadline period is subject to non- Page 19 of 30 PSA Single Project Agreement[2022 Ver.l] CAO 16J * payment under the legal doctrine of "laches" as untimely submitted. Time shall be deemed of the essence with respect to the timely submission of invoices under this Agreement. B.3.2. Invoices not properly prepared (mathematical errors, billing not reflecting actual work done, no signature, etc.) shall be returned to CONSULTANT for correction. Invoices shall be submitted on CONSULTANT's letterhead and must include the Purchase Order Number and Project name and shall not be submitted more than one time monthly. B.3.3. Payments for Additional Services of CONSULTANT as defined in Article 2 hereinabove and for reimbursable expenses will be made monthly upon presentation of a detailed invoice with supporting documentation. B.3.4. Unless specific rates have been established in Attachment 1, attached to this Schedule B, CONSULTANT agrees that, with respect to any subconsultant or subcontractor to be utilized by CONSULTANT for this Agreement or Additional Services, CONSULTANT shall be limited to a maximum markup of five percent (5%) on the fees and expenses associated with such subconsultants and subcontractors. B.3.4.1 Reimbursable Expenses must comply with §112.061, Fla. Stat., or as set forth in the Agreement, be charged without mark-up by the CONSULTANT, and shall consist only of the following items: B.3.4.1.1. Cost for reproducing documents that exceed the number of documents described in this Agreement and postage and handling of Drawings and Specifications. B.3.4.1.2. Travel expenses reasonably and necessarily incurred with respect to Project related trips, to the extent such trips are approved by the COUNTY. Such expenses, if approved by the COUNTY, may include coach airfare, standard accommodations and meals, all in accordance with §112.061, Fla. Stat. Further, such expenses, if approved by the COUNTY, may include mileage for trips that are from/to destinations outside of Collier or Lee Counties. Such trips within Collier and Lee Counties are expressly excluded. B.3.4.1.3. Permit Fees required by the Project. B.3.4.1.4. Expense of overtime work requiring higher than regular rates approved in advance and in writing by the COUNTY. B.3.4.1.5. Expense of models for the County's use. B.3.4.1.6. Other items on request and approved in writing by the COUNTY. B.3.4.1.7. The CONSULTANT shall bear and pay all overhead and other expenses, except for authorized reimbursable expenses, incurred by CONSULTANT in the performance of the Services. B.3.4.1.8. Records of Reimbursable Expenses shall be kept on a generally recognized accounting basis. B.3.5. The CONSULTANT shall obtain the prior written approval of the COUNTY before incurring any reimbursable expenses, and absent such prior approval, no expenses incurred by CONSULTANT will be deemed to be a reimbursable expense. Page 20 0130 PSA Single Project Agreement[2022 Ver.I] CAO 16J4 SCHEDULE B-ATTACHMENT 1 CONSULTANTS HOURLY RATE SCHEDULE Title _ Hourly-Rate Project Executive $150.00 Project Director/ Manager $150.00 Technical Solutions Architect $150.00 Integration Architect $150.00 Functional Consultant $140.00 Transformation Architect $285.00 Transformation Lead $220.00 SAP Fiori Developer $80.00 Sr. Basis Consultant $120.00 Technical Developer(embedded analytics) $80.00 OCM Lead $120.00 The above hourly rates are applicable to Time and Materials task(s) only. The above list may not be all inclusive. Additional hourly rates for other personnel may be added via an Amendment upon mutual agreement in advance and in writing by the parties. ❑ Page 21 of 30 PSA Single Project Agreement[2022 Ver.1] CAO