20 Use External Storage Options for Long-Term Data Availability and Analysis

You can choose to use one of the external storage options, namely Oracle Autonomous Database or OCI Object Storage, to safely and cost-effectively store your IoT sensor and analytics data for long-term persistence.

The application can use your external storage to store raw or aggregated sensor attribute data, and data related to analytics artifacts, such as metrics. You can also store your rule incidents. In addition, you can use the historical data for visualization and analysis in external and third-party applications.

You can use the rich querying functionality in Oracle Autonomous Database, or chart and analyze the stored data in external applications, such as Oracle Analytics Cloud. For example, you can use analysis, projects, and dashboards in Analytics Cloud to find the answers that you need from key IoT data displayed in graphical formats. You can use applications such as Oracle Visual Builder to create dashboards and mashups.

Use OCI Object Storage to Store Historical IoT Data

The Oracle Cloud Infrastructure (OCI) Object Storage service is an internet-scale, high-performance storage platform that offers reliable and cost-efficient data durability. If you have a subscription for OCI Object Storage, you can use it to store your IoT sensor and analytics data for long-term persistence.

You can learn more about OCI Object Storage here:

• Overview of Object Storage
• Get Started with Object Storage

Use the following steps to add and configure your external OCI Object Storage:

1. Add an Oracle Cloud Account
2. Connect to an OCI Object Storage Instance
3. Add and Configure Your External OCI Object Storage Integration

Add an Oracle Cloud Account

Use the Settings > Integrations page in your IoT application to configure an Oracle Cloud account. This Oracle Cloud account is used when specifying integration settings, such as OCI Object Storage settings.

1. In your IoT application, click Menu (), and then click Settings.
2. Click Integrations.
3. Click Add to add a new integration.
4. In the Add Integration dialog, select Oracle Cloud Account and click Add.
   Tip: You can also search for an integration name in the list.
   
   

   

   
   
   Oracle Cloud Account integration gets added to the Integrations page.
5. Under Oracle Cloud Account, add your cloud account details:
   1. Enter your Tenant OCID.
      The tenancy details are available from the Oracle Cloud Infrastructure Console. You need to log in to your Oracle Cloud Infrastructure Console. From the Profile menu, click Tenancy: <YourTenancyName>.
      The tenancy OCID is shown under Tenancy Information. Click Copy to copy it to your clipboard.
      
      

      

      
      
      Paste this value under Tenant OCID in your IoT application.
   2. Enter the User OCID.
      The user details are available from the Oracle Cloud Infrastructure Console. You need to log in to your Oracle Cloud Infrastructure Console. From the Profile menu, click User Settings.

      The user OCID is shown under User Information. Click Copy to copy it to your clipboard.

      Paste this value under User OCID in your IoT application.
   3. Under Public Key, click Generate.
   4. Click Close.
6. Set the public key in OCI Object Storage.
   1. On the Settings>Integration page of your IoT application, under Oracle Cloud Account, click Copy against Public Key to copy the public key that you generated earlier.
   2. Log in to your Oracle Cloud Infrastructure Console.
   3. Under the Profile menu, click User Settings.
   4. Click API Keys under Resources.
   5. Click Add Public Key.
      Note: If three public keys are already listed under API Keys, you have to first delete one public key. An OCI Object Storage service user can't have more than three public keys.
   6. Select Paste Public Keys and paste the key that you copied from your IoT application.
   7. Click Add.
      The fingerprint for the added public key appears under API Keys. The fingerprint should be the same as that displayed on the Settings page of your IoT application.

Connect to an OCI Object Storage Instance

Use the Integrations page in your IoT application to configure OCI Object Storage connection details and to enable Object Storage.

Before configuring the OCI Object Storage connection, you should have already added your Oracle Cloud account on the Settings page.

1. In your IoT application, click Menu (), and then click Settings.
2. Click Integrations.
3. Click Add to add a new integration.
4. In the Add Integration dialog, select Oracle Object Storage Service and click Add.
   Tip: You can also search for an integration name in the list.
   Oracle Object Storage integration gets added to the Integrations page.
