Montebello City Council
June 28, 2023

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-12

4.2.1. Equipment Overview
When customers purchase our state-of-the-art ITS, Avail is committed to ensuring that each agency we work with receives the most value from this investment. To meet this commitment, backward compatibility is a core aspect of our ITS. This feature guarantees functionality with previous Avail in-vehicle solutions.

The key to providing this backward compatibility is in the messaging between the vehicle hardware and the backend system as our in-vehicle unit (IVU), pictured below, can process, incorporate, and generate data from old, new, or any combination of our own equipment. In addition, our coding scheme is continually additive, meaning we can add new content when an enhancement requires changes. The backend (myAvail) tracks the in-vehicle equipment and software versioning to ensure the correct message is sent to each vehicle. This allows an agency to have multiple generations and configurations of in-vehicle equipment, and it makes it possible for our in-vehicle technology to be scalable and progress without making our current hardware obsolete.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-13
Confidential and Proprietary

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-14

4.2.2. In-Vehicle Unit (IVU) (Trade Secret)
Montebello currently has 16 vehicles which are equipped with our latest IVU3, which means that Avail only needs to replace 50 IVUs on MBL’s fleet. This will provide MBL with huge cost savings and a unified technology across the fleet. The in-vehicle unit is a ruggedized, 64-bit, embedded PC, and is the controller of our in-vehicle system. It directly connects to our mobile data terminal/driver display, which the operator will use to log into the bus. When the operator turns on the bus, the IVU automatically turns on; the IVU transitionally shuts down when the bus is powered off. This can be configured to accommodate data transfer needs. The IVU readily communicates to the backend (myAvail).

As illustrated above, the onboard system is an integration of the IVU with the global position system (GPS) and dead reckoning receiver for automatic vehicle locating, the mobile gateway router (MGR), third-party vendor hardware (headsigns, farebox, APCs, etc.), and software, through shared APIs. The IVU also attaches to the sound amplifier, through direct wiring, which drives audio to the interior and external speakers. This onboard integration is provided through the various cables, connections, and interfaces compliant with the SAE J-1708/1587 and J-1939 VAN standards.

As data and reports are vital to the operator, dispatcher, and management, especially for analytics and NTD reporting, Avail Technologies has a store and forward function embedded in the IVU. This function is extremely useful to agencies that encounter areas where there is no cellular coverage, or their cellular reception is spotty. During periods of no coverage, data will be stored in the IVU; it has enough memory to store 30 days’ worth of data. Some examples of this data that are stored are stop reports, APC information, ridership, and farebox information.

The data is stored on non-volatile (hard drive) memory and will be sent to the backend (myAvail) when cellular coverage is restored.

In situations where the IVU needs to be accessed, it can be remotely accessible and configured through the MGR and WLAN; it is also directly accessible through the Ethernet by connecting a laptop computer to the IVU.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-15

4.2.2.1. Discrete IO Service
The IVU also provides a discrete IO service as not all vehicle components can connect to either the J1708 or J1939 networks. For example, the passenger doors and wheelchair lift use a simpler method to communicate their statuses. This method is referred to as a discrete signal. These signals are binary (on or off) and run through a wire that physically connects the bus’s hardware to the IVU. As the door sends a signal to the IVU, it relays the information on the MDT that the door is open or closed.

The discrete IO service monitors physical connections while understanding which connection belongs to which component. For example, when the door changes from closed to open, the discrete signal changes. When this service detects the change, it prepares a message for the master control service that the door is now open. The master control service, in turn, passes the message to the fixed route service for processing. myAvail supports the following discrete signals:
• Door signal
• Wheelchair lift
• TSP (late response)
• Stop/lift request
• Bike rack
• DVR errors/tagging (when supported by the agency)

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-16

4.2.3. Mobile Gateway Router (MGR) (Trade Secret)
Avail utilizes cellular data and Wi-Fi connections via the mobile gateway router (MGR) to communicate data across all our in-vehicle equipment. Avail works with all major MGR modem manufacturers, including Digi, Cradlepoint, and Sierra Wireless.

Avail Technologies will utilize the existing Cradlepoint IBR1700 mobile gateway router (MGR) for MBL’s entire fleet. The MGR is a modem device that acts as the data communications conduit between the onboard vehicle network and the backend (myAvail). This device is connected via Ethernet cable to the IVU and our communications control module (CCM) to provide all network routing and backhaul data connectivity for the IVU and any other onboard devices requiring data connectivity through the cellular carrier or yard Wi-Fi.

Finally, and most importantly, the vehicle router shares data between the various onboard systems, eliminating the need for multiple routers, modems, antennas, and GPS devices. The headsign, internal sign, AVA system, APCs, and farebox will receive the schedule data through the MGR. This takes a huge workload off the operator. At the touch of a button, all onboard vehicle equipment has the information it needs.

4.2.4. Antennas
Avail Technologies will utilize the existing Panorama LG-IN2446 9 IN 1 LOW PRO 4X LTE, 4X WIFI & GPS Antennas to leverage existing equipment and save cost.

4.2.5. GPS (Vehicle Location Tracking)
Avail’s current GPS implementation uses an antenna that contains all the necessary processing circuitry to convert the satellite signal into the standard GPS NMEA (National Marine Electronics Association) data stream, which allows us to track the location of the vehicles. We utilize an offthe-shelf standard GPS device that uses the global navigation satellite system (GNSS), which provides geolocation and time information to our GPS receiver, using the line of sight to four or more GPS satellites.

These standard GPS devices use satellite signals that are often subject to interference from urban canyons (narrow streets between tall buildings), overhangs, multiple level highway interchanges, or anything that can disrupt these low power signals. Avail’s proactive approach to avoiding these disruptions is to include our system with a “dead reckoning” capability. The dead reckoning capability utilizes a three-axis accelerometer/gyro fused with wheel speed and heading to generate an equivalent location, heading, and speed solution. When the GPS signal is lost or degraded, the dead reckoning capability maintains an accurate vehicle location.

This device has a physical connection to our IVU and provides uninterrupted service at all times.

The GPS/dead reckoning unit’s output stream is continuously processed by the IVU to update

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-17
the vehicle latitude, longitude, speed, and direction. These updated values are then used to determine if any position/speed/direction-based conditions have occurred. When the GPS receiver is operating in a dead reckoning mode, the data stream is identical to the GPS data stream, with an additional status indicator of dead reckoning. The Avail system utilizes this data in the same fashion as GPS-satellite data, and logs that a dead reckoned condition is occurring in the data for that vehicle. The Avail system can report when no position data is being received, and reports this as a “bad GPS” vehicle status condition to dispatch.

The system uses global positioning to determine when a vehicle is entering or exiting a trigger box (geofence) which surrounds transit stops and designated geolocation areas. As the vehicle approaches and enters a trigger box for valid stops or designated geolocation areas, it will perform several operator-supported actions, such as making ADA announcements, informing the operator if they are ahead or behind schedule, and changing the destination sign and farebox, if needed.

4.2.6. Mobile Data Terminal (MDT) (Trade Secret)
The MDT is a 10” touchscreen display that provides the driver with a single point of logon for all on-board vehicle equipment and serves as the operator’s interface to the backend (myAvail).

The ruggedized yet responsive touch screen allows the vehicle operator to interact with various on-board systems, and allows flexibility in the form factor, mounting, and environmental options when installed in fleets. The MDT has a HDMI port display and embedded speakers to provide audible event notifications and alerts to the vehicle operator. It connects directly to our IVU which drives the graphical user interface (GUI) video content on the MDT.

The MDT screens that the operator sees after they log onto the system are designed to be concise and user-friendly, with pertinent status information viewable “at-a-glance” to the vehicle operator.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-18

4.2.6.1. MDT Management
For the operator to manage the MDT, they simply log onto the system by typing in their driver ID, and if needed, work ID. If the improper ID is entered, the driver will receive a pop-up on the screen stating an error occurred. This provides validation to the driver and dispatch that the correct login information has been entered in the MDT. Dispatchers are alerted to missed or late logins via color coded updates on their dashboard screen.

Dispatchers can remotely log drivers onto the MDT in the event the driver forgets his login ID or types in the incorrect information. If an operational situation arises where there is a need to have more than one vehicle perform specific work assignments, drivers can log into the same segment of work as other drivers. However, if a driver logs into a segment of work that has not been assigned to them, the system will notify dispatchers that an invalid login has occurred.

The MDT also allows the driver to perform pre-trip and post-trip inspections of their vehicle and equipment, message, or request voice calls with dispatch, play safety announcements, monitor route/trip performance on their section of the route, handle passenger transfer requests, perform APC adjustments (if required), and maintain support screens for testing/diagnostics.

4.2.6.2. Training and Maintenance Logon
MBL staff will be able to log into a vehicle to perform training operations or maintenance without impacting the passenger information tools or operational reporting. Avail Technologies recognizes that training is essential, and this feature allows your operators to do so in a safe training environment. For this function, the operator selects the “menu” icon on the MDT pictured above. Please note that the driver ID still needs to be entered to use the training or maintenance function. This will take them to the training screen with a "logon” button they select. Once logged in, they can select either maintenance or training. During this mode, the headsign can be configured to show Out of Service, Training, or another message. This will also display on the dispatch map as well. The headsign will be changed to “training” when training is used.

4.2.6.3. Single Point of Logon
The IVU recognizes the operator’s ID and pulls the route, block, schedule, and fare information associated with that ID from the backend. This information is also readily accessible and viewable by the dispatcher. Operators will see their performance as they drive the route and be able to interact with the other ITS equipment on the vehicle via this single point logon. Additionally, the operator can communicate with dispatch at the touch of a screen via the canned messages feature.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-19

4.2.6.4. MDT Screens
Once the driver is logged into the onboard system, the first screen they will see is the pre-trip inspection. Once the pre-trip inspection completes its cycle, the MDT screen will then automatically transition to the next screen which includes on-time performance, schedule adherence, route adherence, speed monitoring, and the ability for the driver to see the next three stops. Avail’s software tells the driver where to go in an automated process so that there is as little distraction as possible. The following illustrations are examples of what the operator will see throughout the day while using our MDT.

Set-up screen
On time

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-20
Early
Late

4.2.6.4.1. Pre-Trip Functionality
Avail’s MDT provides a comprehensive pre-trip capability that verifies the CAD/AVL system is functioning and incorporates your driver’s vehicle inspection process. For agencies that are still performing manual recording of walk-around inspections, this saves you significant time, money, and paperwork.

Pre-trip functionality is divided into three sections: vehicle inspections, manual checkouts, and automated startup diagnostics. The first of these is the vehicle inspection, which automates recording and reporting of the driver’s pre-trip walk around checklist. The driver is presented with a series of checklist screens which are configurable to match your current pre-trip form.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-21
The driver must mark each item as pass or fail and specify a reason for any failures before continuing to the next page in the checklist. The following illustrates examples of a pre-trip inspection and the pass/fail requirement that accompanies it.

The last step of the vehicle inspections section allows the driver to record the location and type of exterior body damage by selecting from images of the front, back, right, and left sides of the bus as shown below. The driver selects the quadrant where damage was observed then selects the type(s) of damage. The illustrations below are examples of what the operator will see for the vehicle body inspection.
passed inspection
failed inspection
This illustration depicts
what the operator will see
when the selections above
are completely “filled” out
For this screen, the
operator will select those
items that have failure
issues.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-22
The second step of the pre-trip functionality is the manual inspection of components that are key to meeting ADA requirements and gathering ridership data while in passenger revenue service.

These components are APC counters, AVA announcements, and wheelchair lift. Once again, these checkouts are configurable to match your needs. The MDT screens guide the driver through each of the manual checkouts and automatically records and reports the results.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-23
The final section of the pre-trip functionality is automated startup diagnostics. These are fully automated tests that run in the background while the driver performs the manual sections of the pre-trip functionality. These tests verify communication between the integrated systems in the vehicle. The MDT screen shows a summary of the systems that failed Avail’s automated test. As with the other sections, these results are automatically recorded and reported.

Once the pre-trip functionality tests are completed, the information is submitted (see below) and the pre-trip report is available to both the operator (MDT screen) and the dispatcher (myAvail).

This information is stored in the data warehouse and can be later obtained through the Business Intelligence (BI) reporting module. The timestamped data has vehicle and driver information.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-24
Please note that for critical elements that an agency feels would not allow the bus to pull out, such as a non-functioning radio, they can initiate an email or text to one or more persons within the agency to see that the issue is resolved quickly. The alerts are configurable and can be changed by the administrator.

4.2.6.4.2. Post-Trip Functionality
For agencies that are interested in the post-trip inspection feature when the bus returns to the yard at the end of the day, there can be a post-trip check of the bus. At any time during their service day, the driver may select to reopen pre-trip inspection. The first section of the pre-trip functionality test, vehicle inspections, is available for the driver to review, revise, and resubmit as needed. For post-trip functionality, the operator may re-open the MDT inspection screen and then submit their post-trip inspection. As with the pre-trip functionality, the results are submitted and recorded with timestamps, driver, and vehicle information for later reporting.

Please note that only the first pre-trip section is available. The manual checkouts and automated startup diagnostics are only performed at initial logon.

4.2.6.4.3. Detours
When there is an active detour on an operator’s assignment, they will see notifications on the MDT. The Avail system automatically sends a message to all routes affected by a detour based on date and time. When the operator logs on to the route, the MDT display detour notifications for you. The following illustrations demonstrate what the operator will see when an active detour occurs.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-25

4.2.6.5. Text Messaging
The operator can send canned text messages to dispatch by selecting the MSG icon, on the MDT (illustrated below). When the operator selects this icon, the screen briefly changes, and they are then able to send dispatch a preset message or read a message from dispatch. The three categories illustrated on this screen are emergency (EMR), common (CMN), and wheelchair or farebox messages (FBX/WHL).

4.2.6.6. Headway Spacing
In cases where the operator needs to be mindful of headway spacing, the MDT screen can provide this information to the driver. The following screenshots are several examples of what the driver will see if they are driving a route being monitored by headway. Please note that the spacing between the vehicles is color-coded and will change accordingly depending upon how the vehicles are doing in respect to their schedule.

The system will prompt the operator to or in response to vehicle spacing between their vehicle and the vehicle ahead of you or the “leading” vehicle.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-26

4.2.6.7. Passenger Transfer Request
This feature provides the option for an operator on one vehicle to indicate that a passenger desires a transfer to another route. The in-vehicle system will send the transfer request, and the backend system will determine if the transfer can be supported. If they transfer can be supported, then the backend will send a message to the receiving route’s vehicle notifying them of this request. If the transfer cannot be supported, the vehicle making the request will be notified that it cannot occur. The following illustrations depict how this process occurs.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-27

1. Touch XFER on the home screen.

2. Choose the receiving route from the list.

3. Notify the receiving vehicle about the number of passengers, wheelchairs, and bikes.

4. Touch Enter/Send to send the request.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-28

4.2.7. Vehicle Health Monitoring
We have the capability to interface with Society of Automotive Engineers standard SAE J1939, which allows us to monitor the communication and diagnostics among vehicle components. We can observe the health of each bus at MBL through the J1939 cable as it is directly plugged into the IVU. From the IVU, the vehicle fault alerts are transmitted over cellular to the backend (myAvail), where dispatchers and maintenance are kept apprised of the vehicle’s health.

These alerts generate events in the myAvail maintenance queue, which is part of the dispatcher dashboard, and can be examined through our BI reporting function to provide MBL maintenance staff with the insight and answers that they need.

For fixed route vehicles, our VHM is capable of monitoring and reporting on any diagnostic messages (DM1) active diagnostic trouble code (DTC) with associated suspect parameter numbers (SPNs), and failure mode identifiers (FMIs). Any onboard system connected to the VAN including the engine, transmission, HVAC, and brakes can be monitored. The screenshot below illustrates what the maintenance personnel would see, for an incoming issue.

This feature monitors a variety of maintenance codes that vehicles produce over the J1939 network. The system identifies high priority codes that need to be addressed urgently. This realPage 817 of 1582 Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-29
time monitoring allows your staff to tackle maintenance issues as quickly as they are exposed.

Once detected, myAvail can send emails or text messages directly to the maintenance staff.

The VHM can monitor a wide variety of issues affecting the bus, including but not limited to:
• Pressures–air, oil, hydraulic
• Braking events–hard braking events, fast acceleration events, anti-lock brake system (ABS) activity
• Temperatures–engine, oil/fluid
• Fluid levels–engine oil, engine coolant, other fluid, and fuel • Heating, ventilation, and air-conditioning (HVAC)
The myAvail solution only shows the vehicles that have health issues to the person(s) responsible for monitoring. If a vehicle’s engine is overheating, this information is prioritized and presented to the dispatcher or maintenance staff with an audible tone to alert the user of the urgency.

Additional measures would be available to the user for proper execution, allowing operations to solve the problem effectively and proactively. Our BI reporting tool allows you to run failure reports and get out-of-trend analysis.

4.2.7.1. Real Time VHM Alerts
Vehicle health monitoring alerts are transmitted in real time to the backend system over the cellular data network. The alert, depending upon its configurable priority (5 to 20 seconds), will be sent to myAvail for proper routing to either the dispatcher or maintenance console. The alert will come into either the event queue or timeline based on the alert’s priority and potential effect.

4.2.8. Automated Vehicle Announcements (AVA)
Through our IVU and AVA system, we can provide a completely integrated solution for fully ADAcompliant, automated next stop announcements. These announcements can be made in English and in Spanish and seamlessly integrate with our GPS triggered, next stop announcement capability.

The AVA controller can make time based, location based, and vehicle operator initiated announcements/displays by using the public address/announcement speakers and the interior LED signs. The controller also provides an exterior announcement of the current route number and destination when doors open at a stop. At other locations such as major intersections or time points, the controller will make pre-set location based interior announcements.

The system can provide for volume adjustment based on the time of day (quiet hours) and will also support minimum and maximum volume settings. Our AVA equipment also includes an automatic gain control (AGC) feature to adjust announcement volumes per ambient noise inside the bus.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-30
Providing information to your passengers is crucial, and our in-vehicle system keeps them informed with:
 Public service announcements
 Transfer updates
 Stop requests
 Next stops
 Exterior route announcements
 Date and time
 Safety announcements
ADA announcements: The Americans with Disabilities Act (ADA) requires the ridership, including those that are visually or hearing impaired, to be informed of the vehicle’s progress during service. The system automatically makes these announcements without requiring operator actions. The system displays these announcements on interior signs and plays them over the public address system. Transit personnel can add announcements to any stop or locations defined as nonpublic stops. For the system to be able to make the ADA announcements, the operator must log into their scheduled service and the planning staff must assign the correct announcements.

Headsign updates: The system sets the appropriate headsign value and updates it as needed without involving the operator. For the system to be able to perform this task, the operator must log into their scheduled service and the planning staff must assign the correct sign values.

Stop request: When a rider pulls the stop request cord, the system plays a ‘Stop Request’ announcement and displays a visual confirmation, which displays until the door is opened.

Repeated pulls to the stop request cord are ignored until the door is opened and closed.

Basic information: When the interior sign is not showing ADA information or stop requests, the sign displays the current date, time, and the route name or destination as configured. Optionally, the sign can display the operator’s name.

Exterior route announcements: When either door is opened and the exterior speakers are functional, the system announces the route name to help riders verify they are boarding the correct vehicle. The system can adjust the volume of the announcement based on the time of day and route. The operator is not involved in making these announcements at all.

Safety announcements: The operator can readily access the safety announcements by selecting the “ANNC” icon below. From here, the operator would select the appropriate safety message.

Please note that MBL can have these announcements configured. The announcements, such as “No Profanity” or “No Eating and Drinking,” allows the operator to remind riders of the rules without a direct confrontation.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-31

4.2.8.1. AVA Dispatcher Management (Trade Secret)
Dispatchers manage the AVA announcements using the Announcements tab, under Public Messages in myAvail and assign them at the stop/trigger box level. In addition to the announcements that are associated with specific trigger boxes, the system also provides safety announcements the operator can play as needed. These announcements can be made in English and Spanish; the system is also capable of allowing text-to-speech.

Your dispatchers can use the text-to-speech function to disseminate information to your riders using the Ad Hoc Announcement function in the myAvail Public Messages Tab.

If a text-to-speech announcement is required, the dispatcher creates an ad hoc announcement and enters the information in the “internal sign text” box. The following screenshot illustrates this capability.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-32

4.2.9. Emergency Alarms
There are two types of emergency events that can be generated by a driver: a silent alarm, where the operator engages the covert emergency alarm (EA) button, and emergency message events.

Both types of emergency events are of the highest priority when they are received by dispatch.

Silent alarm emergency events are highlighted in red in the event queue. Emergency text messages are highlighted in yellow. This helps to distinguish emergency events from lower priority events. The following screenshot is an example of the event queue with an emergency event.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-33
When a silent alarm emergency event is received by myAvail, an emergency splash screen is displayed, and an emergency sound is played on the PC until a dispatcher takes ownership of the event. Emergency events are displayed on all myAvail dispatch workstations regardless of the fleet groups being monitored by the dispatcher

4.2.10. Automatic Passenger Counter (APC) – IRMA (Option) If MBL is interested in replacing all its current InfoDev APCs, Avail recommends and can provide pricing for the IRMA Matrix. The IRMA MATRIX is the 5th generation state of the art APC sensor of iris-GmbH. The IRMA MATRIX uses time-of-flight (ToF) technology to generate a 3D image for count processing. With a resolution of 500 pixels (25x20), one pixel can measure 4,096 different height values. Generally speaking, one sensor is sufficient for a standard door in North America. The data collected can be transmitted to an on-board intelligent device via Ethernet and CAN, or alternatively with a gateway via J1708, RS232 and RS485. Based on bus type (i.e. low-floor or high-floor buses), a specific firmware per type is available. The IRMA MARIX sensor has an accuracy rate of 98% based on raw data collected from revenue runs.

The image generated by the sensor allows reliable identification of passengers and movement pattern, such as direction and speed of movement. It also can measure the height of individuals.

The sensor is also capable of recognizing bicycles and strollers/wheelchairs. Pilot projects for this kind of object counting are presently running in Europe and the United States. IRMA MATRIX ensures high counting accuracy independent of color, temperature, and moisture, as well as in darkness, strong sunlight, and reflections.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-34

4.2.11. VoIP (Trade Secret)
Avail has developed a robust Voice over IP (VoIP) solution across public cellular carriers that can utilize either an Avail deployed, or an existing customer provided cellular data communications system. Our VoIP solution is hosted in Microsoft Azure and leverages open-source communication standards for all VoIP call management. The VoIP communications software is supported by our own myAvail suite for all voice call setup and management, with redundant commercial off-the-shelf VoIP servers serving as the “VoIP Application” behind the myAvail suite.

The VoIP servers Avail has selected powers IP based PBX systems, VoIP gateways, and conference servers. Additionally, it is used by small businesses, large businesses, call centers, carriers, and governments worldwide.

While dispatchers and supervisors will interact with myAvail directly for voice call set up, the myAvail suite will interface with the VoIP servers and voice communications console through APIs for the actual VoIP call management and voice talk group selection. This implementation provides a seamless operation for users to streamline their voice call process.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-35
The myAvail VoIP option maintains the same look and feel as a conventional voice radio system to its users, except that instead of the voice conversation being over a radio system, the conversation will be carried over the cellular digital IP data system. Our robust VoIP solution can utilize either an Avail deployed, or an existing customer provided cellular data communications system.

Given that voice communication is critical to the overall fleet operation, Avail has taken every precaution to implement a VoIP solution that will meet the most rigorous transit demands from both a system and functional perspective.

4.2.11.1. Wireless VoIP Gateway
For the VoIP Servers and wireless Gateway equipment, Avail is providing redundant VoIP Servers and wireless Gateway equipment which provide an automated failover to the backup equipment if the primary equipment fails. The diagram below provides a visual representation of the connections and flow of voice traffic between the dispatcher and the fixed route and nonrevenue vehicles.

To ensure a robust and failsafe configuration for VoIP, Avail’s implementation minimizes failure paths within the in-vehicle components. To accomplish this, Avail has combined our rugged and proven Communications Control Module (CCM) with a commercial off-the-shelf VoIP unit into

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-36
the Avail VoIP Module for the in-vehicle solution. This configuration only requires that the cellular MGR, the Avail VoIP Module, handset, and interconnect cables remain intact to provide basic VoIP voice call capabilities.

4.2.11.1.1. Vehicle Hardware
The Vehicle Computer (IVU) provides all the processing, business logic, MDT display interfacing, operator interactions, control, data communications and vehicle component interfaces (AVA, J1708/1587, J1939, discrete, etc.). The vehicle computer incorporates a solid-state hard drive and Intel processor in a fan less chassis.

4.2.11.1.2. Avail VoIP Module
This commercial VoIP unit is a full featured standalone hardware/software VoIP device running a full TCP/IP stack within an embedded real-time OS. The module incorporates an audio pre-amp for the handset/covert mic and a 5W audio speaker output. It is also comprised of the Avail Communications Control Module (CCM).

The CCM, is a fault tolerant IO and audio management device that is used in both VoIP and Land Mobile Radio (LMR) deployments. The CCM manages various IO and Power sources to ensure that basic voice communications are available.

