These posts cover OTM’s underlying data structures — the database tables, GID columns, domain schema, and object relationships that sit behind every screen and integration. They are reference material, not step-by-step guides.

How to use this section: Skim through these posts now to build awareness of how OTM organises its data. You do not need to memorise them. Once you have completed the End-to-End Basic Configs series and started working on integrations or automation, come back here — you will find these posts significantly easier to absorb when you already have hands-on context for the objects they describe.

Domains, Standard Schema and Data Dictionary

OTM organises all of its data using a domain model. Understanding domains, the database schema, and how business objects are identified is foundational for anyone working with OTM data — whether you are building integrations, writing reports, or …

Order Management Data Structure

OTM models order management across three levels: the Purchase Order (what was ordered), the Order Release (a confirmed booking for movement), and Order Movements (the planned legs of that movement). Understanding this hierarchy and the underlying tables is …

Shipment Management Data Structure

A shipment in OTM consists of one or more Equipment records (containers or trailers), Shipment Ship Units loaded into each equipment, and Shipment Ship Unit Lines that link back to the original Order Release lines. Understanding this structure is essential …

Contract & Rate Management Data Structure

OTM models carrier contracting across five layers: Service Provider (who moves the freight), Rate Service (transit time commitments), Rate Distance (how mileage is calculated), Rate Offering (the contract), and Rate Records (the actual cost lanes). …

Business Process Automation Data Structure

The Business Process Automation (BPA) module handles the technical configuration layer of OTM — workflows, notifications, outbound integrations, reports, and transmission logging. The tables below are useful when troubleshooting agent behaviour, auditing …