Point of Sale Enterprise Replacement Services

The Vendor is required to provide point of sale enterprise replacement services for include:- General system architecture & business continuity
1. Web-based/SaaS model:
• Point of sale (POS) must be a 100% web-based, cloud-hosted software-as-a-service (SaaS) solution.
• The system must be accessible via standard, modern web browsers (e.g., google chrome, Microsoft edge, apple safari) without requiring local server installations, VPNs, or proprietary desktop clients.
2. Updates and maintenance:
• All system updates, security patches, and feature enhancements must be managed by the vendor server-side, ensuring zero downtime for the city operations during standard operating hours.
3. Offline operational capabilities (desired):
• The platform's business continuity capabilities in the event of an on-site network or fiber connectivity failure.
• The city desires a system that can gracefully handle basic front-counter check-ins or queue transactions securely until connectivity is restored.
- Enterprise integrations & API requirements
1. Oracle e-business suite (EBS) r12 interface:
• The solution must be fully compatible with the city’s central oracle EBS r12 environment.
• The platform must support direct or automated interface pathways with oracle general ledger (GL) and accounts receivable (AR) modules.
• This integration must seamlessly handle daily revenue categorization, split-tender accounting strings, cash/credit reconciliation, and tax journals generated across the division.
2. Comprehensive API documentation:
• Provide complete, unredacted API documentation as part of their proposal.
• Documentation must include exhaustive reference guides, supported authentication methods, network/connection requirements, rate limits, error handling schemas, supported data formats (e.g., json, xml), security controls, and proven production integration examples.
3. Noteefy messaging integration:
• The solution must feature a seamless, real-time API integration with noteefy (automated tee-time waitlist and notification assistant).
• The system must automatically sync tee-sheet inventory, cancellations, and real-time availability with noteefy to allow automated booking notifications to be sent to golfers without manual staff intervention.
4. Identity management / okta single sign-on (SSO) (highly desired):
• The city highly prefers a platform that natively supports enterprise single sign-on (SSO) via okta using standard SAML 2.0 or oidc protocols.
• This integration will be utilized by finance and parks & recreation administrative staff to access the platform securely using corporate city credentials.