This article describes the plan for testing the new software releases that are compatible with service days that last longer than 24 hours. It also contains the procedures to be used during the testing.
Prerequisites to Testing
Fixed End Server Upgrade
The greater than 24-hour service capability requires myAvail version 7.4.10 or higher. This version also has several other components in it pertaining to the improvements made to the myStop website.
Plan
This update is schedule to start at 1000 PST on 4 NOVEMBER 2021. A member of the Avail Upgrades team will communicate the start, progress, and completion of the upgrade process to your agency's admin staff.
In-Vehicle Software Update
The greater than 24-hour service capability requires in-vehicle version 3.6.0.5 or higher and an agnostic MDT.
Plan
For testing, Avail will utilize 2 of the coaches that are part of the agnostic MDT hardware pilot at Arcadia. These coaches will have their IVU’s hard drives replaced with new drives containing to correct software version. Per Avail standard procedure, an Acceptance Test Procedure (ATP) will be performed after the hard drive swap to ensure that the updated IVU’s correctly interface with the in-vehicle systems.
Schedule Data Changes
We can now accommodate the way blocks were originally cut before any splitting was implemented as a temporary measure to make the system work with the service.
There is only one rule: a singular block number can’t span BOTH the 0000 AND the service day (around 0300) boundaries. They can go back to running continuous blocks that don’t require an operator to log out and log into a different paddle to get onto the next trip.
For example, a block that starts at 0001 and runs until 0600 is now valid in our system and a preferable way to build the schedule.
We are asking that the planning team start to make these changes to the schedule data in advance of the vehicle upgrade CAR so that is ready to be published when the fleets are upgraded and can also be used to demonstrate the features in the Test Environment, if desired.
Identification of Runs/Blocks that Qualify
In the currently published version of schedule data, blocks that start on or after 0001 qualify for the new system to use. Blocks that cross both midnight (0000) and Avail’s start of service day (0240) do not qualify for this new system and will not perform correctly.
Avail has identified the blocks/runs below as suitable for testing:
| Start Time | End Time | Block | Run | Service Level |
| 0220 | 0635 | 10888 | 12828 | Sunday |
| 0215 | 0449 | 10218 | 12033 | Weekday |
| 0220 | 0635 | 10218 | 12033 | Saturday |
Test Introduction
This test will use the production myAvail servers and software. It will require that two (2) of the Arcadia coaches that are part of the agnostic MDT pilot be held back from revenue service as the software upgrades and testing are performed. As such, your agency's management staff and Arcadia dispatchers and supervisors will be notified prior to and at the completion of any testing.
During the upgrade and testing, dispatchers may notice that the pilot coaches go on and offline and log into atypical paddles. During the post-upgrade ATP, an Avail representative will be sending in RTT’s and PRTT’s; the dispatcher should respond to these events and initiate contact with the coach as per agency protocols.
Avail will also be increasing the log level on the IVU to passively capture the schedule-related behavior of the pilot vehicle during the revenue usage of this new set of features. Avail will remotely retrieve and review the logs after a 3-day period before turning the logging level back down.
The Avail representative performing the testing will require the following:
- Laptop
- Cellular Hotspot for internet access
- Your agency's network access or VPN client
- Arcadia myAvail username and password
- Ethernet Cable (For RDP)
Test Procedures
Start this test after upgrading the coaches’ hard drives and verifying the system’s functionality via the ATP in section 1.2.1. Start the test procedure after fully rebooting the in-vehicle system via the MDT. This testing needs to be performed during the timeframes dictated by the schedule data. NO MANUAL ADJUSTMENT OF SYSTEM CLOCKS SHOULD BE PERFORMED. Persons performing testing should be ready at the Arcadia Yard, with the bus, prior to 0200 on the days of testing.
Pilot Coach 1
- Enter the coach number below:
Coach: ________ - Allow the in-vehicle system to finish booting and performing automated diagnostics
- Connect your laptop to the IVU’s RDP port and connect to the IVU
- Open Windows Explorer and navigate to the following directory: C:\Avail\IVU
- Locate the file logging.xml, right click on the file and select “Edit with Notepad ++”
- In the file, locate the logger name=”ScheduleDumper”
- Change the level value="WARN" to level value="DEBUG"
- Save the file
- Reboot the IVU using the MDT
- Allow the in-vehicle system to finish booting and performing automated diagnostics
- Verify that the MDT shows both a registration to the fixed end and a valid GPS lock
- Using a run number, with the appropriate service level, from section 1.3 and the Driver ID 1111, log into the MDT. Record the number used below:
Run: __________ - Visually verify that the MDT recognizes the log in details and begins the log-in process
Pass ☐ Fail - Visually verify that the run file download completes successfully, if applicable Pass ☐ Fail
- Visually verify that the Headsign, block sign, and internal sign show the correct service information Pass ☐ Fail ☐
- Log into Arcadia’s instance of myAvail
- Navigate to the Operations tab
- Locate the coach listed in Step 1
- Visually verify that the service information associated with the log in info is shown next to that vehicle in the Status Grid
Pass ☐ Fail ☐ - Using the MDT, press “Menu” then “Trip Select”
- Enter the current time and available trips listed on the MDT below:
Current time: _________
Trip 1: __________
Trip 2: __________
Trip 3: __________ - Press “Home” on the MDT
- Remain logged into the current trip, and wait until the current time is after 0241 (Daily Schedule Build Time)
- Using the MDT, press “Menu” then “Trip Select”
- Enter the current time and available trips listed on the MDT below:
Current time: _________
Trip 1: __________
Trip 2: __________
Trip 3: __________ - Select a trip that starts after 0241 (Daily Schedule Build Time)
- Visually verify that the MDT recognizes the new trip details and completes the trip select process
Pass ☐ Fail ☐ - Visually verify that the Headsign, block sign, and internal sign show the correct service information
Pass ☐ Fail ☐ - Visually verify that the service information associated with the log in info is shown next to that vehicle in the Status Grid
Pass ☐ Fail ☐ - Connect your laptop to the IVU’s RDP port and connect to the IVU
- Open Windows Explorer and navigate to the following directory: C:\Avail\IVU\Logs
- Find the ScheduleDumper logfile and copy it to your laptop
- Close the RDP session
- Shut the coach down
Pilot Coach 2
- Enter the coach number below:
Coach: _____________ - Allow the in-vehicle system to finish booting and performing automated diagnostics
- Connect your laptop to the IVU’s RDP port and connect to the IVU
- Open Windows Explorer and navigate to the following directory: C:\Avail\IVU
- Locate the file logging.xml, right click on the file and select “Edit with Notepad ++”
- In the file, locate the logger name=”ScheduleDumper”
- Change the level value="WARN" to level value="DEBUG"
- Save the file
- Reboot the IVU using the MDT
- Allow the in-vehicle system to finish booting and performing automated diagnostics
- Verify that the MDT shows both a registration to the fixed end and a valid GPS lock
- Using a run number, with the appropriate service level, from section 1.3 and the Driver ID 1111, log into the MDT. Record the number used below:
Run: __________ - Visually verify that the MDT recognizes the log in details and begins the log-in process
Pass ☐ Fail ☐ - Visually verify that the run file download completes successfully, if applicable
Pass ☐ Fail ☐ - Visually verify that the Headsign, block sign, and internal sign show the correct service information
Pass ☐ Fail ☐ - Log into Arcadia’s instance of myAvail
- Navigate to the Operations tab
- Locate the coach listed in Step 1
- Visually verify that the service information associated with the log in info is shown next to that vehicle in the Status Grid
Pass ☐ Fail ☐ - Using the MDT, press “Menu” then “Trip Select”
- Enter the current time and available trips listed on the MDT below:
Current time: _________
Trip 1: __________
Trip 2: __________
Trip 3: __________ - Press “Home” on the MDT
- Remain logged into the current trip, and wait until the current time is after 0241 (Daily Schedule Build Time)
- Using the MDT, press “Menu” then “Trip Select”
- Enter the current time and available trips listed on the MDT below:
Current time: _________
Trip 1: __________
Trip 2: __________
Trip 3: __________ - Select a trip that starts after 0241 (Daily Schedule Build Time)
- Visually verify that the MDT recognizes the new trip details and completes the trip select process
Pass ☐ Fail ☐ - Visually verify that the Headsign, block sign, and internal sign show the correct service information
Pass ☐ Fail ☐ - Visually verify that the service information associated with the log in info is shown next to that vehicle in the Status Grid
Pass ☐ Fail ☐ - Connect your laptop to the IVU’s RDP port and connect to the IVU
- Open Windows Explorer and navigate to the following directory: C:\Avail\IVU\Logs
- Find the ScheduleDumper logfile and copy it to your laptop
- Close the RDP session
- Shut the coach down
Acceptance of Feature Testing
This testing demonstrated and verified that the Avail Technologies vehicle system functions as intended when operating within route blocks that run across our service boundary. Any issues identified during the tests have been documented in the Project Action Item list and will be addressed within the mutually agreed timeframe.