| Location: | Vermont |
|---|---|
| Posted: | Oct 16, 2026 |
| Due: | Nov 6, 2026 |
| Agency: | State of Vermont |
| Type of Government: | State & Local |
| Category: |
|
| Publication URL: | To access bid details, please log in. |
| TITLE | QUESTIONS DUE | ANSWERS POSTED | DUE DATE | NO POSTING AFTER |
|
State of Vermont Cloud Hosted Cannabis Laboratory Information System (LIMS)
Bidder Response Form |
10/26/2026 04:30PM |
|
11/06/2026 04:30PM |
|
Exhibit C
State of Vermont Bidder Response Form
Request for Proposal Name: State of Vermont Cloud Hosted Cannabis Laboratory Information System (LIMS)
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:
Kyle Emerson, State Purchasing Agent
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?
Describe how your solution can be integrated to other applications and if you offer a standard-based interface to enable integrations.
Respond to the following questions about the solution being proposed:
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.
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.
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.
Hosting
Application Solution
Security
1. 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)
Other Non-Functional Requirements [Describe any additional non-functional requirements or type N/A in this section.]
For each requirement listed, indicate if and how you comply or type "N/A" if it is not applicable to your offering.
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.
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.
PART 5: IMPLEMENTATION/PROJECT MANAGEMENT APPROACH
[Add, modify or delete information in this section to be specific to your RFP.]
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 time-line. Label this Attachment #4.
What types of difficulties have other clients experienced with implementation of the proposed solution?
5 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
[Add, modify or delete information in this section to be specific to your RFP.]
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
[Add, modify or delete information in this section to be specific to your RFP (including specifying any required service levels).]
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?
PART 8: PRICING [Update the pricing chart as needed for your specific RFP.]
Submit pricing for your proposed solution in the table below. Fill in only the lines that are applicable to your proposal. Insert lines for additional costs, but do not delete or rename any lines in the Table. Total each column and provide a total of all columns in the "Total Implementation, plus 5 Year Costs" box on the next page.
Describe any assumptions you have made in relation to the above cost and pricing information.
Provide pricing information for any volume discounts that are available based on the number of software licenses purchased or support years purchased.
Provide pricing for any Functional Requirements marked as "C" (feature is not available in the core solution, but can be provided with customization).
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 bidders 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:
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:
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.
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:
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.
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.
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.
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.
| 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 |
|---|---|
| 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] | [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] |
|---|
| Vendor Response/Explanation | Vendor Response/Explanation | |
|---|---|---|
| Question | Yes or No | |
| A. Does the solution use Service Oriented Architecture for integration? | ||
| B. Does the solution use a Rules Engine for business rules? | ||
| C. Does the solution use any Master Data Management? | ||
| D. Does the solution use any Enterprise Content Management software? | ||
| E. Does the solution use any Case Management software? | ||
| F. Does the solution use any Business Intelligence software? | ||
| G. Does the solution use any Database software? | ||
| H. Does the solution use any Business Process Management software? | ||
| I. Is this a browser based solution and if so what browsers do you support? | ||
| J. Does the solution include an API for integration? |
| ID # | Functional Requirement Description | Availability | Vendor Comments |
|---|---|---|---|
| 1 | Sample Management | ||
| A | As CCB Compliance Agents, we need to populate a standardized laboratory requisition form, so that we can provide the laboratory with basic information about the licensee and sample, and indicate which laboratory tests are needed. | ||
| B | As a CCB QC Lab Analyst, I need to enter sample data into the LIMS, so that essential information about the sample remains associated to the sample throughout lab analysis and can be included on the Certificate of Analysis (COA) and/or other data extracts. | ||
| C | As a CCB QC Lab Analyst, I need the solution to store photos taken of samples in the LIMS and then attach them to the COAs as needed. | ||
| 2 | Lab Analysis | ||
| A | As CCB QC Lab Analyst I need the LIMS to produce a barcode and unique identifier for the sample, so that the sample is properly tracked through the analysis lifecycle. | ||
| B | As CCB QC Lab Analyst, I need the LIMS to generate a printable label with the sample barcode, identifier, and other test information, so tha the sample is efficiently identifiable and scannable at laboratory instruments; proper labeling ensures the integrity of each sample and reduces the risk of sample mix-ups and delays. |
| C | As CCB QC Lab Analyst, I need to assign or remove tests (assays) assigned to a sample, including adding or removing specific analytes or targets from an assay, so that I can manage the tests that will be performed on the sample | ||
|---|---|---|---|
| D | As CCB QC Lab Analyst, I need to assign samples to a run, so that I can perform the assigned assays by executing the run. |
| E | As a CCB QC Lab Analyst, I need to enter test results for a run into the LIMS, where field checks will ensure the entered result is valid (per configured rules) and indicate if a result is out-of-specification (OOS), so that the results are linked to the sample. | ||
|---|---|---|---|
| F | As a CCB QC Lab Analyst, I need to import instrument run results directly to the LIMS, where field checks will ensure the entered result is valid (per configured rules) and indicate if a result is out-of-specification (OOS), so that entering test results into the LIMS is more efficient and less prone to human-error. | ||
| G | As CCB QC Lab Analyst, I need the LIMS to have workflow where another CCB QC Lab Analyst or the CCB QC Lab Director will review entered test results before releasing results, so that the CCB QC Lab follows laboratory best practices. | ||
| 3 Reporting | 3 Reporting | 3 Reporting | 3 Reporting |
| A | As CCB QC Lab Analyst, I need to generate a COA for a sample; the report must contain sample information and selected test results, so that i can send test results to CCB Compliance. | ||
| B | As a CCB QC Lab Analyst, I need to review and release the COA to the intended recipient, so that I have the opportunity to review the final COA to ensure completeness and quality before it is released to CCB Compliance. | ||
| C | As a CCB Compliance Agent, I need to access an electronic copy of the COA through an online portal, network folder, or e-mail attachment, so that I can access the requested test results. |
| D | As a CCB Compliance Agent, I need to receive a notification when the analysis of a submitted samples yields an out-of-specification (OOS) test result, so that I can prioritize compliance follow-up on problematic test results. | ||
|---|---|---|---|
| E | As a CCB Compliance Agent, I need to view test results by assay or licensee, so that I can assess trends and patterns in result data | ||
| 4 Manage LIMS | 4 Manage LIMS | 4 Manage LIMS | 4 Manage LIMS |
| A | As the CCB QC Lab, we need the LIMS to be expandable through the addition of new assays and/or analytes/targets as tests become available, encouraged or required by testing regulations, so that the CCB CQ Lab can stay up-to-date in the rapidly changing cannabis regulatory environment. | ||
| B | As the CCB QC Lab, we need to update specifications (such as reference ranges, Action Limits, etc.) for existing assays and analytes, so that the CCB CQ Lab can stay up-to-date as rules change in the rapidly changing cannabis regulatory environment. | ||
| C | As the CCB QC Lab, we need the LIMS to have the potential to 'onboard' new laboratory instruments that may be procured by the lab, so that the CCB CQ Lab can stay up-to-date in the rapidly changing cannabis regulatory environment | ||
| D | As the CCB QC Lab, we need the COA layout to be configurable, so that the CCB CQ Lab team can design a COA with CCB QC Lab branding, and decide what information is included on the COA so that the report is complete, consistent, and deemed 'easy-to-understand' by CCB Compliance. |
| E | As the CCB QC Lab, we need the label layout to be configurable, so that the CCB CQ Lab team can design a label that fits their sample containers and contains the information they deem necessary for sample tracking | ||
|---|---|---|---|
| F | As the CCB QC Lab Director (or specified user role), I need to add or remove users from the LIMS, So that the LIMS is accessible to those who need access to perform their essential duties, but is restricted appropriately to secure sensitive, non- public data. | ||
| G | As the CCB QC Lab Director, I need to add or remove User Roles within the LIMS, so that the LIMS is accessible to those who need access to perform their essential duties, but is restricted appropriately to secure sensitive, non-public data. | ||
| ID # | Non-Functional Requirement Description | Comply | Vendor's Description of Compliance |
|---|---|---|---|
| 149 | The solution provider will provide an Availability Plan for the SaaS and PaaS solution. The Availability Plan must include the following: Availability Objectives base on the SLA Availability Architecture - high availability, DR, and data protection Availability Management - Roles and Responsibilities, RACI, specific processes and procedures for reporting, analyzing and resolving incidents, and communication with stakeholders. (SaaS, PaaS) | ||
| 168 | Solution provider will monitor critical performance parameters: these can |
| included: CPU usage: the percentage of CPU resources consumed by the software. High CPU usage can affect the responsiveness and speed of the solution. Memory usage: the amount of memory allocated by the software. High memory usage can indicate high resource consumption and affect the performance of the solution Requests per minute and bytes per request: the number of requests received by the software's API per minute and the amount of data handled by each request. Latency and uptime: the delay between a user's action on the software and the response of the software to that action, and the availability of the software to serve requests. Security exposure: the degree to which the software is vulnerable to unauthorized access, modification, or damage. Execution time: the time taken by the software to complete a certain function or task. Throughput: the rate at which the software can process data or transactions. |
|---|
| 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.) | ||
| 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. | ||
| 64 | Solutions will allow the user to export formatted reports from the system in industry standard formats, e.g., Word, Excel, PDF, and TXT. |
| 401 | Service provider will collect performance and capacity metrics (including monitoring alerts or incidents) and will conduct analysis of metrics to identify and remedy any possible capacity issues. | ||
|---|---|---|---|
| 405 | The following capacity management KPIs/metrics will be tracked and reported by the hosting service provider: Total incidents, with cause of capacity, number of emergency changes related to capacity incidents, comparison of capacity forecasts against actual consumption. Service provider will add KPIs to the above list, as requested by the State of Vermont (SOV) in support of the business and continuous improvement. | ||
| 406 | System will support concurrent internal and external users as per contract. This will be tested using load testing prior to go-live and periodically after major release as part of the capacity plan. | ||
| 410 | If required, the Solution Provider will produce a Capacity Management Plan. The document should include the following A description of the scope and objectives of the plan, such as the systems, services, processes, and stakeholders involved. A summary of the current state of the systems and services, such as their performance, availability, reliability, scalability, and security. A forecast of the future demand and growth of the systems and services, based on historical data, trends, projections, and business plans. A gap analysis that identifies the potential risks and issues that may arise from the mismatch between the current and future capacity needs. A strategy and action plan that defines the actions and resources needed to close the gaps and ensure adequate capacity for the systems and services. A set of metrics and indicators that will be used to monitor and report on the progress and effectiveness of the plan. |
| - A review and update process that ensures the plan is regularly evaluated and revised to reflect changing needs and circumstances. | |||
|---|---|---|---|
| 412 | Service Provider will deploy capacity and performance monitoring tools that allow servers, networks, databases, storage, applications, data center infrastructure to scale and shift workloads on-demand without any user perceived interruption. | ||
| 438 | If necessary and required for the solution, solutions must be able to provide services to all parts of the organization and any external stakeholders, such as customers or partners, using any relevant channels, such as web-based interfaces, mobile applications, or APIs. | ||
| 450 | Solutions will provide new and or update existing two-way, real-time interfaces to transfer data between the system and 3rd party Service Providers, e.g., Insurance Division, insurance carriers, and federal databases. | ||
| 457 | The solution database will provide standard data extraction API to allow import and export of data. | ||
| 481 | The software shall maintain compatibility with previous versions of APIs (Application Programming Interfaces) to ensure that any third-party integrations or plugins continue to function correctly. | ||
| 486 | The software shall provide stable APIs (Application Programming Interfaces) that are compatible with future versions of the software, ensuring that any third-party integrations or plugins continue to function correctly. | ||
| 495 | Data transformations will be to and from normalized formats. Normalized data formats facilitate composition and reduce the number of transformations that will be created and maintained. A canonical data representation that spans the enterprise will be used, but is not required. |
| A federated approach to data normalization is required. | |||
|---|---|---|---|
| 509 | The software shall maintain compatibility with previous versions of Application Programming Interfaces (APIs) to ensure third-party integrations or plugins continue to function correctly. |
| ID # | Non-Functional Requirement Description | Comply | Vendor's Description of Compliance |
|---|
| ID # | Non-Functional Requirement Description | Comply | Vendor's Description of Applicable Security Processes | Audit/Monitor Process |
|---|---|---|---|---|
| 428 | Data center facilities must be located within the United States to comply with jurisdictional regulations. | |||
| 515 | Solutions handling Federal Tax Information (FTI) or other sensitive data must comply with FedRamp standards to ensure data security and regulatory compliance. | |||
| 516 | Access to the environment via the State of Vermont internal network must be controlled by a firewall that validates communications based on recognized protocols and approved source/destination IP address ranges. |
| 517 | Applications accessible from the public internet must be deployed on dedicated Demilitarized Zone (DMZ) servers managed by the Contractor to ensure security and isolation from internal networks. | |||
|---|---|---|---|---|
| 518 | Contractor personnel must be authorized by the provider for network and system access across all |
| environments to maintain security and control. | ||||
|---|---|---|---|---|
| 523 | The Contractor must maintain an isolated support network separate from its intranet, including firewall, VPN, intrusion detection, authentication, reporting, and DNS services, as the standard method for personnel to connect to the environment. | |||
| 526 | The Contractor must manage access control to its data centers and the environment, limiting access to State of Vermont's network connections to authorized personnel only. | |||
| 529 | Intrusion Detection Systems (IDS) must provide continuous surveillance to intercept and respond to security events, with alerts forwarded to the hosting service provider's IT security and service desk for review and response. | |||
| 530 | Secure Socket Layer (SSL) must be deployed for all web-based applications hosted by the Contractor, especially those accessible via the internet or secure networks like hardware VPNs, ensuring secure data transmission. | |||
| 531 | The Contractor must deploy non-Secure Socket Layer (SSL) applications privately, accessible |
| only through secure network connections and not exposed to the public internet, with State of Vermont connections to non-internet applications using SSL and secure network connections. | ||||
|---|---|---|---|---|
| 532 | Secure Socket Layer (SSL) -enabled web applications accessed by the State of Vermont (SOV) via the public internet must be deployed internally by the Contractor over SOV's network, with the hosting provider procuring and maintaining SSL certificates on behalf of the SOV. | |||
| 533 | The Contractor must utilize VPN devices in a site-to-site (network-to-network) configuration, leveraging either the public internet or dedicated links for secure data transmission. | |||
| 534 | Internet Protocol Security (IPsec) must be implemented within the VPN strategy to secure data using tunneling and encryption (168-bit Triple DES or AES256) for data privacy. | |||
| 535 | Standard network connectivity between the Contractor and the State of Vermont must be established through a hardware VPN provided by the hosting service provider. | |||
| 538 | Access to logs must be restricted to authorized personnel based on need- |
| to-know and least privilege principles, with log files protected using SHA1 cryptographic hash sums and monitored, and logs accessible via intranet systems relocated daily to non-intranet systems. | ||||
|---|---|---|---|---|
| 539 | Access control policies and procedures must govern resource access within the State of Vermont environment, including physical servers, files, directories, services, database tables, and network protocols. | |||
| 540 | Least Privilege and Separation of Duties (SOD) principles must be applied to all solutions, ensuring user permissions and system functionality align with specific roles based on access needs. | |||
| 541 | New deployments within Contractor data centers must undergo security technical reviews by a cross-organization team, including dedicated security experts, and technologies or tools not meeting security policies or standards must not be deployed. | |||
| 542 | Security and compliance standards for deployment environments must remain consistent whether in production or non-production settings. |
| 543 | All permanent or contract employees handling data must complete data privacy awareness and corporate ethics training, including understanding data privacy, recognizing risks related to personal data, understanding their data responsibilities, and reporting privacy violations. | |||
|---|---|---|---|---|
| 546 | Server instances within deployment environments must be isolated via firewalls based on their application role. | |||
| 547 | Remote access for Contractor employees and subcontractors must require IPsec or SSL-encrypted VPN connections from non-hosting service provider locations to access the network. | |||
| 549 | Access provisioning must be centralized and based on job roles, requiring management approval to ensure appropriate access levels are maintained. | |||
| 550 | Access to operating systems must require secure login procedures with unique user IDs and strong passwords to protect system integrity. | |||
| 551 | Root passwords for hosts and facilities must be changed every 30 |
| days to enhance security and prevent unauthorized access. | ||||
|---|---|---|---|---|
| 553 | Employees must maintain confidentiality of state data by signing confidentiality agreements and complying with company policies on the protection of confidential information. | |||
| 554 | Network controls must protect and control State of Vermont data during transmission, ensuring all connected devices comply with security standards and policies. | |||
| 555 | Designated personnel must handle removable digital media according to defined procedures, with media securely transported, logged, and vaulted by a third-party service provider under contractual obligations to comply with hosting provider-defined media protection terms. | |||
| 556 | Intrusion Detection Systems (IDS) must provide continuous surveillance to intercept and respond to security events, ensuring timely detection and mitigation of threats. | |||
| 557 | State of Vermont data must not be stored on removable drives or mediums unless encrypted to safeguard sensitive information. |
| 558 | Strict restrictions must be maintained over the distribution of media containing state health information, complying with information protection, media sanitization, privacy, and records retention policies. | |||
|---|---|---|---|---|
| 561 | Database passwords must be changed every 180 days to ensure ongoing security and prevent unauthorized access. | |||
| 561 | Data integrity during transmission must be protected using strong encryption protocols such as TLS/SSL or IPsec, along with hashed Message Authentication Codes (HMAC-SHA-1) on VPN networks. | |||
| 562 | The Contractor must implement a Security Information and Event Management (SIEM) system to correlate and alert on security events from Intrusion Detection Systems (IDS), firewall logs, and network flow events, with monitoring conducted 24/7 throughout the year. | |||
| 564 | Third-party anti-virus and anti-spam products must scan all State of Vermont and employee emails and attachments traversing Contractor data centers, with the email infrastructure enforcing TLS |
| encryption for both inbound and outbound emails. | ||||
|---|---|---|---|---|
| 565 | Server operating systems must be hardened by eliminating unnecessary services, accounts, and network access rights to enhance security and reduce vulnerabilities. | |||
| 566 | The Contractor must evaluate and respond promptly to incidents of unauthorized access or handling of State of Vermont (SOV) data, collaborating with relevant teams and law enforcement to restore the confidentiality, integrity, and availability of SOV's environment. | |||
| 571 | Solution administrators must have the capability to create, manage, and assign user accounts with role-based access, including configurations for user groups, locations, and organizational hierarchy. | |||
| 573 | The solution must provide transaction tracking and log consolidation capabilities across the application's data tier to facilitate comprehensive monitoring and analysis. | |||
| 574 | The solution must maintain records of all data additions, changes, and deletions, which must be searchable by user/client ID, date/time, location, and other relevant details to ensure traceability and accountability. |
| 575 | Audit records must be protected from unauthorized modifications and require formal approval for any changes to maintain integrity and compliance. | |||
|---|---|---|---|---|
| 579 | The solution must utilize Single Sign-On (SSO) components for authentication and authorization to streamline user access and enhance security. | |||
| 581 | The solution must support the protection of Personally Identifiable Information (PII) through encryption or de-identification techniques to safeguard sensitive data. | |||
| 582 | The Contractor must certify code against OWASP Application Development Security Standards and mitigate risks outlined in CWE/SANS Top 25 Most Dangerous Software Errors. | |||
| 617 | Authentication of external users will be handled with a SAML or OIDC connection with the State's Okta tenants in DEV, TEST and PROD environments. Internal users shall be authenticated with a SAML or OIDC connection to Entra. The State's preference is to have separate URLs for internal and external authentication. If the application can only facilitate a single auth provider |
| but requires access for both internal and external users, Okta shall be established as the auth provider and will route internal users to Entra. If app functionality depends on internal or external status, the application must have a means to discern such states from OIDC claims, SAML attributes or other reliable method approved by the State. | ||||
|---|---|---|---|---|
| 623 | The application must have an efficient means of provisioning new users while adhering to principles of least privileged access. Unless another method is approved by the State, this should be accomplished by allowing any user log in to the application but preventing use of any functionality as directed by the State until after an internal administrator has approved the user for elevated access. An administrator should be able to approve a user for access before or after their initial login. |
| 16224 | The Contractor must ensure the System Security Plan facilitates the development and submission of a Statement on Standards for Attestation Engagements (SSAE) 18, Service Organization Control (SOC) 2 Type II Compliance Report from hosting providers. The Contractor must ensure the System Security Plan supports the development and maintenance of |
|---|
| organizational information security policies to ensure comprehensive protection of data. The Contractor must ensure the System Security Plan includes a Privacy Impact Analysis that identifies data elements of the system exposing Vermont beneficiaries to potential privacy threats and outlines system controls to mitigate risks of private data disclosure. The Contractor must ensure the System Security Plan establishes a security event notification process, event evaluation and escalation procedures, and security event response procedures to ensure timely and effective handling of security incidents. The Contractor must ensure the System Security Plan provides a complete network diagram detailing servers, printers, workstations, firewalls, intrusion prevention systems, network security device internet connections, and any other network-connected devices. The Contractor must ensure the System Security Plan includes firewall security standards and diagrams, showing sufficient detail of |
|---|
| data flows in and out of security boundaries, including VPNs, subnets, ports, and protocols. The Contractor must ensure the System Security Plan includes a detailed strategy for system log collection and monitoring to ensure ongoing oversight and security. The Contractor must ensure the System Security Plan includes an antivirus deployment and maintenance plan to protect against malware and other security threats. The Contractor must ensure the System Security Plan incorporates a software maintenance strategy, including updates for operating systems and third-party software, to ensure systems remain secure and functional. The Contractor must attest that criminal background checks are completed and passed by all employees before they are granted access to State data. The Contractor must ensure the System Security Plan includes procedures to limit access to information to individuals who need it for their job functions, ensuring access is restricted to the minimum necessary information. |
|---|
| The Contractor must ensure the System Security Plan describes how the physical safety of data under its control is protected using appropriate devices and methods, such as alarm systems, locked files, guards, or other devices to prevent loss or unauthorized access. The Contractor must ensure the System Security Plan includes procedures to prevent unauthorized use of passwords, access logs, badges, or other methods designed to prevent loss or unauthorized access to electronically or mechanically held data. The Contractor must agree to comply with Health Insurance Portability and Accountability Act (HIPAA) Privacy Rules as a Business Associate of the State, ensuring adherence to federal regulations. | ||||
|---|---|---|---|---|
| 16225 | The Contractor must ensure that the System Security Plan complies with State and Federal laws, rules, regulations, standards, and guidelines to include NIST Publication 800-53 current revision | |||
| 16226 | The Contractor must ensure the system(s) maintains compliance with current and future security, privacy, accessibility, and certification laws |
| (State and Federal), regulations, policies, and guidelines relevant to system security, confidentiality, integrity, availability, and safeguarding of information. Where any of these overlap, the Contractor must ensure that the system(s) must always strive to attain the more stringent policy. The Contractor retains responsibility for all modifications to the system(s) to maintain compliance according to the terms and conditions of the resulting Contract. | ||||
|---|---|---|---|---|
| 16238 | The Contractor must maintain a Security Breach Response Team available 24 hours a day, 7 days a week, and within 5 minutes of notification of an incident to respond to security violations and breaches (physical and electronic). This includes communications to a defined list of personnel at the State tied to the State's Continuity of Operations/Disaster Recovery. State staff must be informed of response plan, including specific steps and time frames for resolution. | |||
| 16241 | The Contractor must provide a State- approved, 508-compliant user-centered designed and intuitive |
| interface for Security Administrators to grant, track, manage, and revoke access for individuals. System must also provide auditing capabilities for approved audit resources. | ||||
|---|---|---|---|---|
| 16245 | The Contractor must ensure all systems undergo Industry Standard security testing (e.g., penetration, physical security, web application, social engineering, and vulnerability tests) minimally on an annual basis, as mutually agreed upon between the Contractor and the State, when there has been a significant infrastructure change or resulting from Federal requirements. This security testing must be conducted at no cost to the State and by a Stateapproved third party that maintains no financial or controlling relationship with the Contractor. Additionally, the Contractor must provide documented testing results and generate corrective action plans for any deficiencies identified as well as be responsible for modifications to remain compliant based on the terms and conditions of the Contract. | |||
| 16247 | The Contractor must design and execute security testing to prevent unauthorized access to the system (intrusion detection and vulnerability |
| testing) on a quarterly basis and provide a report of all findings to the State within 10 business days. Any issues identified and reported to the State are to be resolved according to their respective SLA. | ||||
|---|---|---|---|---|
| 32586 | The Contractor must ensure State of Vermont (SOV) data is not stored, transmitted to, or accessed from outside the United States except as authorized in writing by SOV. | |||
| 16222 | The Contractor must ensure that the solution achieves compliance with applicable State and Federal regulations and standards as outlined in the National Institute of Standards and Technology (NIST) Publication 800-53, current revision, upon Operational Go-Live. Compliance must be verified through an independent third-party production security controls assessment. The Contractor must ensure an independent third-party production security controls assessment is conducted at least annually, at no additional cost to the State, and performed by a State-approved third party that has no financial or controlling relationship with the Contractor. |
| The Contractor must be responsible for implementing modifications to maintain compliance with applicable State and Federal regulations and standards as outlined in the National Institute of Standards and Technology (NIST) Publication 800-53, current revision, including the application of compensating controls to address any identified gaps. |
|---|
| 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. | ||
| Other: describe | [List what's applicable or delete this line.] |
| 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. |
| Cost Type | One Time (Implementation) | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|---|
| Software | ||||||
| Enterprise Application: License Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Maintenance &/or License Fee Add-Ons | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Subscription cost | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Storage Limitations and/or Additional Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Database Software: License Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Middleware Tools: License Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Operating System Software: License Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Upgrade Costs for Later Years | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Support and Maintenance Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| Implementation Services | ||||||
| Project Management | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Requirements | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Design (Architect Solution) | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Development (Build, Configure or Aggregate)/Testing | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| System Testing | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Defect Removal | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Implement/Deploy or Integrate | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Quality Management | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Cost Type | One Time (Implementation) | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|---|
| Implementation Services Continued | ||||||
| Training | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| Telecom | $0.00 | |||||
| Bandwidth | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| Hardware | $0.00 | |||||
| Computing Hardware | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Storage and Backup Hardware | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Network Hardware | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Facilities/Data Center | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| Hosting | $0.00 | |||||
| Hosting Fees | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |
| Total Base Costs | $0.00 |
| Total Implementation plus Five Year Costs | $ 0.00 |
|---|
| Clause Location | Exception | Proposed Verbiage |
|---|---|---|
| [indicate RFP, | [briefly describe your concern about this clause] | [describe your suggested alternative wording for the clause or your |
| exhibit, attachment | [briefly describe your concern about this clause] | solution] |
| or addendum, | [briefly describe your concern about this clause] | |
| section & page | [briefly describe your concern about this clause] | |
| number] | [briefly describe your concern about this clause] | |
| [indicate RFP, | [briefly describe your concern about this clause] | [describe your suggested alternative wording for the clause or your |
| exhibit, attachment | [briefly describe your concern about this clause] | solution] |
| or addendum, | [briefly describe your concern about this clause] | |
| section & page | [briefly describe your concern about this clause] | |
| number] | [briefly describe your concern about this clause] | |
| [indicate RFP, | [briefly describe your concern about this clause] | [describe your suggested alternative wording for the clause or your |
| exhibit, attachment | [briefly describe your concern about this clause] | solution] |
| or addendum, | [briefly describe your concern about this clause] | |
| section & page | [briefly describe your concern about this clause] | |
| number] | [briefly describe your concern about this clause] | |
| Summary of Detailed Information | Date of Notification | Outcome |
|---|---|---|
| Provided Equipment or Product | Note or Comment |
|---|---|
| Signature: | |
|---|---|
| Full name: | |
| Title: | |
| Company: | |
| Date: |

With GovernmentContracts, you can:
Statewide DBOOM EVSE RFP Request Date: 9/17/2026 3:12:33 PM Open Date: 9/15/2026 Closing
State Government of Vermont
Bid Due: 11/17/2026
TITLE QUESTIONS DUE ANSWERS POSTED DUE DATE NO POSTING AFTER RFI Fleet Management
State of Vermont
Bid Due: 12/16/2026
Request for Bidders Request Date: 6/29/2026 11:55:02 AM Open Date: 6/29/2026 Closing Date:
State Government of Vermont
Bid Due: 1/07/2027
BGS Fleet Management Information System (FMIS) Request Date: 11/13/2026 9:23:55 AM Open Date:
State Government of Vermont
Bid Due: 12/16/2026