1. General 1.1 The vendor shall provide a scheduling and dispatch software solution to support ADA and conventional shared-ride demandresponsive microtransit services including: ∙ Service design and configuration tools ∙ Staff and customer self-serve trip booking and account management tools ∙ Scheduling, dispatch and service supervision tools ∙ Operator tools ∙ Data collection and reporting tools Mandatory 2. Service Design and Administration 2.1 The solution shall be able to support the delivery of several service types concurrently, including: ∙ Pre-booked and same-day, door-to-door ADA service ∙ Same-day microtransit for ambulatory riders. This may be hometo-hub or stop-to-hub. Mandatory 2.2 The solution shall support various service zones, and permit one or more service type to operate within each zone. Mandatory 2.3 Valid pick-up and drop-off locations shall be defined and updated by JTA from time-to-time within the system for different service types and/or zones. For example, ADA service is provided within 3/4 mile of JTA fixed route service. Mandatory 2.4 The characteritics of different service days, including specific dates operated, and the hours of service for each service day and service type, shall be configurable within the system. For example, certain areas within Jefferson County are only serviced on specific days and at specific times. Mandatory 2.5 The solution shall account for fleet information and different characteristics of the fleet and each vehicle, including but not limited to: ∙ Quantity of vehicles of a given type ∙ Full seated capacity ∙ Maximum capacity, and capacity configurations including storage capacity of mobility devices (e.g., 5 seated + 2 mobility devices, OR 3 seated + 3 mobility devices) ∙ Ramp and/or mobility device lift ∙ Vehicle range ∙ Valid service zone(s) and or service type(s) Mandatory 2.6 Access to administrative features and functionality within the software shall be limited based on user account access privileges. Mandatory 2.7 Staff shall be able to create, modify and remove users and assign user privileges within all aspects of the system. Mandatory 2.8 Interactions performed by users shall be logged by user account, time, and nature of the change. Mandatory 3 Trip Booking 3.1 The solution shall include a trip booking and customer information portal to facilitate customer service and trip requests submitted to JTA Staff, herein referred to as the "Staff Portal". Mandatory 3.2 The Staff Portal shall be available only to authenticated and authorized JTA staff. Mandatory 3.3 The Staff Portal shall be intuitive and simple to use. It shall require minimal keystrokes and clicks to support efficient use. Important 3.4 The solution shall include a self-serve trip booking and customer information portal to provide customers with the ability to make trip requests and inquire about their personal accounts, herein referred to as the "Self-Serve Portal." Mandatory 3.5 The Self-Serve Portal shall be available on web-enabled devices including personal computers, tablets, and smartphones. Mandatory 3.6 The Self-Serve Portal shall be intuitive and accessible to a wide range of users, including users with disabilities. The vendor shall provide documentation related to accessibility features (e.g., conformance with WCAG). Mandatory 3.7 The Self-Serve Portal shall support multiple languages and provide users with options to change the language. Important 3.8 In the following requirements, "Users" refers to both JTA staff using the Staff Portal and clients using the Self-Serve Portal. Where a requirement is only relevant to one group or the other, "JTA Staff" or "Clients" will be used respectively. For information 3.9 Users shall be able to book, view, and modify pre-booked and same-day trips. Mandatory 3.10 JTA Staff shall be able to configure rules related to when cancellations can be made. For example, cancellations within 2 hours of a trip may only be made by staff. Mandatory
