Getting Started with LoadMaster (McLeod) Triage
- Robert Bosner
This article focuses on closing the gap for implementation of LoadMaster! This is primarily an outline of what needs to be done and by whom. For in depth information on a process, click on the referenced KB articles.
New RTA Customer wanting LoadMaster Integration - Where to start:
First - Tech Support and CSM: Schedule meeting with RTA customer to review the expectations of the process and what the Integration is capable of providing. (Fleet Manager and Accountant needed for meeting). It’s recommended to have McLeod on that call, but not required, given their lack of response time.
RTA Customer should at least complete basic training before this meeting takes place! Otherwise, it will turn into a training call, trust me!
For the first meeting, it’s best to have all teams (departments), so everyone is on the same page and understands their roles in the process and what to expect from each other.
During the meeting, Tech Support should review the export utilities outlined in Load Master Integrations - RTA Knowledge Base - Confluence (atlassian.net).
Key points are to know if the customer uses the Invoice Settlement Deductions in LoadMaster (lminvexp.cob).
CSM should be documenting a timeline/recap of the discussion about everything discussed and what is to be expected after the meeting. That recap should also be sent out in an email to all parties involved. Identify what objectives Tech Support, the customer, and CSM need to complete.
Tech Support:
Prepare the LoadMaster integration configurations and PS scripts. This can be done at any point of the process, even before meeting with the customer.
Copy PS Script “Loadmaster Master Script.ps1” and rename it before making any changes.
Copy the folders in \\ftp\FTP\localuser\Mcleod Master (loadmaster) to the customers FTP folder, then edit their “download.txt” and “Loadmastersync.bat” with their data.
Complete as much as possible with the data you have, any missing data can be updated once you obtain it from the customer. FTP password can be obtained from CSM if they still receive a copy of the RTA Welcome Email. Setting up Load Master - RTA Knowledge Base - Confluence (atlassian.net)
Edit the “LoadMaster Settings” in RTA Classic (MFM)
Prepare the Visual Cron task.
Clone the “RTAXXXXX- RTA Loadmaster - TEMPLATE”. Only change the job name and save it before making any edits to the task!
Schedule meeting with either McLeod or Customer’s IT to setup/test FTP scheduled task
If their McLeod system is hosted on their own servers, the meeting with be with their IT, some who has access to the server and has credentials an administrative service account.
If their McLeod system is hosted by McLeod, the meeting with be scheduled with McLeod.
CSM:
Import RTA Customers, Vendors, and Vehicles.
After meeting, send the “customer import.csv” client for them to identify which customer will need to have the Invoice VM journals created from the WOs.
The Customer Abbreviation needs to match the Customer/Payee ID from Loadmaster
The Vendor Abbreviation needs to match the Vendor ID from Loadmaster
RTA Customer:
Fill out GL Code csv file for their customers.
Enter the GL codes for Vendors in the Vendor Account number (this can be done in WEB).