4.2.11.1.3. Covert / Silent Alarm Switch and Covert Microphone As with the closed mic radio system, The Avail VoIP fixed route vehicle solution will be equipped with a covert microphone and silent alarm switch located in a discrete location near the vehicle operator. After the operator has pressed the silent alarm switch, the operator will see a discrete indication on the driver display when a dispatcher takes the silent alarm event.

Normally, the colon in the time-of-day field on the driver display (MDT) flashes every second.

Once a dispatcher has taken the silent alarm emergency event, the colon for the time-of-day stops flashing and remains constant. This lets the driver know that a dispatcher is aware of the situation. If the dispatcher starts covert monitoring on the vehicle, the colon for the time-of-day disappears. This is to inform the driver that there is a covert monitor in progress.

The dispatcher ends the silent alarm event and covert monitoring when the event is closed and then logged on the communications queue screen. When the silent alarm event is logged by the dispatcher, the colon for the time-of-day field on the MDT returns to normal, flashing again. Only the dispatcher can end a silent alarm event.

4.2.11.2. Voice Call with VoIP
Much like a radio call, the dispatcher will click on RTT/PRTT event in the Communications queue (found in the dispatcher dashboard) and from there, the screenshot below illustrates how the dispatcher can initiate one-way or two-way voice calls, by selecting the appropriate option from

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-37
the Voice Call Type field. Calls can also be set up for specific talk groups by selected the appropriate option in the Talk Group field. Individual vehicles or groups of vehicles can also be selected based on Vehicle IDs, Operators, Runs, Routes, Fleet Groups or by selecting the VoIP extension field options, also illustrated below.

Once the dispatcher selects the vehicle or vehicles to have a voice call with, the control information is sent to these vehicles across the data network. Once received by the selected vehicle(s), an audible tone and pop-up message are generated on the vehicle display (MDT) alerting the operator to pick up the handset, completing the call set up, and connecting the dispatcher and vehicles allowing voice communications.

4.2.11.2.1. One-Way and Two-Way Calls
When dispatch initiates a two-way voice call, the MDT will provide a distinct audible tone and visual indication that a two-way voice call has been engaged (see below). At this point, any voice traffic from the dispatcher can be heard through the handset’s cradle speaker. Once the vehicle operator picks up the handset, the cradle speaker is muted, and the audio is routed to the handset’s earpiece. The vehicle operator can push the handset’s push-to-talk button to begin speaking to the dispatcher through the mouthpiece.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-38
When dispatch initiates a one-way voice call, audio is routed to the handset’s cradle speaker and then routed to the handset’s earpiece if the handset is removed from the cradle. The only difference with a one-way voice call is the vehicle operator cannot talk during the call, they can only listen. The handset microphone is muted for the duration of the call.

4.2.11.2.2. Dispatch Console
Dispatchers will utilize the VoIP Voice Dispatch Stations for all voice call communications. The Voice Dispatch Stations are a four line/channel VoIP SIP endpoint device capable of connecting four simultaneous VoIP call sessions.

Each of the channels are fully independent of each other, with separate PTT, volume control, status indicators, etc. for each channel. This allows the dispatcher to participate in or just monitor up to four voice calls sessions simultaneously. The image below shows the VoIP dispatch station.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-39
The Voice Dispatch Station includes an LCD display that will depict a “Name” for each channel as a reference, such that it matches what is presented on the Dispatcher’s Voice Call Setup screen in the Extension field. Once the dispatcher is in an active call, there is an LED indicator above the PTT button that indicates what channel is currently active and in a voice call session is active.

Once connected to a voice call, or just monitoring existing voice calls, the audio is played through the Voice Dispatch Station’s speaker.

The user can adjust the volume on each of the channels independently. Pressing the PTT button for a channel on the Voice Dispatch Station allows the dispatcher to participate in an active voice call on that corresponding channel. Mapping of Voice Dispatch Station channels to active voice call is managed via the dispatchers’ voice call configuration(s). At least one channel will be reserved for active voice calls that originate from the dispatcher’s CAD station, while the others would be used to monitor other active voice call sessions.

4.2.11.2.3. VoIP Call Recording
All voice VoIP voice calls are recorded and saved for reviewing later. These include one-way, two-way, unit, group, and covert mic type calls. myAvail uses a unique session ID that associates voice calls originating from dispatchers or road supervisors to a recorded session for that call.

Each voice call session within the myAvail system includes talk-group, originator, participants, date, time, unique session ID, and call setup status as metadata associated with the voice call session.

Review and playback of recorded voice sessions are managed through myAvail for authorized users only. Voice call recordings and their meta-data are associated using the unique session ID assigned at the voice call setup.

Archiving and deleting of recorded sessions are also managed through myAvail administration and maintenance screens, and again only for authorized users. Storage of the recorded sessions are transferred from the VoIP SIP server to a hosted redundant storage location on a periodic basis.

4.3. Ubisense
Avail has partnered with Ubisense to provide MBL with a Yard Management solution as described in the RFP and addenda. Avail has included Ubisense’s proposal in the Appendix of our proposal which details all the functional and technical details of the Yard Management solution. Please note that Montebello is responsible for providing an appropriate, temperature-controlled area in both dispatch and maintenance buildings to house the IT equipment associated with the CAD & Yard Management systems. Avail Technologies has made assumptions based on the yard management installations where the conduit is not included. If California building code requires conduit, installation pricing may change to meet requirements.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-40

4.4. CAD/AVL Software
The CAD/AVL component of this system has amenities that are requirements of this RFP as it contains pull-in/pullout capability, on-time performance monitoring and tracking, pre- and posttrip monitoring and reporting, vehicle health monitoring with extended analytics, detour management, incident management, real-time, next-stop AVA announcements, multi-language text-to-speech engine, real-time tracking of your fleet with user-friendly maps that contain graphical user interfaces (GUIs), and much more. The data and analytics of these features are stored in the database; when a report is required on a certain feature or topic, this information is readily available in our BI, all with the click of a mouse.

As the in-vehicle area network communicates in real-time to the backend (myAvail) through the MGR, our customers get the real-time data and dispatching information they need, when they need it. Even in remote areas, myAvail offers dispatchers, maintenance, and supervisors realtime information on their fixed route services. In addition, we have developed a predictive analytics feature which provides real-time insights that "predict" future problems and help identify which suites those problems could be examined through, such as Timeline, Route Status, Schedule Status, or Business Intelligence.

Avail’s CAD/AVL is designed to support dispatch, operations supervisor, road supervisor, maintenance, and other positions, as needed. The following bullets provide a brief overview for each position.
• Dispatch: This position within ETMS allows the dispatcher to have access to the dispatch dashboards, track daily operations, see the on-time schedule performance of each route, and communicate with the bus operators.
• Operations supervisor: This position allows supervisors (supervisors/managers/directors) to view current operations and step in to provide direction as needed. The configuration is similar to that of a dispatcher.
• Road supervisor: This position allows field staff to access myAvail on a tablet or laptop in their vehicle. This is configured for the resolution of immediate issues and takes the limitations of the portable device into consideration.
• Customer service: Avail designed this position for properties where the customer service staff handle complaint resolution and monitor the system for potential problems. • Maintenance: The maintenance position leverages vehicle health information (and if applicable, the Transit Assets Suite) to facilitate more efficient operations. This position allows maintenance to monitor the health of the equipment on the vehicle and to assist in locating vehicles that need retrieval or assistance from maintenance.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-41

4.4.1. Computer Aided Dispatch (Trade Secret)
For decades, Avail Technologies has been revolutionizing the ITS industry by spending time with customers and paying attention to the roles and job functions that they perform in their public transit agency positions. We understand what it takes to be a dispatcher. That is why the Operations Suite within myAvail ETMS readily displays the following information for the dispatcher:
 Schedule adherence (OTP)
 Timelines
 Decision support
 Headway management
 Service restoration
 Route adherence
 Morning pullout
 Communication queues for point of contact(s) to the bus operators  Road supervisor coordination
 Detour management
 Incident management
 Real-time map views of enroute vehicles

Dispatcher dashboard

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-42
As the above screenshot illustrates, the myAvail dispatcher dashboard allows dispatchers to see everything they need to perform their job. (Please note that the above is a condensed dashboard as it is typically broadcasted across two monitors. In addition, each of the above quadrants can be “popped out” for sole viewing.)
While dispatch is interacting with operators and maintenance, and viewing routes and vehicles in real-time, behind the scenes, myAvail is performing another aspect of their job. By querying data set to specific parameters agreed upon with MBL, myAvail monitors for potential vehicle issues.

This proactive vehicle health monitoring allows dispatchers to focus on the bus drivers, while having the peace of mind that trends or specifications for the vehicle are being continuously checked.

4.4.1.1. Schedule Adherence (Status Screen) (Trade Secret) For schedule adherence, the system calculates on-time performance by taking the scheduled time from MBL’s active schedule for all timepoint locations in the system and compares the scheduled arrival or departure time directly to the when the vehicle enters or exits each designated timepoint location using the GPS and atomic time on the bus.

At the arrival and departure of each timepoint location, the vehicle automatically sends in a timepoint report over the cellular data network which then gets processed by the system.

Realtime updates are sent to dispatch and all connected real-time passenger information outlets, so the operations team and riders are always given the most current schedule adherence information.

Threshold levels are configurable down to the minute and second. For example, you can define “early” as leaving one second before the scheduled departure time and define “late” as leaving five minutes past the scheduled departure.

The status screen within the dispatcher dashboard illustrates our schedule adherence capability and monitors other key elements of fixed route operations. The following screenshot illustrates what dispatch sees when they are logged into myAvail using the Operations feature.

Please note that all the other tabs (red border) are readily available; the dispatcher can toggle back and forth between them. The dispatcher also can pop these features out and examine more than one aspect at a time.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-43
This screen illustrates how the vehicle is performing in respect to its route adherence and ontime schedule performance. Our color-coded design allows dispatchers and supervisors to see the status of each vehicle (early, late, on time) on the route and whether they are adhering to their route and schedule or deviating from it. The dispatcher is also able to track MBL’s vehicles on the Operations screen/map; this information comes from our IVU’s connection to the GPS/dead-reckoning unit, which continuously updates the vehicle latitude, longitude, speed, and direction.

4.4.1.2. Headway Management
Avail’s headway management can be turned on for any route. The user can configure bunching and gapping thresholds, which trigger events and status changes (illustrated below). The thresholds determine how far apart a bus can be between the leading and trailing bus. Drivers are also given notification if they should slow down, wait at stops, or continue to help with proper spacing.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-44
Headway spacing is also shown to users under the route status. This display has an intuitive visualization of vehicle spacing for the user. It displays the vehicle position along the route, current vehicle state (early, on time, late) and current headway adherence. The headway display can provide information on the quantity of buses and headway compliance along a selected route, including the ability to distinguish between different route path variant. It allows the user to see a single route or multiple ones, depending upon how the dispatcher has their screen configured.

It can illustrate bunching (purple) and gapped (blue) and will also show the smallest gap and largest gap currently between vehicles on this route. The scheduled headway will be displayed in the events column, where it shows events that have been generated related to this route.

Examples include bunching over threshold (when two buses have been bunched for a period of time) or gapping over threshold.

When the dispatcher clicks on a route in the route status tab, it will display just that route in the route map. With this feature, dispatch can view that route individually on a map, which allows them to see how the vehicles are spaced on the route.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-45

4.4.1.3. Timeline (Trade Secret)
The timeline screen in the dispatcher dashboard allows dispatchers to watch specific vehicles over time. Each bus icon represents a fixed route. This tool is also extremely useful for headway, as illustrated below. It can display timepoints and stops located proportionally along the route path. It can track and display the total online buses in each direction as well as offline buses in categories (layover, pull-out, pull-in, deadheading). Lastly, it also highlights and identify areas of vehicle bunching or gapping that require intervention to maintain and control reliable service.

This feature allows dispatchers to see how vehicles are running and how this might affect future transfer connections, crowding, driver reliefs, and schedule adherence. This differs from the schedule status shown above, because the timeline allows you to see historical information for the entire day for that particular vehicle.

The dispatcher can also hover over any vehicle and see not only its current adherence, but also how many times it has been late, on-time, or early, for the last (x) number of time points and act if needed.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-46
Information on the timeline screen

4.4.1.4. Detour Management & Decision Support (Trade Secret) Decision support and detour management are both functions that are included with myAvail and can assist an agency when an accident occurs, an emergency happens, relief is needed, or there is a maintenance issue with the bus.

With decision support, the dispatcher selects the vehicle of interest either on the map or in the status bar, and right clicks on it. The right-click menu will open and the dispatcher has the option to select decision support, illustrated below.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-47

Once the decision support is selected, the following window will open with the vehicle’s pertinent information and dispatch can select the appropriate option for support.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-48
Detour Management
Avail understands that MBL is looking for a solution that has a strong detour management component. Avail’s detour management allows the dispatcher or planner to create new routes when detours are needed by selecting the affected area on the map. Once the detour is created, and the duration of the detour is determined, this information can then be readily shared, in real time, with the operator and the public.

The detour functionality can create ad hoc or planned detours and informs operators and the public about these changes to service routes. This tab uses a Google Maps base that supports full-screen maps, satellite view, and street view. Our detour management functionality includes the following features:
 Ability to plan and define the start and end date and start and end times within each day for the detour.
 Ability to create detours in real time/ad hoc.
 Ability to draw a temporary trace on the map of the detour.  System detection of the routes and stops affected by the detour.  Affected stops are automatically disabled for route and schedule adherence.  Illustrates the affected stops in the RTPI system.
 Automatic and/or manual creation of a detour message to vehicles on the affected routes.  Automatic and/or manual creation of a public service message in the RTPI system.  Automatic and/or manual turn-by-turn directions to be sent via text message to desired vehicles or routes impacted by the detour.

To create a detour within myAvail, a dispatcher or planner uses myAvail to define the detour (illustrated below). The user simply draws a polygon on the map with their mouse where the affected area will be. The user can zoom in/out using the plus/minus buttons, or if they prefer, they can pop out the entire route map by using the full screen option.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-49
Once the drawing is completed (illustrated below) the selected area automatically populates the routes that are affected in the “impacted by detour” grid (right of screen). Routes can be changed accordingly, and stops can be adjusted in the “stop ID” grid.

The user can name the detour, set the start and end dates, set the start and end times within each day that the detour will be in effect, and the cause/effect of the detour (accident/reroute).

The detour map traces the new travel pattern for the detour. This feature is useful where only one route is selected, or several routes are going through an area that needs to be avoided because of road construction or an accident.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-50
Once the affected route(s) and stops have been identified, adjusted accordingly, and saved, the dispatcher can automatically update the agency’s URL or the passenger application myStop® to make riders aware of the detour. The dispatcher also has the option to automatically update public service messages displayed on all RTPI media including wayside signs.

Avail’s detour management function provides the dispatcher with the ability to automatically generate turn-by-turn directions for the detour. These directions are sent as text messages to the drivers on the MDT. If needed, the dispatcher can edit these directions. The illustration below depicts what the bus operator will see.

4.4.1.5. Service Restoration
Another area of strength for Avail is the ability within the CAD/AVL software to provide service restoration for service disruptions. myAvail has advanced service recovery features including functions to aid the dispatcher with day-to-day service disruptions. These include typical service recovery situations where dispatchers may need to cut service for a short turn or add service to handle an unexpected passenger load.

To cut service, myAvail allows the dispatcher to select the portion of the block that will not be serviced due to the cut. For a short turn, this could be as simple as selecting the stop where the short turn will take place. From this point, the system knows to cut service to the end of that trip.

It is also possible for the dispatcher to select a portion of a block that includes partial trips or multiple trips. Once the dispatcher has selected the service that will be cut the system handles the following:
 Removes arrival/departure information for the skipped stops in all the passenger information portals.
 Logs a cut service event, including the trips affected and the missed mileage on these trips.
 Creates a text message to the affected vehicle where the short turn should occur.  Sends an email to a configurable group of people about the service change.  Creates a message to passenger information portals about the service change.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-51
 Incorporates the missed mileage into reports, such as revenue mileage/hours and NTD reports.

To add service, dispatchers can add temporary blocks or add trips to an existing block to meet passenger demand. The dispatcher can assign a vehicle to that block and when the operator logs on, the schedule data for that block will be downloaded to that vehicle. The arrival/departure information for the stops on this block will then be included in all the passenger information portals.

4.4.1.6. Communications, Events, and Maintenance Queues (Trade Secret)
This screen notifies dispatchers and maintenance of communications with operators and potential problems with vehicles.

The communications, events, and maintenance functions operate similarly as each act as a queue. These three queues/screens provide information that is vital to both dispatchers and maintenance. The following bullets describe each of the three.  Communications queue: As operator/dispatch communications are so important within a transit agency, myAvail displays communication messages in their own queue. This queue displays emergency alarms and text messages from vehicles and, for closed-mic systems, displays RTT (request to talk) and PRTT (priority request to talk) messages.
 Event queue: This queue displays operational events from vehicles and system detected events, such as sign communication alarms or wheelchair lift cycle failure.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-52
Operational events include invalid logon attempt, manual out of service, and vehicle movement alarm.
 Maintenance queue: This queue is part of the maintenance role and displays mechanical events. It allows the maintenance department to manage events related to the health of vehicle equipment. When granted permission, dispatchers can also monitor the maintenance queue.

This information can also trigger email/text alerts and be stored for reporting. For myAvail to send alerts, the relevant user account profile must include email and cell phone information.

If an item in any of the three queues needs to be addressed, the user right clicks on the specific item of interest. They will see the drop-down menu shown on the screenshot below. The communications tab, events tab, and the maintenance tab each have a numerical value beside them that displays the count of events in the queue that have not been addressed.

To take responsibility of an event, select the word “take” The user can also select the “take” button at the bottom right of the screen. When the event is taken, it is tagged with the user ID of the person claiming responsibility, which lets others know this issue will be resolved by a specific staff member. When an incident needs to be created in response to the event, dispatch can create an incident by selecting the “log” icon at the bottom the screen. If this event needs to be officially logged as an incident, the user checks the “log as incident” box in the pop up.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-53

4.4.1.7. Incident Management (Trade Secret)
A dispatcher can log an event in one of two ways. The first is when a dispatcher receives an event in the queue and needs to perform an action on an event in the communications, events, or maintenance queue as described above. After the incident is logged, the information can be readily accessible through myAvail Incident Management.

The second option is available within the Compliance Suite, shown below. This option is useful for those incidents that occur outside of the vehicle or if a safety or passenger issue needs to be documented and addressed.

All incidents that are logged in the Operations queues are then readily available in Incident Management, which resides in the Compliance Suite within myAvail ETMS.

Once in this suite, the user selects the “vehicle incidents” option if the incident is vehicle related, or “claims and safety” if the issue is safety related. The user is prompted and guided through forms, allowing them to log an incident associated with an event, record the incident, and pull metrics on incidents. Incident Management also provides a robust tool for searching, editing, and reporting on the logged incidents. The following illustrates creating a new vehicle incident.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-54
Add new incident screen

Basic information screen
This incident reporting tool provides a function for searching and editing. When the incident is logged, myAvail will populate the fields with data generated by the system. The user can search for a specific incident and fill in the fields that have not been populated. The tool also provides an easy-to-use advanced search tool to allow safety and operations staff to look for trends in incidents. All records are date and time stamped. Additionally, this incident can be passed to others for additional input.

Please note that not all events are related to incidents, and as such, the dispatcher can close an event without recording it as an incident. However, all actions taken by a dispatcher resulting Auto-prompt for required fields
Guided Forms

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-55
from an incident can be stored for future reporting simply by logging the event is being closed.

Incident reports are then built from the stored data.

4.4.1.8. Pullout Management System (Trade Secret)
The myAvail Pullout Management module provides a powerful solution for the user in charge of pull out and vehicle assignment, and can be used to support several operations including:
• Operator to run assignments
• Vehicle to block assignments
• Operator and extra-board check-in process
• Notifications for late or missed check-ins, logins, and pullouts • Managing trippers (added or make-up service)
Dispatchers can filter drivers by several parameters such as signed on, signed on but not checked in, or signed on but not pulled out, when a vehicle was scheduled to pull-in, and when the vehicle actually pulled in. This allows the user to focus attention on the critical elements for pull out in each phase. Dispatchers will see vehicles that are assigned, not assigned, and not available to be assigned due to maintenance or other parameters. myAvail integrates with Trapeze OPS to receive operator and vehicle assignments, which are displayed in the Pullout Grid and used to validate vehicle logons.

User view of a sort based on pull out parameters

4.4.1.9. Dispatcher Pullout Screen
The myAvail suite provides validation to not only the driver but also to dispatch that the correct login information has been entered in the MDT. Dispatchers are alerted to missed or late logins via color coded updates on the tabular screen.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-56
Dispatchers can remotely log drivers onto the MDT in the event the driver forgets to login or logs in with the incorrect information. If operational situations arise where there is need to have more than one vehicle perform specific work assignments, drivers can log into the same segment of work as other drivers. However, if a driver logs into a segment of work that has not been assigned to them, the system will notify dispatchers that an invalid login has occurred.

The initial daily assignment of operators to runs and vehicles to blocks are done within Trapeze OPS. At the start of the service data these assignments are retrieved from Trapeze OPS and used to build the myAvail Pullout Grid for the day, as shown below. Any subsequent changes to assignments done within Trapeze OPS are transferred to myAvail and are reflected in the Pullout Grid.

The Pullout grid shows each run piece scheduled for the day. In the run column, myAvail displays an R to indicate relief run pieces and a T for tripper runs. For run pieces that are the first piece of a block, the table shows the scheduled check-in, scheduled login, and scheduled pullout time. myAvail calculates the scheduled check-in and scheduled login times using the scheduled pullout time in conjunction with configurable parameters for how many minutes before the pullout time the check-in and login should occur.

This grid also displays the operator assigned to that run, the vehicle assigned to that block, and the location of the vehicle in the yard (when the optional Yard Map feature is implemented). It can be set to display the time the run piece will end (pull in). This feature is helpful for displaying when an operator or vehicle will be available for unscheduled work. The status column indicates the status of the run piece. The Pullout Grid also allows the dispatcher or supervisor to assign, or reassign, operators and vehicles.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-57
Operator assignment screenshot
The import of assignments from Trapeze OPS to myAvail will be done through a database table maintained by OPS. This table contains a complete listing of the employees’ vehicle and work assignments that are defined in the Trapeze system. myAvail will check this table once a second for any changes. If a change is detected, myAvail will update the Pullout Grid to reflect the changes.

4.4.1.10. AVL Map Views
Avail utilizes the latest internet mapping features and layers for the base GIS and mapping in myAvail. Key features include:
 Full U.S. coverage with full road and satellite views  Traffic data
 Speed limit data down to the street level allows us to alert you when a bus is speeding  Ability to add additional map layers to incorporate additional information such as landmarks
 Ability to create and save views to quickly zoom to key location.  The map illustrates route traces, vehicles color coded with on-time performance information, with the zoom, pan and other map features you would expect. All revenue vehicle information will be provided via the cellular data network. In the case where a larger viewing area is desired, the myAvail map quadrant can be expanded to the full screen or to a separate screen based on the desire of the user.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-58

4.4.1.11. Dispatcher and Operator Interactions
myAvail provides validation to the dispatcher and the driver as they enter their login information into the MDT. When the login is complete, dispatchers are alerted. This allows the dispatchers to see which operators are on time and those who are late or missed.

In the event the driver forgets to login or logs in with the incorrect information, a dispatcher can remotely log that driver onto the MDT. If operational situations arise where there is need to have more than one vehicle perform specific work assignments, drivers can log into the same segment of work as other drivers. However, if a driver logs into a segment of work that has not been assigned to them, the system will notify dispatchers that an invalid login has occurred. A dispatcher can also communicate with the operator through the MDT.

Right click to view detailed
information pertaining to
specific vehicles
Maps allow dispatchers to
view traffic, landmark, etc.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-59

4.4.1.11.1. MDT Data Messaging
One way to reduce voice traffic and to foster more productive communications is to take advantage of data messaging. Dispatchers have a simple interface which allows them to view canned messages from their in-vehicle MDT.

The same interface also provides dispatchers with the ability to quickly send either canned or free-form text messages to individual vehicles or groups of vehicles. Messages can also be scheduled to send in a specific time/date range.

Canned data message editing
In the vehicle, the driver also has a simple to use interface to receive, read, store, and send messages to Dispatch. Messages may be easily reviewed at the driver’s convenience, while the bus is stationary.

Driver received messages

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-60
Driver message send menu

4.4.1.12. Additional Features
In addition to the features that are available in the operations tab for the dispatcher, operations supervisor, road supervisor, customer service, and maintenance, based on the requirements of the RFP, myAvail has other functions that are also critically important to the success of MBL’s CAD/AVL system.

4.4.1.12.1. Replay
myAvail includes a replay function for post review of the vehicle information. Vehicle information is sent into the system over the public network from each vehicle based on time, distance traveled, or the occurrence of an event. This is then plotted on a map on the myAvail workstation, so the dispatchers can always see where vehicles are. The screenshot below illustrates this functionality.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-61
Replay data includes vehicle, driver, route, block, run, trip, direction, stop, schedule adherence status, speed, vehicle alarms, passenger counts (boards, alights, onboard), and more.