5. On the Integrations page, under Object Storage Service, click Connect.
6. In the Oracle Object Storage dialog, provide your object storage connection details.
   1. Enter the Storage URL for your OCI Object Storage.
      For example, https://objectstorage.us-phoenix-1.oraclecloud.com.
   2. Enter the object storage Namespace for your tenancy.
      You can find the object storage namespace in your Oracle Cloud Infrastructure Console. You need to log in to your Oracle Cloud Infrastructure Console. From the Profile menu, click Tenancy: <YourTenancyName>.
   3. Enter the Default Bucket name that stores the data.
      The bucket name must already exist in your OCI Object Storage instance and must be public.
   4. Click Verify Connectivity to verify the connection details and bucket name.
   5. Click Save to save the OCI Object Storage connection details.
7. To enable the connection on the Integrations page, click Edit Configuration under Oracle Object Storage.
8. Toggle the Integration Status switch to ON, and click Save.

Add and Configure Your External OCI Object Storage Integration

To start storing IoT historical data in your OCI Object Storage, add and configure a new integration for External Data Storage (Oracle Object Storage).

Note:

You should have already added an Oracle Cloud account and specified the connection settings for your OCI Object Storage instance.

1. In your IoT application, click Menu (), and then click Settings.
2. Click Integrations.
3. Click Add to add a new integration.
4. In the Add Integration dialog, select External Data Storage (Oracle Object Storage) and click Add.
   Tip: You can also search for an integration name in the list.
   
   

   

   
   

   Note:

   You can only have one external data storage integration at a time. So, you cannot add both Oracle Autonomous Database and Oracle Object Storage integrations at the same time. If you need to switch from Oracle Autonomous Database integration to Oracle Object Storage, you should first remove the Oracle Autonomous Database integration from the Integrations page.
   The External Data Storage (Oracle Object Storage) integration gets added to the Integrations page.
5. On the Integrations page, under External Data Storage (Oracle Object Storage), click Edit Configuration.
   1. Optionally enter a File Prefix.
      Your IoT application prefixes the specified File Prefix to the file names that it stores in OCI Object Storage. This helps with easy identification of files.
   2. The Default Bucket is pre-populated with the bucket that you have used in your Object Storage connection settings.
   3. Optionally change the Export Interval if you want your application to write more frequently to OCI Object Storage.
      The default data export interval is 4 Hours.
   4. Select the IoT data that you wish to store externally:

      Note:

      For Fleet Monitoring, only Attributes, Metrics, and Incidents are applicable.

      • Attributes: You can choose to export all raw sensor attribute data. Alternatively, you can choose to export only aggregated attribute data, which exports aggregates, such as Average, Maximum, and Minimum values of your attribute values. Under Attributes Granularity Level, select Aggregated to export only aggregated attribute data. Under Attributes Granularity Level Interval , specify the aggregation interval. This determines the frequency at which the aggregated values are calculated.

        If you select None (raw data), then all raw sensor data is exported.

      • Metrics: Select to export metric data corresponding to system metrics and computed metrics.

      • Anomalies: Select to export anomaly data.

      • Predictions: Select to export prediction data.

      • Trends: Select to export data related to trends.

      • Incidents: Select to export your rule incidents.
      • Warnings:Select to export your rule warnings.
   5. Toggle the Integration Status switch to Enabled.
6. Click Save to save your configuration settings.

Use Oracle Autonomous Database to Store Historical IoT Data

Oracle Autonomous Database runs on Oracle Cloud Infrastructure and provides workload-optimized cloud services for transaction processing and data warehousing. If you have a subscription for Oracle Autonomous Database, you can use it to store your IoT sensor and analytics data for long-term persistence.

You can choose either an Oracle Autonomous Transaction Processing database , or an Oracle Autonomous Data Warehouse database to externally store your IoT data.

You can learn more about Oracle Autonomous Database options here:

• Oracle Autonomous Database Solutions
• Getting Started with Autonomous Transaction Processing
• Getting Started with Autonomous Data Warehouse

Use the following steps to add and configure your external Oracle Autonomous Database storage:

1. Add an Oracle Autonomous Database Integration
2. Enable and Configure the Oracle Autonomous Database Integration

Add an Oracle Autonomous Database Integration

To start storing IoT historical data in an Oracle Autonomous Database, add and configure a new integration for External Data Storage (Oracle Autonomous Database).

1. In your IoT application, click Menu (), and then click Settings.
2. Click Integrations.
3. Click Add to add a new integration.
4. In the Add Integration dialog, select External Data Storage (Oracle Autonomous Database) and click Add.
   Tip: You can also search for an integration name in the list.
   
   

   

   
   

   Note:

   You can only have one external data storage integration at a time. So, you cannot add both Oracle Autonomous Database and Oracle Object Storage integrations at the same time. If you need to switch from Oracle Object Storage integration to Oracle Autonomous Database, you should first remove the Oracle Object Storage integration from the Integrations page.
   The External Data Storage (Oracle Autonomous Database) integration gets added to the Integrations page.
