Consultant mapping a dispatch-to-delivery workflow on a glass whiteboard beside a freight dispatch office
Process & Project Delivery · Practice 10

When is a new TMS ready to go live?

A new TMS is ready when a representative parallel cycle reconciles billing to an approved tolerance and settlements, EDI, accounting, access and recovery tests also pass. Explain or fix every difference and obtain owner sign-off.

Consulting does not require a software purchase. When a carrier, broker, or private fleet decides to buy freight transportation software, the product is EXSPEEDITE TMS freight transportation software from Exspeedite LLC, a separately organized sister company under common ownership. Founder Scott Elliott. More than 18 years in freight technology.

Installs & configurationData conversionStaff trainingOn-site go-live

When is a new TMS ready to go live?

A new TMS is ready when a representative parallel cycle reconciles billing to an approved tolerance and settlements, EDI, accounting, access and recovery tests also pass. Explain or fix every difference and obtain owner sign-off.

Parallel run
The same loads are processed in both systems during the same period.
Billing tolerance
The largest per-order difference approved by finance; $0.01 below is an illustrative threshold.
Go-live gate
Billing, settlements, EDI, and GL posting each pass, and each pass is signed off.
Rollback plan
A written way back to the old system if the gate fails after cutover.

Parallel billing comparison

-- Illustrative parallel-run check. SQL Server. Read only.
DECLARE @Tolerance decimal(19,4) = 0.01;
SELECT COALESCE(o.OrderNumber, n.OrderNumber) AS OrderNumber,
       o.InvoiceTotal AS OldSystemTotal,
       n.InvoiceTotal AS NewSystemTotal,
       ISNULL(n.InvoiceTotal, 0) - ISNULL(o.InvoiceTotal, 0) AS Difference
FROM parallel.OldInvoice AS o
FULL OUTER JOIN parallel.NewInvoice AS n ON n.OrderNumber = o.OrderNumber
WHERE o.OrderNumber IS NULL
   OR n.OrderNumber IS NULL
   OR o.InvoiceTotal IS NULL OR n.InvoiceTotal IS NULL
   OR ABS(n.InvoiceTotal - o.InvoiceTotal) > @Tolerance
ORDER BY ABS(ISNULL(n.InvoiceTotal, 0) - ISNULL(o.InvoiceTotal, 0)) DESC;

Illustrative artifact: adapt the table names, keys, date boundaries and business rules to your installed system. No customer results are claimed.

Require one invoice per order in this comparison contract, or aggregate to a documented invoice key. Partition by company and currency; NULL totals and unmatched keys remain exceptions.

Strong Tower Consulting, LLC is a Minnesota freight technology consulting firm founded July 29, 2008 by Scott Elliott. The firm advises carriers, brokers, and private fleets on TMS selection, implementation, data, and IT strategy. Consulting does not require a software purchase. Exspeedite LLC is a separately organized sister company under common ownership and builds EXSPEEDITE TMS.

The make-or-break months

Choosing a TMS gets most of the attention. Implementing it is where the money is made or lost. A well-run implementation gives you clean data, rates that calculate correctly the first time, settlements drivers trust, and a team that knows the system. A rushed one gives you months of billing overrides, payroll corrections, frustrated dispatchers and a system everyone blames.

The software is capable. As our original site put it, "You need to install it right, customize it and train your staff to get the most out of it." The risk is in everything around the software:

  • Waiting in the vendor's queue. Implementation teams are stretched, and your start date keeps moving.
  • Dirty source data. Duplicate customers, old addresses, stale rate tables and inconsistent codes get converted straight into the new system.
  • Generic setup. Tariffs, fuel surcharge tables, accessorials, pay plans and document formats are left at defaults that don't match how you run.
  • Thin training. A couple of webinars, then everyone learns the hard way on go-live Monday.
  • No one on the floor. When something breaks during go-live week, there's a support ticket instead of a person who can fix it.

Get started sooner

If you're moving to a new transportation system and the software company's timeline is too far out, we may be able to bring it back in by taking on the installation and training parts of the project. Vendors have limited resources, and we can help you get up and running sooner while staying aligned with the vendor's methodology and support team.

The same applies to upgrades. When it's upgrade time and the vendor is backed up for months, we can plan and run the upgrade, including custom code compatibility checks, in a test environment first (see Legacy TMS Advisory & Migration).

What we do in an implementation

Installation & environment

Server, database and workstation setup, user access, test and production environments, and the backup and recovery plan that should be in place before the first live load (see Data Protection & Business Continuity). As your business grows, we also handle adding workstations, licenses and terminals.

