Holden_RFP_HOL-27-01_Proposal_Forms.docx

DOCX document 29 KB Posted

Attached to
RFP HOL-27-01 - Cloud-Hosted Phone System (UCaaS)
Solicitation number
BD-25-1281-HOLDN-HOLDN-135152
Issued by
Worcester County, Massachusetts

About this file

Summary of Proposal Forms for RFP HOL-27-01

This document comprises the editable proposal forms (Attachments A through F) for the Town of Holden, Massachusetts Request for Proposals for a cloud-hosted phone system (UCaaS), RFP No. HOL-27-01. The Town of Holden seeks to implement a unified communications system serving approximately 195 IP phone users and 38 analog devices across Holden and member-town sites in Paxton, Princeton, and West Boylston. The project encompasses a three-year contract term with sealed paper proposals required in two separate envelopes: a Technical Proposal envelope (Attachments A through E) and a sealed Price Proposal envelope (Attachment F). Proposals are due December 2, 2026, at 2:00 p.m., to be submitted in hard copy to the Office of the Town Manager, 1204 Main St., Holden, MA 01520. The RFP requires proposers to address comprehensive technical requirements including cloud infrastructure, uptime guarantees, call management features, AI-driven capabilities, security compliance, 911 emergency services, hardware provisioning, implementation services, training, and ongoing support.

Pricing must cover all items across the full three-year term on a firm, fixed-price basis, with the Total Three-Year Cost (combining one-time charges and 36 months of recurring monthly charges) serving as the primary cost comparison metric. Key deliverables include 195 new IP desk phones (Yealink T46U or equivalent) and 38 analog adapters, with optional pricing for equipment removal, additional training sessions, text messaging, video meetings, and spare phones. The proposal forms require multiple mandatory certifications including non-collusion, state tax compliance, non-debarment, and conflict of interest disclosures, as well as proof of signatory authority. Proposers must provide at least three references from similar municipal implementations since January 1, 2021, and complete a detailed compliance matrix documenting their response to all mandatory and desirable requirements. The contractor will be responsible for complete project management, number porting, phased or single cutover implementation, on-site support, comprehensive training, and 24/7/365 U.S.-based support throughout the contract term.

View the file

Other files

File Type Posted
RFP HOL-27-01 Cloud-Hosted Phone System UCaaS.pdf PDF

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

TOWN OF HOLDEN, MASSACHUSETTS

REQUEST FOR PROPOSALS – CLOUD-HOSTED PHONE SYSTEM (UCaaS) RFP No. HOL-27-01

PROPOSAL FORMS – ATTACHMENTS A THROUGH F (EDITABLE)

These are editable Word versions of Attachments A through F of RFP No. HOL-27-01. Proposers may complete them electronically by typing in the blank cells, then print and sign them. The forms must be submitted with the proposal as described in Section 4.4 of the RFP:

FORM
TITLE
WHERE IT GOES
Attachment A
Proposal Form and Acknowledgment of Addenda
Technical Proposal envelope
Attachment B
Certifications Required by Law
Technical Proposal envelope
Attachment C
Reference Form
Technical Proposal envelope
Attachment D
Clerk's Certificate of Authority
Technical Proposal envelope
Attachment E
Compliance Matrix
Technical Proposal envelope
Attachment F
Price Proposal Form
Price Proposal envelope ONLY

1. All forms requiring a signature must be signed by the same authorized person who will sign the contract on behalf of the proposer.

1. Do not change the wording of any form. Unauthorized changes to the RFP forms are prohibited and may disqualify a proposal.

1. If this file and the RFP differ, the RFP (including any addenda) governs.

1. Do not include any pricing in the Technical Proposal. Attachment F goes only in the sealed Price Proposal envelope.

ATTACHMENT A

PROPOSAL FORM AND ACKNOWLEDGMENT OF ADDENDA