5. On the Integrations page, under External Data Storage (Oracle Autonomous Database), click Connect to specify the connection details.
   1. In the External Data Storage Connection dialog, click Upload Wallet Zip File to upload the wallet required to securely connect to your database.
      Oracle client credentials (wallet files) are downloaded from Oracle Autonomous Database by a service administrator. If you are not the database administrator, your administrator should provide you with the client credentials. The wallet file for the ATP/ADW database can be downloaded from the ATP/ADW service console.
      After you upload the wallet file, the application verifies the wallet and prompts you for the database login credentials.
   2. Enter the User Name and Password used to log into the database.
   3. Select the Service Name for the database.
      The list of service name options is retrieved from the wallet that you uploaded earlier.
   4. Click Verify Connectivity to verify connectivity to your Oracle Autonomous Database instance.
      
      

      

      
      
      The Save button is enabled after successful verification of the connection credentials.
6. Click Save to save your Oracle Autonomous Database connection settings.

Enable and Configure the Oracle Autonomous Database Integration

To start storing IoT historical data in your Oracle Autonomous Database, enable and configure the integration for External Data Storage (Oracle Autonomous Database).

1. In your IoT application, click Menu (), and then click Settings.
2. Click Integrations.
3. Under External Data Storage (Oracle Autonomous Database), click Edit Configuration.
   1. Optionally enter a Table Prefix.
      Your IoT application prefixes the specified Table Prefix to the table names that it creates in Oracle Autonomous Database. This helps with easy identification of tables.
   2. Optionally change the Export Interval if you want your application to write more frequently to Oracle Autonomous Database.
      The default data export interval is 4 Hours.
   3. Select the IoT data that you wish to store externally:

      Note:

      For Fleet Monitoring, only Attributes, Metrics, and Incidents are applicable.

      • Attributes: You can choose to export all raw sensor attribute data. Alternatively, you can choose to export only aggregated attribute data, which exports aggregates, such as Average, Maximum, and Minimum values of your attribute values. Under Attributes Granularity Level, select Aggregated to export only aggregated attribute data. Under Attributes Granularity Level Interval , specify the aggregation interval. This determines the frequency at which the aggregated values are calculated.

        If you select None (raw data), then all raw sensor data is exported.

      • Metrics: Select to export metric data corresponding to system metrics and computed metrics.

      • Anomalies: Select to export anomaly data.

      • Predictions: Select to export prediction data.

      • Trends: Select to export data related to trends.

      • Incidents: Select to export your rule incidents.
      • Warnings:Select to export your rule warnings.
   4. Toggle the Integration Status switch to Enabled.
4. Click Save to save your configuration settings.

Use Oracle Analytics Cloud to Chart and Analyze Externally Stored Data

You can chart and analyze the stored data in external applications, such as Oracle Analytics Cloud. For example, you can use analyses, projects, and dashboards in Analytics Cloud to find the answers that you need from key IoT data displayed in graphical formats.

Understand the Format of Your Externalized IoT Data

Learn the format in which your IoT sensor and analytics data is stored in an external store.

The IoT data that is externalized depends on the options that you choose to export while adding and configuring your external storage such as Oracle Autonomous Database or OCI Object Storage. In addition to externalizing data about entities in your application, you can choose to externalize IoT data for Metrics, Attributes, and Incidents.

The underlying schema for the externalized data remains the same irrespective of whether you use Oracle Autonomous Database or OCI Object Storage. In the case of Oracle Autonomous Database, externalized data is stored in tables and for OCI Object Storage, data is stored in CSV files. The rest of this topic is explained based on OCI Object Storage.

There are two types of externalized data:

