Skip to main contentPsst! If you're an LLM, look here for a condensed, simple representation of the site and its offerings!

LiveFree Webinar — Wednesday, December 9 at 2:00 PM ET

Register Free →

This Solicitation opportunity from Alabama was posted on December 19, 2025. The submission period has ended. Browse the details below for market research, or find similar active opportunities.

Pest Mgmt USA Plants Database 324676

Closed
SRC0000032493State & Local

Contract Overview

Solicitation details, issuing organization, response deadlines, documents, and interested companies for this government contract opportunity.

Active Opportunities Like This One

AI Contract Overview

Show more

The Alabama Department of Agriculture is soliciting quotes for software support, maintenance, and hosting services for its Pest Management USA Plants Database system, located in Montgomery, Alabama. The contract focuses on the vendor's ongoing responsibility to maintain the existing software application with all current features, including modifications triggered by approved service requests to add functionality or fix issues. The vendor is accountable for remedying any defects or bugs introduced during maintenance but will not be liable for pre-existing issues, which will be treated as enhancements subject to change orders. Maintenance services encompass a broad range of activities such as issue investigation, code changes, research, interfacing with third parties, and participation in meetings. The vendor must follow a structured release management process, delivering one standard annual release plus up to two hot fixes as needed, supported by thorough testing, quality assurance, regression testing, user acceptance testing, and detailed release notes. Support is provided through a dedicated service desk available during business hours, offering Level 2 and 3 technical assistance, while the client provides first-level user support. The vendor is required to track all support hours and incidents, categorizing and reporting them regularly to ensure transparency and accountability. The agreement includes a structured escalation procedure, prioritizes resolution timelines based on issue severity, and mandates coordination between vendor product management and the Department to align on release scheduling and feature prioritization. Client responsibilities include designating points of contact, providing remote access if hosting is client-based, and assisting in issue resolution. Additionally, the vendor’s product management services feature bi-monthly meetings and collaboration with user groups to guide ongoing product enhancements and training, ensuring a comprehensive approach to software lifecycle support and continuous improvement.

General Info

Alabama Agriculture requires vendor for Pest Management software support, maintenance, hosting, and upgrades.

Agency

Place of Performance

Montgomery, AL, 36107, USA

Set-Aside

NONE

Documents

1
PDF, High priority: read this firstrfq
High

Read the document

Every page of every file, in your free workspace.

Read the document

AI Contract Breakdown

Uniform Contract Format

Sign up to view the full breakdown with detailed analysis of each section.

View Full Breakdown

This one is closed. Find the next one like it.

Open contracts like this one, right now:

  • Post Quantum Cryptography (PQC) Readiness and Validation StatusOpen now, due in 18 days
  • Microfocus Software Extended SupportOpen now, due in 15 days
See open contracts like this

Ask CLEATUS

I've read this contract. Ask me anything.

Timeline

PhaseClosed
Posted

Solicitation

Response Deadline

Deadline has passed

Submission Closed

Find active opportunities like this

Get full access to discover similar active contracts, track opportunities, and build proposals with AI assistance.

Organization & Contact Information

Show more
AgencyAlabama
ContactsNo contacts available
OfficeN/A
Organization / AgencyAlabama
Office AddressN/A
ContactsNo contact information available

Full Description

