Skip to content

Example: Integrate a non-supported asset

Here you will find an example of how you can integrate an asset that is not yet supported by octoplant.

This example consists of an automation device with the project files Configuration.ini, Database.bin and Log.txt.

Figure: Project data example device

Select or create a dedicated component type

To begin with, the project data of the automation device to be backed up must be analyzed. It is important to find out which files are to be backed up. If a comparison of the files is desired, the appropriate comparator must then be identified.

If there is no suitable component type for the project files, create a dedicated component type in the Component type editor module of the AdminClient.

Figure: Component type T-5000

Select a comparator

All files that are to be compared but cannot be assigned to a universal comparator, such as ASCII or Excel, can be compared with the Binary comparator.

For the example project, the Binary comparator is explicitly specified for all unknown files (*.*). This
means that changes to a file that is not precisely defined can still be tracked.

For example, the file Database.bin is compared with the Binary comparator, but also files that are added at a later date and whose format is not yet known.

The comparison shows following results:

  • Two new lines were added within the Log.txt file.

    Figure: Comparison Log.txt file

  • There was a change in the file Database.bin.

    Figure: Comparison Database.bin file

Create a component and integrate project data

  1. Create a new component in the UserClient and assign the newly created component type.

  2. Create a base version and execute a Check-In.

Figure: Creating new component T-5000

Your project data is now integrated and users can edit the version locally via Check-Out.

Configure automatic backups of your asset

To back up the data of the your asset at regular intervals, create a job in the AdminClient.

  1. Ensure that the chosen upload type is compatible with the asset's data format and access method.

    For the example project, data is stored manually by the users under the same path (network/local), so that the suitable upload type is Network (UNC).

    Figure: Job configuration for component T-5000

  2. Familiarize yourself with how the configuration looks for each upload type to ensure you can set it up correctly.

  3. Verify that the network settings allow for communication between the octoplant server and the asset.

  4. Before finalizing the job, conduct a test upload to verify that all configurations are correct and that data can be successfully retrieved from the asset.

Related topics