Trimble TMW data (TMWSuite, TruckMate): what fleets can pull

What records sit in TMWSuite and TruckMate?#

TMWSuite and TruckMate hold the operating record of a carrier: what a customer ordered, how the freight moved, who hauled it, what happened at each stop, and what was billed and paid. Both are transportation management systems built for carriers, and both can retain many years of linked history if nobody purged it.

Exact table and module names differ by product, version and configuration, so treat the record map below as a guide to record families rather than a schema. Your TMW administrator or the vendor's documentation is the source for field-level detail.

Export routes, from reports to database access#

Export routes for TMW data range from built-in reports a dispatcher can run to direct database access that needs an administrator and sometimes the vendor. The right route depends on how much history you need and how the system is hosted.

Start with the BI copy if one exists. It usually sits outside the production system, so queries do not slow dispatch, and someone has already worked through the configuration quirks of your installation.

• 1Built-in reports and grid exports: quick and filtered, suited to samples, but often limited in columns and date range.
• 2Scheduled report exports: repeatable extracts for a defined period, useful for regular pulls.
• 3Existing BI or data warehouse feeds: many carriers already replicate TMW data for dashboards, and that copy may be the easiest source.
• 4Read-only database replica or restored backup: the fullest history, if the license and hosting arrangement allow direct access.
• 5Vendor APIs and integration tools: better for ongoing feeds than for one-time history pulls.
• 6Vendor or partner-assisted extraction: common during migrations, and sometimes the only option for hosted systems.

Hosted or on-premise: who controls the database?#

Database control depends on deployment: an on-premise TMW installation usually runs on servers your team administers, while a hosted or cloud deployment leaves the database with the vendor or a hosting partner. That difference decides whether IT can query history directly or must request an extract.

Check three documents before planning a pull: the software license, any hosting or managed services agreement, and the support agreement. Look for terms on database access, extraction methods, third-party access and data return at termination. Vendor ownership and support arrangements for transportation software change over time, so confirm current terms with your account team rather than relying on an old contract summary.

Keep the chain linked from order to settlement#

The chain from order to settlement is what makes TMW data useful, so join keys must survive the export. An order without its movements, or a movement without its stops and check calls, loses the sequence that shows how a load actually ran.

Export the identifiers that join each family: order number, movement or trip number, leg and stop identifiers, invoice number and settlement reference. Keep them even if they will be tokenized later; consistent tokens preserve the joins while hiding the original values.

Free-text fields deserve the same care. A dispatcher remark on a late load, a customer service note about a refused delivery or a billing comment explaining a detention charge often carries the reasoning behind an exception, which is the part of TMW history that AI teams studying logistics exceptions value most.

TMW export checklist#

A TMW export checklist keeps IT, operations and counsel aligned on scope before anyone runs a query against production or a replica.

• 1Confirm the product, version, deployment and who administers the database.
• 2Read the license, hosting and support terms on extraction and third-party access.
• 3List record families and the years of history still present.
• 4Identify the join keys for each family.
• 5Decide which fields are excluded outright, such as settlements and driver personal details.
• 6Choose the export route and run a small test pull.
• 7Check the test for completeness against a known report, such as monthly revenue by customer.
• 8Document the queries and keep the raw extract in your own secured storage.

Pull history before a migration or contract change#

History should be pulled before a TMS migration or contract change, because migrations usually move open orders, active customers and master data rather than years of closed loads. Once the old system is switched off or a hosting contract ends, recovering history can be slow, costly or impossible.

Ask the migration team to include a full historical extract as a named deliverable, with join keys intact and stored in your own environment. That extract serves internal analytics, retention obligations and any later licensing review, whatever the new system keeps.

Illustrative: a refrigerated carrier pulls TMWSuite history before cutover#

Illustrative: a fictional regional refrigerated carrier has run TMWSuite on-premise for many years and plans to move to a new TMS. The CIO wants a complete history before cutover, both for retention and to assess whether its exception records could be licensed.

IT restores a recent backup to a separate server, confirms with the vendor that the license permits this use, and extracts orders, movements, stops, check calls, accessorials and dispatcher remarks with all keys. Driver settlements are excluded in the query itself. A test against monthly revenue reports confirms completeness. The extract goes to an encrypted bucket in the carrier's own cloud account, and the CIO lists temperature excursion and late-delivery exceptions as candidate record families in the data inventory.

How SourceX approaches TMW records#

SourceX approaches TMW records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check uses metadata only, such as the TMW product, deployment, years of history and record families, and no extract is requested at that stage.

If the carrier proceeds, the rights step reviews customer contracts and software terms, preparation pseudonymizes drivers and customers and excludes settlements, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization. Large histories stay in the carrier's own storage or ship on encrypted drives.