Detailed Client Information
The Detail tab allows you to enter more detailed information about a client.
Some fields may not be required for some clients. Use only the fields that are necessary for the client.
| Field | Description |
|---|---|
| Disability type | Disability type as defined in ancillary data. For example, arthritis or
diabetes. Note: If the client's disability type is not listed, contact a system administrator. |
| Client Type | Client type as defined in ancillary data. For example, physical impairment or
cognitive impairment. Note: If the client's client type is not listed, contact a system administrator. |
| General Type | Three-character type assigned by the person registering the client (to be
used according to the needs of the transit site). Note: General type information is
not shown in any other screen. |
| ADA | ADA types as defined in ancillary data. For example, conditional or
unconditional. Note: If the client's ADA type is not listed, contact a system administrator. |
| Load time | Load time for the client in minutes. Use the up and down arrows to adjust
how long the client will need for loading. Note: Load times are added to other
load times previously entered into the system (for example, for client
addresses, space types, or passenger types). Use these times with
caution. |
| Unload time | Unload time for the client in minutes. Use the up and down arrows to
adjust how long the client will need for unloading. Note: Unload times are added
to other unload times previously entered into the system (for example, for
client addresses, space types, or passenger types). Use these times with
caution. |
| Num Spaces | Number of spaces required for the client aboard the vehicle. For example,
1. Note: Num Spaces sets the maximum number that can be used for client
passenger type PU and DO in Trip Booking. Important: Do not
include spaces for additional passengers here. |
| Exempt from Para Service Area check | Prevents the system from performing a check to confirm that the client’s trip
complies with the Para Service Area parameters when saving a trip in Trip Booking.
Otherwise, the travel parameters defined in the Para Service Area Rules ancillary data or Para Service Area Route information defined in Zonal Timetable ancillary data apply to the client's requested bookings. |
| Mobility Aids | Client mobility aids as defined in ancillary data. For example, a guide dog, crutches, or a wheel chair. Note: Selected mobility aids appear in Trip Booking when a booking is made for
the client. To remove a mobility aid for a single trip, in Trip Booking, in
the Mobility Aids field, remove the check mark from its check box.
Note: If the client's mobility aid is not listed, contact a system
administrator. If the mobility aid does not appear, it may not be marked as
selectable in ancillary data.
|
| Para Service | Service type for paraservice as defined in ancillary data. For example,
conditional or unconditional. Note: If the client's service type is not listed,
contact a system administrator. Note: If this field is not listed, a
ParaService Types tab should be available. This allows users to define
multiple paraservices for clients. To enable this option, contact a system
administrator. |
| Comment | Information that will appear in the driver’s manifest and on the Detail tab of Trip Booking. |
| Private | An informative comment that will not be shown to the driver, and is viewable only in Client Registration. |
| Location Restricted Access Allowed | Locations marked as Restricted Access locations (in , on the Detail tab) to which the client is
allowed to travel. If a client without access to a specific restricted location is scheduled to a run at a time when they would be on board at the location, an R violation occurs. On the applicable restricted location trip even in Run Itinerary view (in Schedule Editor), an R-99999 violation is visible (where 99999 is the Client ID of the passenger who is not allowed). |
| Curb | Vehicles must pick up and drop off the client at the curb of the origin and destination locations. |
| Door | Drivers must escort the client to and from the entrance of the origin and destination locations. |
| Bed | Drivers must physically assist the client from inside the origin location to the vehicle and from the vehicle to inside the destination location. |
| WOT | (Wait on Transfer) Indicates the vehicle must wait with the client when the
client trip involves a transfer. Note: In a transfer trip, the vehicle transports a client to a transfer point,
where the client boards another vehicle to complete the trip. In most cases,
the vehicle bringing the client to the transfer point departs as soon as the
client is dropped off at the transfer point. Sometimes, however, it may be
necessary for the vehicle to stay with the client until the client has
transferred safely to the second vehicle. The WOT value is carried over to
Trip Booking.
Tip: Para Polygon Transfer ancillary data allows system
administrators to define a transfer point so that all vehicles dropping off
clients at the transfer point must wait until the client is picked up by
another vehicle.
|
| Space type |
Space type aboard a vehicle required by the client.
Note: If no space type is
selected here, the system uses the space type set in system
properties. Note: When a client booking is saved in Trip Booking, the selected
space type is shown in the Leg Detail frame.
Note: If the client's space type is not listed, contact a system administrator.
|
| Add. SpaceType | Space type for a passenger who always travels with the client. For example,
an escort or assistant. Note: If the passenger's space type is not listed, contact
a system administrator. The same options should be available for the client
and the passenger. |
| Add. PassType | Passenger type for a passenger who always travels with the client. For
example, an escort or assistant. Note: If the passenger's passenger type is not
listed, contact a system administrator. The same options should be available
for the client and the passenger. |
| Add. Fare Type | Fare type for a passenger who always travels with the client. For example,
an escort or assistant. Note: If the passenger's fare type is not listed, contact
a system administrator. The same fare type options should be available for the
client and the passenger. Note: If the defined fare type is currently
inactive, it is marked with an asterisk. |
| Vehicle Type Exclusion | Vehicles the client cannot ride on. For example, a wheelchair van or taxi.
Note: When a new booking is created for the client, the selected vehicle types
are automatically marked for exclusion on the Supplementary
Data tab in Trip Booking. The
system does not include run solutions with the selected vehicle types when
scheduling the booking. |
| Fare Type | Fare type as defined in ancillary data. For example, adult or student. If no fare type is selected, the system shows the selected option in , on the Profile tab, for . Note: When a client booking is saved in Trip Booking, the
selected fare type and the client fare are shown in the Leg
Detail frame. Note: If the defined fare type is currently
inactive, it is marked with an asterisk. Note: If the client's fare type
is not listed, contact a system administrator. |
| Adm. Unit | Administrative unit as defined in ancillary data. An administrative unit
is a set of eligibility rules that apply to a group of clients. It is created
using a Master Client record. Note: If the client's administrative unit is not
listed, contact a system administrator. |
| Default Excl. Group | Indicates that the client can only ride on vehicles that have no other
passengers. Note: When a booking is created and scheduled for the client, the
client is treated as an exclusive group. No other passengers can be scheduled to
ride that vehicle until the completion of the client’s trip (from pick-up to
drop-off). |