Data is displayed on a GIS map and in a tabular format. Tabular data can be quickly and easily sorted and filtered and can be exported to Excel via a menu option.

4.4.1.12.2. Announcement Management (AVA)
myAvail includes an integrated capability to create and maintain all audio files required by the AVA system. Avail is providing professionally recorded audio announcements in our proposed solution. We can also support the use of text-to-speech tools to create announcements. Audio files include all required snippets (e.g., “Now approaching”), stops, routes, transfer information, safety, public service, etc.

4.5. Scheduling Software
Avail Technologies has a comprehensive Planning and Scheduling suite in our myAvail ETMS that provides each of our customers with functionalities that allow them to import, build, validate, and deploy fixed route schedules, create trigger boxes, manage announcements, design reroutes, and much more. User-friendly design guides the individual through the steps for the task that they are trying to achieve. There are also required fields that need to be monitored and checked-off, which prevents errors from occurring such as a stop that does not have a next-stop announcement or audio files not being accompanied for the route in question.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-62

4.5.1. Integration – Optibus
Avail Technologies has successful integrations and live deployments with all the leading scheduling systems including Optibus, CSched HASTUS, Trapeze FX, and Remix.

For this proposal, Avail Technologies will leverage our strong relationship with Optibus and integrate with your existing scheduling software. This will continue to provide MBL with a hosted software solution that will provide the desired outcome for your scheduling system requirements.

Optibus integrates seamlessly with myAvail, as evidenced by the growing list of transit agencies where myAvail is successfully integrated with Optibus today.

Finally, we want to emphasize that once MBL has adopted a scheduling package, your myAvail software platform will be able to move forward to the current version, and future versions deployed through simplified, automated upgrades in the Azure cloud services platform. Now let’s take a quick look at the scheduling options we are presenting.

4.5.1.1. Optibus
Optibus will work with Avail and MBL during project implementation to configure your schedule in the software and complete the schedule export/import process (as described below) to integrate the operations schedule into the myAvail ETMS system.

If applicable, integration with payroll, driver and vehicle assignment changes for daily operations, and runtime analysis can all be provided through myAvail ETMS. The Optibus scheduling software will provide you with a modern, robust scheduling solution.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-63
The Optibus platform is unique in several respects. First, it is focused on real business metrics.

Optibus models your transportation network at the most granular level, generating a quality schedule and immediately highlighting the business key performance indicators and cost data you need to make optimal schedule and cost decisions.

It has the unique ability to provide optimization from agency to operator and from routes to rosters. Optibus creates a holistic plan that carries timetable and route data all the way to scheduling, ensuring that various options can be tested and evaluated, creating visibility on the use of third-party funds and the quality of operations, and allowing optimizations that create better on-time performance on the same budget or even less.

Optibus is provided as a SaaS (Software as a Service) platform. Being cloud native, it saves IT resources and requires no hardware, allows the decommission of costly servers, and supports IT needs. Feature improvements are made continuously. Clients are up and running in weeks, not months. Furthermore, your staff can work remotely, including from home.

With the strongest algorithms in the business and machine learning muscle, Optibus turns your operation into a smart, data-driven business. Forecast the likelihood of on-time performance, incorporate external data, and use demand-related data to bring your service to the forefront of mobility.

Optibus was built to support the world's most complex transit operations as well as small local services. The platform can model any type of preference and constraint across thousands of vehicles to quickly provide an optimized schedule or plan. This not only provides an accurate and actionable plan, it also saves scheduler time and effort and frees them to focus on other areas in the business where their expertise is required.

The Optibus platform is completely cloud native. All platform upgrades are on secure Amazon Web Services cloud servers and are completely seamless to end users and at no additional cost.

New feature development and support in the purchased software modules are released free of charge.

Finally, Avail has included a letter of recommendation from Optibus for this proposal which can be found on the following page.

April, 10th 2023
To Whom it May Concern:

Optibus has worked successfully with Avail at over ten public transit agency sites in the U.S. to ensure successful integration between our respective platforms. Our strategic partnership allows route and schedule data from the Optibus platform to be ingested by the MyAvail software, complete with custom metadata and headsign codes.

Optibus would be happy to continue to work with Avail and the City of Montebello/Montebello Bus Lines to deliver the correct configuration of our products for your needs.

Respectfully,
Sean Grimes
Regional Director
Optibus
535 Mission St. San Francisco, CA 94105
Office: (415) 484-3390
Mobile: (323) 708-1400
www.optibus.com

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-64

4.5.2. myAvail Schedule Import
myAvail is designed so you can import schedule data, validate schedule data, build the vehicle run files, and deploy the files that a schedule change requires through the build and deploy tab.

It distributes these features across four sub-tabs that you must use in sequence to deploy a new schedule. The four tabs are as follows:
• Data import: Imports schedule data from your scheduling package and places the data into an interim database for the initial validation.
• Validate: Identifies problems in the future schedule and provides recommendations for resolving them.
• Build: Initiates the build process for the vehicle block files and the general transit files. • Deploy: Specify the deployment date for the future schedule to become the current, active schedule.

4.5.2.1. Schedule Import and Validation
This module allows the user to import schedule data into the CAD/AVL system. This would be done for each planned schedule change per year (or however often the agency makes interim schedule adjustments). Built-in data validation checks ensure the imported data is complete and error free, and validation errors and warnings are provided to the user to facilitate error correction throughout the validation process.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-65
The left-side of the screen displays a status of all the validations using the following color code:
• Green indicates success.
• Orange indicates warnings.
• Red indicates critical failure.

The main section will display a summary of the import on completion, as shown above.

4.5.2.2. Build
Once the schedule data is imported and validated and trigger boxes are created, all block/run files required for CAD/AVL system operation in the vehicle are generated. In addition, new GTFS files are also generated now.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-66

4.5.2.3. Rostering
Rostering allows the regularly scheduled operator to be associated with the run or runs based on your bidding process. Rosters also enable the assignment of runs to a hold down operator if they are used at your agency.

4.5.2.4. Deploy
Once all CAD/AVL output files are built, they can be scheduled for deployment to the vehicles via the yard wireless LAN network. GTFS files can also be scheduled for public deployment.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-67

4.6. Real Time Passenger Information (RTPI) (Trade Secret) Avail Technologies understands the importance of accurate real-time passenger information to MBL’s passengers to provide them with an easier riding experience. myStop® is our full suite of
real-time passenger information products designed to provide your riders with the accurate, timely, and accessible passenger information they need to make informed decisions. Our traveler information data server (TIDS) is an advanced prediction engine that combines schedule data, real-time on-time performance, and vehicle location, as well as detour and other data to provide accurate next bus arrival and departure predictions. Available platforms to access this information include our desktop and mobile websites, native iOS and Android apps, interactive voice response (IVR) phone system, and 321123 SMS text system, as well as certified GTFS static and real-time feeds, REST API, and integrations with regional 511 systems.

Avail is proposing the myStop® suite to provide the requested predictive arrival and departure information to your riders via the requested portals. The following list addresses each aspect of our RTPI system:
 GTFS (General Transit Feed) Static interfaces with Google Transit to provide a complete trip planning tool for riders.
 GTFS-RT (General Transit Feed) Real-Time supports sharing of real-time data such as arrival predictions, vehicle positions, and service advisories on Google Maps and providers.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-68
 REST (Representation State Transfer) Application Program Interface (API) is the API that allows us to share information with passenger information displays and other public information portals.
 Real-time passenger information is available via a transit property's website on your desktop, laptop, tablet, or smartphone using your preferred web browser.  Smart phone apps such as iPhone and Android apps with the ability to view real-time information.
 Alert subscriptions with real-time information alerts via SMS text and email are available.
 Passenger information displays providing real-time arrival and departure information and infotainment content in various form factors and installation options for transit centers, bus bays, remote stops, or on the transit bus.

Key Features
 TIDS provides accurate and timely next bus information  Full suite of passenger information portals provides accessible information to all riders  Web API and certified GTFS static and real-time feeds  Available in multiple platforms
Key Benefits
 Increased customer satisfaction through real-time bus tracking  Reduced complaints as riders become better informed of issues affecting transit service  Supports regionalization through industry standard data feeds  Creates potential new revenue streams and local business support via advertising

4.6.1. GTFS Static/Real Time
Avail has amassed a great deal of experience over the years interfacing with multiple third-party vendors including Transit App, Swiftly, and regional systems such as 511 to provide our customers with impeccable real-time passenger information.

We have provided real-time and historical data to scheduling packages, regional IVR and realtime passenger information systems, incident tracking and management systems, trip planning systems, and wayside signage. We have built various means into myAvail to support this sharing and openness of data. A common method for interfacing to other systems is through the General Transit Feed (GTFS).
myAvail provides both the GTFS static feed, containing schedule data, and the GTFS Real Time (GTFS-RT) feed containing real-time information such as locations, estimated stop departure information, and service alert messages. All transit agencies that have our system are currently

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-69
providing the GTFS feed to Google for trip planning purposes. Several agencies have also gone through the process of having our GTFS-RT feed validated by Google, using it in the trip planning results. These GTFS feeds can also be made available to other systems that can accept and work with GTFS formatted data.

4.6.2. Representation State Transfer (REST)
In addition to GTFS feeds the myAvail system also includes a set of representation state transfer (REST) services to provide real-time information about items such as:
 Routes: what stops are part of the route, what buses are currently on the route, and what service alerts are currently active for a route
 Stops: characteristics of a stop, stops by route, stops closest to a given latitude and longitude
 Stop departures: scheduled and estimated departures for every route that goes through a given stop
 Vehicle: location of a vehicle, other vehicle information (heading, speed, onboard count, schedule adherence status)
 Service alert message: general, route specific, multi-language REST services are an industry standard means of providing interoperability between systems.

The myAvail REST services provide real-time information in a more targeted way allowing other systems to request only the data that they need and supplying the data in either XML or JSON format. Some systems may find this format easier to work with than the GTFS-RT feed.

To control the use of the myAvail REST services and prevent unwanted access, an API key can be required to use the services. This way, we can track usage by other systems, and impose rate and usage limits if desired. API key management can be done either by Avail or the transit agency.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-70

4.6.3. Website
The myStop® web portal is a feature that Avail has implemented for most of our existing ITS customers. From their preferred web browser, the passenger/customer will visit MBL’s website via their desktop, laptop, tablet, or smartphone and go to the area on the site that references tracking your bus. From here, the user will click on the link for the myStop® website, which will be branded to match the MBL color scheme. From here the user will have the ability to perform the following functions:
• View single and multiple routes
• View all stops and timepoints along the route
• View RTPI for buses and stops
• Search by stop
• Set bus arrival alerts
• See and review public service announcements, detours, and service alerts • Sign in and subscribe to automatic alerts for vehicle arrival • Integrated Google trip planning where riders can enter their starting and ending locations to get real-time information based on your schedules.
• Creates potential new revenue streams and local business support via digital advertising The following illustrations depict several features of the myStop® web application.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-71
Landing page for myStop®

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-72
Agency website where routes have been selected

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-73
Integrated trip planner

4.6.4. Mobile App
Our solution includes our free myStop® mobile app which allows customers to view real-time information and plan trips with our trip planner function. Riders can download the myStop® app through the Apple app store and Google Play, giving both Android and iPhone users real-time route information at their fingertips.

The myStop® app is constantly updated to improve both usability and performance. In the following illustration, we are using the iPhone to illustrate the features and functions of the app.

We encourage MBL to download the app and give it a try.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-74

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-75
Additional capabilities within the myStop® app include:
 Service alerts for routes of interest or within your favorites  Walking directions to the stop through an interface with Google  321123 SMS short code, which includes all inbound and outbound text messages  System experience and performance feedback to the agency  Google trip planning

4.6.5. Subscription Alerts
With subscription alerts, a user can personalize their account to adjust the frequency, routes, or alerts (email or text). This lets the user select how and which information they receive.

By clicking on the bus stop
dot, passengers can view a
schedule for when the bus
will arrive at their stop.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-76

4.6.6. Passenger Information Displays
When it comes to LED and LCD displays providing real-time passenger information, Avail has completed diverse projects ranging from off-the-shelf to detailed and designed solutions to fit specific form factors.

From this experience, we have learned each customer has different preferences. For instance, some properties require Large LCD displays to provide up-to-date information to travelers while others use a small LED style solution no larger than an 8x11 inch piece of paper.

Our open standards-based passenger information data feeds support a multitude of LCD, LED, and solar signage options to reach your customers at every stop along their route, including interactive signage with live customer service interaction and advertising options.

Real-time information is displayed typically in minutes, either as a clock time or as a countdown time. The Avail prediction algorithm updates its prediction as soon as it receives the departure stop report from the vehicle.

Users can create accounts
for personalized access

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-77

4.6.6.1. Infotainment
Avail Technologies is proposing two infotainment signs per bus for 50 buses to provide passenger information along with the AVA system. Avail is partnering with Message Point Media to provide MBL with the MPTV-M37sw HD Intelligent Display that meets the requirements in the RFP. The following content is a brief overview of the interior signs.

TransitPoint Mobile is MPM’s solution for on-board infotainment displays. This solution allows location-based geo-aware content that supports just-in-time passenger information and/or next generation location-based ad services that can maximize opportunities for onboard advertising revenues. We have built a deep interface directly between our infotainment display controller and the onboard IVU that will drive even more exciting capabilities in the near-term.

All the visual application suites share a common architecture and capability set including:
• Multiple animated information display layouts for things like real-time schedule displays, route information, dynamic maps, next bus alerts, service alerts, and emergency alerting • Multilingual text-to-speech functionality in over 12 languages and support for cloud based machine translation for alert information
• Direct integration with myStop® and InfoPoint APIs that offer unique information not exposed through generic open APIs, as well as support for integrating external schedule info at shared stops via open APIs like GTFS, GTFS-RT, and SIRI. We also support vendor specific APIs such as Amtrak, Greyhound, Megabus, and many more. • Our apps are designed to work in a “local first” caching architecture that provides bandwidth efficiency and makes them capable of operating for extended periods with or without internet connectivity. Direct integration with the IVU ensures onboard displays are always operating from the most timely and accurate information on the vehicle instead of depending on cloud API calls.

The “front end” visual layer of our applications is separate from the “back end” data layer. For our clients this means that instead of just using your agency’s colors in the app, we can costeffectively customize the look and feel of the applications to your agency branding and communications goals.

4.6.6.2. Wayside Signage
Avail Technologies understands that MBL is interested in wayside signage. Avail reached out to our signage partner, Message Point Media, to provide MBL with the MPTV-EX15RLP which is a 15” low power outdoor display with integrated LTE. We understand that the 10 wayside locations may not have power or internet connection, so we will add the MP-LP-Solar kits to the signs which include a 48AH LiFePo4 battery, smart charge controller, and battery management system.

E-ink series displays require little power to operate compared to traditional LCD or LED panels, making them ideal candidates for solar-powered signage solutions. Utilizing black and white

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-78
pigment suspended within cells, they only require power to change current images shown, and any image presently displayed will remain stable, even should the display lose power. They work well in climates that experience warmer temperatures.

4.7. Business Intelligence

4.7.1. Central Database Reporting
Avail Technologies has a reporting capability that is unrivaled in the public transit industry. With over 20 years of experience working closely with customers, we have developed a data repository that utilizes a centralized data warehouse to store the vast amounts of data generated by our system and the systems we interface with. The separation between live and historical data ensures the real-time system performance is not impacted by historical data analysis. Advanced extract, transform and load (ETL) procedures ensure that data is stored, related, and optimized to support the advanced predictive analytics and business intelligence functions within the system.

4.7.2. Business Intelligence (Trade Secret)
To comply with the requirements listed in MBL’s RFP with respect to a data warehousing and reporting tool, Avail is proposing our Business Intelligence module. This function will provide MBL with a reporting suite that contains voluminous amounts of data that can be easily analyzed.

Each of the reports generated in this module will provide a clear and user-friendly representation of the selected data parameters. We are proposing this tool to MBL; it will fulfill your requirements for operational, ridership, vehicle health, idle monitoring, driver behavior, and government reporting.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-79
Our Business Intelligence (BI) module has the flexibility to allow the users to see any report they need, when they need it. MBL will have the flexibility to create your own reports through selfservice reporting, have easily navigable and drop-down reporting menus, manage canned reports, adjust reporting parameters to their needs, and have the availability to receive reports at a desired frequency (hourly, weekly, etc.) via email.

Coupled with our data warehouse and analytics engine, our reporting solution can automatically find proactive results and display them in a user-friendly fashion. We do not limit an agency’s ability to access their data, and there are full export capabilities which allow data to be exported and shared in any number of formats.

BI is also role-provisioned meaning it is available to any staff member with “reporting rights” granted to them by the administrator. The reports are configurable to each user and shall allow for canned, custom, or ad hoc reporting.

A menu bar across the top of the home screen displays the different categories of reports and features you can access. For example, the myDash option has features which allow users to customize their BI dashboard so that they can manage their reports and bookmark them.

The following screenshot is our On-time Performance Dashboard under Planning & Scheduling.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-80
Some of the key features of the BI reporting module include:
• Schedule adherence reports by block, run, route, trip, stop, service period, day, hour, and operator
• Visual running time data that easily illustrates the difference between scheduled and realtime data • Farebox ridership information and revenue data block, run, route, trip, stop, service period, day, hour, and operator
• Automatic passenger counts by block, run, route, trip, stop, service period, day, hour, and operator
• Incident and event data
• NTD reporting utilizing the APC count data and system miles and hours information • Operational summary reports including login status reports, pull-in and pull-out reports, schedule adherence reports, etc.
• Vehicle health monitoring (VHM) reports to quickly identify vehicle problem trends before they become major issues
• Self-service reporting module allows users to create their own real-time dashboards and reports
• Ability to quickly apply data filters across all reports to perform and analyze what-if scenario modeling
The following screenshots provide examples of the data that can be accessed and pulled into a report. While there are an unlimited number of reports that the BI is capable of, we have chosen these illustrations based on the requirements outlined in the compliance matrix.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-81

4.7.2.1. Schedule Adherence
The table on the top-left displays departure performance for the previous day. Each agency can use this chart to determine whether the statuses for the previous day’s departures were unusual.

This table can help you identify the beginning of a problematic trend.

The on-time performance overview dashboard provides a high-level overview of the departure statuses. This dashboard will allow each agency to assess the late, early, and on-time statuses of departures over different time periods and by route. These charts will help you identify problematic trends or routes that have unacceptable amounts of departures that are not on time.

The two-line charts display departure statuses over time for the past 30 days and the past year.

The line charts allow you to determine whether there is a problematic trend in the proportion of departures that were not on time. Some trends are easier to identify over time.

The bar chart along the bottom reveals routes with an unacceptable number of early or late departures within the past month. This chart can be helpful when only particular routes have a problem with on-time departures; the line charts for the entire fleet might not indicate an issue.

Clicking any of the charts on the top row opens the on-time analysis in a new window where you have more options for drilling down and filtering. The next section describes the on-time analysis report. On the bar chart on the bottom, clicking a bar for a route opens a bar chart for that one route in a new window.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-82
On-time performance by route
This dashboard displays on-time performance by route. Using the information in the dashboard, you can identify dwell times versus run times, or identify routes that need performance improvements (and set the priorities for these improvements). The information in this dashboard reflects a date range set in the filter. The first bar chart displays the five worst performing routes based on their on-time statuses. The second graph displays the on-time performance for the five routes with the most riders. An impactful route might not have the worst on-time performance, but poor performance will affect more riders, which might increase the priority. Between these two bar charts, you can identify the worst performing routes and the routes that affect the most riders, and help you target remedial efforts on the routes that need it the most.

4.7.2.2. Events
The events dashboard displays the number and type of events over the date period that the filter specifies. Agencies use this dashboard to determine if there are an unusual number of events, the types of events, or a trend in events that can disrupt service. Events are occurrences that myAvail displays in the event, communications, and maintenance queues. Examples of events tracked by the system include the following:
• Emergency alarm
• Priority request to talk

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-83
• Request to talk
• Message from dispatch to vehicle failed
• Call to vehicle failed
• Late logon warning
• Transfer connection in jeopardy
• Message from vehicle
• System error message
• System warning message
• System informational message
• Wheelchair lift event (several levels–pass, fail, and skip) Number of events
The line chart displays the number of events by queue: event, communications, and maintenance. The agency can use the line chart to assess the number of events and determine whether there is a trend. The events dashboard can also be displayed as a pie chart to identify which types of events comprise the largest proportions of events, or as a bar chart to display the number of events by different categories such as day of the week, top five dispatchers, top five drivers, and hour of the day.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-84

4.7.2.3. Pullout/Pull-in
Revenue pullout overview
The revenue pullout overview provides a high-level overview of the statuses for revenue pullouts.

The agency can use this dashboard to assess the late, early, and on-time statuses of revenue pullouts over varying time periods and by route. These charts can help the agency identify problematic trends or routes that have unacceptable amounts of pullouts that are not on-time.

The table on the top-left displays revenue pullout performance for the previous day. The agency can use this chart to determine whether the statuses for the previous day’s pullouts were unusual.

This table can help the agency identify the beginning of a problematic trend.

Both line charts display revenue pullout statuses for the entire fleet over the past 30 days or the past year. These line charts can determine whether there is a problematic trend in the proportion of pullouts that were not on time.

The bar chart along the bottom displays revenue pullout statuses by routes over the past 30 days. This chart reveals whether a route has an unacceptable amount of early or late pullouts within the past month. This chart can be helpful when only particular routes have a problem with on-time pullouts; line charts for the entire fleet might not show a problem.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-85

4.7.2.4. Average Daily Ridership
The average daily ridership report displays the total and average ridership for the date range specified by the filter. It also compares this range to the same period in the previous year. The agency can use this report to see how ridership is changing over time. The summary view report shows information by service level (e.g., weekday, Saturday, Sunday).

The default report displays values for the entire property. The agency can use the filter pane to display ridership values for the routes you specify.

Note: A configurable system parameter determines whether this report utilizes either automated passenger counter (APC) data values or farebox ridership.

Click the plus sign for a service level to expand it and display ridership information for specific routes. For example, the expanded area below displays ridership for weekday routes.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-86
This report provides information by route about the portion of scheduled service that is not recorded, which the reports display as a percentage of total service. This report identifies the routes that have the most incomplete trip segments, incomplete timepoint segments, and stop segments. Avail understands the importance of accurate, reliable, and consistent data and this report highlights the scheduled data that the system is missing with a system generated explanation as to why a particular stop, timepoint or trip segment is missing to help you identify and correct the issue.

This report displays three key performance indicators (KPIs) at the top for the entire property:
• Stops: Indicates the number of incomplete stop segments, total scheduled stop segments, and the percentage of missed stop segments (incomplete/scheduled). • Timepoints: Indicates the number of incomplete timepoint segments, total scheduled timepoint segments, and the percentage of missed timepoint segments (incomplete/scheduled).
• Trips: Indicates the number of incomplete trip segments, total scheduled trip segments, and the percentage of missed trip segments (incomplete/scheduled).

A missed stop, timepoint, or trip segment occurs when there is scheduled service, but the system does not record that service occurring. A high percentage of missed service can occur for a wide variety of reasons and affects various statistics including route utilization. After identifying routes with high percentages of missing service, it is critical to investigate and determine the reason why they are occurring.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-87

4.7.2.5. Vehicle Health/Maintenance
The vehicle issues report displays the top 20 vehicles with the most issues. The agency can use this report to assess the prevalence of maintenance issues across the entire fleet to identify vehicles with an unusually high number of issues. The color-coded bar chart indicates the number of issues by category type. These types include pre-trip issues, ITS issues, and vehicle health monitoring (VHM) issues. The agency can use this report to identify vehicles with an unusually high number of issues for the date range that the filter pane specifies. On the Vehicle Issues report, each bar represents a vehicle. When you click on a bar, you can display the issues for a vehicle in more detail, as shown below, for the VHM Issues and ITS Issues.

ITS ISSUES

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-88

4.7.2.6. NTD Reports
The fixed route performance dashboard displays critical metrics in a dashboard format and as year-to-date tabular reports for printing. This report blends standard reporting while providing guided myDash® functionality. This report has four screens: dashboard, target definition, monthly metrics, and fixed route performance. Using the dashboard, the agency can select any metric that the system or a user generates. The system then displays the performance of that metric against a performance goal you specify for either the previous month or year-to-date (YTD). The agency can use the gear icon to select the metric they want to track and set the date range.

Avail’s NTD reporting capabilities have helped us get over 50 transit agencies certified to use our APCs and reporting in place of the outdated manual process. Here a few of the metrics the system can compile with the push of a button (showing both the average by period–weekday, Saturday, Sunday, and the total over a specified time interval):
• Actual miles
• Actual revenue miles
• Scheduled revenue miles
• Actual hours

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-89
• Actual revenue hours
• Scheduled revenue hours
• Unlinked passenger trips (UPT)
• Passenger miles (PM)
• Number of days scheduled operated
• Average passenger trip length (APTL)

