Enterprise-Wide Direct Internet Access (DIA) and Commodity Broadband Circu Addendum 1

Location: Vermont
Posted: Mar 25, 2026
Due: Apr 17, 2026
Agency: State of Vermont
Type of Government: State & Local
Category:
  • D - Automatic Data Processing and Telecommunication Services
Publication URL: To access bid details, please log in.
TITLE QUESTIONS DUE ANSWERS POSTED DUE DATE NO POSTING AFTER
Enterprise-Wide Direct Internet Access (DIA) and Commodity Broadband Circu
Bidder Response Form
Addendum 1

03/27/2026 04:30PM


04/17/2026 04:30PM

Attachment Preview

ATTACHMENT A:

BIDDER RESPONSE FORM

State of Vermont Bidder Response Form

Request for Proposal Name: Enterprise-Wide Direct Internet Access (DIA) Circuits for the State of Vermont

Vendor Instructions:

Provide the information requested in this form and submit it to the State of Vermont as part of your Request for Proposal (RFP) response. All answers must be provided within the form unless otherwise specified.

Important: This form must be completed and submitted in response to this RFP for your proposal to be considered valid. The submission must also include the eight (8) additional artifacts requested within this form (denoted by underlined green font).

See the RFP for full instructions for submitting a bid. Bids must be received by the due date and at the location specified on the cover page of the RFP.

Direct any questions you have concerning this form or the RFP to:

STATE CONTACT

State of Vermont

Office of Purchasing & Contracting

E-mail Address:

Part 1: VENDOR PROFILE

Complete the table below.

Provide a brief overview of your company including number of years in business, number of employees, nature of business, and description of clients. Identify any parent corporation and/or subsidiaries.

Is your organization currently or has it previously provided solutions and/or services to any agency or entity of the Vermont State government within the past five years? If so, include a complete list of the State entities, the solutions and/or services provided, and the dates your organization provided the State with these services in the last five years.

Provide a Financial Statement* for your company and label it Attachment #1. This requirement can be filled by:

A current Dun and Bradstreet Report that includes a financial analysis of the firm;

An Annual Report if it contains (at a minimum) a Compiled Income Statement and Balance Sheet verified by a Certified Public Accounting firm; or

Tax returns and financial statements including income statements and balance sheets for the most recent 3 years, and any available credit reports.

A confidentiality statement may be included if this financial information is considered non-public information

*Some types of procurements may require bidders to provide additional or specific financial information. Any such additional requirements will be clearly identified and explained within the RFP and may include supplemental forms in addition to this Bidder Response Form.

Disclose any judgments, pending or expected litigation, or other real potential financial reversals, which might materially affect the viability or stability of your company or indicate below that no such condition is known to exist. A confidentiality statement may be included if this information is considered non-public information

Provide a list of three references similar in size and industry (preferably another governmental entity). References shall be clients, other than the State of Vermont, who have implemented your Solution within the past 48 months.

Part 2: Vendor Proposal/Solution

Provide a description of the technology solution you are proposing.

Provide a description of the capabilities of the technology solution you are proposing.

If specific software is being proposed, provide a description of the:

Standard features and functions of the software:

The software licensing requirements for the solution:

Maximum number of concurrent users:

Give a brief description of the evolution of the system/software solution you are proposing. Include the date of the first installed site and major developments which have occurred (e.g. new versions, new modules, specific features).

List the total number of installations in the last 3 years by the year of installation.

Provide the total number of current users for the proposed system and indicate what version they are using.

Have you implemented the proposed solution for other government entities? If so, tell us who, when, and how that implementation went?

Provide a Road Map that outlines the company's short-term and long-term goals for the proposed solution/software and label it Attachment #2. (A confidentiality statement may be included if this information is considered non-public information)

Provide a PowerPoint (minimum of 1 slide and maximum of 10 slides) that provides an Executive level summary of your proposal to the State. Label it Attachment #3.

Describe any infrastructure, equipment, network or hardware required to implement and/or run the solution.

What is your recommended way to host this solution? Does the State need to install devices, for example?

Part 3: Functional Requirements

The table below lists the State's Functional Requirements. Indicate the "Availability" for each requirement for your proposed solution. Use the "Vendor Comments" column to provide any additional information or explanations.

Availability Key:

A - Feature is available in the core ("out-of-the-box") solution.

D - Feature is currently under development (indicate anticipated date of availability in the Vendor comments column).

C - Feature is not available in the core solution, but can provided with customization.

N - Feature is not available. Definition: BRANCH location = non- Data Center location.

Part 4: Non- Functional Requirements

The tables below list the State's Non-Functional Requirements. Indicate if your proposed solution complies in the "Comply" column.:

