HomeMy WebLinkAboutResolution - 6185 - Contract - Multisystems Inc.- MIDAS-PT Software For Citibus - 02/11/1999Resolution No. 6185
Item No. 21
February 11, 1999
RESOLUTION
BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF LUBBOCK
THAT the Mayor of the City of Lubbock BE and is hereby authorized and
directed to execute for and on behalf of the City of Lubbock, a contract for MIDAS -PT
software for Citibus, by and between the City of Lubbock and Multisystems, Inc., and
related documents. Said contract is attached hereto and incorporated in this resolution as
if fully set forth herein and shall be included in the minutes of the City Council.
Passed by the City Council this 11th day of February 1999.
AY SITT , AYO
ATTEST:
KaythieCary
rnell
City Se
APPROVED AS TO CONTENT:
Mildred Cox
Director of Tansportation
APPROVED AS TO FORM:
�,cC�<.- oLe /da�
William de Haas
Competition and Contracts Manager/Attorney
Uccdocs/Multisystems. Res
January 14, 1999
Resolution No. 6185
Item No. 21
February 11, 1999
CONTRACT
THIS CONTRACT, made this //y4--- day of February, 1999, by and between City of
Lubbock, Texas, a municipal corporation (Citibus), hereinafter referred to as "BUYER," and
MULTISYSTEMS, INC., hereinafter referred to as "CONTRACTOR,"
WITNESSETH:
WHEREAS, BUYER desires to engage the CONTRACTOR to furnish and deliver to
BUYER certain computer software to manage information related to the management and
operation of BUYER and to provide to BUYER certain implementation and training services
necessary to effectively utilize and operate the computer software for BUYER at its facilities
located in Lubbock, Texas, such software and services being part of an undertaking by BUYER
known hereinafter as the "INFORMATION SYSTEM PROJECT," or simply "IS PROJECT",
NOW, THEREFORE, BUYER and the CONTRACTOR do mutually agree and consent
as follows:
ARTICLE I - EMPLOYMENT OF CONTRACTOR
1.1 BUYER hereby agrees to engage the CONTRACTOR, and the CONTRACTOR
agrees, to furnish and deliver to BUYER the specified computer software and services hereafter
set forth in connection with the IS Project.
ARTICLE II - CONTRACTOR'S RESPONSIBILITIES
2.1 The CONTRACTOR shall furnish and deliver the computer software described in
Appendix A; train appropriate BUYER personnel to operate and maintain the system; and
provide support, including but not limited to user documentation, operations manuals, and
guarantees and warranties.
2.2 Training, as detailed in CONTRACTOR'S Proposal dated October 20, 1998, shall
consist of 10 days on-site, covering a curriculum as described in Section 4 of the aforementioned
document. Additional training shall be provided at an agreed upon price per day.
2.3 Delivery of the computer software shall be at the expense of the CONTRACTOR.
ARTICLE III - BUYER'S RESPONSIBILITIES
3.1 BUYER shall maintain close liaison with the CONTRACTOR during the course
of the Project. BUYER will designate Dean Lewis to serve in the capacity of Contracting
Officer. The Contracting Officer will be the person designated to serve as the liaison with the
' CONTRACTOR. The designation of any other person as the Contracting Officer shall be
' transmitted, in writing, to the CONTRACTOR.
3.2 BUYER shall provide the necessary computer hardware and related equipment
' necessary to operate the software furnished under this Contract and to allow the CONTRACTOR
' remote dial -in access for diagnostic purposes. The CONTRACTOR shall consult with BUYER
to insure that the hardware to be procured meets the requirements of the software.
' 3.3 BUYER shall make available appropriate personnel for consultation and training
II by the CONTRACTOR. The CONTRACTOR shall submit to BUYER, within a mutually
1I
it
agreeable time period, a proposed training schedule for review and approval by BUYER. All
' specific training dates shall be confirmed with at least two weeks advance notice.
ARTICLE IV - TIME OF PERFORMANCE
4.1 The delivery of the IS computer software and services of the CONTRACTOR
shall commence upon execution of this Contract and shall be undertaken and completed in such a
sequence as to assure expeditious completion of the IS Project. Unless otherwise agreed to by
the CONTRACTOR and BUYER, the delivery of the IS computer software and the services to
be provided shall be completed in accordance with the schedule attached hereto as Appendix B.
ARTICLE V - ACCEPTANCE
5.1 Upon completion of software and hardware installation and training of BUYER
personnel, the CONTRACTOR will certify that the system is ready for final acceptance. The
acceptance period shall extend for 30 days from this notification. Any problems found during
this period shall be corrected by the CONTRACTOR after which time BUYER will verify their
correction. Acceptance of software for the purpose of payment shall occur at the end of this
period but not earlier than 10 days following correction of the last critical problem identified, and
not later than when the system has been used in a live environment for 30 days.
ARTICLE VI - COMPENSATION
6.1 BUYER will pay the CONTRACTOR for performance of its obligations
hereunder the flat lump sum of $66,940 in accordance with the schedule attached hereto as
Appendix C.
6.2 If BUYER requires any additional work not required under this Contract, such
additional work shall be performed at such costs as set forth in the cost schedule attached hereto
as Appendix C or at a fixed price to be agreed upon in writing between the BUYER and the
CONTRACTOR.
ARTICLE VII - NOTICES
7.1 Communications in connection with the IS PROJECT and the CONTRACTOR's
work under this Contract shall be in writing and shall be delivered to the Officer(s) or
employee(s) of BUYER and of the CONTRACTOR designated to receive such communications.
Telephone calls may be used to expedite communications but shall not be official
communications unless and until confirmed in writing.
7.2 All notices or other communications to either party by the other shall be deemed
given when made in writing and deposited in the United States Mail, postage prepaid, addressed
as follows:
To BUYER Mr. John Wilson
Citibus
PO Box 2000, 801 Texas Ave.
Lubbock, TX 79457
To CONTRACTOR
Mr. Keith Forstall
Multisystems, Inc.
10 Fawcett Street
Cambridge, MA 02138
ARTICLE VIII - WARRANTIES
8.1 The IS computer software shall be subject to the warranty provisions of the
Software Maintenance and Support Agreement, attached hereto as Appendix D.
8.2 The commencement of the warranty/support period shall occur at the earlier of
system acceptance or the beginning of use in a production environment.
ARTICLE IX - CONFIDENTIALITY
9.1 The CONTRACTOR shall treat as confidential all BUYER information to which
it may become privy which is not otherwise in the public domain or available through other
channels.
ARTICLE X - PERSONNEL
10.1 The CONTRACTOR warrants and represents that it has or shall retain, at its own
expense, all personnel required to perform the obligations under the Contract.
10.2 All of the work and services required hereunder shall be performed by the
CONTRACTOR, or under its supervision, and all personnel engaged in performing the
CONTRACTOR'S obligations under this Contract shall be authorized under appropriate state
and local law to perform same.
10.3 During the period of the Subcontract and one (1) year thereafter, neither party
shall solicit for hire any employee of the other associated with the performance of this
Subcontract; nor shall either party hire such employee without the express written consent of the
firm who employs that individual; nor shall such employee, if hired with such consent, be
assigned to participate directly on any Subcontract or options contained within.
ARTICLE XI - INDEMNITY
11.1 Each party to the extent permitted by law shall indemnify, keep, and hold
harmless the other party, their agents, officials, directors and employees against all injuries,
deaths, losses, damages, claims, suits, liabilities, judgments, costs, and expenses, which may
accrue, arise out of, or result from, in whole or in part, the first party's acts or omissions,
including acts or omissions of its employees, servants and agents.
ARTICLE XII - TITLEMIGHTS TO IS COMPUTER SOFTWARE
12.1 Adequate documents for securing title and/or rights to use the IS computer
software shall be provided by the CONTRACTOR to BUYER and signed by BUYER before
delivery of the IS computer software to BUYER.
ARTICLE XIII - PATENTS/COPYRIGHTS
13.1 The CONTRACTOR shall agree to save, keep, hold harmless and fully indemnify
the BUYER and all its employees or agents from all damages, costs, or expenses, including
attorneys fees, that may at any time arise, or be set up, in law and/or equity, for any infringement
of the patent rights, copyrights or violation of trade secrets of any persons(s), company or other
entity as consequence of the use by BUYER or by any of its employees or agents, of the IS
computer software, manuals or other items or articles supplied under this Contract.
13.2 If any claim based upon an infringement of a patent or infringement of a
copyright, or violation of a trade secret is asserted against BUYER by virtue of its use of the IS
computer software or any manuals or other items or articles supplied under this Contract,
BUYER shall notify the CONTRACTOR of the assertion of any such claim within sixty (60)
days of BUYER's receipt of formal notice of the assertion thereof. The CONTRACTOR shall
have the exclusive right, if it so chooses, to control and direct the investigation, the defense of the
settlement of such claim, and the CONTRACTOR shall receive the cooperation and assistance of
BUYER in the investigation and defense of any such claim.
ARTICLE XIV - COMPLIANCE WITH FEDERAL, STATE AND LOCAL LAW
14.1 In the performance of its obligations pursuant to this Contract, the
CONTRACTOR and its subcontractors shall comply with all applicable federal, state and local
laws, regulations and rules.
ARTICLE XV - APPLICABLE LAW
15.1 Except as otherwise set forth herein, this Contract shall be governed and
construed in accordance with the laws of the State of Texas. All actions, whether sounding in
contract or in tort, relating to the validity, construction, interpretation, and enforcement of this
Contract shall be instituted and litigated in the courts of Texas, and in no other.
ARTICLE XVI - EXTENT OF CONTRACT
16.1 This Contract represents the entire and integrated agreement between BUYER and
the CONTRACTOR, and supersedes all prior negotiations, statements, instructions, and
representations or agreements, whether written or oral.
16.2 At the election of BUYER, the invalidity or illegality of any provision(s) of this
Contract, as determined by a court of last resort of competent jurisdiction, shall not affect the
validity of the remainder of this Contract, and this Contract shall remain in full force and effect
as if such illegal or invalid provisions were not contained herein.
1
THIS CONTRACT executed the day and year first above written
MC LYB or MULTISYSTEMS, INC.
Windy Sitton, M or
Keith W. Forstall, Vice President
A ST:
Kaythie arnell, City Secretary
APPROVED AS TO CONTENT:
Mildred Cox, Director of Transportation
APPROVED AS TO FORM:
�"• — '& '/V"
William de Haas, Competition and Contracts Manager
no
M
A TEST:
dim SSiryt �X�„ ��
Sandra C. Hatch, Notary (� ��/l 0 1�1
11
11
11
11
n
11
1
�i
1
1
1
APPENDICES
Appendix A - Description of Software
Appendix B - Project Schedule
Appendix C - Payment Schedule
Appendix D - Software Maintenance and Support Agreement
11
IAPPENDIX A: DESCRIPTION OF SOFTWARE
I
1
1
1
1
1
1
1
1
1
MIDAS -PT
- R14�»rI= `; rawEassw, ,
Product
Overview1sPIAT U/2 CLEVELAND STATE UKW MDI A --
an13
Real -Time Paratransit
Scheduling System
MIDAS -PT
Real --Time Paratransit Scheduling System
Multisystems' MIDAS -PT is the most advanced
automated paratransit scheduling software
system available today. This state-of-the-art
system features real-time, fully automated
capabilities that include client registration,
automatic geocoding, mapping, interactive and
batch trip scheduling, brokering for multiple
carriers, dispatching, and other helpful features
that users will find straightforward and simple.
With MIDAS -PT, users are able to run a user
friendly Microsoft WindowsTM based graphical
user interface (GUI) application that is built upon
a widely used commercial Geographic
Information System (GIS). The GIS platform
used by MIDAS -PT is TransCAD® 3.0 from
Caliper Corporation of Newton, MA.
TransCAD is uniquely qualified for transit and
other transportation GIS applications and is
being used by the FTA to build the National
Transportation System Map.
The Windows version of MIDAS -PT has been in
production use since September 1995. It is the
first fully -integrated application in the transit
industry to combine paratransit/ADA service
management with fixed -route telephone -based
customer information within a common, full -
featured GIS environment. Customers across the
country from New England to Florida to
California are testimony to the power of
MIDAS -PT. And, you'll be especially pleased
that our product is backed by a staff whose
paratransit experience is second to none.
MIDAS -PT
Calls Schedules dispatch Reports
Tables Administration
yelp
..
�(216�555-1412 MICFFAELS BRIANJ -- ----
� .,
-Q
,.1,14-01, r 9
,yA
obiHlyAids:
. Iig %ity-Code-3
"
�g
LiFgiConditions:
i
rf�wsoftisl Care Attendee[ Y
al
-. RUN BI0.FOR SCHEDULE 05128/1995
:ETA Ron: -Td s'. Address -..
--.Zone Ste?..Dev.
9:50-
9:55
'
- 0:00 PU03 01/2 CLEVELAND STATE UNN
0807 A
't1
0:05:
-- ---------- ---------
0.40
- --- - - - - --
w A,..
�._
0:45 11:00 0003 01/2 PUBLIC LIBRARY
0783 A -015
_ y,L10
0:50 PU09 01/0 lXtyEIJWD STATE UNIV
11:00 11:00 0004 01/0 SOCIETY BANK(E.CLEV
OBDI A
0987 A 000
' ' 16-
1105
- - - - - - - - - - - - - - - - - -
- - - - - - - - - -
4� ,
.17:55-
2=80 PU05 01/2 PUBLIC LIBRARY
2:05
0783 A
-*`-
1210 1230 DO05 01/2 LAUSCHE STATE OFFICE
2:15
0783 A -020
- - - . ` - - - - - - - - - - - - - - -
- - - - - - - - - -
4 7i U
.
3:00
Trip Functions ----- Stop Functions
i
Run Functions
k
Hold Comment Up.
Change '-Bless
M� Dbox
Client Name MiCHAELS. BRl/W
Request rime 12.300
V
— '
�
t—.��_w l Arldror '
Delete
Pick Up Address PUBLIC LIBRARY
Pick Up Time 1200- . ;.
&W of Pun:. 810 .
Dislancor 29.278109
Can.Trip Bleat.
NEW !
Pick Up Note
ease
Drop ON Address LAUSCHE STATE OFFICE
,_
. _. .....
Drop OR rime IL-10 - -:
- OK Cancel - tAM
YALID? SAVE -
Drop Ott No
- . Trip Nola
-
rleLo
Ambulatory Passengers 1
Fr
Passes ars usm cha�irs 2 �
Cloca; I "1 .•
jMep scale: t Inde - 0.15647 Miles (1:1914)i
- -
The MIDAS -PT system is an ideal system for
paratransit services that want to assign trips to
vehicles while the customer is on the telephone.
MIDAS -PT allows the reservation agent to quickly
visualize one or more scheduling solutions in both
a driver manifest and a map display format. The
reservation agent can simply accept the computer's
top choice or may negotiate with the customer to
select the solution which best meets both the
customer's needs and the operator's productivity
objectives. Batch scheduling offers a powerful
alternative that frees up call -takers to handle more
calls where that is -the -best solution. - Both
interactive and batch algorithms use parameter -
driven objective functions that model your service
policies.
Another powerful feature of MIDAS -PT is its
intelligent use of map displays to provide
extremely quick displays of any part of a route.
Complete map control allows you to zoom in or
out to any scale, pan in any direction, and point -
and -click on any stop to get detailed passenger
information.
MIDAS -PT is designed to handle the demands of
paratransit operations that include not only
standing orders and advanced reservation trips, but
also a high volume of same day will -calls, add-ons,
and cancellations. Extensive features designed to
help dispatchers keep pace with actions on the
street are the product of years of experience in a
real-time environment. MIDAS -PT provides
effective dispatching tools for responding to real-
world situations.
These capabilities have been enhanced through the
addition of digital communications capabilities
with mobile data terminals, reducing the workload
of dispatchers by automatically transmitting
schedule changes to drivers. Mobile
communications also facilitate the collection of
statistical and performance data on services
provided, which greatly reduces clerical labor
while _ providing greater accuracy.. _ These
capabilities may be enhanced with optional
peripherals such as card readers, odometer readers,
and Global Positioning System (GPS) receivers for
automatic vehicle location (AVL).
MIDAS -PT is adaptable to many different
operating environments. It can be used for service
routes and general public dial -a -ride. When
installed with the optional MIDAS -CIS, MIDAS -
PT can handle completely integrated planning and
scheduling of feeder service to scheduled line haul
services, including full fixed route itinerary
planning. And many of our customers use
MIDAS -PT in a brokerage environment that
involves some form of decentralized or
subcontracted service network. Why don't you
call us and see how we can put MIDAS -PT to work
for you?
For further information contact:
Multisystems, Inc. • 10 Fawcett Street • Cambridge, MI 02138 • Tel: 617-864-5810 • Fax: 617-864-3521
Page 2
MIDAS -PT at a Glance
FUNCTIONS FEATURES
Client Registration Look -Up by Name, Phone, or ID (or Partial Entry)
Auto or Manual ID Assignment
Address/Phone Sections for Home, Mail, and
Emergency Contact
Language
Gender
Birthdate
Social Security Number
Extensive ADA eligibility application and certification
tracking
Mobility, Impairment, Disability Codes
Up to Five Sponsors for customer
Expiration/Suspension
Date Last Served
Common Addresses Rapid Booking Feature
"Home" for Rider Home Address
Assists in Efficient Scheduling to High Traffic
Destinations
Photos or Schematics to Show Access Features
Registered Trips Used as Templates for Trip Requests
Created Automatically When Trip is Scheduled
Can Be Used To Restrict Riders to Prior Approved
Trips
User -Specified Threshold for Automatic Deletion
Automatic Geocoding Used to Auto Locate Client Addresses,
Common Addresses, Trip Origins and Destinations
Address Match, Nearest Intersection, or Point -and -
Click on Map
Used to determine ADA -Eligibility of Client & Trip
Mapping Used to Visually validate ADA Service Area
Determination
Used to Evaluate Route Alternatives
Used to Locate Candidate Runs Near a Trip Request
Page 33
MIDAS -PT at a Glance
FUNCTIONS FEATURES
Schedule Specification Master Schedule (Standing Orders, Wait List)
Dated Schedule (Standing Orders, Occasional Trips)
Working Schedule (Copied from Master or Dated)
Handles Holiday Schedules
Run Specification Start and End Times and Zones
Intermediate Time Points and Zones (Waypoints)
Fixed or Floating Lunch Breaks
Fixed Stops for Point Deviation Services
Master, Dated and "What -If' Schedules
Trip Reservations- Reservations for All Trips Taken on -Same Screen
Registered Trips Speed Data Entry on Most Trips
Double Booking Warnings Displayed
Standing Orders (Subscription Trips) — Start and
End, Interim Cancel, Include on Holidays (Y/N)
Occasional Trips (Schedule Now or Later)
■ to 14 (or more) Days in Advance
■ Same Day
Group Trips
Computer Map Display to Determine
ADA Eligibility of Trip via 3/4 -Mile Transit
Route Corridor Overlays
Automated, Real -Time, Scheduling Completed While Client is Still on Phone
Interactive Trip Scheduling
2 Minute Average - Reservation through Scheduling
Interactive, Deferred, or Batch Scheduling
Users May Ask the System for Run Suggestions
User May Accept, Modify, or Override Suggestions
Suggestions Displayed in Stop List; on Computer Map
Scheduling Algorithms Based on:
■ Zone to Zone Travel Time
■ User -Specified Service Standards
■ Vehicle Capacity
■ Operating Hours
■ What's Scheduled Already
■ Vehicle Availability and Waypoints
■ Decision Rules
Page 4
EM
MIDAS -PT at a Glance
FUNCTIONS FEATURES
Brokering Can Support Multiple Carriers
May Assign to Preferred Carrier or Run
Trips may be billed to a Sponsors; Dual
Sponsorship Supported
Dispatching Dispatchers Have Scheduling Access to Today's Trips
May Schedule "ASAPs" and "Will -Calls"
Real -Time Updates to Vehicle Schedules
Dispatcher Monitor Prompts for Pending Actions
Optional Interface with Mobile Data Comm. Systems
Confirmations and May Cancel Trips for any Schedule
Cancellations
May Place Temporary Hold on Standing Orders
May Indicate Type of Cancellation (Early, Late,
No -Show, Missed Trip) For Reporting
Actual Trip Data Input Run -Specific In-Service/Out-of-Service Times
Run -Specific In-Service/Out-of-Service Odometers
Stop -Specific Times and Odometer Readings
Driver and Vehicle Assignments
"On -the -Fly" Customization of Data Input Screen
Optional Data Capture from in -vehicle MDT's
Driver Tracking Badge Number, Personal information
All training, testing, licensing, accident, etc. info
Incident Tracking Optional Complaints, Accidents, and
Commendations Module
All Incident Reports Available as Printouts
Security and User Logging Each User Has a Login and Security Level
Multiple Security Levels
Scheduling Actions Traced and Logged by User ID
Page 5
MIDAS -PT at a Glance
FUNCTIONS
Utility Functions
Applicant Eligibility Reports
Client Information Reports
Run Sheet Reports
Reservation Reports
Performance Reports
Administration Reports
Auditor (Service Exceptions
Reports)
Language
FEATURES
Archiving, Purging, File Reorganization
Cards to be Issued
Presumptive Approval Report
Agency Activity
ADA Eligibility Determination
Full Client Listing
Mailing Labels (Zip)
Mailing Labels by Name
Driver Manifests
Daily Vehicle Listing
-Holding Run Report - -
Taxi Run Report
Unblessed Runs
Unconfirmed Trips
Major Generators Report
Subscription Listing
Fixed Route Report
Quality of Service Report
Passenger Performance Report
Rider Statistics Report
Scheduler Activity Report
Time Distribution Report
Operator Performance Report
Performance Statistics Report
Revocations Report
Turndown Log
Cancel and No Shows Report
Service Exception Summary
TransCAD macro language, "C"
Hardware/Operating System PCs with Novell or Windows NT server, Windows 95 or Windows
for Workgroups clients
Page 6
Client Registration
MIDAS -PT maintains both a client file, for reservations and scheduling, as well as application
records that contain original application information. Thus, a customer may have applications
on-line for several programs, as well as a single consolidated client record.
Detailed information in MIDAS -PT client record includes client name, client ID, three
address/phone sections (including zip code), language, gender, birth -date, social security number,
PCA requirement (the system distinguishes between companions and personal care attendants),
mobility code (e.g., walker, wheelchair), impairment code (e.g., blind, deaf), disability code (e.g.,
arthritis, seizures), up to five sponsors, expiration/suspension date, date last served
(automatically tracked by the system), and additional program -specific or confidential
information. Several windows are used to allow entry of extensive information pertaining to
applications to register for ADA certification.
Client Registration (page A2)
Mobility Limdations --------- — --- -- ------
YES _NO
f — r Can board IiR equipped bus T -
r r Can board bus without lift
r r Can travel to nearest bus stop
r r Can wait at bus stop
r r Can identify carred bus
r r Can handle coins & tickets
r r Can grip railings 8 handles
r r Can balance while seated
r r Can read/hear/understand directions
INext Close I
Professional Verification (page B3)
Health Cara Professional._..
Onto Signed
License Number F— State I
Name
SII
Address
L1yst.ZIP
Phone
Agency l
Pmlession
r Licensed Physician
r Licensed Physical Therapist
r Certified Rehabilityafion Specialist
r Licensed Social Worker
r Licensed Podiatrist
r Licensed Optometrist
C Other RTA approved professional
r Certified Audiologist
r certified Psychologist
r'Nurse (LPN OR F"
r Registered Occupational Therapist
'., r Certified Speech Pathologyist
r Independent Living Specialist
`. hent Ra9letraUon (Page qll-t3..
Gw.t
wm.
neemr
cnrsw..ar
w.. r
sal Tuo nne
Wsrk �.1 �r TDD r—
E.er9m yCnM — __�_�.
rr.m.
I'
wun
r T
Work.- �ca�r 7W
11.1.t -hip r ❑*—�
Ends P..l d F-
A2 N M AS Bt -Be B7 I
Three of the Client Registration Screens
Page 7
Visitor applications, presumptive approvals, and other aspects of the MIDAS -PT eligibility
module ensure full compatibility with ADA. Note also that the system permits automatic or
manual assignment of client Ids. Soundex searches on name are supported.
When searching for a client record, a user may enter a last name or an ID or may enter a portion
of either the last name or ID (as a request parameter), and then select the desired client from the
ensuing list of clients that meet the request.
Once a client record is found, a user may update the record, confirm or cancel a scheduled trip
(from any schedule), book a trip request, or review the tripmaking history of the client.
Each time a client's file is modified, the update time and date is recorded on the file. A "history"
file logs the operator identification of the person who made the change. This information is
available on screen. This client history display includes extensive client statistics, including data
on number of trips, cancellations, service refusals, and no-shows for the current period, the
preceding period, the current year, and the preceding year.
Common Addresses - -
The common address feature allows the use of a code (usually an abbreviation) to represent
frequent origins and destinations, including senior residences, hospitals, clinics, shopping
centers, etc., and identify a specific entrance or pick-up as well. For example, the Main Entrance
of Mass General Hospital could be abbreviated MGHMAIN. When a common address is entered
in an address field, the entire address (including any notes regarding a specific entrance or pick-
up/drop-off point) and zone are automatically entered by the system.
When first entered into the system, common addresses may be categorized by type (e.g., hospital,
shopping, dialysis, municipal, etc.) When booking a trip, the user then selects the desired type
code, and then the specific location. Both the location type and the location itself are selected
from pulldown lists.
Type
Name
Address
ty/S VTp .
Phone F_ ext
Zone
Comment
A Common Address Window
The benefits of using common address codes include less data entry and fewer errors. In
addition, the system will match -up concurrent ridesharable trips with the same stop at the same
time if the stop address of the two trips are exactly the same; otherwise, the system will treat
them as different stops. Use of a common address code ensures exact matches.
Page 8
Automatic Geocoding
Automatic geocoding is provided with MIDAS -PT. With automatic geocoding, the entry of an
address of a new client or new trip will result in the system finding the latitude/longitude and
zone in which the address resides. Lat/longs are used by MIDAS -PT' scheduling algorithms.
The geocoding involves acquiring a Tiger File (of street addresses, available from the US Bureau
of Census and private vendors) for each county represented in the service area, and loading this
information into TransCAD. Alternatively, we can and have used data from ArcInfo as the
source for the MIDAS -PT street segment (geocoding) file.
The following is an illustration of MIDAS -PT displaying the location of a home address. Note
that on any MIDAS -PT map, there is full control over viewing functions such as zoom or pan.
MIDAS -PT MAP
GCRTA Service AreaI-1-1
Address Location Using MIDAS -PT Maps
Page 9
Registered Trips
A registered trip is a unique trip that a particular client has made before. As each client makes a
new trip, MIDAS -PT automatically adds that trip to that client's list of registered trips. In
addition, all notes (e.g., ENTRANCE IS AT REAR) remain with the registered trip record.
Once a client has a registered trip (or trips), any such trip can be used as a template for entering
the trip request (for a standing order or an occasional trip) by simply selecting the trip from a list
of that client's registered trips. This list is automatically displayed for the user whenever the user
chooses to book a trip request for a client. Similar to common addresses, the use of registered
trips reduces data entry effort and time and reduces errors. Once a registered trip is selected (all
you have to do is double click on the correct trip on the list), all the user need do is enter the
appropriate booking code in the appropriate day field(s), the arrival or departure time of the
going trip, and the departure time of the return trip to complete the trip reservation (see below).
There is no limit to the number of registered trips a rider may have. To keep this list manageable
and useable, the system will automatically delete registered trips that have not been reflected in
actual trip -making after a user-specified period (e.g., 96 days):
Master, Dated, Working, and Historic Schedules
In MIDAS -PT, there are four type of schedules: master schedules, dated schedules, working
schedules, and historic schedules.
Master schedules keep track of standing orders (i.e., subscription trips) on specific days of the
week. There are seven master schedules: one for each day of the week. This process can be done
as far in advance as is desired. Standing orders in the master schedule that have been temporarily
canceled or have expired are not copied into the dated schedule. Trips that have not yet been
scheduled onto a run are not copied either, which allows the user to "wait -list" subscription trip
requests. Requests for standing orders may be flagged as to whether or not they are effective on
holidays, and will not be copied if you create a dated schedule as a holiday.
Dated schedules are normally created from master schedules. Once a dated schedule is created
for a particular date, occasional trips may be scheduled directly into this schedule immediately
following the trip reservation (i.e., in real-time mode, while the caller is still on the phone).
Optionally, the scheduling of the trip can be deferred. If the dated schedule has not yet been
created, a trip reservation for that date is automatically put into a holding run for subsequent
scheduling when that dated schedule is created.
Working schedules can be used for training exercises, and "what if' planning.
Historic schedules reflect schedules from yesterday back. These can be kept on-line as long as is
desired by the user.
Page 10
Vehicle Run Specification
A vehicle run in MIDAS -PT is defined as a continuous period or piece of work. Each run is
identified by a unique run number; this run number can be used to identify the run with a specific
subcontractor or service area, if required. Runs are first registered giving information on
operating times (pull-out and pull -in) and vehicle type (which determines seating capacity).
They may also be assigned to certain service areas, by specifying the zones in which they are
expected to be at any time during the operation of the run. These "waypoints" are used by the
scheduling algorithms to evaluate the suitability of runs that may not yet have any trips assigned
to them.
Registered runs can then be copied into any of the daily master schedules (see preceding page).
If service hours of a scheduled run are modified, the system verifies that the changes do not
conflict with trips already scheduled into that run.
Run Name �-
Garage
F—
Vehicle Type
_
Start Time
I
Zone
End Time
I—
Zone
Time
(
Way
Zone
Points
Time
Zone
F_
Schedule; OK Cancel
The Registered Run Window
Special runs are also available for trips assigned to taxis or other undedicated vehicles that may
be utilized. Holding runs (for trips to be scheduled at a later time), cancellation runs (for trips
that are canceled), and refusal runs (for trip requests that cannot be accommodated) are
automatically created by the system.
Page 11
Trip Reservations
The trip reservation process is used to define the following information for each request: client
number, client name, pickup address and zone, destination address and zone, number of
ambulatory and wheelchair positions required (including PCAs and companies), requested day
and time, trip purpose, trip sponsor, etc.
Trip requests can be of several types: subscription, advanced -reservation occasional, and same-
day occasional. The system also handles "will -call" return trips. Depending on the request type,
each trip is sent to the appropriate schedule. Reservations for occasional trips may be entered as
far in advance as is necessary (i.e., MIDAS -PT accommodates the ADA requirement to be able
to accommodate requests up to 14 days in advance of the trip). Requests for far-off dates (e.g.,
for holidays or other special occasions) can also be accommodated. For ease of use, reservations
for all these different trip types are taken on the same screen.
When a client calls to reserve a trip for a given day, the reservation agent searches for the client
record either by client ID or name. When the client record is found, the computer displays a
summary information record of the customer so that the reservation agent can complete positive
identification of the customer, then double clicks to select the correct client. MIDAS -PT then
displays a list of that client's registered trips (see above). In most cases (about 80% of the time),
all the reservation agent needs do is to choose from the list the registered trip that matches the
client's request; the system then automatically copies the registered trip data into the trip request
screen. The system then prompts the reservation agent to identify the day of the week (if the trip
is to be taken within the next seven days) or the date if the trip date is beyond the next seven
days, and revise the requested pick-up or drop-off time, if needed.
Pick-up Address--
r Landmark`
_—
Ph. r_ --
Street HONE
i city
,
Notes
Drop -o(1 Address
r Landmark
Phone—,
Street 1614W. Superior Ave
City Cleveland
Notes
Note
,Trip Type....--. _ ----
—
(' Specific Date Day of
Week
G Mand- Drderi
-
—SUNA
fldwONt
Trip Tins—
Pick-up fi- Dropr.-011
rPiTUESTime
I Book
Time EDSched:
SeheTHU
DK
Cancd
A Trip Request Screen
For new trips not yet on the registered trip list, there are other shortcuts available to the
reservation agent (e.g., the use of "H" as for the client's home and a common address code as the
Page 12
destination). For other addresses, the system automatically provides geocoding. If a trip is
already reserved in the same schedule, the system advises the operator who can determine if the
second reservation is an error, a duplicate request, or a legitimate modification to a previous
request. This feature is very useful in eliminating double and/or conflicting bookings.
MIDAS -PT also accommodates scheduling of various kinds of group trips. For example, you
can set up a list of persons who are eligible to ride on a certain type of subscription service (for
example, residents of an elderly high rise who may elect to go on a weekly shopping trip) and
then select which persons will be on board on each service day.
Selecting Passengers for a Group Trip
Page 13
Run ±
Flet.. Am-
Mep Detail
Map Detai
Not Travelling
Traveling on Run
r 216)555-1213 Passenger 01
+
216)555-1212 John Q. Public
216)555-1214 Passenger 02
_ _ 216)555-1218 Passenger 05 _
216]555-1215 Passenger 03
11216)555-1225
Add» 216)555-1223 Passenger 09
216]555-1216 Passenger 04
216]555-1218 Passenger 06
216]555.1221 Passenger 07
ALL»
2161555-122 Passenger 08
Passenger 11
«RemovE
«ALL
Cancel
- OK
W
Selecting Passengers for a Group Trip
Page 13
Automated, Real -Time, Interactive Trip Scheduling
However, the scheduling of trips may be done either immediately (with the customer on the
phone) or at a later time (if the call -taking and scheduling functions are separated). Scheduling is
accomplished automatically by the system on an interactive basis, with the system generating run
suggestions, and showing the user how the trip would look in each run and the before and after
productivity. This process is described below.
Scheduling Method---- ---- .
Caii6le 'a 216—n
j
G Extended Feasible Suggestions
C' Any Available Time
C' Holding Run
f Taxi
(' Select Specific Run:
4207
H208
120 i
2100
4211
4212-
H213
212 H213
214
H215 +
Diop-off Window 20 mins early to r mins. late
OK Cancel
Scheduling Options
The reservation agent has several options in asking for a feasible run suggestion. A standard
suggestion observes the normal request time windows. Extended feasible suggestions double
these windows, which is useful if the requested time is already heavily scheduled. A third option
is to look for any available time, which may be useful for discretionary trips and last minute
requests.
In coming up with these run suggestions, MIDAS -PT uses a set of scheduling algorithms that
look to user-specified service standards (maximum travel time, average load time, etc.), vehicle
capacity, vehicle type, operating hours, as well as vehicle availability and location based on trips
already scheduled. In particular, the scheduling algorithms use the following prioritizations:
■ The trip must be assigned to a vehicle run appropriate for the request; for example:
motorized wheelchairs can't be handled by sedans, and the vehicle must have the
available capacity to serve the additional trip.
■ The trip must be assigned to a vehicle run that is in operation during a period
compatible with the request.
Page 14
■ The inclusion of the new request with previously scheduled trips must be possible
considering both time and geography, i.e., it cannot exceed user-specified service
standards for maximum travel time, acceptable pick-up/drop-off windows, and other
service standards.
■ The detour necessary to add the new request to an existing trip is to be minimized.
■ A large open "hole" in a vehicle schedule is to be avoided, to preserve flexibility for
future hard -to -serve requests.
■ A vehicle already in service will be given preference over an empty vehicle.
■ For immediate trips, a vehicle flagged by the dispatcher as being on standby will be
given preference.
The algorithm consists of an objective function which scores potential run options with respect to
efficiency and service quality. For each run, the computer displays the run "score", along with
pertinent statistics including productivity, slack time, and the number of trips deviating from
their confirmed departure or arrival times.
i
i
Run Start End
STA Slack Prod. OW ER
2ilG.._050...1,3311._..Ol15:;077;....:....._......._
................................................... *.
H201 0500 1300
001 094.7X
0-1 0 0
H999 0800 1200
002 083.3X
0.5 0 0 +
Run Selection Functions--,
—
IMore
Deny
Hold Taxi
Select
_
--
OK
Cancel
A Set of Run Suggestions
The travel times used in the scheduling algorithm are calculated using latitudes and longitudes of
stops together with a travel time matrix. Independent adjustments can be made for AM and PM
rush hour travel times, for each day of the week. These travel times do not include embarking
and disembarking times: "loading" times are calculated by the system depending on the number
of wheelchairs or ambulatory persons involved and added to the travel time.
The reservation agent may then inspect each suggested run with the pick-up and drop-off of the
trip being requested automatically inserted in the run list, and the before and after productivity
displayed. The reservation agent may also look at the suggested run on the map. Clicking on a
stop on the map will bring up trip status information on the customer and will highlight the other
stop(s) on the tour associated with this rider(s).
Page 15
r
ETA Reg Tri Pas:. Adress Zone Status Day
n�.cc onmo nvi �ardt7 g'.,.dale IN 29A05 B
5
19:00 09:00 D0021 01/0 Cleveland Clinic 39E14 H
19:05
19:10
19:15
19:20
19:25 09:30 D001 01/1 Main Hospital 34C12 B -005
19:30 +
Stop Movement Functions— Trip Functions
� Up Down i Move
—MAP _ _ OKCancel VALID? -
IMMENNE
The Scheduled Run List
GCRTA Service Area
A Route Map Display
Page 16
After reviewing a particular suggestion, the reservation agent may:
■ Confirm that the trip is acceptable as inserted by the system into the run; or
■ Modify the pick-up or drop-off time of any stop in the run, as desired; or
■ Check the validity of the run according to the scheduling rules; or
■ Review the next suggestion, or
■ Over -ride the suggestions all together and schedule the trip on a user -selected run.
An alternative scheduling technique is to select a run by looking at the map to determine what
runs are nearby. This is useful when schedules are full and the scheduler may need to force a trip
onto a run that does not have enough slack in its schedule.
After completing the scheduling of the going trip, the reservation agent is then led by the system
to do the same for the return trip (or each leg of the booked trip request).
Reservation agents can complete a trip booking in two minutes from the point when they pick-
up the phone to the point when they have completed scheduling both legs of the round trip.
If a reservation agent decides that there is no room on the schedule, the call -taker may "hold" the
trip for later review (by a scheduler or dispatcher); or refuse the trip request; or assign the trip to
a taxi/contractor (see next page).
Page 17
The following additional features are used by MIDAS -PT to help govern the scheduling process:
Special Run Identical Stops - The system will attempt to match two stops (from different
Scheduling trips) that have identical registered place names or identical addresses (including
Features zones) and that are reasonably close -in -time. Once these two identical stops are
linked together, the system will recognize these stops as one, i.e., if one is moved
in time (on the same run), the other stop may be moved with it.
The system will not automatically match up identical stops unless the spelling of
the street or registered place, the street number, and the zone are all exactly
identical. Non -identical stops can be manually matched together; when two non-
identical stops are forced together in this way, the system will ask for a
confirmation -- "SAME ADDRESS (Y/1q " -- at the bottom of the screen.
Anchoring - An anchored stop is one that will not be moved by the scheduling
algorithms. Both stops of a trip that is inserted by the system are not
automatically anchored but may be anchored by the scheduler. Both stops of
standing order trips become automatically anchored when they are copied from
template runs into operational runs.
Indirect Stop Movement - Two events may indirectly change an unanchored
stop's time: 1) the changing of the time for the other stop of the same trip: in
this case the system will attempt to maintain the minimum zone -to -zone travel
time by moving the second stop as the first stop is moved, and 2) the insertion or
changing of a proximate stop of a different trip. In either case, schedulers should
be aware of this indirect effect and make further corrective actions, if necessary.
Note that any indirect stop changes that are made by the system will respect the
pickup and dropoff windows that are defined by the system manager. If desired,
the anchoring of stops will prevent indirect stop movement.
Scheduler Modifications - The system's travel times will be invoked in the
automatic insertion of trips. However, the system will allow the scheduler to
manually schedule stops at times that create improbable actual travel times
among stops. Schedulers should especially take note of this with respect to the
start and end times of runs and with respect to the extra time a wheelchair
passenger needs at the pickup and dropoff locations.
Page 18
Automated Real -Time Brokering
MIDAS -PT permits the entry of contractors, contractor reimbursement rates, and hourly trip caps
and daily mileage caps per contractor. The system then can automatically and equivalently
assign trips to contractors (which would then be responsible for scheduling those trips) based on
user-specified trip and mileage ceilings. Ceilings for both standing orders and for occasional
trips may also be differentiated. As with the run suggestions, the reservation agent has the option
of approving or over-riding the system's choice of contractors.
Veh Lease Chargeback 0.0000
Cancel
The Rates Update Window
The system also generates a trip voucher for each trip that is assigned to a contractor. These may
be printed (at the contractor's office if there is a hook-up to a printer there) in a batch -run at the
end of the day, or individually, on demand as the trip is assigned. These vouchers may serve as
both an order form (for the contractor to perform the work) and as an audit trail.
Page 19
Stmt Date 01/01/1993 End Date 01/01/1994
Foot Rate 0.0000
Distance "I) 5280 Facer 1.0000
Time Rate 0.0000
Time (aeca) 60 F-- rl.0000
Baa- Charge 0.0000
sm u'ly (X) 10 Zai
a
Flat Fee 0.0000
Admin (X) I5 —
Exduaive Rate rO.0000
Mobility C -de r -
Shared Rate 0.0000
Sp. Code r-
...—..SroUP-RateD.OB00 -.
•Aevenu--Flag F_-
-
a
Noe-Ca.h 0.0000
Mileage r0
Liquidated Damm
Amount 0.0000
.. - -'-----I
0.0000 0.0000
Threshold U.00 00_
0.0000
Prompt Payment ..__._.
Discou-t Rate FO.0000
_0.0000
_.--- --_...------ ---- j
- I
Days Wall 0.0000
Veh Lease Chargeback 0.0000
Cancel
The Rates Update Window
The system also generates a trip voucher for each trip that is assigned to a contractor. These may
be printed (at the contractor's office if there is a hook-up to a printer there) in a batch -run at the
end of the day, or individually, on demand as the trip is assigned. These vouchers may serve as
both an order form (for the contractor to perform the work) and as an audit trail.
Page 19
Confirmations and Cancellations
Confirmations and cancellations are registered by first calling up the client's file and listing all
trips in the appropriate schedule(s). On this screen, a reservation agent can cancel one, several,
or all of the client's trips. MIDAS -PT allows you to identify whether the cancellation is an early
cancel, late cancel, noshow, or missed trip (noshow charged to the operator). This information is
used for statistical purposes.
Same-day cancellations are sent to the dispatch file and a code is displayed on the dispatcher's
acting screen, indicating that his or her attention is required.
G� Dated t ) Template
i
_ (late 08/02/1994
i
08/02/1994 012 Confirm 16:08D0 16:10 H:Cleve Clini 16:35 HOME
a!
Trip Function——
The
unction -- —
The Cancellation Screen
If a trip is filled on a same day basis, the dispatcher is automatically notified that the customer
needs to be called to confirm whether they still want the trip.
Page 20
Dispatching
MIDAS -PT provides complete support for the dispatcher. A dispatch monitor displays a list of
all items that require attention by the dispatcher. This includes pending pull-outs and pull -ins of
runs, runs with trips that have been added or canceled, and the earliest holding run in which there
is a trip which needs to be scheduled, and the earliest time of any trip that needs to be confirmed
with the rider. The dispatch module includes a specific set of functions designed to manage the
process of confirming with riders and drivers any last minute add-ons or other service changes.
The dispatcher has, in addition to all the scheduling capabilities of the schedulers, a separate
screen for recording actual vehicle and driver assignments, substitutions, and odometer readings.
This screen lists all changes to individual trips that must be communicated to the driver; as these
are dispatched, they are flagged and removed from the screen either individually or all together.
Specific dispatch items needing attention can be highlighted on the dispatch monitor.
- Dispatch Monitor -
Run Time Action
t
H406 09:00 Out of Service
H409 09:00 In Service
H201 10:05 Same Day Trip
H206 11:00 Cancellation
H410 12:00 Out of Service
H999 12:00 Out of Service
H403 13:00 Out of Service
H400 13:00 In Service
H411 13:00 In Service
H606 13:00 In Service
H203 13:30 Out of Service
H001 14:00 In Service
H204 14:00 Out of Service
H220 14:00 In Service
H221 14:00 Out of Service
H401 14:00 Out of Service
H402 14:00 Out of Service
H405 14:00 Out of Service
H407 14:00 Out of Service
H616 14:00 In Service
H404 14:15 Out of Service
H211 14:30 Out of Service
H507 15:00 Out of Service
+.
The Dispatch Monitor
Page 21
The Dispatching functions contain screens and commands which allow the dispatcher to:
■ Record events that occur on the road.
■ Keep track of schedule changes that must be conveyed to drivers.
■ Keep track of last minute fill-ins and other schedule changes that must be confirmed
with riders.
■ Move easily to scheduling, dispatching, and customer confirmation functions.
■ Monitor all pending actions that a dispatcher must perform on a Dispatch Monitor
(shown above).
Run� � Start Time 0550 End Time 1330
Vehicle Type 96 Wheelchair Capacity IJ Seating Capacity 20
n...., n: ... r -ti n..—
PU 09:00- - 2903 Ridgedalt, Clevetand - -
DO 09:45 (110:001614 W. Superior, Cleveland
utSery 13:30
Dispatch HiLite NoHiLite Schedule OK Cance
The Dispatcher's Run List
As reservation agents update the database (e.g., with cancellations and same-day request),
dispatchers instantaneously view these changes. Moreover, the Dispatch Monitor ensures that
dispatchers are automatically prompted any time a reservation agent or other user makes any
change to today's schedule. This ensures that the dispatcher will be aware of any action that must
be taken to inform either drivers or riders of changes that have occurred. More specifically, the
dispatch functions allow the following control over same-day schedule activities:
Page 22
Scheduling
■ Automatically adjust a vehicle's schedule if the driver is running late; the computer
will adjust all stop times based on running the vehicle's schedule as tightly as
possible until it is back on schedule.
■ Identify the earliest wait -listed trip request that should be scheduled.
■ Schedule same day trip requests (into schedules which reflect actual vehicle
schedules as adjusted by the above procedure).
■ Identify a vehicle as being on standby in a particular zone; this will be displayed on
the Dispatch Monitor to assist in identifying vehicles available for ASAP
assignments.
Dispatching - - - - - - -
■ Record each vehicle into and out of service, together with the actual times and
odometer readings.
■ Record vehicle and/or driver changeouts that occur on the road.
■ View on the Dispatch Monitor each change in a driver's assignment that needs to be
communicated to the driver.
■ Record the dispatch of each change to a driver assignment as the information is
communicated.
Customer Confirmations
■ Identify the earliest trip which has been scheduled on a same-day basis that needs to
be confirmed with the rider.
■ Record confirmation of same day trip assignments with the rider as they take place.
Page 23
Trip Data Input
The system allows the entry of run -specific in-service and out -of -service times and odometer
readings, driver assignments, and vehicle assignments, as well as stop -specific times and
odometer readings. With the implementation of mobile data terminals, this process is automatic
and the screen is used to verify information on the progress of the run in real time.
Dated Schedule HZJ'' t -. Time
Odowelm
Time-OdawNr
Nen N202 ± Grays Out 0615
0112
Fint Pickup 0630 : 0152
GoaOe In 1259
0405
lest Diopel1. 1250 0395
Dri 00241 ±
eet
5cheduled Lip CuNm
Twee 1D Name
Cancel
NoShow
Actual '... Daly
Time Odomatm Minn Code Cash P .... no s
0630 PU01 Public. Joseph
rP
F-
�.
0613 D00Public. Joseph
0715 PU02 Public, John
0715
Ir
r
Irr
E
0720 PU03 Public, Joy
I
P
I
0735 PU04 Public. Jo,dan
F
F_
I
0755 D002 Public, John
0010 D004 Public. Jaden
I
Fr
.....
0015 -DOM Public. Joy-
_- - _ - _. - - -
- P
I
0830 PUGS Public. Joni
li-
-�
OF -1
The Run Posting Window
Incident Tracking
MIDAS -PT includes an incident tracking system for complaints, accidents, commendations, etc.
Input screens exist for the complaint and response. Users may review an existing incident report
-- on screen or printout -- by specifying the incident date, client ID, or both.
Reports and Listings
MIDAS -PT Scheduling provides the capability of printing many management and operational
reports. In addition, there is a built in query capability, described later.
The Reports Menu has the following options.
■ Applicant Eligibility
■ Client Information
■ Run Sheets
■ Reservation
■ Performance
■ Administration
■ Auditor
■ Call -a -Lift
Page 24
Each of these options present a dialog box with options from which to choose. The system
displays an online version of the report for you to peruse. If you want to print a hard copy of the
report, click the Print icon or take the Print option from the menu.
Applicant
Applicant eligibility reports include the following:
Eligibility
■ Cards to be Issued
Reports
■ Presumptive Approval Report
■ Agency Activity
■ ADA Eligibility Determination
The Client
Client information reports include:
Information
■ Full Client Listing - Called the Rider List, this is an alphabetical list
Reports
of all the clients in your database.
■ Mailing Labels (Zip) - This is a listing of all the clients by Zip
Code. When the online portion is displayed, all data for the client is
shown, but when you print, only the names and addresses will be
printed in order by zip code.
■ Mailing Labels by Name - This is a listing of all clients by last
naive. When the online portion is displayed, all data for the client is
shown, but when you print, only the names and addresses will be
printed in order by last name.
■ Other eligibility -related reports.
Page 25
ADA Eligibility
Determination
Report
Prepared: 08/03/1994 13:13:25
Greater Cleveland
Regional Transit Authority
ADA ELIGIBILITY DETERMINATION REPORT
page I of I
Page 26
MTD
YTD
MTD YTD
% OF MTD
% OF YTD
% OF MTD
% OF YTD
COUNT
COUNT
PERCENT
TOTAL
TOTAL
GRAND TOTAL
GRAND TOTAL
ADA Applications
III
III
100.0
Completed
ADA Cards Issued
III
111
100.0
100.0
100.0
Category I
111
111
100.0
100.0
100.0
100.0
100.0
Category 2
111
111
100.0
100.0
100.0
100.0
100.0
Category 3
111
111
100.0
100.0
100.0
100.0
100.0
Categories 2 & 3
1 1 1
111
100.0
100.0
100.0
100.0
100.0
Replacement
Ill
111
100.0
100.0
100.0
100.0
100.0
ADA Recertiftcations
III
1 1 1
100.0
Completed
Recertification Cards Issued III
111
100.0
100.0
100.0
Category 1
III
111
100.0
100.0
100.0
100.0
100.0
Category 2
1 I I
111
100.0
100.0
100.0
100.0
100.0
Category 3
I 1 I
Ill
100.0
100.0
100.0
100.0
100.0
Categories 2 & 3
1 l 1
111_
100.0100.0
100.0
100.0
100.0
--
Replacement
_
I I I
_
Ill
100.0
I OOA
100.0
100.0
100.0
Senior Cards
1 11
Ill
100.0
100.0
100.0
Replacement
III
Ill
100.0
100.0
100.0
100.0
100.0
Discount Fare
III
11 I
100.0
100.0
100.0
Cards
Replacement
111
111
100.0
100.0
100.0
100.0
100.0
ADA Visitor
111
Ill
100.0
100.0
100.0
Cards
Replacement
111
Ill
100.0
100.0
100.0
100.0
100.0
Total Issued
111
Ill
100.0
Page 26
The Run Sheet You can produce standard driver manifests and other run list reports:
Reports ■ Driver Manifests - The printout of the driver tour sheets or run
sheets for the day.
■ Daily Vehicle Listing - A report on the vehicle use for a specified
period.
■ Holding Run Report - A report of the trips in holding runs.
■ Taxi Run Report - A report of trips in taxi runs.
■ Unblessed Runs - A list of unblessed runs.
■ Unconfirmed Trips - A list of trips unconfirmed with the clients.
The Driver Trip Report is the manifest or run sheet given to drivers and
- dispatchers to detail the -service to be provided_ The driver may record
odometer readings on this form. The report is sorted by run number. It is
generated for a single date from the daily dated schedule for that day.
GARAGE :EDA MIDAS -PT Scheduling PARATRANSIT DATE:
09/24/91
CARRIER :CARRIER NAME NOT FOUND PARATRANSIT SERVICES TIME:
13:47:03
RUN :X007 DRIVER TRIP REPORT PAGE:
000002
SCHEDULE:09/17/91 TUESDAY
'• ASSIGNMENT • •••`• RIDER INFORMATION ******•• ••••'•• ORIGIN/DESTINATION INFORMATION ......• •••... DRIVER REPORT
SCHEDULED PAX LAST NAME CLIENT/TRIP PLACE AFT CITY CASH ACTUAL
PICK DROP AM NC FIRST NAME PHONE ADDRESS ZONE OWED TIME ODOM
NEEDS METHOD OF PAYMENT
NOTE INTERSECTION
------------ ------------------------------------------------------------------------------------------
0600 5 0 TAYLOR
43484-80A
HONE
CA 2.50
EVELYN
214-000-0000
1125
HIGH VALLEY DR
29A F
M: AMB NO ASSIST I:
BLIND f CANE
D: NO
COGNI/EMOT ATTD: A SIGN: 5
0625 5 0 TAYLOR
43484-80A
EVELYN
7840
LBJ FM
15 N
NAUTILUS CENTER
0645 1 0 NRIGHT
47720 -BOA
HOME
1005 AD 1.00
THOMAS
214-241-3280
3820
SPRING VALLEY RD
14 J
M: CANE I:
DEAF
D: SEIZURE DISOR ATTD: N SIGN: S
0700 1 0 ZAMLEN 47627 -BOA HOME 136 DA 1.00
MARY 214-361-5714 10040 REGAL PARK LN 26 J
Page 27
The Reservation You can produce:
Reports ■ Major Generators Report - A list of Major Generators and the
number of trips to and from them.
■ Subscription Listing - A listing of all trips currently in template
schedules.
■ Fixed Route Report - A list of Major Generators Fixed Route Bus
Stops and the number of trips to and from them.
The Major Generators Report displays a list of landmarks that have been
defined to the system. Included in the report are the landmark location and
for that location, the number of trips on any given day, a total number of
origin trips, a total number of destination trips, and a total number of origin
and destination trips combined. The number of Monday through Sunday
-trips should also equal the total in -the -right column. - - - - -
PREPARED: TUE AVG 15
14:57:06 1995
MIDAS -PT Scheduling PARATRANSIT
MIDAS -PT Scheduling PARATRANSIT
PARATRANSIT SERVICES
PAGE 1 OP 1
9
PARAtAAN3IT SERVICES
MAJOR GENERATORS
FROM 06/12/1995
TO 08/38/1995
LOCATION
_------------------------------------------------------------------------------
MONDAY
TUESDAY
WEDNESDAY
THURSDAY FRIDAY SATURDAY SUNDAY
ORIGINS
_----------
DESTINATIONS TOTALS
_------- ------
----------------
BOTANICAL GARDENS
0
0
1
0 0 1 0
0
2 4
CITY HALL
0
0
1
11 1 0 0
B
11 19
STATE UNIVERSITY
2
2
4
3 4 1 0
0
16 16
STATE OFFICE BUILDING
3
4
2
5 30 0 0
30
14 24
The Subscription Trip Master List provides a listing of all trips currently
in template schedules. This report includes the client name, seating
requirements, origin and destination of the trip and the requested times.
This report is sorted by name. A sample of this report is illustrated below.
Prepared: Fri Aug
11 08:59:39 1995
MIDAS -PT Scheduling PARATRANSIT
PAGE 2 OF
9
PARAtAAN3IT SERVICES
SORT SEO: CLIENT
ID
SUBSCRIPTION TRIP LIST
LAST NAME
FIRST M
RIDER ID TYPE
TIME
DAYAPP
HTWHFA
D
EXPIRREES
__________________________________________________________________
DESTINATION
______________________________________
_________________
DRAGOO
PHILIP
E 77
L 01117 UNION P
1305
F
1991/D /11
1995/03/03
L 04800 BROADWAY
PHILIP
E 77
L 07117 UNION P
1130
W
19 1/07/11
DRAGOO
L 04800 BROADWAY
1995/03/03
DELLA
0 80
L 3333 EDGEWWD ST P
1030
WF
COBB
L 22 LAUREL AVE
1995/09/15
E 99
L 6209 HIGHLAND HILLS DR P
0930
H
1992/04/08
TREVILLE
SHMA
L 2417 IRVING BV
1995/04/08
E 99
L 2417 IAYING BV P
1499
X
19
TREVILLE
EMMA
L 6209 HIGHLAND HILLS DR
1995/0411
/08
GARDNER
GERALD
A 149
L 04005 GASTON AV P
0935
H
1995/06/13
/31
L 1140 EMPIRE CENTRAL PL
GARDNER
GERALD
A 149
L 1140 EXPIRE CENTRAL PL
4 005 GASTON AV
1530
H
19 19
1995/08/19
Page 28
The
Performance
Reports
L-A
You can produce several reports that summarize statistics on operations
performance:
■ Quality of Service Report - A list of the runs and their trip
statistics.
■ Passenger Performance Report - A list of the runs and their
passenger statistics.
The Quality of Service Report provides a look at the runs and how they
fare concerning average number of passengers per mile and per hour,
average trip per minute and mile, and the early and late percentages.
PREPARED: TM AUG 17 11.50:31 1995 PAGE 1 OF
1
Greater Cleveland
Regional Transit Authority
Division of Paratrans it j
Quality of Service
DATE 05/26/95
PASSENGERS PASSENGERS AVG. TRIP AVG TRIP Y. EARLY M LATE
RUN PER MILE PER HOUR PER MIN PER MILE .60 MIN ♦30 MIN 420 MIN ♦10 MIN -60 MSN -30 MIN -20 MIN -10 MIN
________________________________________________________________________________________
C21 000.21 002.14 019.27 005.61 000.00 000.00 000.00 011.5] 000.00 000.00 000.00 000.00
C22 000.18 001. R6 022.69 005.61 000.00 000.00 000.00 000. OD 000.00 000.00 000.00 000.00
Totals
000.19 002.00 020.96 005.61 000.00 000.00 D00. 00 005.16 000.00 000.00 000.00 000.00
The Passenger Performance Report provides a look at the runs and the
number of passengers, a breakdown as to their special needs, if any, and
any cancels, no shows, sent backs, or extra ons.
Prepared: Fri Aug 18 08:12:24 1995 Greater Cleveland Page 1 of 1
Regional Transit Authority
Division of Paratranait
Passenger Performance
DATE: 08/09/1995
••'•• passengers •'••• •••••••••••• Ttlps ••••••••••• * Cancels • No Sent Extra Trips
Run Miles Svc Xis Total Complete Lift Blind Special Total Lift Show Back On Scheduled
C91 90.0 6:45 14 14 0 0 1 3 0 0 0 0 17
C92 80.0 6:45 16 14 3 0 0 2 0 0 0 0 16
Page 29
The You can produce:
Administration , Rider Statistics Report - A look at the type of trips operated
Reports (subscription, advanced reservation, and same day) during the
reporting period for ambulatory, wheelchairs, escorts, and
attendants.
■ Scheduler Activity Report - A look at the individual scheduler's
activity for the range of date specified.
■ Time Distribution Report - A list of the number of trips and zones
at different time intervals of the run.
■ Operator Performance Report - A list of operator data (hours
worked, miles driven, and passengers carried) for the date range
indicated.
■ Performance Statistics Report - A look at vehicle usage
performance for the specified date range.
■ Revocations Report - Provides a look at the current revocations.
The Auditor You can produce:
(Service ■ Turndown Log - A list of the trips turned down for the range of
Exceptions) dates indicated.
Reports ■ Cancel and No Shows Report - A list of the cancellations and no
shows.
■ Service Exception Summary - A list of the number of trips and
zones at different time intervals of the run.
The Cancel and No Show Report presents a list of the trips that were
canceled or trips where the client failed to show up. This report also has
year-to-date totals for each client.
PREPARED: MK 08/07/95 Greater Cleveland Page 1
of 1 Regional Transit Authority
D
Division of PafatfS
u
List of No Shows and cancellation Cot or ubsip[ion Trips
For May In Day Order
Sub This Month Last Month Current Y.T.D. Last Y.T.D. Trip PO
DAY Phone Eeq tN/S Ct LTE N/S Ct LTB N/E [t LTE N/S CT LTE Name Pun Code Time Sub
3229-2510 91-2953 0008821 0 04 0 0 0 0 0 0 0 0 0 0 0 Rushton D don te Y19 M 19:50 999
Page 30
Ad Hoc Query Function
Table Display MIDAS -PT allows you to perform ad-hoc queries on your data. You can
view tables of information so that you see only the information you select,
such as a specific subset of client information. This query capability is
built directly into MIDAS -PT and is available using the Tables Menu.
Once a table is brought up, you will be able to scroll up and down, right
and left to see all of the rows and columns in the table. You may modify
the looks of these tables while you are reviewing them. You may:
■ Change the order of column.
■ Show only certain columns.
■ Change the width of the columns.
■ Change the sort order of the rows.
■ Lock title columns on the screen.
■ Display only certain records.
■ Display columns that are calculated based on other fields.
When you bring up a table of data, the tool bar changes to the one for
modifying the table. To help use these tables, leave the cursor over an
icon for a second and a box briefly explaining that icon appears (e.g., Lock
Columns or Hide Fields). The following is a list of commands and their
icon (when applicable) and their effect on the current table.
Print Table Click this icon to print the contents of the table.
Move Columns To move a column, press and hold down the left
mouse button over the field name and drag it to the
desired location.
Hide Columns To hide a column, click on the field name, then
press the hide column icon.
Lock Columns To lock a column as a title to stay on the screen,
click on the field name and then click on the lock
icon.
Page 31
Sort Dataview
To sort the rows in the data, highlight the column
by which you want to sort by clicking on the field
yi•
name, and press the sort icon. Records will be
sorted in ascending order.
Make Column
To change the width of a column, move the cursor
Narrower or Wider
to the right border of the field name and when the
cursor changes, drag the column narrower or wider,
as you wish. Or you can click the Make Column
Narrower icon to narrow the column or click the
Make Column Wider icon to widen the column.
Select by Value
To select items for the table that meet a certain
criteria, click the select by value icon. This presents
_
a dialog box that allows you to enter the equation
- - - -
- for your -criteria. - - - - - - - - -
Fields to Display
Allows you to select or de -select fields to display.
Use this to re -display columns you may have
hidden but now want to display.
Dataview Settings
Allows you to designate a font, point size, etc. for
your display.
Column Heading &
Click this icon to change the heading and format of
Format
columns in the display.
Security and Operator Logging
Each user is given a login and a security level. Up to seven security levels are provided. All
operator actions regarding clients and trips are automatically stored by the system along with the
date and time when each task was performed and the identification of the person who performed
the action. This logging is done for statistical and complaint -handling purposes, and is available
for on-screen lookups.
Page 32
Error Checking
MIDAS -PT includes several different kinds of checks, including:
■ Checks against data entry errors;
■ Checks to prevent a scheduler from forgetting to completely book every stop on the
(round) trip;
■ Checks for accidental double -booking;
■ Checks to preclude booking a trip for an ineligible person;
■ Checks to preclude scheduling a trip that would exceed the capacity of a vehicle; and
■ Checks that alert the user when revisions to run's start and end time conflict with
trips already scheduled on the run.
The system also has a battery of warnings that alert the user when manual schedulings (where the
user has revised or overridden the system -generated trip insertion) result in cases where certain
service -standards (e.g., maximum travel -time; the -acceptable pick-up/drop--off window) are- -
exceeded.
Posting Procedures
There are three posting procedures: end -of -day, end -of -month, and end -of -year. End -of -day
posting creates a record for the specified operations date and creates summary statistics on total
trips, total trips by trip type (standing order, advance -reservation, and same-day), total
cancellations, total no-shows, and total refusals, and total trips that "violate" specified service
parameters. End -of -month posting moves the current month's statistics into the previous month's
fields, and sets the current month's values to zero. End -of -year posting accomplishes the same
thing on a yearly basis.
Utility Functions
The system comes with archiving, purging, and file reorganization functions.
Interfaces
MIDAS -PT is embedded in the TransCAD geographic information system (GIS) from Caliper
Corporation. MIDAS -PT is integrated with Multisystems' Customer Information System. It is
also fully compatible with our MIDAS -BD Operator Tracking System, which is used by a
growing number of transit agencies nationwide.
Page 33
MIDAS -PT
Installation/Reference List
Daily Trip
LAN Operating
Date
Organization/Address
Contact/Phone No.
Volume
Hardware
System/Workstations
Installed
Topeka Transit
Ms. Cindy Pauls
200
Pentium
Windows NT/
Windows 95
11/98
(in progress)
201 N. Kansas Ave.
(785) 233-2011
PC
Topeka, KS 66603
Bay Metropolitan Transportation Authority
Mr. Eric Sprague
500
Pentium
Windows NT/
Windows 95
9/98
(in progress)
1510 N. Johnson
(517) 894-2900
PC
Bay City, MI 48708
Greater Peoria Mass Transit District
Mr. John
500
Pentium
Windows NT/
Windows 95
8/98
(in progress)
2105 NE Jefferson Ave.
Stowkowski
PC
Peoria, IL 61603
(309) 676-8015
Knoxville Area Transit
Ms. Beverly
150
Pentium
Windows NT/
Windows 95
9/98
(in progress)
1135 Magnolia Ave.
Campbell
PC
Knoxville, TN 37917
(423) 546-3752
Special Transit Service, Inc.
Mr. Fred Roberge
600
Pentium
Novell/Windows 95
6/98
(in progress)
211 Gay Street
(603) 668-8603
PC
Manchester, NH 03103
City of Simi Valley
Ms. Diane Jones
100
Pentium
Novell/Windows 95
2/98
2929 Tapo Canyon Road
(805) 583-6700
PC
Simi Valley, CA 93063
Prince Georges County
Ms. Deana Brown
700
Pentium
Windows NT/
2/98
9400 Peppercorn Place, Suite 320
(301) 883-5689
PC
Windows 95
Largo, MD 20774
Daily Trip
LAN Operating
Date
Organization/Address
Contact/Phone No.
Volume
Hardware
System/Workstations
Installed
Whatcom Transportation Authority
Mr. Cris Colburn
600
Pentium
Windows NT/
11/97
2011 Young Street
(360) 715-4511
PC
Windows NT
(in progress)
Bellingham, WA 98225
CityRide
Ms. Martha
1000
Pentium
Windows NT/
09/98
Los Angeles DOT
Melendez D'Andrea
PC
Windows 95
(in progress)
221 N. Figueroa St., Suite 401
(213) 580-5419
Los Angeles, CA 90012
The Ride
Mr. Bob Rizzo
3000
Pentium
Novell/
11/97
Massachusetts Bay Transportation Authority
(617) 222-4441
PC
Windows 95
(in progress)
10 Park Plaza, 4h Floor
Boston, MA 02116
Cooperative Alliance for Seacoast Transportation
Mr. Bryan Clements
200
Pentium
Novell/
10/97
(COAST)
(603) 862-1931
PC
Windows 95
(in progress)
University of New Hampshire
Transportation Building
Durham, NH 03824
Watts Labor Community Action Committee
Ms. Cindy Park
150
Pentium
Windows NT/
9/97
10950 South Central Avenue
(213) 563-4736
PC
Windows 95
(in progress)
Los Angeles, CA 90059
Cape Ann Transportation Operating Company
Ms. Kay Nordstrom
250
Pentium
Windows NT/
9/97
168 Eastern Avenue
(508) 283-7916
PC
Windows 95
(in progress)
Gloucester, MA 01930
Metro Area Transit
Mr. David Pares
350
Pentium
Windows NT/
03/97
2222 Curring Street
(402) 341-7560
PC
Windows NT
Omaha, NE 68102
Daily Trip
LAN Operating
Date
Organization/Address
Contact/Phone No.
Volume
Hardware
System/Workstations
Installed
Heart of Georgia Community
Ms. Derelyn Allen
150
Pentium
Windows 95/
01/97
Action Agency
(770) 358-9478
PC
Single User
P.O. Box 3982, 13 Pine Street
Eastman, GA 31023
Broward County Transit
Mr. Mike Haddad
3,000
Pentium
Novell/
12/96
3201 West Copans Road
(954) 357-8465
PC
Windows 3.1
Pompano Beach, FL 33069
Southwest Ohio Regional Transit Authority
Ms. Jenifer Hartman
900
Pentium
Novell/
12/96
1014 Vine Street
(513) 566-5195
PC
Windows 95
Cincinnati, OH 45202
Kansas City Area
Mr. Walter Chism
900
Pentium
Windows NT
12/96
Transportation Authority
(816) 346-0809
PC
Windows 95
1350 East 17th Street
Kansas City, MO 64108
Muncie Indiana Transit System
Mr. Kevin Barton
300
Pentium
Novell/
11/96
1300 E. Seymour Street
(317) 282-2762
PC
Windows 95
Muncie, IN 47302
MDTs/GPS
Greater Bridgeport Transit District
Ms. Kim Kelly-
550
Pentium
Novell/
10/96
One Cross Street
Morton
PC
Windows 95
Bridgeport, CT 06610
(203) 366-7070
Berks Area Reading
Mr. Bob Rimby
700
Pentium
Novell/
10/96
Transportation Authority
(610) 921-0601,
PC
Windows 95
1700 North 11th Street
ext. 209
Reading, PA 19604
Western Transit Systems, Inc.
Mr. Jerry Slagle
350
Pentium
WindowNT/
07/96
1619 E. Lincoln Avenue
(714) 535-0156
PC
Windows NT
Anaheim, CA 92805
MDTs
Organization/Address
Daily Trip LAN Operating Date
Contact/Phone No. Volume Hardware System/Workstations Installed
Greater Cleveland Regional
Mr. Larry Bauer
Transit Authority
(216) 781-6135
615 Superior Avenue West
Cleveland, OH 44113
Riverside Transit Agency
Mr. Jay Peterson
185 Third Street
(909) 684-0850
Riverside, CA 92507
Westchester County Department of Transportation
Ms. Mary
112 East Post Road
Helmsworth-Hamby
White Plains, NY 10601
(914) 285-5445
1,000 Pentium
PC
500
450
486 PC
MDTs
486 PC
Novell/
Windows 3.1
Novell/
DOS
Novell/DOS
09/95
11/94
9/94
APPENDIX B: PROJECT SCHEDULE
Exhibit 5-1
Installation Schedule
1/21199
1 2 3
February' March` April`
I CODE
Site Visit E]
Multisystems Task
Customer Task 0
Milestone Required for Schedule Adherence
Production Use Begins 0
I"All dates contingent on Notice to Proceed by 211199
no
Site Visits
MILESTONE: NOTICE TO PROCEED
—44—
Obtain Street Database
Obtain list of zip codes & associated popular town names
Obtain Company Logo
Obtain Pricing Samples
Obtain samples of reports
MILESTONE: CUSTOMER DELIVERY OF DATA
Data Conversion: Build Service Area Map
Data Conversion: Client file
Define all code values to be used.
Hardware Installation
MILESTONE: SOFTWARE INSTALLATION
Training: Administration and Setup
Training: Eligibility
Data Conversion: Clean up client file
CUSTOMER MILESTONE: CLIENT FILE DATA VALIDATION AND
ACCEPTANCE
Production Use: Eligibility
Training: Reservations/Scheduling
Define and Enter Registered Runs (service to be operated)
Data Conversion: Enter Standing Orders
Training: Dispatching
Clean up Standing Order Schedules
Enter sample day of demand trips
Parallel Test
CUSTOMER MILESTONE: ACCEPTANCE OF PARALLEL TEST
RESULTS
Training: Reporting/Billing
Production Use: Reservations & Scheduling
Production Use: Dispatching
Production Use: Reporting
I CODE
Site Visit E]
Multisystems Task
Customer Task 0
Milestone Required for Schedule Adherence
Production Use Begins 0
I"All dates contingent on Notice to Proceed by 211199
no
11
11
1 APPENDIX C: COST AND PAYMENT SCHEDULE
1
Multisystems, Inc.
1/21/99
Price Quotation for
Lubbock Citibus
Item
Description
Perpetual Licenses
includes: $20,270
1 MIDAS -PT
1 TransCAD
4 TransCAD runtime
1 R&R Report Writer
Project Management $3,840
Setup Geographic Data $8,760
Non -Geographic Data $1,200
Customization $5,760
Training $7,920
1 days on site, installation
10 days on site, MIDAS
Implementation support $8,640
4 days on site, startup support
8 Pre -acceptance support
Travel $6,750
5 Air Fare
15 Per diem
Documentation $0
Documentation of modifications
MIDAS manuals
TransCAD manual
telephone line charges, postage,
Miscellaneous Expenses reproduction, etc. $1,800
BASE PRICE, MIDAS -PT $64,940
Level 2 Maintenance & Support Program, 6 am - 10 pm EST, 7 days a week $2,000
(over and above the base level support included in base price)
TOTAL PRICE, MIDAS -PT $66,940
Payment Schedule — Citibus
Payment terms for application software and services will be net thirty days on the
following suggested schedule based on the contract amounts for MIDAS -PT:
• Installation of Base Software 50%
• Conversion of client specific data 15%
• Training 20%
• Acceptance 15%
(within four weeks of production use, contingent on fixing bugs identified
during that period)
11
APPENDIX D: SOFTWARE MAINTENANCE AND SUPPORT AGREEMENT
11
11
17
1�1
MULTISYSTEMS MAINTENANCE AND SUPPORT AGREEMENT
Subject to the provisions contained herein, Multisystems, Inc. (hereinafter referred to as "Multisystems") will provide the Customer
named below (hereinafter referred to as "Customer") the following maintenance services.
CORRECTION OF SOFTWARE DEFECTS
Upon receipt of written notice(s) from the Customer specifying failures or errors found in the Software, and upon receipt of such
additional information as Multisystems may request, Multisystems will use its best efforts to respond within four (4) hours to correct
defects in the current, unaltered release of such Software during the hours of support.
Multisystems is not obligated to perform investigation and/or correction of defects found by Multisystems to be in other than a
current, unaltered release; or caused by (i) negligence or modification of the Software; (ii) use thereof in combination with Software
not provided by Multisystems; (iii) inappropriate use of the Software; (iv) failure to supply the necessary facilities for correct
operation of the Software; (v) hardware failures; or (vi) Acts of God affecting the functionality and performance of the Software.
Multisystems is also not obliged to respond to hardware, communications, or operating system problems affecting the platform on
which the Software is installed.
Should Multisystems render service for any of these situations not covered under this Agreement, Customer agrees to pay for time and
materials at the prevailing rates for such service, plus travel charges and all out of pocket expenses incurred by Multisystems in
rendering such service.
I' For the purpose of this Agreement, a defect is considered to exist when the Software does not perform according to the description
given in the appropriate version of the User Manual and when the said defect affects the performance of the Software.
' This Agreement, including the reverse side hereof, represents the complete and exclusive statement of the agreements between the
parties and supersedes all prior agreements and representations between them. This Agreement is binding upon the parties upon
execution by Customer and acceptance by Multisystems, Inc.
TELEPHONE SUPPORT
Telephone support is available Monday to Friday inclusively from 8:30 a.m. to 5:30 p.m. (Prevailing Eastern Time) excluding
Massachusetts public holidays. Long distance charges are payable by Multisystems through a toll-free support number or by
' reversing charges. Any additional telephone support covered by this agreement is specified above.
Please note that telephone support is offered as a service for trained customers who believe that they have encountered a problem with
the Software or who have a question about an infrequently used feature. The MIDAS Help Desk does not cover services specifically
excluded from the fixed price terms of your maintenance contract. Examples of excluded services include the following:
• Telephone support does not cover professional services to recover data corrupted or lost as a result of the failure of power
systems (e.g., dead batteries in a UPS) or data storage systems (e.g., unreadable backup tapes).
• Telephone support may not be used to obtain system administration expertise in diagnosing hardware or network operating
system problems.
• Telephone support does not include consulting services in transit management such as how to cut driver runs or build efficient
schedules.
' Telephone support is not intended to be used as a substitute for training of persons who have not completed our standard training,
such as may result from staff turnover following on-site training.
' Multisystems will respond to the first of the above requests as a priority item on a time and materials basis. Subject to the availability
of staff time, Multisystems may agree on a case by case basis to provide the other types of services on a time and materials basis.
With regard to hardware and system software, the customer is responsible for providing or outsourcing someone to handle normal
' system administrator responsibilities.
ADDITIONS AND IMPROVEMENTS AND NEW VERSIONS
From time to time, Multisystems may develop additions or improvements to the Software. These additions or improvements to the
Software could be a new report, a new command or a new function. If requested by the Customer, they can be adapted and/or
d installed by Multisystems on the Customer's version of the Software. Multisystems may also issue new versions of the Software,
herein referred to as a "New Version," and will make available to the Customer a copy of such New Version. These
additions/improvements or "New Versions" will be provided at no additional license charge, although charges related to the
installation of these additions or improvements by Multisystems will be payable by the Customer and invoiced separately.
Page 1 of 2
All additions/improvements or New Versions will be supplied with appropriate documentation.
Multisystems shall have no obligation hereunder to furnish the Customer with separately priced components to the Software.
All Installation or Customization as requested by the Customer for additions, improvements and New Versions are in addition to this
Agreement, and are in no way covered under the terms and conditions of this Agreement.
FEES
For services as specified herein, the Customer will pay Multisystems a fee as specified on page 1 of this Agreement. The Customer
will reimburse Multisystems for all other direct expenses such as telex, courier, and travel expenses incurred during the provision of
the services specified in this Agreement.
PAYMENT
Payment for the Initial Period of performance shall be made in full within 30 days of the Commencement Date of this Agreement.
Multisystems is not obligated to provide support if this payment is delinquent, until the account is settled.
PRICE CHANGES
Should the price for Multisystems Maintenance and Support Agreement increase, or the terms of such agreement change,
Multisystems will provide the Customer with notification of such change at least two (2) months prior to the Renewal Anniversary
Date of this Agreement.
TERM
Commencing on the date specified on page 1, this Agreement shall continue in full force for the Initial Period, and will automatically
renew thereafter as provided herein.
RENEWAL
Thirty (30) days prior to the Renewal Anniversary Date of this Agreement, Multisystems will issue an invoice to the Customer for
maintenance fees. Customer has fifteen (15) days in which to notify Multisystems that it elects not to renew this Agreement. No
response from the Customer during this period will cause this Agreement to automatically renew for a one (1) year period.
CANCELLATION
Should the Customer be in breach of any term or condition of this Agreement and fails to correct such breach within sixty (60) days of
written notice thereof by Multisystems, Multisystems reserves the right to cancel this Agreement.
Accepted by:
' CUSTOMER: Citibus MULTISYSTEMS, INC.
PO Box 2000, 801 Texas Ave. 10 Fawcett Street
(Street Address/P.O. Box)
Lubbock. Tx 79457 Cambridge, MA 02138
(City, State, Zip)
(806) 767-2380 (617) 864-5810
(Telephone)
By:
(Authorized Signature)
(Name and Title)
(Date)
(Authorized Signature)
Keith W. Forstall, Vice President
(Name and Title)
(Date)
Commencement Date: earlier of Acceptance or Production Use SOFTWARE to be maintained shall be:
Initial Period: One Year MIDAS -PT
Initial Period Fee: $8.000
Telephone Support: ❑ 8:30am — 5:30pm prevailing Eastern time, business days excluding holidays
®' 6am —I Opm x 7 days ❑ 24 hours x 7 days
40
Li
1
Page 2 of 2
10 Fawcett Street
Cambridge, MA 02138-1110