Include in the Technical Proposal envelope RFP Title: Cloud-Hosted Phone System (UCaaS) RFP No.: HOL-27-01 The undersigned proposes to furnish the cloud-hosted phone system, equipment and services described in this Request for Proposals, in accordance with all of its terms, conditions and specifications, and agrees that this proposal will remain valid for ninety (90) days after the proposal due date. The undersigned certifies that it has read and understands this RFP and all addenda, that the Price Proposal is submitted separately in a sealed envelope, and that it will sign the Town's contract (Exhibit 1) if selected.

Legal name of proposer

Business address

Type of entity (corporation, LLC, partnership, etc.) and state of organization

Federal Tax ID number

Contact person, title

Telephone / email

Massachusetts office location, if any

Acknowledgment of Addenda The proposer acknowledges receipt of the following addenda (enter "None" if no addenda were issued):

ADDENDUM NO.
DATE
ADDENDUM NO.
DATE

Authorized Signature

Date

Print Name & Title

ATTACHMENT B

CERTIFICATIONS REQUIRED BY LAW

Include in the Technical Proposal envelope. All certifications must be executed.

CERTIFICATE OF NON-COLLUSION

Pursuant to M.G.L. c. 30B, §10 The undersigned certifies under penalties of perjury that this bid or proposal has been made and submitted in good faith and without collusion or fraud with any other person. As used in this certification, the word "person" shall mean any natural person, business, partnership, corporation, union, committee, club, or other organization, entity, or group of individuals.

Authorized Signature

Date

Print Name & Title

Name of Proposer

CERTIFICATE OF STATE TAX COMPLIANCE

Pursuant to M.G.L. c. 62C, §49A I, the authorized signatory named below, for the proposer named below, whose principal place of business is stated below, certify under the penalties of perjury that, to the best of my knowledge and belief, the proposer is in compliance with all laws of the Commonwealth of Massachusetts relating to taxes, reporting of employees and contractors, and withholding and remitting child support.

Name of authorized signatory

Name of proposer

Principal place of business

Signature

Date

Print Name & Title

Federal Tax ID Number

CERTIFICATE OF NON-DEBARMENT

The undersigned certifies under penalties of perjury that the proposer, its principals and its proposed subcontractors are not currently debarred, suspended or otherwise excluded from bidding on or working on public contracts by the Commonwealth of Massachusetts, under M.G.L. c. 29, §29F or any other law, or by any agency of the federal government, and are not included on any state or federal list of debarred or suspended contractors.

Authorized Signature

Date

Print Name & Title

CERTIFICATE OF COMPLIANCE WITH CONFLICT OF INTEREST LAW

The undersigned certifies that the proposer is familiar with the Massachusetts Conflict of Interest Law, M.G.L. c. 268A, and that, to the best of its knowledge, no employee or official of the Town of Holden has a financial interest in this proposal or in the proposer, except as disclosed below:

Disclosure (if none, write "None")

Authorized Signature

Date

Print Name & Title

ATTACHMENT C

REFERENCE FORM

Include in the Technical Proposal envelope Proposer (legal name)

RFP Title: Cloud-Hosted Phone System (UCaaS) RFP No.: HOL-27-01 Provide at least three references from current or recent projects similar in scope and size to this RFP, preferably Massachusetts municipalities, for which the proposer has provided hosted phone systems since January 1, 2021. Do not use the Town of Holden as a reference.

Reference 1 Organization

Contact name & title

Phone / email

Address

Number of users / sites

Description and dates of services provided

Reference 2 Organization

Contact name & title

Phone / email

Address

Number of users / sites

Description and dates of services provided

Reference 3 Organization

Contact name & title

Phone / email

Address

Number of users / sites

Description and dates of services provided

Attach additional sheets if necessary.

ATTACHMENT D

CLERK'S CERTIFICATE OF AUTHORITY

Include in the Technical Proposal envelope I, the Clerk/Secretary named below, certify that I am the duly elected Clerk/Secretary of the corporation named below (the "Corporation"), a corporation organized under the laws of the state stated below, and that:

Name of Clerk/Secretary

Name of Corporation

State of organization