Show more
The Alabama Department of Agriculture Pesticide Management is seeking a quote for Software support, maintenance, and hosting, 1445 Federal Drive Montgomery, AL 36107.  Please see attached documents for full descrption of specifications for DatabaseSoftware MaintenanceVendor must maintain software application all features either wanted or unwanted are the current set of features of the Database software application system.  Software Maintenance is defined as the modification of a software product after delivery to implement approved service requests for either new functionality or to fix a current unwanted feature.  Warranty services solely provide for resolution of any problems, defects, and/or deficiencies introduced by vendor in the process of software maintenance that have been reported with in the current contract where the intended results do not meet the documented and agreed upon specifications of the service request. The following elements reflect items that are supplied as part of Software Maintenance and Support:What constitutes the use of maintenance hours? Any request submitted to the serve desk for investigation, requested code change, requested research, emailed question with required response, 3rd party interfaces resulting in errors not created by vendor, request for participation of meetings, request for discussions with a 3rd party for integration.   Break-Fix Under this Statement of Work (SOW), vendor will provide services to modify the Database software to remedy an unwanted feature or implement approved service requests.  Vendor does not take on liability from the previous vendor’s code.  If vendor introduce a bug or break-fix error to the system vendor will remedy the issue.  Existing bug within the code not introduced by vendor are considered features of the current system and will be considered a change order/enhancement.  Quality Assurance Process & Testing Vender will test each major and minor release prior to delivery to the client in accordance with technical and business specifications agreed upon for the release, perform regression testing to validate that the new functionality has not negatively impacted existing functionality within the product, and provide the release for User Acceptance Testing (UAT).  Release Deployment Vendor will work with the business area to provide a maintenance release schedule that will include agreed-upon change requests in a structured process: Standard releases:  Vendor will provide 1 standard release annually; in addition to up to 2 as needed “Hot Fix “during the service period if the issue is related to a customer facing issue or required financial requirement. Emergency release: Vendor will exercise all commercially reasonable efforts to test such emergency fixes in accordance with the requirements of this section. 
Vendor also will deliver or make available to the client, with the delivery of each release, detailed release notes describing the release content.  Release Management Vendor needs to have a Release Management process provides customer support, improved planning, and testing. This standardized approach to software delivery management provides for full quality assurance, communication, and consistency in versioning.  Items to be included in a release are prioritized between our Product Management team and Alabama Department of Agriculture.  Vendor will work with the client to develop a maintenance release schedule, which will include agreed-upon change requests in a structured process.Vendor will provide support, as defined in this agreement, for the current major production release of the software and the current major production release – 1.  Customers who choose to remain on older production release versions may be charged additional costs/hours for the added work effort in supporting older versions.Product ManagementVendor will provide product management to assist in coordination of support activities.  As part of our maintenance service, our Product Manager, a subject matter expert in USAPLANTS will provide: Bimonthly (every other month) meeting to discuss the operations of USAPLANTS that focuses on: Current support/training hour usage Discussion of any new feature sets (enhancements) for changes that can be prioritized in a product release listing and product roadmap per a separate SOW Shared discussion on other client activities or enhancement requests for prioritization Discussion on internal infrastructure changes
Coordinating with the client POC for prioritization and release dates of future releases
Product Management further includes: Providing information on enhancements or customizations made by other clients at no additional charge unless additional configurations are required to enable the functionality. Supporting User Group administration and meetings lead by the license holder of the software. Reviewing requested feature sets for prioritization across clients to be able to address high priority items as quickly as possible Assisting the user community in coordinating requirements, including potential cost sharing across clients User group conferences and user workshop coordination which is led by the License Holder.
Client Responsibilities: This section describes the responsibilities of the Alabama Department of Agriculture under this agreement. Designated Support Contacts
The client will designate one (1) single point of contact (POC) with an optional backup.  The POC is responsible for coordinating with Vendor POC for prioritization and release dates of maintenance items as well as reporting and management of incidents.The client will designate one (1) or more product administrators to serve as the primary client contact for Vendor Support and Maintenance Services.  User Support
The client will provide end-user first-level support.  Vendor will need to provide and be responsible for Level 2 and 3 support of the product. Backups and Procedures
For products hosted by the client, the client will be responsible for maintaining staging and production environments and for performing all necessary back-ups, database monitoring and tuning, recovery, and required product operating procedures.  If Vendor does not provide Production hosting for the solution, the State will be required to host their own staging environment.  For products hosted by Vendor. Vendor will perform these tasks. Remote Access
For products hosted by the client, the client will provide vendor remote access to the servers on which the product resides.  For products hosted by Vendor as an outsourced hosting service, the client will not have direct access, e.g., via virtual private network (VPN), to any of the hosted servers. Client Assistance in Resolving Unwanted Features
The client will provide such assistance and cooperate with vendor in helping to identify and address unwanted features.  Client delays in providing assistance affecting the total elapsed time of the maintenance task(s) related to the request may result in delayed completion of the task, charge of additional maintenance hours, or both.When providing a detailed description of the issue you are experiencing, please remember to include such items and details as:  
Username experiencing the issue. Identify what you expected to happen vs what happened. Document steps to reproduce issue. Identify the module/page - menu item selected to get to the page/report Parameters/data values populated, button clicked, etc. If any error message is displayed, please copy/include in the report. Finally, be sure to select the appropriate Priority and click the Submit button.

   Support and Problem Resolution Agreement Support and Problem Resolution The Vendor Service Desk provides a single Point of Contact (PoC) for issue tracking and resolution for the Level 2 and Level 3 support requests.  Vendor provides SMEs on the USAPLANTS solution in conjunction with our Service Desk team to ensure a timely incident response and resolution to any issues or needs identified.  Our Service Desk is available 8:00 a.m. to 6:00 p.m. Eastern Time on business workdays.  Timeframes outside of these normal business hours are negotiable. Support Process This agreement includes hours of support indicated on page 2; these allocated hours of support will expire the end of the contract term.  Support hours include issue resolution for items outside of software maintenance (i.e., data fixes), meetings to discuss software changes outside of Product Management monthly meetings, and enhancements or code changes, such as cosmetic changes on a report. Training includes webinars, continuing education training, and additional meetings to educate staff at the client request.  Hours can be purchased should a client need additional support/training assistance.  Support hours can be used for maintenance, enhancements and training. Support and Maintenance Services History Tracking System Vendor will maintain a customer- specific Support and Maintenance Services history, including updated records of the client’s product configuration.  Vendor creating a transparent relationship and will log all support hours and classify them in the monthly statement: the date, time, title and time spent on each contact to support desk the total number of contracted hours, total used and remaining hours available.