Configuration for how you haul

  • Company, terminal, division and GL structure
  • Customer tariffs, mileage bases, minimums and fuel surcharge schedules
  • Accessorial codes and rules: detention, layover, stop-offs, lumpers, TONU, hazmat
  • Driver and owner-operator pay plans, deductions, escrow and advances
  • Equipment, trailers and maintenance setups
  • Invoices, settlement statements, cheques, manifests and other business documents (see Reporting & Business Documents)

Data conversion

We plan the data path before anything moves. Customers, consignees and locations, rates, equipment, drivers, vendors and carriers, open AR and AP, and the history you need for reporting and audits are each mapped, cleansed, test-loaded and reconciled. We don't trust a conversion until the AR aging, open payables and key reports tie out to the old system. Cleanup often uses SQL directly against the source data (see SQL Data Mining & Analytics).

Interfaces

ELD and telematics feeds, EDI trading partners, fuel card imports, imaging and the accounting interface each need to be connected, tested and monitored. We coordinate the other vendors so the interfaces are ready on the same day as the TMS (see ELD, EDI & Back-Office Integration).

Testing

We test with your real freight: multi-stop loads, brokered loads, detention, consolidated invoices, owner-operator settlements with deductions, an EDI tender and status update. Then we run parallel where it makes sense, comparing invoices and settlements between old and new systems until they match.

Training

Role-based training for customer service, dispatch and planning, billing, payroll and settlements, safety, maintenance and accounting, on your data, on site or remote. Super-users get deeper training so knowledge stays in the building after we leave (see Training & Enablement).

Go-live week

A written cutover plan, a go/no-go checkpoint, and an experienced person on the floor. During go-live we sit with dispatch, billing and payroll, fix issues as they surface, and work the vendor's support queue on your behalf.

Independent by design

Strong Tower never requires you to buy our software. Our sister company, Exspeedite LLC, builds a TMS, and that's why we understand implementations from the inside. We help you implement the system you chose, and we answer to you, not to a vendor.

Go-lives our clients remember

Since 2008, Strong Tower Consulting has helped carriers through first-time installs, software conversions, upgrades and go-live weeks. Our team includes people who led Training & Installation for a transportation software company and coordinated installations, training and go-lives across North America. Here's what clients have said, in their own words:

How an implementation runs

  1. Readiness review. Requirements, data quality, interfaces, hardware, staffing and calendar. We flag the risks before they become problems (see Business Analysis).
  2. Plan. Schedule, responsibilities across your team, the vendor and us, test plan, cutover plan and rollback plan (see Project & Program Management).
  3. Build. Install, configure, convert and connect interfaces, with regular checkpoints.
  4. Test & train. Scenario testing, parallel runs and role-based training.
  5. Go live. Cutover weekend and on-site go-live week.
  6. Stabilize. Post-go-live support, punch list and follow-up training as you use more of the system.

Are you ready to go live?

Carrier TMS Implementation Stage-Gate & Cutover Readiness Matrix

In enterprise fleet software transitions, rushing a go-live before critical sub-systems are verified creates catastrophic billing halts and driver turnover. Strong Tower enforces five rigorous stage-gates before authorizing cutover:

Implementation Stage-Gate Go-Live Failure Mode Prevented Strong Tower Verification Standard Carrier Operational & Cash Flow Impact
Gate 1: Master Data & Tariff Audit Dirty customer profiles and unverified rating matrices corrupt the new database, requiring manual rating on every order. Automate SQL deduplication and run 100 historical live loads through new rating tables, verifying line-item match against legacy invoices. Prevents post-cutover billing paralysis and ensures customer invoices generate accurately on Day 1 without manual overrides.
Gate 2: EDI & Telematics Integration ELD duty clocks fail to feed dispatch; customer EDI 204 tenders and 214 check calls drop, causing shipper compliance fines. Execute end-to-end integration testing: live GPS pings from Samsara/Motive into dispatch boards, and successful EDI 997 functional acknowledgments. No result is assumed. Measure it on your own records.
Gate 3: Mock Billing & Settlement Parallel Driver pay plans and deduction escrows miscalculate; drivers receive incorrect direct deposits, triggering immediate turnover. Run a full parallel weekly payroll and customer billing cycle in the test environment, tying out settlement totals down to the penny. No result is assumed. Measure it on your own records.
Gate 4: Role-Based User Enablement Staff receives generic vendor webinar overviews; dispatchers lock up during peak Monday morning customer call volume. Conduct hands-on role-specific training using carrier-specific freight scenarios and certify department super-users across every terminal. No result is assumed. Measure it on your own records.
Gate 5: Weekend Cutover & Rollback Plan Cutover weekend runs out of time; unexpected data conversion errors leave dispatch with zero operating software on Monday. Execute minute-by-minute cutover runbook with formal Sunday 2:00 PM Go/No-Go decision gate and fully tested fallback protocol. If the new TMS is not ready, the fleet stays on the current system.