a)the officer named below is authorized to sign proposals, contracts and other documents on behalf of the Corporation, and to bind the Corporation to their terms;
b)this authority was granted by vote of the Corporation's Board of Directors or shareholders at a meeting held on the date stated below, and remains in full force and effect as of the date below; and
c)the officer named below signed the proposal submitted in response to the Town of Holden Request for Proposals for a Cloud-Hosted Phone System (UCaaS), RFP No. HOL-27-01.
Name of authorized officer

Title of authorized officer

Date of meeting / vote

Clerk/Secretary Signature

Date

Print Name

(Corporate Seal) If the proposer is not a corporation, attach equivalent evidence of the signer's authority (for example, a certificate of the manager of a limited liability company).

ATTACHMENT E

COMPLIANCE MATRIX

Include in the Technical Proposal envelope. Do not include prices.

For each requirement, enter Comply, Partial, Alternative or Does Not Comply and a short explanation. In the last column, state whether the item is included in the proposed base service or is an extra-cost item (do not state prices). Any exception to a requirement must be stated here. A proposal that does not comply with every mandatory (M) requirement does not meet Minimum Criterion 2.

ITEM
REQUIREMENT
M/D
RESPONSE
EXPLANATION
INCL. / EXTRA
3.2.1(a)
Fully cloud-hosted platform in at least two geographically separate U.S. data centers with automatic failover.
M
3.2.1(b)
Financially backed uptime SLA of at least 99.99% per month, with service credits.
M
3.2.1(c)
Financially backed uptime SLA of 99.999% per month.
D
3.2.1(d)
An on-site survivability appliance or gateway at the Public Safety Building that keeps internal calling and 911 calling working if the building loses internet service.
D
3.2.1(e)
All Town data, call records, voicemail and AI-generated content stored and processed only in the United States.
M
3.2.1(f)
Survivability: when a site's internet fails, calls automatically re-route to mobile apps, another site or a defined number, and staff can keep working from any Town location if an office must close.
M
3.2.1(g)
Software updates, upgrades and new features delivered automatically at no extra cost during the term.
M
3.2.1(h)
The proposal identifies the specific service plan or tier proposed, and that plan includes every mandatory (M) feature in this RFP. No mandatory feature may require a higher plan tier or an add-on not shown on Attachment F.
M
3.2.1(i)
Scalable to at least 300 extensions without replacing the platform, with lines added or removed at the contract per-line rate.
M
3.2.1(j)
Native Microsoft Teams integration (direct routing or certified Teams calling) so staff can call from Teams.
D
3.2.1(k)
Single administrator portal for all sites, users, call flows and reports, with role-based access for department administrators.
M
3.2.2(a)
Direct dial number for each user and four-digit extension dialing between all Town sites.
M
3.2.2(b)
Unlimited domestic (U.S. and Canada) calling for all users, with no per-minute charges.
M
3.2.2(c)
Hold, transfer (blind and warm), conference (at least 6 parties), call park and pickup, call forwarding, do-not-disturb, caller ID and call history.
M
3.2.2(d)
Voicemail-to-email and visual voicemail.
M
3.2.2(e)
Auto attendants with time-of-day, holiday and emergency-closure schedules that department administrators can change themselves.
M
3.2.2(f)
Hunt groups and call queues with music on hold, announcements and overflow.
M
3.2.2(g)
Desktop (Windows/Mac) and mobile (iOS/Android) apps so users can make and take calls on their Town number from anywhere.
M
3.2.2(h)
Shared lines/bridged line appearances and busy lamp field for front-office staff.
M
3.2.2(i)
Paging and intercom through phone speakers, and integration with existing overhead paging at the Public Safety Building (two paging lines) and the Library.
M
3.2.2(j)
Fax solution (e-fax or ATA) for current fax lines.
M
3.2.2(k)
For elevator emergency phones, fire alarm and other life-safety lines, the proposal states how each will be supported in compliance with applicable code (for example, a dedicated line or an approved cellular communicator), or confirms that the Town will keep separate service for these lines.
M
3.2.2(l)
Dial-by-name directory for callers and a searchable employee directory for staff.
M
3.2.2(m)
Basic business text messaging (SMS) from Town numbers, including shared department text inboxes, with 10DLC registration handled by the Contractor.
D
3.2.2(n)
Video meetings and screen sharing within the same platform.
D
3.2.2(o)
Presence and chat integrated with Microsoft 365.
D
3.2.2(p)
Hot desking, so staff can log in to any Town phone with their own extension (for example, for police and fire shifts and shared offices).
D
3.2.2(q)
Moving a live call between devices (desk phone, computer and mobile app) without hanging up.
D
3.2.2(r)
Call delegation, so an assistant can answer and manage calls on behalf of another user.
D
3.2.3(a)
A voicemail box for every user, including staff with no phone (for example, patrol officers).
M
3.2.3(b)
Remote voicemail access, and the ability to change greetings and PINs remotely.
M
3.2.3(c)
Separate greetings for internal and external callers, plus out-of-office greetings.
M
3.2.3(d)
Forward a voicemail to one or more coworkers with a recorded comment.
M
3.2.3(e)
Transfer a caller directly into any user's voicemail.
M
3.2.3(f)
Scheduled after-hours and holiday greetings on main and department numbers.
M
3.2.4(a)
One central call accounting system for all sites that shows which extension placed or received each call, regardless of the phone's physical location.
M
3.2.4(b)
Call detail records (CDR) exportable to Microsoft Excel or CSV.
M
3.2.5(a)
AI virtual receptionist / voice agent that answers the main number and department lines 24/7 in natural language, answers common questions from a Town-approved knowledge base (hours, trash schedule, permits), and routes callers to the right person or queue.
D
3.2.5(b)
Multilingual support: the AI receptionist and live calls support at least English and Spanish, including real-time translation or captions.
D
3.2.5(c)
Call transcription and AI summaries with action items, saved to the user's call history.
D
3.2.5(d)
Voicemail transcription and AI summary delivered by email and in the app.
D
3.2.5(e)
AI meeting assistant for video meetings: transcripts, summaries and action items.
D
3.2.5(f)
AI noise and echo suppression for calls and meetings.
D
3.2.5(g)
AI analytics: call volume trends, peak-hour forecasting and missed-call insights by department.
D
3.2.5(h)
Natural-language administration and reporting (for example, "show me missed calls to the Clerk's office last week").
D
3.2.5(i)
The proposal explains how each AI feature is billed (included, per user, per minute or per agent). For any usage-based AI feature, the system provides usage alerts and a Town-set spending cap.
M
3.2.6(a)
Town content (audio, transcripts, summaries, voicemail, knowledge base) is never used to train or improve the Contractor's or any third party's AI models.
M
3.2.6(b)
AI call transcription supports an automatic caller announcement and is off by default until the Town enables it, so the Town can comply with M.G.L. c. 272, §99 (all-party consent).
M
3.2.6(c)
The AI receptionist identifies itself as an automated assistant and gives callers a way to reach a person.
M
3.2.6(d)
The Town controls retention periods for transcripts, summaries and voicemail, and can export and delete them, to meet the Massachusetts Public Records Law (M.G.L. c. 66) and the Municipal Records Retention Schedule.
M
3.2.6(e)
The Contractor discloses all subprocessors and AI model providers, and notifies the Town before changing them.
M
3.2.6(f)
The Town can review and approve the knowledge base and scripts the AI receptionist uses before go-live.
M
3.2.7(a)
Compliance with Kari's Law: direct 911 dialing with no prefix, and notification (email, SMS, screen pop or desk-phone alert) to designated Town staff whenever 911 is dialed.
M
3.2.7(b)
Compliance with RAY BAUM'S Act: dispatchable location (address plus building, floor and room) sent with every 911 call, including for softphone and remote users, with location updates when a user moves.
M
3.2.7(c)
Compliance with Massachusetts State 911 Department requirements for multi-line telephone systems.
M
3.2.7(d)
911 calls route to the correct PSAP for each site and work during a site's internet outage through the survivability plan.
M
3.2.7(e)
The Contractor builds and maintains the E911 location database for all lines, including member-town sites in Paxton, Princeton and West Boylston, with each site's correct civic address and 911 routing, and tests 911 at every site before cutover.
M
3.2.8(a)
Encryption in transit (TLS/SRTP) and at rest.
M
3.2.8(b)
Single sign-on with Microsoft Entra ID and multi-factor authentication for administrator and user portals.
M
3.2.8(c)
Current SOC 2 Type II report (or equivalent) provided on request.
M
3.2.8(d)
Toll-fraud protection, international calling blocked by default, and alerts for unusual call activity.
M
3.2.8(e)
Written notice to the Town within 72 hours of any security incident affecting Town data, consistent with M.G.L. c. 93H.
M
3.2.8(f)
Administrator audit logs available to the Town.
M
3.2.8(g)
Ability to place voicemail, text messages and transcripts on legal hold and export them for public records requests and litigation.
M
3.2.8(h)
STIR/SHAKEN call authentication and spam and robocall labeling or blocking, with administrator-adjustable settings, including blocking spam before it reaches the AI receptionist.
D
3.2.8(i)
CJIS-compliant configuration for Police Department lines.
D
3.2.9(a)
New handsets (not refurbished unless the Town agrees in writing) certified by the platform, PoE-powered, with color display and headset port.
M
3.2.9(b)
Every desk phone has a speakerphone, a message-waiting light, and a built-in gigabit network switch port so a PC can connect through the phone.
M
3.2.9(c)
Hearing-aid compatible and ADA-accessible options, including TTY/RTT support.
M
3.2.9(d)
Zero-touch provisioning and remote firmware updates.
M
3.2.9(e)
Handsets purchased by the Town are open-standard SIP phones that can be re-provisioned on another provider's platform, so the Town can keep them if it changes providers at the end of the contract.
M
3.2.9(f)
EPEAT-registered devices and a take-back or recycling program for the Town's old phones.
D
3.3.1(a)
Named project manager and implementation engineer for the duration of the project.
M
3.3.1(b)
Kickoff within 10 business days of contract execution, followed by a written project plan and schedule.
M
3.3.1(c)
Network readiness assessment of every site before configuration, with written findings on bandwidth, QoS and PoE, including the upload and download bandwidth the system needs at each site so the Town can confirm its internet service is sufficient.
M
3.3.1(d)
Discovery sessions with each department to design call flows, auto attendants and queues; the Town approves the final design in writing.
M
3.3.1(e)
The Contractor manages all number porting, including coordination with the current carrier (Uniti), and gives the Town at least 5 business days' notice of each port date.
M
3.3.1(f)
Phased or single cutover outside business hours, with a written rollback plan.
M
3.3.1(g)
On-site support at all locations listed in Attachment G on the first business day after cutover.
M
3.3.1(h)
Removal and recycling of the Town's old phone equipment if the Town requests it (priced as an optional item).
M
3.3.1(i)
Full system configuration documentation: user list, numbers, call flows by station, E911 locations and administrator guides, delivered electronically.
M
3.3.2(a)
End-user training (live virtual or on-site, recorded for later use) plus quick-reference guides.
M
3.3.2(b)
Administrator training for the Town's IT staff and department administrators on moves/adds/changes, auto attendant schedules, reporting and AI settings.
M
3.3.2(c)
Two (2) on-site training sessions at Town Hall.
D
3.3.3(a)
24/7/365 U.S.-based support by phone, email and portal, including remote access to resolve service issues.
M
3.3.3(b)
Unlimited moves, adds and changes by the Contractor at no charge, plus Town self-service in the administrator portal.
M
3.3.3(c)
Service credits for missed uptime SLA, stated in the proposal.
M
3.3.3(d)
Named account manager and quarterly service reviews with usage, SLA and AI reports.
M
3.3.3(e)
Advance replacement of failed handsets for the full contract term.
M
3.4(a)
Before cutover, the Contractor tests every site, including call quality (QoS), all call flows, voicemail, paging, fax and 911, and gives the Town the written results.
M
3.4(b)
System Acceptance occurs when the Town confirms in writing that the system has run for 30 days after final cutover with no unresolved Priority 1 or 2 issues. Final payment of one-time charges is due only after System Acceptance.
M
3.4(c)
All equipment and software come with the manufacturer's warranty. New equipment not covered by the manufacturer's warranty may be returned at any time for a full refund. For all system purchases, the warranty period begins on the System Acceptance Date.
M
3.4(d)
A full warranty of at least one (1) year from System Acceptance covering all hardware, software and labor, with warranty service available 24/7/365, including remote access to resolve service and maintenance issues.
M
3.4(e)
After the warranty period, maintenance and support of all hardware and software for the remainder of the contract term, included in the recurring price.
M
3.4(f)
Warranty longer than one (1) year at no additional charge. Proposers must state the length of any extended warranty in their proposal.
D