• Data of all entities in your application and the schema of the IoT data.
  This data is exported to the following set of CSV files that are explained later in this topic:

  • File_Prefix_ENTITY_TYPES
  • File_Prefix_ENTITY_TYPE_ATTRIBUTES
  • File_Prefix_ENTITIES
  • File_Prefix_ENTITY_ATTRIBUTES
  • File_Prefix_ANALYTICS

  These CSV files are created and present in the ORG_NAME > Fleet Monitoring folder, where ORG_NAME represents the organization under which the entities are present in your application.

  In the preceding CSV files list, File_Prefix is the prefix that you specified in the File Prefix field while adding and configuring your OCI Object Storage. When you externalize data, the IoT application prefixes the specified File Prefix to the file names that it stores in OCI Object Storage. This helps with easy identification of files.

  Note that if you are using Oracle Autonomous Database, then data is exported into tables with the same naming convention as that of the CSV files. The only difference is that File_Prefix is replaced with Table_Prefixwhich is the prefix that you specified in the Table Prefix field while adding and configuring your Oracle Autonomous Database for externalization.

  The following are the entities for which data is exported when an externalization job is run:

  • Vehicles
  • Drivers
  • Trips
  • Shipments
  • Stops
  • Ship orders
  • Equipments
  • Ship units
  • Ship items

  Each time an externalization job is run, all the entities and corresponding data in the previously listed CSV files are overwritten. In the case of Trips and Shipments entities, the ones that are in running status are externalized to one of the relevant CSV files listed earlier and the ones that are in Completed status are externalized to timestamp-based CSV files that are explained later in this topic. This is illustrated by the following example:

  Suppose the externalize job runs every one hour. When the job runs at 4 PM, all trips/ shipments and their stops, ship orders, equipments, ship units, ship items completed between 3 PM and 4 PM are included in the File_Prefix_ENTITIES_timestamp.csv file located in the ORG_NAME > Fleet Monitoring > Year > Month > Date > entities folder, and their respective attributes are included in the File_Prefix_ENTITY_ATTRIBUTES_timestamp.csv file located in the ORG_NAME > Fleet Monitoring > Year > Month > Date > entitiesAttributes folder. Any running trips and the corresponding trip attributes including ship orders, equipments, ship units, and ship items are included in the File_Prefix_ENTITIES.csv and File_Prefix_ENTITY_ATTRIBUTES.csv files, respectively.

• IoT data of attributes, metrics, and incidents.

  These files are created based on the IoT data that you chose to externalize while adding and configuring your external store. The files are located in a set of time series subfolders under the ORG_NAME > Fleet Monitoring folder. The following is the list of files:

  • File_Prefix_ATTRIBUTE_VALUES_timestamp.csv and File_Prefix_AGG_ATTRIBUTE_VALUES_timestamp.csv: Depending on whether you chose to store raw attribute data or aggregated attribute data, the File_Prefix_ATTRIBUTE_VALUES_timestamp.csv or File_Prefix_AGG_ATTRIBUTE_VALUES_timestamp.csv file is created, respectively.

    While configuring your external store, if you selected to export only raw data (selected the None (raw data) option), then the File_Prefix_ATTRIBUTE_VALUES_timestamp.csv file is created. This file contains all raw sensor attribute data and is located in the ORG_NAME > Fleet Monitoring > Year > Month > Date > attributeValues folder.

    If you selected to export only aggregated attribute data (selected the Aggregated option), then the File_Prefix_AGG_ATTRIBUTE_VALUES_timestamp.csv file is created. This file is located in the ORG_NAME > Fleet Monitoring > Year > Month > Date > attributeValues folder.

    The following image shows a sample File_Prefix_ATTRIBUTE_VALUES_timestamp.csv file extract:

    
    
    
    
    

    The following image shows a sample File_Prefix_AGG_ATTRIBUTE_VALUES_timestamp.csv file extract:

    
    
    
    
    

  • File_Prefix_METRIC_VALUES_Timestamp.csv: This file contains all your metric data corresponding to system metrics and computed metrics. This file is located in the ORG_NAME > Fleet Monitoring > Year > Month > Date > metricValues folder.

    The following image shows a sample File_Prefix_METRIC_VALUES_timestamp.csv file extract:

    
    
    
    
    

  • File_Prefix_INCIDENTS_Timestamp.csv: This file contains your rule incidents data and is located in the ORG_NAME > Fleet Monitoring > Year > Month > Date > incidents folder. This folder additionally contains the File_Prefix_INCIDENT_OCCURRENCESTimestamp.csv and File_Prefix_INCIDENT_COMMENTSTimestamp.csv files that contain information about every occurrence of an incident and incident progress comments, respectively.

    The following image shows a sample File_Prefix_INCIDENTS_timestamp.csv file extract:

    
    
    
    
    

    The following image shows a sample File_Prefix_INCIDENT_OCCURRENCES_timestamp.csv file extract:

    
    
    
    
    

    The following image shows a sample File_Prefix_INCIDENT_COMMENTS_timestamp.csv file extract:

    
    
    
    
    

  The following screenshot displays the folder structure for attributeValues with timestamp-based CSV files:

  
  
  
  
  

