32701-26-331_RFP_Functional_and_Technical_Requirements.xlsx

XLSX spreadsheet 44 KB Posted

Attached to
A Tennessee State Parks Reservation and Retail Point of Sale System
Solicitation number
RFP 32701-26-331
Issued by
Davidson County, Tennessee

About this file

This is a Functional and Technical Requirements Matrix for a comprehensive reservation and retail point-of-sale system to be implemented by Tennessee State Parks. The system will manage advanced reservations for all Tennessee State Parks' reservable products, including campgrounds, cabins, marinas, group facilities, day-use areas, tours, access permits, and programs across multiple channels: phone (1-888-TN-PARKS), walk-in, online portals (tnstateparks.com and reserve.tnstateparks.com), and field applications in park offices. The requirements matrix contains over 200 functional and technical specifications organized into 16 major categories: General Requirements, Customer Accounts Management, System Setup, Map System, Online Reservation Website, Modern Hospitality Features, Data Integration and Analytics, Reporting, Retail POS and Stock Inventory Management, Gift Cards, Refund and Cancellation Processing, Marina Registration and Management, Credit Card Processing, Journal Vouchers/SARs, and Customer Relationship Management. Respondents must address each requirement individually, selecting from compliance/delivery status codes (Fully Compliant at Go-Live, Compliant via Configuration at Go-Live, Compliant via Customization at Go-Live, Phased – Post Go-Live, or Not Proposed) and providing detailed substantiating comments. Many requirements are designated as High priority and mandatory at go-live, while others are Medium or Low priority and may be phased post-implementation with justified timelines and milestones.

The requirements emphasize a commercially proven, production-ready solution currently operating at multiple comparable customer sites managing 500,000+ annual transactions, with no system-imposed limits on inventory scaling. The proposed solution must include a dedicated non-production testing/UAT environment, full integration of reservation, customer, POS, and financial data into a centralized database with encryption per FIPS 140-3 standards, and seamless migration of all historical data. Key technical requirements include integration with Tennessee's general ledger system (Edison or successor), WorldPay/FIS credit card processing, ValuTec gift card processing, real-time API access for third-party analytics and integrations, comprehensive reporting dashboards (occupancy, revenue, dynamic pricing, forecasting, reconciliation), mobile-responsive WCAG 2.2 AA accessibility compliance, and PCI DSS compliance for all payment processing. The system must support flexible business rules, dynamic pricing, multi-channel payment options (credit card, gift card, Apple Pay, Google Pay), and operational features including housekeeping management, trip protection, denial/regret tracking, and modern hospitality capabilities. All responses will be evaluated holistically based on clarity, feasibility, alignment with State priorities, and demonstrated commitment to delivery at no additional cost, with all listed requirements intended for inclusion in the final contract.

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

REQUIREMENTS MATRIX

Attachment 6.2-Section E-Functional & Technical Requirements Matrix
Instructions for Completing Functional and Technical Requirements

Overview

This tab contains the State's functional and technical requirements for the proposed solution. Respondents must address each requirement individually to demonstrate how their solution meets or will meet the specified needs. Unlike traditional self-scoring matrices, this RFP uses a holistic evaluation approach for Section C. Your responses will be assessed qualitatively based on clarity, feasibility, alignment with State priorities, and commitment to delivery—all at no additional cost to the State.

The State intends for all requirements listed in this tab to be included in the final contract without extra fees. Many requirements are mandatory at go-live (initial production rollout), while others may be phased in post-go-live via an agreed-upon timeline. Respondents should propose phasing only where justified, providing detailed plans in their responses.

Do not include pricing information in your responses. Blank, vague, or incomplete entries may be deemed non-responsive and impact your holistic score.

Structure of the Requirements Matrix

The matrix includes the following columns:

ID: Unique identifier for the requirement (pre-populated; do not modify).
Business Requirements: Narrative description of the requirement (pre-populated; do not modify).
Priority: Indicates relative importance (H = High, M = Medium, L = Low; pre-populated; do not modify). Use this to prioritize your efforts—higher-priority items are less amenable to phasing or exceptions.
Compliance / Delivery Status: Select one code from the dropdown list (or enter manually if not using Excel validation). This indicates your commitment to meeting the requirement.
Respondent Comments / Approach: Provide detailed substantiation here (free text; required for every row). Explain how the requirement is or will be met, including any tools, processes, or integrations. For phased or exception items, include timelines, milestones, risks, dependencies, and interim solutions. Reference supporting materials (e.g., "See Implementation Plan, Section 3.4" or "Demonstrated in Reference Site Y"). Cross-reference related requirements if applicable.
Mandatory at Go-Live?: Pre-populated by the State where known (Yes/No/To Be Determined).

Compliance / Delivery Status Codes

Select the code that best describes your proposed solution's ability to meet the requirement. All codes imply full contractual commitment at no extra cost. Use the following options exactly as listed:

Fully Compliant at Go-Live: The requirement is fully met in the proposed solution and will be delivered and operational at initial go-live/production rollout (no configuration, customization, or phasing needed beyond standard implementation tuning).
Compliant via Configuration at Go-Live: Fully met at go-live through parameter/settings adjustments only (no code changes or major development required).
Compliant via Customization at Go-Live: Fully met at go-live but requires code-level changes, extensions, or subcontractor work (provide a detailed plan in comments, including effort estimates and risks).
Phased – Post Go-Live: Will be delivered after go-live per an agreed phased implementation schedule (must provide proposed timeline, milestones, dependencies, and any interim workarounds in comments; subject to State approval during contract negotiation).
Not Proposed: Cannot meet the requirement (even with phasing, customization, or alternatives). Use sparingly. “Not Proposed” does not automatically disqualify your proposal. Evaluation is holistic across the entire submission, but it may significantly weaken your score on mandatory or high-priority items.
Prioritize "at Go-Live" codes for High-priority (H) items unless phasing is clearly justified (e.g., due to dependencies on State systems).
For "Phased – Post Go-Live", ensure your proposal includes a high-level project plan (in your overall RFP response) summarizing all phased items with timelines (e.g., Phase 1: Go-Live + 3 months; Phase 2: Go-Live + 12 months).
The awarded contractor will be accountable for all responses here, as this tab will be referenced as Attachment 2 in the Pro Forma Contract.

How to Complete the Matrix

Review Each Requirement: Read the Business Requirements column carefully. Consider the Priority and any pre-populated Mandatory at Go-Live? status.
Select a Compliance / Delivery Status Code: Choose the most accurate code based on your solution's capabilities and proposed delivery.
Provide Substantiating Comments:
Describe the approach in detail (e.g., "Achieved via our core CRM module with standard API integration to Edison; no custom code needed").
For phased items: Include specifics like "Proposed for Phase 2 (Q2 2027), dependent on State data migration completion; interim manual process via Excel exports."
For exceptions: Justify and propose alternatives (e.g., "Alternative: Use OAuth 2.1 instead of OAuth 2.0 for enhanced security; meets intent with forward compatibility").
Keep comments concise yet comprehensive (aim for 50-200 words per row; use bullet points for clarity).
Relate to multiple requirements if applicable (e.g., "See response to ID 3.01 for shared business rule engine").
Propose Mandatory Status if Blank: If the Mandatory at Go-Live? column is empty, suggest "Yes" or "No" based on your assessment, with rationale in comments.
Ensure Holistic Alignment: Your responses should demonstrate innovation, low risk, and value—evaluators will score the entire matrix as one cohesive document in Section C.
FUNCTIONAL AND TECHNICAL REQUIREMENTS MATRIX
Business RequirementsPriorityCompliance / Delivery StatusRespondent Comments / ApproachMandatory at

Go-Live?

