Specifications include, but are not limited to: MET Transit seeks to improve the efficiency and effectiveness of its demand response
transportation services by the acquisition and implementation of a centralized web-based
scheduling and dispatching software solution, including support for fifteen (15) vehicles. The
proposed software system described herein must enhance capabilities to manage customer
files, generate schedules, and assist or eliminate the reliance on manual schedule production.
The proposed solution must reduce manual duplication of data, increase accuracy of statistical
reporting, billing, and provide management with higher levels of oversight in the operations area.
The system must be able to import existing RouteMatch databases for ease of implementation.
2.2 Scheduling and Dispatching Software Systems – Technical Specifications
The successful software solution will contain the following elements:
2.2.1 Client Database
A. Build New Client Database Files
The selected vendor, as soon as practical after notice to proceed from MET Transit,
shall be responsible for providing a data “template” in order for staff to begin compilation
of information necessary to complete the client database elements required for use in
scheduling, trip assignment, and reporting.
B. Data Conversion of Existing Database
The selected vendor, as soon as practical after notice to proceed, will evaluate current
database, hosted by RouteMatch, and develop appropriate data conversion process that
converts existing information into a compatible format for use in the scheduling and
dispatching software solution.
C. Database Attributes
Client database shall be capable of providing a full range of data elements for each
client in the system. Information shall include, at a minimum, full identification including
gender, address, contact details, third party/emergency contacts, disability status,
mobility aides used, required accommodations, caregiver, language spoken by client,
program affiliation, and payee options including third-party contracts. Additionally,
system shall permit assignment of various demographic codes, such as senior, youth,
D. MET Transit will not define the required fields nor dictate the format for data to populate
the client database fields. Vendor shall be responsible for providing a fully functional
client file suitable to transit system needs.
2.2.2 Client Database Functionality
A. Customer Look-Up
The customer database shall provide functionality to allow customer service agents to
readily look-up client records for edit, trip-booking, etc. Search capabilities should be
based on customer name, and identification number, or similar characteristic. When
looking up a customer, auto-complete features are desirable to minimize user input.
B. New Client Entry/Customer Edits
System shall be capable of registering new clients, capturing information about addresses, disability type, space requirement, load/unload time, fares, payment options,
eligibility conditions, funding sources, etc. while a customer service agent has the new
customer on the telephone.
System shall permit edit of all fields in a customer records in a real-time basis and shall
permit suspensions (temporary) of service.