Before we recommend a go-live date, we want clear answers to a short list of questions. If any answer is "not yet," the date should wait.

  • Do converted open AR and AP balances tie out to the old system, customer by customer and vendor by vendor?
  • Have real loads been rated in the new system, including fuel surcharge and accessorials, with results that match what you bill today?
  • Has a full payroll cycle been run in test, including owner-operator deductions, advances and escrow, and do the settlement statements match?
  • Are EDI trading partners tested and ready to send tenders to, and receive status updates and invoices from, the new system?
  • Are ELD, fuel card, imaging and accounting interfaces connected and verified with real data?
  • Has every user been trained on the tasks they'll do on day one, and do you have super-users in each department?
  • Is there a written cutover plan, a go/no-go decision point, and a rollback plan everyone understands?

This list is short on purpose. It's the difference between a go-live that feels like a busy week and one that feels like a crisis.

How do carriers migrate off a legacy AS400 / IBM i TMS without losing rating logic or halting Monday dispatch?

Carriers migrate off legacy AS400 / IBM i systems cleanly by selecting one of four architectural paths, Rehost, Re-platform, SaaS Re-architect, or Hybrid, decoding EBCDIC and packed-decimal DB2 files, extracting embedded RPG/COBOL rating rules into testable tariff matrices, and validating every dollar in a 2 to 4 week parallel pilot backed by a written Monday Morning Failure / Rollback Plan. Most fleet transitions complete within a 3 to 9 month benchmark window depending on terminal count, EDI trading partner volume, and custom RPG tariff complexity.

The 4-Path Legacy AS400 / IBM i Migration Decision Framework

4-Path Migration Decision Framework for AS400 / IBM i transportation systems
Migration Path Architectural Scope Best Fit Benchmark Timeline
1. Rehost (Lift & Shift) Move existing IBM i LPAR, DB2/400, and RPG/COBOL binaries onto managed cloud Power hardware without changing application code. Fleets facing aging on-premise hardware or colocation exit deadlines that need stability before a full TMS replacement. 3 to 4 months
2. Re-platform Convert DB2/DDS physical files and runtime components to modern SQL Server or cloud-native databases while preserving core operational workflows. Carriers with deeply customized green-screen workflows that need SQL reporting, modern APIs, and lower IBM i licensing overhead. 5 to 7 months
3. SaaS Re-architect Full data conversion and process cutover from AS400/IBM i to a modern commercial or cloud TMS with clean master data and native EDI/ELD APIs. Carriers ready to retire RPG/COBOL technical debt and standardize dispatch, rating, and settlements on a supported platform. 4 to 8 months
4. Hybrid Coexistence Modernize dispatch, ELD telematics, imaging, and customer portals in a new TMS while keeping IBM i active for historical GL, audit archives, or phased terminal rollouts via CDC/API sync. Multi-division or high-volume fleets where a big-bang weekend cutover across all terminals carries unacceptable operational risk. 6 to 9 months

How are EBCDIC data, packed-decimal fields, and RPG/COBOL rating tariffs extracted cleanly?

AS400 / IBM i databases store character strings in EBCDIC and pack currency, dates, and weights into binary COMP-3 packed-decimal fields, while decades of customer-specific rating exceptions live inside RPG or COBOL source programs rather than database tables. Standard CSV exports corrupt signs, truncate precision, and miss the rate logic that actually runs your billing.

  • EBCDIC & Packed-Decimal (COMP-3) Decoding: We extract physical files via native IBM i journaling, ODBC/DRDA, or binary record parsers using DDS layouts, transcoding EBCDIC (CCSID 37) to UTF-8 and unpacking COMP-3 and zoned-decimal nibbles with strict sign-byte verification so AR/AP balances and settlement deductions never drift by a penny.
  • RPG / COBOL Rating & Tariff Extraction: Customer minimums, lane overrides, fuel surcharge peg formulas, accessorial triggers, and owner-operator settlement splits are often hard-coded in RPG/400, ILE RPG, or COBOL calculation subroutines. We audit the source members alongside historical invoice line items to translate every active rule into deterministic target TMS tariff matrices.
  • 3 to 9 Month Timeline Benchmarks: Single-terminal fleets with standardized tariffs typically complete extraction, cleansing, and cutover in 3 to 4 months; multi-terminal carriers with heavy EDI 204/214/210 partner testing average 5 to 7 months; and complex fleets with decades of custom RPG rating and hybrid GL bridges benchmark at 7 to 9 months.

Why run a 2 to 4 week parallel pilot and a Monday Morning Failure / Rollback Plan?