4.7.2.7. myDash®
For a feature-rich dashboard set-up, the myDash® function allows the user to fully customize their BI dashboard from scratch. This approach is especially useful for individuals who are transit and data analysts.

When the user first selects the myDash® option, they are immediately presented with the following screen, which allows them to customize their dashboard right from the start. The “add” button, below each report selection, allows the individual to quickly select the reports they need by clicking on that button. Once the reports have been added, if the user selects the myDash® menu bar option again, it will refresh the screen and the reports are automatically populated into the dashboard. The user can also bookmark reports and adjust the layout by selecting the settings gear at the top right of the new tab option.

Some of the key reports that can be added to an individual’s dashboard include:

1. Schedule adherence by block, run, route, trip, stop, service period, day, hour, or operator

2. Run times that easily illustrate the difference between scheduled and real-time

3. Farebox ridership and revenue data by block, run, route, trip, stop, hour, etc.

4. Automatic passenger counts by block, run, route, trip, stop, hour, operator etc.

5. Incident and event data

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-90

6. NTD Reporting utilizing the APC count data and system miles and hours

7. Login status reports, pull in and pullout reports, etc.

8. Vehicle health monitoring and vehicle problem trends

4.7.2.8. Self-Service Reporting Module (SSRM)
Much like myDash®, when the user selects the self-service option, they are immediately presented with the following screen.

As the individual hovers over any of the symbols on the far-left navigation screen, they are presented with various options that allow them to build their report(s). The analysis option, illustrated below, allows the user to select the source from which they will pull their data, and once that option is selected, they will be directly presented with another field that allows them to select the specific data element (APC data, driver logons, fare currency, event data, etc.) they are interested in examining.

While this feature is intuitive, to ensure that each agency can fully leverage this useful tool, Avail Technologies will provide a training plan and training hours specific to this feature. In addition, to ensure that each agency receives a training plan that meets the requirements for their users and fulfills SSRM reporting infrastructure and requirements, this aspect will be fully vetted during the project kickoff of Avail’s project implementation plan.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-91
Using the analysis feature, users can create custom datasets that are easily exported to Excel, or visualizations can be created in the visual analysis tool. Users can also add their visualizations or tables to dashboards and reports within the self-service framework. All their work can then be shared with others across the organization.

At a high-level, SSRM capabilities include:
• Report management interface where users manage, schedule, and share dashboards, reports, and analyses.
• Data discovery for users to quickly visualize new insights with features like automatic data grouping, customizable in-cell graphics, and best-fit chart recommendations. • Report layout editor helps users design and format print-ready reports with data visualizations.
• Query builder for users to select the data sources they have access to, choose specific data for analysis, and feed this data into the analysis grid to create visualizations. • Metadata builder for IT and developers to define recognizable table and column names for users to query their data.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-92

4.8. Third-Party Integration
Through our onboard system, Avail Technologies has the capability to integrate with multiple third-party vendors by being able to directly wire those systems to our IVU. From there, the IVU and the third-party system readily communicates (bidirectionally) and this information is sent to and from the backend (myAvail). Avail uses both J1939 and J1708.

J1708 is the communications hardware standard, and we use J1587 as the communications protocol. These components form a communications network that transit vehicles use to connect various components. The nonproprietary standard allows different components produced by various manufacturers to communicate.

Avail uses the J1708 network, which connects components such as the farebox, internal signage, APC controller, and the destination sign.

The J1708 device driver provides an application program interface (API) for sending and receiving SAE J1708 messages. It is designed to work with our J1587 software and abstracts away the technical details and many complexities associated with message timing and interfacing to the physical layer. This increases the simplicity of the application software and improves reliability.

The service also provides an SAE J1939 protocol stack designed by Simma Software, a nationally recognized controller area network (CAN) bus expert, to meet the demanding needs of the highspeed CAN. This source code uses a high-performance modular design and has a simple API.

Interfaces such as SAE J1939, SAE J1708/J1587, Avail's IVU in-vehicle data service API, Ethernet, MGRs, back-end APIs, and cellular networks allow us to currently integrate with 50 third-party hardware and software vendors that support the public transit industry. Below is an image of just some of our third-party partners.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-93

4.8.1. Headsigns – TwinVision/Hanover/Aesys
For Avail, this is a standard J1708 integration connected to our IVU. If there are headsigns that have Wi-Fi capability, we will connect that headsign to the MGR so there is Wi-Fi capability.

Should the need arise, the bus operator could manually update the headsign with our system.

Avail Technologies integrates seamlessly with Twin Vision, Hanover, and Aesys headsign displays to support the integration that MBL is requesting for destination signs. We have been doing headsign integration since our first project over 23 years ago.

Avail is proposing to interface with the existing headsigns to provide the requested features for controlling the headsign. Triggering the headsign will work in accordance with each stop and timepoint encountered. When the vehicle is logged into a run using the MDT the following capabilities are supported based on operations:
• When operating on deadhead from the garage to the first trip of the run, the MDT will automatically command the headsign to display a message that can be configured by MBL. This message could be “outbound,” “inbound,” “out of service,” “from garage,” or the message that will be displayed during the first trip. • When the vehicle is logged into a run using the MDT but operating on deadhead to the garage from the final trip of the run, the MDT will automatically command the headsign to display a message that can be configured by MBL. This message could be “out of service,” “to garage,” or the message that will be displayed during the final trip.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-94
• When the vehicle is logged on but operating on deadhead for interlining between trips in the course of a run, the MDT will automatically tell the headsign to display a message that can be configured by MBL. This message could be “out of service” or the message displayed during either the previous or upcoming trip. • When the vehicle is logged into any run using the MDT, the vehicle operator will be able to override automatic headsign control and manually command the headsign to display one of a set of preconfigured messages that can be configured by MBL (e.g., “out of service” or “in training”).
• When the vehicle is in covert alarm mode, the MDT will automatically command the headsign to display one of a set of preconfigured messages that can be configured by MBL (e.g., “call police”).

4.8.2. Farebox – Cubic
Any of the fareboxes we integrate with supports a physical J1708 interface. J1708 refers to a Society of Automotive Engineers (SAE) serial communications hardware standard while J1587 is the communications protocol. These two components form a communications network that transit vehicles use to connect to various components in their fleet. myAvail and the farebox is connected by the J1708. Because of this connection, we can update farebox changes on the fly. If the route changes during the run, the updated route is sent to the farebox. There is also an option to send location data to the farebox upon door open events.

The J1708, which is also connected to the MDT, interfaces with the farebox and gives the operator a single point of logon for all connected components—when they log into the MDT, it automatically logs them into the farebox.

In fact, our J1708 integration capability is so strong that we helped GFI to perfect the J1708 interface between GFI and ITS systems. Through this interface, we can send driver ID, route, run, trip, direction, stop ID, and fare set to the farebox. In addition to this, to comply with NTD reporting requirements, myAvail designed BI reporting tools to provide reporting on the GFI data set. We can pull the entire dataset from the GFI database, providing a user-friendly data mining capability that anyone in your organization can adopt.

This is a powerful reporting engine and truly unique in the capabilities it provides. It is the key interface to the vast amount of data stored in our backend transit database and data warehouse, providing robust data analysis and reporting capabilities.

Some of the key features of the myAvail reporting module include:
• Farebox ridership and revenue data
• Automatic passenger counts
• NTD reporting utilizing the APC count data and system miles and hours information

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-95
The following screenshots are several examples of the data that can be mined from our data warehouse and pulled into a report. In the Farebox and APC Analysis option, the user can examine this data by route, block, run, fare, trip, vehicle, driver, month, date, hour, minute, day of week, direction, service level, stops, and peak times.

Reporting parameters for Farebox and APC Analysis
Day of week report

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-96
Report of APC and fare analysis
We provide a single point of login to your Genfare farebox via the MDT screen. We have numerous deployments of farebox/ITS integration, going back a decade, for the GFI/Genfare fareboxes. While myAvail can and has been successfully integrated with the fareboxes as you are using them now with your existing CAD/AVL systems, there is still support you may need from GFI to ensure you have the proper J1708 interface and licensing in place with GFI.

Through this integration, you will only need one reporting tool to correlate your APC data with your fare data.

4.8.2.1. Cubic
We are providing a single point of login to your Cubic
fareboxes. This is an off-the-shelf capability for Avail and will utilize the same implementation as installed at other
agencies. This interface allows the MDT to be the single login point for all connected components. You can check the
health of the unit and send driver ID, route, run, trip, block, and fare set to the farebox through this interface. Note: Cubic may require that a software upgrade is obtained in order to complete this integration.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-97
The myAvail reporting tools provide reporting on the fare data set. If the UFS data is made available to Avail via a remote database connection, Avail can provide the same data reporting features as is currently supported with GFI systems. However, this data is also controlled by MBL, and is not supplied to ITS contractors directly from Cubic. If MBL can access data or reports in a suitable data format, Avail can work with MBL to import the data for reporting purposes. No other vendor in the industry has the level of integration or the number of integrated solutions as Avail.

Avail has many years of experience with the Genfare manufactured farebox hardware and has recently begun the process of integration with the CUBIC TAP system. In fact, we currently have a Cubic TAP equipped farebox in the Avail lab for initial testing and validation of our standard J1708 farebox messages. Avail has developed an interface to produce the required logon and geolocation capabilities that property name has requested, and we will work with CUBIC to ensure full compatibility.

4.8.2.2. Fare Import Upload
One feature in the Planning and Scheduling suite is our Fare Import Upload card. This feature (and the data it captures) would typically be used be a range of roles at a transit agency, from the finance and executive team to planners and operations. Data from a customer’s fare system is imported to Avail’s Fare Import system and validated against transit schedule data. It’s important to note that multiple fare sources can be imported, including your Cubic data.

Ridership is a core data set for most high-level metrics and specific activities. This data can then be used to calculate KPIs, such as ridership or per revenue hour and used at a granular level to determine underperforming trips that may be cut from the service schedule or overloaded trips that may require the use of tripper buses to manage capacity problems in the future.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-98

4.8.3. Automatic Passenger Counter - InfoDev
Avail has numerous existing customers with NTD certified InfoDev APC systems. In fact, Avail has worked closely with the FTA to successfully implement a fast-track APC certification process that we are currently utilizing with all our customers who request NTD certification.

To save costs by leveraging existing equipment, which is fully compatible, Avail will integrate with your current InfoDev GW-200 Gateway APC systems on your fixed route fleet. The APC solution will be seamlessly integrated with our MDT and IVU for fully automated operation to provide a minimum of 97% accuracy. Counts are transmitted over the primary data network in real time to the central system to give dispatchers continuous feedback on busloads to allow them to proactively anticipate and prevent any over-capacity issues before they happen. In situations where feeder buses may be needed, equipping the dispatcher with the ability to see the real-time passenger counts enables them to make better decisions during regular operations.

This is also true when the operator needs to know the passenger count during an emergency.

Avail stores the real-time APC data in our data warehouse and can provide APC ridership data through our BI reporting toolset as well as through our vehicle replay feature.

4.8.4. TSP
Avail understands that MBL would like to work with a vendor who can provide integration for a TSP solution. Avail has supported multiple traffic signal priority integration projects over our history, including implementations with other systems such as the GTT Opticom solution in locations such as Grand Rapids, Michigan, and Indianapolis, Indiana (for the BRT solutions), and the Emtrac TSP solution in the Minneapolis / St. Paul area to support the Minnesota Valley Transit Authority regional system. We are prepared to support the future implementation of the MBL TSP solution when you are ready to implement it.

4.9. Transit Assets Suite (Option) (Trade Secret)
The transit assets suite meets all the technical aspects that MBL is seeking for your fleet maintenance management software. The transit assets suite was specifically designed to adhere to FTA’s Transit Asset Management Guide. As such, it can manage asset classes, and enable components of asset management including inventory, purchase and work orders, condition assessment, and performance analysis. You can track the lifecycle of all agency assets including rolling stock, components, equipment, and facilities. Our system will help your agency ensure safe, dependable, and accessible services while complying with the state of good repair.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-99
Transit Assets allows for a strategic and systematic process of operating, maintaining, upgrading, and expanding physical assets effectively throughout their life cycle. It focuses on business and engineering practices for resource allocation and utilization, with the objective of better decisionmaking based upon quality information and well-defined objectives.

The suite also has functionalities that include, but are not limited to:
 Generating work orders
 Maintaining parts and leased inventory
 Maintaining current and historical vehicle inventory and maintenance records  Creating and managing preventative maintenance programs  Managing asset conditions
 Managing daily services such as fuel and fluid consumption or tank meter entries  Having a fully customizable reporting dashboard and system (business intelligence).

The following screenshot illustrates the features of the transit assets suite.

Transit assets suite (trade secret)
This suite features smart search functionality and bookmark/favorite tagging. These features, coupled with the Wayfinder learning tool, provide an insightful environment for the user and make it easy for them to learn and understand.

4.9.1. Asset Inventory
Asset inventory is the foundational block for your transit asset maintenance software. It has specific features designed for vehicles (rolling stock), fixed assets (such as bus stop signs and maintenance garages), and components. It's geared towards tracking assets that move and integrates into our CAD AVL system; equipment deployed on a bus can be automatically identified.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-100
This suite identifies the agency’s assets, their location, and key attributes like age and type of asset. It has an inquiry view and vehicle status updates status; if a vehicle is going to be out of service you can mark it as unavailable.

Additionally, the components inventory provides a hierarchical method with the capability to break the asset inventory down to the smallest maintainable unit for your specific agency needs.

Asset inventory (trade secret)
The vehicle master card features comprehensive recordkeeping capabilities including the ability to add notes and photos for documentation and associate warranty information with a vehicle.

Multiple warranties for the same asset can be tracked and defined by the begin and end date, how much time remains, and if it's determined by calendar date, miles, or hours, Later when you create a work order, the first thing the system does is check for any active warranties; before the work order is logged, you are able to indicate if it is a warranty repair that may be reimbursed versus a general repair.

Other features include NTD statistics to help with reporting, inspections set up by mileage or time, tire tracking, assigned work orders, and the history of consumables, which is especially important for timely maintenance.

Vehicle history tracks everything that happened to the vehicle during a given period including miles, hours, failures, labor costs, consumables, and any overhead cost parts or outside work that was done allowing you to calculate the cost per mile, cost per hour, and miles between failures.

Service history is very important from a transit standpoint maintain vehicles in a state of good repair. Auditors can check individual records quickly and easily.

The vehicle information screen shows bus ID, model and year, what fleet it belongs to, chassis number, license, and tag expiration depending on state. The software is on the CAD/AVL side so MCDID tells the system what vehicle it is, you can put it in fleet group (fixed route, nonrevenue, paratransit, etc.).

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-101
Equipment that is specific to one bus is entered on the vehicle side, while things that are common to the entire fleet, are set up in fleet. Once you define a bus in the fleet, the characteristics are inherited throughout the record.

Vehicle information (trade secret)

4.9.2. Asset Condition
Asset condition provides the capability to track required condition ratings for FTA’s transit asset management plan and forms the foundation for asset condition monitoring utilizing the deep business intelligence capabilities of ETMS. Consumables, downtime, preventative maintenance performance, and vehicle health monitoring provide ample data to measure the condition of your assets in real time.

Asset condition (trade secret)

4.9.3. Fleet Management
Fleet management features are dedicated to managing rolling stock inventory. Preventative maintenance cycles, daily fleet service records, interfaces to fuel island systems, and fleet-specific repair campaigns are all managed here.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-102
Preventative maintenance determines the type and frequency of inspections and maintenance procedures, defines the minimum requirements for servicing and maintaining equipment, serves as a comprehensive maintenance checklist, and forecasts those inspections coming due. Utilizing our setup procedures improves the efficiency of determining that the preventative maintenance schedule is adhered to. These measures help reduce errors in day-to-day operations and increase the overall preparedness of the agency’s ability to serve the public. The implementation of preventative maintenance procedures is a vital part of efforts to promote safe practices.

The following screenshot illustrates the features of the fleet management module.

Fleet management (trade secret)
The fuel island feature allows users to import data from an automated fuel island. We have over 30 years of experience creating multiple fuel island interfaces; if an agency selects a vendor we currently do not have an interface for, one can easily and quickly be created if the system allows data export. The data from these systems will be imported into the myAvail database and integrates with inventory, vehicle maintenance, and general ledger. The module allows data import from a fuel island file, error log reviews, and access to fuel island files from within myAvail. The interface allows you to import the data you need to process and report on fuel and fluid usage across the fleet. The data is provided both through built-in standard reports and the business intelligence platform.
“S & A Systems, Inc., the manufacturer of
the FLEETWATCH Fuel and Fluids
Management System, have many
successful integrations with the Transit
Assets product offered by Avail
Technologies. Public Transit Agencies in
many states, including California, all
benefit from the seamless integration
between the FLEETWATCH System and
Transit Asset software. S & A Systems is a
proud partner with Avail Technologies in
their product offerings.”
Don Srygley, President
S & A Systems, Inc.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-103

4.9.4. Maintenance management
The vehicle maintenance system is designed to monitor maintenance activities and associated costs. Each vehicle is assigned a unique identification number and grouped into a fleet according to make, model, purchase date, etc. Pertinent fleet and vehicle information such as vehicle type, status, year, fuel capacity, seating capacity, expected MPG, and tire cost are also maintained here. Maintenance management is dedicated to managing the workflow and the workforce of both vehicles and facilities. Work orders are managed and assigned in this module.

Vehicle service work should be entered into the system daily; as the service information is entered, costs are calculated, and appropriate general ledger transactions are generated.

Performance information is available for each vehicle and fleet. Inventory levels of consumables such as fuel and oil are automatically reduced as the system is updated.

Data on tire usage and costs makes tracking tires easy. Daily entries track tire mileage, while special reports highlight tire maintenance requirements. Other reports include vehicle listing, tire listing, tire change report, tire overhead and cost report, monthly mileage report, monthly maintenance report, and several inspection due reports.

One of the unique features of myAvail ETMS is that a request for these work orders can come from anywhere in the organization. An operator identifying a failure on a pre-trip inspection or a customer service representative reporting a leaking sink in a transit center can be routed seamlessly into the maintenance management system to be prioritized, assigned, and repaired.

The work order processing module tracks and records maintenance activities, and interfaces with inventory, vehicle maintenance, vehicle problems, and general ledger. Class codes are used to define the inventory asset and expense accounts. Using the work order pending feature, work orders may be updated individually or in a batch update process. Parts issued on a work order will first be committed and display in the committed field on the inventory master. The available field displays the adjustment to the total available items by reducing the total amount by the number of items committed. Once the work order is updated, the on-hand quantity will be updated, reducing the total by the number of committed items. Committed will now display zero, and the available field will continue to display the reduced total. Journal entries are updated to a general ledger subsidiary journal.

Inspections are automatically updated in the vehicle master in the vehicle maintenance module.

Work orders can be generated for component inspections and rebuilds. In addition, campaign work orders can be generated for a range of vehicle fleets or components.

Each work order is printed with a bar code for quick scanning with the bar code unit. Work order material and labor may be tracked and updated via the bar code units, which, when updated, will automatically update on the work orders. Notes can be entered by mechanics or supervisors.

Objects such as schematics or pictures may be attached.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-104
Other components of the work order module include tool inventory tracking, tasks setup for employee assignments, and employee assignment time. Historical data may be reviewed at any time.

Any road call or safety defects that are entered in the vehicle problems field will automatically generate a work order. Any deferred defects created in vehicle problems will be available for assignment to a generated work order. When the work order is closed and updated, the assigned deferred defect will be marked as repaired.

All open work orders and additional information from the work order status maintenance form can be displayed on a large monitor (this requires a PC to run unattended).

The following screenshot illustrates the features of the maintenance management module.

Maintenance management (trade secret)

4.9.5. Parts Management
Parts management is a comprehensive inventory management system focused on ensuring the correct quantity of parts is on hand to repair mission-critical assets. From intelligent reordering systems to handheld bar code scanners (included with our offer), this system is optimized to manage inventory quickly and efficiently across your fleet and facilities maintenance divisions.

It also assists in managing, tracking, and maintaining inventory, costs and quantities through purchasing, receipts, invoices, issues, and associated costs.

Inventory adjustments, transfers, and physical inventory counts are also tracked here. The automatic reorder process provides the ability to manage minimum and maximum stock levels for auto-generation of purchase orders (POs) and may be adjusted before placing the purchase orders.

Daily service issues in vehicle maintenance and work order issues are interfaced with the inventory module and are capable of automatically reducing the level of inventory and interface

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-105
with the general ledger. Physical inventory counting and cycle counting are made easy with the inventory bar code system.

Adjustments to inventory can be processed at any time. Multiple inventory locations may be tracked, while PO invoicing computes the average costs for each item and updates the invoice information to accounts payable. This method of average costing is a standard practice used by the transit industry. Historical data is always available and maintained within the inventory module to assist in reporting, analyzing, and auditing.

The following screenshot illustrates the features of the parts management module.

Parts management (trade secret)

4.9.6. Facilities management
Facilities management allows you to manage your fixed assets. Preventative maintenance cycles and repair campaigns are also managed here. Facilities takes advantage of the same work order maintenance management as the vehicle systems. Facilities and fleet mirrors one another; they both utilize preventative maintenance cycles, work orders, and utilize inventory. The following screenshot illustrates the features of the facilities management module.

Facilities management (trade secret)

4.9.7. Business Intelligence
The transit assets suite also provides access to data driven reports in the maintenance dashboard.

Advanced business intelligence is a consolidated data warehouse and business intelligence

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 4-106
solution with data that spans your entire agency and intuitive visualizations that support informed decision making. The dashboard provides key metrics such as the cost of planned versus unplanned maintenance over specified periods, cost of road calls, and upcoming planned maintenance. Users can define KPIs, set targets, drill down to enable a more detailed analysis and paint a clear picture of the current performance, do self-service reporting, explore trends, and perform other key metrics.

Maintenance dashboard (trade secret)

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 5-1

5. Price
Avail understands the significance of this investment and the fact that you are making it to help you achieve your stated goals, not just to merely purchase technology. In our pricing proposal we want to demonstrate our commitment to Montebello Bus Lines to not only help you achieve your goals, but also to assure you that Avail will be a valued long-term partner MBL, and truly has your best interests in mind. But before we get into the details of the pricing, we would like to emphasize a few key aspects of doing business with Avail.

Avail’s 24-year proven track record of having backward compatibility with in-vehicle and backend technology ensures your system will be just as current 15 years from now as it is the day you buy it and requires no other investment over the normal support contracts and standard vehicle replacement you do today. As you add vehicles, Avail provides our latest in-vehicle technology that is backward compatible and by being under long-term support you receive periodic software updates. That’s a huge long-term cost of ownership benefit of working with us over other vendors.

Avail’s CAD/AVL product suites were developed specifically for the needs of public transit operations and have been adopted nationwide by scores of transit users for decades. Our ETMS product not only includes all the CAD/AVL software and hardware modules requested by this RFP, but some of the nation’s most forward thinking and feature rich ERP/EAM, Business Intelligence, and data warehousing products available. Our proven tools and processes will ensure that MBL achieves the highest level of operational improvements and efficiency.

Avail’s services and support contracts go far beyond just answering the phone and providing bug fixes. We have people who are there helping you squeeze every ounce of operational benefit out of the investment you made. We provide additional training as people leave and change roles, we provide hands on help when you’re doing route analysis in preparation of a service change, we develop reports and queries to make sure you’re utilizing the data, and much more.

And again, it’s all included in the price shown. These are all additional charges with other vendors.

While companies come and go, Avail is employee owned. The people you will work with daily have a vested interest in doing the right thing. We are Avail, here for you today. We will be Avail, for you tomorrow.

To further demonstrate our commitment to MBL, you will see in our response to the technical scope of the proposal that we can meet, and in some cases exceed, your desired outcome of the specifications with our off the shelf myAvail and myStop® solutions. This approach will provide MBL with a modern, Enterprise level CAD/AVL replacement for a price that is budget friendly both now and for long-term cost of ownership.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 5-2
To summarize, we believe the offer that Avail is extending will not only meet the needs of MBL, but our approach will be very competitive when comparing to other fully compliant offers. You may, however, find that Avail doesn’t have the lowest price at initial glance, but history has shown that vendors who win on lowest upfront price typically make it up along the way with change orders and upcharges for what they consider to be “additional services.” When you hire Avail, the price you see is the price you pay. We will do what it takes and invest where we need to invest to ensure your success from the very beginning.

5.1. Pricing Approach
To facilitate your review and ensure MBL evaluation committee have the information you need to make an informed decision, Avail has included the following subsections within our Price Proposal:
 Avail has provided additional details on our pricing, i.e. “Pricing Notes”  Avail has acknowledged the recommended project Payment Milestones  Lastly, the final section of this document will be Exhibit D – Price Proposal Sheet

5.2. Pricing Notes (Confidential and Proprietary)
Avail would like to provide the following additional details regarding our pricing. The notes here refer directly to the sections and line items in Exhibit D – Price Proposal Sheet. As you review the price sheet, you will notice “included” or “see price notes” in some of the cells. “Included” indicates the item is included in the overall price but has not been broken out due to the integrated nature of the item in our system and/or pricing. “See price notes” pertains to any item where we have provided additional explanation in the following sections.

