CRM RFP 677-IT27-03.pdf

PDF 1 MB Posted

Attached to
Citizen Request Management System (CRM) RFP
Solicitation number
677-IT27-03
Issued by
Wake County, North Carolina

About this file

Summary

This Request for Proposals (RFP #677-IT27-03) is issued by the Town of Wendell, North Carolina, for the procurement of a comprehensive Citizen Request Management System (CRM). The Town seeks qualified vendors to provide, implement, configure, and support an organization-wide solution that manages the complete lifecycle of resident service requests. The RFP was posted on November 10, 2026, with written questions due by November 20, 2026, at 5:00 PM ET. Town responses to proposer questions will be issued by November 25, 2026, at 5:00 PM ET. Proposals must be submitted electronically through the North Carolina Electronic Vendor Portal (eVP) by December 3, 2026, at 3:00 PM ET. Respondent demonstrations are anticipated following initial proposal evaluation at the Town's discretion. Gregory Kipyego, IT Director (gkipyego@townofwendellnc.gov), serves as the primary contact. The contract is expected to be a multi-year engagement with ongoing support, though specific contract term details are referenced through negotiation with the selected vendor following award.

The Town requests pricing organized by category across five years, including one-time implementation costs, software licensing/subscription fees, training, support and maintenance, hosting, and other ancillary costs, with vendors identifying all expenses and indicating whether services are included in subscription fees. Proposals will be evaluated on functional requirements fit (15%), citizen and staff experience (10%), implementation approach (10%), GIS and integration capabilities (10%), security and reliability (10%), reporting capabilities (10%), system integration with Town systems (10%), and overall cost (25%). The Town prefers cloud-based or Software as a Service solutions but will consider alternative architectures if they provide clear operational or financial advantages. The proposal must address integration with existing Town systems including Revize, Accela, ArcGIS, iMAPS, and Bluebeam, as well as future systems such as Brightly and Tyler Cityworks. Vendors are required to obtain insurance including General Liability ($1,000,000/$2,000,000), Commercial Automobile Liability ($1,000,000), Cyber Liability ($1,000,000), and Workers' Compensation at statutory limits, with the Town listed as additional insured. Price quotations must remain firm for 120 days following the proposal due date.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

v.10.21.26

409 Landing View Dr. Wendell, NC 27591

Telephone: (919) 365-4450 www.townofwendellnc.gov

REQUEST FOR PROPOSALS

RFP #677-IT27-03

Project Title: CITIZEN REQUEST MANAGEMENT SYSTEM

Issue Date: November 10, 2026

Due Date: December 3, 2026 at 3:00 PM EST ET

Issuing Department: Information Technology

Direct all inquiries concerning this RFP to:

Name: Gregory Kipyego

Title: IT Director Email: gkipyego@townofwendellnc.gov

Table of Contents

1 REQUEST FOR PROPOSALS

1.1 Introduction

1.2 Purpose and Background

1.3 Notice to Proposers Regarding RFP Terms and Conditions

1.4 RFP Response Timeline

1.5 Proposal Questions

1.6 Proposal Submission Requirements and Contact Information

1.7 Rights to Submitted Material

2 PROPOSALS

2.1 Request for Proposal Document

2.2 Evaluation Criteria

2.3 Proposal Evaluation Process

2.4 Final Selection

3 SCOPE OF SERVICES

4 COST PROPOSAL/ EXECUTION OF PROPOSAL

5 REFERENCES

APPENDIX A - INSTRUCTIONS TO VENDORS

APPENDIX B – TOWN OF WENDELL WORKFLOW DIAGRAMS

APPENDIX C – FUNCTIONAL REQUIREMENTS MATRIX……………………...21

APPENDIX D – VENDOR DEMONSTRATION SCENARIOS…………………...25

1 REQUEST FOR PROPOSALS

1.1 Introduction

The Town of Wendell, North Carolina, is requesting proposals from qualified firms to provide, implement, configure, and support an organization-wide Citizen Request Management System (CRM).

The selected solution will support the complete lifecycle of requests received from residents.

1.2 Purpose and Background

The Town currently uses multiple systems to receive, route, track, map, document, and manage resident concerns and related internal work. The new CRM should provide a more cohesive resident-request experience while supporting practical integration with the Town's existing tools and future operational systems.

Current System /

Tool Current Use Reference

Revize Public Service Request

Public-facing intake for resident concerns and service requests https://cms.revize.com/revize/apps/revize_psr/public/index.php ?client_department_id=488

Accela PublicStuf f

Internal work-order / request tracking and staff processing https://gov.publicstuff.com/?redirect=reports/custom

ArcGIS

GIS, mapping, spatial data, and Town geographic layers

Existing Town platform iMAPS

Parcel/propert y and geographic reference information

Existing external/local-government mapping resource

Email Requests received by email or phone

Existing Town communication channels

The Town has developed a workflow that visualizes how citizen requests move through the process from submission to final closure. The workflow is attached as Appendix B.

The Proposed solutions must support these workflows. The Town is not prescribing the underlying technical architecture used to implement them. Vendors may recommend the technical approach, system https://cms.revize.com/revize/apps/revize_psr/public/index.php?client_department_id=488 https://cms.revize.com/revize/apps/revize_psr/public/index.php?client_department_id=488 https://gov.publicstuff.com/?redirect=reports/custom configuration, integrations, and supporting components necessary to deliver the required workflows and functional requirements. The proposal must clearly identify the recommended architecture, dependencies, costs, transition approach, and how the CRM can exchange data with current or future work-order and asset-management platforms. Potential future systems may include Brightly, Tyler Cityworks, Accela, or other Enterprise Resource Planning system (ERP) asset management or Work order platforms that may be selected by the Town; this list is illustrative and not exhaustive.

1.3 Notice to Proposers Regarding RFP Terms and Conditions

It shall be the Proposer’s responsibility to read the Instructions, all relevant exhibits and attachments, and any other components made a part of this RFP and comply with all requirements and specifications herein.

Proposers also are responsible for obtaining and complying with all Addenda and other changes that may be issued in connection with this RFP.

If Proposers have questions, issues, or exceptions regarding any term, condition, or other component within this RFP, those must be submitted as questions in accordance with the instructions in Section 1.6 Proposal Questions. If the Town determines that any changes will be made as a result of the questions asked, then such decisions will be communicated in the form of an RFP addendum. Other than through this process, the Town rejects and will not be required to evaluate or consider any additional or modified terms and conditions submitted with Proposer’s proposal. This applies to any language appearing in or attached to the document as part of the Proposer’s proposal that purports to vary any terms and conditions or Proposers’ instructions herein or to render the proposal non-binding or subject to further negotiation. Proposer’s proposal shall constitute a firm offer. By execution and delivery of this RFP Response, the Proposer agrees that Proposer is prepared to enter into a contract should Town select Proposer’s proposal and that any additional or modified terms and conditions, whether submitted purposely or inadvertently, shall have no force or effect, and will be disregarded. Noncompliance with, or any attempt to alter or delete, this paragraph shall constitute sufficient grounds to reject Proposer’s proposal as nonresponsive.

If a Proposer desires modification of the terms and conditions of this solicitation, it is urged and cautioned to inquire during the question period, in accordance with the instructions in this RFP, about whether specific language proposed as a modification is acceptable to or will be considered by the Town.

Identification of objections or exceptions to the Town’s terms and conditions in the proposal itself shall not be allowed and shall be disregarded or the proposal rejected.

Successful Contractor shall procure and maintain, for the duration of the contract, insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the work by the Contractor, his agents, representatives, or employees, if applicable.

Minimum limits of insurance coverage are:

General Liability $1,000,000 per occurrence/ $2,000,000 aggregate Commercial Automobile Liability $1,000,000 CSL Commercial Excess/Umbrella Liability $1,000,000 per occurrence Workers’ Compensation Statutory Limits Employer’s Liability $500,000 per occurrence Cyber Liability $1,000,000 per claim and aggregate

A successful Contractor will be required to provide a Certificate of Insurance with the Town, its elected officials, officers, employees and volunteers listed as additional insured.

1.4 RFP Response Timeline

The RFP process shall adhere to the following schedule:

Note: All times shown as Eastern Time (ET).

1.5 Proposal Questions

Upon review of the RFP documents, Proposers may have questions to clarify or interpret the RFP in order to submit the best proposal possible. To accommodate the Proposal Questions process, Proposers shall submit any such questions by the above due date. The Town will not entertain any further questions after the due date. Written questions shall be emailed to gkipyego@townofwendellnc.gov by the date and time specified above. Proposers should enter “RFP #677-IT27-03: Questions” as the subject for the email.

Questions submittals should include a reference to the applicable RFP section and be submitted in the format shown below:

Reference Vendor Question

RFP Section, Page Number Vendor question …?

Questions received prior to the submission deadline date, the Town’s response, and any additional terms deemed necessary by the Town will be posted in the form of an addendum to the North Carolina Electronic Vendor Portal (eVP), https://evp.nc.gov/solicitations, and shall become an Addendum to this RFP. No information, instruction or advice provided orally or informally by any Town personnel, whether made in response to a question or otherwise in connection with this RFP, shall be considered authoritative or binding. Vendors shall rely only on written material contained in an Addendum to this RFP.

1.6 Proposal Submission Requirements and Contact Information

Electronic responses ONLY will be accepted through the NC eVP website. Interested parties must be logged in to submit proposals electronically. Registration information is available at NC Electronic Vendor Portal (eVP). It shall be the Vendor’s sole responsibility to ensure access to the NC eVP website and for submission by the designated time. Proposals must be clearly marked with name of the submitting company, the RFP number and RFP title. Proposers must submit one (1) electronic version, submitted as a viewable and printable Adobe Portable Document File (PDF).

Submissions that do not comply with the stated submission method will be deemed non-responsive. The Town reserves the right to reject any or all proposals for any reason and to waive any informality it deems in its best interest. Any requirements in the RFP that cannot be met must be indicated in the proposal.

Proposers must respond to the entire Request for Proposals (RFP). An incomplete proposal may be eliminated from consideration at the discretion of Wendell.

Proposals must follow the format as defined in Section 2 PROPOSALS.

Respondents are cautioned not to make changes to any of the terms and conditions in this solicitation.

Doing so may render a Respondent’s proposal unacceptable and unresponsive for award. Question and inquiries must be made in writing as outlined in Section 1.

RFP Process Date and time RFP Posted November 10, 2026 Proposers Written Questions Due November 20, 2026 5:00 PM Town Responses to Proposers Questions November 25, 2026 5:00 PM Proposal Submission Deadline December 3, 2026 3:00 PM Respondent Demo(s) (by invite only) Tentative https://evp.nc.gov/solicitations/ https://evp.nc.gov/solicitations/ https://evp.nc.gov/ https://evp.nc.gov/

1.7 Rights to Submitted Material

All proposals, responses, inquiries, or correspondence relating to or in reference to this RFP, and all reports, charts, and other documentation submitted by Proposers (other than materials submitted as and qualifying as trade secrets under North Carolina law) shall become the property of the Town when received and the entire proposal shall be subject to the public records laws of the State of North Carolina except where a proper trade secrets exception has been made by the Proposer in accordance with the procedures allowed by North Carolina law.

The Town reserves the right to retain all proposals submitted and to use any ideas in a proposal regardless of whether that proposal is selected. Submission of a proposal indicates acceptance by the Proposer of the conditions contained in this Request for Proposal.

2 PROPOSALS

Responses must follow the format outlined herein. The Town may reject as non-responsive at its sole discretion any proposal or any part thereof that is incomplete, inadequate in its response, or departs in any substantive way from the required format. Proposal responses shall be organized in the following manner:

A. Cover Letter/Letter of Intent

Respondents shall submit a clear and concise response identifying the following information:

a. Full Legal Name of the Firm

b. Primary contact person working on the Town’s behalf and their contact information

c. The Firm’s contact information

d. Why the Town should select the Firm for this work

e. Acknowledgement of any Addenda (if applicable)

B. Qualification and Experience

The Proposer should describe its track record in performing services comparable to those specified in the RFP and other information relevant to making a determination as to the ability of the Proposer to perform these services. List at least three (3) references for contracts in the past five (5) years similar to the scope and size of the project specified herein

C. Project Understanding and Approach

This section shall include a brief summary of the Proposer’s understanding of the scope of services presented in this RFP and emphasize any unique aspects or strengths of the Proposal. A description of each task and deliverable and the schedule for accomplishing each shall be included.

D. Organization, Staffing and Certifications/Qualifications This section must include the proposed staffing, and deployment and organization of personnel to be assigned to this project. The Proposer shall provide information as to the qualifications and experience of all personnel to be assigned to this project, including resumes citing experience with similar projects and the responsibilities to be assigned to each person. For proposed subcontractors, please provide the name of each vendor, the office location, contact name and telephone number, and the services to be provided

E. Cost Proposal (Section 4) Proposals shall include pricing for the scope of work, all labor, time, and materials. Sales Tax shall not be included in any proposed prices. The Town is not tax-exempt and will pay sales tax where applicable. Any applicable Sales tax shall be invoiced as a separate item.

F. In addition to A-E these submittals are required:

• Completed Appendix C – Functional Requirements Matrix

• Completed Cost Proposal & RFP Execution - Section 4

• Vendor Responses Required in Section 3 - Scope of Services - XII. Integration and Data

Transition

2.1 Request for Proposal Document

The RFP is comprised of the base RFP document, any attachments, and any addenda released before Contract award. All attachments and addenda released for this RFP in advance of any Contract award are incorporated herein by reference.

2.2 Evaluation Criteria

This is not a bid. There will not be a public bid opening. Proposals will be evaluated based on the following criteria:

Criteria Weight Functional requirements and workflow fit 15

Citizen and staff user experience 10

Implementation approach and staffing 10

GIS, mobile and integration capabilities 10

Security, reliability and support 10

Reporting and management visibility 10

Integration Capabilities with Town Systems 10

Overall Cost 25

TOTAL 100

2.3 Proposal Evaluation Process

The Town shall review all Vendor responses to this RFP to confirm that they meet the specifications and requirements of the RFP.

All proposals must be received by the issuing agency not later than the date and time specified on the cover sheet of this RFP.

At that date and time, the package containing the proposals from each responding firm will remain sealed and opened at time of review. Interested parties are cautioned that these costs and their components are subject to further evaluation for completeness and correctness and therefore may not be an exact indicator of a vendor’s pricing position.

At their option, the evaluators may request oral presentations or discussion with any or all Vendors for the purpose of clarification or to amplify the materials presented in any part of the proposal. Vendors are cautioned, however, that the evaluators are not required to request presentations or other clarification—and often do not. Therefore, all proposals should be complete and reflect the most favorable terms available from the Vendor.

Following the initial evaluation of written proposals, the Town may, at its sole discretion, shortlist one or more proposers for demonstrations, interviews, reference checks, product testing, or other evaluation activities. Information obtained through these activities may be considered in the final ranking and selection of the successful proposer.

Proposals will generally be evaluated according to completeness, content, and experience with similar projects, ability of the Vendor and its staff, and cost. Specific evaluation criteria are listed in 2.2 EVALUATION CRITERIA, above.

Vendors are cautioned that this is a request for offers, not an offer or request to contract, and the Town reserves the unqualified right to reject any and all offers at any time if such rejection is deemed to be in the best interest of the Town.

2.4 Final Selection

The purpose of this document is to provide general and specific information for use by Vendor(s) in submitting a proposal to supply the Town of Wendell with information technology goods and services as listed above in accordance with N.C.G.S. 143-129.8. We will select a qualified Vendor(s) with whom we will develop a mutually beneficial contractual relationship. Our decision to award will be based on our determination of the proposal that offers the best overall value and benefit to the Town, taking into account pricing, maintenance and support, and any value-added services and other factors specified herein.

Proposals will be reviewed after opening and will be ranked in order of choice. A recommendation will then be presented to the Town Manager for approval to negotiate a contract with the #1 choice and, if unsuccessful, to then pursue negotiations with the #2 choice. All Proposers will be notified of their standing following the Town’s decision. Price quoted must be held firm for 120 days after the RFP is due. The Town reserves the right to make an award without further discussion of the proposal submitted. The Town shall not be bound or in any way obligated until both parties have executed a contract. The Town also reserves the right to delay the award of a contract or to not award a contract. The RFP may be awarded by individual task or total proposal, whichever is most advantageous to the Town of Wendell.

The general conditions and specifications of the RFP and the selected proposal, as amended by agreement between the Town and the selected Proposer including e-mail or written correspondence relative to the RFP, may become part of the contract documents. Failure of the awarded Contractor to perform as represented may result in elimination of the Contractor from competition or in contract cancellation or termination.

3 SCOPE OF SERVICES

I. Project Objectives

The purpose of this Project is to establish a comprehensive system for receiving and managing citizen service requests from submission through final closure. The Town expects the selected solution to accomplish the following outcomes:

A. Provide residents with a simple, mobile-friendly way to submit and track requests for service and receive timely updates.

B. Create clear departmental and individual ownership, with automated routing, escalation, and supervisory review.

C. Support distinct, configurable back-end routing workflows for citizen-originated, elected-official, and Town Manager-originated requests, while maintaining a consistent request submission process.

D. Coordinate multi-department issues through parent/child or equivalent linked-request functionality.

E. Provide Supervisors, Department Heads, and the Town Manager’s Office with role-appropriate dashboards and reporting tools that provide visibility into request status, aging and overdue items, workload, response and resolution times, trends, and overall service performance.

F. Support GIS, photographs, attachments, mobile field work, secure access, and future system integrations.

G. Allow authorized Town administrators to configure and maintain categories, routing rules, workflows, notices, and reports through available system functionality, with minimal reliance on vendor programming or technical support.

H. Support integration or handoff between citizen requests and current or future work-order / asset-management systems.

I. Support citizen self-service capabilities such as FAQs/knowledge content, request search, alerts/subscriptions, and two-way communication.

J. Provide a mobile application that allows residents to submit service requests, upload photos or supporting information, view the status of submitted requests, receive notifications or updates, and interact with the Town’s request-management process from a mobile device.

II. Software Licensing, Hosting and Platform

The Town prefers a vendor-supported cloud or Software as a Service solution with predictable recurring costs, strong availability, and minimal infrastructure requirements. Vendors may propose another architecture when it provides a clear operational or financial advantage.

III. Core CRM System Functions

The proposed system must manage the full service-request lifecycle on a single, auditable record. Core functionality should include request intake, classification, routing, assignment, reassignment, staff notes, internal notes, attachments, photographs, location information, workflow, escalation, resolution, approval, closure, search, reporting, and history.

The system must allow the Town to configure request categories, subcategories, responsible departments, workgroups, individual assignees, priority, target response times, target completion times, status values, notifications, and approval requirements. Routine configuration should be available to authorized Town administrators without custom development.

IV. Citizen-Facing Experience

The citizen-facing experience should be clean, intuitive, mobile-friendly, and consistent with the Town's website and branding. Residents should be able to submit requests from a mobile browser, mobile app, or desktop. Authorized Town staff should also be able to submit requests on behalf of residents. The experience should support category-specific questions, location capture, photographs or video, status tracking, request search, two-way communication, knowledge-base/FAQ content, and configurable alerts or subscriptions.

The proposed public interface must be capable of being linked from, embedded within, or otherwise presented seamlessly through the Town's website. The Town currently anticipates requestor contact information for submitted service requests. Vendors should describe registered-user and identity/contact verification options, and whether anonymous submission can be disabled. For non-emergency Police request types, the Town must be able to display a prominent disclaimer directing users to 911 or other emergency channels when an immediate police response is required.

Citizen Experience Minimum Expectation

Submission Responsive web experience for desktops, tablets, and mobile devices.

Location Address search, map selection, and geographic validation where supported.

Attachments Photographs and supporting documents with configurable file controls.

Confirmation Immediate acknowledgment and a unique request/case number.

Tracking Ability for the requestor to review status of their request.

Communication Email notifications at minimum; SMS capability is optional.

Accessibility Conformance with WCAG 2.1 accessibility standards and applicable public-sector web accessibility requirements and best practices.

Mobile Application Include native mobile-app availability, supported platforms, quick links, notifications, and whether capabilities differ from the mobile web portal.

Two-Way Communication Staff can request additional information from the residents while preserving the communication history with the request.

Knowledge Base / FAQ Display configurable help or FAQ content before or during request submission to answer common questions and reduce unnecessary requests.

Alerts / Subscriptions Allow residents to subscribe to configured topics, areas, events, closures, or service updates where supported.

V. Organization-Wide Workflow

Request origin is a required workflow attribute because it determines routing, oversight, and final closure authority. Requests may originate directly from a citizen, from an elected official, or from the Town Manager's Office. The current Town workflow diagram also identifies department-level routing for Individual departments with routing by topic and assignee and with parent/child ticket controls when more than one department is responsible.

A. Citizen-Originated Requests

A citizen request should be acknowledged automatically, classified, and routed to the department responsible. Assigned staff investigate the issue, document the work performed, and mark the request resolved or soft closed. For purposes of this workflow, soft close means the assigned staff member has completed the work and submitted the request for supervisory review, but the request remains open within the system pending final approval.

The Department Head or designated approver reviews the completed work. Rejected work returns to the assigned staff member for additional action. Approved work is hard closed by the Department Head, after which the citizen receives a closure notification. Hard close means the request has received final departmental approval, no further action is expected, and the request is considered formally closed.

Following hard closure, the citizen receives a closure notification.

B. Elected Official-Originated Requests

An issue reported or forwarded by an elected official is received by the Town Manager's Office and routed to the department responsible. Staff complete the work and the Department Head reviews the resolution.

Once departmental approval is complete, the request returns to the Town Manager's Office for final hard close. The Town Manager's Office must retain visibility into all tickets throughout the entire process, regardless of the request's origin or submission method.

C. Town Manager's Office-Originated Requests

Requests initiated by the Town Manager's Office follow the same departmental work and approval process, but final hard close remains with the Town Manager's Office. The system must be capable of preventing premature closure by users who do not hold the required final-approval authority.

VI. Multi-Department Requests

Some issues require coordinated work by more than one department. The system must support a master/parent request and separate departmental child requests or provide an equivalent linked-workflow design that gives each department independent ownership while preserving one overall record of the citizen issue.

Each participating department must be able to complete and obtain approval for its portion of the work independently. The parent request must remain open while any required child request is incomplete or unapproved. Authorized users should be able to view the status of all related work from one location, and the system should prevent accidental closure of the parent request before all required departmental work is complete.

The system should also support identifying and managing duplicate or related requests, such as multiple residents reporting the same issue. Authorized staff should be able to link or consolidate these requests while maintaining appropriate tracking, reporting, and communication with each requester.

VII. Departmental Configuration

The CRM will be used across multiple departments. The Town expects a common organization-wide framework with department-specific categories, topics, routing, notifications, service targets, staff assignments, approval paths, and configurable forms. Initial departmental use includes Parks & Recreation, Police for non-emergency matters, Planning, Public Works, Administration, and Fire.

Department Examples of Initial Use

Parks & Recreation Trail maintenance, restrooms, graffiti coordination, playgrounds, facility issues, rentals, and other parks/recreation requests; route by topic and assignee.

Police Approved non-emergency traffic, parking, graffiti coordination, and community concerns. The CRM is not intended to replace 911, CAD, or emergency communications.

Planning Code enforcement, zoning enforcement, development inquiries, transit/bus inquiries, utility/encroachment inquiries, and related planning questions.

Public Works

Trash pickup, street and sidewalk issues, signs/striping, street lighting, building maintenance, downtown dumpsters, traffic signals, stormwater, street sweeping, and other public works service requests.

Administration Administrative topics routed by category/topic and assignee.

VIII. GIS, Mapping and Mobile Operations

Geographic information is part of service-request intake and management. The solution should support address lookup, map-based request submission, geocoding, geographic search, internal heat maps, service-area/geofence routing, request visualization, and use of relevant Town GIS layers. Vendors must describe integration with Esri/ArcGIS services and how the solution can reference or interoperate with iMAPS or other parcel/location resources used by the Town. Public display of an interactive request map is not required; internal mapping and geographic analysis are required or strongly preferred as identified in Appendix C.

Field staff must be able to work from a practical web interface. At minimum, staff should be able to view assignments and location information, add notes, update status, capture and upload photographs, and complete or soft-close work. Vendors should identify whether this capability is delivered through a responsive browser, native application, or both, and whether offline work is supported.

IX. Notifications and Communications

The system must maintain a reliable communication history associated with each request. A resident should receive confirmation when a request is submitted and a final notification after the appropriate approval and closure. The Town should be able to configure additional notices for information requests, status changes, delays, scheduled work, events, closures, cancellations, or other milestones without custom development.

Two-way resident communication is desired so staff can request additional information without losing the request history.

Internal notifications should support assignments, reassignment, aging, escalation, Department Head approval, rejected work, and final-review requirements. Email is required. SMS/text messaging is optional and should be separately identified if it carries additional cost.

X. Reporting and Management Visibility

The selected system must provide useful operational reporting. Reports and dashboards should allow authorized users to understand request volume, backlog, aging, response and resolution time, department workload, staff assignments, request origin, geographic concentrations, escalations, and multi-department activity.

Audience Dashboard Focus

Assigned Staff My open work, due items, overdue requests, returned work, recent updates, and workload.

Department Heads Department workload, aging, requests awaiting approval, overdue work, staff assignments, escalations, and performance data.

Town Manager's Office

Organization-wide volume, aging, department performance, escalations, elected-official requests, Town Manager-originated requests, multi-department requests, and items awaiting final close.

Authorized Town users should be able to create, filter, export, schedule, and modify reports without vendor programming. Historical search should support request number, requestor, address, location, department, category, staff member, date, status, keyword, and request origin.

XI. Roles, Security and Administration

The system must provide role-based access control appropriate for a municipal environment. The Town anticipates roles such as staff user, supervisor, administrator, Department Head, Manager and Town Manager's Office. Permissions must be configurable and should support separation between public information and internal information.

The solution must support encryption in transit and at rest, multi-factor authentication, centralized authentication/SSO with Okta, Microsoft Entra ID or an equivalent standards-based method, administrative and audit logging, secure backup, disaster recovery, vulnerability management, and a documented incident-response process. Vendors must identify independent security attestations such as SOC 2 Type II or equivalent where available.

All Town data must remain the property of the Town of Wendell. Vendors must describe data location, retention, backup, export formats, end-of-contract data return, and secure deletion. The Town must be able to retrieve its information in a commonly usable format without unreasonable dependency on the vendor.

XII. Integration and Data Transition

The proposed CRM will replace the Town’s current Revize Public Service Request system as the primary resident-facing service request platform.

Vendors should explain how the proposed CRM will support the Town’s required workflows and how it can exchange data with current or future work-order or asset-management platforms, including systems such as Accela, Brightly, Tyler Cityworks, or other platforms selected by the Town.

Vendors must also address interoperability with ArcGIS and the Town's use of iMAPS and Bluebeam, as applicable to the proposed architecture.

Area Vendor Response Required

Website Integration Explain how the public request experience will be linked, embedded, branded, migrated from, or otherwise integrated with the Town website and current public-request entry point.

ArcGIS / Esri Describe map, geocoding, layer, feature-service, location validation, and GIS data integration capabilities and related licensing or professional-service costs.

iMAPS Describe options to reference, link, or integrate parcel/property/location information where technically and contractually feasible.

Future Work-Order / Asset Systems

Describe standards-based integration with potential future platforms such as Brightly, Tyler Cityworks, Accela, or other Town-selected systems. The list is illustrative and not exhaustive.

APIs / Integration Identify APIs, webhooks, middleware, authentication methods, data-exchange options, import/export methods, rate limits, limitations, and additional costs.

Historical Data Provide separate options for no migration, open/active requests only, selected history, and full migration where feasible.

Cutover Describe how the vendor will minimize disruption and preserve open work, routing, citizen communications, identifiers, and audit history during transition.

XIII. Services to Be Provided

The selected vendor will be responsible for the professional services required to place the solution into production and support a successful transition. Services are expected to include project management, discovery and workflow validation, system configuration, portal Customization, departmental setup, security roles, request categories, routing, approvals, notifications, GIS and integration work, reports, dashboards, testing, training, go-live support, and post-implementation stabilization.

The vendor must designate a qualified Project Manager who will serve as the primary implementation contact, maintain the project plan, coordinate vendor resources, manage risks and schedule, facilitate status meetings, and provide regular progress updates. The proposal should identify the proposed project team and relevant municipal implementation experience.

XIV. Project Plan, Testing and Training

The proposal must include a realistic implementation plan with major phases, deliverables, assumptions, dependencies, Town responsibilities, vendor responsibilities, testing, training, and go-live activities. The Town is interested in a deliberate implementation that validates workflow and security before production use rather than an accelerated deployment.

User Acceptance Testing must include the major workflows described in this RFP, including citizen submission, automated routing, staff resolution, Department Head approval, rejected work, elected-official routing, Town Manager final closure, parent/child requests, notifications, reports, GIS, mobile use, and role-based permissions. Material workflow defects must be resolved before final production acceptance.

Training must be appropriate for system administrators, Department Heads, supervisors, staff users, the Town Manager's Office, and users who will create reports or maintain configuration. The Town prefers reusable training materials and permission to record instructor-led sessions for internal use.

XV. Ongoing Support and Service Levels

The vendor must provide ongoing maintenance and support for the proposed system. The proposal shall describe support hours, support channels, severity levels, response targets, escalation procedures, planned maintenance, software-release practices, security updates, major upgrades, customer-success resources, and the handling of configuration during upgrades.

Service Area System Information Required

Availability Published service availability commitment and historical uptime, if available.

Critical Support Response and escalation process for outages, security events, or material loss of functionality.

Backups / Recovery Backup frequency, retention, Recovery Point Objective, Recovery Time Objective, and disaster-recovery approach.

Upgrades Release frequency, testing process, advance notice, and impact on Town configuration or integrations.

Support Model Support hours, channels, severity definitions, response targets, and escalation contacts.

4 COST PROPOSAL/EXECUTION OF PROPOSAL

CATEGORY Year 1 Year 2 Year 3 Year 4 Year 5

One-Time Implementation Cost $

Software Licensing / Subscription $ $ $ $ $

Training $ $ $ $ $

Support & Maintenance (if not included) $ $ $ $ $

Hosting (if not included) $ $ $ $ $

Other Costs $ $ $ $ $

TOTAL ANNUAL COST $ $ $ $ $

5-Year Total Cost $________________________________

Identify all costs associated with the proposed solution. If hosting, maintenance, support, upgrades, or other recurring services are included within the software subscription fee, vendors shall indicate "Included" rather than listing a separate cost.

Vendors may attach supplemental pricing sheets as necessary to fully describe and itemize proposed costs. Supplemental sheets shall reference the applicable category shown in the Cost Proposal form and shall be included in the Five-Year Total Cost of Ownership calculation unless identified as optional.

The proposal must identify:

• Hosting environment and associated costs

• Software licensing or subscription model and basis of pricing

• Administrative, staff, departmental and enterprise licensing

• Citizen or public user access model

• Storage limits, overage fees, and data retention costs

• API or integration fees

• Mobile licensing costs

• GIS-related costs

• Optional modules

• Implementation, configuration, data migration, training and project management fees

• Ongoing support, maintenance, upgrade, and renewal costs; and

• Any third-party software, products, or services required for full functionality of the proposed solution.

By submitting this proposal, the potential contractor certifies the following:

• This proposal is signed by an authorized representative of the firm.

• The potential contractor has read and understands the conditions set forth in this RFP to include general conditions/service terms, any addenda, and all attached exhibits and agrees to them with no exceptions.

Vendor Name: _________________________

By:

(Signature)

Name:

(Printed)

Title:

Date

5 REFERENCES

Offeror must supply (3) three Governmental Agency or Private Company references for which services have been performed during the past (5) five years. Offerors are cautioned to provide accurate reference information. References will be checked during evaluation period.

OFFEROR: _________________________________________________________________

CITY, STATE, ZIP: __________________________________________________________

Reference # 1

Firm Name & Contact Name: ________________________________________________________

Business Address _____________________________________________________________

City: ______________________________ State: ________ Zip Code: _____________

Phone Number: (____) ______________________

Email Address: ______________________________________________________________

Reference # 2

Firm Name & Contact Name: ________________________________________________________

Business Address _____________________________________________________________

City: ______________________________ State: ________ Zip Code: _____________

Reference # 3

Firm Name& Contact Name: ________________________________________________________

Business Address ____________________________________________________________

City: ______________________________ State: ________ Zip Code: _____________

APPENDIX A - INSTRUCTIONS TO VENDORS

1. READ, REVIEW AND COMPLY: It shall be the Vendor’s responsibility to read this entire document, review all enclosures and attachments, and any addenda thereto, and comply with all requirements specified herein, regardless of whether appearing in these Instructions to Vendors or elsewhere in this RFP document.

2. ACCEPTANCE AND REJECTION: The Town reserves the right to reject any and all proposals, to waive any informality in proposals and, unless otherwise specified by the Vendor, to accept any item in the proposal. If either a unit price or an extended price is obviously in error and the other is obviously correct, the incorrect price will be disregarded.

3. BASIS FOR REJECTION: The Town reserves the right to reject any and all offers, in whole or in part, by deeming the offer unsatisfactory as to quality or quantity, delivery, price or service offered, non-compliance with the requirements or intent of this solicitation, lack of competitiveness, error(s) in specifications or indications that revision would be advantageous to the Town, cancellation or other changes in the intended project or any other determination that the proposed requirement is no longer needed, limitation or lack of available funds, circumstances that prevent determination of the best offer, or any other determination that rejection would be in the best interest of the Town.

4. EXECUTION: Failure to sign EXECUTION PAGE in the indicated space will render proposal non-responsive, and it shall be rejected.

5. ORDER OF PRECEDENCE: In cases of conflict between specific provisions in this solicitation or those in any resulting contract, the order of precedence shall be (high to low): (1) The Contract Terms,

(2) RFP Terms, (3) Instructions in INSTRUCTIONS TO VENDORS, and (4) Vendor’s Proposal.

6. INFORMATION AND DESCRIPTIVE LITERATURE: Vendor shall furnish all information requested and, in the spaces, provided in this document. Further, if required elsewhere in this proposal, each Vendor must submit with their proposal sketches, descriptive literature and/or complete specifications covering the products offered. Reference to literature submitted with a previous proposal or available elsewhere will not satisfy this provision. Proposals that do not comply with these requirements shall be subject to rejection without further consideration.

7. CONFIDENTIAL INFORMATION: To the extent permitted by applicable statutes and rules, the Town will maintain confidential trade secrets that the Vendor does not wish disclosed. As a condition to confidential treatment, each page containing trade secret information shall be identified in boldface at the top and bottom as “CONFIDENTIAL” by the Vendor, with specific trade secret information enclosed in boxes or similar indication. Cost information shall not be deemed confidential under any circumstances. Regardless of what a Vendor may label as a trade secret, the determination whether it is or is not entitled to protection will be determined in accordance with G.S. 132-1.2. Any material labeled as confidential constitutes a representation by the Vendor that it has made a reasonable effort in good faith to determine that such material is, in fact, a trade secret under G.S. 132-1.2. Vendors are urged and cautioned to limit the marking of information as a trade secret or as confidential so far as is possible.

8. COMMUNICATIONS BY VENDORS: In submitting its proposal, the Vendor agrees not to discuss or otherwise reveal the contents of its proposal to any source, government or private, outside of the using or issuing agency until after the award of the Contract or cancellation of this RFP. All Vendors are forbidden from having any communications with the using or issuing agency, or any other representative therein, concerning the solicitation, during the evaluation of the proposals (i.e., after the public opening of the proposals and before the award of the Contract), unless the Town directly contacts the Vendor(s) for purposes of seeking clarification or another reason permitted by the solicitation. A

Vendor shall not: (a) transmit to the issuing and/or using agency any information commenting on the ability or qualifications of any other Vendor to provide the advertised good, equipment, commodity;

(b) identify defects, errors and/or omissions in any other Vendor’s proposal and/or prices at any time during the procurement process; and/or (c) engage in or attempt any other communication or conduct that could influence the evaluation and/or award of the Contract that is the subject of this RFP. Vendors not in compliance with this provision may be disqualified, at the option of the Town, from the Contract award. Only those communications with the using agency or issuing agency authorized by this RFP are permitted.

9. WITHDRAWAL OF PROPOSAL: A Proposal may be withdrawn only in writing and actually received by the office issuing the RFP prior to the time for the opening of Proposals identified on the cover page of this RFP (or such later date included in an Addendum to the RFP). A withdrawal request must be on Vendor’s letterhead and signed by an official of the Vendor authorized to make such request.

Any withdrawal request made after the opening of Proposals shall be allowed only for good cause shown and in the sole discretion of the Town.

10. INFORMAL COMMENTS: The Town shall not be bound by informal explanations, instructions or information given at any time by anyone on behalf of the Town during the competitive process or after award. The Town is bound only by information provided in this RFP and in formal Addenda issued through the eVP website.

11. COST FOR PROPOSAL PREPARATION: Any costs incurred by Vendor in preparing or submitting offers are the Vendor’s sole responsibility; the Town will not reimburse any Vendor for any costs incurred prior to award.

12. VENDOR’S REPRESENTATIVE: Each Vendor shall submit with its proposal the name, address, and telephone number of the person(s) with authority to bind the firm and answer questions or provide clarification concerning the firm's proposal.

13. SUBCONTRACTING: Unless expressly prohibited, a Vendor may propose to subcontract portions of the work to identified subcontractor(s), provided that its proposal clearly describe what work it plans to subcontract and that Vendor includes in its proposal all information regarding employees, business experience, and other information for each proposed subcontractor that is required to be provided for Vendor itself.

14. INSPECTION AT VENDOR’S SITE: The Town reserves the right to inspect, at a reasonable time, the equipment/item, plant, or other facilities of a prospective Vendor prior to Contract award, and during the Contract term as necessary, for the Town determination that such equipment/item, plant or other facilities conform with the specifications/requirements and are adequate and suitable for the proper and effective performance of the Contract.

APPENDIX B - Town of Wendell Workflow Diagrams

The diagrams below summarize the Town's desired operational controls. The diagrams are intended to communicate the required business process; vendors may propose a different screen design or technical implementation when it preserves the same routing, approval, accountability, notification, escalation, and closure controls.

Figure B-1. Organization-wide citizen request workflow.

Figure B-2. Multi-department request control.

APPENDIX C - Functional Requirements Matrix

For each requirement, enter one response code and provide a concise explanation where needed.

Functionality represented as standard or configurable may be required to be demonstrated using the proposed production platform.

Code Meaning

Y Standard features included in the proposed base solution and price.

C Available through normal configuration without custom development.

M Requires modification or custom development; cost and schedule must be identified.

N Not available.

T Provided through a third-party product or integration;

provider and cost must be identified.

Platform and Integration Feature / Function Response Comments Cloud-hosted production environment Separate test/sandbox environment Okta or Microsoft Entra ID single sign-on Multi-factor authentication REST API and/or modern integration framework Webhooks or event-based integration Website linking, embedding, or integration Esri GIS integration Data export capability Data Backup and disaster recovery Role-based access control and audit logging Work-order system integration / handoff capability Asset-management integration capability Integration capability with Brightly, Tyler Cityworks, Accela, or other future Town-selected systems iMAPS / parcel-location reference capability where feasible

Citizen Experience

Responsive public request portal

Town branding and configurable public interface Submission from desktop, app and mobile browser Address lookup and map-based location selection Photograph and document attachments Immediate submission confirmation Unique request/case number Public status tracking when enabled by Town Registered user option Ability to disable anonymous submissions / require contact information

Email citizen notifications SMS citizen notifications Citizen mobile application Mobile-app quick links / configurable shortcuts Photo and video upload capability Citizen request search Two-way resident/staff communication Knowledge base / FAQ presented before or during submission

Post-closure satisfaction survey / rating (optional) Social-media integration options (optional)

Workflow and Routing

Configurable request categories and subcategories Automatic routing by category Routing by department/workgroup Assignment and reassignment Preservation of request origin Configurable statuses Staff resolution / soft close Department Head approval Rejected work returned to assigned staff Town Manager final approval workflow Configurable escalation and aging rules Target response and completion times Parent/child or equivalent multi-department workflow Parent issues…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .