Configuration Management¶

The DataPortal enables remote configuration updates of communication units (configuration over the air - COTA). Configuration updates are managed using configuration bundles, which allow version control and provide transparency regarding the installation status of selected machines.

Configuration bundles are visible only within the respective tenant organization (typically the OEM). Users belonging to the tenant, including its child organizations, can view and assign configuration bundles according to their Permission Set. Users outside of the tenant cannot see or assign configuration bundles. See Tenant for further details.

A remote configuration update of a communication unit consists of two steps:

In the first step, the Create Configuration Bundle procedure must be completed.
In the second step, the transfer of the configuration update to the device must be triggered, either by selecting one or more CUs for the Configuration Update/Mass COTA or by selecting the configuration bundle first, see Select Configuration Bundle for Update.

Figure 1: Communication unit Configuration

Requirements¶

In order to have the configuration update option available within the DataPortal, the following preconditions must be fulfilled:

Feature	Permission Set Name	Level
Upload/Deletion of Configuration into the Configuration Management Repository	Models	Admin
Triggering or Cancelling of Remote Configuration, either of	Models	Admin
Machines	Admin

Feature Name	Status
Configuration Management	ON

Software Update Use Cases¶

A: As telematics OEM manager with Models Admin permission set I need to be able to manage configurations and configuration bundles to provide them for updating existing machines or configuring new machines.

Permission Set	Level	Description
Models	Admin	Is allowed to manage configurations and bundles.
Models	Admin	Is allowed to download configuration files.

B: As telematics OEM manager with Models Admin permission set I need to be able to start/stop COTA/FOTA requests for machines and models so I can test and rollout fleet wide software updates.

Permission Set	Level	Description
Models	Admin	Is allowed to view configurations and bundles.
Models	Admin	Is allowed to view current and historical COTA requests of a machine.
Models	Admin	Is allowed to create a COTA request for a machine.
Models	Admin	Is allowed to view current and historical FOTA requests of a machine.
Models	Admin	Is allowed to create a FOTA request for a machine.

C: As an OEM end-of-line worker with Machines Admin permission set I need to be able to start/stop COTA/FOTA requests for machines to be able to install the latest software version into a new machine.

Permission Set	Level	Description
Machines	Admin	Is not allowed to manage configurations and bundles.
Machines	Admin	Is not allowed to download configuration files.
Machines	Admin	Is allowed to view configurations and bundles.
Machines	Admin	Is allowed to view current and historical COTA requests of a machine.
Machines	Admin	Is allowed to create a COTA request for a machine.
Machines	Admin	Is allowed to view current and historical FOTA requests of a machine.
Machines	Admin	Is allowed to create a FOTA request for a machine.

Create Configuration Bundle¶

Note

The configuration management in the DataPortal requires a combination of a .dod* and its corresponding .bin files. This will be considered as a configuration bundle. A .bin file can be created when having the new *.dod open with the Proemion Configurator software.

Open Settings > Communication Units Management > Configuration Bundles.

✓ The table with the available configuration bundles opens.
Click on the + icon in the top right corner to add a new configuration.

Figure 2: Add new configuration
In the NEW CONFIGURATION dialog click on Upload .dod file button to select the new *.dod file.

Figure 3: Upload .dod file

Note

The uploaded .dod file will be validated for consistency. In case of an error, the upload will be cancelled and a specific error message will be displayed. To detect the root cause of the error and resolve it, contact the Service and Support.
Click on Upload .bin file button to select the corresponding *.bin file.

Figure 4: Upload .bin file

Note

The product code and the device configuration version string must be same in both the .dod* and .bin* files.

The New Configuration section opens.

Figure 5: Upload Details
Regarding the Versions bundle, you may choose Add to existing or Create new files.
Enter a proper Bundle Name.
Select the Organization.
Click on Save.

✓ After saving, the Configuration Overview with the available configuration bundles opens and the new configuration bundle is available now.

Figure 6: Configuration overview with new bundle

Select Configuration Bundle for Update¶

Open Settings > Communication Units Management > Configuration bundles.
Select the desired Configuration bundle to open it.
By the end of the line of the desired configuration version, open the context-menu via the 3-dots.
Select Install on machines.

Note

When there are no eligible machines for this update, the Install on machines option will not be displayed.

The Select machines page opens in the Firmware and Configuration Updates menu.
Choose all or specific machines for the configuration update and Continue. The Configuration update page opens. In case there are conflicts for the selected machines, the information is displayed here, too:

Figure 7: Configuration update information page

You can then proceed with the firmware update for all machines or only those without a pending update.
Click Update to start the update of the firmware on the selected devices. ✓ The configuration update runs in the background.

Delete Configuration Bundle¶

In case that an already uploaded version of a configuration bundle needs to be deleted, go to Administration > Communication unit Configuration, open the specific bundle and delete the versions which are not required anymore.

Note

Consider that only versions without machine usage can be deleted.

Figure 8: Delete Version of Config Bundle