Yes = the solution complies with the stated requirement.

No = the solution does not comply with the stated requirement.

N/A = Not applicable to this offering.

Describe how the requirement is met in the "Vendor Description of Compliance" column.

4.1 Hosting

4.2 Application Solution

4.3 Security

As a solution vendor, you must have documented and implemented security practices for the following and have a process to audit/monitor for adherence. Indicate "Yes" or "No" in the "Comply" column or "N/A" if the requirement is not applicable to this offering. Use the "Vendor Description of Applicable Security Processes" column to describe how you meet the requirement and the "Audit/Monitor" column to indicate how you monitor for compliance. (A confidentiality statement may be included if this information is considered non-public information)

4.4 Other Non-Functional Requirements

For each requirement listed, indicate if and how you comply or type "N/A" if it is not applicable to your offering.

4.5 Data Compliance

Vendors and their solutions must adhere to applicable State and Federal standards, policies, and laws based on the type of data that will be stored, accessed, transmitted and/or controlled by the solution. If the "Type of Data" column is checked below, respond "Yes" or "No" in the "Comply" column and provide an explanation on how you comply in the "Vendor's Description of Compliance" column.

4.6 State of Vermont Cybersecurity Standard Update

Bidder shall certify by checking the box below the Solution shall not include, incorporate, rely on, utilize or be supported by any products or services subject to the limitations provided under State of Vermont Cybersecurity Standard Update, which Bidder acknowledges has been provided to it, and is available on-line at the following URL:

Bidder hereby certifies that in connection with the Request for Proposal, none of the applicable products or services will be included in or used to support State systems in a manner prohibited under the Standard. Note - If you are tracking the eight artifacts highlighted in green as noted in the introduction, this is one of the eight items. Checking the box is mandatory.

Part 5: IMPLEMENTATION/Project Management Approach

Describe the approach you would recommend for project managing this engagement.

Provide a list of the standard project management deliverables that you would normally produce for this type of engagement.

Provide a proposed list of project phases, major milestones, and an implementation timeline. Label this Attachment #4.

What types of difficulties have other clients experienced with implementation of the proposed solution?

Describe the experience and qualifications of the Project Manager you would offer as the resource for this engagement. Provide a copy of their resume and label it Attachment #5.

Part 6: TECHNICAL Services

Describe the technical services included in your proposal (e.g., business analysis, configuration, testing, implementation, etc.).

Provide a list of the standard deliverables for the technical services described above.

Provide a description of the roles/services/tasks the State will be expected to cover as part of this engagement. Describe any additional roles/services/tasks that are optional, but would be beneficial for the State to provide.

Describe your typical conversion plan to convert data from existing systems to your proposed solution (if applicable).