1.00 General Requirements
1.01The proposed solution must be fully functional, Commercially Proven Solution, and currently operating in a production (non-test) environment at multiple comparable customer sites of similar scope and scale (multi-park public recreation/reservation systems managing ≥500,000 annual transactions).HYes
1.02Provide and maintain a separate, non-production testing environment (including a dedicated User Acceptance Testing [UAT] instance) that mirrors the production system configuration, data volume, and integrations, allowing Tennessee State Parks staff to fully test all modifications, enhancements, patches, and new features prior to deployment to production.HYes
1.03The solution must contain no embedded clock, timer, counter, usage-limiting mechanism, kill switch, or other code that could disable, degrade, corrupt, erase, or otherwise render the software inoperable or non-compliant with Tennessee State Parks requirements at any time.HYes
1.04All components of the system must be fully integrated to eliminate duplicate data entry and redundant storage. All data must be encrypted at rest and in transit per current FIPS 140-3 standards (or successor), stored in a single centralized database, and support seamless migration and integration of existing Tennessee State Parks historical reservation, customer, and transaction data.HYes
1.05The system must support selective export and download of data in standard, interoperable formats (CSV, Excel, JSON, PDF) compatible with common tools such as Adobe, Microsoft Excel, Power BI, Tableau, GIS software, and State of Tennessee enterprise reporting platforms.HYes
1.06The system must provide a consistent, unified user experience for reservations whether entered by park staff (in-park/field workstations or mobile POS devices) or by customers online. The interface must share a common look, feel, navigation, and branding aligned with tnstateparks.com and reserve.tnstateparks.com. The awarded vendor will receive TSP style guides and branding assets to ensure full compliance.HYes
1.07The system must perform real-time input validation, clearly highlight erroneous fields in red (or equivalent high-contrast indicator), and display specific, user-friendly error messages explaining exactly what data is required or incorrect.HYes
1.08The system must support flexible, role-based security with multiple permission levels that can be created, modified, or removed by authorized TSP administrators as operational needs evolve, including granular control over access to reservations, customer data, financial transactions, reporting, and administrative functions.HYes
2.00 Customer Accounts Management
2.00Offer optional guest accounts with modern, hospitality-industry convenience (similar to major hotels and airlines): Guests can book and manage reservations without ever creating or logging in to an account (guest checkout flow). However, the system must automatically recognize returning customers via email/phone match and offer to “claim” or link their history to a free, optional account at any time. Once claimed, the account provides persistent benefits such as viewing past/future reservations, faster booking (pre-filled info), saved payment methods (PCI-compliant), preference storage, and one-click rebooking of favorites—all without requiring login for basic transactions.HYes
2.01The system must maintain a centralized, deduplicated customer database with robust duplicate prevention: automatically detect and block duplicate name/address entries during creation, prompt staff to use or update the existing record instead.HYes
2.02Provide automated inactivity alerts to administrative staff for customer accounts unused for a configurable period (e.g., 3 years), with options to archive or retain.MNo
2.03Enable fast, multi-criteria search and retrieval of any customer record across all Tennessee State Parks using customer number, last name + first name, phone number, email, address, organization name, or other key fields.HYes
2.04Allow authorized staff to view a complete 360° customer profile from any TSP workstation, including full history of reservations, registrations, programs, payments, refunds, and notes—regardless of park or entry channel.HTBD
2.05Include powerful duplicate-merge tools to combine reservation, registration, and payment histories from accidentally created duplicate records into a single authoritative profile.MNo
2.06Allow TSP administrators to add custom fields to customer profiles (e.g., preferences, special needs, geographic region) and enable tracking/reporting by those fields.MNo
2.07Provide customer flagging functionality (e.g., VIP, special attention, prior violations, no-show history) with configurable visibility and alerts.MNo
2.08Support secure, internal-only notes/comments attached to customer or organization records, visible only to authorized staff levels.HYes
2.09Generate customizable mailing-list exports and address labels (individual or batch) filtered by customer type, group affiliation, facility type reserved, geographic area, or other criteria.MNo
3.00 System Setup
3.01The system must support advanced reservations for all current Tennessee State Parks reservable products—including campgrounds/campsites, cabins, marinas (slips and storage), group camp/lodge facilities, day-use facilities (picnic shelters, community buildings, pavilions, open space venues, etc.), tours, access permits, programs/events, and any other bookable items—via phone (1-888-TN-PARKS), walk-in, online portals (tnstateparks.com and reserve.tnstateparks.com), or field application in park offices.HYes
3.02Enable complete setup and centralized management of all inventory items (campsites, cabins, marina slips/storage, group camp/lodge, day-use shelters/pavilions/venues, program slots, tour times, permit types, etc.) with comprehensive details: park location, physical address, major intersection/landmarks, directions from major roadways, parking availability/capacity, and full amenity descriptions (including but not limited to number of bed/baths, showers, playgrounds, camp store, boat ramps, restrooms, fishing access, Wi-Fi, ADA features, etc.).HYes
3.03Provide intuitive visual availability tools: interactive park maps, zoomable site diagrams, and calendar/grid views displaying real-time status (occupied, vacant, reserved, registered, held, out-of-service, or maintenance) for any selectable date range across all product types.HYes
3.04Record and automatically enforce multiple product-specific reservation rules and restrictions (e.g., ADA compliance, maximum occupants/vehicles, pet policies, boat length/beam/draft for slips, vehicle/tent pad dimensions, minimum/maximum stay, seasonal/channel-specific rules, age requirements for programs, etc.).HYes
3.05Allow users to copy or move an existing reservation to a compatible product in the same park or a different park without re-entering customer data. Customer information is global and transfers automatically. However, payments are park-specific (tied to each park’s unique MID) and cannot be transferred across parks — new payment collection is required when moving to a different park. The system must run full rule validation on the target product before confirming the action.HYes
3.06Support unlimited inventory scaling—no system-imposed limits on the number of campsites, cabins, slips, facilities, program slots, tour times, or permit issuances per park—to accommodate future additions, park expansions, or new offerings.MYes
3.07Proactively identify and display all existing reservations potentially impacted by a planned closure, out-of-service status, or maintenance hold on any product, with tools for bulk customer notifications (email/text) and easy adjustments/refunds.HYes
3.08Enable authorized staff to easily update any product record—including name, description, photos/images, rates/pricing tiers, restrictions, availability calendar, and attributes—with full version history and audit trail for changes.HYes
3.09Support flexible categorization and multi-attribute filtering of products (by park, region, type, special features: e.g., full hookups, electric/water, handicap accessible, premium/view, shaded, waterfront, lakefront, pet-friendly, group capacity) for efficient search, availability display, reporting, and customer-facing filters.HYes
3.10Facilitate secure electronic import/migration of all historical reservation, inventory, and occupancy data with 100% integrity—no loss of past bookings, customer linkages, payment history, or occupancy records during transition.HYes
3.11Provide highly configurable, date-range-specific business rule engine, including:

* Variable minimum/maximum stay requirements by season, day of week, sales channel (online vs. field/in-park), product type, or demand period.