5.2.1. Item #4 – New CAD/AVL Equipment
Avail recognizes that Montebello Bus Lines is procuring CAD/AVL equipment for 66 vehicles.

Montebello Bus Lines is an existing customer that currently has our latest equipment on 16 vehicles.

5.2.2. Item #5 – Infotainment Passenger Display Signs
In addition to the 50 buses (2 signs per bus) which will be receiving new MPM infotainment signs, Avail is also providing 16 controllers for the 16 buses with the existing Luminator infotainment signs.

5.2.3. Item #8a – Ubisense Yard Management System
MBL currently uses our standard myAvail Yard Management solution. Due to the requirements in the RFP to “automatically record movements of a vehicle in, out of, and within the yard”, Avail

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 5-3
has provided pricing for the Ubisense Yard Management system. If MBL wishes to continue to utilize the myAvail Yard Management solution, this would provide cost savings.

5.2.4. Item #9 – Cloud and Wayside CAD/AVL Installation All cloud hosting of the central CAD/AVL system is currently covered under the existing support and warranty agreement between MBL and Avail Technologies.

This section includes pricing for all cloud-based services associated with MessagePoint Media and physical installation.

5.2.5. Item #11 – Training, Maintenance, and Technical
Support
Support pricing includes all feature functionality that MBL purchased through Avail Technologies, along with the additional features of Ubisense, MessagePoint Media (Wayside and Infotainment), and VoIP.

5.2.6. Item # Option 1 – Pre-Trip
Pre-Trip is included in our base offering.

5.3. Payment Milestones (Confidential and Proprietary)
The milestone payment schedule below tracks our project implementation plan/schedule and can be reviewed during negotiations. *
*The support and warranty term can either be capitalized and the value included in the above milestones or paid annually at the agreed rate for the term commencing upon completion of System Acceptance.

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 5-4

5.4. Exhibit D – Price Proposal Sheet (Confidential and Proprietary)
Avail has included Exhibit D – Price Proposal Sheet on the following pages of the proposal.

EXHIBIT D
RFP No. 23-8