Describe and attach your typical Implementation Plan (label it Attachment #6), which shall include planning for the transition to maintenance and operations.

Describe the experience and qualifications of the technical resources proposed for this engagement. Provide their resume(s) and label them Attachment #7.

Describe the training that is included in your proposal.

Describe the system, administrator, and/or user documentation that is included in your proposal.

Part 7: Maintenance and Support Services

See Attachment F for State SLA

Provide answers to the questions below regarding your company's Maintenance and Support Services:

Describe how adherence to your service levels is measured and what remedies you would provide the State when performance doesn't meet the standard?

See Attachment F for State SLA.

Part 8: PRICING

See and Complete Attachment B: Pricing.

Part 9: Terms and Conditions

Exceptions to the States standard terms, conditions, and templates is strongly discouraged. Accordingly, exceptions may result in a determination that a bidder's proposal is not in the best interest of the State. However, if a bidder does wish to take exception to the State's terms, conditions, or templates they must indicate those objections in the table below. Add lines to the table below as needed. The State considers contractor documents the bidder wishes to append to the contract as exceptions.

Part 10: CERTIFICATE OF COMPLIANCE/Authorized Company Signature

NON COLLUSION: Bidder hereby certifies that the prices quoted have been arrived at without collusion and that no prior information concerning these prices has been received from or given to a competitive company. If there is sufficient evidence to warrant investigation of the bid/contract process by the Office of the Attorney General, bidder understands that this paragraph might be used as a basis for litigation.

CONTRACT TERMS: Bidder hereby acknowledges that is has read, understands and agrees to the terms of this RFP, including Attachment C: Standard State Contract Provisions, and any other contract attachments included with this RFP.

Worker Classification Compliance Requirement: In accordance with Section 32 of The Vermont Recovery and Reinvestment Act of 2009 (Act No. 54), the following provisions and requirements apply to Bidder when the amount of its bid exceeds $250,000.00.

Self-Reporting. Bidder hereby self-reports the following information relating to past violations, convictions, suspensions, and any other information related to past performance relative to coding and classification of workers, that occurred in the previous 12 months.

Subcontractor Reporting. Bidder hereby acknowledges and agrees that if it is a successful bidder, prior to execution of any contract resulting from this RFP, Bidder will provide to the State a list of all proposed subcontractors and subcontractors' subcontractors, together with the identity of those subcontractors' workers compensation insurance providers, and additional required or requested information, as applicable, in accordance with Section 32 of The Vermont Recovery and Reinvestment Act of 2009 (Act No. 54), and Bidder will provide any update of such list to the State as additional subcontractors are hired. Bidder further acknowledges and agrees that the failure to submit subcontractor reporting in accordance with Section 32 of The Vermont Recovery and Reinvestment Act of 2009 (Act No. 54) will constitute non-compliance and may result in cancellation of contract and/or restriction from bidding on future state contracts.

EXECUTIVE ORDER 05-16: Climate Change Considerations in State Procurements Certification

Bidder certifies to the following (Bidder may attach any desired explanation or substantiation. Please also note that Bidder may be asked to provide documentation for any applicable claims):

Bidder owns, leases or utilizes, for business purposes, space that has received:

Energy Star(R) Certification

LEED(R), Green Globes(R), or Living Buildings ChallengeSM Certification

Other internationally recognized building certification:

____________________________________________________________________________

2. Bidder has received incentives or rebates from an Energy Efficiency Utility or Energy Efficiency Program in the last five years for energy efficient improvements made at bidder's place of business. Please explain:

_____________________________________________________________________________

3. Please Check all that apply:

Bidder can claim on-site renewable power or anaerobic-digester power ("cow-power"). Or bidder consumes renewable electricity through voluntary purchase or offset, provided no such claimed power can be double-claimed by another party.

Bidder uses renewable biomass or bio-fuel for the purposes of thermal (heat) energy at its place of business.

Bidder's heating system has modern, high-efficiency units (boilers, furnaces, stoves, etc.), having reduced emissions of particulate matter and other air pollutants.

Bidder tracks its energy consumption and harmful greenhouse gas emissions. What tool is used to do this? _____________________

Bidder promotes the use of plug-in electric vehicles by providing electric vehicle charging, electric fleet vehicles, preferred parking, designated parking, purchase or lease incentives, etc..

Bidder offers employees an option for a fossil fuel divestment retirement account.

Bidder offers products or services that reduce waste, conserve water, or promote energy efficiency and conservation. Please explain:

____________________________________________________________________________

____________________________________________________________________________

Please list any additional practices that promote clean energy and take action to address climate change:

_____________________________________________________________________________

____________________________________________________________________________

_____________________________________________________________________________

EXECUTIVE ORDER 02 - 22: Solidarity with the Ukrainian People

By checking this box, Bidder certifies that none of the goods, products, or materials offered in response to this solicitation are Russian-sourced goods or produced by Russian entities. If Bidder is unable to check the box, it shall indicate in the table below which of the applicable offerings are Russian-sourced goods and/or which are produced by Russian entities. An additional column is provided for any note or comment that you may have.

CERTIFICATION REGARDING USE OF CONTRACT FUNDS FOR LOBBYING: The following provision is applicable to the Contractor for contracts over $100,000.00, and Contractor shall include this clause in all its subcontracts over $100,000.00.

1. The prospective contractor certifies, to the best of his or her knowledge and belief, under the penalties of perjury under the laws of the State of Vermont and the United States that on behalf of the person, firm, association, or corporation he or she represents, that:

a. No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to influence an officer or employee of any Federal agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement.

b. If any funds other than Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any Federal agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form-LLL, "Disclosure Form to Report Lobbying," in accordance with its instructions.

2. This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by 31 U.S.C. 1352. Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.

3. The prospective contractor also agrees that they shall require that the language of this certification be included in all lower tier subcontracts, which exceed $100,000 and that all such recipients shall certify and disclose accordingly.

For your bid to be considered valid, this Bidder Response Form must be signed by a duly authorized representative of the bidder, and submitted as part of the response to the proposal.

I am authorized to submit a proposal to the State of Vermont in response to this RFP on behalf of my organization. The information provided as part of my organization's response is a true and accurate representation of my organization's ability to meet the State of Vermont's business needs as expressed in this RFP.

ATTACHMENT B:

PRICING

PRICING SUBMISSION REQUIREMENTS:

Vendors must submit clear pricing for each site they can serve and a concise rollup that summarizes coverage by feed type and bandwidth. Delivery timelines are collected separately so schedule risk can be reviewed independently. All figures must be submitted in a spreadsheet instead of inline in the table, and reconcile to the site inventory in Attachment G: State of Vermont Inventory. Note: Please note Section 3 regarding the scoring percentage given to pricing. Pricing is a key component in the State's evaluation of this RFP's responses. Retainage: Vendors should assume a 10% retainage of payment will be held by the State until the successful completion and acceptance of all deliverables, subject to review and verification of performance against contract terms.

Submission instructions:

Complete Table 1: Pricing Rollup Summary to show coverage by bandwidth and by single or dual feed. Format response as a spreadsheet formatted to match Table 1.

Complete Table 2: Delivery Timeline Summary to show installation readiness by timeframe and construction status. Format response as a spreadsheet formatted to match Table 2.

Complete Table 3: Per Site Pricing requirements. Format response as a spreadsheet formatted to match Table 3.

Enter zero for nonrecurring cost when waived and note waived in the comments field.

Identify dual feeds only when the paths are physically diverse and not fed from the same pole line direction, route, or remote office.

Do not combine different transport types on a single line.

Ensure all totals and percentages reconcile to Attachment G: State of Vermont Inventory.

Table 1: Pricing Rollup Summary

Vendors must complete this table as a spreadsheet. Percentages are calculated against the total number of sites in Attachment G: State of Vermont Inventory. Note: The State strongly prefers proposals with zero or minimal NRCs and will evaluate cost competitiveness accordingly. NRC and other terms are defined in Attachment F.

Table 2: Delivery Timeline Summary

Vendors must complete this table as a spreadsheet. Delivery timing is measured in calendar days after receipt of order. Delivery is defined as the point at which the requested service is fully provisioned end to end and accepted by the State, including completion of any required access infrastructure. This includes, as applicable, construction or extension of fiber plant, use of existing provider facilities, or delivery over alternative last mile technologies. A service is considered delivered only when all underlying infrastructure required to support the circuit is complete, the service is installed at the demarcation point, the circuit is active and passing traffic at the contracted bandwidth, all required testing has been successfully completed, and the State has formally accepted the service. Delivery does not include provider ready for service status or partial completion of underlying infrastructure prior to State validation and acceptance.

Table 3: Per Site Pricing Requirements

Vendors must provide the following fields for each site proposed. Submit these fields as a spreadsheet component. Note: This RFP seeks vendors capable of delivering reliable broadband and DIA circuits to State sites across a wide geographic footprint, including support for path diversity at critical locations. Circuits must support SD-WAN integration and must be sourced from a broad mix of providers, including local, regional, wireless, and satellite, depending on site feasibility. It is anticipated that this RFP will have multiple awardees based on this logic.

Site ID.

Address.

Feed type single or dual.

Bandwidth Mbps or Gbps.

Transport type fiber, cable, fixed wireless, LTE, 5G, satellite.

Monthly recurring cost USD.

Nonrecurring cost USD.

Estimated install days after receipt of order.

Path diversity yes or no.

Path diversity description.

Contract term months.

Comments.

Definitions and clarifications:

Dual feed means two independently routed last mile paths with separate physical handoffs where feasible.

Deliverable means the circuit can be installed and made operational within the stated timeframe.

Excluded or unable to serve means the vendor has no viable delivery method for the site or doesn't wish to service.

Optional Time and Materials Services

The State may issue written task orders under the awarded contract for time and materials services within the scope of this procurement. These services are not part of the bid pricing or evaluation.

Typical work performed includes:

Structured wiring work and cable pulls.

Install or relocate data and voice jacks and associated endpoints and telephony equipment.

Extend or relocate the demarcation point.

Mount and secure equipment racks, shelves, and network appliances.

Hang and aim wireless access points and external antennas.

Install cable management, ladder racks, trays, and surface raceway, where required.

Label terminations and patch panels.

Patch cross connect and complete basic continuity testing.

Remove and dispose of decommissioned cabling and equipment.

Name of Bidder:

Signature of Bidder:

Date:

Item Detail
Company Name: [insert the name that you do business under]
Physical Address: [if more than one office - put the address of your head office]
Postal Address: [e.g. P.O Box address]
Business Website: [url address]
Type of Entity (Legal Status): [sole trader/partnership/limited liability company or specify other]
Primary Contact: [name of the person responsible for communicating with the Buyer]
Title: [job title or position]
Email Address: [email]
Phone Number: [landline]
Fax Number: [fax]
Reference 1 Detail Detail
Reference Company Name: [insert the name that you do business under] [insert the name that you do business under]
Company Address: [address] [address]
Type of Industry: [industry type: e.g., government, telecommunications, etc.] [industry type: e.g., government, telecommunications, etc.]
Contact Name: [if applicable] [if applicable]
Contact Phone Number: [phone] [phone]
Contact Email Address: [email] [email]
Description of System(s) Implemented: [description] [description]
Date of Implementation: [date] [date]
Reference 2 Reference 2 Detail
Reference Company Name: Reference Company Name: [insert the name that you do business under]
Company Address: Company Address: [address]
Type of Industry: Type of Industry: [industry type: e.g., government, telecommunications, etc.]
Contact Name: Contact Name: [if applicable]
Contact Phone Number: Contact Phone Number: [phone]
Contact Email Address: Contact Email Address: [email]
Description of System(s) Implemented: Description of System(s) Implemented: [description]
Date of Implementation: Date of Implementation: [date]
Reference 3 Detail
Reference Company Name: [insert the name that you do business under]
Company Address: [address]
Type of Industry: [industry type: e.g., government, telecommunications, etc.]
Contact Name: [if applicable]
Contact Phone Number: [phone]
Contact Email Address: [email]
Description of System(s) Implemented: [description]
Date of Implementation: [date]
ID # Functional Requirement Description Availability Vendor Comments
1. Connectivity and Transport Design 1. Connectivity and Transport Design 1. Connectivity and Transport Design 1. Connectivity and Transport Design
1.1 Replace legacy branch office ELAN and ELINE circuits with Dedicated Internet Access (DIA) or commodity broadband services at speed tiers of 250Mb (small), 500Mb (medium), 1 Gbps (large), 2Gb (extra-large) or better -- subject to site requirements.
1.2 Except for requested wave type circuits, all proposed circuits must operate at Layer 3 and support SD-WAN overlay integration without dependence on legacy Layer 2 transport (ELAN, ELINE, etc.).
1.3 Each connection must terminate at the network demarcation point with a standard Ethernet handoff.
1.4 Redundant dual circuit capability must be supported at specified sites where physically feasible.
1.5 Proposals must be based on Dedicated Internet Access, Commodity Broadband, or Wave services. Vendors shall not propose ELAN, ELINE, or MPLS unless explicitly requested by the State.
2 Provider Access and Sourcing 2 Provider Access and Sourcing 2 Provider Access and Sourcing 2 Provider Access and Sourcing
2.1 The vendor must be able to source DIA or commodity broadband circuits from any available provider, including local, regional, national, wireless, and satellite.
2.2 The vendor must be capable of coordinating complex circuits when last-mile and upstream providers differ.
2.3 All sourcing must follow a vendor-agnostic model and must not limit the State's options to any specific carrier.
2.4 For sites where the bidder is the incumbent circuit provider, the bidder must procure the secondary circuit from a different provider. The bidder must also identify the secondary provider in their proposal. This arrangement is commonly referred to as a Type II service.
2.5 Vendor must disclose all last-mile providers and underlying physical media.
3 Path Diversity and Critical Site Resilience 3 Path Diversity and Critical Site Resilience 3 Path Diversity and Critical Site Resilience 3 Path Diversity and Critical Site Resilience
3.1 For designated critical sites, vendor must provide physically diverse circuit paths or non-terrestrial alternatives such as cellular or satellite
3.1.1 Redundant circuits must not share any pole line, conduit, remote terminal, or central office.
3.1.2 Circuits must not enter through the same building conduit or wall unless dual entrance is not physically or financially feasible.
3.1.3 An engineered workaround must be proposed when dual entry is not available.
3.1.4 At branch sites (non-datacenter locations) redundant backup circuits do not have to be the same bandwidth as primary when not practical.
3.2 Vendor must provide a documented route analysis confirming physical separation.
3.3 Critical sites will be identified by the State and must be prioritized for maximum uptime and resiliency.
3.4 Vendor must provide circuit KMZs, shapefiles, as-built, or equivalent documentation upon request.
4 Contract Terms and Flexibility 4 Contract Terms and Flexibility 4 Contract Terms and Flexibility 4 Contract Terms and Flexibility
4.1 All circuits must be offered with month-to-month or annual contract options.
4.2 The State must be able to cancel any circuit at any time without penalty or early termination fee.
4.3 Bandwidth may be scaled up or down without requiring a new contract or restarting the term. The State reserves the right to increase or decrease bandwidth within the existing contract framework, subject to mutually- agreed pricing adjustments, without necessitating execution of a new contract.
5 Billing and Invoicing
5.1 Vendor must provide a single consolidated monthly invoice for all active circuits to include any requested SOV billing codes or designators at the circuit level, deemed necessary by the State.
5.2 Invoices must include detailed line items for each site, provider, transport type, and cost.
5.3 Invoices must comply with ADS business office payment terms, with a minimum net 60 window.
5.4 The billing system must support export in structured formats such as CSV or API.
6.0 Support and Service Levels
6.1 Vendor must provide 24x7x365 technical support via a U.S.-based Network Operations Center (NOC).
6.2 Support must include clear escalation paths with defined response and resolution timelines.
6.3 The following minimum SLAs must be guaranteed: 99.9% uptime, latency < 40ms, jitter < 15ms, packet loss < 0.5% Intra-LATA.
6.4 Vendor must provide proactive outage alerts and ticket updates to State contacts.
7.0 Governance and Operational Oversight
7.1 Vendor must conduct annual reviews to identify new providers, underutilized circuits, and cost-saving opportunities.
7.2 Vendor must participate in quarterly operational review meetings with ADS.
7.3 Reporting must include circuit uptime, performance data, trouble ticket history, and recommendations.
8.0 Cost Savings and Transparency
8.1 The State intends to reduce overall circuit expenses by transitioning from legacy E-LAN and E-LINE circuits to dedicated internet or commodity services. Vendors must describe how their proposed solution supports this objective.
8.2 All pricing must be fully transparent and include NRCs, MRCs, taxes, fees, and surcharges.
8.4 The State strongly prefers proposals with zero or minimal NRCs and will evaluate cost competitiveness accordingly.
9.0 Security and Compliance
9.1 All services must comply with State and federal security policies, including CJIS, HIPAA, and IRS 1075.
9.2 No vendor may intercept, proxy, decrypt, or inspect SD-WAN encrypted traffic.
9.3 Lawful intercept is permitted only when legally authorized, documented, auditable, and limited to the minimum required scope.
9.4 Man-in-the-middle (MITM) practices, TLS/SSL interception, or deep packet inspection of encrypted traffic are strictly prohibited.
9.5 Vendor must submit quarterly security compliance attestations and report any violations to ADS immediately.
ID # Non-Functional Requirement Description Comply Vendor's Description of Compliance
H1 Any technical solution must be hosted in a US data center.
H2 Any hosting provider must provide for back-up and disaster recovery models and plans as needed for the solution.
H3 Any hosting provider will abide by ITIL best practices for change requests, incident management, problem management and service desk.
A1 Any solutions vendor must provide for the backup/recover, data retention and disaster recovery of a contracted/hosted application solution.
A2 Any solutions vendor must provide for application management and design standard of all technology platforms and environments for the application solution (Development, Staging, Productions, DR, etc.)
ID # Non-Functional Requirement Description Comply Vendor's Description of Compliance
A3 Any solutions vendor must engage the State of Vermont using Service Level Agreements for system and application performance, incident reporting and maintenance.
A4 The State owns any data they enter, migrate, or transmit into the solution and the vendor shall allow the State to pull or copy this data at any time free of charge.
A5 As a contract deliverable, the vendor shall supply an up-to-date data dictionary that represents all data respective of the solution it will provide. The data dictionary must contain the following attributes: The technology (RDBMS platform) that hosts the data source, i.e. Oracle, SQL Server, MySQL, DB2, etc. The location where the data source is hosted Thorough descriptions of each table in the data source Thorough descriptions of each column within each table in the data source. In addition to business definitions, column descriptions must include the following detail: schema names; file group names (if applicable); data types; lengths; primary and foreign key constrains; applied formatting; applied calculations; applied aggregations; NULL-ability; default values.
ID # Non-Functional Requirement Description Comply Vendor's Description of Applicable Security Processes Audit/Monitor Process
S1 Input validation
S2 Output encoding
S3 Authentication and password management
S4 Session management
S5 Access control
S6 Cryptographic practices
S7 Error handling and logging
S8 Data protection from unauthorized use, modification, disclosure or destruction (accidental or intentional).
S9 Communication security
S10 System configuration
S11 Database security
S12 File management
S13 Memory management
S14 Fraud detection
S15 General coding practices
S16 POA&M management
S17 Risk Assessment Practices including but not limited to vulnerability assessment and pen testing
S18 Incident response planning and testing
S19 System Security Plan delivery
Non-Functional Requirements for Circuits RFP 2025 Non-Functional Requirements for Circuits RFP 2025 Non-Functional Requirements for Circuits RFP 2025 Vendor Compliance
NFR ID Functional Requirement Section Non-Functional Requirement as mapped to Functional Requirement Yes/No/NA
NFR06 1.0 Connectivity and Transport Design All circuits must operate at Layer 3 and support SD-WAN overlay integration.
NFR07 1.0 Connectivity and Transport Design If applicable, sites must support dual-WAN configurations for redundancy and failover.
NFR22 1.0 Connectivity and Transport Design The solution must support multiple transport types and flexible contract structures.
NFR19 2.0 Provider Access and Sourcing Vendors must source circuits from a vendor-agnostic model without carrier preference.
NFR08 3.0 Path Diversity and Critical Site Resilience Critical sites must be provisioned with physically diverse circuit paths.
NFR20 3.0 Path Diversity and Critical Site Resilience Vendors must ensure that all route data can be exported in widely used mapping formats (such as Google Earth or GIS files) whenever the State requests it. This guarantees that Vermont can access, review, and reuse its own route information across different systems without being tied to a single vendor's tools.
NFR09 4.0 Contract Terms and Flexibility Vendors must offer flexible contract options including month-to-month terms.
NFR10 4.0 Contract Terms and Flexibility The solution must allow cancellation without penalties or early termination fees.
NFR11 4.0 Contract Terms and Flexibility Bandwidth must be scalable without requiring contract renegotiation or term restart.
NFR15 5.0 Billing and Invoicing Billing systems must support data export in structured formats such as CSV or API.
NFR21 5.0 Billing and Invoicing Invoices must include itemized details by site, transport type, provider, and cost.
NFR24 5.0 Billing and Invoicing The vendor must support API-based integration for reporting and billing data exchange.
NFR01 6.0 Support and Service Levels The solution must guarantee network uptime of at least 99.9%.
NFR02 6.0 Support and Service Levels The solution must ensure latency does not exceed 40 milliseconds.
NFR03 6.0 Support and Service Levels The solution must maintain jitter below 15 milliseconds to support real-time services.
NFR04 6.0 Support and Service Levels The solution must ensure packet loss does not exceed 0.5% within Intra-LATA regions.
NFR12 6.0 Support and Service Levels Vendors must provide 24x7x365 support through a U.S.-based Network Operations Center.
NFR13 6.0 Support and Service Levels The support model must include defined escalation paths with SLA-based resolution times.
NFR14 6.0 Support and Service Levels Vendors must provide proactive outage alerts and ticket updates to designated contacts.
NFR17 7.0 Governance and Operational Oversight Vendors must participate in quarterly performance and operational review meetings.
NFR16 8.0 Cost Savings and Transparency All vendor pricing must be fully transparent, showing one-time setup costs, ongoing monthly fees, taxes, and any surcharges. This ensures the State has a complete view of the total cost, avoids hidden charges, and allows fair comparison across vendors.
NFR05 9.0 Security and Compliance The solution must comply with all applicable CJIS, HIPAA, and IRS 1075 requirements.
NFR18 9.0 Security and Compliance Vendors must not intercept, decrypt, or proxy encrypted SD-WAN traffic.
NFR25 9.0 Security and Compliance Vendors must submit quarterly compliance attestations to verify policy adherence.
NFR26 Other: Throttling The solution provider must guarantee that no traffic throttling or artificial limitations are imposed on circuit performance. Bandwidth must remain consistent with the contracted service levels under all normal operating conditions.
NFR27 Other: Monitoring for contracted bandwidth The solution provider must supply regular performance reports and make real-time monitoring available to the State, demonstrating that contracted bandwidth is consistently delivered without throttling. Metrics must include throughput, latency, packet loss, and uptime, with thresholds aligned to the agreed Service Level Agreement (SLA).
NFR28 Other: Type II Service The solution must support carrier diversity by ensuring secondary circuits are provisioned from an alternate provider when the incumbent is supplying the primary circuit. This protects against single-provider failure and aligns with State resiliency standards.
Type of Data Applicable State & Federal Standards, Policies, and Laws Comply Vendor's Description of Compliance
Publicly available information NIST 800-171
Confidential Personally Identifiable Information (PII) State law on Notification of Security Breaches State Law on Social Security Number Protection State law on the Protection of Personal Information National Institute of Standards & Technology: NIST SP 800-53 Revision 4 "Moderate" risk controls Privacy Act of 1974, 5 U.S.C. 552a.
Payment Card Information Payment Card Industry Data Security Standard (PCI DSS) v 3.2
Federal Tax Information Internal Revenue Service Tax Information Security Guidelines for Federal, State and Local Agencies: IRS Pub 1075
Personal Health Information (PHI) Health Insurance Portability and Accountability Act of 1996: HIPAA The Health Information Technology for Economic and Clinical Health Act HITECH Code of Federal Regulations 45 CFR 95.621
Type of Data Applicable State & Federal Standards, Policies, and Laws Comply Vendor's Description of Compliance
Affordable Care Act Personally Identifiable Information (PII) Internal Revenue Service Tax Information Security Guidelines for Federal, State and Local Agencies IRS Pub 1075 Minimum Acceptable Risk Standards for Exchanges MARS-E 2.0 (Scroll down the page)
Medicaid Information Medicaid Information Technology Architecture MITA3.0 Code of Federal Regulations 45 CFR 95.621
Prescription Information State law on the Confidentiality of Prescription Information
Student Education Data Family Educational Rights and Privacy Act: FERPA
Personal Information from Motor Vehicle Records Driver's Privacy Protection Act (Title XXX) ("DPPA") 18 U.S.C. Chapter 123, 2721 - 2725
Criminal Records Criminal Justice Information Security Policy: CJIS
Other sensitive data Data that does not fit into the above categories but is sensitive and requires additional protection.
Questions Vendor Response
Service: Customer Phone &/or Email Support Service: Customer Phone &/or Email Support
What is the method for contacting technical support?
What are the hours of operation for support?
What is the turnaround time for responses?
What is the escalation process for support issues?
Who comprises the support team and what are their qualifications?
Define your response resolution metrics and how you capture and report them.
Service: Incident/Security Breach Notification and Process Service: Incident/Security Breach Notification and Process
Describe your identification and notification process for security breaches.
Service: Data Management Service: Data Management
Describe how data is stored, retained and backed up (including frequency).
Service: Hosting Service: Hosting
Describe the hosting service and associated service levels.
Questions Vendor Response
Service: Scheduled Maintenance/Downtime Service: Scheduled Maintenance/Downtime
What is the frequency of scheduled maintenance and downtime?
What is the notification process for scheduled maintenance and downtime?
Describe how "maintenance" updates are tested with customers prior to installing them in their live environments.
Service: System Upgrades Service: System Upgrades
Are software upgrades provided as part of the software support contract?
Describe your software upgrade process.
How often are new versions released?
Is documentation and training provided for system upgrades?
Are there additional costs for upgrades and/or new releases?
Describe how and when the State will have an opportunity to test system upgrades/releases prior to live installation.
Describe how the State will validate post installation and how changes will be backed out in the event that a problem is encountered.
Questions Vendor Response
Service: Bug Fixes and Minor Enhancements Service: Bug Fixes and Minor Enhancements
Describe the frequency and process for providing, testing, and installing bug fixes and minor enhancements.
Service: Disaster Recovery Service: Disaster Recovery
Describe the disaster recovery services included in this proposal for any non-state hosted services.
What is your standard RPO and RTO?
Describe the plan your company has in place for its own disaster recovery of any sites that may be involved in support of this proposal.
Clause Location Exception Proposed Verbiage
[indicate RFP, exhibit, attachment or addendum, section & page number] [briefly describe your concern about this clause] [describe your suggested alternative wording for the clause or your solution]
[indicate RFP, exhibit, attachment or addendum, section & page number] [briefly describe your concern about this clause] [describe your suggested alternative wording for the clause or your solution]
[indicate RFP, exhibit, attachment or addendum, section & page number] [briefly describe your concern about this clause] [describe your suggested alternative wording for the clause or your solution]
Summary of Detailed Information Date of Notification Outcome
Provided Equipment or Product Note or Comment
Signature:
Full name:
Title:
Company:
Date:
Category Number of sites priced Percent of total sites priced Average MRC USD Average NRC USD
Single feed 250Mbps or less
Single feed 500Mbps
Single feed 1 Gbps
Dual feed 1 Gbps per feed
Single feed 2 Gbps
Dual feed 2 Gbps per feed
Wave Services (Point to Point Optical Services (Layer 1))
Excluded or unable to serve
Delivery timeframe Number of sites Percent of total sites Notes
Deliverable within 30 days after receipt of order
Deliverable within 31 to 60 days after receipt of order
Deliverable within 61 to 90 days after receipt of order
Construction required or greater than 90 days
Excluded or unable to serve
This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.
Daily notification on new contract opportunities

With GovernmentContracts, you can:

  • Find more opportunities and win more business
  • Receive daily alerts for all new bid opportunities
  • Get contract opportunities matched to your business
ONE WEEK FREE TRIAL

See also

Reading ER P23-1 (404) Request Date: 7/29/2026 1:05:25 PM Open Date: Closing Date:

State Government of Vermont

Bid Due: 8/21/2026

Williston Road Stormwater Structures Request Date: 7/29/2026 8:42:48 AM Open Date: Closing Date:

State Government of Vermont

Bid Due: 8/27/2026

Follow Dental and Audiology Coordinator for the Vermont Army National Guard Active Contract

DEPT OF DEFENSE

Bid Due: 8/23/2026

Roadway Line Striping and Markings Request Date: 7/24/2026 2:23:32 PM Open Date: Closing

State Government of Vermont

Bid Due: 8/19/2026

* Disclaimer: Information regarding bids, requests for proposals (RFPs), or requests for qualifications (RFQs) is provided on this website only for convenience and does not constitute official public notice. Persons wishing to respond to or inquire about bids, RFPs, or RFQs should contact the appropriate government department.