| Location: | Vermont |
|---|---|
| Posted: | Apr 29, 2026 |
| Due: | May 22, 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 |
|
ANR FPR VT State Parks Reservation Management System
Bidder Response Form Addendum 1 |
04/24/2026 04:30PM |
|
05/22/2026 04:30PM |
|
Exhibit C
State of Vermont Bidder Response Form
State of Vermont Bidder Response Form
Request for Proposal Name: ANR FPR VT State Parks Reservation Management System
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 seven (7) 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.
3.01 Functional Requirements
3.02 Business Rules
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 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.4 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.5 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: GENERAL ADMINISTRATIVE REQUIREMENTS
5.01 Project Management & Planning
As a State project manager, I want the Contractor to plan, manage, and report project activities using State-approved tools and plans So that the project is executed consistently, collaboratively, and in alignment with State governance standards.
5.2 Human Resources & Staffing Management
As a State contract manager, I want visibility and oversight of Contractor staffing and personnel So that the project maintains qualified, available and accountable resources.
5.3 Contract & Financial Management
As a State financial administrator
I want Contractor invoicing, subcontractor oversight, and legal responses managed consistently
So that financial compliance, accountability, and transparency are maintained.
5.4 Communications & Documentation Management
As a State project manager
I want project documentation and communications managed using State standards
So that information is accurate, compliant, and accessible.
5.5 Technical Design & Implementation
As a State enterprise architect
I want system, interface, and data design documentation maintained and approved
So that technical components are traceable, consistent, and support integrated operations.
5.6 Infrastructure & Hosting Management
As a State technical operations lead
I want the Contractor to manage hosting, environments, and infrastructure performance
So that systems operate reliably and meet service level agreements.
5.7 Security & Compliance Management
As a State security and privacy lead
I want compliant security controls, assessments, and protected environments
So that systems meet Federal and State privacy, audit, and cybersecurity standards.
5.8 Testing & Quality Management
As a State quality lead
I want quality and testing activities managed under approved standards and plans
So that the system meets performance, compliance, and operational expectations.
5.09 Training & User Support Management
As a State user support administrator
I want training, user guides, and help desk services delivered using State standards
So that users are supported and enabled throughout system adoption.
5.10 Operations & Maintenance Management
As a State Operations Manager,
I want maintenance, defect management, release control, and performance monitoring,
So that system stability and operational continuity are sustained.
5.11 Business Continuity & Disaster Recovery
As a State Continuity and Risk Program Owner,
I want reliable BC/DR/CIR planning, exercises, and recovery capabilities,
So that critical operations can resume during incidents or outages.
5.12 Transition & Closeout Management
As a State Program Lead,
I want an orderly turnover and transfer of knowledge, assets, and responsibilities,
So that future providers can assume services without disruption.
Part 6: 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 time-line. 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 7: 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 8: Maintenance and Support Services
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 9: PRICING
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 10: 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 11: 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.
ANR FPR VT State Parks Reservation Management System
| 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] |
| Vendor Response/Explanation | Vendor Response/Explanation | |
|---|---|---|
| Question | Yes or No | |
| Does the solution use Service Oriented Architecture for integration? | ||
| Does the solution use a Rules Engine for business rules? | ||
| Does the solution use any Master Data Management? | ||
| Does the solution use any Enterprise Content Management software? | ||
| Does the solution use any Case Management software? | ||
| Does the solution use any Business Intelligence software? | ||
| Does the solution use any Database software? | ||
| Does the solution use any Business Process Management software? | ||
| Is this a browser-based solution and if so, what browsers do you support? | ||
| Does the solution include an API for integration? |
| 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management |
|---|---|---|---|---|---|
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1356 | User Story | ANR FPR Reservation System: User Account Creation | As a Visitor or Group Coordinator, I need the ability to create a user account, so that I can submit reservations and receive relevant notifications. | ||
| 1357 | User Story | ANR FPR Reservation System: Manage User Account | As a Visitor or Group Coordinator, I need the ability to manage my user account, so that I can maintain accurate demographic information. | ||
| 1358 | User Story | ANR FPR Reservation System: Account Type | As a Visitor or Group Coordinator, I need the ability to identify the type of online user account, so that I can maintain appropriate demographic information and complete individual or group reservations. | ||
| 1359 | User Story | ANR FPR Reservation System: Residency Question | As a Visitor, I need the ability to provide my primary state of residency, so that I can receive any applicable discounts. | ||
| 1360 | User Story | ANR FPR Reservation System: Card on File | As a Visitor or Group Coordinator, I need the ability to add a credit card to my account, so that I can streamline payment processing for reservations and ensure secure transactions. | ||
| 1361 | User Story | ANR FPR Reservation System: Reservation History | As a Visitor or Group Coordinator, I need the ability to view my reservation history, so that I can track past bookings and reference for future use. | ||
| 1362 | User Story | ANR FPR Reservation System: User ID Recovery | As a Visitor or Group Coordinator, I need the ability to securely retrieve my user ID, so that I can regain access to my user account. | ||
| 1363 | User Story | ANR FPR Reservation System: Account Password Reset | As a Visitor or Group Coordinator, I need the ability to reset my password, so that I can regain access to my user account. | ||
| 1364 | User Story | ANR FPR Reservation System: Reservation Booking Channels | As a Visitor or Group Coordinator, I need the ability to make a reservation through various channels, so that I can choose the most convenient method for securing my booking. | ||
| 1365 | User Story | ANR FPR Reservation System: Search Filters | As a Visitor or Group Coordinator, I need the ability to search using selected filters, so that I can find campsite options that match my criteria before making a reservation. | ||
| 1366 | User Story | ANR FPR Reservation System: Date Range Search | As a Visitor, I need the ability to specify a date range and choose between searching all State of Vermont Parks or selected parks, so that I can find available camping options that fit my travel dates. | ||
| 1367 | User Story | ANR FPR Reservation System: Only Available Sites | As a Visitor, I need the system to provide only available sites when I search parks using selected filters by date range, so that I do not encounter unavailable options. | ||
| 1368 | User Story | ANR FPR Reservation System: Search by Park | As a Visitor, I need the ability to search for parks by entering a county, town, zip code or combination, so that I can view a comprehensive list of all parks within the specified area. | ||
| 1369 | User Story | ANR FPR Reservation System: Search by Radius | As a Visitor, I need the ability to search for parks by specifying a radius from a chosen county, town, or zip code, so that I can see a complete list of all parks within that area. | ||
| 1370 | User Story | ANR FPR Reservation System: Search Park by Filters | As a Visitor, I need the ability to select specified filters and search across all parks, so that I can see only those results that meet my criteria. | ||
| 1371 | User Story | ANR FPR Reservation System: Site Size | As a Visitor, I need the ability to search for campsites with specific size requirements (such as those that accommodate my RV's length), so that I can find a site that meets my needs. | ||
| 1372 | User Story | ANR FPR Reservation System: ADA Accessible | As a Visitor or Group Coordinator, I need the ability to search for ADA accessible sites, so that I can reserve a campsite that meets my accessibility needs. | ||
| 1373 | User Story | ANR FPR Reservation System: Amenities Search | As a Visitor, I need the ability to search campsites based on selected amenities, so that I can find sites that meet my preferences. | ||
| 1374 | User Story | ANR FPR Reservation System: Rental Items by Location | As a Visitor, I need the ability to view available rental items by location, so that I can easily find what I need for my visit and complete the rental process upon arrival. | ||
| 1375 | User Story | ANR FPR Reservation System: Pet-Friendly Sites | As a Visitor, I need the ability to search for campsites that are pet-friendly, so that I know my pets are welcome and accommodated during my stay. | ||
| 1376 | User Story | ANR FPR Reservation System: Number of People | As a Visitor, I need the ability to specify the number of people included in a single reservation, so that I can ensure the campsite accommodates everyone in my group and the correct amount is charged. | ||
| 1377 | User Story | ANR FPR Reservation System: Photos by Campsite | As a Visitor, I need to see photos of each campsite available at a particular location, so that I can choose the one that best fits my needs and preferences. | ||
| 1378 | User Story | ANR FPR Reservation System: Videos by Campsite | As a Visitor, I need the ability to view videos of campsites by location, so that I can choose a site that meets my preferences. | ||
| 1379 | User Story | ANR FPR Reservation System: Seyon Lodge Amenities | As a Visitor, I need the ability to view available options at Seyon Lodge (e.g., meal catering or the Frequent Flyer Anglers Pass), so that I can plan my visit according to my preferences and amenities offered. | ||
| 1380 | User Story | ANR FPR Reservation System: Seyon Lodge Availability | As a Visitor or Group Coordinator, I need to view availability for Seyon Lodge State Park in Groton State Forest, so that I can find open dates that fit with my travel plans. | ||
| 1381 | User Story | ANR FPR Reservation System: Seyon Lodge Reservation | As a Visitor or Group Coordinator, I need the ability to reserve the Seyon Lodge State Park in Groton State Forest, so that I can secure accommodations for up to 16 people for the desired dates. | ||
| 1382 | User Story | ANR FPR Reservation System: Reservation Hold Time | As FPR Staff, I need the system to designate an amount of time that a reservation can be held, so that it is automatically released if not confirmed within that timeframe. | ||
| 1383 | User Story | ANR FPR Reservation System: Save and Logout | As a Visitor or Group Coordinator, I need the ability to save my reservation progress, so that I can return at a later time without losing any information. | ||
| 1384 | User Story | ANR FPR Reservation System: Pet Fees | As FPR Staff, I need the ability to capture information about pets during the reservation process, so that the appropriate pet-related fees can be applied accurately. | ||
| 1385 | User Story | ANR FPR Reservation System: Residency Fees | As FPR Staff, I need the system to reference primary state of residency during the reservation process, so that I can verify the correct service fees are applied. | ||
| 1386 | User Story | ANR FPR Reservation System: Visitor Data | As FPR Staff, I need the ability to collect visitor data (e.g., Have you ever visited a VT park in the past?) during the reservation process, so that I can improve service offerings and better understand visitor preferences. | ||
| 1387 | User Story | ANR FPR Reservation System: Information Opt-Out | As a Visitor or Group Coordinator, I need the ability to opt-out of information sharing during the reservation process, so that my information is not shared or used for marketing purposes. | ||
| 1388 | User Story | ANR FPR Reservation System: Optional Survey | As FPR Staff, I need the ability to provide an optional survey to a visitor after they have completed their reservation, so that I can gather feedback to improve services and enhance the visitor experience. | ||
| 1389 | User Story | ANR FPR Reservation System: Reservation Number | As FPR Staff, I need the system to issue a unique reservation number, so that I can ensure organized tracking of reservations and prevent duplication. | ||
| 1390 | User Story | ANR FPR Reservation System: Reservation Notes | As FPR Staff, I need the ability to manage internal notes on a reservation, so that I can document details for future reference, ensuring they are visible to staff only. | ||
| 1391 | User Story | ANR FPR Reservation System: Camping Payment | As a Visitor, I need the ability to submit online payments or pay in person using various methods, so that I can complete my camping reservation. | ||
| 1392 | User Story | ANR FPR Reservation System: Camping Payment Receipt | As a Visitor, I need the system to generate a receipt after submitting payment, so that I can confirm my camping reservation payment was processed. | ||
| 1393 | User Story | ANR FPR Reservation System: Camping Confirmation | As a Visitor, I need to receive a confirmation email, so that I verify my camping reservation details and review park-specific Terms of Use. | ||
| 1394 | User Story | ANR FPR Reservation System: Edit Reservation | As a Visitor or Group Coordinator, I need the ability to edit reservations, so that I can adjust my plans without having to cancel and rebook. | ||
| 1395 | User Story | ANR FPR Reservation System: Confirmation of Changes | As a Visitor or Group Coordinator, I need to receive an email confirmation after any changes are made to my reservation, so that I can verify the accuracy of the updates. | ||
| 1396 | User Story | ANR FPR Reservation System: Cancel Reservation | As a Visitor or Group Coordinator, I need the ability to cancel my reservation, so that the dates, location and/or program become available for others to book. | ||
| 1397 | User Story | ANR FPR Reservation System: Cancellation Reason | As a Visitor or Group Coordinator, I need the ability to provide a reason for my cancellation, so that FPR can gather insights into cancellation trends. | ||
| 1398 | User Story | ANR FPR Reservation System: Cancellation Refund | As a Visitor or Group Coordinator, I need the system to automatically refund payment after cancelling a reservation, so that I am reimbursed promptly. | ||
| 1399 | User Story | ANR FPR Reservation System: Cancellation Confirmation | As a Visitor or Group Coordinator, I need to receive an email confirmation after cancelling my reservation, so that I can verify the cancellation was processed. | ||
| 1400 | User Story | ANR FPR Reservation System: Cancellation Waitlist | As a Visitor, I need the ability to join a waitlist for fully booked sites, so that I can reserve a site if one becomes available. | ||
| 1401 | User Story | ANR FPR Reservation System: Cancellation Waitlist Notification | As a Visitor, I need to receive an email when a site on the waitlist that meets my criteria becomes available, so that I can quickly make a reservation and secure the site. | ||
| 1402 | User Story | ANR FPR Reservation System: Consolidated Booking Confirmation | As FPR Staff, I need the system to consolidate booking confirmations into a single email when a visitor reserves multiple campsites, so that I can provide one comprehensive confirmation simplifying transaction records. | ||
| 1403 | User Story | ANR FPR Reservation System: Upload Campsite Photos | As a Visitor, I need the ability to upload photos that meet pre-approved criteria (similar to RDC), so that I can quickly and efficiently share images of campsites at a particular location. | ||
| 1404 | User Story | ANR FPR Reservation System: Group Day-Entry Sites | As a Group Coordinator, I need the ability to reserve group day-entry sites, so that I can ensure the space and facilities will accommodate all members of my group. | ||
| 1405 | User Story | ANR FPR Reservation System: Group Reservation | As a Group Coordinator, I need the ability to make a group-specific or program-specific reservation, so that I can manage activities and ensure all necessary facilities and resources are available. | ||
| 1406 | User Story | ANR FPR Reservation System: Group Site Block | As FPR Staff, I need the ability to block a group of sites at a particular location, so that individuals can reserve a specific site from the blocked group. | ||
| 1407 | User Story | ANR FPR Reservation System: Group Site Reservation | As a Visitor, I need the ability to reserve a site within a group block, so that I am located with other visitors attending the same event. | ||
| 1408 | User Story | ANR FPR Reservation System: Educational and Guided Programs Reservation | As a Visitor or Group Coordinator, I need the ability to reserve a spot in an educational and/or guided program, so that I can participate in an interactive nature activity. | ||
| 1409 | User Story | ANR FPR Reservation System: Educational and Guided Programs Search | As a Visitor or Group Coordinator, I need the ability to search for educational and/or guided programs by park location, activity type, duration, age suitability, and special requirements, so that I can find activities that match my interests. | ||
| 1410 | User Story | ANR FPR Reservation System: Educational and Guided Programs Waitlist | As a Visitor or Group Coordinator, I need the ability to join a waitlist for fully booked educational and/or guided programs, so that I can be notified if a spot becomes available and have the opportunity to reserve it. | ||
| 1411 | User Story | ANR FPR Reservation System: 2-Week Hold | As FPR Staff, I need the system to allow a reservation to be placed on hold for up to two weeks without immediate payment, so that visitors have time to finalize their plans and payment details before confirming the reservation. | ||
| 1412 | User Story | ANR FPR Reservation System: Payment Reminders | As FPR Staff, I need the system to automatically email payment reminders 14 days and 7 days before the due date, so that I can ensure timely payment and finalize reservations. | ||
| 1413 | User Story | ANR FPR Reservation System: No Payment Email | As FPR Staff, I need the system to automatically email a no-payment reminder 1 day after the due date, so that the visitor is notified their reservation has been released due to non-payment. | ||
| 1414 | User Story | ANR FPR Reservation System: Damage Deposits | As FPR Staff, I need the ability to accept a damage deposit, so that I ensure coverage for any potential damages during a visitor's stay. | ||
| 1415 | User Story | ANR FPR Reservation System: Manual Check-in Process | As FPR Staff, I need the ability to check-in visitors, so that I can verify reservation details (such as number of party members present), issue necessary parking tags, and provide information about park rules, maps, and scheduled activities or events. | ||
| 1416 | User Story | ANR FPR Reservation System: Self-Service Check-in and Check-out | As a Visitor, I need the ability to check-in and check-out at the park using self-service (e.g., kiosk, QR code, mobile app), so that I can verify my reservation, access park information, and confirm my visit without having to wait for staff assistance. | ||
| 1417 | User Story | ANR FPR Reservation System: Self-Service Partial Check-in | As a Visitor, I need the ability to complete partial check-in using self-service (e.g., kiosk, QR code, mobile app), so that the members who have arrived can receive their parking permits and park information while waiting for the rest of the group to arrive. | ||
| 1418 | User Story | ANR FPR Reservation System: Manual Partial Check-in | As FPR Staff, I need the ability to process partial check-ins, so that I can verify and record the arrival of some party members and ensure smooth entry for the remaining members upon their arrival. | ||
| 1419 | User Story | ANR FPR Reservation System: Manual Check-out | As FPR Staff, I need the ability to check-out visitors at the park, so I can finalize their visit and provide assistance if needed. | ||
| 1420 | User Story | ANR FPR Reservation System: Check-out Email | As FPR Staff, I need the system to automatically email overnight visitors at check-out, so that they receive a confirmation of their visit and any relevant follow-up information. | ||
| 1421 | User Story | ANR FPR Reservation System: Lottery System | As FPR Staff, I need the ability to manage a lottery system for specified sites with random selection, so that visitors have a fair chance of securing a booking. | ||
| 1422 | User Story | ANR FPR Reservation System: Survey Management | As FPR Staff, I need the ability to manage optional survey questions, so that I can ensure the survey remains relevant and gathers feedback to improve services and visitor satisfaction. | ||
| 1423 | User Story | ANR FPR Reservation System: Camping Dashboard | As FPR Staff, I need a camping dashboard that displays real-time data on current occupancy, upcoming reservations, and availability across multiple locations, so that I can manage bookings. | ||
| 1424 | User Story | ANR FPR Reservation System: Add Camping Reservation | As FPR Staff, I need the ability to add a campsite reservation, so that I can secure a spot for the visitor's desired dates. | ||
| 1425 | User Story | ANR FPR Reservation System: Modify Camping Reservation | As FPR Staff, I need the ability to modify an existing campsite reservation, so that I can help a visitor accommodate changes in their plans. | ||
| 1426 | User Story | ANR FPR Reservation System: Cancel Camping Reservation | As FPR Staff, I need the ability to cancel a campsite reservation, so I can assist a visitor and free up the spot for others to reserve. | ||
| 1427 | User Story | ANR FPR Reservation System: Add Campsites | As FPR Staff, I need the ability to add new campsites, so that they can be made available for public use. | ||
| 1428 | User Story | ANR FPR Reservation System: Modify Campsites | As FPR Staff, I need the ability to modify existing campsites, so that I can ensure accurate information is provided to visitors. | ||
| 1429 | User Story | ANR FPR Reservation System: Remove Campsites | As FPR Staff, I need the ability to remove campsites, so that I can manage their availability. | ||
| 1430 | User Story | ANR FPR Reservation System: Add Amenities | As FPR Staff, I need the ability to add amenities, so that I can offer new options to visitors. | ||
| 1431 | User Story | ANR FPR Reservation System: Modify Amenities | As FPR Staff, I need the ability to modify existing amenities, so that I can update availablity details. | ||
| 1432 | User Story | ANR FPR Reservation System: Remove Amenities | As FPR Staff, I need the ability to remove amenities, so that I can maintain accurate records. | ||
| 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services |
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1433 | User Story | ANR FPR Reservation System: Self-Service Day-Entry | As FPR Staff, I need the ability to manage prepaid day-entry passes with self-service lines (e.g., kiosk, QR code, mobile app), so that I can streamline park entry and reduce visitor wait times. | ||
| 1434 | User Story | ANR FPR Reservation System: Parking Reservation | As a Visitor, I need the ability to reserve a parking space online or in person at select locations, so that I can ensure I have a spot for my car during my visit. | ||
| 1435 | User Story | ANR FPR Reservation System: Vehicle Details | As a Visitor, I need the ability to provide vehicle details, so that I can associate my vehicle with my camping or parking reservation. | ||
| 1436 | User Story | ANR FPR Reservation System: Parking Payment | As a Visitor, I need the ability to pay for parking online or in person, so that I can secure a parking space for my vehicle. | ||
| 1437 | User Story | ANR FPR Reservation System: Parking Payment Receipt | As a Visitor, I need the system to email a receipt for printing or generate a paper receipt after submitting payment for parking, so that I can display proof of payment on my vehicle's dashboard. | ||
| 1438 | User Story | ANR FPR Reservation System: Self-Service Parking | As a Visitor, I need the ability to use self-service parking (e.g., kiosk, QR code, mobile app), so that I can pay for all-day parking and receive a digital ticket for display in my vehicle. | ||
| 1439 | User Story | ANR FPR Reservation System: Parking Alerts | As FPR Staff, I need the system to send automated alerts when parking is at predefined thresholds, so that I can proactively manage parking and resources. | ||
| 1440 | User Story | ANR FPR Reservation System: Parking Dashboard | As FPR Staff, I need the system to provide a dashboard that displays parking capacity at select locations, so that I can see the number of open spots at any given time. | ||
| 1441 | User Story | ANR FPR Reservation System: Public Parking Dashboard | As a Visitor, I need to view an online, real-time dashboard displaying parking availability by park location, so I can plan my visit accordingly. | ||
| 1442 | User Story | ANR FPR Reservation System: Boat Slip/Mooring Search | As a Visitor, I need the ability to search for a boat slip or mooring by size allocation (e.g., show me dock spaces that accommodate a 30ft boat), so that I can find a suitable space that fits my boat. | ||
| 1443 | User Story | ANR FPR Reservation System: Boat Slip/Mooring Reservation | As a Visitor, I need the ability to reserve a boat slip or mooring, so that I can ensure a spot for my boat during my visit. | ||
| 1444 | User Story | ANR FPR Reservation System: Boat Slip/Mooring Payment | As a Visitor, I need the ability to pay for a boat slip or mooring, so that I can complete my reservation. | ||
| 1445 | User Story | ANR FPR Reservation System: Boat Slip/Mooring Payment Receipt | As a Visitor, I need the system to email or generate a paper receipt after submitting payment, so that I can provide proof of payment for my boat slip or mooring. | ||
| 1446 | User Story | ANR FPR Reservation System: Boat Slip/Mooring Check-in and Check-out | As FPR Staff, I need the system to manage both check-in and check-out processes for Boat Slip/Mooring, so that I can track occupancy and vacated slips in real-time. | ||
| 1447 | User Story | ANR FPR Reservation System: Boat Slip/Mooring Dashboard | As FPR Staff, I need the system to provide a dashboard that displays boat slips and moorings availability, current occupancy, and upcoming reservations, so that I can assign available spots for in-person reservations. | ||
| 1448 | User Story | ANR FPR Reservation System: Dock Pump-Out | As FPR Staff, I need the ability to track dock pump-out services at the dock, so that I can ensure accurate reporting to the State of Vermont Fish and Wildlife for reimbursement. | ||
| 1449 | User Story | ANR FPR Reservation System: Dump Station | As FPR Staff, I need the ability to charge visitors for using the dump station if they are not staying in the park, so that I can ensure fair usage of park facilities. | ||
| 1450 | User Story | ANR FPR Reservation System: Ferry Schedule | As a Visitor, I need the system to generate a ferry schedule, so that I can see days and times of operation. | ||
| 1451 | User Story | ANR FPR Reservation System: Ferry Service Reservation | As a Visitor, I need the ability to reserve ferry service for a specific date and time slot, so that I can guarantee travel to and from Kill Kare State Park or Burton Island State Park. | ||
| 1452 | User Story | ANR FPR Reservation System: Ferry Service Payment | As a Visitor, I need the ability to pay for ferry service, so that I can ensure transportation to my boat-accessible site. | ||
| 1453 | User Story | ANR FPR Reservation System: Ferry Service Payment Receipt | As a Visitor, I need the system to email or generate a paper receipt after submitting payment, so that I can provide proof of payment for ferry services. | ||
| 1454 | User Story | ANR FPR Reservation System: Gear Delivery Reservation | As a Visitor, I need the ability to reserve a specific date and time slot for gear delivery service to and from Burton Island State Park, so that I ensure assistance with transporting my equipment to my site. | ||
| 1455 | User Story | ANR FPR Reservation System: Gear Delivery Payment | As a Visitor, I need the ability to pay for gear delivery, so that I can ensure gear delivery services are scheduled. | ||
| 1456 | User Story | ANR FPR Reservation System: Gear Delivery Payment Receipt | As a Visitor, I need the system to email or generate a paper receipt after submitting payment, so that I can provide proof of payment for gear delivery services. | ||
| 1457 | User Story | ANR FPR Reservation System: Add Boat Slip or Mooring | As FPR Staff, I need the ability to add a new boat slip or mooring, so that it can be made available for public use. | ||
| 1458 | User Story | ANR FPR Reservation System: Modify Boat Slip or Mooring | As FPR Staff, I need the ability to modify existing boat slips or moorings, so that I can ensure the accuracy of public information. | ||
| 1459 | User Story | ANR FPR Reservation System: Remove Boat Slip or Mooring | As FPR Staff, I need the ability to remove a boat slip or mooring, so that it is no longer available for public use. | ||
| 1460 | User Story | ANR FPR Reservation System: Add Ferry Schedule | As FPR Staff, I need the ability to add dates and times to the ferry schedule, so that I can ensure up-to-date information is available for public use. | ||
| 1461 | User Story | ANR FPR Reservation System: Modify Ferry Schedule | As FPR Staff, I need the ability to modify existing dates and times in the ferry schedule, so that I can maintain schedule accuracy. | ||
| 1462 | User Story | ANR FPR Reservation System: Remove Ferry Schedule | As FPR Staff, I need the ability to remove dates and times from the ferry schedule, so that I can prevent outdated information from being displayed. | ||
| 1463 | User Story | ANR FPR Reservation System: Add Gear Delivery Schedule | As FPR Staff, I need the ability to add dates and times to the gear delivery schedule, so that I can ensure up-to-date information for the public. | ||
| 1464 | User Story | ANR FPR Reservation System: Modify Gear Delivery Schedule | As FPR Staff, I need the ability to modify existing dates and times in the gear delivery schedule, so that I can maintain schedule for accuracy. | ||
| 1465 | User Story | ANR FPR Reservation System: Remove Gear Delivery Schedule | As FPR Staff, I need the ability to remove dates and times from the gear delivery schedule, so that I can prevent outdated schedules from displaying to the public | ||
| 1466 | User Story | ANR FPR Reservation System: Add Gear Delivery Resources | As FPR Staff, I need the ability to add new gear delivery resources (e.g., add an ATV or golf cart), so that I can ensure all necessary equipment is available. | ||
| 1467 | User Story | ANR FPR Reservation System: Modify Gear Delivery Resources | As FPR Staff, I need the ability to modify existing gear delivery resources (e.g., updating maintenance records), so that I can keep information current and ensure equipment is in optimal condition. | ||
| 1468 | User Story | ANR FPR Reservation System: Remove Gear Delivery Resources | As FPR Staff, I need the ability to remove gear delivery resources (e.g., take faulty ATV out of inventory), so that I can manage resources efficiently. | ||
| 1469 | User Story | ANR FPR Reservation System: Add Parking Spaces | As FPR Staff, I need the ability to add new parking spaces, so that I can accommodate more visitors. | ||
| 1470 | User Story | ANR FPR Reservation System: Modify Parking Spaces | As FPR Staff, I need the ability to modify existing parking spaces, so that I can update the configuration. | ||
| 1471 | User Story | ANR FPR Reservation System: Remove Parking Spaces | As FPR Staff, I need the ability to remove parking spaces, so that I can manage space allocation. | ||
| 1472 | User Story | ANR FPR Reservation System: Add Parking and Marina Services Reservation | As FPR Staff, I need the ability to add parking and marina services, so that I can help a visitor complete their request. | ||
| 1473 | User Story | ANR FPR Reservation System: Modify Parking and Marina Services Reservation | As FPR Staff, I need the ability to modify existing parking and marina services, so that I can assist a visitor with changes in their plans. | ||
| 1474 | User Story | ANR FPR Reservation System: Cancel Parking and Marina Services Reservation | As FPR Staff, I need the ability to cancel parking and marina services, so that I can update availability for other visitors. | ||
| 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight |
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1475 | User Story | ANR FPR Reservation System: Day-Entry Pass | As a Visitor, I need the ability to purchase a day-entry pass online or in person, so that I can access the park conveniently. | ||
| 1476 | User Story | ANR FPR Reservation System: Bulk Coupons | As FPR Staff, I need the ability to distribute bulk coupons, so that I can track visitors entering the park for day-use at no charge. | ||
| 1477 | User Story | ANR FPR Reservation System: 10-Visit Punch Pass | As a Visitor, I need the ability to purchase a 10-visit punch pass, so that I can access various day-entry State of Vermont parks without having to pay for each individual visit. | ||
| 1478 | User Story | ANR FPR Reservation System: Discount Codes | As FPR Staff, I need the ability to provide a discount code, so that visitors can receive promotional pricing or special offers. | ||
| 1479 | User Story | ANR FPR Reservation System: Gift Card | As a Visitor, I need the ability to purchase a physical or electronic gift card with no expiration date, so that the recipient can use it at their convenience. | ||
| 1480 | User Story | ANR FPR Reservation System: Valid Forms of Entry | As a Visitor, I need the ability to use a valid form of entry, so that I can enjoy day-entry to any State of Vermont park without additional payment. | ||
| 1481 | User Story | ANR FPR Reservation System: Valid Forms of Entry Tracking | As FPR Staff, I need the ability to track Valid Forms of Entry by program, so that I can invoice programs at a later date for reimbursement. | ||
| 1482 | User Story | ANR FPR Reservation System: Individual Season Pass | As a Visitor, I need the ability to purchase an individual season pass, so that I have unlimited access to State of Vermont day-entry parks throughout the season without having to pay for each visit. | ||
| 1483 | User Story | ANR FPR Reservation System: Season Pass and Group-Entry Pass Barcode | As FPR Staff, I need the ability to add a barcode to a season pass and group-entry pass, so that I can track entry and verify visitor access. | ||
| 1484 | User Story | ANR FPR Reservation System: Vehicle Pass | As a Visitor, I need the ability to purchase a vehicle pass, so that I can access State of Vermont day-entry parks throughout the season without having to pay for each individual riding in my vehicle. | ||
| 1485 | User Story | ANR FPR Reservation System: Organizational Vehicle | As a Visitor, I need the ability to purchase an organizational vehicle (17-passenger) pass, so that I can facilitate transportation for group activities without additional transportation fees. | ||
| 1486 | User Story | ANR FPR Reservation System: Student Groups | As a Group Coordinator, I need the ability to submit an anticipated headcount for a K-12 student group at least two weeks before our visit, so that the park can prepare for our arrival, with payment collected on the day of entry based on actual attendance. | ||
| 1487 | User Story | ANR FPR Reservation System: Municipal Groups | As a Visitor, I need the ability to arrange municipal recreation group entry for 1-25 people, including staff and driver, so that I can manage group visits and within budget. | ||
| 1488 | User Story | ANR FPR Reservation System: Municipal Groups Add'l | As a Visitor, I need the ability to add additional municipal recreation groups of 25 people (or a portion) for the same rate, so that I can maintain consistent pricing for entry. | ||
| 1489 | User Story | ANR FPR Reservation System: Group Rate | As FPR Staff, I need the ability to charge an individual visitor the group day-use rate, so I can apply approved discounts for entry. | ||
| 1490 | User Story | ANR FPR Reservation System: Rental Item | As a Visitor, I need the ability to rent a recreational item by location, so that I can enjoy and explore the area I am visiting. | ||
| 1491 | User Story | ANR FPR Reservation System: Rental Payment | As a Visitor, I need the ability to pay for rentals with an acceptable form of payment, so that I can complete my rental transaction and provide payment in full. | ||
| 1492 | User Story | ANR FPR Reservation System: Rental Payment Receipt | As FPR Staff, I need the system to automatically generate a rental receipt, so that visitors are informed of the rental rules, return time, and any potential additional fees. | ||
| 1493 | User Story | ANR FPR Reservation System: Rental Age Restrictions | As FPR Staff, I need the ability to validate age restrictions on rentals, so that I can ensure compliance with safety regulations and legal requirements. | ||
| 1494 | User Story | ANR FPR Reservation System: Rental Waiver | As a Visitor, I need to complete and sign a rental specific waiver, so that I am informed of all safety and liability requirements. | ||
| 1495 | User Story | ANR FPR Reservation System: Rental Check-in and Check-out | As FPR Staff, I need the ability to manage check-in and check-out for rentals, so that I can track rental durations. | ||
| 1496 | User Story | ANR FPR Reservation System: Rental Late Fee | As FPR Staff, I need the ability to apply a late fee to overdue rentals, so that I can encourage timely returns and maintain availability of rental inventory. | ||
| 1497 | User Story | ANR FPR Reservation System: Rental Timeframes | As FPR Staff, I need the ability to track rental start and return times, so that I can ensure timely returns and monitor availability for the next customer. | ||
| 1498 | User Story | ANR FPR Reservation System: Rental Item Tracking | As FPR Staff, I need the ability to track ID numbers on all rental items, so that I can manage accurate inventory. | ||
| 1499 | User Story | ANR FPR Reservation System: Rental Dashboard | As FPR Staff, I need the system to provide a dashboard displaying daily rental and time slot availability by location, so that I can provide up-to-date information to visitors. | ||
| 1500 | User Story | ANR FPR Reservation System: Inventory Designation | As FPR Staff, I need the ability to designate inventory as restrictive or non-restrictive, so that I ensure accurate sales tracking and optimize inventory control. | ||
| 1501 | User Story | ANR FPR Reservation System: Inventory Management | As FPR Staff, I need the ability to manage inventory levels, movements, stockouts, and reorder points, so that I can maintain accurate records of stock quantities and ensure sufficient inventory to meet demand without overstocking. | ||
| 1502 | User Story | ANR FPR Reservation System: Inventory Reconciliation | As FPR Staff, I need the ability to reconcile actual inventory on hand with the inventory recorded in the system, so that I can ensure accurate stock levels. | ||
| 1503 | User Story | ANR FPR Reservation System: Merchandise Workload | As FPR Staff, I need the ability to manage merchandise workload, so I can monitor transfers, stock levels and when to reorder items. | ||
| 1504 | User Story | ANR FPR Reservation System: Drop Ship | As FPR Staff, I need the ability to drop ship merchandise directly from suppliers to customers, so that I can expand product offerings without holding inventory and reduce shipping times for customers. | ||
| 1505 | User Story | ANR FPR Reservation System: Shipping Fees | As FPR Staff, I need the ability to standardize shipping fees and implement free shipping for orders above a set sub-total, so that I can ensure consistent pricing and streamline the billing process. | ||
| 1506 | User Story | ANR FPR Reservation System: View Inventory Across Parks | As FPR Staff, I need the ability to view inventory across different parks, so that I can request items as needed. | ||
| 1507 | User Story | ANR FPR Reservation System: Warehouse Inventory | As FPR Staff, I need the ability to manage inventory at both regional and home office warehouses, so that I can ensure accurate stock levels and optimize resource distribution. | ||
| 1508 | User Story | ANR FPR Reservation System: Wholesale and Retail Pricing | As FPR Staff, I need the ability to manage wholesale and retail pricing, so that I can implement accurate pricing strategies and optimize profit margins. | ||
| 1509 | User Story | ANR FPR Reservation System: Contactless Purchase | As a Visitor, I need the ability to make contactless purchases using my mobile device, so that I can complete transactions without needing staff assistance. | ||
| 1510 | User Story | ANR FPR Reservation System: Add POS Items | As FPR Staff, I need the ability to add concession items, camping supplies, passes and merchandise, so that I can keep inventory current. | ||
| 1511 | User Story | ANR FPR Reservation System: Modify POS Items | As FPR Staff, I need the ability to modify concession items, camping supplies, passes and merchandise, so that I can provide up-to-date options for purchase. | ||
| 1512 | User Story | ANR FPR Reservation System: Remove POS Items | As FPR Staff, I need the ability to remove concession items, camping supplies, passes and merchandise, so that items no longer available. | ||
| 1513 | User Story | ANR FPR Reservation System: Add Rentals | As FPR Staff, I need the ability to add rental inventory by location, so that I can ensure accurate availability of rental items. | ||
| 1514 | User Story | ANR FPR Reservation System: Modify Rentals | As FPR Staff, I need the ability to modify rental inventory by location, so that I can provide visitors with up-to-date options to choose from. | ||
| 1515 | User Story | ANR FPR Reservation System: Remove Rentals | As FPR Staff, I need the ability to remove rental inventory by location, so that rental items no longer available do not show to the public. | ||
| 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting |
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1516 | User Story | ANR FPR Reservation System: Process Payments | As FPR Staff, I need the ability to process a payment, so that customer transactions are completed. | ||
| 1517 | User Story | ANR FPR Reservation System: Payment Type | As FPR Staff, I need the ability to process various payment types, so that I can accommodate visitor preferences. | ||
| 1518 | User Story | ANR FPR Reservation System: Process Refunds | As FPR Staff, I need the ability to process a refund, so that accounts stay up-to-date and reservations are immediately available for other customers. | ||
| 1519 | User Story | ANR FPR Reservation System: Process Refunds in NIC | As FPR Staff, I need the ability to process a refund in NIC, so that funds are returned back to the original method of payment. | ||
| 1520 | User Story | ANR FPR Reservation System: Process Transfers | As FPR Staff, I need the ability to process a transfer, so that I can allocate fees from one reservation to another. | ||
| 1521 | User Story | ANR FPR Reservation System: Split Payments | As FPR Staff, I need the ability to process split payments, so that I can apply a single payment to multiple accounts. | ||
| 1522 | User Story | ANR FPR Reservation System: NSF Processing | As FPR Staff, I need the system to process NSF transactions, apply an NSF fee, and add the charge back to the account, so that I can ensure accurate account balances. | ||
| 1523 | User Story | ANR FPR Reservation System: Access to NIC Data for Reconciliation and NSF | As FPR Staff, I need the ability to access financial transactions in NIC, so that I am able to reconcile payments and validate NSF processing. | ||
| 1524 | User Story | ANR FPR Reservation System: Cash Drawer Starting Amount | As FPR Staff, I need the ability to verify the starting amount by cash drawer, so that I can accurately reconcile at the end of my shift. | ||
| 1525 | User Story | ANR FPR Reservation System: Cash Drawer Support | As FPR Staff, I need the system to accommodate cash drawers, so that I can securely manage cash transactions at multiple sites across parks. | ||
| 1526 | User Story | ANR FPR Reservation System: Blind Closeout | As FPR Staff, I need the ability to perform a blind closeout reconciliation of financial transactions, so that I can ensure all transactions are accurately recorded and discrepancies are identified without prior knowledge of expected outcomes. | ||
| 1527 | User Story | ANR FPR Reservation System: Bank Deposit | As FPR Staff, I need the ability to generate a bank deposit following the blind closeout process, so that I can ensure accurate financial reconciliation and manage cash for each location. | ||
| 1528 | User Story | ANR FPR Reservation System: Create Invoice | As FPR Staff, I need the ability to create an invoice, so that I can provide organizations with amount due for services. | ||
| 1529 | User Story | ANR FPR Reservation System: Charge Back | As FPR Staff, I need the ability to charge back to a special program, so that I can accurately bill for the usage of bulk coupons. | ||
| 1530 | User Story | ANR FPR Reservation System: Financial Transaction Processing | As FPR Staff, I need the system to automatically defer processing financial transactions on observed federal holidays and schedule them for the following business day, so that I can ensure compliance with banking regulations and maintain accurate financial operations. | ||
| 1531 | User Story | ANR FPR Reservation System: Financial Transactions to VISION | As FPR Staff, I need the system to send financial transactions to VISION, so that I can maintain compliance with State financial regulations. | ||
| 1532 | User Story | ANR FPR Reservation System: Financial Transaction Fields | As FPR Staff, I need the ability to capture specific accounting fields when completing financial transactions, so that I can ensure data consistency with VISION. | ||
| 1533 | User Story | ANR FPR Reservation System: Seasonal Demand Pricing | As FPR Staff, I need the ability to adjust rates and fees based on seasonal demand and site amenities, so that I can ensure fair pricing for all visitors, reflecting site popularity without surge pricing. | ||
| 1534 | User Story | ANR FPR Reservation System: VT Parks Forever Donations | As FPR Staff, I need the ability to add a round-up line during the online checkout process, so that visitors can easily contribute additional funds to support the Vermont Parks Forever project. | ||
| 1535 | User Story | ANR FPR Reservation System: Add Fees | As FPR Staff, I need the ability to add new fees, so that I can ensure all services and resources are accurately priced for visitors. | ||
| 1536 | User Story | ANR FPR Reservation System: Modify Fees | As FPR Staff, I need the ability to modify existing fees, so that I can update pricing to reflect changes in costs or policies. | ||
| 1537 | User Story | ANR FPR Reservation System: Expire Fees | As FPR Staff, I need the ability to expire fees, so that I can maintain an accurate and current fee structure. | ||
| 1538 | User Story | ANR FPR Reservation System: Manage Finance and Accounting | As FPR Staff, I need the ability to manage accounting information, so that I can provide consistent accounting and up-to-date reporting for all transactions. | ||
| 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload |
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1539 | User Story | ANR FPR Reservation System: Ad-Hoc Queries | As FPR Staff, I need the ability to perform ad-hoc queries on demand, so that I can generate as-needed reports and/or search results. | ||
| 1540 | User Story | ANR FPR Reservation System: Export Ad-Hoc Queries | As FPR Staff, I need the ability to export ad-hoc query results in various formats, so that I can share data with stakeholders. | ||
| 1541 | User Story | ANR FPR Reservation System: Save Ad-hoc Queries | As FPR Staff, I need the system to save queries for future use, so that I don't have to rebuild commonly used queries. | ||
| 1542 | User Story | ANR FPR Reservation System: Save and Rerun Reports | As FPR Staff, I need the ability to save report definitions, so that I can easily rerun reports without having to redefine parameters. | ||
| 1543 | User Story | ANR FPR Reservation System: Schedule Recurring Reports | As FPR Staff, I need the ability to schedule recurring reports, so that recipient(s) receive automated reports on specified dates. | ||
| 1544 | User Story | ANR FPR Reservation System: Send Scheduled Reports | As FPR Staff, I need the system to automatically send scheduled reports, so that recipient(s) receive the correct information at the designated time. | ||
| 1545 | User Story | ANR FPR Reservation System: Send Ad-hoc Reports | As FPR Staff, I need the ability to send ad-hoc reports, so that recipient(s) receive reports as needed. | ||
| 1546 | User Story | ANR FPR Reservation System: Out-Of-The-Box Reports | As FPR Staff, I need the ability to run out-of-the-box reports, so that I can quickly access information and make informed decisions without vendor support. | ||
| 1547 | User Story | ANR FPR Reservation System: Report Filters | As FPR Staff, I need the ability to apply various filters to reports, so that I can analyze relevant data, understand visitor demographics and assess camping demands. | ||
| 1548 | User Story | ANR FPR Reservation System: Report Modes | As FPR Staff, I need the ability to view reports in Summary or Detail modes, so that I can access high-lever or detailed information. | ||
| 1549 | User Story | ANR FPR Reservation System: Report Access | As a System Administrator, I need the ability to assign report access by user role, so that I can ensure data security and compliance with organizational policies. | ||
| 1550 | User Story | ANR FPR Reservation System: Accounts Receivable Report | As FPR Staff, I need the ability to generate a detailed Accounts Receivable Report, so that I can improve cash flow management. | ||
| 1551 | User Story | ANR FPR Reservation System: ACFR-1 Report | As FPR Staff, I need the ability to generate a detailed Annual Comprehensive Financial Report, so that I can meet State of Vermont requirements under 32 V.S.A. 163, 32 V.S.A. 167, and 32 V.S.A. 168. | ||
| 1552 | User Story | ANR FPR Reservation System: Attendance Comparison Report | As FPR Staff, I need to generate a detailed Attendance Comparison Report, so that I can analyze changes in visitor patterns over time. | ||
| 1553 | User Story | ANR FPR Reservation System: Average Daily Rate (ADR) | As FPR Staff, I need the ability to generate a detailed Average Daily Rate (ADR) Report, so that I can review the average price paid per occupied room or site over a given period. | ||
| 1554 | User Story | ANR FPR Reservation System: Bicycle Rental Revenue Report | As FPR Staff, I need the ability to generate a detailed Bicycle Rental Revenue Report, so that I can provide accurate billing information to our local rental vendor. | ||
| 1555 | User Story | ANR FPR Reservation System: Cancellations Report | As FPR Staff, I need to the ability to generate a detailed Cancellations Report, so that I can reivew cancellation reasons and improve reservation policies. | ||
| 1556 | User Story | ANR FPR Reservation System: Check-In Tracking Report | As FPR Staff, I need the ability to generate a detailed Check-In Tracking Report, so that I can track early and/or late check-ins to assist with a more efficient check-in process. | ||
| 1557 | User Story | ANR FPR Reservation System: Crew and Passenger Report | As FPR Staff, I need the ability to generate a detailed Crew and Passenger Report, so that I can meet United States Coast Guard and Customs and Border Protection requirements under 46 CFR 122.502 and 19 CFR 4.64. | ||
| 1558 | User Story | ANR FPR Reservation System: Day-Entry Attendance Report | As FPR Staff, I need the ability to generate a detailed Day-Entry Attendance Report by hour and by location, so that I can ensure adequate staffing and improve visitor experience. | ||
| 1559 | User Story | ANR FPR Reservation System: Marina Pump-Outs Report | As FPR Staff, I need the ability to generate a detailed Marina Pump-Outs Report, so that I can meet State of Vermont, Fish and Wildlife requirements for reimbursement | ||
| 1560 | User Story | ANR FPR Reservation System: Donations Round-Up Report | As FPR Staff, I need the ability to generate a detailed Donations Round-Up Report, so that I can facilitate donor communication and manage mailings efficiently. | ||
| 1561 | User Story | ANR FPR Reservation System: Facility Occupancy Report | As FPR Staff, I need the ability to generate a detailed Facility Occupancy Report, so that I can monitor and manage facility usage effectively and ensure optimal resource allocation. | ||
| 1562 | User Story | ANR FPR Reservation System: Financial Metrics Report | As FPR Staff, I need the ability to generate a detailed Financial Metrics Report, so that I can evaluate key performance indicators for strategic evaluation. | ||
| 1563 | User Story | ANR FPR Reservation System: Forecasting Report | As FPR Staff, I need the ability to generate a detailed Forecasting Report, so that I can analyze revenue based on changes to pricing structure and adjust strategies accordingly. | ||
| 1564 | User Story | ANR FPR Reservation System: Gear Delivery Report | As FPR Staff, I need the ability to generate a detailed Gear Delivery Report, so that I can review the schedule of booked days and times. | ||
| 1565 | User Story | ANR FPR Reservation System: General Ledger Summary and Detailed Transactions Report | As FPR Staff, I need the ability to generate a detailed General Ledger Summary and Detailed Transactions Report, so that I can understand financial activities and ensure audit compliance. | ||
| 1566 | User Story | ANR FPR Reservation System: Group Booking Attendees Report | As FPR Staff, I need the ability to generate a detailed Group Booking Attendees Report, so that I can tailor services and programs to visitor demographics. | ||
| 1567 | User Story | ANR FPR Reservation System: Inventory Report | As FPR Staff, I need the ability to generate a detailed Inventory Report, so that I can track inventory levels and manage stock. | ||
| 1568 | User Story | ANR FPR Reservation System: Marketing Metrics Report | As FPR Staff, I need the ability to generate a detailed Marketing Metrics Report, so that I can track the sources of web traffic and understand how visitors are reaching our website. | ||
| 1569 | User Story | ANR FPR Reservation System: NASPD Fiscal Year Metrics Report | As FPR Staff, I need the ability to generate a detailed NASPD Fiscal Year Metrics Report, so that I can comply with NASPD reporting standards. | ||
| 1570 | User Story | ANR FPR Reservation System: No-Show Report | As FPR Staff, I need the ability to generate a detailed No-Show Report for visitors who do not complete the check-in process, so that I can understand customer behavior and improve reservation policies. | ||
| 1571 | User Story | ANR FPR Reservation System: Outstanding Receivables Report | As FPR Staff, I need the ability to generate a detailed Outstanding Receivables Report, so that I can monitor overdue payments and unpaid invoices. | ||
| 1572 | User Story | ANR FPR Reservation System: Overall Attendance Report | As FPR Staff, I need the ability to generate a detailed Overall Attendance Report, so that I can review day-entry and camping reservations, allowing me to monitor visitor trends. | ||
| 1573 | User Story | ANR FPR Reservation System: Pass Usage Report | As FPR Staff, I need the ability to generate a detailed Pass Usage Report, so that I can understand pass use and cost comparison. | ||
| 1574 | User Story | ANR FPR Reservation System: Peak Demand Report | As FPR Staff, I need the ability to generate a detailed Peak Demand Report, so that I can plan for increased demand during holidays and weekends, optimizing staffing and resources. | ||
| 1575 | User Story | ANR FPR Reservation System: Program Attendance and Waitlist Report | As FPR Staff, I need the ability to generate a detailed Program Attendance and Waitlist Report, so that I can optimize program capacity and manage participant expectations. | ||
| 1576 | User Story | ANR FPR Reservation System: Program Enrollment and Rosters Report | As FPR Staff, I need the ability to generate a detailed Program Enrollment and Rosters Report, so that I can manage and track participation in programs. | ||
| 1577 | User Story | ANR FPR Reservation System: Programs Report | As FPR Staff, I need the ability to generate detailed Programs Profitability and Billing Report, so that I can evaluate financial performance and provide accurate billing information to special programs. | ||
| 1578 | User Story | ANR FPR Reservation System: Reservation Activity by Location Report | As FPR Staff, I need the ability to generate a detailed Reservation Activity by Location Report, so that I can view reservation activity across different locations. | ||
| 1579 | User Story | ANR FPR Reservation System: Reservation Booking Channel Report | As FPR Staff, I need the ability to generate a detailed Reservation Booking Channel Report, so that I can assess booking methods. | ||
| 1580 | User Story | ANR FPR Reservation System: Revenue Report | As FPR Staff, I need the ability to generate a detailed Revenue Report, so that I can evaluate all revenue sources and identify trends. | ||
| 1581 | User Story | ANR FPR Reservation System: Revenue Per Room (RevPAR) | As FPR Staff, I need the ability to generate a detailed Revenue Per Room (RevPAR) Report, so that I can view much revenue each available room generated. | ||
| 1582 | User Story | ANR FPR Reservation System: Sales Report | As FPR Staff, I need the ability to generate a detailed Sales Report, so that I can track financial performance and identify revenue opportunities. | ||
| 1583 | User Story | ANR FPR Reservation System: Survey Results Report | As FPR Staff, I need the ability to generate a detailed Survey Results Report, so that I can provide recommendations to improve services and enhance customer satisfaction. | ||
| 1584 | User Story | Camping Attendance and ANR FPR Reservation System: Utilization Report | As FPR Staff, I need to generate a detailed Utilization Report, so that I can assess facility usage and optimize campsite management. | ||
| 1585 | User Story | ANR FPR Reservation System: Visitor Data Report | As FPR Staff, I need the ability to generate a detailed Visitor Data Report, so that I can review arrival and departure dates, length of stay and other visit related data. | ||
| 1586 | User Story | ANR FPR Reservation System: Add Task Type | As FPR Staff, I need the ability to add a new task, so that I can effectively organize my responsibilities. | ||
| 1587 | User Story | ANR FPR Reservation System: Modify Task Type | As FPR Staff, I need the ability to modify a task, so that I can efficiently manage my workload. | ||
| 1588 | User Story | ANR FPR Reservation System: Remove Task Type | As FPR Staff, I need the ability to remove a task, so that my workload responsibilities remain current and accurate. | ||
| 1589 | User Story | ANR FPR Reservation System: Task User | As FPR Staff, I need the ability to assign users to a task, so that I can ensure clear responsibility. | ||
| 1590 | User Story | ANR FPR Reservation System: Task Due Date | As FPR Staff, I need the ability to assign a due date to a task, so that I can ensure timely completion of work. | ||
| 1591 | User Story | ANR FPR Reservation System: Task Reminder | As FPR Staff, I need the system to provide timely notifications for upcoming task deadlines, so that I can ensure all required tasks are completed on time. | ||
| 1592 | User Story | ANR FPR Reservation System: Task Queue | As FPR Staff, I need the ability to view tasks assigned to me, so that I can monitor and balance my workload. | ||
| 1593 | User Story | ANR FPR Reservation System: Task Dashboard | As FPR Staff, I need a comprehensive dashboard, so that I can quickly view outstanding tasks, their assignees, and due dates. | ||
| 1594 | User Story | ANR FPR Reservation System: Manage Tasks | As FPR Staff, I need the ability to manage tasks, so that I can align them with the type of work being tracked and accomplished. | ||
| 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management |
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1595 | User Story | ANR FPR Reservation System: Accessibility Standards | As a Visitor, Group Coordinator, or FPR Staff, I need the system to provide content that complies with accessibility standards, so that I meet the requirements of Section 504 of the Rehabilitation Act and Title II of the ADA, adhering to WCAG 2.1 Levels A and AA | ||
| 1596 | User Story | ANR FPR Reservation System: ADO Requirements Documentation | As FPR Staff, I need the vendor to utilize the State of Vermont ADO instance to document decisions captured during requirements grooming sessions, so that I can ensure stakeholder input and decisions are accurately documented. | ||
| 1597 | User Story | ANR FPR Reservation System: ADO Requirements Traceability Matrix | As FPR Staff, I need the vendor to utilize the State of Vermont ADO instance to manage and trace requirements to test cases, log and track bugs to resolution (RTM), so that I can ensure all project requirements have been validated. | ||
| 1598 | User Story | ANR FPR Reservation System: Barcode Reader | As FPR Staff, I need the ability to use a barcode reader, so that I can track inventory levels and entries efficiently. | ||
| 1599 | User Story | ANR FPR Reservation System: Browser Accessibility and Compatibility | As a Visitor, Group Coordinator or FPR Staff, I need the ability to access the system through all major internet browsers, so that all features and functions are fully supported and operational. | ||
| 1600 | User Story | ANR FPR Reservation System: Compatibility with Current Hardware | As FPR Staff, I need the system to be fully functional with current hardware, so that I can reduce the need to purchase new equipment. | ||
| 1601 | User Story | ANR FPR Reservation System: Configuration Updates | As FPR Staff, I need the ability to make simple configuration changes, so that I can ensure the system remains current and up to date without relying on vendor support. | ||
| 1602 | User Story | ANR FPR Reservation System: Disconnected Mode | As FPR Staff, I need the ability to access the system when disconnected from the internet, so that I can continue to perform essential tasks without interruption in areas with limited connectivity. | ||
| 1603 | User Story | ANR FPR Reservation System: Display Error Messages | As a Visitor, Group Coordinator or FPR Staff, I need the system to display error messages when I enter invalid data, so I can correct my input. | ||
| 1604 | User Story | ANR FPR Reservation System: Duplicate Contacts | As a Visitor, Group Coordinator or FPR Staff, I need the system to prevent duplicate contact entries, so that records retain accurate and reliable data. | ||
| 1605 | User Story | ANR FPR Reservation System: Intuitive User Interface (UI) | As a Visitor, Group Coordinator or FPR Staff, I need the system to provide an intuitive user interface that is easy to navigate and understand, so that I can perform tasks efficiently and reduce the likelihood of errors. | ||
| 1606 | User Story | ANR FPR Reservation System: Legacy Migration Data Cleansing | As FPR Staff, I need the vendor to perform data cleansing and reduce duplicate contacts, so that accurate records are migrated and data integrity improved. | ||
| 1607 | User Story | ANR FPR Reservation System: Legacy Migration Mapping | As FPR Staff, I need legacy data mapped and migrated from Aspira, so that users can access all historical records in the new system. | ||
| 1608 | User Story | ANR FPR Reservation System: Manage Communications | As FPR Staff, I need the ability to maintain all communications, so that I can ensure the information is accurate, up-to-date, and tailored to meet the specific needs of recipients. | ||
| 1609 | User Story | ANR FPR Reservation System: Mobile Devices Accessibility | As a Visitor, Group Coordinator or FPR Staff, I need the system to be fully functional on mobile devices, so that I can access and interact with the system while working in the field or attempting to place a reservation. | ||
| 1610 | User Story | ANR FPR Reservation System: Mobile Sync to System | As FPR Staff, I need my mobile device to sync with the system when connected to the internet and display the last synchronization date and time, so that I can ensure all my data is up to date across devices. | ||
| 1611 | User Story | ANR FPR Reservation System: Overbooking Notification | As FPR Staff, I need the system to alert me when an overbooking is attempted, so that I can prevent scheduling conflicts. | ||
| 1612 | User Story | ANR FPR Reservation System: Password Reset 90-days | As FPR Staff, I need the system to require a password reset every 90-days, so that I am in compliance with State of Vermont security standards. | ||
| 1613 | User Story | ANR FPR Reservation System: Production Support-Phone | As FPR Staff, I need ongoing system support after go-live, so that staff can receive phone support 7-days per week during park operating hours, so that operational issues are resolved quickly. | ||
| 1614 | User Story | ANR FPR Reservation System: Production Support-Tickets | As FPR Staff, I need the ability to submit non-urgent or complex issues through a ticketing system, so that issues are tracked and escalated appropriately. | ||
| 1615 | User Story | ANR FPR Reservation System: Program Files Install | As FPR Staff, I need the system to be installed in the program files with a streamlined process, ensuring default access for all users, so that no device customization is required. | ||
| 1616 | User Story | ANR FPR Reservation System: Required Fields | As a Visitor, Group Coordinator or FPR Staff, I need the system to highlight required fields, so that I am prompted to enter the necessary data to proceed. | ||
| 1617 | User Story | ANR FPR Reservation System: Revision History and Audit Log | As FPR Staff, I need the system to retain a comprehensive revision history and audit log, so that I can track when changes were made and by whom. | ||
| 1618 | User Story | ANR FPR Reservation System: Search Functionality | As FPR Staff, I need the system to provide the ability to search using multiple criteria (e.g., Last Name or Reservation Number), so that I can find specific information that meets my search requirements. | ||
| 1619 | User Story | ANR FPR Reservation System: Security Roles and Permissions | As FPR Staff, I need the ability to define and manage security roles and permissions (security matrix), so that I can ensure users have appropriate access to resources. | ||
| 1620 | User Story | ANR FPR Reservation System: Self-Service Account Recovery (SSAR) | As a Visitor, Group Coordinator or FPR Staff, I need the ability to securely retrieve my user ID and reset my password (SSAR), so that I can regain access to my user account. | ||
| 1621 | User Story | ANR FPR Reservation System: Signature Capture Device | As FPR Staff, I need the ability to use a signature capture device to collect customer signatures, so that I can verify authorized transactions. | ||
| 1622 | User Story | ANR FPR Reservation System: Single Sign-On (SSO) | As FPR Staff, I need the ability to use the State of Vermont single sign-on (SSO), so that I am in compliance with State of Vermont security standards. | ||
| 1623 | User Story | ANR FPR Reservation System: State Document Retention | As FPR Staff, I need the system to retain records pursuant to 1 V.S.A. 315 (Management of public records), so that I can ensure compliance with State of Vermont records retention requirements. | ||
| 1624 | User Story | ANR FPR Reservation System: Test Environment | As FPR Staff, I need access to a regularly updated test environment from the vendor, so that we can train new staff, test modifications, and review enhancements without impacting the production environment. | ||
| 1625 | User Story | ANR FPR Reservation System: Training Sessions | As FPR Staff, I need the vendor to provide comprehensive training sessions, so that end-users can effectively utilize the system and maximize its potential. | ||
| 1626 | User Story | ANR FPR Reservation System: UAT Test Cases | As FPR Staff, I need the vendor to provide comprehensive UAT cases, so that I can ensure the delivered product meets the business requirements and is ready for deployment. | ||
| 1627 | User Story | ANR FPR Reservation System: Unique User ID and Password | As a Visitor, Group Coordinator or FPR Staff, I need the system to allow a unique user ID and password [in accordance with State of Vermont security standards], so that I can ensure secure access to my profile and data based on my security role. | ||
| 1628 | User Story | ANR FPR Reservation System: Upgrades and Enhancements | As FPR Staff, I need the vendor to provide an efficient method for implementing system upgrades and enhancements, so that I can ensure minimal downtime. | ||
| 1629 | User Story | ANR FPR Reservation System: User Guides and Job Aides | As FPR Staff, I need the vendor to provide comprehensive user guides and concise job aides, so that end-users have reliable reference materials to support efficient system use. | ||
| 50 Future Considerations | 50 Future Considerations | 50 Future Considerations | 50 Future Considerations | 50 Future Considerations | 50 Future Considerations |
| State ID# | Work Item Type | Title | Description | Availability? | Vendor Comments |
| 1630 | User Story | ANR FPR Reservation System: Future ACCD Integration | As FPR Staff, I need the system to support future integration with a travel planning platform (e.g., ACCD Trip Planner), so that users can seamlessly plan and manage their trips within the system without needing to use external tools. | ||
| 1631 | User Story | ANR FPR Reservation System: Future Call Center Service | As FPR Staff, I need the system to support future functionality with a call center service, so that we can streamline call handling. | ||
| 1632 | User Story | ANR FPR Reservation System: Future Education Activities and Visitor Programming | As FPR Staff, I need the system to support future functionality for educational activities and visitor programming, so that I can manage events and ensure accessible for participants. | ||
| 1633 | User Story | ANR FPR Reservation System: Future Fish and Wildlife Integration | As FPR Staff, I need the system to support future integration with VT Fish and Wildlife licensing, so that I can align with future regulatory changes and licensing requirements. | ||
| 1634 | User Story | ANR FPR Reservation System: Future Special Use Permits | As FPR Staff, I need the system to support future functionality for managing special use permits, so that I can facilitate events on state-managed lands and trails, collect fees, and ensure compliance with insurance requirements. | ||
| 1635 | User Story | ANR FPR Reservation System: Future Workday Integration | As FPR Staff, I need the system to support future integration with Workday, so that I can streamline HR processes. |
| 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management | 01 Account & Reservation Management |
|---|---|---|---|---|
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1636 | Business Rule | Cabin Type Filter | When a Visitor wishes to make a reservation, cabin filters must include at least the following: 1. Cabin - up to 2 w/electric 2. Cabin - up to 2 w/o electric 3. Cabin - up to 4 w/electric 4. Cabin - up to 4 w/o electric 5. Cabin - up to 6 w/electric 6. Cabin - up to 6 w/o electric Additional cabin types may be included as necessary. | |
| 1637 | Business Rule | Campsite Type Filter | When a Visitor wishes to make a reservation, campsite filters must include at least the following: 1. Tent - small 2. Tent - medium 3. Tent - large 4. Tent ONLY 5. Tent/RV 6. RV - up to 18' 7. RV - up to 24' 8. RV - up to 30' 9. RV - 40' and over 10. Horse site Additional campsite types may be included as necessary. | |
| 1638 | Business Rule | Cancellation Reason | When a Visitor wishes to cancel a reservation, the list of reasons must include at least the following: 1. Plans Changed 2. Found Another Option 3. Unexpected 4. Other a. provide free text 5. Weather Additional cancellation reasons may be included as necessary. | |
| 1639 | Business Rule | Cottage Type Filter | When a Visitor wishes to make a reservation, cottage filters must include at least the following: 1. Cottage - up to 4 w/electric 2. Cottage - up to 4 w/o electric 3. Cottage - up to 6 w/electric 4. Cottage - up to 6 w/oelectric 5. Cottage - up to 8 w/electric 6. Cottage - up to 8 w/o electric Additional cottage types may be included as necessary. | |
| 1640 | Business Rule | Educational & Guided Programs Filter | When a Visitor wishes to make a reservation, program filters must include at least the following: 1. Nature Walk 2. Nature Hike 3. Wildlife Program 4. History & Culture 5. Campfire Program 6. Junior Ranger Program Additional educational and guided programs may be included as necessary. | |
| 1641 | Business Rule | Group Account Demographics | When a Visitor creates a group account online, the list of demographic fields must include at least the following: 1. Group Name 2. Contact First Name 3. Contact Last Name 4. Contact Email Address 5. Contact Phone Number 6. Group Mailing Address Additional group account demographic fields may be included as necessary. | |
| 1642 | Business Rule | Group Day-Entry Sites Filter | When a Group Coordinator wishes to make a reservation, group day-entry filters must include at least the following: 1. Pavilion - Open Air 2. Pavilion - Enclosed Space Additional group day-entry sites may be included as necessary. | |
| 1643 | Business Rule | Individual Account Demographics | When a Visitor creates an individual account online, the list of demographic fields must include at least the following: 1. First Name 2. Last Name 3. Email Address 4. Phone Number 5. Mailing Address 6. State of Residency Additional individual account demographic fields may be included as necessary. | |
| 1644 | Business Rule | Lean-to Type Filter | When a Visitor wishes to make a reservation, lean-to filters must include at least the following: 1. Prime lean-to 1. Standard lean-to 2. CCC (Civilian Conservation Corp) lean-to Additional lean-to types may be included as necessary. | |
| 1645 | Business Rule | List of Amenities Filter | When a Visitor wishes to make a reservation, amenities filter must include at least the following: 1. Walk-in site 2. Drive-thru site 3. Boat-in site 4. Shaded site 5. No Shade site 6. Grass access site 7. Dirt access site 8. Pavement access site 9. Electric 10. Waterfront 11. Sewer 12. Electric/Water 13. Electric/Sewer 14. Water/Sewer 15. Electric/Water/Sewer 16. Fire Ring 17. Fire Pit 18. Pedestal Grill 19. Close Proximity to Bathrooms 20. Close Proximity to Showers 21. Close Proximity to Playground 22. Close Proximity to Water/Beach 23. Close Proximity to Concession Additional amenities may be included as necessary. | |
| 1646 | Business Rule | Lottery System Sites | When FPR Staff wishes to set up sites as part of the lottery system, the list must include at least the following: 1. Stone Hut 2. Burton Island Additional lottery system sites may be included as necessary. | |
| 1647 | Business Rule | Region 1 Filter | When a Visitor wishes to make a reservation, the Vermont State Park Region 1 filter must include at least the following: Region 1: Southeast Region 1. Allis 2. Camp Plymouth 3. Coolidge 4. Fort Dummer 5. Gifford Woods 6. Jamaica 7. Lowell Lake 8. Molly Stark 9. Mt. Ascutney 10. Muckross 11. Quechee 12. Silver Lake 13. Townshend 14. Wilgus Additional parks may be added to Region 1 as necessary. | |
| 1648 | Business Rule | Region 2 Filter | When a Visitor wishes to make a reservation, the Vermont State Park Region 2 filter must include at least the following: Region 2 - Southwest Region 1. Bomoseen 2. Branbury 3. Button Bay 4. D.A.R. 5. Emerald Lake 6. Half Moon Pond 7. Kingsland Bay 8. Mt. Philo 9. Lake Shaftsbury 10. Lake St. Catherine 11. Taconic Mountains Ramble 12. Woodford Additional parks may be added to Region 2 as necessary. | |
| 1649 | Business Rule | Region 3 Filter | When a Visitor wishes to make a reservation, the Vermont State Park Region 3 filter must include at least the following: Region 3 - Northwest Region 1. Alburgh Dunes 2. Burton Island 3. Grand Isle 4. Kill Kare 5. Knight Island 6. Knight Point 7. Lake Carmi 8. Niquette Bay 9. North Hero 10. Sand Bar 11. Underhill 12. Woods Island Additional parks may be added to Region 3 as necessary. | |
| 1650 | Business Rule | Region 4 Filter | When a Visitor wishes to make a reservation, the Vermont State Park Region 4 filter must include at least the following: Region 4 - Northeast Region 1. Big Deer 2. Boulder Beach 3. Brighton 4. Crystal Lake 5. Elmore 6. Green River Reservoir 7. Kettle Pond 8. Little River 9. Maidstone 10. Molly's Falls Pond 11. New Discovery 12. Ricker Pond 13. Seyon Lodge 14. Smugglers' Notch 15. Stillwater 16. Waterbury Center Additional parks may be added to Region 4 as necessary. | |
| 1651 | Business Rule | Reservation Hold Time | When configuring reservation hold time, the amount of time must be set to: A. 15 minutes Hold time may be adjusted when necessary. | |
| 1652 | Business Rule | Reservation Booking Channel | When a Visitor wishes to make a reservation, the booking channels must include at least the following: 1. Call the Park 2. In Person at the Park 3. Online 4. Call Center Additional reservation booking channels may be included as necessary. | |
| 1653 | Business Rule | Reservation Types | When a Visitor wishes to make a reservation, the types of reservations available must include at least the following: 1. Camping 2. Pavilion/Meeting Room 3. Parking 4. Boat Slip/Mooring 5. Ferry Service 6. Gear Delivery 7. Rentals Additional reservation types may be included as necessary. | |
| 1654 | Business Rule | State of Vermont Counties Filter | When a Visitor wishes to make a reservation, the State of Vermont counties filter must include at least the following: 1. Addison County 2. Bennington County 3. Caledonia County 4. Chittenden County 5. Essex County 6. Franklin County 7. Grand Isle County 8. Lamoille County 9. Orange County 10. Orleans County 11. Rutland County 12. Washington County 13. Windham County 14. Windsor County Additional counties may be included as necessary. | |
| 1655 | Business Rule | State of Vermont List of City-Town-Zip Code Filter | When a Visitor wishes to make a reservation, the list of Vermont Cities and Towns by Zip Code filter must include at least the following: 1. Refer to Exhibit E: ANR FPR Reservation System_Vermont Cities and Towns with Zip Code_by COUNTY. Additional State of Vermont Cities, Towns, and/or Zip Codes may be included as necessary. | |
| 1656 | Business Rule | State of Vermont Parks Filter | When a Visitor wishes to make a reservation, the list of Vermont State parks filter must include at least the following: 1. Refer to Exhibit D: ANR FPR Reservation System_Vermont State Parks_by COUNTY by CITY-TOWN by ZIP CODE. Additional State of Vermont parks may be included as necessary. | |
| 1657 | Business Rule | User Account Types | When a Visitor wishes to create an online account, the list of user account types must include at least the following: 1. Individual 2. Group Additional user account types may be included as necessary. | |
| 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services | 02 Parking & Marina Services |
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1658 | Business Rule | Gear Delivery Scheduling Inputs | When a Visitor wishes to schedule gear deliver, the list of inputs must include at least the following: 1. Arrival Gear Delivery Date 2. Arrival Gear Delivery Time 3. Departure Gear Delivery Date 4. Departure Gear Delivery Time Additional gear delivery scheduling inputs may be included as necessary. | |
| 1659 | Business Rule | Gear Delivery Scheduling Parameters | When configuring the gear delivery schedule, the list of parameters must include at least the following: 1. 20 minutes per delivery 2. 2 to 3 deliveries per cart [based on amount of gear per Visitor] Additional gear delivery scheduling parameters may be included as necessary. | |
| 1660 | Business Rule | Boat Slip/Mooring Type Filters | When a Visitor wishes to reserve a boat slip or mooring, the list of types must include at least the following: 1. up to 20ft 2. up to 30ft 3. up to 50ft 4. Mooring Additional boat slip or mooring types may be included as necesaary. | |
| 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight | 03 Inventory & Rental Oversight |
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1661 | Business Rule | Pass Types | When a Visitor wishes to purchase a pass, the list of pass types must include at least the following: 1. Day-Entry Pass 2. Individual Season Pass 3. 10-Visit Punch Pass 4. Vehicle Pass 5. Organizational Pass 6. Organizational Vehicle Pass 7. Student Group 8. Municipal Group Additional pass types may be included as necesaary. | |
| 1662 | Business Rule | Rental Items | When a Visitor wishes to rent an item, the list must include at least the following: 1. Canoe & Paddles 2. Kayak & Paddle 3. Tandem Kayak & Paddles 4. Stand-up Paddle Board & Paddle 5. Peddle Boat 6. Row Boat & Oars 7. Bicycle Additional rental items may be included as necessary. | |
| 1663 | Business Rule | Rental Timeframes | When a Visitor wishes to complete a rental, the list of timeframes must include at least the following: 1. 0.5 hour 2. 1.0 hour 3. 0.5 day [4 hours] 4. 1.0 day [8 hours] Additional rental timeframes may be included as necessary. | |
| 1664 | Business Rule | Individual Season Pass | When purchasing an individual season pass, the following information must be collected: 1. First Name 2. Last Name 3. Mailing Address 4. Phone Number 5. Email Address 6. Primary State of Residency Additional information may be included as necessary. | |
| 1665 | Business Rule | Vehicle Season Pass | When purchasing a vehicle season pass, the following information must be collected: 1. Year 2. Make 3. Model 4. Color 5. License Plate Additional information may be included as necessary. | |
| 1666 | Business Rule | Valid Forms of Entry by Special Program | When a Visitor wants to enter a park with a valid form of entry, the list of valid forms by special program must include at least the following: A. Parks Access Program: 1. EBT Card 2. WIC Card 3. 3SquaresVT Card B. Other Programs: 1. Library Pass 2. Parks Prescription 3. Green Mountain Passport 4. Town Clerk Pass Additional valid forms of entry and/or special programs may be included as necessary. | |
| 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting | 04 Finance & Accounting |
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1667 | Business Rule | Fee Types | When configuring the fee table, the list of fees must include at least the following: 1. Reservation Fee [based on type & size] 2. Rental Fee [based on item] 3. Amenities Fee [based on amenities] 4. Day Use Fee 5. Pet Fee 6. Merchandise Fee [based on type of merchandise] 7. POS Items Fee [based on POS item] 8. NSF Fee 9. Sales & Use Tax 10. Meals & Rooms Tax 11. Local Option Tax 12. Docking Fee [by the foot] 13. Mooring Fee 14. Round-Trip Ferry Fee [Island Runner] 15. Day-Trip Ferry Fee [Island Runner] 16. Pump-Out Fee [boat dock] 17. Dump Station Fee [NOT staying at Park] 18. Group Entry Fee [K-12 School Year ONLY] 19. Municipal Group Fee [up to 25 people, including staff & driver] 20. Municipal Group Add'l 25 Fee 21. Cancellation Fee [Pavilion & Shelter Rentals ONLY] 22. Seyon Lodge-Frequent Flyer Anglers Pass 23. Seyon Lodge-Site Fee [up to 50 people] 24. Seyon Lodge-Site Fee [50-150 people] 25. Reservation Deposit 26. Damage Deposit 27. Monthly Municipal Recreation Group Fee Additional fee types may be included as necessary. | |
| 1668 | Business Rule | Financial Transaction Fields | When configuring financial transactions, the list of fields must include at least the following: 1. Business Unit 2. Account Code 3. Fund Code 4. Department ID 5. Program Code 6. Project Code Additional financial transaction fields may be included as necessary. | |
| 1669 | Business Rule | Fiscal Year | When configuring fiscal year, the timeframe must be set to: A. July 1st - June 30th Fiscal Year dates may be adjusted when necessary. | |
| 1670 | Business Rule | In-person Payment Types | When payments are made in person, the list acceptable forms of payment must include at least the following: 1. Cash 2. Check 3. Debit Card 4. Credit Card Additional forms of payment may be included as necessary. | |
| 1671 | Business Rule | Online Payment Types | When payments are made online, the list acceptable forms of payment must include at least the following: 1. Debit Card 2. ACH/Bank payment (to include routing and account numbers) 3. Credit Card 4. Internal Transfer Additional forms of payment may be included as necessary. | |
| 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload | 05 Reports & Workload |
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1672 | Business Rule | Export Formats | When generating a query for export, the list of export formats must include at least the following: 1. PDF 2. Excel 3. Word 4. CSV Additional query export formats may be included as necessary. | |
| 1673 | Business Rule | Report Filters | When generating a report, the list of filters must include at least the following: 1. Park Location 2. Visitor Ages 3. Residency 3. Reservation Intake Type 4. Site Type 5. Amenities 6. POS Categories 7. POS Items 8. Date Range 9. 1hr Time Increments Additional report filters may be included as necessary. | |
| 1674 | Business Rule | Task Types | When generating a task, the list of types must include at least the following: 1. Follow-up 2. Issue 3. Test Case 4. Cancellation due to No Show Additional task types may be included as necessary. | |
| 1675 | Business Rule | Average Daily Rate (ADR) Report | When generating the Average Daily Rate (ADR) Report, the following formula must be followed: Formula ADR = Total Room Revenue/Number of Rooms Sold Example: Room revenue: $45,000 Rooms sold: 300 ADR = $150 The ADR formula may be adjusted as necessary. | |
| 1676 | Business Rule | Report Recipients | When a report is generated, it must be distributed to at least the following: 1. An individual 2. A distribution list Additional report recipients may be included as necessary. | |
| 1677 | Business Rule | Revenue Per Room (RevPAR) Report | When generating the Revenue Per Room (RevPAR) Report, one of the following formulas must be followed: Formula #1 RevPAR = Total Room Revenue/Total Available Rooms RevPAR = ADR * Occupancy Rate RevPAR Includes unsold rooms Blends pricing + occupancy Rooms available: 400 Room revenue: $45,000 RevPAR = $112.50 Formula #2 ADR: $150 Occupancy: 75% RevPAR = $112.50 The RevPAR formula may be adjusted as necessary. | |
| 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management | 06 System Accessibility & User Management |
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1678 | Business Rule | Mobile Devices | When accessing the system from mobile devices, the list of acceptable devices must include at least the following: 1. iPhone 2. iPad 3. Laptop 4. Tablet Additional devices may be supported as necessary. If these devices are not included, staff will be unable to access the system when in the field. | |
| 50 Future Considerations | 50 Future Considerations | 50 Future Considerations | 50 Future Considerations | 50 Future Considerations |
| State ID# | Work Item Type | Title | Description | Vendor Comments |
| 1679 | Business Rule | Special Use Permit Groups | When requesting a special use permit, the list of groups must include at least the following: 1. Commercial 2. Adventure Race 3. Research Additional special use permit groups may be included as necessary. |
| ID # | Non-Functional Requirement Description | Comply | Vendor's Description of Compliance |
|---|---|---|---|
| H1 | Any technical solution must be hosted in a 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. |
| 01 NFR: Agility | 01 NFR: Agility | 01 NFR: Agility | 01 NFR: Agility |
|---|---|---|---|
| State ID# | Description | Comply | Vendors Description of Compliance |
| 1236 | The solution must test and validate new features and updates before releasing them to the customers using automated tools and processes. | ||
| 1237 | The solution must comply with the relevant laws, regulations, standards, and best practices for data security, privacy, accessibility, and ethics. | ||
| 1238 | The solution must maintain a consistent and coherent user interface and user experience across different devices, browsers, and platforms. | ||
| 1239 | The solution must collaborate with other stakeholders such as developers, testers, customers, users, partners, vendors, etc. using communication and coordination tools and methods. | ||
| 1240 | The solution must evolve and improve continuously by applying agile principles and practices such as iterative development, feedback loops, retrospectives, etc. | ||
| 1241 | The solution must deliver value to the customers and users by solving their problems and meeting their expectations. | ||
| 1242 | The solution must automate repetitive or tedious tasks such as backups, notifications, reports, etc. by using automation tools and scripts. | ||
| 1295 | The system must support integration with the State of Vermont's identity providers (Entra for internal users and Okta for external such as providers) using SAML 2.0 or OpenID Connect, and otherwise in accordance with state protocol. | ||
| 02 NFR: Compatibility | 02 NFR: Compatibility | 02 NFR: Compatibility | 02 NFR: Compatibility |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1250 | Solutions will provide the ability for on-line access by any site connected to the State of Vermont's Network. | ||
| 1251 | The Solution must use normalized data formats for all data transformations. Normalized data formats simplify composition, meaning that it is easier to combine data from different sources. This reduces the number of transformations that are needed, which in turn improves compatibility of the system. | ||
| 1252 | The solution must enable the sharing of particular data with other SOV and local agencies while ensuring the anonymity and complete de-identification of the data. The data must be shared in a controlled manner to ensure that only authorized personnel have access to it. The solution must enable the sharing of particular data with other SOV and local agencies while ensuring the anonymity and complete de-identification of the data. The data must be shared in a controlled manner to ensure that only authorized personnel have access to it. | ||
| 1253 | If the solution is used for TAX information, the solution must comply with IRS Publication 1075. IRS 1075 outlines the security and privacy requirements for protecting FTI, which includes information related to federal taxes, tax returns, and taxpayer information. Compliance with these requirements is mandatory for all systems that store, process, or transmit FTI. Therefore, it is crucial to ensure that the system adheres to the guidelines specified in IRS Publication 1075 to maintain the confidentiality, integrity, and availability of FTI and prevent unauthorized access, disclosure, or use of this sensitive information. | ||
| 1254 | The proposed solutions must allow for the migration of contact and address information from the State's mainframe system to shared application and database systems to ensure its availability. | ||
| 1255 | The solutions to have comprehensive and flexible data source connectivity tools through adapters. The tools must support a range of source types, including non-solution database and legacy databases, packaged applications, web services, semi-structured and unstructured data, and XML structures. This NFR ensures that the system can access and utilize data from different sources, enabling efficient and effective data processing and management. | ||
| 1256 | The solution must provide the capability to perform source to destination file integrity checks for exchange data and alert appropriate parties with issues. | ||
| 1257 | The solutions must verify Social Security Numbers (SSN) using a Federal data source through interface with theVermont Federal HUB when required. | ||
| 1258 | The solution database will have data replication capabilities to external file formats or other RDBM Systems. | ||
| 1259 | The solution database will provide standard data extraction API to allow import and export of data. | ||
| 1260 | Solutions will define what is the level and complexity of data transformations required to support the information exchange needs between applications | ||
| 1261 | Solutions will define what will be the requirement for software in supporting data integration with the enterprise's customers and suppliers | ||
| 1262 | Solutions will adhere to or create common methods and tools for creating, maintaining, and accessing the data shared across the enterprise. | ||
| 1263 | Full refreshes will consist of copying the database and full application code from the source environment to the target environment and making the required configuration changes within the database and application of the target environment. | ||
| 1264 | Partial refreshes will consist of copying of the database and/or part of the application code from the source environment to the target environment and making the required configuration changes within the database and application of the target environment. | ||
| 1265 | Solutions will include data modeling capability that is configurable, customizable, extensible, and upgradable. | ||
| 1266 | Data de-duplication and cleansing will be employed on all mastered subject areas. | ||
| 1267 | Data de-duplication and cleansing will be employed in all application software to minimize the entry of "dirty" data into a target environment or other solutions. | ||
| 1268 | A metadata catalog will be maintained for the enterprise information model. | ||
| 1269 | The software shall support backward compatibility with at least two previous versions of the software, ensuring that users can upgrade without losing any important data or functionality. | ||
| 1270 | The software shall maintain data integrity when transitioning from older versions to newer versions, ensuring that users can access their previous data without any errors or inconsistencies. | ||
| 1271 | The software shall be designed with flexibility to accommodate future changes and updates, ensuring that future versions of the software will be able to function correctly without significant modification. | ||
| 1272 | The software shall support easy data migration from the current version to future versions of the software, ensuring that users can upgrade without losing any important data or functionality | ||
| 1273 | 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. | ||
| 1274 | The software shall be designed with scalability in mind, ensuring that future versions of the software can handle increased workload or data volumes without performance degradation. | ||
| 1275 | The software shall be able to function correctly on multiple hardware and software platforms, such as different operating systems, browsers, and devices. | ||
| 1276 | The software shall provide a high level of configurability, allowing users to customize the software to meet their specific needs and preferences. | ||
| 1277 | The software shall be able to integrate with other software and hardware systems used in the environment in which it operates, such as databases, servers, and other applications. | ||
| 1278 | 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. | ||
| 1279 | Solutions will have a mechanism to share specific data, e.g., limited data sets, detailed data at the level of the individual, but with the data anonymous and completely de-identified in a controllable fashion with other State of Vermont (SOV) and local agencies. | ||
| 1280 | Solutions will build in contingencies for the storage of transactions where there is dependency on availability of data from business partners that provide authoritative data, e.g., the IRS, DHS, and SSA. | ||
| 1281 | Solutions will promote sharing, leverage, and reuse of technologies and systems within and among State of Vermont (SOV). This includes multi-state efforts, availability for reuse, identification of open source, cloud-based, and commercial products, customization, transition and retirement plans. | ||
| 1282 | Solution will define the requirement for all software to support data integration with other systems | ||
| 1283 | Solutions running on shared Infrastructure will support reorganization of database/index/configuration online without the need for the solution to shut down. | ||
| 1284 | Database data exports will contain all data from the State of Vermont (SOV)'s production database(s) or the subset of data specified in the data export request. | ||
| 1288 | If the application records any information also collected by Okta (e.g., First Name, Last Name, Email required; Alternative Email, Phone, or DOB) then the application must source and update that data from Okta at each login unless directed otherwise by the Agency. The application must also provide an endpoint to receive realtime user profile updates should the state decide to push such data to the application. | ||
| 1294 | Salesforce applications must use established state protocol for the Salesforce and Okta integration, including use of OIDC auth providers and the State's common handler code. | ||
| 03 NFR: Maintainability | 03 NFR: Maintainability | 03 NFR: Maintainability | 03 NFR: Maintainability |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1209 | The solution must support automated analysis tools for identifying and reporting on issues such as code quality, security vulnerabilities, and performance bottlenecks. | ||
| 1210 | The solution must support automated testing, with clear and well-defined test cases and test data. | ||
| 1211 | The solution must have clear and well-defined interfaces and APIs for testing and simulation purposes. | ||
| 1212 | The solution must support the use of testing and simulation tools to facilitate unit testing, integration testing, and performance testing. | ||
| 1213 | Solutions will have the capability to track and report usage. | ||
| 1214 | Solutions will have documentation for assisting rule authors and administrators with best practices for rule repository creation and maintenance, repository check-in/checkout, and repository promotion across environments. Solutions will include text documentation and meta-data in the rules repository. | ||
| 1215 | Solutions will have the ability for an administrator to create and maintain retention schedules as defined by VSARA. | ||
| 1216 | Solutions will automatically calculate transfer and destruction dates (and assign records ready for deletion to the appropriate review process for approval of final deletion) for all records in the retention schedules. | ||
| 1217 | Solutions will include a workflow tool to support the records management process. | ||
| 1296 | The solution shall support consistent configuration, integration behavior, and data structures across development, test, and production environments, with environment-specific values externally configurable. | ||
| 1297 | Business rules such as fees, eligibility, seasonality, and reservation constraints shall be configurable without requiring source code changes. | ||
| 1298 | The solution shall support configurable data retention and archival policies in accordance with Agency requirements. | ||
| 04 NFR: Performance Efficiency | 04 NFR: Performance Efficiency | 04 NFR: Performance Efficiency | 04 NFR: Performance Efficiency |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1243 | Server workloads will scale on-demand without shutting down the application to provide continuous scalability. | ||
| 1244 | The Relational Database Management System (RDBMS) must have the ability to support advanced configurations for storing data temporarily in a cache. This includes the ability to support caching on the client or application side as well as on the server side. Caching is a technique used to improve the performance of a system by temporarily storing frequently accessed data in a location that is faster to access than the original data source. | ||
| 1245 | The solution must respond to user requests within 2 seconds under normal load conditions. | ||
| 1246 | The solution must scale up or down automatically based on the demand and traffic patterns. | ||
| 1247 | The solution must have a monitoring and logging mechanism to track and report the performance metrics and errors. | ||
| 1248 | The solution must have a performance testing and tuning mechanism to identify and resolve any performance issues or bottlenecks. | ||
| 1249 | The solution must support multiple browsers and devices with different screen sizes and resolutions. | ||
| 05 NFR: Reliability | 05 NFR: Reliability | 05 NFR: Reliability | 05 NFR: Reliability |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1206 | Solutions will provide the ability to recover from data loss due to end user error and end application error. Recovery includes the following: The ability to recover from data loss: The solutions will be able to restore or recover any data that is lost due to various reasons, such as hardware failure, network outage, human error, or malicious attack. Due to end user error: The solutions will be able to recover from data loss caused by mistakes or errors made by the end users of the solutions, such as deleting or modifying data accidentally or incorrectly. Due to end application error: The solutions will be able to recover from data loss caused by errors or bugs in the end applications that use the solutions, such as crashing, freezing, or corrupting data. (SaaS, PaaS) | ||
| 1207 | The recovery point objective (RPO) will meet State requirements as defined in the Service Level Agreement. | ||
| 1208 | The recovery time objective (RTO) will meet State requirements as defined in the Service Level Agreement. | ||
| 06 NFR: Security | 06 NFR: Security | 06 NFR: Security | 06 NFR: Security |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1285 | When user requests to log in, or requests an authenticated page, they shall be redirected to the State's central login widget (currently at my.vermont.gov) in order to ensure that the user is challenged with state approved authenticators in a state approved user experience. | ||
| 1286 | 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 seperate URLs for internal and external authenthication. 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. | ||
| 1287 | With respect to user attributes required for the application use but not collected from general Okta registration, the Contractor shall ensure portions of the application are secured from users with incomplete profiles. The Contractor may request from ADS that Okta profile enrollment policies are used to capture app specific profile data with Okta, but ADS may decline to store such data within Okta for any internal reason. | ||
| 1289 | Contractor shall make the application session length configurable and set in accordance with agency requirements. | ||
| 1290 | Contractor shall ensure that all logout triggers, which are to be provided to all authenticated external users, are effective at terminating both the app session and the Okta SSO session. | ||
| 1291 | For agencies requiring identity proofing, the application must redirect users with insufficient proofing confirmed on their OIDC claims or SAML attributes, to the state's remote proofing solution at id.vermont.gov or other proofing solution as directed by the State. | ||
| 1292 | 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. | ||
| 1293 | If the application maintains its own user records, it must rely on the Okta alphanumeric unique guide for the subject, also known as a "sub". If a connection with an unknown Okta user is initially made with the Okta username (which is the user's email), the sub must then be used to maintain the connection going forward so as to prevent disruptions in application access if the user changes their email in Okta. | ||
| 1299 | Data center facilities must be located within the United States to comply with jurisdictional regulations. | ||
| 1300 | Solutions handling Federal Tax Information (FTI) or other sensitive data must comply with FedRamp standards to ensure data security and regulatory compliance. | ||
| 1301 | 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. | ||
| 1302 | 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. | ||
| 1303 | Contractor personnel must be authorized by the provider for network and system access across all environments to maintain security and control. | ||
| 1304 | 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. | ||
| 1305 | 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. | ||
| 1306 | 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. | ||
| 1307 | 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. | ||
| 1308 | 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. | ||
| 1309 | 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. | ||
| 1310 | 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. | ||
| 1311 | 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. | ||
| 1312 | Standard network connectivity between the Contractor and the State of Vermont must be established through a hardware VPN provided by the hosting service provider. | ||
| 1313 | 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. | ||
| 1314 | 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. | ||
| 1315 | 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. | ||
| 1316 | 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. | ||
| 1317 | Security and compliance standards for deployment environments must remain consistent whether in production or non-production settings. | ||
| 1318 | 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. | ||
| 1319 | Server instances within deployment environments must be isolated via firewalls based on their application role. | ||
| 1320 | 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. | ||
| 1321 | Access provisioning must be centralized and based on job roles, requiring management approval to ensure appropriate access levels are maintained. | ||
| 1322 | Access to operating systems must require secure login procedures with unique user IDs and strong passwords to protect system integrity. | ||
| 1323 | Root passwords for hosts and facilities must be changed every 30 days to enhance security and prevent unauthorized access. | ||
| 1324 | Employees must maintain confidentiality of state data by signing confidentiality agreements and complying with company policies on the protection of confidential information. | ||
| 1325 | Network controls must protect and control State of Vermont data during transmission, ensuring all connected devices comply with security standards and policies. | ||
| 1326 | 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. | ||
| 1327 | Intrusion Detection Systems (IDS) must provide continuous surveillance to intercept and respond to security events, ensuring timely detection and mitigation of threats. | ||
| 1328 | State of Vermont data must not be stored on removable drives or mediums unless encrypted to safeguard sensitive information. | ||
| 1329 | 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. | ||
| 1330 | 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. | ||
| 1331 | 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. | ||
| 1332 | 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. | ||
| 1333 | The Contractor must provide documented results of the independent third-party production security controls assessment and develop corrective action plans for any deficiencies identified during the assessment. | ||
| 1334 | The Contractor must ensure all modifications necessary 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, are executed in accordance with the terms and conditions of the Contract. | ||
| 1335 | Database passwords must be changed every 180 days to ensure ongoing security and prevent unauthorized access. | ||
| 1336 | 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. | ||
| 1337 | 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. | ||
| 1338 | 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. | ||
| 1339 | Server operating systems must be hardened by eliminating unnecessary services, accounts, and network access rights to enhance security and reduce vulnerabilities. | ||
| 1340 | 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. | ||
| 1341 | 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. | ||
| 1342 | The solution must provide transaction tracking and log consolidation capabilities across the application's data tier to facilitate comprehensive monitoring and analysis. | ||
| 1343 | 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. | ||
| 1344 | Audit records must be protected from unauthorized modifications and require formal approval for any changes to maintain integrity and compliance. | ||
| 1345 | The solution must utilize Single Sign-On (SSO) components for authentication and authorization to streamline user access and enhance security. | ||
| 1346 | The solution must support the protection of Personally Identifiable Information (PII) through encryption or de-identification techniques to safeguard sensitive data. | ||
| 1347 | The Contractor must certify code against OWASP Application Development Security Standards and mitigate risks outlined in CWE/SANS Top 25 Most Dangerous Software Errors. | ||
| 1349 | The Contractor must ensure that the System Security Plan complies with State and Federal laws, rules, regulations, standards, and guidelines to include the following: 1. NIST Publication 800-53 current revision; 2. Federal Information Processing Standard (FIPS) 200; 3. The American Recovery and Reinvestment Act (ARRA); 4. Title XIX of the Social Security Act; 5. Health Insurance Portability and Accountability Act of 1996 (HIPAA); 6. Health Information Technology for Economic and Clinical Health Act (HITECH) of 2009 | ||
| 1350 | 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. | ||
| 1351 | 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. | ||
| 1352 | 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. | ||
| 1353 | The Contractor must ensure all systems undergo Industry Standard security testing (e.g., penetration, physical security, web application, social engineering, and vulnerability tests) prior to go live and 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 State approved 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. | ||
| 1354 | 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. | ||
| 1355 | 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. | ||
| 07 NFR: Transferability | 07 NFR: Transferability | 07 NFR: Transferability | 07 NFR: Transferability |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1199 | Solutions will allow the user to export formatted reports from the system in industry standard formats, e.g., Word, Excel, PDF, and TXT. | ||
| 1200 | Solutions will have a defined data migration strategy or process. | ||
| 1201 | Solutions will provide tooling to support the Extract-Transform-Load (ETL) process that involves: Extracting data from data sources. Transforming to fit business needs (which can include quality levels). - Loading into the target data store. - Caching: The ability to cache federation results and various subsets of the source data to improve performance in situations where source data volumes are large; therefore, retrieving all data required for integration directly from the source is not feasible. | ||
| 1202 | The ability to easily transfer data from one system to another without being required to re-enter data | ||
| 1203 | Web services, including APIs, SOA, REST, and SOAP must not compromise end-to-end system security and adherence. | ||
| 1204 | Solutions will support access from multiple channels and devices. | ||
| 1205 | The solution's interfaces/integrations must continue to operate despite the failure or unavailability of individual technology components, such as an application platform or network connection. | ||
| 08 NFR: Usability | 08 NFR: Usability | 08 NFR: Usability | 08 NFR: Usability |
| State #ID | Description | Comply? | Vendors Description of Compliance |
| 1218 | Solutions will provide the capability to identify and apply a rule change appropriately to existing cases. | ||
| 1219 | Solutions will permit all users (dependent on role-based security and access rights) to have current and up-to-date information regarding a client's information when connected to solutions, given the operational and technical constraints of the data source(s). The data displayed will be time-stamped to reflect the currency of the data. | ||
| 1220 | The State of Vermont (SOV) will access applications through a URL entered in a web browser. | ||
| 1221 | Solutions will provide access to standardized reporting, ad hoc queries, and data visualization. | ||
| 1222 | Solutions will provide the ability to maintain and display the history of each rule change in the rules engine. | ||
| 1223 | If a survey engine is required for the solution, survey engine should provide a user-friendly interface, robust features, and customization options to create, distribute, and analyze surveys effectively. | ||
| 1224 | Solutions will provide index-based search capabilities. | ||
| 1225 | Solutions will provide the capability to access the output of the document management system over the Internet and/or Intranet web sites via web services. | ||
| 1226 | The solution should conform to the web accessibility guidelines specified by the W3C level 2 accessibility guidelines, ensuring that the application is accessible to users with disabilities. The system should meet the standards outlined in the guidelines to provide an inclusive and user-friendly experience for all users, regardless of their abilities. The application should be designed to accommodate a wide range of assistive technologies and should be tested to ensure compliance with accessibility guidelines | ||
| 1227 | Information will be provided to applicants and enrollees in plain language and in a manner that is accessible and timely. Individuals living with disabilities including accessible web sites and the provision of auxiliary aids and services at no cost to the individual in accordance with the Americans with Disabilities Act and sections 504 / 508 of the Rehabilitation Act. Individuals who are limited English proficient through the provision of language services at no cost to the individual, including oral interpretation, written translations. Taglines in non-English languages indicating the availability of language services. | ||
| 1228 | Solutions will provide speech and hearing impaired person with the ability to communicate through a Teletypewriter (TTY) or Telecommunications Display Device (TDD). | ||
| 1229 | Solutions will provide the ability for user to create and customize reports, queries, and dashboards. | ||
| 1230 | Solutions will generate ad-hoc and standard reports in real time, as well as historical for incoming and outgoing contacts. | ||
| 1231 | Solutions will allow for user analytics to be captured and reported. | ||
| 1232 | Solutions will provide support for full text search. | ||
| 1233 | Solutions will enable central workflow alerts and transactional status. Solutions will centralize pending work items for the user as in a work queue. | ||
| 1234 | The system should provide the ability to create, customize and interact with he system should provide the ability to create, customize and interact with multi-dimensional views and tables, enabling users to explore data and gain insights into complex relationships between various dimensions. | ||
| 1235 | Solutions will highlight and flag required and incomplete data fields. |
| 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. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1010 | The Contractor must follow project management methodologies as directed by the State that are consistent with the Project Management Institute's (PMI) Project Management Body of Knowledge (PMBOK) Guide v7 and Agile project management. | ||
| 1011 | The Contractor must use the State-managed SharePoint Online Project Management Repository in accordance with State standards and expectations. | ||
| 1012 | The Contractor must complete the activities specified in the Enterprise Project Management Office (EPMO) Project Lifecycle as published on the EPMO public-facing website. | ||
| 1013 | The Contractor must provide, on a weekly basis, a current project schedule in Microsoft Project format (v2013 or later). | ||
| 1014 | The Contractor must maintain a decision log, risk log, and issue log (in State-approved tools), updated at least weekly, with clear owners and due dates. | ||
| 1015 | The Contractor must actively collaborate with all State-approved Contractors and Subcontractors, sharing information, designs, and schedules necessary to achieve an integrated solution. | ||
| 1016 | The Contractor must participate in State-facilitated cross-vendor forums, and align to shared standards, environments, calendars, and schedules as directed by the State. | ||
| 1017 | If an inter-vendor conflict cannot be resolved collaboratively within five business days, the Contractor must escalate the issue to the State no later than one business day thereafter. | ||
| 1018 | The Contractor must review, provide feedback on, signoff, and conform to the project's State-authored Business Analysis Plan. | ||
| 1019 | The Contractor must follow business analysis methodologies that are consistent with the International Institute for Business Analysis (IIBA) Guide to Business Analysis Body of Knowledge (BABOK) v3. | ||
| 1020 | The Contractor must collaborate with the State to elicit user stories and requirements at sufficient detail to ensure the solution meets the needs of the State. | ||
| 1021 | The Contractor must maintain and manage all requirements, user stories, and business rules in the State's Azure DevOps (ADO) tenet per the direction of the State. | ||
| 1022 | The Contractor must develop and keep current a State-approved Risk Management Plan. | ||
| 1023 | The Contractor must develop and keep current a State-approved Implementation Plan that outlines the approach for the design, development, and implementation of all technology and services in accordance with the solution scope. | ||
| 1024 | The Contractor must, upon Contract execution, participate in the project Steering Committee, which will govern and steer the project. | ||
| 1025 | The Contractor must review, provide feedback on, signoff, and conform to the project's State-authored Change Management Plan. | ||
| 1026 | The Contractor must collaborate with all State-approved Contractors and Subcontractors under the direction of the State Change Control Board to manage change within a multi-Contractor, integrated systems solution as it relates to any system- or non-system-based changes, modifications, or maintenance activities, efforts, tasks, or projects | ||
| 1027 | The Contractor must identify the impact of data source changes to all solution components and capabilities, so that the changes may be verified to be in accordance with the approved Change Management Plan. | ||
| 1028 | The Contractor must monitor and inform the State of industry changes that may have an impact on business processes or on systems covered by the Contract, so that the State can prepare for and implement any necessary updates and stay aligned with industry changes and best practices. | ||
| 1029 | The Contractor must review, provide feedback on, signoff, and conform to the project's State-authored Scope Management Plan. | ||
| 1030 | The Contractor must develop a State-approved Project Kickoff Deck. | ||
| 1031 | The Contractor must review, provide feedback on, signoff, and conform to the project's State-authored Schedule Management Plan. | ||
| 1032 | The Contractor must review, provide feedback on, signoff, and conform to the project's State-authored Deliverables Matrix. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1034 | The Contractor must keep current, on the State's SharePoint site, a Personnel Table of all Contractor staff and Subcontractor staff associated with the project. The Personnel Table must provide: (a) Full name (b) Business phone number (c) Business email address (d) Project role (e) Project responsibilities. | ||
| 1035 | The Contractor must develop and keep current a State-approved Organizational Chart of all Contractor and Subcontractor personnel working on the project. | ||
| 1036 | The Contractor must provide the State with resumes for Contractor and Subcontractor staff working on the project. | ||
| 1037 | The Contractor must ensure vacant positions supporting this Contract are filled within 60 calendar days of date of vacancy or obtain written approval by the State for extended vacancies. | ||
| 1038 | The Contractor must provide the State 20 business days or more advance notice of any plans to change, hire, or reassign personnel supporting this Contract. | ||
| 1039 | The Contractor must notify the State within one business day of the replacement, reassignment, resignation, or termination of any personnel directly supporting this Contract. | ||
| 1040 | The Contractor must replace or reassign personnel supporting this Contract for cause (i.e., where the State can demonstrate a reason) at the State's request. The State shall report to Contractor any concerns regarding Contractor Personnel that may lead the State to make such a request with sufficient detail and time for Contractor to take corrective measures. | ||
| 1041 | The Contractor must conduct an initial criminal background check/investigation on all new hires supporting this Contract as well as conduct follow-up criminal investigations every two years, if requested, for all staff supporting this Contract. The costs for the initial criminal background check must be the responsibility of the Contractor. | ||
| 1042 | The Contractor's staffing solution may include staff located both within the United States as well as outside the United States. | ||
| 1043 | The Contractor must ensure that all licensed Contractor staff maintain current licensure required for their role on the project, with no State or Federal sanctions. | ||
| 1044 | The Contractor must cross train its staff to prevent loss of knowledge and expertise when staff leave, as well as to minimize negative impacts to project timelines due to resource availability. | ||
| 1045 | The Contractor must keep current a State-approved process for immediate removal, with just cause or reason, physical and remote access to systems and facilities for Contractor or Subcontractor employees deemed unfit to continue employment. | ||
| 1046 | The Contractor must develop and keep current a State-approved Resource Management Plan. | ||
| 1047 | The Contractor must bear the costs of changes, hires, or reassignment of Contractor personnel. | ||
| 1048 | The Contractor must develop and apply onboarding and training processes for new staff and turnover in staff. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1050 | The Contractor must develop and keep current a State-approved process for all invoicing activities. | ||
| 1051 | The Contractor must correct and reissue invoices within 10 business days of State notification. | ||
| 1052 | The Contractor must make all Subcontractor agreements available to the State upon request. | ||
| 1053 | The Contractor must be responsible/accountable for all subcontracted work assigned, including responsibility for enforcement and oversight of subcontractors and their compliance with all State and Federal contractual terms/provisions as included within this Contract. | ||
| 1054 | For any Subcontract, the Contractor must identify a designated Subcontractor contact who is accessible to the State. | ||
| 1055 | The Contractor must provide, at no cost to the State, information and data as requested by the State to fulfill requests for litigation, subpoenas, open record requests, or other legal actions. | ||
| 1056 | Upon State request, the Contractor must provide staff and resources to assist the State with preparing and reviewing materials planned to be shared at forum(s), such as national organizations and conferences, on efforts related to this Contract. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1058 | The Contractor must review, provide feedback on, signoff, and conform to the project's State-authored Communication Management Plan. | ||
| 1059 | The Contractor must notify the State of all legislative, executive level, and media inquiries with respect to this project and forward any such inquiries to the State within one business day of the Contractor's awareness of said inquiry. | ||
| 1060 | The Contractor must not respond to legislative, executive level, or media inquiries regarding the project unless directed by the State, except where required by law. | ||
| 1061 | The Contractor must ensure all communications conform to State of Vermont brand standards as issued by the Chief Marketing Office. | ||
| 1062 | The Contractor must ensure that the Contractor's own name, logo, or any reference to the Contractor are not included in any public-facing communications with respect to this project, unless approved by the State. | ||
| 1063 | The Contractor must develop and keep current a State-approved Deliverables Management Plan. | ||
| 1064 | The Contractor must update and maintain all Project Deliverables on a mutually agreed upon cadence as approved by the State. | ||
| 1065 | The Contractor must prepare, update, revise, and submit to the State for approval all operational, systems, or reporting based documentation (in all original forms/media) as they relate to system changes, maintenance, or modification work requests. | ||
| 1066 | The Contractor must create and maintain all system and technical documentation for the solution. | ||
| 1067 | System and technical documentation must utilize State-approved language, diagrams, and structure. | ||
| 1068 | The Contractor must utilize the State-approved Project Management Repository as well as any other State-required document repository to maintain system?related business, technical, and operational documentation. | ||
| 1069 | The Contractor must ensure all documentation is readily available online and electronically maintained, retained, archived, and restored as required by all document and data retention laws, including any applicable litigation hold. | ||
| 1070 | The Contractor must ensure all documentation is prepared and accessible using current State standard/approved software packages. | ||
| 1071 | All project documentation must be reviewed and approved by the State prior to publication. | ||
| 1072 | The Contractor must provide new, routinely maintained, and updated documentation for all contracted functions in accordance with the State?approved documentation development, maintenance, and quality review process. | ||
| 1073 | The Contractor must maintain a documentation standard that aligns with the standards and templates set forth by the State and other contracted Contractors and utilize the approved standard throughout the life of the Contract. | ||
| 1074 | The Contractor must revise any required documentation deliverable if requested to do so by the State. | ||
| 1075 | The Contractor must maintain complete and detailed records of all Contractor-facilitated meetings with the State related to the Contract, software development lifecycle documents, presentations, project artifacts, and any other interaction and post and maintain these artifacts in the Project Management Repository within five business days of the meeting or interaction. | ||
| 1076 | The Contractor must secure State approval prior to any representation or presentation of documentation related to this project, including any local, State, national conferences, or other public or private forums. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1078 | The Contractor must develop and keep current a State-approved Business Design/System Design Document. | ||
| 1079 | The Contractor must create and keep current documentation of all operational, system, and technical processes as they relate to the solution. | ||
| 1080 | The Contractor must develop and keep current a State-approved Interface Control Document that documents all data elements, processes, methodologies, mechanisms, protocols, and other related information for each data source. | ||
| 1081 | The Contractor must document and keep current all conceptual, logical, and physical models for all database service layers and supporting data stores and make the models available online to the State. | ||
| 1082 | The Contractor must store all conceptual, logical, and physical models in a State-approved repository. | ||
| 1083 | The Contractor must complete all conceptual, logical, and physical models to reflect the most current updates or changes based on approval by the State 10 business days prior to implementation of the planned change. Updates must be published to users at the time of implementation. | ||
| 1084 | The Contractor must provide documentation that describes the contents, format, and structure of all databases and the relationships among all database objects. | ||
| 1085 | All user interfaces must comply with the most recent version of Section 508 Standards and WCAG Level A and AA Success Criteria. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1087 | The Contractor must implement, host (or arrange for State-approved third-party hosting), operate, maintain, and manage all infrastructure, including all hardware, software, middleware, and licenses necessary for successful operation of all systems and services under the Contract. | ||
| 1088 | The Contractor must be solely responsible for the end-to-end oversight and management of all environments during implementation and transition, such that performance metrics and service level agreements are met. | ||
| 1089 | The Contractor must retain the responsibility and costs for providing network connectivity and access to all systems and data under their scope to all State-authorized stakeholders. | ||
| 1090 | The Contractor must retain all responsibility and costs for all software, hardware, and infrastructure Maintenance and Operations necessary to fulfill their obligations of this Contract. | ||
| 1091 | The Contractor must collaborate with the State to provide, as a subsidiary plan to the Business Design/System Design Document, an Asset Management Plan that describes the process the Contractor must use to manage applicable technology assets for the duration of the Contract within a multi-Contractor, integrated system-wide enterprise solution. This plan must include: (a) Hardware/software inventory (including location) (b) Procurement information (c) Contract information (d) License management. | ||
| 1092 | The Contractor must provide the base infrastructure and optimization of all systems under the scope of this Contract to meet required application-specific uptime/response time requirements related to performance requirements, deliverable due dates, and Service Level Agreements. | ||
| 1093 | The Contractor must provide reporting of all infrastructure optimizations annually, or after any major system change, to meet or exceed performance requirements or as requested by the State. | ||
| 1094 | The Contractor must document and maintain State-approved application-specific response time requirements, measurements, and reporting. | ||
| 1095 | The Contractor must continuously monitor, track, and report monthly to the State infrastructure space and storage trends over the term of the Contract. | ||
| 1096 | The Contractor must notify the State and present the upgrade/replacement plan within 20 business days of awareness of a software or infrastructure upgrade notice received from a software/infrastructure contractor, unless the change is categorized as an Emergency Upgrade, in which case notification must be given five days prior to the upgrade date. | ||
| 1097 | The Contractor must implement each approved upgrade/replacement plan for all software and infrastructure upgrades in accordance with a State-approved schedule. | ||
| 1098 | The Contractor must provide the tools and infrastructure to support required access to all systems and data under their scope to all State-authorized stakeholders. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1101 | The Contractor must meet the applicable State and Federal privacy and security standards in the hosting and support of all infrastructure, including cloud computing standards for data maintained within the solution. | ||
| 1102 | The Contractor must provide secure access as applicable and appropriate to the development and test environments to a subset of authorized users. Authorization must be by each environment and conform to the security protocols used by the State. | ||
| 1103 | The Contractor must ensure development and test environments have sufficient security controls in place to prevent unauthorized access. | ||
| 1104 | The Contractor must ensure that test environments, aligned with State standards and approval, do not contain mask critical and sensitive data as required for distribution. This includes data classified as Protected Health Information (PHI) and Personally Identifiable Information (PII). | ||
| 1105 | The Contractor must ensure that test environments must adhere to the same level of security compliance for such data as required in a production environment, unless authorized otherwise in writing by the State. | ||
| 1106 | The Contractor must provide appropriate system access and/or a walk-through of any Contractor facilities and operations as directed by the State to facilitate external and internal audits. | ||
| 1108 | The Contractor must provide an independent, third-party security and privacy controls assessment report that covers compliance with NIST SP 800-53 standards and the Open Web Application Security Project Top 10. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1110 | The Contractor must develop and keep current a State-approved Quality Management Plan that is consistent with ISO 9001:2015, Quality Management System (QMS), Total Quality Management (TQM), SSAE18 SOC 2 Type 2, and Continuous Quality Improvement principles and standards. | ||
| 1111 | The Contractor must collaborate with the State and all State-identified Contractors/partners to achieve and maintain quality system and operational services in accordance with State?approved performance metrics and benchmarks. | ||
| 1113 | The Contractor must lead, coordinate, and be responsible for all project quality assurance management, documentation quality assurance, and quality assurance testing meetings as requested and required under the Quality Management Plan and/or by the State. | ||
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
| 1115 | The Contractor must provide adequate and dedicated staff to implement, monitor, and address all quality assurance and improvement activities required under the Quality Management Plan. | ||
| 1116 | The Contractor must take a proactive role in identifying and addressing quality control issues within the solution in the effort to meet or exceed performance benchmarks/metrics for the State. | ||
| 1117 | The Contractor must develop and keep current a State-approved Test Management Plan. | ||
| 1118 | The Contractor must collaborate with other project Contractors to ensure the Test Management Plan establishes test frameworks and test objectives, supporting all Contractors and partners involved in the solution. | ||
| 1119 | The Test Management Plan must comply with ISO/IEC/IEEE 29119-3:2021 standards. | ||
| 1120 | The solution must enable State-approved users to load data into development, testing, training, and other non-production environments. | ||
| 1121 | The Contractor must provide secure access as applicable and appropriate to the development and test environments to a subset of authorized users. | ||
| 1122 | The Contractor must ensure development and test environments enable access to appropriate devices and resources required to connect to the State environment. | ||
| 1123 | The Contractor must implement a User Acceptance Test (UAT) environment so there is a dedicated environment for user acceptance testing activities. | ||
| 1124 | The solution must adhere to established and mutually agreed-upon standards, procedures, and protocols for data loading into non-production environments. | ||
| 1125 | The Contractor must develop, for each system change, a State-approved suite of test cases that includes the test scope, approach, and tools, and is used to complete testing and provide the documented test results to the State. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1126 | The Contractor must provide resources to assist, complete, and submit results, in a State-approved format, of all comprehensive system(s) tests as documented in the State-approved Test Management Plan. | ||
| 1127 | The Contractor must provide sufficient time and resources for all testing performed by the Contractor, and to support testing done by entities other than the Contractor. | ||
| 1128 | The Contractor must ensure that all draft deliverables meet the State's minimum expectations for grammar, spelling, formatting, and overall quality, with revisions made at no additional cost and without impacting the project schedule. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1130 | The Contractor must develop and keep current a State-approved User Training Plan. | ||
| 1131 | The Contractor must develop and keep current a searchable, web-based State-approved User Guide. | ||
| 1132 | The User Guide must be used as part of the basis for user training, unless otherwise specified by the State. | ||
| 1133 | The Contractor must develop and keep current training materials in compliance with Americans with Disabilities Act of 1990 (ADA) standards. Any identified changes to training materials to comply with this requirement must be addressed at no cost to the State. | ||
| 1134 | The Contractor must provide training to the State, its agents, and Successor Contractor(s). | ||
| 1135 | The Contractor must develop and keep current a State-approved Help Desk Plan. | ||
| 1136 | The Contractor must maintain a State-approved help desk support function that enables users to submit requests through a web portal during State business days, 7 a.m. ET to 7 p.m. ET. | ||
| 1137 | The Contractor must maintain a State-approved help desk support function that enables users to submit requests by phone during State business days, 7 a.m. ET to 7 p.m. ET. | ||
| 1138 | The Contractor must provide technical assistance as needed to assist users in researching problems, reviewing production outputs, and understanding report formats. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1140 | The Contractor must develop and keep current a State-approved System Maintenance Support Plan. | ||
| 1141 | The Contractor must provide Maintenance Support activities during certification and transition to the maintenance and operations vendor(s). This includes making changes to existing functionality and features that are necessary to continue proper system and/or operational services. | ||
| 1142 | The Contractor must perform and complete all work necessary to correct and resolve each defect identified in the solution. | ||
| 1143 | The Contractor must utilize Microsoft Azure DevOps, the State-approved online Defect Management tool, for the identification, impact assessment, definition, traceability, verification, and reporting of all defects and resolutions. | ||
| 1144 | The Contractor must conduct development walk-throughs as appropriate to demonstrate to the State that all functions have been completely and accurately planned, developed, and unit tested. | ||
| 1145 | The Contractor must, in coordination with the State, maintain a comprehensive lessons-learned repository in the State's Azure DevOps tenant that is a knowledge base of all lessons learned. | ||
| 1146 | The Contractor must detect, log, notify, and respond appropriately to errors and exceptions in both system and data processing. | ||
| 1147 | The Contractor must collaborate with the source system Contractor to resolve bad or otherwise corrupt data in accordance with the data quality review process timelines. | ||
| 1148 | The Contractor must maintain a data quality review process for the identification and resolution of corrupt or bad data. | ||
| 1149 | The Contractor must develop and keep current a State-approved Release Management Plan. | ||
| 1150 | The Contractor must have the ability to selectively move modifications on a release schedule with State approval, with the flexibility to selectively back out system changes prior to a release (last minute) without significant resources or impact (point in time restore). | ||
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
| 1151 | The Contractor must implement improvements, changes, or enhancements following a State-approved approach that must enable all other environments to update and mirror the production functionality. | ||
| 1152 | The Contractor must provide, as part of the Release Management Plan, a Network Design and Monitoring Plan for an optimally performing computing and data transporting environment. | ||
| 1153 | The Contractor must implement a configuration management process with established promotion and version control procedures for the implementation of a multi-Contractor, integrated system-wide enterprise. | ||
| 1154 | The Contractor must maintain, as part of the Release Management Plan, change management metadata regarding all system application release and operational performance and behavior. | ||
| 1155 | The Contractor must provide a quarterly Configuration Management Summary report providing a high-level overview of any changes to the system baseline configuration and operational usage. | ||
| 1156 | The Contractor must document and maintain State-approved standard maintenance windows for system maintenance and downtime that are coordinated across solutions and minimize stakeholder disruption. | ||
| 1157 | The Contractor must obtain State approval before initiating scheduled and emergency maintenance windows and system outages. | ||
| 1158 | The Contractor must document all incidents in accordance with the State standard Incident Reporting Form template. | ||
| 1159 | The Contractor must notify affected State stakeholders of scheduled and emergency maintenance windows and system outages. | ||
| 1160 | The Contractor must develop and keep current a State-approved Performance Management Plan. | ||
| 1161 | The Contractor must allow a State representative to participate in any Contractor-facilitated user group that is associated with any part of the solution. | ||
| 1162 | The Contractor must develop and keep current a State-approved Operating Procedures Guide. | ||
| 1163 | The solution must include exception handling mechanisms to facilitate error correction and/or auditing across all components of the solution without impacting concurrent, overall operations, as well as reporting of exceptions to the State. | ||
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
| 1164 | The Contractor must transcribe the lessons-learned repository to a lessons-learned report within 60 business days after the project is completed. |
| Requirement Description | Comply (Y/N) | Vendor's Description of Compliance | |
|---|---|---|---|
| 1166 | The Contractor must develop and keep current a State-approved Business Continuity, Cyber Incident Response, and Disaster Recovery (BC/DR/CIR) Plan. | ||
| 1167 | The Contractor must ensure the Business Continuity/Disaster Recovery/Cyber Incident Response Plan: (a) provides a framework for reconstructing vital operations to ensure the safety of employees (b) provides for the resumption of time sensitive operations and services in the event of an emergency (c) provides for initial and ongoing notification procedures (d) complies with all NIST CP-2, NIST 800-61, and IR-8, NIST-800-53 standards (e) complies with the latest version of ARC-AMPE standards. | ||
| 1168 | The Contractor must ensure the Business Continuity/Disaster Recovery/Cyber Incident Response Plan's operational and system functions, including systems and operations under the scope of Subcontractors, adhere to Health Insurance Portability and Accountability Act and National Institute of Standards and Technology standards. | ||
| 1169 | The Contractor must provide an up-to-date copy of the Business Continuity/Disaster Recovery/Cyber Incident Response Plan in a secure, highly accessible, centralized online location and at an offsite location approved by the State. | ||
| 1170 | The Contractor must submit the Business Continuity, Cyber Incident Response, and Disaster Recovery Plan annually or more frequently as directed by the State, such as after a major system change that materially affects the plan. | ||
| 1171 | The Contractor must perform annual Business Continuity, Disaster Recovery, and Cyber Incident Response exercises, including pre-go-live activities. | ||
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
| 1172 | Business Continuity (BC), Disaster Recovery (DR), and Cyber Incident Response (CIR) exercises must include activities selected from the BC/DR/CIR Plans to verify the viability of each plan in accordance with NIST CP-4 and IR-8 standards. | ||
| 1173 | The Contractor must perform Business Continuity, Disaster Recovery, and Cyber Incident Response exercises after major system changes as required by the State. | ||
| 1174 | The Contractor must document all Business Continuity, Disaster Recovery, and Cyber Incident Response activities and report to the State instances where appropriately trained personnel were unable to complete the necessary recovery procedures. | ||
| 1175 | The Contractor must adjust contingency and training plans to correct deficiencies identified through Business Continuity, Disaster Recovery, and Cyber Incident Response exercises and present updates to the State for approval. | ||
| 1176 | The Contractor must provide annual test reports to the State within 10 business days of exercise, Business Continuity (BC)/Disaster Recovery (DR) and Cyber Incident Response (CIR) Plan reports within one business day of incident, and BC/DR/CIR Plan updates within one business day of identified deficiency. | ||
| 1177 | The Contractor must evaluate systems and business processes in collaboration with the State for criticality and necessity to determine appropriate return to operations time frames during development of both the initial and ongoing Business Continuity/Disaster Recovery/Cyber Incident Response Plans. | ||
| 1178 | The Contractor must update key personnel contact information as it relates to the Business Continuity/Disaster Recovery/Cyber Incident Response Plans within one business day of notification of the change. | ||
| 1179 | The Contractor must implement a State-approved alert process to handle system-related issues, including notifying State-identified contacts in accordance with the Business Continuity/Disaster Recovery/Cyber Incident Response Plans. | ||
| 1180 | The Contractor must review any new applicable Contractor provided business processes, including systems and operations under the scope of Subcontractors, for impact on mission critical functionality and update Business Continuity/Disaster Recovery/Cyber Incident Response Plans prior to new business process implementation. | ||
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
| 1181 | The Contractor must ensure that personnel who are responsible for systems recovery and cyber incident response are trained in accordance with NIST Publication 800-53 current revision and latest version of ARC-AMPE standards and tested in their ability to execute the contingency and incident response procedures. | ||
| 1182 | The Contractor must provide for backup capabilities at a geographically separate remote site(s) from the Contractor's primary site(s) in accordance with the standards set forth in the Business Continuity/Disaster Recovery/Cyber Incident Response Plans. System and data backup and recovery points must be mutually agreed upon between the Contractor and the State. | ||
| 1183 | The Contractor must provide a backup and recovery/failover system(s) in compliance with State and Federal rules and regulations to ensure full backup. | ||
| 1184 | Backup and Recovery Services must be in place for Production Environment and Non-Production Environments. | ||
| 1185 | The solution must ensure that all backups are immutable (unchangeable). | ||
| 1186 | The solution must employ backup strategies that include air gap measures. | ||
| 1197 | In coordination with the State, the Contractor must provide training to Contractor staff and State-identified stakeholders on the execution of the Business Continuity/Disaster Recovery/Cyber Incident Response Plans a minimum of 20 business days prior to implementation of the Contractor's module components, with the implementation of major changes, and annually thereafter. |
| State ID | Requirement Description | Comply (Y/N) | Vendor's Description of Compliance |
|---|---|---|---|
| 1189 | The Contractor must transition and train, as requested and negotiated, any or all infrastructure responsibilities necessary to fulfill the Contractor's contractual obligations to the State or another party upon notification from the State. This includes but is not limited to transference of: The Cloud Service Provider's (CSP) member accounts using the appropriate mechanisms; Complete system inventory for all Contractor services; Contractor cloud boundary access control policies; Network ACLs; Security Groups; Roles; Users; 2FA/Multi-Factor Authentication tooling; Infrastructure as Code programs and scripts; Security and compliance monitoring tools and processes; Audit logs; System monitoring; SIEM tooling and logs; Vulnerability Management; Plan of Action and Milestones; Compliance scans; Data backups; Configuration Management Database items; Disaster Recovery fail-over and recovery routines. |
| 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 | $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 | $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, 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: |

With GovernmentContracts, you can:
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