RFI_32801-REAL2026_Amendment_5_Written_Questions_and_Comments.pdf
PDF 296 KB Posted
- Solicitation number
- RFI 32801-REAL2026
- Issued by
- Davidson County, Tennessee
About this file
This document is Amendment 5 to Request for Information (RFI) #32801-REAL2026 issued by the Tennessee Wildlife Resources Agency (TWRA) for the development, implementation, and administration of a Remote Easy Access License (R.E.A.L.) point-of-sale system. The RFI was issued on August 31, 2026, with written questions and comments due by 2:00 p.m. Central Time on September 11, 2026. TWRA provided state responses to submitted questions and comments on October 21, 2026, with the RFI response deadline set for 2:00 p.m. on October 28, 2026. The system will manage the complete lifecycle of hunting and fishing licenses, boat registrations and titling, game harvest reporting, quota hunt draw applications, reservations management, captive wildlife permitting, and other fee collection items across multiple transaction channels including in-person point-of-sale, web, and mobile platforms. TWRA processes approximately 1.1 million license sales annually across 245 license types, 91,000 quota hunt applications, 200,000 harvest records, and 125,000 boat registrations. TWRA prefers a 10-year contract term with additional renewal options dependent on Chief Procurement Officer approval.
Key technical requirements include a 4-hour Recovery Time Objective with zero data loss for critical transactions, 99.97% monthly uptime availability, real-time ACH revenue processing, and automated eligibility validation. The contractor must achieve one of six security certifications including ISO/IEC 27001:2022, FedRAMP Moderate or higher, GovRAMP, SOC 2 Type II, HITRUST r2, or annual NIST SP 800-53 audits, maintain $10 million cyber liability insurance per occurrence and aggregate, and encrypt all state data using FIPS 140-2/140-3 standards with data housed in the continental United States. Data conversion must be accurate with zero acceptable material-error thresholds for mission-critical data, utilizing authoritative sources including vessel registration, customer, Tennessee driver's license, agent information, hunter education, boater education, harvest reporting, and historical quota-hunt priority data. The final RFP will specify payment processing costs, settlement procedures, refunds, chargebacks, customer-paid fees, and detailed deliverables with formal acceptance criteria, including project management plans, quality assurance plans, system design documentation, test management plans, conversion and installation strategies, training strategies, and implementation manuals. This RFI is strictly for receiving vendor feedback and redlines; a formal RFP will be developed based on vendor input and will not be considered a prerequisite for participation in future solicitations.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFI # 32801-REAL2026 Amendment 5 Written Questions and Comments
STATE OF TENNESSEE
WILDLIFE RESOURCES AGENCY
REQUEST FOR INFORMATION # 32801-REAL2026
FOR REMOTE EASY ACCESS LICENSE (R.E.A.L)
POINT-OF-SALE SYSTEM
AMENDMENT 5
WRITTEN QUESTIONS AND COMMENTS
DATE: OCTOBER 21, 2026
RFI # 32801-REAL2026 IS AMENDED AS FOLLOWS:
1. This RFI Schedule of Events updates and confirms scheduled RFI dates. Any event, time, or date containing revised or new text is highlighted.
EVENT
TIME
(central time zone)
DATE
1. RFI Issued AUGUST 31, 2026
2. Written “Questions & Comments” Deadline 2:00 p.m. SEPTEMBER 11, 2026
3. State Response to Written “Questions & Comments” OCTOBER 21, 2026
4. RFI Response Deadline 2:00 p.m. OCTOBER 28, 2026
2. State responses to questions and comments in the table below amend and clarify this RFI.
Any restatement of RFI text in the Question/Comment column shall NOT be construed as a change in the actual wording of the RFI document.
QUESTION / COMMENT STATE RESPONSE
1. Was this released with the intent of suppliers to submit actual RFP responses?
No, this RFI is strictly for the purposes or receiving vendor feedback and redlines. A formal RFP will be developed based on vendor feedback.
2. Could TWRA confirm the intended commercial model for payment processing, ACH settlement, refunds, chargebacks, and any public-facing service fees, including which party will hold each operational responsibility? In other words, would payment processing costs be absorbed by the agency, passed on to the consumer, or some blend or option to do either?
The final RFP and contract will specify payment processing, settlement, refunds, chargebacks, and any customer-paid fees based on the agreement between the vendor and the state.
3. Could TWRA provide the expected initial term, renewal options, and maximum contract duration permitted for this procurement? A multi-year term is important to support conversion, implementation, and long-term administration of the system.
TWRA would prefer to do a 10-year term and additional renewal options would be dependent on CPO approval.
4. Could TWRA identify the deliverables subject to formal acceptance, the acceptance criteria for each, and the review period? We recommend that minor defects not materially impairing intended use be managed through the support process rather than delay acceptance, go-live, or payment.
The RFP will identify formal deliverables and acceptance activities. Deliverables include the Project Management Plan, Quality Assurance Plan, systems development lifecycle methodology, analysis specifications, system overview, general and detailed system design, Test Management Plan, Conversion Strategy, Installation Strategy, Training Strategy, database designs, forms, reports, screen formats, Implementation Plan, manuals, quick-reference cards, and pilot plan.
The State reviews and approves phase deliverables; State staff conduct UAT after contractor unit, integration, system, and regression testing.
The final approved work plan and contract will establish detailed review periods and acceptance criteria.
5. The scope requires a four-hour RTO and zero data loss for critical transactions, while Section D.39 identifies a 24-hour RTO and 12-hour RPO. Which recovery objectives should govern, and should they vary by criticality of service?
TWRA utilizes a 4-hour RTO and zero data loss . See Pro Forma Section A.5.h and revised D.39.c.
6. Could TWRA confirm the required security-assurance framework under Section D.39, including whether a current SOC 2 Type II report would satisfy the final requirement? The template currently presents multiple alternative frameworks.
The Pro Forma lists ISO/IEC 27001:2022, FedRAMP Moderate or higher, GovRAMP, SOC 2 Type II covering Security, Availability, and Confidentiality, HITRUST r2, and an annual NIST SP 800-53 audit as alternatives.
The final required option has not been selected in this draft. A SOC 2 Type II report would satisfy the requirement only if the final contract selects that option and the report covers the specified criteria and processing environment.
7. Could TWRA clarify the intended requirements for data conversion, including authoritative legacy sources, the process for resolving source-data quality issues, reconciliation
Required conversion sources: vessel registration, customer, Tennessee driver’s license, agent information, hunter education, boater education, harvest reporting, historical big-game harvest, quota-hunt priority history, methodology, and acceptable material-error thresholds?
and event-manager files. Requirements for data conversion: to be accurate. How to accomplish that will be left to the vendor.
Please refer to RFI 35910- REAL2026_Attachment B_Pro Foma Draft – section A.5.i..
Authoritative legacy sources: Brandt
Process for resolving data quality issues:
Notify TWRA of issues and, if required, TWRA works with Brandt for corrections.
Reconciliation methodology: The vendor will do this and TWRA can follow up with its own checks.
Acceptable material-error threshold: The industry standard is 0% for mission critical data, <0.1% for master data and active operations, 1%-5% for historical and transactional data but optimal threshold is 0%.
Please see item 3.
8. Could TWRA clarify the intended availability and support measurement methodology, including exclusions for scheduled maintenance, third-party connectivity, and other events outside the contractor’s control?
The public internet/mobile service is required 24 hours a day, seven days a week. Agent and customer help-desk requirements are separate: customer support is 6 a.m. to 10 p.m. CST, seven days a week, with calls answered within 15 seconds; agent/state support is at least 8 a.m. to 4:30 p.m.
Monday through Friday and may include peak-season hours. Agent calls must not remain in queue over 60 seconds, service completion must not exceed five minutes, and abandoned calls must be below 7% daily.
9. Could TWRA clarify ownership, procurement, deployment, replacement, and support responsibilities for license-agent hardware and connectivity, including the expected scope of store-and-forward capability?
Agents must provide their own computers, supported operating systems/browsers, internet connection, 8.5-by-11-inch paper, and ink. The agency is not requesting the vendor to provide hardware to license-agents.
10. Could TWRA clarify how post-award legislative, policy, integration, and functional changes will be prioritized and funded? In particular, how will the 1,000 annual development hours be defined, approved, carried forward, or supplemented?
Written change-control documentation identifying the affected module, request date, requestor, due date, request type, affected platform, and detailed description.
The contractor must respond with system impact and a cost estimate. The Pro Forma provides up to 1,000 development hours per year, excluding bug fixes, legislative and policy changes, security updates, planning, QA, project management, and deployment;
unused hours may be dismissed, rolled forward, or charged back at the State’s discretion.
Legislative/statutory changes and policy changes will take top priority to ensure completion by effective date. Development hours will be approved by TWRA Project Team and may be carried forward or supplemented if agreed upon by the vendor and TWRA.
11. How do 1-, 2-, and 3-year registrations expire?
How are mid-term transfers and refunds handled? Are Coast Guard documented vessels excluded? How are liens added and released?
The registration is calculated from the registration date for one, two, or three years, with no registration exceeding three years and 30 days.
Renewals may not exceed that limit. If a vessel is transferred to another individual halfway through the term, there is no refund and the new registrant/owner must start the process over and their registration will begin upon approval. Coast Guard documented vessels are required to be registered and the customer is to identify what is a CG documented vessel and provide the documentation number and proof of documentation.
Vessel titling is not currently required by Tennessee law; however, it is anticipated that legislation will be passed to require it.
The system must be capable of title and lienholder processing. Coast Guard documentation is captured as a vessel attribute; documented vessels are not stated to be excluded. Lien additions not added at the time of registration must be submitted directly to TWRA for completion. Any lien release must also go through TWRA.
12. For Harvest Reporting, Is GPS required, optional, or check-station only? Must a duplicate harvest be blocked? Do the 334 check stations operate without reliable connectivity?
GPS coordinates are required where available. Harvest reporting must be available through internet, mobile, and WEB POS, and the host update must be real time.
The system must create a permanent harvest log and unique harvest confirmation number. Duplicates must be blocked.
Every physical check station operates on the store owner provided internet so that portion of the question is not something we can answer.
13. Will TWRA accept a vendor-hosted commercial SaaS solution that is configured to meet Tennessee requirements, with State-specific development limited to mutually agreed functional gaps and integrations?
Yes. The attachments in the RFP expressly contemplate an existing software package and require a product functional demonstration and identification of each modification needed to meet Tennessee requirements.
A proposed package or SaaS solution must include all required customizations, training, development, and modification costs and must meet the State’s hosting, security, integration, and functional requirements.
14. The draft leaves scoring weights, the price form, and the calendar blank. Will the final RFP fill those in? Will vendors also do a scored demo of a live system already used by another wildlife agency?
As a draft document, this RFI omits event schedules, pricing, and scoring criteria.
These elements will be fully updated if the project proceeds to an RFP.
15. Will TWRA provide respondents with the current product catalog, eligibility and dependency rules, channel permissions, draw and harvest rules, customer-management rules, representative forms, and current-state process documentation necessary to evaluate solution fit and implementation effort?
The listed items will be included as attachments to the released RFP.
Attachments will identify the required functional sources and rules along with a full product catalog of all licenses.
16. The draft asks for priority points and party applications but does not say how the draw works. For each hunt: how are points earned and used? How big can a party be? Does each person use a quota slot? When is the fee charged — when they apply, when they win, or both?
Hunt categories are configurable for application dates, age, licensing, residency, party-size limits, priority points, number of choices, fees, quota, leftover allocation, ineligibility, and lottery logic.
A party leader receives a party number and may add members at submission, afterward, and after the lottery. Applicants select choices, order, and number of permits.
Applications receive random numbers and are sorted by priority; the lowest random number in the highest priority group is reviewed first. If one party member is drawn, the entire party is drawn. Application fees are charged except for valid Lifetime or Annual Sportsman holders; the draft does not state a separate win-time fee. Points are earned by either purchasing a priority point during the open application period specific to that hunt or submitting an application and the application being unsuccessful.
Party sizes very by hunt and how the points are considered also varies by hunt. An apply-alone array is available for party sizes up to a maximum of 75. Some hunts consider highest priority member, and some do an average of all party members, we also have hunts that do not consider priority at all and do not allow for priority points to be obtained.
The fee is currently $12 per drawing (if a quota hunt has 2 drawings then the fee is charged twice if the customer selects two drawings) and that fee is non-refundable and charged at the time of application.
17. The draft says remote agents can sell while the internet is down, then sync later. The contract also says the public website, the mobile site, and staff screens must work that way. Is offline selling only for agents with bad internet, or for every channel? If a device is offline, which licenses can it sell, and what happens if two people buy the last one?
Offline transactions are for mobile harvest only.
18. One part of the draft says agents deposit money weekly. Another part says money moves every day and the agent is locked out if a transfer fails. Which is it for retail stores, county clerks, and TWRA offices? If an office transfer fails, does that office get locked out too?
The contractor produces a weekly ACH file for the prior week’s sales, sweeps designated agent accounts based on sales minus accumulated agent fees, and transmits the file to Treasury with reconciliation. Sweeps may also be scheduled by individual dollar threshold or regular schedule, but at least weekly.
If ACH fails, the contractor immediately locks out the agent; the State determines the cause, resolves payment, and resets the account. This applies to all license agents who are in an ACH category, which does include retail stores and county clerks.
TWRA funds are processed and deposited internally outside of the licensing solution.
Please refer to RFI 35910- REAL2026_Attachment B_Pro Foma Draft – section A.5.d.
19. The draft says some licenses are digital and some paper, cards, boat papers, and decals still go in the mail. Which items are digital only?
Which must be printed? Which must be mailed?
Can a person hunt or boat the same day on a
The RFP attachments will identify fulfillment exceptions. The contractor’s fulfillment center prints durable hard cards and mails contractor-fulfilled items the next business day.
phone confirmation, or do they have to wait for the mail? Who prints titles and decals today?
The State fulfills boat registration certificates and decals, boat titles, lifetime Sportsman cards and certificates, senior-citizen and other special licenses, guide licenses, and hunter/boater education cards; customers cannot select contractor fulfillment for those exceptions.
Non-printed privileges are issued digitally via a PDF that the customer may print.
20. The draft says TWRA staff can change fees, hunts, and agent status. The contract also gives 1,000 development hours a year. When TWRA adds a new license, changes a fee, or opens a hunt, is that normal staff setup, or does it use those hours?
State staff to add or inactivate license types, boat registrations, event-registration and titling types, and update fees with automatic application to the appropriate tables. Those configuration actions are administrative setup. It does not use development hours.
21. The draft is about boats. Are ATVs, OHVs, or snowmobiles in this buy? For boats, which of these can a customer do on the website, which can an agent do, and which can only TWRA staff do: new title, transfer, renewal, replacement, add a lien, release a lien, out-of-state title? Do county clerks title boats, sell licenses, or both?
ATVs, OHVs, nor snowmobiles are registered through TWRA. Original boat registrations are processed at all TWRA offices and online; transfers at TWRA offices and online; renewals at TWRA offices, online, and license-agent locations. Captive-wildlife permits are online and central-office administrative transactions; falconry is central-office administrative only.
New, Transfer and Replacement Titles can be done at TWRA offices and online. Liens may be added at the time of application online, if not added during that time they must go to TWRA central-office as will the lease of a lien.
Each state handles their own titling processes we will not do out of state titles.
Some clerks sell licenses but not all and all clerks collect sales/use tax for person-to-person transactions and persons bringing vessels in from out to state to use primarily in the state of TENNESSEE. The customer then submits documentation to us for registration and eventually when the time comes titling.
22. The draft requires the federal HIP survey when someone buys. Are any other surveys required before the license is issued?
Internal-use surveys are required before other licenses can be issued.
23. The draft asks for a weekly stolen-boat report and a yearly Coast Guard report. Does TWRA
Yes. TWRA requires a weekly stored stolen-vessel report with print/export capability and an annual Coast Guard report available need a file sent to another system, or is a report the staff can export enough?
before January 10. That file does not get sent to another system; it gets sent to the TWRA Project Team.
24. Boat records must tie to a unique TWRA customer number. Who issues that number today? Does it have to stay the same after conversion? Can one person have more than one customer record now, and what should happen to those at go-live?
If a customer does not have a TWRA ID, the system must issue one when the customer information is processed. The TWRA ID number will stay with the customer, and it will need to stay the same during the conversion.
A customer should not have more than one record. The social security and drivers license numbers should be a blocker to prevent duplicate records from being created. If such records exist, we simply leave them as is and merge them as we come across them at this time.
25. Agents include stores and county clerks. Do clerks sell the same licenses as stores? Do they also title and register boats? Do they keep the same issuing fee? Are any products clerk-only or store-only?
Acting as license agents, county clerks function identically to regular license stores without any special capabilities beyond those of standard agents. They collect all standard fees and process taxes through the Department of Revenue system to facilitate boat registration and titling, though they do not perform the registration or titling function themselves.
26. How many quota hunts run in a normal year?
What is the largest party? Does the group file one application, or does each person apply and then get linked?
TWRA conducts 15 drawings each year. It supports configurable party minimums and maximums, party numbers, post-submission and post-lottery member additions Our largest party size if 75 for one hunt only. A party leader will apply, create the hunt choices and order and each member will then apply using a party number provided to the leader at the end of their transaction.
27. After a draw runs, can TWRA add quota, move someone to another hunt, or pick a winner by hand? If they do, do existing winners stay, or can those awards change?
TWRA does not add quota post drawing, however we do allow for over fill for some drawings per the rules. Quota hunts are not transferrable, and we only do “hand drawings” for waterfowl leftovers. The awards will only change in the event of a system error.
28. When someone registers a new boat, is the title always part of that sale, optional, or a later step? Can a boat be registered with no title, or titled with no registration?
Because Tennessee currently does not title vessels, future titling will be integrated into the original or transfer process, while certain vessels will remain exempt and registerable without a title. Currently, titles are not anticipated to be authorized without at least a one-year registration.
29. The draft says staff can break the link between a customer and a boat. When do they do that — sold, destroyed, transferred, or a data fix? What happens to the title, lien, and registration history when they do?
Authorized State personnel may break the customer-vessel link when a vessel is registered to the wrong customer. It also requires editable vessel fields, stolen-vessel reporting, title/lien data, and complete vessel history. The attachments do not provide a separate disposition rule for sold or destroyed vessels; link-breaking and history treatment will be controlled by permissions and State-approved design.
With Tennessee not being a titling state as of yet, the desire would be that the title stays connected when marked sold until someone else registers/titles that vessel. The transfer indicator only appears when we transfer the vessel to someone else, so the understanding would be that the customer should also be applying for a title and the previous owner should no longer be associated.
Registration history must stay intact and be verified for lien release prior to transfer.
30. Are decals and titles printed as needed, pulled from numbered stock, or both? If there is stock, who owns it, and does the system have to track each one, including voids and waste?
Currently, all printed items are produced in-house at the agency.
31. Are commercial fishing licenses in on day one?
For captive wildlife and falconry, does the person buy it like a hunting license, apply and wait for TWRA to approve, or both? Falconry is called a three-year permit. Is that one product that lasts three years, or a one-year product sold three times?
Commercial fishing is to be included on day one.
Captive-wildlife permits require an application, supporting documents, State review, approval/denial/request for more information, and payment after approval;
processing is online/mobile or central-office administrative.
Falconry requires an exam, qualifications, application, State approval, and a permit; it is central-office administrative only and has apprentice, general, and master classes.
The permit is a single permit that spans a three-fiscal-year period.
32. The RFI mentions “sampling results.” Is that lab work, creel surveys, or something else? Is a magazine subscription sold like a license, or is it a separate mail product?
Sampling results are results that TWRA sends to a lab for Chronic Wasting Disease testing and then the results are returned to TWRA and then uploaded to the vendor to be added to the customer’s harvest record.
Magazine subscriptions are sold like licenses.
33. Customers pay agents a fee on most licenses.
Does TWRA set that amount on the product, does the agent set it, or both? Must that fee show as its own line on the receipt and in the money sent to Treasury?
The fee that the customer pays to the license agent is set by statute.
The fee must be shown as its own item and is retained by the license agent and not included in the weekly sweep to treasury.
34. The draft says 100 percent of customers, license history, draw history, harvest history, and boat records must move. How many years of each are required on day one? Is today’s R.E.A.L. system the only source?
TWRA has collected this data electronically since 1999. On day one, the objective is to ensure that as much data as possible is received and converted –with priority on active licenses and permits. While data delays during any cutover period are understood and can be discussed between the vendor and the State for scheduling flexibility, a replicated database of all TWRA records is also maintained.
35. What response period does the State anticipate providing between the release of final Q&A responses or amendments and the proposal deadline?
Refer to the schedule of events in Item 1 of this document and Item 4 of the released RFI. Future RFP dates will align with the applicable RFP schedule.
36. Will TWRA consider a phased implementation (for example, licensing and harvest first; boat titling and specialized permits later), and if so, what is the required first production date and any statutory or license-year constraints on cutover?
TWRA requires a pilot plan six months before full implementation and pilot execution three months before full implementation. Please refer to RFI 35910- REAL2026_Attachment B_Pro Foma Draft – section A.5.i.
The pilot must include all R.E.A.L. modules and platforms, have written State approval, and upload pilot privilege data weekly to the current contractor so the final database remains integrated.
37. C.22 requires HIP survey capture. Is HIP limited to collecting responses at purchase, or must the system also transmit files to USFWS in a specified format and schedule?
USFW requires all HIP data to be transmitted to them in a specified format and on a detailed schedule. This applies to all states that collect HIP data.
38. Please list required system integrations for go-live (State Treasury/ACH, payment processor, ACH processes are owned by the State of Tennessee Treasury; payment processors
USFWS/HIP/Federal Aid, Coast Guard, law enforcement/stolen vessel, hunter education, state identity/SSO, county clerk systems, data warehouse/ERP, others), including which party owns each interface and whether a file exchange is acceptable in lieu of a real-time
API.
for online sales are the ownership of the vendor, agents and TWRA will collect funds internally separate of the vendor solution;
license agents (which include county clerks) deposit all funds into an approved account for ACH Sweep, TWRA will maintain their funds through internal state approved processes.
County clerks do not have a separate system that we oversee, if they sell licenses they function just like license agents.
A file exchange would only be acceptable if our side if the integration isn't compatible with API. API should be considered primary for all interfaces.
Please refer to RFI 35910- REAL2026_Attachment C - R.E.A.L. System Required Integrations
39. C.43–C.47 require annual curriculum updates, agent certification via sandbox test transactions, manuals 30 days before go-live, and a post-training effectiveness report for 465 agents plus regional staff. Will TWRA accept a role-based digital training model (in-app help, LMS, train-the-trainer) in lieu of contractor-delivered in-person training at each location, and who is responsible for agent attendance and certification enforcement?
Yes. Agent training need not be one-on-one at each site and may use group or area meetings, telephone, video, manuals, and videos or suitable substitutes.
Contractor training for State staff is classroom-based at specified TWRA offices.
The contractor must provide training materials, follow-up, evaluation, and a training schedule supporting UAT, conversion, pilot, and implementation.
40. Please identify any enacted or formally introduced legislation expected to affect the project scope, business rules, or implementation schedule.
Beyond boat titling and lien recordation, there is no legislation that could modify the scope, business rules, or implementation schedule. However, given that this system will retain social security numbers, TWRA-issued ID numbers (state-issued IDs), customer home addresses, email addresses, and phone numbers, all data protection requirements are applicable.
41. Would TWRA consider evaluating an integrated CRM and customer-engagement capability that supports configurable segmentation, email, SMS, push notifications, consent management, and recruitment, retention, and reactivation initiatives using R.E.A.L. system data?
The RFP will include optional marketing and hard-card capabilities but do not require an integrated CRM or campaign-management platform. It also requires customer records and related consent/solicitation fields where specified. Respondents may propose CRM and engagement capabilities for State consideration, subject to final scope and approval.
42. If a third-party marketing platform will be used to communicate with customers from the R.E.A.L.
system, does TWRA expect the R.E.A.L.
system to serve as the system of record for consent and marketing opt-in management?
In addition to the marketing option that is to be included in the RFP, the agency maintains its own communication platform that does rely on obtaining records from the system. The agency expects the REAL system to include consent for marketing opt-in management and an indicator within the database tables to indicate the customer preference.
43. Does TWRA intend to issue any type of hard card promotional products moving forward?
Yes
44. Does TWRA expect to maintain management of programs such as the TARP program through the R.E.A.L. system?
Yes
45. Does TWRA expect the updated R.E.A.L.
system to continue to offer for sale other merchandise and privileges beyond hunting, fishing and outdoor recreation?
Yes
46. What channels does TWRA expect to communicate and deliver transactional information to customers (e.g. SMS, email, push notification, etc.)?
Transactional communication will be delivered exclusively via email. Push notifications are optional and not required.
Please see item 6.
47. What percentage of harvest reports are submitted online versus at a check station or point-of-sale agent?
80-90% of harvests are currently submitted online/mobile. Point of sale agents will only collect harvest reporting data if they are an authorized check station.
48. What percentage of license sales occur online versus at a point-of-sale agent?
77% are sold online, 18 % at license agents the rest are sold through TWRA or the vendor help desk.
49. Will the State permit the contractor to provide its own integrated payment-processing solution and serve as merchant of record for public internet and mobile transactions, or must the contractor integrate with a State-designated payment processor? If a State processor is required, please identify the processor, gateway, and applicable technical and commercial terms.
For online/mobile sales, the vendor may provide its own integrated payment-processing solution.
Agent sales shall be conducted in the method in which the agent conducts their normal business and make deposits into an approved account for ACH transfers.
The State is required to use the state processing methods which are not integrated into the system in any way and is operated completely independent of the licensing solution.
50. Please describe the required funds-flow model for public internet, mobile, agent, and TWRA-office transactions, including settlement timing, State deposits, vendor fees, refunds, reversals, chargebacks, and reconciliation responsibilities.
A license is sold online or at a license agent and deposited into a designated account provided to TWRA. Weekly ACH sweeps of agent accounts (including the vendor for online sales), transfer of the prior week’s sales less accumulated agent fees, Treasury transmission and reconciliation, and collection of online/mobile revenue with the contractor handling fee retained before the balance is deposited to the State account.
The sales included begin at 12:00AM Monday through 11:59PM Sunday of each week. The agent is to be able to run an ACH report on Monday to verify the ACH draft.
The draft traditionally occurs on Tuesday of each week. State deposits are handled outside of the licensing solution.
Chargebacks are not to be disputed, and a report is to be provided weekly to the State for the state to collect the fees.
Please refer to RFI 35910- REAL2026_Attachment B_Pro Foma Draft – section A.5.d.
Reconciliation is the responsibility of both the vendor and the state.
51. Will the contractor be permitted to charge customers a convenience, service, or transaction fee for public internet and mobile transactions? If so, may the fee vary based on channel, transaction type, fulfillment requirements, or order value?
Yes, subject to the terms of the final contract.
The Pro Forma contains maximum-fee placeholders for mobile and public internet transactions, fulfilled and non-fulfilled, and for durable hard cards.
52. May payment-processing fees be separately passed through to the purchaser, or must all card-processing costs be included within the maximum customer transaction fee?
Any and all fees charged to the customer must be identifiable and apparent on a ‘per transaction’ basis. The final agreed upon fees remain subject to the final contract terms and conditions.
53. Do public internet and mobile transactions qualify for the purchaser-paid issuing or agent fee currently associated with sales through physical license agents? If so, please identify
An online convenience fee may be appropriate; however, the Agency seeks to encourage online transactions over physical license agents. Potential respondents should consider whether or not an additional the amount, statutory basis, and party entitled to receive the fee.
fee for online sales is required in light of the policy aims. The contractor will collect and keep any additional fee, which should be considered in their cost proposal.
54. Will the State consider a pricing structure that includes some combination of a one-time implementation fee, annual SaaS subscription, State-paid transaction fees, customer-paid transaction fees, payment-processing charges, fulfillment fees, and hourly rates for approved changes?
Yes, the draft Pro Forma includes per-transaction compensation, hourly rates for approved changes, and maximum third-party fees for mobile/public internet transactions and hard cards. Attachment D requires all development, customization, and training costs in the cost proposal. The final RFP will establish the permitted pricing categories and evaluation method.
55. Please provide at least three years of transaction counts by channel and transaction type, including agent POS, TWRA office, public internet, mobile, harvest reporting, quota applications, boat transactions, fulfilled transactions, and non-fulfilled transactions.
Please also provide average order value and credit/debit-card volume.
Please refer to RFI 32801-REAL2026 – Written Questions and Comments – Attachment 1.
Credit/debit card volume 3-year transactions 23/24 757,825 count Average order $51.26;
24/25 801,854 count average order $51.64;
25/26 875,273 count average order $51.38 those are the only credit card vendor processing avenues that we have and are online sales.
56. When will the State provide the completed cost categories and evaluation factors currently shown as placeholders in Attachment 6.3? Will respondents have an opportunity to comment on the proposed pricing structure before the RFP is finalized?
The draft document intentionally leaves cost categories and evaluation factors incomplete. These elements will be provided in the final RFP. The final procurement will state whether respondents may comment on the pricing structure before release.
57. What are the anticipated contract effective date, target go-live date, operational blackout periods, and other external deadlines that should inform the implementation schedule?
Should an RFP follow this RFI, all dates will align with the applicable RFP schedule.
Contract dates will be detailed on the Pro Forma document following award.
58. What State resources will be dedicated to requirements validation, configuration decisions and execution, data remediation, integration testing, UAT, training, and acceptance? Will the implementation schedule account for State decision-making and deliverable turnaround times?
Attachments to be released with the RFP will define State responsibilities. The implementation plan must account for these activities and the State-approved schedule.
59. May a contractor use its established implementation methodology mapped to TBSM requirements, or does the State expect the contractor to adopt TBSM as the exclusive delivery methodology?
The RFP will require delivery in accordance with TBSM. RFP attachments will require a systems development lifecycle methodology tailored to this contract. A respondent may propose an established methodology, but it must map to and satisfy TBSM and the State-approved project plans.
60. Attachment A requires development and testing environments that mirror the State’s production infrastructure. For a vendor-hosted SaaS solution, will the State accept non-production environments using scrubbed data that are functionally representative of the contractor’s production environment?
For STS response
61. Does “mobile portal” require native iOS and Android applications, a mobile-responsive website, or either approach? If native applications are required, please identify the required features, including digital-license storage, offline access, harvest reporting, push notifications, and managed-area check-in/check-out.
The attachments require a responsive web site for licenses, permits, boat registrations, events, and reservations and describe internet/mobile applications. They do not require native iOS and Android applications.
The final technical response may propose the compliant mobile approach.
62. Please describe the required event-management functionality, including event creation, schedules, capacity, waitlists, instructors or volunteers, attendance, payments, cancellations, refunds, communications, and reporting. Does finishing an event give a certification that is required to buy a license later?
Registration, waitlist, capacity, schedules, surveys (pre and post event), payments (including varying payments), cancellations, refunds, communications, reporting, requirements before applying.
It may require a certification to be given at a later date, but not at this time.
Please refer to item 5.
63. Please identify the resources and use cases covered by “reservations management,” such as facilities, campsites, shooting ranges, appointments, classes, timed-entry inventory, or other resources, together with applicable capacity, availability, payment, and cancellation rules.
The system manages State-designated sites and spaces, such as handicapped-accessible duck blinds, shooting ranges, and classrooms. The State establishes all dates, times, rates, and participant-based fees, while the system must prevent double-booking, identify every participant, and allow edits up to a State-designated cutoff. Note that these bookings are distinct from Tennessee State Parks reservations.
64. Does the scope include the sale of merchandise or physical products such as apparel, posters, publications, or equipment? If so, please describe requirements for catalogs, inventory, sales tax, shipping, returns, and fulfillment.
Yes, merchandise orders and sales-tax collection products will vary depending on the choices selected by the agency. A catalog of items, inventory, and reports are required. Vendor shipping is optional and not required.
65. Does the State expect the contractor to provide, own, configure, support, replace, or remotely manage physical POS equipment?
Alternatively, will the State accept a browser-based solution operating on State- and agent-provided devices?
This procurement does not request any physical equipment for license agents.
66. Does the State anticipate requirements for CRM, customer segmentation, email, SMS, push notifications, campaign management, marketing automation, customer surveys, or related marketing services?
Full CRM, segmentation, SMS, push notifications, and marketing automation services are not required; however, collaborative marketing services are required.
67. Please clarify the required store-and-forward functionality, including the channels and transaction types that must operate offline.
Does the State expect licenses to be issued and payments accepted without real-time eligibility, inventory, identity, or payment authorization?
Store-and-forward is required for Web POS at remote license-agent locations during intermittent connectivity, especially, in instances of licensure and harvest reporting.
When customers purchase from license agents, they are paying the agent directly through their own payment processing system outside of the REAL system.
68. Please identify which party is expected to print, assemble, mail, and track licenses, hard cards, boat certificates, titles, and decals. Please provide annual volumes, materials specifications, postage responsibility, turnaround standards, and whether subcontracted fulfillment is permitted.
Licenses purchased online are delivered via email from the contracted vendor, the pdf of the license is not mailed.
Hard cards will be mailed from the vendor and tracked via vendor contract with USPS if applicable. Postage and material responsibility for this item is for the vendor and is expected to be mailed the next business day.
Boat certificates/decals, titles, lifetime licenses, guide licenses and permanent specialty cards are printed by the state with a required fulfillment file sent from the vendor.
The State is open to a drop ship arrangement for all print materials if it is a cost-benefit to the State.
69. Please provide detailed current-state workflows, forms, interfaces, and sample reports for boat registration, titling, transfers, liens, ownership changes, stolen-boat exceptions, title printing, Coast Guard reporting, and record unlinking.
Workflows depend on the transaction being completed. Reports are all generated from the tables within the REAL system data .
Detailed information will be listed in the RFP to each of those processes.
70. The RFI describes weekly ACH collection from license agents, while Attachment A calls for daily ACH files to the Treasury. Please clarify the required settlement cadence and the
The contractor produces weekly prior-week ACH files, sweeps agent accounts net of accumulated agent fees, transmits to Treasury, and provides reconciliation and contractor’s responsibilities for initiating ACH debits, handling returns, restricting agent access, and administering installment payments.
sweep reports. Sweeps may follow State-approved dollar or schedule criteria but are at least weekly. Failed ACH causes immediate agent lockout; the State resolves the failure and resets the agent.
Administrative screens must support debit/credit adjustments for installment payments tied to the failed ACH.
71. Will the requirement to transfer 100% of records be measured against a mutually approved set of valid and usable source records following profiling and remediation? Please clarify State responsibilities for resolving incomplete, corrupt, duplicate, or internally inconsistent source data.
Source records comprise all data from the current vendor (Brandt), preferably utilized in the format received from them. The vendor is responsible for resolving any incomplete, corrupt, duplicate, or inconsistent source data. For conversion and verification, the vendor must convert the data for use in their system by any suitable method. While the vendor is responsible for verifying successful conversion, the TWRA will conduct accuracy spot-checks by randomly reviewing a percentage of records to ensure all data is valid and correctly mapped.
72. Please clarify whether the required Data Dictionary and schema documentation may consist of a logical ERD, defined data elements, and appropriate table-level relationships, or whether the State expects the contractor’s complete proprietary physical database schema.
The state requires database logical and physical designs, file structures, data elements, relationships, and interface files in the approved design. A logical ERD alone would not cover the stated requirement; the final deliverable must include the approved logical and physical database/file documentation while protecting unrelated proprietary information.
Please refer to RFI 35910- REAL2026_Attachment B_Pro Foma Draft – section A.5.a.
73. Please identify all legacy databases, estimated record counts, file formats, external systems, payment interfaces, education providers, fulfillment vendors, financial systems, federal reporting interfaces, and other integrations included in scope.
The legacy/automated source files for vessel registration, customer licenses, customer data, driver’s license, agents, hunter and boater education, harvest, historical big-game harvest, quota priority history, and event manager. Payment/ACH, Coast Guard/Info-Link, fulfillment/SFTP, and federal HIP data exchanges are required on designated interfaces.
74. Attachment B requires every call to be answered within 15 seconds. Is this intended as an average speed-of-answer metric or an absolute per-call requirement? Please also clarify required hours, languages, channels, call
Customer support must be available from 6:00 a.m. to 10:00 p.m. CST, seven days a week, with every call answered within 15 seconds. Agent and State support shall operate at least Monday through Friday from 8:00 a.m. to 4:30 p.m., maintaining a queue volumes, abandonment treatment, and severity-based resolution targets.
time under 60 seconds, service completion within five minutes, and daily abandoned calls below 7%, with staffing increased during peak periods.
75. Please confirm whether the absence of requirements C.16, C.35, and C.36 from Attachment 6.2 is intentional or whether requirements were inadvertently omitted.
This is a draft document. Evaluation Factors have been intentionally omitted.
76. In the RFI's Statement of Purpose, it mentions "reservations management". Does that relate to reservations for Tennessee State Parks? If not, what does it relate to?
Handicapped-accessible duck blinds, shooting ranges, classrooms, and other State-designated sites and spaces.
Responsibilities for Tennessee State Parks belong to a separate State agency.
77. For the mandatory requirement to demonstrate two to three contracts of similar scope for other State agencies, may a respondent rely on qualifying contracts performed by an identified subcontractor or combined project team, and what minimum functions must a contract include to be considered “similar scope”?
This is in reference to vendor references from states that are similar in nature to what TWRA’s needs are as it pertains to the scope. A similar scope would be another state that has some/all of the same requirements that we have for the vendor.
78. Please identify the incumbent platform and contractor and provide the expected legacy-data scope, available export formats, interface documentation, historical retention period, attachment volume, data-quality profile, and required parallel-operation or cutover period.
The incumbent solution is provided by our current vendor Brandt. Total legacy attachment volume is estimated at approximately 500 GB. Full technical specifications—including legacy data scope, available export formats, interface documentation, and data-quality profiles— will be coordinated with the incumbent and made available during the transition and onboarding phase. The schedule for parallel operations and final cutover will be determined collaboratively during implementation planning.
79. Please provide the required integration inventory, including payment gateway, ACH and Treasury systems, identity services, boat-registration or titling systems, agent hardware, printers, federal reporting systems, and any State-managed APIs, and clarify which party bears PCI merchant-of-record and payment-reconciliation responsibility.
For the RFI, this information is unavailable at this time, but it may be considered for inclusion in the final RFP.
80. Please clarify the required toll-free help-desk users, operating hours, channels, historical
Customer help desk: toll-free line, 6 a.m. to 10 p.m. CST seven days a week, every call contact volumes, service levels, and staffing expectations, including whether 24/7 availability applies only to the system or also to human support.
answered within 15 seconds, and support interactions and resolution metrics tracked.
Agent/state help desk: unique toll-free line, minimum 8 a.m. to 4:30 p.m. Monday-Friday plus State-designated peak periods; queue under 60 seconds, service completion within five minutes, abandoned calls under 7% daily, and adequate staffing.
Customer Help Desk: Provided via a toll-free line operating from 6:00 a.m. to 10:00 p.m. CST, seven days a week. Requires a maximum 15-second answer time, with tracking for all support interactions and resolution metrics.
Agent/State Help Desk: Provided via a dedicated toll-free line operating Monday through Friday from 8:00 a.m. to 4:30 p.m., plus State-designated peak periods.
Requires a queue time under 60 seconds, service completion within five minutes, daily abandoned calls under 7%, and adequate staffing.
General Availability: While the underlying system must remain available 24/7, live human support is not required 24/7 under these attachments.
81. Please confirm whether the State will permit a recurring SaaS or per-transaction pricing model with implementation and migration costs incorporated into recurring charges, whether convenience fees may be assessed to purchasers, and which projected transaction volumes the State will use to evaluate variable pricing.
Yes, subject to the final RFP and contract.
The Pro Forma includes transaction-based compensation, approved-change hourly rates, and maximum third-party fees for mobile/public internet transactions and hard cards. TWRA will require implementation, customization, development, and training costs in the cost proposal. The final RFP will define any recurring SaaS, implementation, migration, convenience-fee, and volume-evaluation terms.
3. Delete RFI 35910-REAL2026_Attachment B_Pro Foma Draft section A.5.i. in its entirety and insert the following in its place (any sentence or paragraph containing revised or new text is highlighted):
A.5.i. The Contractor shall develop a comprehensive data conversion plan that details the mapping, transformation, and validation procedures for migrating existing customer, agent, and historical records into the R.E.A.L. System database. The Contractor shall perform data cleansing and normalization on all legacy datasets to ensure consistency, accuracy, and compliance with the new System's data schema and business rules prior to final migration.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .