OTM Domains, Standard Schema and Data Dictionary

Domains:

OTM Data is organized into domains. Each domain is like grouping of data / business transactions based on the different business units with in the same organization.

If there is a corporation with logistics requirements across various business units like “Merchandise Shipping”, “Food and Beverages”, etc - you typically create one domain for each of these business units so that users and their roles can be tied to each business unit. User/role tied to a particular domain can only access data for their specific domain/business unit. Also advantage with domains is that customization specific to a business unit can be better controlled/maintained. For example, OTM Agents(workflows) with custom code can be developed specific to each domain so they they trigger only for transactions within that domain.

01 - Domain, Items, Locations, and Equipment

Note: These posts are numbered to cover a typical end to end transaction flow that happens in OTM at a very high level.

01 - Domain, Items, Locations, and Equipment

02 - Itinerary

03 - Service Provider and Rates

04 - Business Numbers, Planning Parameter

05 - Bulk Plan

06 - Tender process

07 - Invoicing

08 - Voucher Allocation

Below is a typical OTM end to end flow in it’s most simple/vanilla usage. Readers can explore more on each of the below topics and use this as starting point to understand basic OTM configurations using OTM Help documentation.