A 2 to 4 week parallel pilot proves invoice-to-invoice and settlement-to-settlement parity on live freight before you retire the AS400, while a written Monday Morning Failure / Rollback Plan guarantees dispatchers and drivers never face a Monday morning operational halt if an edge case appears after cutover.

  • 2 to 4 Week Parallel Pilot: During the final month before cutover, representative orders, EDI tenders, fuel surcharges, and driver settlements are processed simultaneously in the IBM i system and the target TMS. Every variance above $0.01 is traced to its root cause, bad DDS mapping, missing accessorial code, or RPG rounding rule, and resolved before go-live authorization.
  • Sunday 2:00 PM Go/No-Go Gate: Cutover weekend runs on a minute-by-minute runbook. If master data reconciliation, EDI 997 acknowledgments, or ELD dispatch feeds fail verification by Sunday 2:00 PM, leadership triggers the fallback before Monday freight moves.
  • Monday Morning Failure / Rollback Plan: The legacy IBM i LPAR remains warm and snapshot-protected with pre-cutover journals intact. Written cutback thresholds define exactly when to pause new-system dispatch, re-point EDI/AS2 endpoints back to the AS400, and capture any weekend loads without losing billing or HOS continuity.

After go-live: using more of what you bought

Go-live is the beginning, not the end. Most carriers start with the core: order entry, dispatch, billing and settlements. Once the team is comfortable, there's usually much more value in the system. As we told clients on our original site, "There is a lot to the software, and you have more there than you know." Carriers often keep us on for ongoing training and consulting as they implement new parts of their software after go-live. We help you phase in the next layer, whether that's imaging, mobile communications, repair and maintenance, deeper reporting or new EDI partners, with the same care as the first.

What you get

DeliverableWhat it gives you
Readiness assessmentKnown risks and gaps before the project starts
Configured systemTariffs, pay plans, accessorials and documents set up for how you operate
Reconciled data conversionClean master data and open balances that tie out to the old system
Tested interfacesELD, EDI, fuel card, imaging and accounting connections verified before go-live
Trained staff & super-usersA team that knows the system on day one, with internal experts to carry it forward
Cutover & go-live supportA written runbook and an experienced person on the floor

Who this is for

Truckload and LTL carriers, brokerages and 3PLs, intermodal and drayage operators, and private fleets that are:

  • Implementing a TMS for the first time
  • Replacing an older system and converting years of data
  • Stuck waiting for a vendor implementation slot
  • Mid-implementation and worried about go-live
  • Live on a new system but using only part of it

Frequently asked questions

The vendor's implementation date is months away. Can you help us start sooner?

Often, yes. Software vendors have limited implementation resources. We can take on the installation, configuration and training parts of the project so you are not waiting in their queue, while coordinating closely with the vendor.

What data do you convert?

Typically customers, consignees and locations, rate tables and tariffs, fuel surcharge schedules, accessorial codes, equipment, drivers and pay plans, vendors and carriers, plus open AR and AP and whatever history you need for reporting. We map, cleanse, test-load and reconcile before cutover.

Do you train our staff?

Yes. Training is role-based: customer service and order entry, dispatch and planning, billing, payroll and settlements, safety and maintenance, and accounting. It can be on site or remote, and we train on your own data and scenarios.

Are you on site for go-live?

Usually, yes. Go-live week is when an experienced person on the floor matters most. We work alongside dispatch, billing and payroll, fix issues as they surface, and coordinate with the vendor's support team.

Do we have to be implementing Exspeedite for you to help?

No. Strong Tower Consulting is independent. Our implementation support never requires buying our sister company's software. We help carriers implement the system they have chosen.

How do carriers migrate off a legacy AS400 or IBM i TMS without losing rating logic?

Carriers migrate off AS400 or IBM i systems by choosing one of four paths, Rehost, Re-platform, SaaS Re-architect, or Hybrid, decoding EBCDIC and packed-decimal (COMP-3) DB2 files, extracting customer rating and settlement logic from RPG or COBOL source programs, and proving parity in a 2 to 4 week parallel pilot before weekend cutover.

How long does a legacy AS400 / IBM i TMS migration take?

Typical AS400 or IBM i TMS migrations benchmark at 3 to 9 months end to end: 3 to 4 months for a single-terminal SaaS cutover with clean tariffs, 5 to 7 months for multi-terminal EDI-intensive fleets, and 7 to 9 months when complex RPG or COBOL rating engines require custom extraction and a hybrid transition.

What is a Monday Morning Failure / Rollback Plan in a TMS cutover?

A Monday Morning Failure / Rollback Plan is a written fallback protocol with a Sunday 2:00 PM Go/No-Go gate, a frozen IBM i snapshot with journaled transactions, and explicit cutback triggers so dispatch and billing can revert cleanly to the legacy system if rating, EDI, or settlement checks fail on launch morning.

Start Here

Go live with confidence.

A readiness review from Strong Tower shows you where your implementation stands and what it will take to get to a clean go-live.

Related advisory and implementation guidance

Connect this topic with the related consulting scope and operating guidance.