* Ability for authorized administrators to temporarily override or reduce minimum stays for targeted date windows (e.g., lower a 7-night cabin minimum to 2–3 nights for a specific unsold block to maximize occupancy).HYes
3.12For day-use facilities only (shelters, pavilions, community buildings, open space venues, etc.), support configurable half-day and full-day reservation options with separate pricing structures and time windows (e.g., morning/afternoon slots).MYes
3.13Allow administrative, maintenance, or special-purpose holds on any product/site/slip/facility/program slot/tour time: automatically remove from public availability inventory during the hold period, prevent new bookings, require mandatory staff comments explaining the reason, and log full audit trail (user, date/time, hold/release details) for accountability.HYes
3.14Integrate with the State's centralized general ledger (via Edison or successor system) to automatically post and classify all revenue transactions, fees, payments, refunds, and journal entries for each reservable product/inventory item, ensuring accurate real-time financial reconciliation and compliance with State of Tennessee accounting standards.HTBD
4.00 Map System: The system will provide for a map system for each park with the following requirements:
4.01System must provide interactive, real-time maps for all reservable products (campsites, cabins, marina slips, day-use facilities) in both the public online reservation portal (reserve.tnstateparks.com) and staff/admin back-end portal that displays availability status (occupied, vacant, reserved, registered, held, out-of-service) via color-coding, symbols, or alphanumeric indicators.HYes
4.02System must include a detailed main park map for each Tennessee State Park, showing the entire park layout with clickable/zoomable points of interest (e.g., campsites, cabins, marina docks, day-use areas, trails, entrances) that reveal sub-maps or details for specific areas like camp loops or slip sections.HYes
4.03All maps must adhere to Tennessee State Parks branding standards, incorporating provided style sheets for colors, fonts, logos, icons, and visual elements to ensure consistent look and feel across online portal and staff interfaces.HYes
4.04Each map must include a north-facing compass arrow, with all maps for a particular park oriented in the same direction (north at the top by default) for user consistency and ease of navigation.MYes
4.05Maps must feature a clear, customizable legend explaining all symbols, colors, and icons (e.g., green for available, red for occupied, icons for amenities like restrooms, showers, playgrounds, boat ramps, Wi-Fi, ADA access, waterfront), positioned visibly and accessibly.MYes
4.06Maps must be fully interactive: support zoom, pan, rotation (with snap-back to north), hover/click pop-ups for site details (e.g., attributes like hookups, dimensions, rates, photos, real-time status), and filters (by type, features, availability) in both online and staff views.MTBD
4.07System must display proximity of reservable products to park attributes on maps (e.g., distance to restrooms, laundry, dump stations, playgrounds, recreation areas, entrances, roadways, water features), aiding customer selection and staff management.MYes
4.08For marina-specific maps, each slip/storage area must show dock/slip number, status (via symbols/color-coding), and clickable tables/pop-ups with attributes (length, width, depth, covered/uncovered, water/electric hookups, etc.).MYes
4.09Maps must integrate with real-time availability data, updating dynamically as reservations are made/canceled/held, with options for date-range views in grid or map format.HYes
4.10System must support map editing and uploads via Content Management System (CMS), allowing authorized staff to add/update park maps, site diagrams, geospatial data, and amenities without coding.MYes
4.11All maps must be mobile-responsive, WCAG 2.2 AA compliant (e.g., alt text for images, high-contrast legends, keyboard navigation, screen reader support), and optimized for offline viewing/download (e.g., via PDF export or app integration).HYes
4.12System must provide API/GIS integration for accurate geospatial data (e.g., via ArcGIS or similar), enabling overlays of trails, boundaries, elevations, and external data sources for enhanced mapping.LNo
4.13Public online maps must prioritize user-friendly discovery: searchable by park/region, with directions integration (e.g., Google Maps links) and real-time filters syncing with reservation search.HTBD
5.00 Online Reservation Website
5.01WorldPay/FIS credit card processing integration (pending procurement confirmation)HYes
5.02ValuTec gift card processing integration (and any subsequent gift card solution) supporting physical and e-gift cards (sale, activation, reload, deactivation, redemption, refund application)HYes
5.03The system must support multiple payment options including credit card, gift card, Apple Pay, Google Pay where applicable.HYes
5.04Real-time availability displayed on tnstateparks.com showing live, up-to-date status for all reservablesHYes
5.05Flexible booking options including groups, transient stays, and multi-product types in one transaction (e.g., overnight + event + boat rental)MNo
5.06Automatic suggestion of alternate booking dates when requested dates are unavailableMTBD
5.07Automated invoices sent to customersHYes
5.08Adaptability for future needs including addition of new parks, new amenities, and modern hospitality features (text confirmations, self check-in, Trip Protection)HNo
5.09Fully web-based solution (no native mobile app required)HYes
5.10Configurable business rules and policiesHYes
5.11Non-editable audit log for all invoice/transaction changes capturing user, date/time, and modification detailsHYes
5.13Integration with Google Analytics 4 (GA4) for marketing data and conversion trackingHYes
5.14Open API support for third-party integrations (marketing tools, analytics, GIS, Edison/PeopleSoft, revenue management, OTAs, discount verification, etc.)HTBD
5.15Consistent application of TSP branding guidelines across UI, receipts, automated emails, and reportingHYes
5.16Delivery of urgent notifications to reservation holders via email, phone, or text when stay is impactedH
5.17Compliance with current ADA website accessibility guidelines (WCAG 2.2 Level AA)HYes
5.18Centralized customer database containing contact information, reservation history, purchases, payments, refunds; field staff update capabilityHYes
5.19Unique transaction identification number assigned to every transactionHYes
5.20Optional donation round-ups or fixed donations added to each transactionMYes
5.21Easy configuration and application of reservation fees and/or change fees on modificationsHYes
5.22Multilingual supportMNo
6.00 Online Reservation Website & Capabilities
6.01Secure internet site(s) for public reservations, event/program registration, gift card purchases, donations, payments, and secure user profilesHYes
6.02Website available 24/7 (except scheduled maintenance), mobile-first/responsive, TSP look/feel, TSP-approved content, clickable links to TSP/other approved sitesHYes
6.03Help center with reservation information and FAQs; explain rule-based failures and suggest modifications (e.g., calendar link, min-stay notice)MNo
6.04Multi-park search by desired features, date range, nights (park name, region, facility type, amenities, park features); direct link into reservation processHYes
6.06Support multiple payment types online, including partial payment with gift card and balance via credit card/other gift cardHYes
6.07Compatibility with common browsers (Internet Explorer, Chrome, Firefox, Safari, Mozilla)HYes
6.08Compliance with WCAG 2.2 Level AA ADA website guidelinesHYes
6.09Event calendar functionality that populates upcoming events with registration links on TNStateParks.comHYes
6.10Auto-fill city/state using postal code on all online forms (reservation, registration, donation, payment)MYes
6.11Online modification/cancellation via customer account with automatic application of change/cancel fees per TSP rulesHYes
6.12Support for discounts including promo codes per TSP business rules/policiesHYes
6.13Business rules (max/min LOS, restricted check-in/out) integrated into online availability views (calendar grid & map)HYes
6.14Ability to make standalone or add-on credit card donationsMYes
6.15Posting of photos for all facilities visible to customersMYes
6.16User information not required until end of booking process or when accessing reservations w/ 'guest checkout' option; login possible anytime without losing dataHYes
7.00 Modern Hospitality Features
7.01Trip Protection add-on for advanced reservations as a percentage of total reservation costMTBD
7.02Round-up / donation options available in both backend UI (portal) and onlineMYes
7.03Support denial/regret tracking: Automatically log and categorize instances where potential reservations are denied (no availability/restrictions) or regretted (guest abandons despite availability), including reason codes, lost revenue estimates, date/product/channel details; provide reports and dashboards to analyze trends and inform pricing, inventory, and rule adjustments.MTBD
7.04Housekeeping app to help staff effectively organize and communicate cabin availabilityMYes
7.05Dynamic Pricing adequately communicated to customers and field staffHYes
7.06Ability to hide included fees / taxes from customer display for internal accounting purposes (e.g., designate portion to reservation fee account while showing total)MYes
7.07Receipt / confirmation add-to-wallet support for Google Wallet and Apple WalletMTBD
7.08Text notifications and self check-in capabilityMNo
7.09Online discount validation using ID.me or similarMTBD
8.00 Data Integration and Analytics
8.01The system shall provide a secure, RESTful API for exporting reservation, customer, revenue, and operational data (e.g., campsites, cabins, retail transactions) to third-party data analytics tools, enabling integration without custom development on the analytics side.HYes
8.02API shall support real-time data synchronization and streaming (e.g., via webhooks or event-driven updates) to allow third-party analytics tools to access live data for timely insights, such as occupancy trends or revenue forecasts.HYes
8.03The system shall support standard data formats for API responses, including JSON, XML, and CSV, to facilitate easy ingestion by third-party analytics platforms.MTBD
8.04API access shall include robust authentication and authorization mechanisms, such as OAuth 2.0, API keys, or role-based access control (RBAC), to ensure secure data sharing with authorized third-party analytics providers.HTBD
8.05The system shall provide comprehensive API documentation, including endpoint descriptions, request/response examples, error codes, and rate limiting details, to enable seamless integration by third-party developers.MTBD
8.06API shall allow querying of historical and aggregated data (e.g., reservations over time, customer demographics) to support advanced analytics, including AI-driven natural language queries processed by third-party tools.HYes
8.07The system shall support scalability for high-volume data requests, with performance benchmarks (e.g., response time < 2 seconds for standard queries, handling 10,000+ requests/day) to accommodate growing park operations data.MYes
8.08API shall include logging and monitoring features to track integration activities, errors, and usage metrics, integrable with third-party analytics for auditing purposes.HYes
8.09The system shall enable configurable data access policies, allowing TSP staff to define what data subsets (e.g., anonymized customer data) are exposed to third-party analytics tools.MYes
8.10API shall support testing environments (e.g., sandbox) for third-party analytics integration development, without impacting production data.LTBD
9.00 Reporting
9.01Real-time At-a-Glance Dashboard: Displays current and forecasted occupancy rates, revenue trends, booking conversions, top-performing parks/facilities, and key alerts (e.g., low inventory, high abandonment, exceptions). Filterable by park, facility type, date range, user role; includes drill-down, date comparison, and KPI visualizations.HYes
9.02Occupancy & Utilization Report: Detailed current/historical/future occupancy by park, facility (campsites, cabins, day-use, marinas), date, season, day-of-week, channel. Includes % filled, RevPAS (Revenue Per Available Site), predictive forecasts, and YOY comparisons.HYes
9.03Arrival/Departure & Daily Operations Report: Sortable/printable lists of arrivals, departures, registered guests, assignments, permit details (site number, guest name, due-out date). Supports bulk large-font camping permits; includes date-range filters and comparisons.HYes
9.04Revenue & Financial Summary Report: Daily/weekly/monthly/annual totals by source (reservations, retail/POS, fees, donations, gift cards), park, facility, revenue category. Integrates with Edison/PeopleSoft chart of accounts; shows Dynamic Pricing impacts and date comparisons.HYes
9.05Transaction Detail & Audit Report: Full history of reservations, changes, cancellations, refunds, payments with unique ID, user/timestamps, non-editable logs. Drill-down for disputes/overrides; supports PCI/financial auditing and date-range comparisons.HYes
9.06Dynamic Pricing & Rate Performance Report: Tracks adjustments (base vs. demand-based), impacts on bookings/occupancy/revenue, ADR (Average Daily Rate), yield (actual vs. forecast). Segmented by season/day/lead time/facility; includes comparisons to prior periods.HYes
9.07Booking Pace & Lead Time Report: Analyzes advance booking patterns vs. historical norms by park/facility/channel. Highlights demand acceleration/slowdown; supports date comparisons and forecasting inputs.HYes
9.08Cancellation, No-Show & Refund Report: Details rates, no-shows, refund amounts/reasons, revenue impact. Segmented by timing/facility; includes AP check refunds and date comparisons.HYes
9.09Marina-Specific Operational Report: Slip/storage occupancy, transient vs. seasonal, utility readings, renewals/payments, late fees, past-due accounts, boat validation logs; supports date-range and comparison views.HYes
9.10Ad-Hoc/Custom Report Builder: User-friendly tool for TSP staff to create/save/schedule/export custom reports using any database fields (filters, sorting, drill-down, aggregation). All future report requests (if data exists in system) included in proposal scope at no extra cost.HYes
9.11Gift Card & POS Operational Report: ValuTec activity (sales/reloads/redemptions/refunds/balances), aged/slow-moving retail inventory, inventory on hand, blind count reconciliation; integrates Accrual Accounting with date comparisons.HYes
9.12Exception & Alert Report: Operational exceptions (overrides, holds, overbooking attempts, high abandonment, urgent notifications); includes audit trail and date-range filtering.HYes
9.13Accounts Receivable Aging Report: Real-time AR aging summary by customer/invoice, categorized (current/30/60/90+ days past due), amounts due, original posting dates; supports export and date-as-of selection.HYes
9.14Advanced Deposits Report: Tracks collected deposits, application to reservations, refunds/credits; aged/deferred revenue breakdown with date-range and comparison views.HYes
9.15Forecasting Report: Predictive occupancy/revenue/demand based on pace, historical trends, external factors; includes what-if scenarios and YOY comparisons.HYes
9.16Pace Reports: Daily/weekly booking pace vs. prior years/seasons by park/facility/channel; highlights variances and supports forecasting inputs.HYes
9.17Refunds Report (including AP Check Refunds): All refunds (credit card, cash, gift card, AP checks) with original transaction details, approval logs, amounts, reasons; date-range and comparison capabilities.HYes
9.18Journal Vouchers & SAR Report: Folio creation with speed charts, attached docs, error checks; tracks Special Arrangement Request discounts/donations against budgets; audit trail and date filters.HYes
9.19Transactions (Payments & Refunds) Report: Detailed payment/refund history by type, date, park, facility; includes debits/credits breakdown for reconciliation.HYes
9.20Debits/Credits Details Report: Ledger-style view of debits/credits by account, transaction, date; supports trial-balance-like summaries, reconciliations, period comparisons, and full revenue traceabilityHYes
9.21RevPAS / RevPAR Performance Report: Revenue per available site/room (RevPAS/RevPAR equivalents) by park/facility/date; includes ADR, occupancy, yield, and historical comparisons.HYes
9.22Inventory Attributes Report: Details on product attributes (hookups, ADA, pet policy, etc.), usage trends, aged inventory; supports filtering.HYes
9.23Audit & Compliance Reports: Non-editable logs of system changes, user actions, overrides, holds; supports PCI/financial audits, security reviews, and date-range exports.HYes
9.24Taxes Report: Collected taxes by type (state/local), park, facility, transaction; reconciliation with payments.HYes
9.25Discounts & Promo Report: Usage of discounts/promo codes, impacts on revenue/occupancy, redemption rates by code/type/facility; includes comparisons to non-discounted periods.HYes
9.26Reconciliation/Deposit Reports: Daily/weekly/monthly/date parameters deposit reconciliations (credit card, cash, checks), batch totals vs. system records; supports Edison integration and date-range audits.HYes
9.27Customer & Marketing Reports: Aggregated guest demographics, repeat visits, geographic tracking, survey summaries; mailing list exports and channel effectiveness.HYes
10.00 Retail POS and Stock Inventory Management
10.01The POS module must be fully integrated in real time with the central reservation, customer, gift card, and accounting systems (Edison/PeopleSoft), eliminating duplicate data entry.HYes
10.02Support multi-location management with a system-wide view for central office oversight and individual park-level views; enable easy addition of new retail locations as parks expand.HYes
10.03Provide a modern, touch-screen optimized interface with customizable quick-sale buttons (minimum 20 configurable), tabs, and product menus for fast transaction processing.HYes
10.04Support multiple payment types in a single transaction (split tender): cash, credit/debit, gift card, check, and mobile wallets (Apple Pay, Google Pay).HYes
10.05Automatically calculate change due, apply taxes correctly by location/product type, and handle tax-exempt transactions with audit trail.HYes
10.06Support barcode scanning (manufacturer UPC and system-generated), price lookup (no transaction created), and quick product search.HYes
10.07Allow creation and sale of package/kit items (e.g., gift baskets, camping bundles) as a single transaction line item.LNo
10.08Support non-scheduled rental transactions for items such as boats, kayaks, or equipment in configurable time increments (e.g., 30 minutes, 1 hour, half-day, full day, multi-day).HYes
10.09Require unique employee login for every transaction; track performance and maintain full audit trail by cashier, device, and location.HYes
10.10Automatically calculate and apply correct taxes based on transaction type, item category, location-specific rates, and state rules. Fully automate Tennessee sales tax holidays (e.g., back-to-school exemption) by date range, exempting qualifying items (clothing ≤$100, school supplies ≤$100, computers ≤$1,500) without manual intervention.HYes
10.11Allow entry of customer tax-exempt numbers/certificates at checkout; record and store for audit. Generate tax exemption detail reports (by customer, transaction, date) and combined breakdowns (sales tax, grocery, liquor, occupancy, local, etc.) on one report.HYes
10.12Support sale of variable-quantity items (e.g., gallons of gas, pounds of bait/ice, bulk merchandise) with accurate unit pricing, inventory deduction, and tax calculation.HYes
10.13Allow addition of products to cart via barcode scan, one-touch quick buttons, price lookup, or manual entry; no additional steps after scan or button press. Associate minimum 25 manufacturer UPC codes per product for flexible scanning.HYes
10.14Permit combining retail purchases with refundable reservable facility fees (e.g., boat rental deposit refund) in a single transaction; print originating park name on all receipts.MNo
10.15Support multiple-item returns/refunds in one transaction; optional no-receipt printing; allow auxiliary printers (e.g., desktop when receipt printer fails).HYes
10.16Allow authorized users to correct transaction errors post-completion, print correction/seasonal messages on receipts, and update messages over time.HYes
10.17Record and reconcile deposits (including multi-day deposits); scan/attach deposit proof; flag warnings if deposits are missing or unmatched.MYes
10.18Generate interim/end-of-shift subtotal reports by payment method (cash, check, credit, debit, gift card), receipt number range used, and variance alerts for reconciliation.HYes
10.19Provide real-time perpetual inventory tracking at each retail location with independent stock levels; allow park-level entry of new products available to other locations within the same park.HYes
10.20Automatically deduct correct quantity on sale (e.g., 1 can vs. 6-pack vs. case); support stocking at different unit levels (single, pack, case) with accurate cost/quantity updates.MTBD
10.21Support inventory transfers between locations (same park or different parks); allow receiving location to merge into existing items to prevent duplicates.HYes
10.22Allow adjustments for vendor returns, write-offs, damaged/spoiled items, park use, or transfers; require reason code and maintain full audit trail.HYes
10.23Calculate weighted average cost price (Total Price Paid incl. shipping / Total Quantity) for each item; aggregate across all purchases.LNo
10.24Provide dollar-value valuation of inventory (by item, category, location, or entire park) at retail and cost; support partial physical counts without affecting full inventory.HYes
10.25Generate downloadable blind count sheets (PDF/Excel) with barcode, description, price, and blank count column; support hand-held scanner upload (contractor-provided device).HYes
10.26Produce reports showing inventory entered, transferred, damaged/spoiled (cost, quantity, total), and audit history of all movements/adjustments.HYes
10.27Allow grouping/viewing of like items (e.g., apparel, food, marine supplies) for field users; provide low-stock alerts and reorder reports.HYes
10.28Provide comprehensive POS-specific reports: Operator Collection Report, POS Detail Report (by category/sub-category/product), Sales by Cashier, Voids/Discounts/Refunds Report, End-of-Shift Reconciliation, and marina/gas reports (gallons purchased, price/gallon, coupons/tickets, discounts).HYes
10.29Generate daily deposit Reconciliation Reports comparing system totals to actual cash/check/gift card deposits, with variance alerts.HYes
10.30Support real-time and scheduled reporting with export to Excel, PDF, CSV; include drill-down to individual transactions.HYes
10.31Track and report employee performance metrics (sales per cashier, voids/refunds by user) with audit trail for accountability.HYes
10.32Maintain non-editable audit logs for every transaction, void, refund, discount, price override, and Inventory Adjustment (user ID, timestamp, reason, device/location).HYes
10.33Be fully PCI DSS compliant; mask credit card numbers on all receipts/screens (show last 4 digits only). Require manager approval (logged reason) for voids, refunds, discounts over configurable amount, and price overrides.HYes
10.34Support secure employee access levels with unique logins; restrict price changes, voids, and refunds to authorized roles only.HYes
10.35System shall support penny rounding for cash transactions, automatically adjusting totals to the nearest 5 or 10 cents and logging both original and rounded amounts per TSP rounding rules.HYes
11.00 Gift Cards
11.01System must be able to process gift cards issued under the State's FIS contract or any subsequent contract providing gift card services. Gift cards will be sold at all park locations, TSP central office and online and sold in any amount approved by TSP. There can be a minimum amount for cards sold online. Gift cards must be accepted by the system for payment at all TSP retail locations and through reservation website.HYes
11.02Gift card processing must include a security PIN number to help prevent fraudulent use of gift cards when redeeming online - PIN provided by ValuTec.HYes
11.03System must seamlessly integrate previously issued gift cards that have an outstanding balance. Gift cards must not expire. This includes the previously issued gift cards as well as gift cards sold under this contract.HYes
11.04Ability to scan and keep gift card data (number) at the time of the transaction and retain info on invoice from gift card purchase or redemption.HYes
12.00 Refund and Cancellation Processing
12.01The system must support refunds and cancellations through multiple channels: self-service online cancellation form (reserve.tnstateparks.com), call center (1-888-TN-PARKS), and in-park processing by staff, in accordance with TSP product-specific policies (e.g., cabins: no refund within 14 days of arrival; campsites: full refund minus $5 fee if cancelled ≥2 days prior).HYes
12.02Automatically enforce TSP cancellation policies by product type, date window, and fee structure; calculate refund amount (full, partial, or zero) based on policy rules, reservation fees, taxes, and any non-refundable portions; display clear refund preview before processing.HYes
12.03Process refunds to the original payment method (credit/debit card) where possible, in full compliance with PCI DSS (no storage of full card data post-authorization, secure tokenization for refunds); require manager approval and documented reason only for exceptions (e.g., compromised card, post-closure invoice adjustments).HYes
12.04Allow override to issue AP check refunds (via Edison integration) only when original card refund is not feasible (e.g., card compromised, expired, or TSP policy requires); generate and track required Finance & Administration electronic form for approval and transmission.HYes
12.05For cash refunds (e.g., in-park walk-up or same-day cancellations), display an alert to verify till balance covers the refund amount; prevent processing if till total is insufficient.HYes
12.06Require complete customer information (name, contact, reservation details) before processing any refund; flag and prevent completion if data is incomplete.HYes
12.07Support refund to gift card (ValuTec or successor) as an option when original payment was gift card or customer requests; apply funds back to card balance with audit trail.MYes
12.08Post all refunds correctly to the original invoice/reservation record, even if the invoice is already closed in the system; no manual ledger adjustments required.HYes
12.09Maintain full, non-editable audit trail for every refund (user, timestamp, reason, approval if required, original transaction ID, refund amount/method, policy applied, channel used).HYes
12.10Generate comprehensive refund reporting, including: all refunds (by date range, park, facility, channel, method, amount), AP check refunds flowing through Edison, no-check refund transactions, gift card refunds, and policy-driven denials; support export (Excel, PDF, CSV) and drill-down to individual records.HYes
12.11Provide real-time refund status tracking for guests (e.g., via email confirmation, online account view) and staff alerts for pending high-value or exception refunds requiring review.MYes
12.12Allow TSP administrators to configure refund rules, fee schedules, approval thresholds, and exception workflows (e.g., auto-approve routine policy refunds, escalate others).HYes
13.00 Marina Registration, Management & Map System
13.01System must be capable of creating monthly and annual contracts for all marinas (slips and dry dock storage) by phone or walk-in. Contracts must also be able to be completed through a field application in a park office.HYes
13.02Ability to set up marinas and slips/storage within each marina. Ability to view maps or other visual representation of slips occupied, vacant, and available for reservation or allocation. Record marina location (e.g., address, park, major intersection), including directions from major roadways and information about parking facilities, equipment, and amenities.HYes
13.03A detailed main park map showing the entire marina. Each map will have a north compass arrow, and all maps will be oriented in the same direction, preferably north at the top. Each slip on the map must show dock and slip number, and status through symbols, color-coding, and/or alphanumeric characters.HYes
13.04Each slip will have a table showing all attributes (length, width, depth, covered/uncovered, water, electric, TV, internet, etc.) activated by clicking the marina slip on the map.MTBD
13.05System must provide the option of displaying facility (dates and slips) availability in a grid format for the following attributes: All slips and dry dock storage on a grid format; From any starting date in the past to the maximum window in the future; For any date range within the maximum reservation window; Indicate whether Open, Reserved, Registered, or Held; Operator has the option to print out any portion of the grid; Take reservations using full sum or periodic billing; and view and record utility meter readings.HYes
13.06System must allow for payment online for slip rental deposits and monthly payments via credit card, debit card, or check. Customers must be able to print a receipt which includes the slip number(s) covered by the payment. System must provide instant confirmation of payment on slip rentals as well as email confirmation. Slip/storage rental system will fully integrate with all other segments of the system, including other stores and services, through the system's integrated shopping cart.HYes
13.07System must allow for transient slip rental and reservation by park visitors (walk-in park only).HYes
13.08For each marina, the system must maintain a list of slip holders and their assigned slip number, location, and contract number. Slip holder information must include customer name, address, phone number, boat make, and boat registration number. The system must have the flexibility to allow park staff to modify this information. System will manage marina's accounts receivable from mooring/slip/storage rentals.HYes
13.09System will send email courtesy notifications to monthly renters and provide for automatic billing for weekly/monthly/annual rental rates against renter's credit card. System shall provide for management of past due payments on rentals of slip/storage rentals and collect proof of insurance.HYes
13.10System must collect a boat registration number, a boat type, and boat length. Staff will also have the option of entering other boat characteristics including make, model, and name of boat into the system.HYes
13.11System must allow each park to generate contract agreements with customer-specific information that can be sent or emailed to slip holders each year. The contract agreements will be customizable with park-specific information as well. System must have the flexibility to add new slips as they are constructed.HYes
13.12For each park, the system must maintain a log of annual slip contracts that are mailed, those that have been paid, and contracts that are awaiting payment. The log must be viewable and printable from the park office. System must calculate the appropriate fees for each slip and account for any discounts. System must allow park staff, with the appropriate permission levels, to override prices or length limitations.HYes
13.13System must allow a dock holder to pay for a renewal online or at the park office and allow for prorated refunds on state slips based on the departure date.MYes
13.14System must generate a report that provides information on which slip contracts have been paid online. The information must include slip holder information, slip number, payment date, and payment type, and confirmation that the contract terms were accepted.HYes
13.15System must allow staff to transfer a reservation from the existing slip to a vacant slip and allow contract agreements to be viewed/printed from a field workstation.MYes
13.16At the beginning of each year, the system must automatically generate contracts for those customers who had a slip contract at the end of the previous season, except for those persons whose slip expired based on the specified rotation.MYes
13.17For slips that are not paid in full on a specified date, the system must calculate a late fee and add it to the amount due. Reporting that shows if a customer is past due.HYes
13.18System must have the ability to allow for reservations to be taken for transient slips, easy extension of stays, transfers and early departures, collect customer information for slip rentals, including customer name, address, phone number and email address, collect transient boat information that includes registration number, boat name, beam, length, draft and electric hook-up required and generate a confirmation email for each reservation.MTBD
13.19System must calculate fees based on the length of the boat, with a minimum per night fee regardless of boat length.HYes
13.20System must provide printable and sortable reports for the marina, including arrival reports and Occupancy Reports. These will be available for a date or date range selected by the user.HYes
14.00 Credit Card Processing
14.01System will interface with the state-contracted merchant services provider (e.g., WorldPay/FIS or successor) for all credit card transactions and must be fully PCI DSS compliant. Software must handle credit card payments through central reservations, all in-park sites, and the reservation website.HYes
14.02System must accept Visa, Mastercard, Discover Card, American Express, and bank-issued credit cards backed by any of these networks.HYes

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 .