The File_Prefix_ENTITY_TYPES.csv and File_Prefix_ENTITY_TYPE_ATTRIBUTES.csv files contain schema of IoT data, whereas the File_Prefix_ENTITIES.csv, File_Prefix_ENTITY_ATTRIBUTES.csv, and File_Prefix_ANALYTICS.csv files contain the IoT data of all entities.

Schema Files

• File_Prefix_ENTITY_TYPES.csv: Describes the types of entities used in your application. These are vehicles, drivers, trips, shipments, stops, ship orders, equipments, ship units, and ship items. Except for vehicles, all other entities have only one type per organization. As you can have multiple vehicle types in your application, there can be corresponding multiple entries of vehicle types in the file.

  The following image shows a sample File_Prefix_ENTITY_TYPES.csv file extract:

  
  
  
  
  

• File_Prefix_ENTITY_TYPE_ATTRIBUTES.csv: Each entity type has several attributes associated with it. This CSV file has the definition for all the attributes associated with each of the entity types. Each attribute is in a separate row along with the associated fields. The ENTITY_TYPE_ID field indicates the entity type with which the particular attribute is associated. All entity types have a set of core attributes that are static, being built-in. The vehicle type can additionally have custom and sensor attributes that you might have defined in the application. The type of an attribute is accordingly indicated in the TYPE field as static, custom, or sensor.

  The following image shows a sample File_Prefix_ENTITY_TYPE_ATTRIBUTES.csv file extract:

  
  
  
  
  

IoT Data Files

• File_Prefix_ENTITIES.csv: Contains the basic data for all entity types. The basic data for an entity includes its name, entity type ID, Org ID, Parent ID, Status, State, and timestamp columns such as created, created by, and so on.

  The following image shows a sample File_Prefix_ENTITIES.csv file extract:

  
  
  
  
  
• File_Prefix_ENTITY_ATTRIBUTES.csv: Contains the attributes and their values for all entities. The entity to which each attribute belongs to can be determined from the ENTITY_ID column value. Each attribute value is represent by one row in the file and the values can be either in the STRING_VALUE, NUMBER_VALUE, DATE_VALUE, or BINARY_VALUE column, depending on the data type.

  The following image shows a sample File_Prefix_ENTITY_ATTRIBUTES.csv file extract:

  
  
  
  
  

• File_Prefix_ANALYTICS.csv: Contains the list of all custom or user-defined KPIs for vehicles, drivers, trips, shipments, ship orders, equipments, ship units, and ship items in your application.

  The following image shows a sample File_Prefix_ANALYTICS.csv file extract:

  
  
  
  
  

Core Attributes for Entities

Core attributes are attributes of entities present in the entity schema.

The following is the list of core attributes for every entity that is externalized:

Vehicle

• Category
• Driver Id
• Driver Name
• Make
• Model
• Registration Number
• Trip Id
• Trip Name
• Type Name
• Vin
• Year
• Years

Driver

• Login Id
• Trip Id
• Vehicle Id
• Vehicle Name

Trip

• Actual End Time
• Actual Start Time
• Asset Or Tracker Source
• Bill Of Lading
• Capacity Utilization
• Carrier Name
• Carrier Ref Num
• Commodities
• Completed Remark
• Cost
• Cost Currency
• Cost In USD
• Creation Source
• Delivered
• Domain Name
• Driver External Id
• Driver Id
• Driver Login Id
• Driver Name
• Earliest Start Time
• End Location
• Equipment Count
• Estimated Duration Seconds
• External Id
• Has Error
• Integration Id
• Integration Type
• Is Hazardous
• Is Temperature Controlled
• Latest Start Time
• Next Stop Index
• Planned Drive Distance
• Planned Drive Duration Seconds
• Planned End Time
• Planned Start Time
• Priority
• Service Mode
• Ship Order Count
• Ship Unit Count
• Start Location
• Status
• Stops Classification
• Stops Completed
• Toll Road
• Total Loaded Distance
• Total Loaded Distance In KM
• Total Loaded Distance UOM
• Total Planned Transit Duration
• Total Stops
• Total Unloaded Distance
• Total Unloaded Distance In KM
• Total Unloaded Distance UOM
• Total Volume
• Total Volume In CBM
• Total Volume UOM
• Total Weight
• Total Weight In KG
• Total Weight UOM
• Tracker Id For Third Party Carrier
• Trip Class
• Trip Distance
• Trip Length Classification
• Trip Type
• Vehicle Id
• Vehicle Name
• Vehicle Registration Number
• Vehicle Type
• Version

