All requests for proposals that are compliant with the mandatory requirements shall be reviewed and evaluated by an Evaluation Committee approved by the Purchasing Director. Evaluation Committees are usually comprised of at least three voting members, but they can be any size. Voting membership on the Evaluation Committee shall be limited to County employees; however, the Purchasing Director, Procurement Officer, public officials and / or consultants under contract with Wayne County may sit as consulting members. All proposals will be evaluated based on Section 3.10 below. All proposals that are compliant with the mandatory requirements will be scored and ranked using a weighted scoring template. Wayne County may also, at its option, invite proposers being evaluated to make a verbal presentation or conduct site visits, if appropriate. 3.10 Evaluation Criteria Weight 1. Preferred Qualifications Section 4.1.2 – Preferred Qualifications 5 2. Solution Section 2 – Specifications and Scope of Work 15 3. Functional Requirements Appendix A – Functional Requirements 20 4. Implementation and Project Plan Appendix B – Implementation Services Additional Information Exhibit 1 – Preliminary Project Plan 20 5. Resources Appendix C - Project Team and Proposed Personnel Exhibit 2 – Personnel Resumes 5 6. Technical Requirements Appendix D – Technical Services Additional Information 10 7. Service Levels Appendix F – Service Levels 5 8. Interfaces Appendix G – Interfaces 5 9. Qualifications and References Section 4.1 – Proposer Qualifications and References 5 10. Pricing Appendix H – ERP Pricing 10 TOTAL 100 3.11 Optional to Enhance Evaluation Process
proposed ERP solution that have started but are not yet complete. Proposers should note that the Wayne County will give preference to references for US-based implementations involving the proposed ERP software. The following information must be provided for each qualifying or additional reference: Company Name Brief overview of business operations, with an emphasis on ERP related business in the public sector Annual budget of the entity at the time the project started Head in employees for that entity at the time the project started Proposer Role (Prime Supplier or Subcontractor) If Proposer was the Prime Supplier, name key Subcontractors If Proposer was the Subcontractor, name the Prime Supplier on the project ERP Software Project Description Modules Implemented Third Party Software Implemented Actual implementation time frame Contact name and title Email, phone, and address of contact name (Proposer Response Here): III) - Proposer References for Implementation of Third Party Products (if any) If the Proposer has proposed any party software, the Proposer must also provide a minimum of 1 reference for a completed project in the U.S. involving the implementation of that product. One reference for each third party product proposed will be required. Proposers should note that the County will give preference to references involving governments in the U.S. and where the Proposer was involved as the prime Supplier. However, it is permissible to submit reference information for implementation of such products that involve a Subcontractor, as long as the proposed role and extent of involvement for that Subcontractor are sufficient. It is also permissible to provide a reference that does not involve a US-based public sector entity. The following information must be provided for each qualifying or additional reference: Company Name overview of business operations, with an emphasis on ERP related business in the public sector
Appendix B - Implementation Services Additional Information Proposer Responsibilities The following overview of implementation tasks, activities and deliverables should be considered in the Proposer’s response to the RFP. It is understood that the Proposer may modify or augment the following with their proven implementation methodology and associated stages. If the implementation methodology proposed uses different terms or term definitions than the County then a crosswalk of County and implementation terms and definitions should be provided as part of the response. Required Response Item for this Appendix B Appendix B, Section 1: Proposers shall describe their Implementation Methodology through the completion of the table below. Additionally, Proposers may include a narrative describing their Implementation Methodology. (Proposer Response Here): County General Implementation Overview Proposer Implementation Methodology Project Project Activities Project Stage Deliverables Project Project Activities Project Stage Deliverables Project Planning and Organization The objectives of this stage are to further define the overall project scope and to develop the procedures and mechanisms required to plan and control the project. This stage sets the overall direction and approach for managing the project. This stage formally documents the detailed overall project scope to facilitate its execution through a project plan. The Plan stage also defines the team members, roles and responsibilities, and the communication plan that will be used throughout the project. This stage concludes with a kickoff meeting for the project team and the Executive office. This stage may also include initial system training for the project team members. Project Charter Project Schedule Work Breakdown Structure General Communication Plan Resource Plan Project Kickoff Meeting Weekly Status Reports Executive Summary Reports Project Cadence Plan Project Execution Platform Consultant Resumes Project Team Organization (selected Supplier) Project Team Organization (County) Project Team Training
Solution Design The objectives of this stage are to allow the County and selected Supplier project team members to come to a common understanding of County-wide business requirements / business processes and regional/departmental business requirements / business processes. Subsequently, this understanding will be used to create a detailed inventory of business processes, configuration requirements and integration requirements necessary for the successful configuration and operation of the ERP solution. The selected Supplier will work with the County to review and understand how the business processes will work within the ERP system. The selected Supplier will also work with the County to develop business process templates that allow for the configuration of the software solution. This stage will also entail the definition and configuration aspects of other ERP structures including chart of accounts, organization hierarchy, locations, employees, etc. The selected Supplier will lead the appropriate workshops and design sessions to understand and finalize needed ERP structures. It is expected that the selected Supplier will recommend best practices in structure, process and ERP utilization. Technical Technical Specification Document Architecture Diagram Architecture/design Documentation Infrastructure/Environment Validation Database Diagram Functional Fit Gap Analysis Documentation Updated Business and Functional Requirements Documentation Process and Transaction Mapping to Software Functionality Inventory of Transactions, Reports, and Processes Software Configuration Guide Data Data Cleansing Guidelines Data Migration Design Documentation Interfaces Interface Requirements Development of Interface Specifications Interface Architecture Reporting Reporting Requirements Development of Reporting Specifications