Device Framework

General

This page contains an overview of the Device Framework functionality in 3PL Dynamics - TMS - Road Transportation.

The 3PL TMS Device Interface Framework is introduced to streamline the process of managing and controlling telematics devices, Automatic Planning Systems and What's app Business. Typically, constructing a message for these systems involves gathering data from relational tables and supplementing it with specific information. When this process is hardcoded in codeunits, it introduces a significant challenge: any modification can lead to long turnaround times and create a dependency on development resources. This lack of agility is a major drawback, especially when timely adjustments are needed. To address this issue and enhance flexibility, the Device Framework has been introduced, alongside the 3PL Message Configuration. This framework empowers IT professionals by enabling them to configure and adjust message structures without needing to rely on developers. It promotes autonomy and allows for quicker adaptation to changing requirements, ultimately increasing efficiency.

Structure Device Framework

Device Framework Structure

Functionality

Process Flow Device Tasks

The follwing flow shows the outbound process.

Process Flow Device Task

Step 1. Trigger New Task Activity

A New Task Activity can be triggered by appling a functionset in a Status Change or a Step. Page: New Task Activity contains a functionset which can be applied for a new task.

Step 2. Resource Check

The system performs the following checks before proceeding:

Does the Trip contains a Resource?
Is Resource-Device linked to the Resource?
Is the Resource-Device active?

Step 3. Determinate Task Configuration

When a valid resource has been found the system will use the resource device information to find the applicable Device Task Configuration based on its associated field values: Device Code, Brand, and Model.

Step 4. Apply Table- and Criteria filters

On the Device Task Configuration filtervalues can be specified in the fields: Table Filter and Criteria Function Set. These fields determinate which Device Task Configuration is applicable.

Step 5. Create record on Device Task Outbound Log

If a Device Task Configuration is applicable a record is created in the Device Task Outbound Log with the status: NEW.

Step 6. Process Device Task Outbound Log

The field: Message Configuration Code on the Device Task Configuration determines what type of message and what data is to be processed in the Device Task Outbound Log.
Depending on the value of the field: Trigger Type on the Device Task Configuration the Device Task Outbound Log will either be processed directly, processed in the background(Directly-session) or manually. When the Device Task Outbound Log is processed the status will be changed in: SUCCEEDED.

Step 7. Process DI message

When processing the Device Task Outbound Log the associated DI Message, as configured via the Device Task Configuration, will be processed. When the processing of the DI Message is completed the status of theDI Message will be updated via the Device Task Outbound Log. The status will either be updated to: DI Proceessed or DI Failed. See?DI Message for more information on DI-Messages. From the page: DI-message list the content of the message can be viewed.

Step 8. Trigger TMS Events

After updating the status, TMS Events can be triggered. For example to update a status, change a department or to decouple a trip. See page: Event Function: Device Task Process Outbound for a list of TMS events applicable.

Proces Flow Device Activity Mappping

Device Activity Mapping Flow

Step 1. DI Message RCV-DEVICE-ACTIVITY

The 3PL Datahub function constantly checks for updates on the portal of the boardcomputers. When new messages are availble a message will be created based on the messagetype: RCV-DEVICE-ACTIVITY. This message can contain multiple activities from multiple Resource Devices.

Step 2. Job Queue 1 Map Device Activities

By running the Jobqueue - Task 1 the mapping of the messages will be excecuted.

Step 3. Device Check

The system performs the following checks before proceeding:

Does the message value: ExternalDeviceId match a fieldvalue: External Device Id of a Device?
Is this Device linked to an active Resource - Device?
Is this Resource Device linked to a Resource

Step 4. Determination Device Activity Configuration

Based on the values of the fields: Device Code, Brand and Model of the Resource Device the corresponding Device Activity Configuration will be determinated. If a Device Activity Configuration is determinated the process will be continued.

Step 5. Determination mapping line

Based on the value of the field: ExternalActivityType the corresponding mapping line of the Device Activity Configuration will be determinated. If a mapping line is found the message can be processed.

Step 6. Update status

When a Device Activity has been mapped without problems the status will be changed to: Mapping Succeeded. If the processing has failed the status will be set to: Mapping Failed.

Proces Flow Device Activity processing

Device Activity Processing Flow

Step 1. Job Queue 2 Process Device Activities

By running the Jobqueue - Task 2 the lines on the Tab: Processing of the Device Activities will be executed.

Step 2. Determinate Device Activity to be processed

The system will only process Device Activies with the status: Mapping Succeeded or Retry Process (Pending).

Step 3. Determination processing line

In step 4. of the Process flow Device Activity Mapping the Device Activity Configuration has been determinated on a Device Activity. Based on the filters in the fields: Condition Function and Table Filter on the tab: Processing of the Device Activity Configuration will be determinated which lines have to be processed.

Step 4. Execute functions processing line

The functions in the fields: Execute Function Set and Processing Function will be executed.

Step 5. Update status

When a Device Activity has been processed without problems the status will be changed to: Processing Succeeded. If the processing has failed the status will be set to: Processing Failed.

Settings

The following settings are applicable when using the Device Framework.

Setting	Description
Devices	A list of all Devices or applications integrated via the Device Framework.
Resource Devices	This page contains the link between a resource and the Device.
Device Task Configurations	This page contains the configuration of tasks(outbound).
Message Configuration	Functionality to configure messages.
Device Activity Configuration	This page contains the configuration of activities(inbound).

Table of Contents