COMPUTER-AIDED DISPATCH/AUTOMATIC VEHICLE LOCATION SYSTEM COST PROPOSAL SHEET (Three Year Term)
CAD/AVL System RFP No. 23-8
In accordance with the Request for Proposal issued by the City of Montebello Transportation Department (hereinafter referred to as "Contractor/Proposer), the undersigned proposing company hereby agrees to furnish all necessary labor, materials and incidentals required for the above stated contract as set forth in the Scope of Work and any addenda thereto, and to perform all work in the manner and time prescribed therein.

CONFIDENTIAL AND PROPRIETARY

CONFIDENTIAL AND PROPRIETARY

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 6-1

6.Appendix

1. Forms

2. Compliance Matrix

3. Ubisense Proposal

4. Sample Maintenance Plan

5. Sample Training Plan

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 6-2

1. Forms

1. Proposal Submittal Checklist

2. Forms and Certifications

3. Certificate of Status

4. Exhibit A Indemnification and Hold Harmless Agreement

5. Exhibit B References

6. Exhibit C Insurance

7. Exhibit D Cost Proposal Sheet (Included in Section 5)

8. Exhibit E Statement of DBE Participation

9. Exhibit F Bidder’s List of Subcontractors DBE and Non-DBE

10. Exhibit G Certification Regarding Debarment, Suspension and Other Matters

11. Exhibit H Performance Guarantee Certification

12. Exhibit I Performance Bond

13. Exhibit J Irrevocable Standby Letter of Credit Certificate a. Avail Technologies Performance Guarantee Letter
b. Statement from Banking Institution

14. Exhibit K Bank Draft

CAD/AVL System RFP No. 23-8
7 Montebello Bus Lines

PROPOSAL SUBMISSION CHECKLIST
This checklist must be completed and returned with the Proposal. Failure to return this checklist may be cause for considering the Proposal non-responsive.

Description Section/
Page
Proposer shall
initial here
1 Proposal Page # 5
2 Letter of Transmittal Page # 43
3 Licensing, Permits, and Certificates Page # 17
4 Indemnification and Hold Harmless Agreement and Waiver of Subrogation and Contribution
Exhibit A
5 References Exhibit B
6 Insurance Exhibit C
7 Cost Proposal Sheet Exhibit D
8 Statement Of Disadvantaged Business Enterprise Participation Exhibit E 9 Bidder’s List of Subcontractors (DBE and Non-DBE) Exhibit F 10 Certification Regarding Debarment, Suspension…. Exhibit G 11 Performance Guarantee Certification Exhibit H
12 Performance Bond Exhibit I
13 Irrevocable Standby Letter Of Credit Certificate Exhibit J 14 Bank Draft Exhibit K

OPTIONAL ITEMS
15 Requests for exceptions or deviations. Page # 8
Company Name:

Name of Proposer initialing document (print):

Email address of Company Contact:

Signature:

Title:

Date:

Avail Technologies, Inc.

Kevin McKay
[email protected]
Chief Operating Officer
4/18/2023
N/A

Secretary of State
Certificate of Status
I, SHIRLEY N. WEBER, PH.D., California Secretary of State, hereby certify:

Entity Name: AVAIL TECHNOLOGIES, INC
Entity No.: 3487754
Registration Date: 06/15/2012
Entity Type: Stock Corporation - Out of State - Stock
Formed In: PENNSYLVANIA
Status: Active
The above referenced entity is active on the Secretary of State's records and is qualified to transact intrastate business in California.

This certificate relates to the status of the entity on the Secretary of State’s records as of the date of this certificate and does not reflect documents that are pending review or other events that may impact status.

No information is available from this office regarding the financial condition, status of licenses, if any, business activities or practices of the entity.

IN WITNESS WHEREOF, I execute this certificate and affix the Great Seal of the State of California this day of March 16, 2023.

SHIRLEY N. WEBER, PH.D.

Secretary of State
Certificate No.:

To verify the issuance of this Certificate, use the Certificate No. above with the Secretary of State Certification Verification Search available at bizfileOnline.sos.ca.gov. 091950731

CAD/AVL System RFP No. 23-8
Montebello Bus Lines

EXHIBIT B

REFERENCES
List at Least Three (3) Professional References:
1 Project City/Agency/Other:

Person of Contact:

Phone Number:

E-mail Address:

Address:

City, State, Zip Code:

Description of Contract (Please
include contract value, award
date, term of contract, and
description of work):

Contract Value: $
Award Date:

Term of Contract:

Description of Work:
2 Project City/Agency/Other:

Person of Contact:

Phone Number:

E-mail Address:

Address:

City, State, Zip Code:

Description of Contract (Please
include contract value, award
date, term of contract, and
description of work):

Contract Value: $
Award Date:

Term of Contract:

Description of Work:
3 Project City/Agency/Other:

Person of Contact:

Phone Number:

E-mail Address:

Address:

City, State, Zip Code:

Description of Contract (Please
include contract value, award
date, term of contract, and
description of work):

Contract Value: $
Award Date:

Term of Contract:

Description of Work:

ITS Implementation and Upgrades
1/21
ITS Implementation and Upgrades
Foothill Transit
LaShawn Gillespie, Director of Customer Service and Operations 626-931-7206
[email protected]
100 S. Vincent Ave., Suite 200
West Covina, CA 91790
The City of Norwalk - Norwalk Transit System (NTS)
12700 Norwalk Boulevard
Norwalk, CA 90650
562-929-5554
[email protected]
Derek Donnell
Stanislaus Regional Transit Authority (StanRTA)
1001 9th Street
Modesto, CA 95353
Adam Barth, Chied Executive Officer
209-774-4586
[email protected]
$10.6 Million
1,756,134.00
ITS Implementation
Until 2028
1/22
Until 2025
1/18
Until 2026
$1,400,000.00

CAD/AVL System RFP No. 23-8
Montebello Bus Lines

EXHIBIT C

INSURANCE
The Proposal shall include a statement that the insurance requirements set forth in the contract documents can be obtained and will be carried without reservation or exclusion should Proposer be awarded a contract pursuant to this RFP.

The successful Proposer shall at all times during the term of the awarded Agreement, carry, maintain, and keep in force and effect, with an insurance company admitted to do business in California, rated “A” or better in the most recent A.M. Best’s Insurance Rating Guide, and approved by the CITY, a policy or policies of:

A. Commercial General Liability Insurance using Insurance Services Office Commercial General Liability form CG 00 O1 or the exact equivalent. Defense costs must be paid in addition to limits.

There shall be no cross liability exclusion for claims or suits by one insured against another. Limits shall be no less than $1,000,000 per occurrence for all covered losses and no less than $2,000,000 general aggregate.

B. Business Auto Coverage on ISO Business Auto Coverage form CA 00 O1 including symbol 1 (Any Auto) or the exact equivalent. Limits shall be no less than $1,000,000 per accident, combined single limit. If Contractor owns no vehicles, this requirement may be satisfied by a non-owned auto endorsement to the general liability policy described in the preceding subsection. If Contractor or Contractor’s employees will use personal autos in any way on this project, Contractor shall provide evidence of personal auto liability coverage for each such person.

C. Workers' Compensation insurance on a state approved policy form providing statutory benefits as required by law with employer's liability limits no less than $1,000,000 per accident for all covered losses.

D. Professional Liability or Errors and Omissions Insurance as appropriate to the profession, written on a policy form coverage specifically designed to protect against acts, errors or omissions of the Contractor and "Covered Professional Services" as designated in the policy must specifically include work performed under this Agreement. The policy limit shall be not less than $1,000,000 per claim and in the aggregate. The policy must "pay on behalf of' the insured and must include a provision establishing the insurer's duty to defend. The policy retroactive date shall be on or before the effective date of this Agreement. City, it’s officers, employees, attorneys, and designated volunteers shall be named as additional insured on the policy, or policies, as to commercial general liability bodily injury and property damage coverage’s and automobile coverage’s with respect to liability arising out of successful Proposer’s work under this Agreement.

E. All insurance policies shall provide that the insurance coverage shall not be non-renewed, canceled, reduced, or otherwise modified (except through the addition of additional insureds to the policy) by the insurance carrier without the insurance carrier giving City thirty (30) days' prior written notice thereof. Any such thirty (30) day notice shall be submitted to City via certified mail, return receipt requested, addressed to "Risk Manager," City of Montebello, 1600 West Beverly

ACKNOWLEDGED

CAD/AVL System RFP No. 23-8
Montebello Bus Lines
Boulevard, Montebello, California, 90640. Contractor agrees that it will not cancel, reduce or otherwise modify said insurance coverage.

F. Contractor shall submit to City (i) insurance certificates indicating compliance with the minimum worker's compensation insurance requirements above, and (ii) insurance policy endorsements indicating compliance with all other minimum insurance requirements above, not less than one (1) day prior to beginning of performance under this Agreement. Endorsements shall be executed on City's appropriate standard forms entitled "Additional Insured Endorsement".

CAD/AVL System RFP No. 23-8
Montebello Bus Lines

EXHIBIT E

STATEMENT OF

DISADVANTAGED BUSINESS ENTERPRISE PARTICIPATION
This proposal provides for the following Disadvantaged Business Enterprise participation:

Disadvantaged Business Enterprise
Firm Name
Address
Phone Number
Type of Business
Current DBE Certification? Yes* *No
*(If "Yes," attach copy of current Letter of Certification and copy of current Statement of Personal Net Worth.)
Total $
% of Total Contract
Signature: Date:
314-363-6626
4/13/2023
6422 Bridgecrest Dr, Lithia, FL 33547
Anderson Technical Solutions, LLC
X
Commercial/Government Installations

4.33%
100,500.00

CAD/AVL System RFP No. 23-8
Montebello Bus Lines

EXHIBIT F
Bidder’s List of Subcontractors (DBE and Non-DBE)
Part I
The bidder shall list all subcontractors (both DBE and non-DBE) in accordance with Section 2-1.054 the Standard Specification and per Title 49, Section 26.11 of the Code of Federal Regulations. This listing is required in addition to listing DBE Subcontractors elsewhere in the proposal. Photocopy this form for additional firms.

Firm Name/
Address/
City, State, ZIP
Phone/
Fax
Annual Gross
Receipts
Description of Portion of Work to be
Performed
Local Agency Use Only
(Certified DBE?)
Name Phone < $1 million YES
< $5 million NO
Address < $10 million If YES list DBE #:

Fax < $15 million
City State ZIP > $15 million Age of Firm (Yrs.)
Name Phone < $1 million YES
< $5 million NO
Address < $10 million If YES list DBE #:

Fax < $15 million
City State ZIP > $15 million Age of Firm (Yrs.)
Name Phone < $1 million YES
< $5 million NO
Address < $10 million If YES list DBE #:

Fax < $15 million
City State ZIP > $15 million Age of Firm (Yrs.)
Lithia, Fl 33547
Installation of CAD/AVL sysyem snd components
6422 Bridgecrest Dr
Anderson
Technical
Solutions, LLC 314-363
6626
Message Point
Media of Alabama,
Inc
4628 Montevallo Rd,
Ste 204
Birmingham, AL
35210
Ubisense America
LLC
1630 Welton St
STE 1000E
Denver, CO 80202

1.720.549.7553
Services
Real Time Vehicle Location Hardware
Yard Management Solution
51519

CAD/AVL System RFP No. 23-8
Montebello Bus Lines
Part II
The bidder shall list all subcontractors who provided a quote or bid but were not selected to participate as a subcontractor on this project. This is required for compliance with Title 49, Section 26 of the Code of Federal Regulations. Photocopy this form for additional firms.

Firm Name/
Address/
City, State, ZIP
Phone/
Fax Annual Gross Receipts Description of Portion of Work to be Performed
Local Agency
Use Only
(Certified
DBE?)
Name Phone < $1 million YES
< $5 million NO
Address < $10 million If YES list DBE
#:

Fax < $15 million
City State ZIP > $15 million Age of Firm
(Yrs.)
Name Phone < $1 million YES
< $5 million NO
Address < $10 million If YES list DBE
#:

Fax < $15 million
City State ZIP > $15 million Age of Firm
(Yrs.)

CAD/AVL System RFP No. 23-8

EXHIBIT G

CERTIFICATION REGARDING DEBARMENT, SUSPENSION AND OTHER RESPONSIBILITY MATTERS -

PRIMARY COVERED TRANSACTIONS
The Avail Technologies, Inc./ Kevin McKay certifies to the best of it's (Firm Name/ Principle)
knowledge and belief, that it and its principals:

1. Are not presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from covered transactions by any Federal department or agency:

2. Have not within a three-year period preceding this proposal been convicted of or had a civil judgment rendered against them for commission of fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a public (Federal, State or Local) transaction or contract under a public transaction; violation of Federal or State antitrust statutes or commission of embezzlement, theft, forgery, bribery, falsification or destruction of records, making false statements or receiving stolen property;

3. Are not presently indicted for or otherwise criminally or civilly charged by a government entity (Federal, State or local) with commission of any of the offenses enumerated in paragraph (2) of this certification; and

4. Have not within a three-year period preceding this application/proposal had one or more public transactions (Federal, State or local) terminated for cause of default.

If unable to certify to any of the statements in this certification, the participant shall attach an explanation to this certification.

THE PRIMARY PARTICIPANT Avail Technologies, Inc./Kevin McKay _ CERTIFIES (Firm Name/Principal)

OR AFFIRMS THE TRUTHFULNESS AND ACCURACY OF THE CONTENTS OF THE STATEMENTS SUBMITTED ON OR WITH THIS CERTIFICATION AND UNDERSTANDS THAT THE PROVISIONS OF 31 U.S.C. SECTIONS 3801 ET SEQ. ARE APPLICABLE THERETO.
_ _ Chief Operating Officer
Signature and TitjexJi Authorized Official
The undersigned chief legal counsel for the Avail Technologies, Inc. (Contractor) hereby certifies that the Avail Technologies, Inc. (Contractor) has authority under State and Local law to comply with the subjeoburanceijharthe certification above has been legally made.

Signature^ Attorney \ v Date
Montebello Bus Lines

CAD/AVL System RFP No. 23-8
Montebello Bus Lines

EXHIBIT I

PERFORMANCE BOND
KNOW ALL MEN BY THESE PRESENTS: that
(Insert full name and address and legal title of Contractor) as Principal, hereinafter called Contractor, and,
(Insert full name and address or legal title of Surety) as Surety, hereinafter called Authority, in the amount of $_____________ for the payment whereof Contractor and Surety bind themselves, their heirs, executers, administrators, successors and assigns, jointly and severally, firmly by these presents.

WHEREAS, Contractor has by written agreement dated _______________________, 20____, entered into a contract with the City for Contract No.__________________, which contract is by reference made a part hereof, and is hereinafter referred to as the “Contract”.

NOW, THEREFORE, THE CONDITION OF THIS OBLIGATION is such that, if Contractor shall promptly and faithfully perform said Contract, then this obligation shall be null and void; otherwise it shall remain in full force and effect.

The Surety hereby waives notice of any alteration or extension of time made by the City.

Whenever Contractor shall be, and is declared by the City to be in default under the Contract, the City having performed City’s obligations thereunder, the Surety may promptly remedy the default, or shall promptly

1. Complete the Contract in accordance with it terms and conditions, or

2. Obtain a bid or bids for completing the Contract in accordance with its terms and conditions, and upon determination by Surety of the lowest responsible bidder, or, if the City elects, upon determination by the City and the Surety jointly of the lowest responsible bidder, arrange for a contract between such bidder and the Authority, and make available as Work progresses (even though there should be a default or a succession of defaults under the contract or contracts of completion arranged under this paragraph) sufficient funds to pay the cost of completion less the balance of the contract price; but not exceeding, the amount set forth in the first paragraph hereof.

The term "balance of the contract price," as used in this paragraph, shall mean the total amount payable by the City to Contractor under the Contract and any amendments thereto, less the amount properly paid by the City to Contractor.

Any suit under this bond must be instituted before the expiration of two (2) years from the date on which final payment under the Contract falls.

No right of action shall accrue on this bond to or for the use of any person or corporation other than the RECIPIENT or the heirs, executors, administrators or successors of the City.

Not Applicable
Avail Technologies will provide a Letter of Credit as its Performance Guarantee if chosen for award (Per RFP pg. 18)

CAD/AVL System RFP No. 23-8
Montebello Bus Lines
Signed and sealed this ____________________ day of 20____.

WITNESS PRINCIPLE
(SEAL)
(TITLE)

WITNESS SURETY
(SEAL)
(TITLE)
Attach hereto proof of authority of officers or agents to sign bond.

CAD/AVL System RFP No. 23-8
Montebello Bus Lines

EXHIBIT J

IRREVOCABLE STANDBY LETTER OF CREDIT CERTIFICATE
The undersigned states that he/she is of the of the
(Title)
(The “Beneficiary”) and hereby
(Name of Beneficiary)
Certifies on behalf of the Beneficiary to (the "Bank), with (Name of Issuing Bank)
Reference to Irrevocable Standby Letter of Credit No. Issued by the Bank (the "Letter of Credit"), that:

1. The undersigned is duly authorized to execute and deliver this certificate on behalf of the Beneficiary.

2. The Beneficiary is making a drawing under the Letter of Credit.

3. An Event of Default has occurred under Contract No.

4. The amount of the draft presented with this certificate does not exceed the total maximum amount drawable today under the Letter of Credit as provided therein.

IN WITNESS WHEREOF, this certificate is executed this __________________ day of_____, 20____.

NAME OF BENEFICIARY
By:

Its:

Not Applicable
Per RFP (pg 18), "If the Contractor chooses to provide a Letter of Credit as its Performance Guarantee, the City shall furnish with its bid, certification that an Irrevocable Standby Letter of Credit will be furnished should the Bidder become the successful Contractor. The Contractor shall also provide a statement from the banking institution certifying that an Irrevocable Standby Letter of Credit for the action will be provided if the Contract is awarded to the Bidder." Avail has provided a statement from the banking institution on the following page.

April 20, 2023
Rohan Anderson
Senior Management Analyst
Montebello Bus Lines
400 S. Taylor Ave.

Montebello, CA 90640
RE: Statement on Bonding Requirements, CAD/AVL System RFP No. 23-8 Mr. Anderson,
Avail is pleased to submit our proposal in response to the City of Montebello CAD/AVL System RFP No. 23-8. Regarding the City’s Bond Requirements, specifically the Performance Guarantee, the City has provided for two approaches: a Performance Bond or a Letter of Credit. Avail is choosing to provide an Irrevocable Standby Letter of Credit, and we have included the requested letter from our Banking partner showing support.

Avail will provide a Performance Guarantee for the project in its entirety, but we are proposing a slightly modified approach of doing so. Avail is proposing to divide the project into smaller distinct phases with clearly defined deliverables not to exceed $500,000. At the onset of each phase, Avail will provide an irrevocable LOC of $500,000 for that phase. Upon the City’s formal acceptance of all work and deliverables for that phase, Avail will then provide another $500,000 LOC for the next phase, and so on. We believe our proposed approach balances the City’s need for protection while allowing Avail to manage the impact on our company's working capital and line of credit.

Avail took a similar approach to the City’s original solicitation for an ITS system in 2014, and we successfully completed that contract with the City. We are proud to be the incumbent ITS provider to the City for nearly a decade. As such, there are several other factors that provide the City additional protections and risk mitigations that are unique to Avail:

1. Our cloud-based central system is already in use by the City of Montebello. So this project is simply an ‘upgrade’ for Avail vs a full ground up replacement for another vendor.

2. Over the past year+ the City has purchased 16 new buses that are equipped with Avail’s latest generation ITS hardware. Our proposed solution preserves this investment for the City vs needing to replace with a different vendor’s equipment.

3. Avail is proposing a fully off-the-shelf solution that is successfully deployed with peer agencies in your nearby area including Foothill Transit, Norwalk Transit, and Antelope Valley Transit.

Confidential and Proprietary

2 Avail is providing the requested bid guarantee equal to 10% of the first-year bid price in the form of a certified check. This is a show of commitment that we are serious about being responsive to your needs as outlined in your RFP and willing to enter into good faith negotiations should the City deem our approach outlined above worthy of consideration.

In closing, Avail greatly values our relationship with the City of Montebello and the opportunity to provide you with technologies and services this past decade. We are committed to being able to continue to do so in the coming years as a result of this procurement.

Sincerely,
Rick Spangler
Chief Technology Officer
cc Dorsey Houtz, Chief Executive Officer
Kevin McKay, Chief Operating Officer

April 20, 2023
Rohan Anderson
Senior Management Analyst
Montebello Bus Lines
400 S. Taylor Avenue
Montebello, CA 90640
Re: Avail Technologies
Dear Sir or Madam:

Please be advised that Avail Technologies, Inc. has an approved facility in which they have the availability to issue irrevocable letters of credit to support the contract should they be awarded the bid.

AmeriServ believes in a partnership with the customers we serve, and Avail is one of our highly valued relationships. We have built this engagement on trust, integrity and strong lines of communication, all of which are attributes of the Avail management team.

Based on these qualities, AmeriServ looks forward to a long-term relationship with the company.

Sincerely,
Tara M Shaffer
Senior Vice President
Commercial Banking

Montebello Bus Lines

EXHIBIT K
Bank Draft

FOR VALUE RECEIVED
Pay on the presentment to the sum of
(Name of Beneficiary) Dollars ($)
Charge to the Account of Irrevocable Standby Letter of
(Name of Issuing Bank)
Credit No. Dated:

To
(Name of Issuing Bank)

NAME OF BENEFICIARY
By
Its
Not Applicable
Per RFP (pg 18), "If the Contractor chooses to provide a Letter of Credit as its CAD/AVL System RFP No. 23-8 Performance Guarantee, the City shall furnish with its bid, certification that an Irrevocable Standby Letter of Credit will be furnished should the Bidder become the successful Contractor. The Contractor shall also provide a statement from the banking institution certifying that an Irrevocable Standby Letter of Credit for the action will be provided if the Contract is awarded to the Bidder."

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 2-3

2. Compliance Matrix
Avail has compiled the Scope of Work from the RFP and provided a matrix of our compliance for each requirement.

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines Stated Requirement Proposed Compliance (C, CM, NC) Alternate Stated Requirement 1: Computer‐Aided Dispatch and Automated Vehicle Location(CAD/AVL) System The Computer‐Aided Dispatch (CAD) component shall be the primary means of assigning, overseeing, and communicating with MBL vehicles; preparing and processing incident reports.

C
CAD shall support multiple user groups (e.g., driver supervisors,operations managers, system administrator) with settable system rights and privileges. CAD functionality shall be available on MBL workstations via a web‐based application or similar means.

C
The Automatic Vehicle Location (AVL) component shall store, and regularly update real‐time vehicle location information of MBL vehicles. C The AVL component of the total solution shall display the vehicle information in real‐time on a geographic map at workstations for dispatch, customer service and other stakeholders along with otherpertinent information regarding the route, vehicle and schedule data.

C
The CAD/AVL system shall also be able to integrate or import transit data (Routes, Stops, Trips, etc.) via direct integration, and/or imports fromroute/scheduling exports.

C
The CAD/AVL system shall also have the capability to input changes to the line, pattern and schedule data from a workstation, for full or ad‐hocchanges and detours at the trip, run and line levels. The system shall also support interlining.

C
Proposer shall be sufficiently knowledgeable of the transit scheduling software to carry out the required integration for meeting these CAD/AVL system specifications.

C
Such bidirectional data transfer and synchronization with the CAD/AVL System and other MBL systems shall occur either automatically or upon user initiation, dependent upon MBL CAD/AVL System administrator settings.

C
2: Graphical User Interface
All the information that is provided to the CAD/AVL users shall be via intuitive and easy to use Graphical User Interfaces (GUI). C CITY OF MONTEBELLO REQUIREMENTS MATRIX RFP No. 23‐8 Computer Aided Dispatch/Automatic Vehicle Location System 04.20.2023 4/20/2023 Compliance Matrix 1

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines The GUI shall not be static and shall be fully customizable for each class of user. For example, dispatchers shall be able to customize what they are able to view on the screens related to route and vehicle information, customer service agents shall be able to customize what they are able to view on the screens related to real‐time vehicle/route performanceinformation and triggers etc.

C
The system shall display if vehicle(s) are in operation but have not been logged in. C
The dispatchers shall have the capability to remotely login these vehicleswith the operator and route credentials which shall populate all the other on‐vehicle systems through single sign‐on.

C
3: Geographic Display/Functionality
Geographic display/functionality shall include the following but not limited to: C• Allow centering geographic display on and automatically tracking a specified vehicle C
• Allow centering on specified lines, stops, and time points. C• Allow selection of vehicle icon to display text/tabular display dataabout vehicle C• Automatically adjust minor vehicle location discrepancies to showvehicle icons on streets C • Automatically center the display on a vehicle with a covert alarm status while the covert alarm is active C
• Include an up to date map of all highways, streets, and roads by name C • On highest‐level map, show MBL’s full service area C• On lowest‐level map, show all streets, roads, railroad tracks, water boundaries, jurisdictional boundaries, bus stops, transfer points, and significant landmarks within the displayed area
C
4: Operations Display/Functionality
Operations display/functionality shall include the following, but not limited to: C
• Display the conditions, location, direction of travel and route/schedule adherence of vehicle C
• Display selected lists of data, including vehicle schedules, Operator identification, assignments and schedules, pull‐in/layover status, back in‐service time/place, schedule and route adherence.

C
4/20/2023 Compliance Matrix 2

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • Display assignments of operators to lines/runs and or vehicles. C • Display various types of canned and custom text messages C • Visible list of unacknowledged and acknowledge message and responses
C
• Allow the ability to create unlimited customized dispatch triggers and/or alerts C
• Triggers and/or alerts shall have the capability to be created in real‐ time within the CAD component C
• Operations status entries shall be generated automatically by the CAD/AVL system when an out‐of‐tolerance condition is detected. The CAD/AVL system shall generate notifications for a number of vehicle C
5: Incident ReportingThe CAD/AVL system shall support automatic and manual collection and entry of vehicle information for incident reports. C
For each incident report, the CAD/AVL system shall automatically record vehicle status, run, line, schedule deviation, time, operator identification, location, alarm status, other pertinent vehicle information, system date and time, workstation identification, and dispatch user.

C
Incident reports shall accept from a console and record manually entered text, coded, combo‐boxed or check‐boxed notes, and anindication that the incident is closed or the report cancelled.

C
The CAD Incident Report subsystem shall also include the following features, but not limited to: C• Automatically assign a unique identification to each created incident report
C
• Be searchable by any incident report data field C
• Allow recording of free‐form text comments (i.e. Memo field) C• Be exportable in a various format (e.g. Comma delimited, PDF, and MS Office applications) C
• Maintain a log of incident report creations and modifications by user,date, and time C6: Time of Arrival and Departure Data The CAD/AVL System shall determine dynamic estimated time of arrival to the next vehicle stop for each vehicle based on data from the AVLSystem.

C
4/20/2023 Compliance Matrix 3

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines The time of arrival information shall be available for the Passenger Information Display System (PIDS), internet access including MBL’s public website, Google, Computer‐Aided Dispatch (CAD), and other systems. C The time of arrival/departure information shall be determined using an analytical algorithm that utilizes the current AVL information for the approaching/departing vehicle relative to a stop.

C
The CAD/AVL System shall have functionality to calculate the arrival/departure times for a number of vehicles at each stop for all routes and directions serving that stop.

C
The CAD/AVL System shall provide GTFS‐RT feed to support externalcustomer information and planning applications. C7: ReportingComprehensive reporting shall be provided by the system to display critical reports and information to enable management to monitorperformance and conditions.

C
The solution shall also provide for viewing and reporting of data by exception that is configurable by the users. CThe configurable parameters shall allow for various event triggers such as vehicles running early or late, vehicle off‐route, service type, date, time, route, and vehicle.

C
The system shall allow for flexible reporting (canned, custom and Ad hoc) and mining of data. C
Reporting functionalities and capabilities shall include the following at a minimum, but not limited to: C
• Revenue Vehicle Operations C
• Dashboards that display critical information on a continuous basis C • Current status of service showing active CEA, number of vehiclescurrently on routes, percent of fleet on time, and percent of fleet late C• Dispatch user information such as vehicle and line assignments, action events such as vehicle calls and alarms, and dispatch user responses, all with time tags for analysis
C
• Stop information including line, run, direction, vehicle, operator, miles,etc.

C
• Summary data on trip number, line, run, day of week, time period,Operator ID, vehicle ID, schedule adherence, passenger boarding’s, etc.

Summaries shall be for daily, weeks, months, quarters, and years C
4/20/2023 Compliance Matrix 4

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • Time‐point data including trip vehicle, line, run, and time of time‐point passage
C
• Trip information including line, run, direction, vehicle, operator, miles,etc.

C
• Revenue and non‐revenue miles and hours C
• Schedule adherence C• Bus assignments including changes C• Run cancellations C• Out late buses C• Service delays, including type, reason, length of delay, service loss,mileage lost C• Operator Management C• Operator assignments and assignment fulfillment C • Incident Reports involving Operator error C• Accident Reports C8: Onboard Vehicle System Requirements The Contractor shall furnish and install a CAD/AVL System for MBL vehicles, with all equipment, cabling software, components and licenses necessary.

C
9: Vehicle Logic UnitThe Contractor shall provide a VLU that has, the following specifications at a minimum, but not limited to: C
• The VLU shall be the central processing device and data storage device installed onboard for all vehicles and powered by the vehicle’s electrical system
C
• The VLU shall be integrated with the onboard equipment on each vehicle that provides route/ destination announcements and onboardvisual signs with both audible and textual messages, etc.

C
• The VLU shall provide the interface/transmission of data to and from all subsystems such as audio announcements, PIDS, onboard visual signs, etc.

C
• The GPS receiver shall be integrated into the VLU to provide time andlocation data for AVL functions C• Multiple port selections C• Data storage capacity shall be sufficient to store the complete current and pending route schedules, announcement files, and event messages C 4/20/2023 Compliance Matrix 5

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • System configuration settings related specifically to a vehicle shall bestored in a vehicle configuration module such that the VLU unit can be swapped out and vehicle information not lost.

C
• The VLU shall be provisioned for future expansion and interoperability C10: Mobile Data Terminal (MDT) The Contractor shall provide a MDT that has, the following specifications at a minimum, but not limited to: C• The MDT shall automatically engage when the vehicle is started, and shut down a programmable amount of time after the vehicle is turned off.

C
• The MDT shall store the most recent location received from the GPS receiver, so that if the GPS receiver is not able to report the location, the last known good location will remain available.

C
• The MDT shall incorporate a color graphical screen capable of displaying fonts of variable size and can change colors between day and night or has automatic brightness controls.

C
• The MDT shall have capabilities to show the Operator turn by turndirections. C• The MDT shall have the capabilities to show the Operator if they areahead of schedule or behind schedule in number of minutes and or color code.

C
• The MDT shall be equipped with appropriate functional buttons (physical and or touch screen) capable of controlling other onboard systems (e.g. NGFS, head signs, etc.).

C
• The MDT display shall be readable by the Operator from the seated position under the full range of ambient illumination conditions, through the incorporation of such measures as driver‐operated
brightness/contrast control, anti‐glare coating and adjustable orientation mounting.

C
• The MDT shall be capable of providing unique audio tones to alert the Operator of incoming messages. CThe MDT shall be capable of, but not limited to, displaying the following onboard information and interface to onboard systems during operation of the vehicle:

C
• Data Messaging C• Emergency Alarm C
4/20/2023 Compliance Matrix 6

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • Head Sign Control C• Logon C• Maintenance C• NGFS‐ Mobile Validator (Ability to show fare on MDT, accept and cancel transaction from MDT etc.)
CM
Avail can provide an in‐Vehicle API that the NFGS Mobilevalidator can comsume as long as it connected to the internal bus network. Avail can provide trip information + fareset to the validators and can work with the NFGS vendor to ensure they have the specs to consume the data. All data would be on the Validator, not the MDT
• Route Guidance C• Schedule Adherence C• Stop Announcement C • Talk C• Transfer Notification C• Trip/Schedule Display Control C• The MDT shall support en route changes of the assigned Operators for cases such as mechanical breakdowns, Operator substitutions, etc. C • The MDT shall enable Operators to send user‐friendly, easy to use predefined text data messages to dispatch with a minimum of interactione.g. wheel chair loaded, bike loaded etc. These text messages shall be user configurable by system administrator and flexible in the way theyare ordered on the MDT.

C
• Operators shall be able to review recently received messages at anytime with a minimum of interaction. The MDT shall be capable of retaining at least the last (10) ten received messages for Operator review. The received messages shall be ordered chronologically with the most recently received message presented first.

C
• When the vehicle receives a data message, the Operator shall benotified by a mutable audio tone signal and the message shall beavailable for display on the MDT within one second after it is received. C 4/20/2023 Compliance Matrix 7

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • The MDT shall provide for automatic control of all destination signs in vehicles. The destination signs shall be automatically updated by the Operator at logon and at predefined points along each route (e.g., at the end of a trip). The points at which destination sign messages shall beautomatically changed shall be configurable by MBL.

C
11: Covert Emergency AlarmThe Contractor shall provide a Covert Emergency Alarm (CEA) which willactivate a silent alarm when an Operator presses a button in an inconspicuous location of the Operator‘s area.

C
When engaged, the CEA shall include the following functionality, butnot limited to: C • Issue an emergency alarm, including vehicle location, to the dispatch workstation C• Discreetly display the CEA activation to the Operator C• Send discrete visual signal to Operator when a dispatch workstationacknowledges receipt of CEA C• Emergency Alarms shall have the highest priority of all data messages. C • Cause exterior head signs to display an emergency message C • A CEA event indication shall not be noticeable to passengers. C • Update the vehicle location to the dispatch workstation no less thanevery (5) five seconds C• Allow supervisor to override and disable a CEA using the dispatch workstation C12: Automatic Voice Annunciators
The Contractor shall provide an Automatic Voice Annunciator (AVA) system in each MBL vehicle that shall automatically audibly and visually announce stops and stop requests; and change onboard visual signs. C The AVA system shall determine where or when to make stop announcements and onboard visual signs changes using AVL system data and pre‐defined location or time parameters.

C
Once the Operator is logged into the MDT, the AVA system shall be fullyautomatic requiring no driver interaction. C The AVA system shall include interior and exterior speakers and all relevant equipment for audible announcements. C
4/20/2023 Compliance Matrix 8

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines 13: Destination Announcements
When a vehicle is approaching a stop, one or more announcements shall be made for approaching stop. CRequirements, capabilities, and features of the announcement system shall include but not limited to: C
• Allow MBL administrators to configure announcements C• Destination description by street, intersection, location, or landmark C• Disabling of exterior audio announcement by time of day, route and vehicle C
• Distance or time of announcement(s) prior to the stop C• Multiple occurrences of announcement for a given stop, including uponarrival C• Type of announcement (visual, interior audio, and/or exterior audio) bybus or trolley location C• Allow Operator to disable AVA system in the event of malfunction CM AVA disability is a system setting • Allow Operator to manually invoke the pre‐defined announcements C• Automatically make other pre‐defined announcements periodically orat pre‐defined locations C• Display time periodically or at pre‐defined locations C • If an unscheduled stop is made, continue to make correct next stopannouncements C
• If vehicle goes off‐route, disable announcements until vehicle returns to the assigned route C• Include pre‐defined announcements C• Make audio and visual “Stop Requested” announcements and clear when a door is opened C• Make line and destination location announcements prior to and upon arriving at bus stops C• Meet Americans with Disabilities Act (ADA) requirements for the busstop announcements C
14: Announcement DatabaseThe AVA system shall include a database of audio and visual stop and other pre‐defined announcements. C
4/20/2023 Compliance Matrix 9

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines The database shall include necessary administrative tools for MBL to easily modify announcement parameters for individual stops including but not limited to announcement content, location, frequency, and type. C 15: On‐Board Passenger Display Signs
The Proposer shall provide and install inside each vehicle: C • At least one electronic variable display sign for visual bus stop and other pre‐defined announcements C• Conceal cable connections to the sign enclosure C• House visual signs in a vandal‐resistant enclosure with a scratch resistant faceplate lens C
• Use text of sufficient size, brightness, contrast, and clarity to bereadable by persons with normal vision from anywhere in the vehicle under typical day and night ambient lighting conditions C
16: Yard Managemet System (YMS)The Yard Management System shall maintain a MBL yard plan showingthe current vehicle locations, IDs, availability status, and assignments by operator and run; and provide for vehicle status updates by the Maintenance Department.

C
The yard plan and vehicle status shall be available to the Dispatch Center console and to selected pre‐existing Maintenance Department workstations.

C
Other requirements, capabilities, or features of the Yard ManagementSystem shall include but not limited to: C• Display MBL yard plan in graphical format matching the actual layout of the yard. C• Automatically record movements of a vehicle in, out of, and within the yard. C
Provide vehicle status such as: C
• Holding vehicles for maintenance C
• Vehicle being cleaned and disinfected C
• Vehicle disinfected and ready for revenue service etc. C17: Acess to Data and InterfaceThe vendor is expected to partner with MBL and other authorized vendor products to interface and share data via import/export of files or API, when applicable.

C
4/20/2023 Compliance Matrix 10

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines Similar to the GTFS data standard, MBL follows other national efforts to standardize key data sources and allow for easy integration betweentechnology companies.

C
18: NDT Reporting• Ridership reporting solution shall provide NTD reporting for ridership and passenger miles C
• The Contractor shall assist MBL in obtaining NTD certification for ridership and passenger miles and describe the NTD process in proposal C 19: Voice Over IP (VoIP)• The vehicle operator shall be able to select on the OCU a voice call through a request to talk (RTT) and a priority request to talk (PRTT),which will immediately send the request to the central system C
• The OCU or VCU shall retry sending the message until acknowledged by the central system or until all retries have been exhausted. The vehicleoperator will be notified that the request was successfully transmitted or not
C
• The proposed voice solution shall include either voice over IP (VoIP) as embedded feature of the OCU or VCU C
• The vehicle operator shall not have use of the voice radio unlessrequested by a Dispatcher through a voice call or the OCU or VCU loses data communications to the central system and the radio is in fallback C • The vehicle operator shall have free use of the voice system when in fallback mode. The voice system shall be in fallback mode when the OCU or VCU is powered off, when the OCU or VCU is powered on but not fully operational, when the OCU or VCU has lost data communications to the central system, or when the OCU or VCU is commanded to enter fallback mode by Dispatch
CM
• The vehicle operator shall have free use of the voicesystem when in fallback mode. The voice system shall be in fallback mode when the OCU or VCU is powered off, whenthe OCU or VCU is powered on but not fully operational, when the OCU or VCU has lost data communications to thecentral system, or when the OCU or VCU is commanded to enter fallback mode by Dispatch
• If voice audio from Dispatch is playing on the driver speaker and the vehicle operator picks up the handset, the Dispatch audio will be automatically routed to the handset
C
• The voice call will automatically end when the vehicle operator places the handset in the cradle, the configured call timeout period elapses or when no voice is detected for a configurable period
C
4/20/2023 Compliance Matrix 11

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • It is paramount that the bus operator can always get in touch with dispatch and therefore the voice communications solution shall support fallback. When data communications between the VCU and the central system are lost, for any reason, the VCU shall go to open microphonemode, which allows the bus operator to pick‐up the handset and talk without sending any text messages
C
• The system shall support monitoring the audio onboard the bus. When in emergency mode, the VCU shall allow the covert microphone to beenabled by the dispatcher. When enabled, the covert microphone audioshall be routed through the radio or VoIP to the dispatcher that enabledthe covert microphone C
20: Dispatch‐Initated Public Annoncements• The VCU shall immediately playback any public audio announcementson the interior speakers using text to speech (TTS) that were sent by a Dispatcher
C
• The VCU shall immediately display any public text announcement sent on the interior LED sign by a Dispatcher C
21: Traffic Signal Priority (TSP) Integration
• The proposed system must be expandable to integrate with future Traffic Signal Priority (TSP). C
• Contractors shall provide the name and references of TSP systems in which integrations have been successfully completed C
22: Planning and Scheduling (Optional)
• Be able to provide U.S. Census data on the service area, including but not limited to ethnic and socioeconomic data. C• Ability to pull demographic data using the radius from the routealignment (i.e. .25 miles from a fixed transit route) C • Generate maps with census data overlays, and the ability to export saidmaps as a .jpeg or .pdf file. C• Run a Title VI analysis within the set service area, including the ability to determine average minority percentage by line and system‐wide C • Ability to generate map that can distinguish census block groups as above or below average system‐wide minority C• Ability to run Title VI Service Equity Analysis for service or routemodifications C 4/20/2023 Compliance Matrix 12

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • Provide modeling capabilities to simulate new routes or route modifications C• Present easy‐to‐read route statistics C23: Pre Trip Inspection (Optional)Pre‐trip inspection reporting prior to pull‐out to eliminate manualprocessing of paper‐based inspection. CShall be fully customizable to include: C Fully customizable inspection forms C• Allow operator keyed input to address specific issues and comments C• Force mandatory post‐trip inspection and end of day for vehicle C We do not force mandatory post‐trip inspection • Capable of sending inspection reports to designated staff in real‐time C • Configurable inspection duration validity (i.e. 24 hours, 48 hours, etc.) C • Alerts/notifies staff when vehicle leaves the garage without a valid status
C
24: Automatical Vehicle Monitoring (AVM) (Optional)
• The VCU shall include an automatic vehicle monitoring (AVM) system that monitors onboard equipment through the standard interfaces forperformance data and faults C
• During the design phase of the project, the Contractor shall describethe need for installing any hardware or software upgrades required for this interface
C
• The VCU shall indicate to the vehicle operator via the OCU anyequipment that has faults C• The VCU shall immediately report any equipment faults identified by MBL to the central system C
• The VCU shall timestamp and geocode all data collected by AVM C • The system shall be capable of verifying active communication betweenall monitored systems and the VCU, and be capable of using multiple communication protocols
C
• The VCU shall transmit all AVM collected data to the central system through the WLAN upon entry to the WLAN coverage at the depot andevery fifteen minutes while in WLAN coverage.

C
4/20/2023 Compliance Matrix 13

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines • The VCU shall be capable of monitoring the performance data that istypically available on the bus networks ‐ The Contractor will validate the availability of AVM fault and performance data
C
The Contractor will work with MBL to document the final list of performance and fault data to be collected during the design phase C 25: WarrantyAll equipment and workmanship (on board equipment, backend equipment, software, and other accompanying equipment) should havea minimum of 3 years warranty from the date of final acceptance of work.

C
• Proposals will provide an explanation of the coverage provided by the warranty, including the response method and plan for provision of parts and labor.

C
• The Contractor warrants the documentation provided completely and that it accurately reflects the operation and maintenance of the equipment and software, and provides all information necessary tomaintain the system.

C
26: MaintenanceProposals must include pricing for maintenance and provide an explanation of the coverage, including response times and plans for provision of parts and labor. Proposals must address maintenance provisions for software patches and version upgrades.

C
The Proposer is required to notify MBL at least one month in advance of installation when new software releases become available. C The Proposer is required to notify MBL at least six months in advance when it is expected that the current release and related systems will no longer be supported.

C
The Proposer will ensure that all existing software configurations are protected after the system has been upgraded for the entire duration ofthe time when MBL uses the product.

C
These changes must be reported to the MBL Director. C27: Techincal Support and TrainingThe Proposer will provide a contact person and phone number to assist MBL with any technical questions. CThe Proposer will submit a training plan that describes the procedures that will be employed to adequately accomplish training related to the implementation and full utilization of the system.

C
4/20/2023 Compliance Matrix 14

Confidential and Proprietary RFP No. 23‐8 CAD/AVL System Montebello Bus Lines Training shall be provided to personnel designated by MBL. C Training for all hardware and software must be provided on‐site and will at minimum include: C
• Name and phone number of the person responsible for training. C• How to install or setup a computer as a viewing station. C• How to operate the software C• How to record and retrieve data. C 4/20/2023 Compliance Matrix 15

Proposal in Response to RFP issued by: City of Montebello RFP No. 23-8 Computer-Aided Dispatch/Automatic Vehicle Location System 3-4

3.Ubisense Proposal

This document contains confidential and proprietary information and is the property of Ubisense America LLC Except for internal use, reproduction without prior written permission from Ubisense America LLC is prohibited. © 2023 Ubisense America LLC.

Avail Technologies for the Montebello Bus Lines RFP
Response to RFP 23-8 – Yard Management System
Solution
4/14/2023
Version 1.0
Ubisense Order No. SO-50043350
Presented to:

Presented by
Ubisense America LLC
1630 Welton Street
Suite 1000E
Denver CO 80202
Sales Contact: Casey Riva – Technical Account Manager
Phone: +1.530.412.3886
Email: [email protected]
www.ubisense.com

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 1
Created for Avail Technologies
4/14/2023
1 Version History
Ver 1 20230413 Initial Proposal
Ver2 20230414 Removed SaaS and updated term length for Software Subscription.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 2
Created for Avail Technologies
4/14/2023
2 Letter of Introduction
Ubisense is an end-to-end provider of location intelligence solutions across large scale, multi-site, public transit, manufacturing, and logistics industries. Recognized by Gartner as a leader in the “Location intelligence” space, Ubisense provides solutions to address three broad areas of value for users:

1. The ability to quickly locate assets, eliminating wasted search time

2. The ability to accurately monitor the movement and control flow of assets throughout the facility.

3. The ability to identify process issues before, or as they occur, providing real time information to rebalance operations and stay on schedule.

Real time location solutions provide users with on demand information to quickly answer the question - Where are my assets? While this information is valuable to solve the immediate need for the user, it does not encompass the entire challenge for the business. Rather, people wish to find things because they are required for a particular purpose, at a particular place, at a particular time, or directed to a particular spot ahead of time.

Ubisense specializes in systems that tackle this problem, as stated in the points above. not simply finding assets but ensuring that they are guided correctly and quickly flow through the desired process.

Examples in Transit Management include:
• Where is the best position to park this bus to prepare for the pull-out or maintenance? • Which bus of type X is available to pull out now without being blocked? • How should bus route assignments be reallocated because of an unplanned maintenance issue? • When can this bus be repaired based on the availability of the appropriate maintenance bay? • Which is the most ideal next bus to send to the terminal bus stop to maintain the correct schedule conflict?
In order to perform these functions, the solution must include:
• A reliable, precise location sensing system which can determine bus location to an accuracy of one parking space, maintenance bay or bus stop.
• A software platform capable of integrating with other data sources and merging those with location context.
• A business logic engine capable of implementing complex rules. • A system interface to pass business data to other systems. • A user interface to allow manual monitoring and intervention.

Ubisense specializes in Real-Time location enabled Yard Management applications which can be quickly tailored to model the current dispatch, maintenance, and return to service processes in place at each garage. The SmartSpace platform provides a solution which reflects your current daily process, can be easily adapted to future changes, and does not require your business to conform to a standard set of functionalities with no development. As the fleet mix continues to evolve, SmartSpace can be easily adapted to support new bus models and process requirements for hybrid and EV vehicles.

Contact information for all key project representation can be found in Appendix Solution Representative Contract Signatory
Casey Riva Scott Mullarkey
[email protected] [email protected]
530.412.3886 902.524.7743

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 3
Created for Avail Technologies
4/14/2023
Table of Contents
1 Version History ................................................................................................................................................................... 1 2 Letter of Introduction......................................................................................................................................................... 2 Table of Contents ...................................................................................................................................................................... 3 3 Executive Summary ............................................................................................................................................................ 5 4 Company Introduction ....................................................................................................................................................... 6

4.1 Investors and Management..................................................................................................................................... 7

4.2 Gartner Achievements............................................................................................................................................. 8 5 Ubisense Team................................................................................................................................................................. 10

5.1 Project Team.......................................................................................................................................................... 10 6 Product Introductions – Dimension 4 Ultra-Wide Band (UWB) ....................................................................................... 12

6.1 Location Accuracy and Reliability .......................................................................................................................... 13

6.2 Hardware Architecture .......................................................................................................................................... 15

6.3 Deployment Architecture ...................................................................................................................................... 15

6.4 D4 Sensor Options................................................................................................................................................ 17

6.5 D4 Timing Distribution Unit................................................................................................................................... 17

6.6 Dimension4 Tags.................................................................................................................................................... 18

6.7 Advanced System Planning and Calibration Tools................................................................................................. 18 7 Product Introductions – SmartSpace................................................................................................................................ 20

7.1 Application Configuration Methodology ............................................................................................................... 22

7.2 Platform Components ........................................................................................................................................... 22

7.3 Standard On-premise Architecture ....................................................................................................................... 37

7.4 Cloud Architecture................................................................................................................................................. 38 8 Transit Management Solution Overview.......................................................................................................................... 39

8.1 SmartSpace Software ............................................................................................................................................ 41

8.2 Ubisense Dimension4 UWB and RTK GPS Transit Tag ........................................................................................... 45

8.3 System Architecture .............................................................................................................................................. 47

8.4 Integration Overview............................................................................................................................................. 48

8.5 Coverage Areas...................................................................................................................................................... 49 9 MBL Transit Management Solution Requirements.......................................................................................................... 50 10 Pricing Models and Application License ........................................................................................................................... 51

10.1 Software as a Service............................................................................................................................................. 51

10.2 Payment Milestones.............................................................................................................................................. 52 11 The Understanding of Work and Project Approach ......................................................................................................... 53

11.1 Project Delivery Methodology............................................................................................................................... 53

11.2 Detailed Design Phase ........................................................................................................................................... 53

11.3 Implementation And Testing ................................................................................................................................. 54

11.4 Integration Testing Phase ...................................................................................................................................... 55

11.5 Training, Introduction and Stabilization Phase...................................................................................................... 55

11.6 Project Management............................................................................................................................................. 56

11.7 System Verification and Testing Process............................................................................................................... 56 12 Operational Support & Incident Management ................................................................................................................ 59 13 Assumptions and Terms................................................................................................................................................... 64

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 4
Created for Avail Technologies
4/14/2023

13.1 Terms..................................................................................................................................................................... 64

13.2 Assumptions.......................................................................................................................................................... 64 14 Customer References....................................................................................................................................................... 65

14.1 Metro Transit, Minneapolis, MN United States..................................................................................................... 65

14.2 RTL Transit. ............................................................................................................................................................ 68

14.3 Brampton Transit................................................................................................................................................... 68

14.4 TPF, Switzerland .................................................................................................................................................... 68 15 Appendix .......................................................................................................................................................................... 70

15.1 Key Contact Information........................................................................................................................................ 70

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 5
Created for Avail Technologies
4/14/2023
3 Executive Summary
Ubisense has been deploying location enabled solutions in large scale, operation critical environments for more than twenty years, focusing solely on location solutions across numerous industries. Ubisense is recognized by Gartner as a Leader in the location industry and Ubisense has been voted as the Customer Choice among similar providers.

Ubisense SmartSpace solutions are used amongst transit agencies globally, providing a real-time digital markup of each garage, automated vehicle routing based on priorities, real-time notifications of process issues, and capture of historical performance metrics.

Ubisense SmartSpace Transit Management and Dimension4 (hardware) will provide Montebello Bus Lines(MBL) with quality location performance and out of the box software functionality while maintaining continuity in the user experience and sustainment process. With the Ubisense Dimension4 UWB/RTK-GPS tag, centimeter level precision both indoors and outdoors can be achieved, providing a reliable real-time digital markup that users can trust that is always up-to-date and correct.

Ubisense SmartSpace platform is configured to provide a browser accessible digital representation of the garages/yards with Real-time interoperability with other systems. Ubisense Dimension4 hardware attached to the MBL fleet can be detected at any location where Ubisense sensing infrastructure is installed and directly displayed and tracked on the SmartSpace Yard Management application.

Ubisense follows a proven and efficient deployment approach comprising of the following key phases:
• Detailed Application and System Design
• System Commissioning
• Through Location System and Application Testing
• System Go-Live Support
Our services team has extensive experience deploying complex solutions ensuring the projects stay on schedule and within budget. A detailed explanation of the delivery methodology can be found in the Section 11.1 Ubisense uses industry-standard tools to manage the project, provide support, and produce application training documentation. Ubisense provides detailed solution documentation, including the as designed solution, as built solution, detailed charge request documents which a transparent understanding of any modification to the software functionality or tracking deliverables.

Ubisense utilizes commercially available products such as SharePoint for secure document management, Confluence and Jira for project documentation and support and complies with the ISO27001 Standard for information security.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 6
Created for Avail Technologies
4/14/2023
4 Company Introduction
Ubisense has been deploying location and identification enabled solutions in large scale, operation critical environments for 20 years, focusing solely on location solutions across numerous industries. Ubisense is recognized by Gartner as a Leader in the location industry and Ubisense has been voted as the Customer Choice among similar providers.

We do this with industry-leading sensors and an open
software platform that business users can easily
configure for planning, monitoring, and controlling
physical process flows.

Headquartered in Cambridge UK, Ubisense operates
globally, with more than 1000 customers, transforming
their physical space into SmartSpace. We support
customers directly through offices and teams in North
America, Germany, France, Japan, and United Kingdom,
and indirectly through large industry partners that span all the major economic territories globally.

Our customers span many industries including manufacturing, MRO, logistics, public transportation, pharmaceuticals, and defense, but they all have common challenges – large numbers of assets distributed throughout either a plant or geographic operating area that they wish to locate and manage more efficiently. We deliver solutions to help them meet this challenge.

Figure 2 - Customer Distribution
Our pedigree in manufacturing has enabled us to prove out our products in some of the harshest industrial environments. Ubisense is now deployed at a large scale in nine of the top ten automotive manufacturers (by volume), with more than 5% of the world’s passenger vehicle production relying on mission-critical solutions from Ubisense for daily execution. Our manufacturing solutions are also deployed in six of the top ten Fortune 500 manufacturers and by three of the top five aerospace manufacturers.

Figure 1 - Ubisense Office Locations

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 7
Created for Avail Technologies
4/14/2023
Our clients are world leaders in their industries, including Automotive (Daimler Mercedes Benz, BMW, Mini, GM, Toyota, Honda, Aston Martin), Commercial Vehicles (John Deere, Claas, Mitsubishi Trucks, Freightliner, Paccar) and Aerospace (Airbus, Safran, Lockheed Martin).

4.1 Investors and Management
Ubisense is owned by Investcorp Technology Partners, a division of Investcorp who have a focus investing in growing software companies selling B2B products that solve mission critical problems.

The Ubisense executive team includes multiple veterans of the indoor location and ultra-wideband (UWB) technology space, including principal drivers of the current worldwide standards for UWB location, and pioneers in creating and delivering the world’s first truly enterprise-scale deployments of UWB into complex industrial environments.

Figure 4 - Ubisense Leadership
Ubisense remains a founder-led business, with all four founders (from 2002) still driving the strategy and direction of our business and products, leading, and defining the next technological wave in indoor location services for industry. Ubisense is currently operating on our third generation UWB location platform and our fourth-generation software platform.

Figure 3 - Investcorp

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 8
Created for Avail Technologies
4/14/2023
Figure 5 - Company Milestones and Technology Advancement

4.2 Gartner Achievements
Gartner’s Magic Quadrant is widely recognized as the world’s most influential market analysis for IT buyers.

Ubisense was ranked as a leader and features in the upper tier of vendor scores for all use cases in the Critical Capabilities for indoor Location Services in the Global 2022 report. “Ubisense’s SmartSpace platform delivers centimeter-level accuracy using UWB with sub-second beacons as well as hybrid tags combining UWB and BLE” – Gartner, 2022
Figure 6 - Gartner Magic Quadrant 2022

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 9
Created for Avail Technologies
4/14/2023
Ubisense was also recognized in the Garner Peer Insights as the Customers’ Choice in 2021 which distinctly recognizes vendors and products that are highly rated by their customers.

Figure 7 - Gartner Customer Choice

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 10
Created for Avail Technologies
4/14/2023
5 Ubisense Team

5.1 Project Team
Ubisense has a professional sales, delivery, and support team which can deliver our solutions globally. The Americas team is led by the following key members:

Figure 8 - Ubisense Project Team

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 11
Created for Avail Technologies
4/14/2023
Figure 9 - Ubisense Organization Chart
Ubisense employs a diverse and highly qualified team of Pre-Sales Consultants, Project Managers and Technical Delivery Engineers.

Pre-Sales Consultants assist with the technical aspects during the proposal stage and work in lock-steo with the account managers to compose the porposed solution.

At the time of award, the Manager for the Technical Deployment team, assigns a Project Manager to lead the project and the engineers for the deployment of the solution based on the current workloads and expertise required for the succesful delivery of the solution per the high quality standards held by Ubisense.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 12
Created for Avail Technologies
4/14/2023
6 Product Introductions – Dimension 4 Ultra-Wide Band (UWB) Figure 10 - Ubisense Products
Ubisense Dimension4 (D4) is a best-in-class precision real-time location system. It consists of hardware, firmware and server-based software components that together have helped D4 become the most widely-deployed, highaccuracy and production-proven location system in the world. Dimension4 is differentiated from other UWB location systems through unique capabilities built deeply into both the hardware and software layers of the system.

Figure 11 - Ubisense D4 RTLS Data
• Enterprise Scalability, implementing fog processing techniques for enterprise scalability and controlsready real-time performance. • Industrial Strength, with system deployment and IT management tools for mission-critical reliability. • Highest Reliability, being the only system to measure both angle and time-of-arrival from tags for location precision and robustness.
• Lowest TCO, with the best available battery lifetimes in the industry, with batteries lasting as long as 15 years.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 13
Created for Avail Technologies
4/14/2023

6.1 Location Accuracy and Reliability
Location Accuracy and Reliability
Dimension4 is based on Ubisense’s formulation of Ultra-Wideband (UWB) technology which couples standard Time Difference of Arrival (TDOA) with unique Angle of Arrival (AOA) measurement. The addition of AOA triples the amount of useful location information gathered by each sensor. This additional information is what makes Dimension4 the most precise and robust tracking system in hostile environments which are highly metallic and highly dynamic.

Figure 12 - Location Accuracy Technology Comparison
In dynamic, metallic environments any single piece of measured data may be corrupted either by signal blockage or reflections off surfaces. The result of such data corruption is always to reduce the accuracy and reliability of location measurements. For an equivalent density of sensing infrastructure, Dimension4 is uniquely accurate and robust since, with 3x the data of other systems, it can detect and discard corrupted data and still have enough data remaining to precisely determine location.

In order to facilitate TDOA measurement, many systems require either cabling, or reference tags or both in order to synchronize the sensors with sufficient accuracy. In addition to providing extra reliability, AoA measurement allows Dimension4 to run with wireless infrastructure, free from reference tags. This capability not only reduces the overall cost of system ownership, but also allows Dimension4 to be deployed in situations where cabling is either prohibited or not practically feasible. Even in AoA-only wireless mode, Dimension4 has double the information available to other location systems.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 14
Created for Avail Technologies
4/14/2023
Figure 13 - UWB AoA and TDoA
In dynamic, metallic environments any single piece of measured data may be corrupted either by signal blockage or reflections off surfaces. The result of such data corruption is always to reduce the accuracy and reliability of location measurements. For an equivalent density of sensing infrastructure, Dimension4 is uniquely accurate and robust since, with three times the data of other systems, it can detect and discard corrupted data and still have enough data remaining to precisely determine location.

Ubisense technology allows for implementing real-time tracking applications with both high accuracy and high reliability. The following chart shows which typical accuracy and confidence level are achieved in an average Ubisense UWB deployment (orange column).

Figure 14 - Ubisense Location Confidence
However, there is a direct relationship between the achievable accuracy with a given confidence level and the number of infrastructure (sensors) to be deployed. Therefore, it is important that the business use case to be implemented determines the level of accuracy to be achieved.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 15
Created for Avail Technologies
4/14/2023

6.2 Hardware Architecture
Dimension4 sensors are wired into the existing network with Cat5e cables and a timing-distribution unit, which allows each individual cable to carry a combination of power (PoE), data and precise time synchronisation to each sensor.

This allows sensors to generate the maximum number of tag measurements by harnessing both angle (AoA) and time (TDoA) information, giving highest-possible 3D precision and redundancy in highly cluttered and complex manufacturing environments such as assembly lines.

Figure 15 - Hardware Architecture

6.3 Deployment Architecture
Ubisense SmartSpace and Dimension4 products are built using the same architecture that has been in use in large-scale installations for over a decade. As a result, the underlying protocols and techniques have been proven in many different environments on various computing platforms.

SmartSpace and Dimension4 utilize a client-server model, deployed as a collection of microservices using standard protocols (TCP/IP, UDP). The microservices approach enables several important features of SmartSpace and Dimension4, including:
• Ease of deployment across Cloud, On-premise or Hybrid deployments • Highly-distributed systems with predictable real-time performance • Modularity and flexible licensing through feature and capability bundling

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 16
Created for Avail Technologies
4/14/2023
Figure 16 - Example Cloud Architecture
Figure 17 - Example On-Premise Architecture

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 17
Created for Avail Technologies
4/14/2023

6.4 D4 Sensor Options
Dimension4 sensors are first class Ethernet connected devices that can be deployed both indoors and outdoors using the appropriate ingress protection. Ubisense sensors come in three IP variants and are engineered to operate in harsh industrial environments.
• IP30 – intended for normal indoor operation with minimal dust and risk of water. • IP54 – intended for industrial environments where there is a higher risk of dust and water. This back cover protects the sensor ports and cabling connections from accumulating dust and water splashes. • IP69K – intended for extreme outdoor operation in hard industrial conditions. This back cover protects from dust and water, extreme heat and cold, and is fully pressure tested against water ingress.

Figure 18 - D4 Sensor Ingress Ratings

6.5 D4 Timing Distribution Unit
The Dimension4 Timing Distribution Unit (TDU) is a 2U rack mountable POE device that provides precision timing synchronization support for up to 21 sensors in a Ubisense sensor network. It reduces the number of long cable runs required for a sensor installation by combining the network and timing signals onto a single cable. TDUs can be chained together to support larger sensor systems.

Figure 19 - Timing Distribution Unit

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 18
Created for Avail Technologies
4/14/2023

6.6 Dimension4 Tags
Dimension4 tags are available in various form factors and ingress protection ratings, covering a broad spectrum of use-cases from real-time control of devices to wide-area asset management. The following datasheet excerpt provides details on sizing, typical applications, and battery lifetimes. Ubisense Dimension4 tags have a typical battery lifetime anywhere from 5x to 10x longer than comparable systems on the market today.

Figure 20 - Ubisense Tag Family

6.7 Advanced System Planning and Calibration Tools
Ubisense utilizes state of the art tools and technologies to design and quickly deploy large sensor systems.

Sensor planing tools
Ubisense utilizes state of the art sensor planning tools to ensure reliable tracking performance is met everywhere within the designated tracking areas. Ubisense sensor planning tools provide a coverage heat map and simulated tracking performance to ensure there are no gaps in coverage ahead of the sensor installation.

Figure 21 - 3D Sensor Planning Tools and Location Quality Simulation

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 19
Created for Avail Technologies
4/14/2023
Lidar Calibration and Testing Process
Once the system is installed, the commissioning and testing can be performed with little to no impact to operations.

Ubisense calibration tools make use of handheld lidar scanners to capture the environment, automatically identify the sensor locations within the facility, and calibrate each sensor in the system.

These tools allow for systems to be deployed, calibrated, and tested in high traffic 24/7 operation environments.

Figure 22 - Environment Point Cloud Capture
These same tools are also used to evaluate the actual performance of the system post calibration, identify any areas of weaker tracking and provide empirical data on system performance for acceptance testing.

Figure 23 - Scanning, Calibration, Validation Process

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 20
Created for Avail Technologies
4/14/2023
7 Product Introductions – SmartSpace
Ubisense SmartSpace is a modular software configuration platform that manages real time location and identification data from multiple sources to support industrial scale mission critical visibility and control.

SmartSpace makes it easy to build, deploy and manage software applications that can detect and respond to realworld physical interactions between people, things, and the environment. The modularity of SmartSpace means that users can license only the functionality they will need for their specific location aware applications.

Scalability and real-time performance lie at the core of the SmartSpace architecture, allowing users to build applications that scale from micro-installations (small control systems running on a single machine) through to large sites with several servers and thousands of sensors, devices, people, etc., all with predictable performance.

Figure 24 - Ubisense Digital Twin
Scalability and real-time performance lie at the core of the SmartSpace architecture, allowing users to build applications that scale from micro-installations (small control systems running on a single machine) through to large sites with several servers and thousands of sensors, devices, people etc., all with predictable performance.

To facilitate building sensor-rich, industrial-scale implementations, SmartSpace is fully sensor-independent, meaning it can take in and handle location and identification events from almost any data source, including thirdparty sensors (e.g. RTLS, BLE), third-party RFID readers (e.g. passive RFID, barcode) or other software systems (such as RDBMS, ERP or WMS).

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 21
Created for Avail Technologies
4/14/2023
Figure 25 - Integrated Location Systems
For any given SmartSpace deployment, Ubisense assembles, configures and licenses only those components required to meet the customer’s needs, avoiding any cost or functionality bloat from unwanted functionality.

SmartSpace is easily upgradable to add further functional components as future needs change.

Figure 26 - Ubisense SmartSpace Platform
SmartSpace makes it easy to build applications on top of many variable and heterogeneous data sources using only configuration (rather than having to write application programs). It includes a full set of integrations to common systems which must be involved in location-aware applications (e.g., third-party databases, ERPs, MESs), visibility components like sophisticated browser-based maps, dashboards and reporting components like graphs for analytics.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 22
Created for Avail Technologies
4/14/2023

7.1 Application Configuration Methodology
Creating applications in SmartSpace follows a standard workflow through the functional components of the system, allowing everything from very simple, to very complex location-driven applications, that look, behave and integrate in their own unique ways, to be built.

Figure 27 - SmartSpace Configuration Workflow

7.2 Platform Components
SmartSpace Core and Digital Twin Visualisation
Data Modeling
SmartSpace provides a no-code interface to flexibly create the types necessary to define a new application datamodel. User-defined types are created with appropriate properties, which can be any of the basic numeric or string types as well as user-defined types already defined in the data model.

Figure 28 - SmartSpace Data Modeling

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 23
Created for Avail Technologies
4/14/2023
Types which represent real-world objects can include one or more Space Properties, which are the geometric extents (zones) defined around the object that move and interact with the spaces of other object types in the data model when objects are given a location. Multiple inheritance is fully supported, so that new types can be created from a combination of parent types which own the properties required.

Spatial monitoring
Spatial monitoring is a generic and scalable way of creating software definitions of the physical relationships that exist between objects in the real world that we want to detect and act on in SmartSpace.

This is one of the most fundamental and powerful features of SmartSpace, as it provides a generic language by which we can turn millions of location and identification updates from a multitude of different sensing technologies into a concrete set of events that have real meaning to real-world business process.

Figure 29 - Software Defined Spatial Extents
SmartSpace provides the capability for a powerful three-dimensional visualisation of any configured digital twin of a customer environment. This visualisation includes all the geometric features of the customer environment, live moving objects with accurate representations and all the spatial properties that have been defined to control process logic and reporting.

Figure 30 - Real Time Spatial Monitoring

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 24
Created for Avail Technologies
4/14/2023
Business Rules Engine
SmartSpace Rules engine developer provides a graphical environment to capture logic and relationships between objects in rules and event handlers that reflect your business processes. These definitions are then used by the Business rules engine.

The Business rules workspace provides an editing environment which aids the creation of rule and event definitions. Definitions are constructed by dragging and dropping properties and keywords into available slots in templates. Visual cues in the interface and real-time error messages support the creation of valid definitions.

Figure 31 - Drag and Drop Rules Configuration Engine
The Business Rules Engine provides for the following kinds of definition:

Rules
Rules are statements of fact used to evaluate when a particular state or condition in a process is established.

Events
Actions defined in an event definition run when a value or a fact about a property changes. Events can be used to create or delete objects, set a property, set or unset representations, or send notifications. More than one action can be included in an event, and further tests and conditions can be specified within the definition.

Timeouts
A timeout is triggered when the time specified by a property (whose type must be time) is reached. Timeouts can be used to create or delete objects, set a property, set or unset representations, or send notifications. More than one action can be included in a timeout, and further tests and conditions can be specified within the definition.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 25
Created for Avail Technologies
4/14/2023
Location Rules Engine
SmartSpace uses Location Rules to control the orientation and position of objects as they move through the production of maintenance environment. In this way, objects shown on the map can reliably snap to bays, or lanes, and move in directions with orientation that is consistent with the real world.

Robust Location
Figure 32 - Raw Data vs Robust Location Parking
Parking Paths
Paths are defined for each lane to provide stabilization for any raw location noise. Location rules provide an additional level of software supported filtering to ensure vehicles are correctly located in the correct lane and sequence.

Figure 33 - Software Defined Parking Paths

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 26
Created for Avail Technologies
4/14/2023
Figure 34 - Dense Vehicle Parking with Parking Support
Location Quality Monitoring
A key strength for SmartSpace is to be able to analyze the accuracy and robustness of the location systems that feed location data into the system. With location quality monitoring, various location quality monitors can be set up across a deployment and each can generate health metrics. For example, location quality monitoring can be used to identify if there any outages in the tracking of the tags, or if there are any large jumps in the location data.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 27
Created for Avail Technologies
4/14/2023
Visibility
Web Map Visibility
Users can easily identify and find any tracked product or asset once it is associated to a tag. Object locations are continuously updated in SmartSpace from the underlying location system and end-users can find objects using the SmartSpace web map.

The web map is a configurable, browser-based interface that displays the current locations of tracked assets. It supports role-specific searches that can be configured to the needs of specific types of end user. Each search can be set up to display context-specific representations for assets, including labels and annotations based on Business object properties.

Figure 35 - Example Web Map
Figure 36 - Example Web Map – Transit

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 28
Created for Avail Technologies
4/14/2023
Human-Machine Interfaces
The HMI (Human Machine Interface) component of SmartSpace allows for fast creation of custom web interfaces and applications (dashboards and many other types of data-driven interfaces) within the Ubisense SmartSpace web site. Queries into both current (real-time) and historical (reporting) data are defined and piped into a variety of visualisation formats including:
• Custom interactive dashboards or work instructions with user-input • Visual components such as progress bars or gauges
• Embedded versions of SmartSpace web maps or SmartSpace web reports Administrators can use a web-based editor to develop and test interfaces, before publishing the finished versions to designated SmartSpace roles. Access to these dashboards can then be granted to specific users/roles as desired.

Figure 37 - HMI Dashboard Examples
Reporting
SmartSpace Reporting has two key components, which support persistent logging and report creation based on any data held within the SmartSpace data model.

The Web reports feature runs queries over any recorded location or property history to generate sophisticated tabular and chart-based reports displayed in the browser. On its own, this feature can deliver pre-built reports, such as those available as part of a vertical application. With the Reports engine developer feature, reports can be created and edited by customers to incorporate new data or extend existing SmartSpace reporting capabilities over time.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 29
Created for Avail Technologies
4/14/2023
Figure 38 - Reporting Charts
Web reports can be accessed from a wide variety of devices, ranging from desktop computers to tablets and phones, and do not require installation. A wide variety of chart types are supported including line, discrete bar, multi-bar, horizontal bar, stacked area, scatter, cumulative line, line and focus, pie, histogram, box plot, Sankey diagram, chord diagram and location history.

A small set of example reports built using SmartSpace are shown in the following images.

Figure 39 - Dwell Time Comparison

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 30
Created for Avail Technologies
4/14/2023
Figure 40 - Mixed Report Dashboard
Figure 41 - Sankey Flow Diagram

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 31
Created for Avail Technologies
4/14/2023
Figure 42 - Vehicle Location History Report

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 32
Created for Avail Technologies
4/14/2023
System Integration
Figure 43 – Ubisense System Integrations
SmartSpace applications are very seldom deployed without integration with existing enterprise and shop floor control systems, primarily because so much of the context that is derived from location is wrapped up in other business systems.

Ubisense regularly integrates SmartSpace with many different systems including ERP (typically SAP), MES (various), quality and warehouse management, PLCs, tool controllers and other automation devices. Integration with any of these systems is dependent on the available interfaces of the source system, but to-date there has not been a system with which we have not been able to integrate our platform.

A few of the major integration paths available are described below, with more information available at www.ubisensesmartspace.com.

RDBMS Map
Use SmartSpace’s RDBMS Map feature to integrate with external relational database management systems to read or write application data. The mapping allows the configuration of the import and export of object properties between the Ubisense platform and external database schemas. Operations can be scheduled or triggered based on changes to object properties. Any ODBC compliant database can be mapped into SmartSpace.

Web Services
Web Service integration is enabled through SmartSpace’s REST API. It is an http-based API allowing the viewing or creation of objects and properties in the SmartSpace object model which:
• Provides an interface to the Ubisense platform without requiring knowledge of or access to Ubisense protocols.
• Allows for easy access to the platform information without needing to write software. This is useful for viewing information in a one time/non-automated fashion or when writing lightweight web scripts.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 33
Created for Avail Technologies
4/14/2023
.NET API
The SmartSpace Application .NET API provides a set of related .NET assemblies which can be referenced in a .NET project to access the Ubisense data model. The API supports creating and removing object instances, setting and reading object properties, including custom business object properties. It also supports callbacks when object properties are inserted, updated or removed.

Additionally, the .NET interface to SmartSpace enables standard .NET libraries to be used for industrial protocol integrations, e.g., OPC UA and MQTT.

RTLS and RFID Integration
Ubisense provides connectors for external location data generated from other systems such as GPS, BLE, or passive RFID.

The External data connector (EDC) is a service for collecting location and/or property data from an external system and injecting it into SmartSpace. It supports a range of protocols for connecting to external customer systems, including HTTP(S) queries (server and client), web sockets (client), and TCP (client) and allows imports in various formats, including XML, JSON, CSV, and single-field, unformatted data.

The LLRP interface enables configurable integration and mapping of identification events from 3rd-party RFID readers that support LLRP to objects and events. The LLRP interface collects tag reports from readers and stores the data (what tags have been seen by what readers) in the assertion store/UDM, allowing a user to write logic based on this data using the business rules engine.

Advanced IT
User and Role Authentication
Ubisense allows for users and their roles to be defined within SmartSpace or imported from external systems via LDAP.

SmartSpace roles control which parts of the web interface can be accessed by a user, and the maps, reports and other screens available to them. It also determines which users should receive notifications, emails and alerts generated through the Business rules engine.

This allows the application experience to be tailored to meet the needs of specific classes of end user.

The SmartSpace configuration client includes a workspace for defining roles and assigning users to them. In addition, SmartSpace provides a browser-based view of the underlying users and roles model, giving system administrators simple access for editing or extending the underlying user and group allocations.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 34
Created for Avail Technologies
4/14/2023
Figure 44 - Ubisense Users and Role Authentication
Service Security
SmartSpace implements a service-oriented architecture where each service is a unit of functionality that works with other services to deliver some larger capability. Service security allows each service to be protected so only authorized users and clients can access the data or execute operations to modify it.

Key features include:
• Protection of system state at the service level for security and data integrity • Three service access levels: Open, Read-only, Closed
• Configurable role-based multi-level security model
• Each (Role, Service, Cell) combination maps to a service access level • Uses AES-128 (Advanced Encryption Standard)
• Client credential entry integrated with Windows authentication Figure 45 - Ubisense Service Security

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 35
Created for Avail Technologies
4/14/2023
SmartSpace Failover Control
SmartSpace Failover automates switching from active to standby machines in case of machine failure, or to enable maintenance or backups, in a manner that protects data integrity by ensuring that active and standby machines never run at the same time.

Failover is based around the ‘two machine’ setup in which pairs of machines are configured so that at any one time only one machine is active whilst the other is on standby. If the active machine stops or fails, the standby machine takes over.

SmartSpace Failover ensures platform availability by automating switchover to an alternative host. It assumes an up-to-date copy of production data is made available by some method, for example by using SmartSpace Replication. Ubisense Failover runs on Linux and Windows platforms.

Figure 46 - Ubisense Failover Control
SmartSpace Replication
Replication provides software support for the configuration of a continuously updated backup of the live dataset.

This is stored on a separate (backup) machine, which also has the Ubisense platform installed, but inactive. In case the production machine fails, the Ubisense platform on the backup machine can be started and take over as the production platform server.

The backup machine can also share the same data as the live machine, for example by using a Storage Area Network (SAN) or Network-Attached Storage (NAS).

The benefits of using Replication are:
• Replication is performed in software, meaning there is no need for specialized high availability storage hardware
• The copy of data on the backup machine can be used as a hot backup • Live machine is immune from latency problems commonly caused by synchronous replication • Good for long-distance off-site replication where latency would be a serious issue

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 36
Created for Avail Technologies
4/14/2023
Figure 47 - Ubisense Replication Model
Health Monitoring
Recording and analyzing system health is often a requirement for enterprise location system deployments.

Ubisense Health Monitoring works by periodically delivering metrics to a central health monitoring service.

Separate services expose these measurements to an external metrics database system such as Prometheus.

Metrics can then be viewed on configurable dashboards in a web browser. Isolation of monitoring from the operation of the SmartSpace platform ensures a minimal impact on system performance.

Figure 48 - Health Monitor Dashboard

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 37
Created for Avail Technologies
4/14/2023

7.3 Standard On-premise Architecture
Ubisense SmartSpace and Dimension4 products are built using the same architecture that has been in use in large-scale installations for over a decade. As a result, the underlying protocols and techniques have been proven in many different environments on various computing platforms.

SmartSpace and Dimension4 utilize a client-server model, deployed as a collection of microservices using standard protocols (TCP/IP, UDP). The microservices approach enables a number of important features of SmartSpace and Dimension4, including:
• Ease of deployment across Cloud, On-premise or Hybrid deployments • Highly distributed systems with predictable real-time performance • Modularity and flexible licensing through feature and capability bundling Figure 49 - On Premise Architecture

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 38
Created for Avail Technologies
4/14/2023

7.4 Cloud Architecture
Ubisense solutions, including its local sensor system, can be provided as fully cloud hosted Solutions. Our cloud support enables:

1. Ubisense software components to be fully cloud hosted

2. Running all Dimension4 hardware at the edge, with no on-premise server dependencies

3. Running as a high-availability service, using the optimal combination of Ubisense and AWS components for seamless failover and mission-critical reliability

4. An entirely open platform to integration with 3rd party cloud services for additional sensor data ingestion or output for machine learning
Figure 50 - Cloud Architecture Example

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 39
Created for Avail Technologies
4/14/2023
8 Transit Management Solution Overview
This chapter defines the solution to be implemented for MBL, which is comprised by this proposal.

It starts with a description of the Ubisense SmartSpace application for transit depots, called “SmartSpace Transit Management Solution” in Chapter 8.1. All screenshots included are examples, which need further detailing and customization for MBL. Chapter 8.2 comprises details about the combined RTK GPS and UWB tag solution to be used at MBL, Chapter 8.3 briefly explains the HW and SW architecture, Chapter 8.4 defines our assumptions about the bespoken interfaces between SmartSpace and Avail systems. The final Chapter 8.5 defines the covered areas for all depots.

The Ubisense SmartSpace software platform is an out of the box configuration tool used tailor application behavior for Transit Management. Complimented by seamless indoor and outdoor, centimeter level tracking, using UWB/RTK GPS from the Dimension4 location system, Ubisense provides reliable real time solutions for asset visibility, process monitoring, and historical performance KPIs.

Ubisense solutions help operations manage the ever-increasing complexity of the yard. Transit authorities must manage a complicated mixed fleet drive, multi-site operations, staffing availability and safety policies. Ubisense provides the tools to help manage this complex manual process by providing a reliable real time digital markup, process monitoring and alerting, and measure key KPIs for continuous improvement.

Figure 51 - Industry Challenges
Ubisense tracks the precise real-time location and movement of vehicles across indoor and outdoor transit yards so you can eliminate wasted search time and automate processes by knowing the locations and status of all of your vehicles, all of the time, with a browser-based map and easy to use search capabilities. Transit Management systems save hours of search time and remove the need to manually log every vehicle’s location and provide operations with accurate bus locations to rebalance routes and operator assignments.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 40
Created for Avail Technologies
4/14/2023
Figure 52 - Smart Yard Solutions
SmartSpace Transit Management brings all pertinent vehicle detail, schedule, battery, and maintenance information to the users’ fingertips. Users will be able to quickly identify which vehicles are available, on hold, or assigned to a route by glancing at the map or selecting a vehicle to view its attributes. Process monitoring uses time-based alerts to determine and notify operations of late pullouts in real time, flag potential scheduling mismatches based on vehicle location and ability to exit the depot and identify buses which have not returned to the garage based on their scheduled pull in time.

Figure 53 - Smart Yard Process Monitor
Ubisense describes the detailed feature sets of the MONTEBELLO BUS LINES configuration in the requirements in Section - MBL Transit Management Solution Requirements
An overview of Ubisense SmartSpace Transit Management can be found on our website at - https://ubisense.com/transit-management/

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 41
Created for Avail Technologies
4/14/2023

8.1 SmartSpace Software
A three-dimensional model of the transit yard is created in software with spaces easily defined to represent entrance, parking, cleaning and maintenance areas. Vehicle locations are recorded in real-time with ‘snap-tospace’ neatly depicting actual vehicle location relative to the environment. Integrations with existing packaged or bespoke transit systems means information is consolidated in one place with easy-to-use maps, and configurable searches, alerts and automations.
3D models are built in software and important spaces easily defined and maintained, such as parking or maintenance bays, dispatch lanes, fuel and wash locations, and fare probe.

Figure 54 - Ubisense Digital Twin
A 2D, browser-based map provides real-time visibility to each vehicle location within the depot. Users can quickly switch between garages for multi-site support.

Figure 55 - Browser Based Web Map

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 42
Created for Avail Technologies
4/14/2023
Ubisense location rules apply snap to space parking support to ensure the map is clear and stable for the users to view. Location rules can identify the orientation of the parked vehicle, accurately reflecting its physical orientation on the map.

Figure 56 - Ubisense Web Map - Vehicle Selection
Specific vehicles which match the search criteria are shown in the summary panel on the left. Selecting a bus from this list will automatically take the user to the vehicle location on the web map. Users can specify any attribute in the system as a search criteria to find a specific subset of vehicles.

Figure 57 - Web Map Search Results

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 43
Created for Avail Technologies
4/14/2023
When users select a vehicle on the map, all pertinent vehicle data is shown in the details window. What is shown in the detail windows can be configured by search and role, showing only the relevant information to users or searches.

Figure 58 - Web Map Selected Vehicle Details Window
Each user role and search configuration is capable of different color schemes to call attention to different vehicle states.

Additional icons can be added to the vehicle to represent different vehicle conditions, such as maintenance repairs, vehicles needing wash, vehicles needing fuel, or EV vehicles with low State of Charge.

In addition to interactive web maps, Ubisense provides simple web forms for data management. These interfaces allow select users to sustain the system by adding new fleet vehicles, managing the home base assignment of fleet vehicles, update vehicle tag association, manage alerting timeouts, etc.

Like the web maps, these forms are browser based and accessible by any connected device with permissions to edit the data.

Figure 59 - Colors and Status Icons

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 44
Created for Avail Technologies
4/14/2023
Figure 60 - Example Web Form Summary Table
Figure 61 - Example Web Form - Data Management
External Systems
Ubisense has partnered with Avail and will interface with the Avail software solution to pull in the necessary vehicle details to support the requirements specified by MBL.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 45
Created for Avail Technologies
4/14/2023

8.2 Ubisense Dimension4 UWB and RTK GPS Transit Tag
Ubisense has selected the following hardware for the MBL installation based on 10+ years in the Transit Yard Management Industry.

The Ubisense UWB/RTK-GPS tag has been selected due to its ability to provide real time sub meter accuracy anywhere at the depot, both indoors and outdoors.

The Ubisense Transit Tag incorporates an RTK-GPS unit for centimeter-level positioning. It receives RTK-GPS satellite signals and local correctional signals from a local RTK-GPS base unit and is capable of positioning within 10cm. When a GPS position is successfully found, it relays the location back to the Ubisense location system using the 2.4GHz radio.

Ubisense tags are installed on the roof of the vehicle near the front. Tags are mounted to the exterior of the vehicle and in a location unobstructed by other equipment on the roof. The tags are fully weatherproof and designed to last 10+ years in constant exposure to harsh outdoor elements.

Figure 63 - Approximate Tag Mounting Location
Figure 62 – Ubisense UWB/RTKGPS Transit Tag

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 46
Created for Avail Technologies
4/14/2023
Outdoor Tracking
Ubisense deploys a local sensor system to receive the signals from the vehicle tags. A local base station is installed at each garage which broadcasts a local correction stream for the tags. When outdoors, the Ubisense tags receive the GPS signal and the correction stream and sends its location back to the Ubisense sensors.

Figure 64 - Ubisense Solution Diagram - RTK GPS
Below is an example of the accuracy produced by the Ubisense Transit tag. Here you can see the vehicle move between each parking space in an outdoor lot and the reflected path within the system. This level of accuracy will ensure that the outdoor positions of the vehicles within the depot are always accurate down to the individual parking spot.

Figure 65 – Ubisense RTK GPS Tracking Accuracy

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 47
Created for Avail Technologies
4/14/2023
Indoor Tracking
Indoors, UWB sensors will be deployed in the maintenance bays, wash bays, and other locations to provide real time vehicle identification. Ubisense UWB sensors are deployed in an array around the coverage area and work together to receive the UWB signal from the tag and determine the vehicle location. Ubisense UWB provides a sub meter location 99% of the time ensuring that each vehicle is located in its respective bays.

Figure 66 - Ubisense UWB Sensor Data

8.3 System Architecture
Ubisense Transit Management Solutions are comprised of location hardware for the vehicles, sensing infrastructure for the divisions, and application software to deliver the functional requirements specified by MONTEBELLO BUS LINES.

Each vehicle is fitted with a Ubisense tag so that it can be identified in any depot which has Ubisense sensing infrastructure installed. Ubisense sensors are networked POE devices and connected to the local network at each division. Location network traffic is forwarded to the application server for consumption by the SmartSpace software application.

Ubisense SmartSpace application is hosted on a server and provides all application functionality, integration services, user interfaces, and historical data logging. All user interfaces can be accessed by any browserbased device with connectivity to the network, access to the user interfaces are controlled through the Users and Roles configuration.

A more detailed explanation of the hardware and software architecture can be found in Section 6.2 and 6.3

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 48
Created for Avail Technologies
4/14/2023

8.4 Integration Overview
The Ubisense SmartSpace platform is an open platform that supports flexible integration into an existing ecosystem of business systems. In the case of MBL, integration with other business systems allows for enhanced yard management application functionality, joining accurate location data with context relevant business data, workflows, and management policies. The beauty of SmartSpace is that the configuration deployed today can be easily modified and extended in the future, allowing Montebello Bus Lines to gain incrementally more value out of existing data and their investment in a system like SmartSpace, all through configuration.

To populate the SmartSpace Yard Management data model, Ubisense integrates SmartSpace with Avail system.

Avail Technologies Inc. (Preferred Partner of Ubisense) Integration Avail Technologies Inc. has designated Ubisense as Preferred Partner, allowing for the ability to offer seamless integration with an already established working relationship. Through the life of this implementation, due to the partnership, there is potential for further enhancements beyond the currently stated features to be offered in the future.

Ubisense SmartSpace will interface with the Avail’s API endpoint using http calls and JSON packets to receive at a minimum:
• Availability status.
• Operator assignment and run.
• Maintenance status and holds.
• Vehicle Cleaning Status, Disinfected and ready for revenue.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 49
Created for Avail Technologies
4/14/2023

8.5 Coverage Areas
For each garage, the images below show the areas covered by the systems, the location technology and any areas excluded from coverage.

Base Coverage
Outdoor RTK-GPS:

Indoor UWB:

Add-on (Optional)
Outdoor RTK-GPS:

Indoor UWB:

Maintenance Area and Outdoor Parking

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 50
Created for Avail Technologies
4/14/2023
9 MBL Transit Management Solution Requirements
Requirements from RFP 23-8 - Yard Management System
Yard Management System (YMS)

1. The Yard Management System shall maintain a MBL yard plan showing the current vehicle locations, IDs, availability status, and assignments by operator and run; and provide for vehicle status updates by the Maintenance Department. The yard plan and vehicle status shall be available to the Dispatch Center console and to selected pre-existing Maintenance Department workstations. Other requirements, capabilities, or features of the Yard Management System shall include but not limited to:
1) Display MBL yard plan in graphical format matching the actual layout of the yard.

Yes, SmartSpace provides an easy to use interface with a 2D, browser-based map which matches the physical layout of the yard and displays the real-time position for each vehicle location within the yard.

SmartSpace UIs can be viewed on any connected device such as a phone or tablet. The UI allows for graphically rich layouts and vehicle icons. Vehicle icons can display various representation based on model, color codes based on status, labels for vehicle ID or pullout time, and decorations indicating error conditions or maintenance requests, among other things. 2) Automatically record movements of a vehicle in, out of, and within the yard.

