DOI RFP: Customer Relationship Management of Limited-use Hunting and Fishing Opportunities

Notice ID 140F0921R0009

“The U.S. Fish and Wildlife Service (FWS) is seeking a vendor to support the first phase of migrating upwards of 118  field stations to a Software as a Service (SaaS) platform application that

  • supports a wide range of features to manage limited-hunting opportunities on national wildlife refuges and fish hatcheries. Field station use cases range from simple reservation options to more complicated lottery deployment, and integrate with pay.gov.
  • Is FedRAMP in-process or willing to become Tailored Moderate Impact-SaaS authorized under FWS Agency sponsorship (FedRAMP Readiness Documentation)

As part of this first phase, the vendor will work with FWS to ensure Fed-Ramp compliance, conduct discovery to analyze field station needs, created a migration plan for stations with varying business rules into the new platform, on-board a pilot group of stations (10-40) to the platform. For the pilot group the vendor will provide all aspects of information technology, customer support, and fee management…”

“Requirements and Performance Objectives

The proposed SaaS must support multiple workflows, user management, hosting, access, security, platform administration and fee management to manage a limited-use hunting and fishing opportunities on FWS public lands and waters.  This SaaS is hereafter referred to as the ‘Platform’.

The Contractor must meet all federal contracting and information system regulations aligned with the project.

Contractor proposals should include:

  1. An overview of how the proposed Platform meets functional user requirements detailed below.
  2. At least three references from clients with similar use cases.
  3. An overview of how internal and external customer support will be addressed during normal business hours and weekends commonly when permits and licensing features are active.
  4. All the necessary documentation to ensure the Platform meets the non-functional user requirements described below.
  5. Price for migration and on-boarding of 30 field stations with varying business rules on to fed-ramp ready platform. A proposed per user, transaction or annual per field station cost-structure for on-going use of the Platform.
  6. Functional User Requirements
  7. Provide a web browser SaaS platform where administrators can customize and manage their dashboard based upon their individual and/or group login and role credentials. Applicants can link, apply, and view their license, permit, lottery, registration status from either their desktop/laptop or mobile device.
  8. Set workflows that address the majority of field station limited use draws, lotteries, and first-come serve hunting opportunities.
  9. User-friendly public experience that addresses opportunity availability, applicant eligibility, automatic notifications, electronic permit downloads, multiple applications, and easy payment processing.
  10. User-friendly administrator experience that allows user to query permit availability, adjust quotas, manage public users, track fee collection, and run local and national reports.
  11. Integration with Pay.gov.
  12. Leverages existing FWS GIS web services and other internal data sources for species and hunt unit data.
  13. An application programming interface (API) that makes these opportunities available to other systems including the FWS website and Recreation.gov.
  14. The Platform shall use responsive design principals such that it is accessible from a variety of devices including mobile phones.
  15. Non-functional User Requirements

1) Customer Experience
The Contractor will describe methods used to measure usage and customer experience to ensure both internal and external customers’ needs are met.

2) Service Level Agreements (SLAs)
The Contractor shall identify the hosting location(s) and provide documentation at the time of solicitation that describes the system architecture and infrastructure to meet the SLA’s for system availability, backup, redundancy, accessibility, and cyber security assurances…”

‘E. Projected Contract Structure
The period of the contract will be effective for 12 months from date of award, unless terminated earlier…’

Read more here.

0
Tags:

This topic contains 0 replies, has 1 voice, and was last updated by  Jackie Gilbert 1 week, 6 days ago.

  • Author
    Posts
  • #136804

    Replies viewable by members only

    0

You must be logged in to reply to this topic.

CONTACT US

Questions?. Send us an email and we'll get back to you, asap.

Sending

©2021 MileMarker10, LLC all rights reserved | Community and Member Guidelines | Privacy Policy | About G2Xchange FedCiv

Opportunities. Starting Points.

About our Data

The Vault is a listing of expiring contracts, task orders, etc. within a certain set of parameters, to include:

  • Have an initial total estimated contract value of $10 million or above
  • Federal Civilian Only – DHS, Transportation, Justice, Labor, Interior, Commerce, Energy, State, and Treasury Actions
  • NAICS codes include: 511210, 518210, 519130, 519190, 541511,
    541512, 
    541513, 541519, 541611, 541618,
    541690, 541720, 541990
  • Were modified within the last 12 calendar months
  • The data represented is based on information provided by the government

Who has access? Please note that ALL G2Xchange FedCiv Members will receive access to all basic and much of the advanced data. G2Xchange FedCiv Corporate Members will receive access to ALL Vault content (basic and advanced).

Feedback/Suggestions? Contact us at Vault@G2Xchange.com and let us know what you think. 

G2Xchange FedCiv

Log in with your credentials for G2Xchange FedCiv

Forgot your details?