Progress 09/01/23 to 08/31/24
Outputs
Target Audience:
Nothing Reported
Changes/Problems:Challenges and changes have revolved around project timeline (No-Cost Extension approved 07/18/24), pilot parameter alterations, and redistribution of project resources (Budget Revision Request submitted 11/07/24). Timeline: FR8relay's proposed Work Plan intended to complete Technical Development (TO1) and shift focus toward Partner Engagement (TO2) and Validation (TO3) in the second year. However, due to an ongoing life-threatening condition of key personnel beginning December 2023, the completion of the software prototype (TO1) was significantly delayed. The most significant challenge in TO2 has been securing suitable freight loads for the live trucking pilot. For example, Watco identified a customer account that appeared to be an ideal fit for a fall 2024 relay pilot, offering ample freight moving in complementary directions over a two-week period. However, this opportunity did not materialize because the contracted carrier's drivers were not domiciled in the required locations. While the identified lane was promising for relay operations, the current distribution of human and equipment resources did not align with operational needs. To address this, we continued further data analysis to pinpoint alternative freight lanes and loads with relay potential, a challenging task in a currently volatile freight market. One promising approach we are leveraging involves analyzing the Request for Proposals (RFP) data Watco uses to strategize their annual bids. By advising Watco to target freight contracts with lanes optimized for relay configurations in 2025, we are proactively creating a system aligned with relay operations, rather than retrofitting relay opportunities into an unoptimized network. Pilot Parameters: Watco wishes to limit the scope of the original pilot from 5 nodes to 3 nodes to mitigate operational risk by reducing complexity. They have also proposed simplifying the project's nodal site operations by utilizing physical sites known to partners, instead seeking out partnerships with third-party locations. They have confirmed that our existing teams should be able to monitor and support each node during the pilot, further simplifying TO2 by removing the need for recruiting and training external nodal operators. Redistribution of Project Resources: In a Budget Revision Request (submitted this fall), we proposed reallocating savings from the narrowed pilot parameters to support increased efforts by our Principal Investigator and Software Developer, both of whom are essential to achieving the technical objectives of our project. The expanded data analysis (described above), additional time to clean data sets, and revisions to our relay scheduling logic and algorithm development (based on iterative feedback fromtrucking partners) have all demanded more time. What opportunities for training and professional development has the project provided?
Nothing Reported
How have the results been disseminated to communities of interest?
Nothing Reported
What do you plan to do during the next reporting period to accomplish the goals?Technical Objective 2 Continued: Once the loads have been secured for the pilot, we anticipate that securing truck drivers, tractors, trailers, and nodal sites will be smooth, as Watco will be facilitating this within their existing networks. We will also devise appropriate procedures and tools for real-time support of participants during the live pilot. Validation Phase (Technical Objective 3): Simulation Revalidation: The PI and SD will revalidate Phase I simulation results using updated load data and pilot-specific conditions to minimize risks. Revised simulations will be shared with pilot partners, with feedback integrated as needed. Pre-Pilot Preparation: The PI and Watco will confirm active loads and fill gaps with dispatchers. The PM and PA will ensure accurate system data entry for tractors, trailers, drivers, and loads. On-site training will cover job assignments, pilot protocols, app usage, and trailer exchange processes. Pre-pilot surveys and evaluations will also be completed. Pilot Implementation: The 2-week pilot will include round-the-clock monitoring by the PI, PM, and PA, who will address technical and logistical issues. The SD will provide software support, and the PI will liaise with Watco on load progress. Data Collection and Analysis: Pilot data will be compiled, analyzed using Excel and Python, and assessed qualitatively for content by coders. Key metrics include driver time away, equipment utilization, transit time, and empty miles. Results will be synthesized into a case study. Findings Dissemination: A case study will be shared with participants and stakeholders via email and presented at community events led by the PM. A final report will also be submitted to the USDA.
Impacts
What was accomplished under these goals?
Technical Objective 1: Technical Development In spite of delays (described in the Changes/Problems section below), during the reporting year, we completed Version 1.0 of a software system with the minimum features required to implement live relay trucking and developed a testing methodology. Technical Objective 2: Partner Engagement We developed a cost model analysis with inputs and feedback from our trucking project partner, Watco Logistics. We found that relay could increase profitability between 50% and 500% (depending on the lane). This analysis answered one of Watco's top two questions: What are the net savings from relay operations when compared to relay operating costs? Significant time in TO2 has been spent on data analysis to identify the freight lane and load candidates for the relay pilot, meeting Watco's operational criteria. This has beena particularly challenging task in a currently volatile freight market. The task began with analyzing load data for Watco's current contracts, andexpanded to analysis of Request for Proposals (RFP) data that Watco is usingto strategize their 2025bids. By advising Watco to target freight contracts with lanes optimized for relay configurations, we are proactively creating a system aligned with relay operations, rather than retrofitting relay opportunities into an unoptimized network. Beyond pilot planning with Watco, our team has designed a monitoring and evaluation approach to measure pilot progress and outcomes. We created instruments for quantitative and qualitative data collection and collecting baseline data from all pilot participants and stakeholders. This approach and its instruments will be further refined with feedback from pilot partners in the coming months.
Publications
|
Progress 09/01/22 to 08/31/23
Outputs
Target Audience:
Nothing Reported
Changes/Problems:Our research timeline was extended due to the following reasons: Software Developer - We started our recruiting efforts in September 2022,but due to the extremely competitive market for software development talent, we didn't finda good candidate until the end of January 2023. Trucking partner - We faced some difficulties getting meetings with Watco early this year due to their busy schedules around acquisitions and construction of their new offices and warehouse. We resolved this issue after discussions with their team and being assigned a new point of contact. What opportunities for training and professional development has the project provided?
Nothing Reported
How have the results been disseminated to communities of interest?
Nothing Reported
What do you plan to do during the next reporting period to accomplish the goals?Technical Objective 1: Technical Development The latest version of each software application will be demonstrated to and tested by our partners at Watco in January (following their busy trucking season). Iterative feedback will be integrated into the product as many times as necessary to fulfill Watco and FR8relay's standards for operational needs. External APIs will function to import load data from Watco's fleet management system using either file transfer protocol (FTP) or REST APIs. While Thakur and Bee have garnered an understanding of Watco's data types and formats (e.g. asset identification, zip code, time, etc.), the development of these integrations is pending Watco's final stated preferences around factors having variable costs (e.g. API call frequency, etc.). Project team members will conduct quality testing for each app and log bugs in Jira (software project management tool) to be fixed by Bee. Once a satisfactory version is complete, it will be shared with a larger group of pilot partners for their feedback. These inputs will be evaluated and integrated into the final beta product. Technical Objective 2: Partner Engagement Once the lane and nodes are finalized with Watco, they will assist us in securing the loads, carriers, drivers, tractors, and trailers needed for the pilot. Watco has an existing network of independent motor carriers from which to recruit trucking companies and/or drivers domiciled in the rural communities at each relay exchange location to participate in the pilot. In cases where Watco's network does not include drivers domiciled in or around our pilot relay nodes, Watco has agreed to onboard additional carriers and owner-operators recruited by FR8relay so long as they meet their carrier requirements.For this pilot, minimum requirements are one acre of paved land in close proximity to the interstate exit (for both north and southbound lanes). A site candidate could be an empty lot of land or an open area of an existing fuel station (local or chain). Ideally would have a small office space and bathroom on site. For the pilot, node operators could use office space off site and travel to site during trailer exchange windows. Plans for nodal site operators will be determined in partnership with broker, carrier, and business owner partners. However, the preliminary plan is for FR8relay to hire three people at each nodal exchange point to staff the site 24 hours a day throughout the 2-week period. Our final tasks in TO2 will be developing appropriate procedures and tools for supporting participants during the pilot and designing a monitoring and evaluation approach to measure pilot progress and outcomes. This will include creating instruments for quantitative and qualitative data collection and collecting baseline data from all stakeholders. Technical Objective 3: Validation The Validation objective consists of five primary tasks. First, the Thakur and Bee will work to revalidate the simulation results from the Phase I project using updated load data sets from Watco and more specific conditions from the upcoming pilot. The purpose of this is to reduce the risk when running the pilot with live trucks and drivers. The latest simulation results will be shared with pilot partners, any feedback will be integrated, and simulations will be re-run if applicable. Second, our team will engage in pre-pilot preparation. Thakur will work with Watco to confirm the active status of all loads assigned to the pilot, and use dispatchers to procure additional loads to fill in any gaps in the pilot relay circuit. The Yuan and Hopper will confirm the accurate data entry of all participating tractors, trailers, drivers, and loads in the software system. The Thakur, Yuan, and Hopper will conduct an on-site training with pilot participants at each nodal site. We will communicate specific job assignments to individual drivers and nodal operators and distribute related supplies and equipment (including to substitute drivers). This will include instruction and practice of pilot protocols including mobile application use and physical process of trailer drop and hook exchange. Our team will finalize a rigorous monitoring and evaluation protocol and conduct pre-pilot surveys and/or interviews at this time. The third Validation task is the 2-week implementation of relay trucking. Thakur will be responsible for initiating and terminating the pilot. He will be supported by the Yuan and Hopper to closely monitor pilot activity around the clock to provide technical and logistical support to drivers and nodal operators as needed. This includes recommending and deploying relay disruption mitigations wherever applicable. Bee will provide technical support for the software applications as needed, and Thakur will maintain communications with Watco on the progress and completion of each load. The validation fourth task is concerned with collecting and analyzing data. Data will be compiled from pilot and pre-pilot instruments. Post-pilot surveys and/or interviews will be conducted. Thakur and Bee will use Excel and Python to statistically analyze quantitative data. Qualitative data will be analyzed for content by multiple coders (likely Yuan and Hopper) to avoid bias. Results will be synthesized and reported in case study format. The last task is sharing research findings back to participants and other stakeholders in two ways. First, the case study report will be emailed or mailed to all pilot participants and other key stakeholders. Second, the Yuan will facilitate one live stakeholder event in each nodal community for the purpose of presenting research findings to stakeholders and providing question and answer (Q&A) sessions. Finally, a final report will be composed for the USDA. ?
Impacts
What was accomplished under these goals?
In line with our proposal, FR8relay's Year 1 Work Plan focused on the first two of our three Phase II technical objectives (TO): Technical Development (TO1) and Partner Engagement (TO2). Technical Objective 1: Technical Development Phase II technical development has built upon Phase I work to develop a beta software system with the minimum features required to implement live relay trucking with dynamic scheduling on a cloud platform with seamless dissemination of processed information to various system users. Primary TO1 tasks include: user interface design, frontend coding, backend updating, application programming interfaces (APIs) development, and quality testing. The bulk of this work has been successfully performed, and we are on course to complete TO1 by January 2024. Principal Investigator (PI) Aayush Thakur and Full Stack Software Development Engineer (SD) Jon Bee have been responsible for the iterative development of mobile and web application user interfaces. Thakur built upon preliminary user experience research conducted in the field to understand trucking carrier operational processes and increase familiarity with other trucking softwares. He worked with Bee to develop product UI/UX wireframes for three software applications (apps): 1) trucking carrier web app, 2) truck driver mobile app, and 3) FR8relay administrative (admin) app. In the pilot, Watco will use the web-based Carrier App to configure a relay lane on FR8relay's platform. Next they will import their loads to the platform via external application programming interfaces (APIs). FR8relay's system will then schedule relay-eligible loads on the given lane and assign relay driving duties to driver users. Bee designed two user types for carriers: broker user and dispatcher user. During the pilot, the Driver App will guide truck driver participants in a relay workflow, from accepting relay driving assignments, to navigation to load pick-up and drop-off sites, to bill of lading (BOL) documentation transfer, to trailer exchange, to sending relay progression notifications to other platform users. In advance of the pilot, FR8relay's project team will use the web-based Admin App to create carrier user accounts for Watco, as well as any partner carrier participants, and to create driver user accounts for all truck drivers participants. Throughout the pilot, FR8relay will monitor and manage these accounts as needed. Bee has implemented the design requirements for each interface with frontend software coding. He has completed backend database updates, developed the logic for internal APIs to connect the web and mobile applications with the backend, and is in the process of coding for fluid internal connectivity. Technical Objective 2: Partner Engagement The second objective of this Phase II project focuses on establishing the working relationships to mobilize human and machine assets, physical land, and other resources necessary to implement and evaluate our relay trucking pilot. Primary TO2 tasks include: securing freight loads, truck drivers, tractors, trailers, nodal operators, and physical sites for relay trailer exchanges, as well as developing pilot monitoring and evaluation (M&E) and support processes and instruments.The project team discovered early on that we placed most TO2 tasks too early on the proposed timeline for reasons explained below. This said, we do not expect significant delays in TO3 pilot implementation, as Watco's support should facilitate narrowing down the partner search. PI Thakur and Project Manager (PM) Deme Yuan have been meeting intermittently with executives and other staff from Watco since February 2023. Initial meetings focused on presenting our relay model and proposed pilot scope to an expanded group of Watco team members supporting this pilot, and answering their model, operational, and technology questions. Watco has two central research questions surrounding relay trucking viability for freight brokerages: 1) freight density and volume analysis within their existing networks, and 2) net savings from relay operations when compared to operating costs. Thakur and Bee have been analyzing Watco's operational load data and identifying patterns for ideal lanes and load candidates for the pilot. The project team has added a cost analysis model task. Discussions with Watco have also highlighted focus on methods for reducing risk during the pilot. This includes their preference for partnering with a single trucking carrier for the pilot to reduce additional legal considerations during trailer exchanges (e.g. eliminates interchange liability agreements), and offers the opportunity to use potential existing resources (e.g. physical sites for trailer exchanges and/or on-site staff and security). A second risk mitigation strategy Watco proposes is to narrow the geographic scope from a five-node pilot to a three-node pilot. Doing so would reduce system complexity to lower the risk of compounding delays caused by relay disruption events. Early on, Thakur, Yuan, and Project Assistant Jordan Hopper worked with subcontractor Building Communities to identify and document prospective business and landowners in the communities proposed as physical sites for relay trailer exchanges during the pilot. The proposed sites were: McKinney, TX; Chouteau, OK; Kansas City, MO; St. Louis, MO, and Joliet, IL. However, based on the potential lane alterations discussed with Watco, we have put community outreach on hold until nodes are solidified. ?
Publications
- Type:
Conference Papers and Presentations
Status:
Published
Year Published:
2023
Citation:
Relay Model for Full Truckload Freight Transportation. Chanchad, Neel; Thakur, Aayush; Milburn, Ashlea - IISE Annual Conference. Proceedings, 2023
|