Yes, Ubisense Dimension4 sensors coupled with the Ubisense SmartSpace software, record real-time locations of vehicles entering the yard, exiting the yard, and anywhere at any time within the yard. The Dimension4 sensor system provides centimeter level accuracy and continuously track in real-time the locations of vehicles without any interaction required from the user.

Location data is stored in a SQL database for historical use can used to generate the ‘Location History’ report which presents a snail trail of the vehicles movement and dwell times at each stop point.

Historical data is available for use in external systems as well, such as PowerBi.

2. Provide vehicle status such as:
• Holding vehicles for maintenance
• Vehicle being cleaned and disinfected
• Vehicle disinfected and ready for revenue service etc.

Yes, SmartSpace provides, via its browser-based map the ability to display details about a specific vehicle, like the current status of a vehicle, automatically detected based on the vehicle location, such as ongoing cleaning and disinfection, as well as any information that can be pulled from the CAD/AVL system. The 2D browser-based map allows for vehicles to be filtered, searched, or tracked using any attribute associated with a vehicle, such as a vehicle name, ID, status, type of vehicle (such as electric, hybrid, gas), current location, etc...

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 53
Created for Avail Technologies
4/14/2023
11 The Understanding of Work and Project Approach

11.1 Project Delivery Methodology
The Ubisense project methodology spans the delivery project lifecycle – from project kick-off through to project end-of-life (retirement) – and outlines the key (mandatory) activities, deliverables, and milestones that shall be achieved for each RTLS delivery. This framework seeks to align all members of the project team by clearly defining goals and accountability across the various project phases and required activities.