Shipment

• Carrier Id
• Carrier Name
• Completed Remark
• Cost
• Cost Currency
• Delivered
• Domain Name
• Driver External Id
• Driver Id
• Driver Login Id
• Earliest End Time
• Earliest Start Time
• End Time
• Equipment External Id
• Equipment Group Id
• Equipment Utilization
• External Id
• External Reference
• Latest Start Time
• Loaded Distance
• Next Stop Sequence
• Number Of Orders
• Number Of Ship Units
• Planned Drive Distance
• Planned Drive Duration
• Power Unit External Id
• Power Unit Id
• Power Unit Registration Number
• Shipper Id
• Shipper Name
• Start Time
• Stops Completed
• Toll Road
• Total Stops
• TPL Managed
• Tracker Status
• Tracking Id
• Transport Mode
• Trip Id
• Unloaded Distance
• Volume
• Volume Utilization
• Weight
• Weight Utilization

Stop

• Actual Arrival Time
• Actual Departure Time
• City
• Country
• Equipment Drop Count
• Equipment Pickup Count
• Estimated Arrival Time
• Estimated Departure Time
• Estimated Distance To Next Stop
• Estimated Time To Next Stop
• External Stop Sequence
• Facility Id
• Fence Id
• Inner Fence Arrival Time
• Inner Fence Departure Time
• Load Id
• Location Ref
• Planned Arrival Time
• Planned Departure Time
• Planned Stop Duration
• Postal Code
• Ship Unit Drop Count
• Ship Unit Pickup Count
• State
• Stop Duration
• Stop Number
• Stop Type
• Street
• Time Zone

Ship Order

• Trip Id
• Order Number
• Order Key
• Early Pickup Date
• Late Pickup Date
• Early Drop Date
• Late Drop Date
• Ship Unit Count
• Ship Item Count
• Special Instruction

Equipment

• Trip Id
• Trip Equipment Ref
• Equipment Number
• Equipment Type
• Pickup Stop Sequence
• Drop Stop Sequence
• Length In Metre
• Length
• Length UOM
• Max Volume In Cbm
• Max Volume
• Max Volume UOM
• Max Weight In Kg
• Max Weight
• Max Weight UOM
• Is Detached
• Is Linked
• Asset Or Tracker Source
• Alerts
• Open Incidents
• Is Hazardous
• Commodities
• Parent Entity Id
• Parent Entity Name
• Parent Entity Type
• Asset Id
• Asset Name
• Asset Type
• Asset External Id
• Custom Attributes
• Device Endpoint Ids
• Device Endpoint Names

Ship Unit

• Trip Id
• Ship Order Numbers
• Ship Unit Number
• Ship Unit Key
• Ship Unit Type
• Special Instruction
• Trip Equipment Ref
• Count
• Pickup Stop Sequence
• Drop Stop Sequence
• Volume In Cbm
• Volume
• Volume UOM
• Weight In Kg
• Weight
• Weight UOM
• Is Detached
• Is Linked
• Asset Or Tracker Source
• Alerts
• Open Incidents
• Is Hazardous
• Commodities
• Parent Entity Id
• Parent Entity Name
• Parent Entity Type
• Asset Id
• Asset Name
• Asset Type
• Asset External Id
• Custom Attributes
• Device Endpoint Ids
• Device Endpoint Names

Ship Item

• Trip Id
• Ship Order Number
• Ship Item Number
• Ship Item Key
• Ship Unit Number
• Special Instruction
• Trip Equipment Ref
• Quantity
• Pickup Stop Sequence
• Drop Stop Sequence
• Volume In Cbm
• Volume
• Volume UOM
• Weight In Kg
• Weight
• Weight UOM
• Is Detached
• Is Linked
• Asset Or Tracker Source
• Alerts
• Open Incidents
• Is Hazardous
• Commodities
• Parent Entity Id
• Parent Entity Name
• Parent Entity Type
• Asset Id
• Asset Name
• Asset Type
• Asset External Id
• Custom Attributes
• Device Endpoint Ids
• Device Endpoint Names