✅ McLeod (LoadMaster) Integration Guide for Tier 2

This guide walks Tier 2 support through preparing and implementing the LoadMaster (McLeod) integration for new RTA customers, including configuration, scripting, and scheduled task setup.

🧭 Phase 1: Initial Customer Setup & Discovery

🎯 Meeting Preparation

  • Participants: Tier 2, CSM, Fleet Manager, and Accountant.

  • Schedule Kickoff Call to:

    • Set expectations and review integration capabilities.

    • Confirm customer has completed basic RTA training.

    • Optionally include McLeod (not required due to slow response).

🔍 Integration Utility Overview

Integration Utility

Description

Common Use Case

Should the Customer Enable It?

lmhubimp.cob – PM Hub Readings Import

Imports odometer readings from LoadMaster into RTA

Enables timely PM updates and audit trail of mileage

✅ Recommended if They don’t have telematics

lmfulimp.cob – Fuel Ticket Import

Imports fuel transaction history into RTA, including gallons, cost, odometer

Keeps RTA fuel records in sync for audit/fuel reporting

✅ Recommended if using LoadMaster fuel data

lmmsgimp.cob – Mobile Messages Import

Imports driver/vehicle notes into RTA

For fleets using in-cab communication & note-taking

🔶 Optional; depends on use of mobile comms

lmcstimp.cob – Customer/Payee Import

Imports or updates customer records into RTA

Required for invoice VM journal export & WO associations

✅ Essential if exporting invoices or journals

lmvndimp.cob – Vendor Import

Imports vendor contact and billing info into RTA

Required for purchase order and AP voucher linkage

✅ Generally needed

lmvehexp.cob – Tractor/Trailer Export

Exports vehicle data from RTA to LoadMaster (e.g., trailers, tractors)

Needed when RTA is the master system for units

🔶 Optional based on workflow ownership

lmpmexp.cob – PM Message Export

Sends due PM status messages from RTA to LoadMaster

Useful if dispatchers want to see PM warnings in LoadMaster

🔶 Optional but recommended

lmwoexp.cob – VM Journal Export

Exports work order costs for journal entries

Used if customer tracks repair costs in LoadMaster

✅ Recommended if they need WO cost accounting in LM

lmpoexp.cob – AP Voucher Export

Exports closed POs for AP processing in LoadMaster

Required if McLeod handles invoice payment & AP

✅ Needed if AP is done in LoadMaster

lminvexp.cob – Invoice/Settlement Export

Exports RTA invoices for customer billing and deductions

Vital if LoadMaster manages settlements or billing

✅ Essential if LoadMaster handles settlements

🧾 During the Meeting

  • Tech Support:

    • Review the above utilities and confirm which apply.

  • CSM:

    • Document decisions and expectations.

    • Send a recap email to all parties involved.

🛠️ Phase 2: LoadMaster Configuration & File Prep

🔧 Script & File Setup

📁 Copy Files and Scripts

  • Navigate to:
    \\ftp\FTP\localuser\Mcleod Master (loadmaster)

  • Copy all contents to the customer’s FTP folder:
    \\FTP\FTP\localuser\RTAXXXXX\

⚙️ PowerShell Script Preparation

  • Locate the file in \\ftp\c$\users\public:
    RTA03049_Trekker_Loadmaster.ps1

  • Copy and paste it into the same .

  • Rename the copy to:
    RTAXXXXX-CompanyName-Loadmaster.ps1

  • Open the file in PowerShell ISE or Notepad++:

    • Update the $rtaSerialNumber

    • Uncomment and enable only the needed integration utilities (based on Phase 1)

📝 Batch & Sync Script Configuration

  • Edit the following files in \\FTP\FTP\localuser\RTAXXXXX\Prod\RTASYNC:

    • download.txt: Include the FTP session URL (see below)

    • Loadmastersync.bat: Confirm sync parameters

🔐 WinSCP & FTP Password Formatting

  • Launch WinSCP outside of Bastion to connect.

  • Generate PowerShell script with credentials encoded via:

    • Session > Generate Session URL/Code

    • Include username & password

    • Switch format to PowerShell Script

  • Copy the generated URL into download.txt

🧩 Phase 3: RTA Configuration

🗂 Enable Integration Enhancements

  • Activate either:

    • RTALME – Standard

    • RTALMA – Advanced (adds support for GL cost code mapping for journals)

⚙️ Directory Setup via editcnfg.cob (SAU)

  • Configure:

    • RTA_TO_LME_DIR: For RTA exports (→ LoadMaster)

    • LME_TO_RTA_DIR: For LM exports (→ RTA)

    • LME_ARCHIVE_DIR: Processed data storage

🏢 Facility Configuration (MFM)

  • Navigate: Master > Facility > File Maintenance (MFM)

  • Set:

    • LoadMaster Company ID (TMS #)

    • Optional: Facility-specific import/export directories

🧑‍💼 Phase 4: CSM & Customer Tasks

👤 CSM Responsibilities

  • Import RTA Customers, Vendors, and Vehicles.

    • The Customer Abbreviation needs to match the Customer/Payee ID from Loadmaster

    • The Vendor Abbreviation needs to match the Vendor ID from Loadmaster

🧾 Customer Tasks

  • GL Code CSV for customers - This is vital if they are using lminvexp, and also where a lot of time will be spent figuring out what costs go to what GL.

  • Vendor GL Codes entered into the vendor account number field

🔁 Phase 5: Automation of Integration Process

⏱ Schedule in VisualCron

  • Clone job: RTAXXXXX - RTA Loadmaster - TEMPLATE

    • Rename to: RTAXXXXX-CompanyName-Loadmaster

    • Do not activate it immediately

  • Set the cloned job to:

    • Execute the prepared PowerShell script (.ps1)

    • Run every 15 minutes

    • Verify correct task steps and triggers

  • After validation, enable and activate the job

🧼 Final QA & Testing

  • Validate:

    • Directories and script configs

    • File exchange via WinSCP

    • That exported/imported files process correctly

  • Test:

    • Manual run of .ps1 script

    • Verify each utility functions as expected

    • Scheduled VisualCron job runs reliably

Search