Ubisense will provide the following service deliverables, following our proven methodology for design, install, test, and deployment of SmartSpace RTLS solutions:

Project Phases:
• Detailed Design Phase
• Installation and Implementation Phase
• Integration Testing Phase
• Training, Introduction and Stabilization Phase
• Final Acceptance
Project Management by Ubisense is provided across all phases.

11.2 Detailed Design Phase
The detailed design phase is a critical phase to define and agree the complete infrastructure, software configuration and roll-out plan for the solution. This phase starts with a project kickoff meeting and comprises a series of workshops conducted with all key stakeholders with both Ubisense and the customer.

The design workshops allow the customer to provide direct feedback on the look, feel, and behavior of the software configuration, color schemes, and other interfaces.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 54
Created for Avail Technologies
4/14/2023
All results are documented in a comprehensive Detailed Design Document that Ubisense creates and the customer reviews and accepts. The following list describes the most important tasks and deliverables:
• Define project organization, roles and responsibilities • Review project scope and areas to be covered by SmartSpace as defined in this proposal • Conduct a detailed site survey to define the precise location, orientation and mounting approach for each sensor, which results in the Detailed Sensor Installation Plan (PDF document) • Agree the tag attachment location for assets to be tracked, detailing the assumptions described in this proposal • Agree the server, client and network architecture for operating the SmartSpace solution • Review and detail the use cases that will be supported by the SmartSpace solution • Specify the necessary data model and configuration of the SmartSpace solution in order to meet the use cases.

Items to be specified depend on the use cases and the SmartSpace modules included in this proposal. Examples are: object types and properties, representations, map layout, rules, areas, filters, searches, reports, user model
• Specify any interfaces between SmartSpace and customer IT systems as far as such interfaces are included in this proposal. The specification comprises definition of protocols and data to be exchanged between the systems
• Define any customer specific extensions to SmartSpace products as far as such extensions are included in this proposal
• A System Specification Document describing the details of the use case and the necessary Smart Space configuration, as well as the integration with Customer’s IT systems. The basic assumptions outlined in section “Project Scope” will be the basis of the System Specification Document, any fundamental changes will be treated as change a request.
• Definition of test procedure and acceptance criteria
• Create a test specification including the definition of acceptance criteria, detailing the assumptions of this proposal.
• Create a training plan
• Review and detail project schedule, defining a phased approach, if necessary • Support the customer’s creation of an operations and support model, including any necessary changes to work processes, fallback procedures, etc.

The detailed design session may take place over multiple on-site visits, comprising of a site survey to determine hardware locations and a joint design workshop with Customer to agree on the application configuration.

Ubisense consultants prepare, moderate and document the necessary workshops and reviews. The phase is completed by the milestone “Detailed Design accepted”.

11.3 Implementation And Testing
Software Installation and Configuration:
• Install agreed Ubisense SW products on servers and client computers • Apply the SmartSpace configurations as agreed in the Detailed Design Document (Examples: create data model, representations, map layout, rules, areas, zones, filters, searches, HMIs and reports; load facility CAD plans; create user model)

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 55
Created for Avail Technologies
4/14/2023
• Configure SmartSpace interfaces to customer IT systems as agreed in the Detailed Design Document • Minor on-site changes to the Ubisense SmartSpace configuration, as agreed in the System Specification Document, in the event of required configuration changes or changes to Customer systems. • Develop and apply customer specific SmartSpace extensions as agreed in the Detailed Design Document • Perform functional tests of the applied SmartSpace configuration and extensions RTLS Hardware Installation:
• Train the customer or their contractor on mounting, orientating and cabling Ubisense sensors, following the Detailed Sensor Installation Plan; assist with any questions concerning the sensor installation • Remote check of correct network connection and timing distribution of sensors, after sensors have been mounted and cabled (network + timing) by Sub-Contractor. Confirmation of the complete and correct connections of all sensors to the Ubisense platform incl. a correct timing distribution is a prerequisite for Ubisense’ on site visit to complete implementation and testing • Configure the sensor infrastructure (sensors, sensor groups, timing tree, network parameters) in SmartSpace • After completion of sensor mounting and cabling by the customer, check sensor positions and orientation, survey sensor positions using a Total Station, calibrate and test sensors • Validate tracking quality in the areas to be covered as defined in the Detailed Design Document. If necessary optimize sensor positions and orientation together with the customer • On-site check of mounting and orientation of new sensors, surveying, calibration, configuration and tracking test of new sensors and cells
The Installation and Implementation Phase is completed by the milestone “System installation completed”.

11.4 Integration Testing Phase
Reliability testing is critical to ensure the application is working optimally and can be used as defined in the Detailed Design Document. Ubisense and the customer will jointly test the correctness and reliability of the solution. This comprises:
• Joint testing of the end-end SmartSpace solution and IT interfaces, following use cases and test cases defined in the Detailed Design Document
• As far as appropriate for the agreed use cases, statistical reliability testing using proven Ubisense test methodology
The phase will be completed by the milestone “System released for go live”.

11.5 Training, Introduction and Stabilization Phase
Training
Ubisense will provide comprehensive training on the use of the SmartSpace application and all of its feature sets.

Ubisense utilizes a train the trainer approach and will provide training to key stakeholders, management, and team leads.

Confidential and Proprietary
© 2023 Ubisense America LLC.

Ubisense Transit Management Page 56
Created for Avail Technologies
4/14/2023
• End User Training will be provided with focus on the use of the configurated application functionality for daily users.
• Power User Training will be provided to appointed personnel. This training will cover normal operation sustainment such as updating data, adding/removing vehicles, managing the tag associations • Admin/Application Owner Training will be provided to appointed personnel and will cover software and hardware troubleshooting, hardware replacement, server management and ticket reporting, etc.

Introduction and Stabilization
Following the roll-out schedule defined in the Detailed Design Document, the released system will be transferred into production, in phases, as agreed.

The customer is responsible for operating the system in the production environment. • Remote check of applied changes and system performance for minimum 2 full weeks, incl. regular status calls with Customer and documentation of any issues or identified change requests • Remote review of installation performance, adjustment of any configuration, which may be necessary to address issues identified during the remote check, including re-testing changed configuration • One additional on-site visit (one week) to address any stabilization issues and apply final adaptions • At the end of the stabilization phase the system will be accepted by Customer, assuming there are no open issues which have a severe impact on operations.

11.6 Project Management
The allocation of a Project Manager (PM) to act as the single point of contact (POC) for the customer concerning all aspects of their transformation to utilizing SmartSpace is a best practice Ubisense follows. For large installations, a full-time PM will be allocated. For smaller scale installations, a PM may be assigned part-time. The PM is responsible for the coordination of all activities and deliverables to be completed to fulfil the customer’s business requirements, including the management of the overall project schedule, risk and issue management, and all communications – internally and with the customer - regarding the project’s progress. The PM is also responsible for tracking and controlling the project’s costs and forecasting revenue generation. During a project, the following deliverables will be the responsibility of the Project Manager.

11.7 System Verification and Testing Process
Acceptance testing and acceptance criteria for the Dimension4 location tracking system Within the project phase “Integration Testing” the reliability of the Dimension4 location tracking system will be tested on top of the basic tracking validation tests already done during the project phase “Installation and Implementation”. The latter validate the correctness of the sensor configuration, survey and calibration, whereas the tests, which are described in the following, prove, if the reliability and robustness of the location tracking system is sufficient for the agreed use cases.
• For the complete area to be covered by Ubisense Dimension4 sensors (defined within the Detailed Design Document) Ubisense tags, either mounted to assets which shall be tracked, or – in case those