Planning, Zoning, Plan Review, and Permitting Application Pre-Offer - PowerPoint PPT Presentation

Request for Proposals (RFP) RFP 19-019 Planning, Zoning, Plan Review, and Permitting Application Pre-Offer Conference October 9, 2018 – 11:00 A.M. Calvin C. Goode Building, 8 th Floor, Room 854 Finance Department

Agenda  Introductions Procurement Officer – Andria Williams and Tim Reed Technology Manager – Shannon Tolle Project Manager – Melanie Hanks Project Owner – Mary Ann Fotinos  Questions and Answers (Q&A) Process  RFP Basics  Evaluation Criteria  Attachments  Scope of Work  Transparency Policy 2

Questions & Answers (Q&A) Process  Written questions only  Some answers available today during Q&A session  All answers published on web  Written answers supersede verbal answers  Submit questions by October 16, 2018  10 :00 a.m. local Arizona time  Email: Andria.Williams@phoenix.gov 3

RFP Basics Pre-Proposal Conference  Proposers attending via web or conference bridge must send an email to the Procurement Officer, Andria.Williams@phoenix.gov, confirming attendance immediately following this Pre- Offer conference 4

RFP Basics Addenda  Addenda  Any changes to the instructions, plans, drawings, specifications, or contract documents will be in the form of an addendum, available at https://www.phoenix.gov/solicitations. The Offeror must acknowledge receipt of any/all addenda by signing and returning the document with the proposal submittal.  No electronic notification will be sent to vendors when addenda is issued. 5

RFP Basics Proposal Due Date Proposal Due Date November 16, 2018 2:00 P.M. Local Arizona Time Late proposals will be rejected. 6

RFP Basics Statement of Bonding Ability  Offerors must submit a letter from a bonding or insurance company stating that the Offeror can qualify for and procure the performance and/or payment surety required in this solicitation.  Submittals received without the required statement of ability to secure a performance or payment surety may be considered as non-responsive.  Offerors anticipating the submittal of a cash surety in lieu of a bond should submit a statement notifying the City. 7

RFP Basics Proposer Instructions  Proposal Packet  1 original and 1 electronic copy (portable drive or CD)  Tabbed and organized in following order: Tab 1 – Title Page Tab 2 – Cover Letter Tab 3 – Table of Contents Tab 4 – Executive Summary Tab 5 – Company Background and Experience Tab 6 – Solution Response Tab 7 – Implementation Approach Tab 8 – Offeror References Tab 9 – Staff Resumes and References Tab 10 – Additional Materials Offeror Wishes to Include Tab 11 – Submittal Section and Statement of Bonding Ability Tab 12 – Signed Addenda Pricing Workbook – Separate, sealed folder and separate electronic file – both clearly marked 8

Evaluation Criteria A. Requirements (Functional and Technical) 300 POINTS B. Implementation Services 250 POINTS C. Infrastructure, Support and Maintenance 200 POINTS D. Experience and Qualification 150 POINTS E. Price 100 POINTS TOTAL AVAILABLE POINTS: 1000 MAXIMUM 9

Attachments  Appendix A – SHAPE Phoenix Use Cases  Appendix B – SHAPE Phoenix Functional Requirements  Appendix C – SHAPE Phoenix Technical Requirements  Appendix D – SHAPE Phoenix Pricing Workbook 10

Scope of Work Melanie Hanks Planning and Development Department Project Manager Christina Rinaldi Gartner, Inc. Project Consultant 11

Scope of Work  The SHAPE Phoenix Project targets replacing the Planning and Development’s primary land management applications, and other supporting applications.  KIVA  PlanWeb  Expand geospatial integration  Scalability, flexibility and accountability 12

Scope of Work  KIVA; code purchased in 1990’s. KIVA supports community planning, development and regulation activities.  Plan Review  Inspections  Permitting  Historic Preservation  Impact Fees  PlanWeb; developed in-house.  Zoning Processes 13

Scope of Work  Other Items:  Electronic Plan Review  GIS Integration  Document Management  Capabilities for Online Portal  Mobile  Financial Tracking and Reporting Capabilities 14

Solicitation Transparency Policy Phoenix City Code, Chapter 43, Section 43-36  Commencing on the date and time a solicitation is published, potential or actual offerors or respondents (including their representatives) shall only discuss matters associated with the solicitation with the Procurement Officer or by requesting a public meeting.  This policy is intended to create a level playing field for all Offerors, assure that contracts are awarded in public, and protect the integrity of the selection process. OFFERS THAT VIOLATE THIS POLICY SHALL BE DISQUALIFIED. All questions must be directed, in writing, to the Procurement Officer . 15

Questions