Source: https://docplayer.net/18002129-5126p-change-management-consulting-services-peoplesoft-financials-and-supply-chain-management-release-9-2-upgrade-1.html
Timestamp: 2020-01-19 23:52:25
Document Index: 316668537

Matched Legal Cases: ['art 1', 'art 1', 'art 2', 'art 3', 'art 1', 'art 2']

5126P - Change Management Consulting Services - PeopleSoft Financials and Supply Chain Management Release 9.2 Upgrade 1. - PDF Free Download
Download "5126P - Change Management Consulting Services - PeopleSoft Financials and Supply Chain Management Release 9.2 Upgrade 1."
1 Request for Proposal Finance and Corporate Services Department 5126P - Change Management Consulting Services - PeopleSoft Financials and Supply Chain 1. Introduction 1.1 The City of Richmond (the City ) invites responses to this Request for Proposal ( RFP ) from qualified Change Management Consultants interested in providing functional change management consultancy services for the City s PeopleSoft Financials and Supply Chain Management ( FSCM ) 9.2 upgrade. 1.2 The objective of this RFP is to provide the City with qualified Proponents capable of carrying out the work herein defined. The subsequent Proponent Submissions will form the basis for evaluation, potential interview and selection. 2. Definitions 2.1 Throughout this RFP the following definitions apply: a) City s Designated Representatives means the City s employees or representatives who are authorized in writing to deal with the Consultant on behalf of the City in connection with the goods, materials, equipment and services or to make decisions in connection with the Contract; b) City means the municipal corporation, generally known as the City of Richmond in British Columbia, Canada; c) Closing Time means the closing date, time, and place as set out in subsection 4.1 of this RFP; d) Consultant means the individual, partnership, corporation or combination thereof, including joint venturers, who or which is awarded a Contract who enters into a written Contract with the City to perform and to oversee the Work. e) Contract Documents means the purchase order, the Consultant s Proposal, the RFP and such other documents as applicable, including the City s purchase order all amendments or addenda agreed between the parties; f) Contract or Agreement means the agreement formed between the City and the Consultant as resulting from this RFP, executed by the City and the Consultant and evidenced
2 City of Richmond 2 3. Key Dates g) G.S.T. means the Goods and Services tax administered under the Excise Tax Act (Canada) and any successor tax or levy therefore in force from time-to-time; h) Lead Proponent is the Proponent whose Proposal, as determined through the evaluation criteria described in this RFP, provides the best overall value in meeting the requirements of the RFP, and with whom a Contract will be considered; i) Project means the scope of Work and Requirements described in this RFP; j) Proponent means an individual partnership, corporation or combination thereof, including joint venturers or a company that submits, or intends to submit, a Proposal in response to this RFP; k) Proposal or Submission means a proposal submitted by a Proponent in response to this RFP; l) Requirements means all of the specifications, requirements and services set out in the RFP that describes the general requirements that the goods, materials, equipment and services must meet and the Successful Proponent must provide; m) Response means the same as Proposal or Submission ; n) RFP or Request for Proposals means this request for proposals, inclusive of all appendices and any addenda that may be issued by the City; o) Services means the same as Work ; p) Successful Proponent means the same as Consultant and; q) Work or Works means the provision of all labour, services, materials, equipment, and any other necessary items and actions for the Successful Proponent to complete and perform its obligations in accordance with the Requirements and terms and conditions of the Contract. 3.1 In order to assist Proponents, following are the key target dates and Events with respect to this RFP process. Such dates are not guaranteed and may change based upon circumstances. 1. RFP issued February 20 th, Page 2
3 City of Richmond 3 4. Submission Details 2. Inquiries received up to March 4 th, Closing Date for submission of Proposals March 10 th, Evaluation and Award (if any) Mid-March (two) hard copies, and 1 (one) additional electronic copy (on a CD ROM or memory stick) of Proposals marked 5126 EOI Change Management Consulting Services - PeopleSoft Financials and Supply Chain Management Release 9.2 Upgrade and addressed to the Purchasing Section, will be received at the Information Counter, Main Floor, Richmond City Hall, 6911 No. 3 Road, Richmond BC V6Y 2C1, 3:00pm local time March 10th, Submissions received after this time may, at the City s discretion, be returned to the sender unopened. 4.3 Hard copy and electronic copy submissions should be identical to each other and in the same file format (i.e. Excel, word). 4.4 Proposals should be submitted in a sealed envelope or package, marked with the Proponent s name and the RFP title and number. 4.5 Amendments to a Proposal may be submitted if delivered in writing prior to the Closing Time in a sealed envelope or package, marked with the Proponent s name and the RFP title and number. 4.6 Proposals already delivered to the City may be withdrawn by written notice only, provided such notice is received at the Purchasing Services office prior to the Closing Time. 4.7 Any and all costs associated with the preparation and submission of the Proposal, including any costs incurred by the Proponent after the Closing Time, will be borne solely by the Proponent. 4.8 By submitting a Proposal, the Proponent acknowledges and agrees that the City will not be responsible for any costs, expenses, losses, damages (including damages for loss of anticipated profit) or liabilities incurred by the Proponent as a result of or arising out of submitting a Proposal for the proposed Contract, or due to the City s acceptance or non-acceptance of their Proposal or any breach by the City of the bid contract between the City and each of the Proponents or arising out of any contract award not made in accordance with the express or implied terms of the Proposal documents Page 3
4 City of Richmond 4 5. Enquiries and Addenda 5.1 Clarification of terms and conditions of the RFP document and RFP process and all other inquiries shall be directed to: Julia Turick, Buyer II City of Richmond 5.2 The City, its agents and employees shall not be responsible for any information given by way of oral or verbal communication. 5.3 The City will only respond to questions that are submitted in writing. Any questions that are received and answered by City Staff that affect the RFP process, any interpretation of, additions to, deletions from, or any other corrections to the RFP document, may be issued as written addenda by the City. It is the sole responsibility of potential Proponents to check the following websites to ensure that all available information has been received prior to submitting a Proposal: a) City: b) BC Bid: The decision to issue or not issue an addendum is entirely at the sole discretion of the City. 5.5 The deadline for inquiries for this RFP is 5:00 p.m., local time on March 4th, The City reserves the right not to respond to inquiries received after this deadline. 5.6 Each addendum will be incorporated into and become part of the RFP document. No amendment of any kind to the RFP is effective unless it is contained in a written addendum issued by the City s Purchasing Section. 6. Project Background 6.1 The City is planning for PeopleSoft FSCM Upgrade from 9.0 to The City proposes to engage the services of a PeopleSoft FSCM 9.2 Upgrade Change Management Consultant to provide scope, resources and schedule management specifically for PeopleSoft FSCM modules including General Ledger, Purchasing, Accounts Payable, Inventory, Billing, Receivables, Project Costing, Asset Management and nvision Financial Reporting Page 4
5 City of Richmond 5 7. Project Objectives 7.1 The focus of the project will be on the PeopleSoft applications and structures and processes that directly interact with the applications. In addition, the City is engaged to redesign the chartfield structure within the PeopleSoft application. 7.2 More specifically, the project will be responsible for the following activities: a) Upgrade the following applications from the currently implemented version 9.0 to version 9.2: 1. General Ledger 2. Payables 3. Purchasing 4. Inventory 5. Billing 6. Receivables 7. Project Costing 8. Asset Management b) Chartfield redesign will include conversion of master data and transactional data from the currently implemented version 9.0 to the new version 9.2. c) A business process review and fit-gap analysis that is performed in order to: 1. Compare the currently implemented and customized version 9.0 functionality to the functionality delivered in version 9.2 without customization. 2. Identify any resulting gaps in the delivered 9.2 that may require City to perform customization. d) Develop and implement process changes that make use of PeopleSoft functionality and/or improve processing quality/timeliness. e) Reproduce financial reports that are considered to still be required after a review of all City financial reports has been conducted. f) Deliver all existing public queries that are considered to be still required in the new version 9.2 after a review of all City public queries has been Page 5
6 City of Richmond 6 8. Project Timeline conducted. The project team may elect to make certain high-value private queries available as public queries. g) Deliver all existing external interfaces that are still in use on the currently implemented version 9.0 in the new version 9.2. h) Review and redevelopment of the transaction Interface model between 3rd party applications and PeopleSoft. i) Transfer and update the currently employed security model from version 9.0 to version 9.2. j) Ensure that business process controls and security assignments continue to comply with appropriate control standards. k) Full unit testing, integration testing, system testing and end user acceptance testing/approval of the new version prior to go-live. l) Provide training and knowledge transfer for the new version to City end users as well as business analysts and IT staff responsible for system maintenance. m) Upgrade of the PeopleTools software layer from version 8.52 to version n) Comprehensive documentation of all deliverables and processes. a) Chartfield redesign implemented by the end of June b) Upgrade to 9.2 implemented by November Scope of the Change Management Consultant 9.1 Under the direction of the Manager of Enterprise Application Development and the Manager of Financial Systems the consultant will be required to, but may not be limited to the following: a) Prepare and develop an upgrade plan and change management plan which encompasses process and application changes resulting from fit gap scope reviews. b) Implement the upgrade plan and change management plan that includes business unit stakeholders, process owners and departmental change agents Page 6
7 City of Richmond 7 c) Monitor progress on the upgrade plan and change management plan and tasks by creating and documenting status reports. d) Facilitates meetings with the project team to discuss, resolve and document progress and issues logs. e) Develop a test plan that includes objectives, test criteria, testers, scenarios, and expected results. f) Coordinate and document the testing activities and schedules with users. g) Document application and business processes to be adopted by end users 10. Submission Format 10.1 Responses submitted should be no more than 20 (twenty) pages in length, not including appendices, and should adhere to the following structure including section title and order as indicated below: SECTION A: Cover Letter and Executive Summary a) This covering letter referencing the RFP number and title should clearly state the Proponent s understanding of the services to be provided. The letter should include the name(s) of the person(s) who will be authorized to make representations for the Proponent, their title(s) and telephone number(s) and address. The cover letter should be signed by an authorized signatory in a position to legally bind the Proponent to statements made in response to this RFP. b) The executive summary should provide a synopsis of your overall approach and key points in your Proposal. SECTION B: Table of Contents a) The Table of Contents should reference the applicable section, sub-section and page numbers (e.g. Section C pages x-x, Sub-Section Part 1 page x-x). Pages should be consecutively numbered. SECTION C: Experience, Reputation, Capacity, and Resources a) Provide sufficient information that demonstrates the Proponent s experience, reputation, capacity, and availability of resources, including the ability to meet Requirements of this RFP, qualifications and competencies, track record, references of current and former clients for types of services described in this RFP. b) Provide sufficient information about your company that includes, but is not limited to the following: Page 7
8 City of Richmond 8 Part 1: Should include the following information: i. Contact information, including name, title, address, , telephone number and facsimile numbers. ii. iii. iv. Any other name(s) Proponent is, or has, been doing business under. Location of head office and subsidiary offices, as applicable; number of employees; A corporate profile of the Proponent s firm outlining its history, philosophy and target market; v. A detailed listing, with descriptions, of successfully completed projects that demonstrate the Proponent s experience with providing the types of services required by this RFP; including: a. A detailed resume identifying the individual s qualifications and experience. b. Number of years individual has worked for the company and specific projects worked on. c. Confirmation of the onsite availability of the individual for the duration of the project. Part 2: Additional Information i. In this section, Proponents may provide any additional comments about their experience, capacity, and resources which they feel would be informative and beneficial to the City. Part 3: References i. Proponents should provide a list of former and current references for all customers for whom the Proponent has provided the similar services required in this RFP, with an emphasis on local municipalities, for the past five (5) years (list all). Proponents should include a brief ½ page summary of the services provided, and the date of services. Include the organization name and address, telephone, and address of primary contact. The City may, during the evaluation process, contact the references to confirm statements made in response to this RFP. SECTION D: TECHNICAL INFORMATION In this section Proponents should provide: Part 1: Methodology, Work Plan and Schedule Page 8
9 City of Richmond 9 i. In this section, provide a specific timetable, milestones, meetings and detailed work plan for the Services as outlined in Section 8 (eight), including timelines for completion of specific tasks, time requirements and identification of specific deliverables. ii. List the City s staff, and time requirements of each that would be required to participate during the performance of the Services. iii. A short narrative (no more than two pages) that illustrates the Proponent s understanding of the Project (including background, objectives and scope), the Requirements, Project deliverables and Project objectives and how these will be achieved by the Proponent s methodology; iv. A methodology that describes the key elements of the approach that would be employed by the Proponent in undertaking this Project for the City as outlined in this RFP. Step by step procedures, documentation and a schedule of activities which indicate how it proposes to meet these needs should also be provided. This methodology should also include information explaining each project task, including what will be expected of both the Consultant and the City with respect to each task, and how the tasks achieve the project objectives/outcomes. This section should be clearly laid out, with each task succinctly described, and deliverables/outcome associated with each task identified. v. A detailed Project schedule of all activities, including milestones, project meetings, interim reports and progress reports required for this Project. vi. A detailed description of Project deliverables that will be provided to the City. Part 2: Applicable Standards i. Proponents should reference all applicable standards to be used in determining and completing their methodologies. If there are any standards specific to the Proponent s firms (not required by applicable industry standards) that will be applied during the performance of the services, then these should be specified in the Proposals as they will need to be considered by the City. SECTION E: PROPOSED FEES FOR METHOLOGY a) Appendix One Fee Schedule should be submitted in the format included with this RFP and shall represent the total fees to complete the Project including expenses and disbursements b) Additionally, in this section Proponents should provide pricing, payment options and cost saving strategies to the City, including: Page 9
10 City of Richmond 10 c) Confirm that all invoices will be in Canadian Funds; d) Please include any cost saving strategies that will benefit the City. SECTION F: WORKSAFE, INSURANCE(S), BUSINESS LICENSE In this section Proponents should provide: 11. Evaluation of Proposals i. Confirmation of WorkSafe BC coverage. Proponents not already having the WorkSafe appropriate coverage will be required to obtain the appropriate coverage prior to Contract award. ii. Confirmation of Required Insurance (See section 9.1 of shared/assets/general_conditions_for_ Consulting_Services_Provided_to_the_City28608.pdf ) iii. The Successful Proponent will be required to carry the appropriate insurance coverage amounts prior to Contract award All Proposals will be evaluated for their compliance and suitability with respect to the requirements of the City by a committee composed of City staff or designates, which may include 3 rd party consultants The City will review the Proposals submitted to determine whether, in the City s opinion, Proponents have demonstrated the required experience and qualifications to fulfill the obligations of the services identified in this RFP The City, in its sole discretion, may conduct any inquiries, clarifications or investigations on any or all of the Proposals, without having any duty or obligation to do so for all, including but not limited to contacting references, to verify the statements, documents, and information submitted in connection with the Proposal and may seek clarification from the Proponent s clients regarding any financial and experience issues Proposals will be evaluated on the basis of the overall best value to City based on quality, service, price and any other criteria set out herein including: 1. Extensive experience of PeopleSoft FSCM experience as a project manager in both systems implementation and major release upgrade methodology. 2. Extensive experience in analyzing PeopleSoft applications with focus on Finance and supply Chain process, General Ledger, Procurement to Pay, Billing and Receivables, Capital Project Management, Chartfield Design/Redesign, Project Costing, Asset Management and Financial Management & Reporting Page 10
11 City of Richmond Previously and successfully completed projects of a similar size and complexity to the scope of work described in this RFP. 4. Extension experience in PeopleSoft Upgrade project management, change management, resource scheduling, scope and timeline management, testing, and documentation. 5. Financial proposal and demonstrated value for money in terms of deliverables and effort. 6. Proposed methodology including Respondents: a. Ability to provide detailed explanation of each task and what will be required of the Proponent; b. Ability to address the scope of work and make reference to the requirements outlined in the RFP; and, c. Quality of details of the estimated project time effort and budget. 7. Ability to work on site; and, 8. Compliance to RFP requirements Preference may be given to Submissions offering innovative methodology, those that require the least impact to City resources, and environmentally beneficial goods or services Proponents may be interviewed by the City. Each Proponent should be prepared to demonstrate or otherwise substantiate any areas of the Response, its own qualifications for services required, and any other area of interest relative to its Response Reference checks may also by conducted by the City Prior to Contract award, the Proponent may be required to demonstrate financial stability. As such, the Proponent may be required to provide annual financial reports or a set of financial statements prepared by an accountant and covering the last 2 (two) fiscal years Preference may be given to Proposals offering innovative concepts, those that require least impact to the City resources, and environmentally beneficial products or services The City may, prior to Contract award, negotiate changes to the scope of the Work, the materials, the Requirements or any conditions with any one or more of the Proponents without having any duty or obligation to advise any other Proponents or to allow them to vary their prices as a result of changes to the scope of Work, the materials, the Specifications, or any conditions, and the City shall have no liability to any other Proponent as a result of such negotiations or modifications Page 11
12 City of Richmond RFP Process 12.1 This RFP is not an agreement to purchase goods or services. The City is not obligated to select a Proponent or to proceed to negotiations for a Contract, or to award any Contract. As such, the City reserves the right to unilaterally take the following actions, and shall not be liable for any such actions: a) accept a Proposal that deviates from the Requirements, Specifications or the conditions specified in this Proposal; b) accept a Proposal which is not the lowest cost Proposal; c) accept all or any part of a Proposal; d) amend the scope and description of the products and services to be procured as described in this RFP, and the qualifications that may be required to meet those requirements; e) assess the ability of the Proponent to perform the Contract and reject any Proposal where, in the City s sole estimation, the personnel and/or resources of the Proponent are deemed insufficient; f) cancel the RFP process and recommence in respect of the same RFP with the same or an amended set of documents, information and requirements; g) cancel the RFP process at any time and reject all submissions; h) not accept any Proposal in response to this RFP; i) reject a Proposal even if it is the only Proposal received by the City; j) reject any and all Proposals, including without limitation the lowest priced Proposal, even if the lowest priced Proposal conforms in all aspects with the RFP; k) reject or accept any or all Proposals at any time prior to execution of a Contract; l) reject Proposals which are incomplete, conditional or obscure or erasures or alterations of any kind, or m) split the Requirements between one or more Proponents The Proponent acknowledges and agrees that any RFP is in no way whatsoever an offer to enter into an agreement and submission of a Request of Proposal by any Proponent does not in any way whatsoever create a binding agreement. The Proponent acknowledges that the City has no contractual obligations whatsoever arising out of the RFP process Page 12
13 City of Richmond Negotiations 13.1 The award of the contract may be subject to negotiations with the Lead Proponent. Such negotiations include, but are not limited to, the following: a) changes or work refinements in the service requirements or scope of work proposed by the Lead Proponent; b) price if directly related to a change or refinement in the proposed scope of work proposed by the Lead Proponent; c) specific contract details as deemed reasonable for negotiation by the City; and, d) structure of the Consultant team and participants If a written contract cannot be negotiated within 30 (thirty) days of notification to the Lead Proponent, the City may, at its discretion at any time thereafter, terminate negotiations with the Lead Proponent and either enters into negotiations with the next qualified Proponent or cancel the RFP process and not enter into a contract with any Proponent. 14. Working Agreement 14.1 The Successful Proponent will enter into a contract for services with the City based upon the information contained in this RFP and the Successful Proponent s Submission and any negotiated modifications thereto. 15. Award of Contract 15.1 Award of a Contract is contingent on funds being approved and the contract award being made by the appropriate City authority No Contract will be formed, with any Proponent, until the Contract terms have been successfully negotiated between both parties (the City and the Successful Proponent). The City is not obligated to any Proponent in any manner until a purchase order is issued and an agreement has been signed by an authorized person to sign on behalf of the City The City s purchase order, the Proposal, the RFP and such other documents including all amendments or addenda, shall form the basis for the Contract between the Consultant and the City. In the event of a conflict between any of the Contract Documents, the following documents will take precedence and govern over each other in the following order of priority from highest to lowest: a) The City s purchase order including the standard purchase order terms and conditions; Page 13
14 City of Richmond 14 b) Or any mutually agreed to amendments between the Proponent and the City; c) The Proposal; and d) The RFP and any subsequent addenda Where the head office of the Successful Proponent is located within the City and/or where the Successful Proponent is required to perform the Service at a site located within the City, the Successful Proponent should have a valid City business license prior to Contract execution The City is not under any obligation to award a Contract and may elect to terminate this RFP at anytime. 16. Publication of the Results of this RFP 16.1 The City will publish the name of the successful Proponent on the websites listed in section 5.3. No other notices will be issued by the City. Proponents shall visit these websites to obtain the results of this RFP. 17. General Terms of this RFP 17.1 All Proposals shall remain open for a minimum of 90 (ninety) days after the Closing Time, whether or not another Proposal has been accepted The City reserves the right to cancel this RFP for any reason without any liability to any Proponent or to waive irregularities at its own discretion Except as expressly and specifically permitted in these instructions, no Proponent shall have any claim for any compensation of any kind whatsoever, as a result of participating in the RFP, and by submitting a proposal each proponent shall be deemed to have agreed that it has no claim Proponents are advised that the City will not necessarily accept any Proposal and the City reserves the right to reject any or all Proposals at any time without further explanation or to accept any Proposal considered advantageous to the City A Proposal which contains an error, omission, or misstatement, which contains qualifying conditions, which does not fully address all the requirements of this RFP, or which otherwise fails to conform to the requirements in this RFP, including the Proposal format and content requirements, may be rejected in whole or in part by the City at its sole discretion Notwithstanding the foregoing or any other provision of this RFP, the City may in its sole discretion elect to retain for consideration Proposals which deviate either materially from the Proposal Format and Content Requirements set out in hereto or which otherwise fail to conform to any other requirement of this RFP Page 14
15 City of Richmond The City may waive any non-compliance with the RFP, specifications, or any conditions of anything required by the RFP and may, at its sole discretion, elect to retain for consideration Proposals which are non-conforming, which do not contain the content or form required by the RFP or because they have not complied with the process for submission set out herein The City may choose, at its sole discretion, to proceed with all of the components of the Work, none of the components or selected components of the Work All Proposals will remain confidential, subject to the Freedom of Information and Protection of Privacy Act of British Columbia. 18. Ownership of Proposals 18.1 All Proposals submitted, other than any Proposal withdrawn prior to the opening of Proposals or any late Proposals, become the property of City and will not be returned to Proponents. 19. Conflict of Interest 19.1 Proponents shall disclose any potential conflicts of interest and existing business relationships they may have with the City, its elected or appointed officials or employees. The City may rely on such disclosure. The City may reject a Proposal from any Proponent that the City judges would be in a conflict of interest if the Proponent is awarded a Contract. Failure to disclose, or provide false or insufficient disclosure of the nature and extent of any relationship the Proponent may have with any employee, officer or director of the City shall be grounds for immediate termination of any Contract with the City, in the City s sole discretion, without further liability of notice By submitting a Proposal, the Proponent warrants that neither it nor any of its officers or directors, or any employee with authority to bind the Proponent, has any financial or personal relationship or affiliation with any elected official or employee of the City or their immediate families which might in any way be seen by the City to create a conflict. 20. Confidentiality 20.1 Information about the City obtained by Proponents must not be disclosed unless prior written authorization is obtained from the City The Consultant agrees that this obligation of confidentiality will survive the termination of the Contract between the Consultant and the City Page 15
16 City of Richmond No Lobbying 21.1 From the date on which this RFP is issued until the RFP process is terminated, Proponents (including any directors, employees, officers, agents, consultants, or representatives) should not communicate with the City, directly or indirectly, about the RFP or the Project except via the designated Contact Person in Section Information Disclaimer 22.1 The City, including its Designated Representatives and its directors, officers, employees, agents, Consultants and advisors are not liable or responsible for any verbal or written information, or any advice, or any errors or omissions, which may be contained in this RFP or otherwise provided to any Proponent pursuant to this RFP The Proponent shall conduct its own independent investigations and interpretations and shall not rely on the City with respect to information, advice, or documentation provided by the City. The information contained in this RFP is provisional and will be superseded by other agreement documents The City makes no representation, warranty, or undertaking of with respect to this RFP and the City, its Designated Representatives and its directors, officers, employees, agents, Consultants and advisors, shall not be liable or responsible for the accuracy or completeness of the information in this RFP or any other written or oral information made available to any interested person or its advisors, and any liability however arising, is expressly disclaimed by the City While the City has made considerable efforts to ensure an accurate representation of information in this RFP, the information contained in this RFP is supplied solely as a guideline for the Proponent and is not necessarily comprehensive or exhaustive. Nothing in this RFP is intended to relieve the Proponent from forming its own opinions and conclusions in respect of the matters addressed in the RFP. 23. Freedom of Information and Protection of Privacy Act (BC) 23.1 Proponents should note that the City is subject to the Freedom of Information and Protection of Privacy Act (British Columbia), which imposes significant obligations on the City s Consultants to protect all personal information acquired from the City in the course of providing any service to the City Page 16
17 City of Richmond 17 Appendix One - Fee Schedule Activity Description 1 Prepare and develop the upgrade plan and change management plan which includes: - Identifies and prioritization of upgrade scope - Roles and responsibilities - Identification of Stakeholders and business unit leads - Timeline/Gantt chart - Work breakdown structure - Project Cost Allocation 2 Monitors progress on the upgrade plan and change management plan and tasks by creating and documenting status reports. - Identify and track activities within review period - Document outstanding tasks and develop remediation activities to address timeline impacts. - Plan and forecast upcoming tasks - Coordinate activity schedules to ensure completion of task. 3 Facilitates meetings with the project team to discuss, resolve and document progress and issues logs. (Please add details to description.) 4 Implement a change management plan that includes business unit stakeholders, process owners and departmental change agents. (Please add details to description.) 5 Conduct a post project review (please add details to description) Estimates (Days) Hourly Rate ($/hr) Subtotal days $ Estimated disbursements (expenses) $ Total Cost per Activity Page 17
18 City of Richmond 18 Activity Description Estimates (Days) Hourly Rate ($/hr) Subtotal Fees and Disbursements $ Estimated G.S.T. (5%) $ Total $ Total Cost per Activity Page 18