ATTACHMENT F

PRICE PROPOSAL FORM

SUBMIT ONLY IN THE SEALED PRICE PROPOSAL ENVELOPE

Proposer (legal name)

RFP Title: Cloud-Hosted Phone System (UCaaS) RFP No.: HOL-27-01 Price every line. Prices must be firm for the full three-year term. The Total Three-Year Cost (one-time charges plus 36 months of recurring charges) will be used to compare proposals under Section 4.16. Quantities cover all Holden and member-town sites in Attachment G: 195 IP phones and about 38 analog devices. Line 1 covers the 195 IP phone users; line 2 covers the analog devices (fax, conference, cordless, elevator, paging and similar lines), which may be priced at a lower-cost license type if available. Line 9 is the new IP desk phones (Town reference model: Yealink T46U or equal) and line 11 is the analog adapters. State the plan or tier proposed (Section 3.2.1).

Plan / tier proposed

#
ITEM
QTY
UNIT PRICE
MONTHLY (x 36)
ONE-TIME
THREE-YEAR TOTAL
1
Cloud calling license – full user (all Section 3.2 features, unlimited U.S./Canada calling)
195
2
Analog device, fax or common-area license (if priced lower than a full user)
38
3
AI virtual receptionist / voice agent for the main Town number. State the billing basis (per receptionist or per minute) and the minutes included, if any.
1
4
AI transcription and summaries (if not included)
195
5
AI analytics (if not included). If priced per user or per administrator, state the unit and the price per unit.
1 (account-wide)
6
Microsoft Teams integration (if not included)
195
7
Fax / analog line service
9
8
Phone numbers (DIDs) and toll-free numbers
221
9
Standard desk phone (purchase)
195
10
Cordless/DECT handset and base (purchase)
1
11
Analog adapter (ATA) (purchase)
38
12
Implementation, porting, configuration and project management
1
13
Training
1
14
Day-one on-site support
1
15
Maintenance and support of Town-owned equipment after the warranty period (if not included in licenses). State the monthly price and the number of months it applies in the three-year term (expected approximately 20); three-year total = monthly × months.
1 (lot)
16
Other items required for a complete, working system (list each item, quantity and purpose). Any item needed to deliver the system described in this RFP that is not priced on this form will be provided at no additional cost to the Town.
As listed

TOTAL THREE-YEAR COST

Regulatory fees and surcharges (Section 4.18). List every fee or surcharge that would appear on Town invoices. Fees not listed here may not be invoiced.

FEE OR SURCHARGE
CURRENT RATE
EST. MONTHLY

Optional items (priced separately; not included in the Total Three-Year Cost):

#
OPTIONAL ITEM
MONTHLY
ONE-TIME
O-1
Removal and recycling of old phone equipment
O-2
Additional on-site training (per session)
O-3
Basic business text messaging (SMS), including shared department inboxes and 10DLC registration
O-4
Video meetings
O-5
On-site survivability appliance or gateway – Public Safety Building (if not included)
O-6
Additional user license (per user, per month)
O-7
Spare desk phones – five (5), same model as line 9 (price per phone)

Authorized Signature

Date

Print Name & Title

Town of Holden of RFP No. HOL-27-01 – Proposal Forms

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