Reporting and Management of Incidents Reports of incidents (an "Incident Report") will be made by the client to the Vendor Service Desk.  If there are multiple Incidents, the client will prioritize their incidents with respect to each other.  The Service Desk will log the reported incident and provide the client with an Incident tracking number for reference when making follow-up inquiries.The Incident Report will contain: the date and time of the call the name of the product the client contact name, e-mail address if available, and telephone number a description of the incident
The client will provide vendor with as much information as possible to enable vendor to investigate and attempt to identify and verify the reported issue or defect.  The client will work with vendor support personnel during the problem isolation process, as reasonably needed.  Vendor will manage and maintain records with respect to the resolution of all reported Incidents ("Incident Resolution Report") and may facilitate status calls for ‘High Impact’ or ‘Work Stoppage’ classifications. Vendor will maintain the working history of Incident Reports and provide the client with expected resolution dates, and – for unwanted features – a status of where the update is in the Vendor release and quality assurance process.   Vendor must have a Quality Assurance Process includes: Test Case Development – These cases are derived directly from the business.  Test cases cover both positive and negative test scenarios. System Integration Testing (SIT) – The objective of SIT is to verify the correctness of the newly designed items, and their interaction with the other functional areas of the system.  Testing focuses on new or altered functionality of application. System Acceptance Testing (SAT) – The goal of SAT is to logically combine all the key components described in the integration section of this document in strategic end-to-end testing flows to validate that core functionality is processing correctly. Regression Testing – Regression Testing is done to confirm that a recent program or code change has not adversely affected existing production features.  Regression Testing is a full or partial selection of previously executed test cases which are re-executed to ensure existing functionalities work to specification. Test Results Reports  vendor will prepare reports documenting testing efforts as well as any known issues prior to handing over the release for UAT. User Acceptance Testing (UAT) – vendor will provide initial test cases, test monitoring and defect tracking during the UAT test period as well as correct critical defects that are related to the agreement’s business and technical specifications and will deliver each release to the client only after such release has been approved by the client. 
The following terms relating to Incidents and Defects are defined as follows: Unwanted Feature: Any non-conformance of the Product to operate in accordance with the Documentation, or the Product to operate in accordance with the Performance Standards that currently exists in the application. Defect: Any non-conformance of the Product to operate in accordance with the Documentation, or the Product to operate in accordance with the Performance Standards that was introduced by features created by vendor. Emergency Release: Corrections to a small number of known errors used to remediate a Major Incident and/or a potential security breach that might cause a Major Incident.  Vend Inspection Services will follow the Emergency Change procedure and ensuing Emergency Release procedure to implement an Emergency Release for the impacted Customers. Incident: An unplanned interruption to an IT Service or a reduction in the Quality of an IT Service.  Failure of a Configuration Item that has not yet impacted Service is also an Incident. Incident Response: A email, and/or update from the Vendor Service Desk or telephone call from Vendor acknowledging that an Incident Report has been received and that appropriate technical personnel have been assigned to work on the Incident. Interim Resolution: Vendor: (a) reinitiates or restarts, as applicable, the product, if the reported Defect caused the product to be inoperative; (b) enables the client to access the product, as applicable, if the reported Defect caused the client to be unable to access the product; or (c) provides the client with a workaround acceptable to the client that solves or mitigates a reported Defect. Issue: Any of the following: (a) any presently identified event, circumstance, or problem that adversely affects the ability to meet project requirements, or a missed Deliverable Due Date or Critical Milestone Due Date, whether by Vendoror the client; or (b) any event, problem, difficulty, or circumstance which affects or may affect the Product or the operation of the Product by the client, including the failure to meet the Performance Standards.  Issues do not include unwanted features (see definition of Unwanted Features). Major Release: Contains large areas of new functionality, some of which may eliminate temporary fixes to problems.  A major release usually supersedes all preceding minor releases and emergency releases. Vendor Inspections Services must push a full (as opposed to partial) set of software components to the appropriate customer environment. Minor Release: Contains small enhancements and fixes, some of which may have already been issued as an emergency release.  A minor release usually supersedes all preceding emergency releases.  Release and Deployment Management will determine the frequency of minor releases.  Minor releases will be deployed as follows:
Full Release: Vendor Inspections Service must push a full set of software components to the appropriate customer environment.  The software will incorporate all changed components from prior releases. Partial Release: The Release and Deployment Management Process will define criteria for a partial Minor Release for CI items.
Resolution: A correction or modification that permanently corrects the unwanted features or Defect, or for non-Defect-based Incidents, a permanent product that ensures the Incident will not be repeated. Service Request: A request from a user for information, or advice, or for a Standard Change or for Access to an IT Service. Work Stoppage: Defined as an unwanted feature or defect that directly impacts the daily operation of the business and provides no suitable work around.
Appendix C: Service Level Agreement Resolution Times The service is available 8:00 a.m. to 6:00 p.m. Eastern Time on Federal business days, unless stated otherwise in the contract.  Vendorwill respond within the timeframe noted in Figure 2.  “Medium” and “Low” severity reported system defects and product deficiencies will be prioritized and corrected in a future product release.   Time to:Level of SeverityDescriptionAcknowledgeResolution plan 1. High ImpactSoftware does not execute1 hour4 hours2. Medium ImpactSoftware execution is significantly restricted or severely impaired1 business day3. Low ImpactSoftware executes with minor errors5 business days Issue Resolution Plan Client support is initially handled by Vendor Service Desk which will provide responsive and professional service for less complex support and will quickly transfer complex support needs to Vendor’s Product SMEs.  Vendor logs and tracks all problem contacts through resolution.  Monthly reports to each licensee provide details on all calls and use of support time.Technical support will be offered by telephone, email, and/or direct viewing of the production environment or mobile device. Vendor requires direct access to client infrastructure (e.g., VPN) in order to execute this service agreement.  Device-level support is optionally available via GoToAssist.As part of the Vendor release management process, items will be prioritized between our Product Management team and the Alabama Department of Agriculture.  Vendor will provide aging reports to review older support requests/bugs to ensure these items are being addressed as appropriate based on priority.  All issues are reviewed prior to each minor release and targeted for a future release based on priority.Vendor goal is to resolve all priority 1 items not considered for an emergency release in the next available minor release.  Priority 2 items will be scheduled within the next two maintenance releases after submission to vendor.  Any modifications to source code will follow standard release management for the specific product.If you are impacted by a High Priority issue the process is to email the support desk, followed by a phone call to the Support Desk.  If you do not reach a support desk specialist then please call designated  employee vendor provides. Escalation Procedures Vendor must have an escalation process:The escalation path that is followed if the Alabama Department of Agriculture     escalates service requests and defects for which an Interim Resolution has not been provided and/or has not been addressed in a timely or appropriate manner.  The client has the right to require Vendor to assign an appropriate support and/or technical resource from Vendor to coordinate and oversee resolution of such defect or request.  In this case, resolution efforts will be communicated through daily calls.  If these escalation procedures fail to produce a satisfactory resolution, the Executive Sponsors will discuss a corrective action plan to resolve the timeliness of correcting defects or requests.Escalation LevelContact DetailsLv. 1   Supplier Part Number Requirement on Quick Quotes:The standard solicitation submission requirement to provide a “Supplier Part Number” has been removed.  This information may still be necessary for certain Quick Quotes. If required, agencies shall include the following term and condition to clearly indicate to suppliers that part number(s) for each item are necessary.                Model/Part Number and Descriptive literature:The brands and model numbers referenced provide a level of quality, and unless otherwise specified, are not restrictive. Suppliers quoting alternate items must provide a complete model/part number as well as descriptive/technical literature for consideration and evaluation with their quote. Reference to literature with a previous solicitation will not satisfy this requirement.  Failure to provide the required literature may result in the rejection of the supplier’s response.

Get AI-powered intelligence on the opportunities still open

Every solicitation package arrives shredded into a compliance breakdown and matched to your past performance, with incumbent history and alerts on amendments and award.

Miguel
Hillary
Keith Deutsch
Christine

Join 900+ contractors already using CLEATUS