> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/connectivity/data-forwarding/unigis.md).

# Unigis

The **Unigis** protocol is a vehicle location data forwarding protocol between Navixy and a TMS platform developed by Unigis. The most frequent use cases relate to real-time collection of GPS tracking and vehicle Telematics data by logistics departments of large manufacturing and retail chain companies. Most of these companies are located in the US, Mexico, Colombia, Chile, Argentina, Brazil and Spain.

*Protocol Category: Enterprise compliance*

### Table of contents

1. [What is Unigis?](#what-is-unigis)
2. [Technical information about Unigis](#tech-info-unigis)
3. [Unigis Configuration](#unigis-config)
4. [Setting up](#setting-up)
5. [Managing](#managing)
6. [Troubleshooting](#troubleshooting)

### What is Unigis?

Through the Unigis data forwarding protocol, fleet GPS tracking data is streamlined across multiple servers, allowing data retransmission between Navixy and Unigis partners.

Using the Unigis protocol, users can integrate with self-service chains and/or suppliers of products and services within the Unigis network, such as Walmart, Home Depot, and Kimberly-Clark. Fleet data can be transmitted between all parties without requiring access to Navixy's platform.

### Unigis general technical information

The Unigis protocol uses SOAP to send XML data from tracking devices to Unigis over HTTP as part of the OSI application layer. Data is pushed from the Navixy platform to Unigis every 5 minutes.

Data that’s sent to Unigis:

* Date and time
* Longitude
* Latitude
* Altitude
* Speed
* Inputs events
* Door Open
* Panic Button
* Engine Off
* Theft
* External ID (License Plate)

Format: ASCII

### Unigis configuration

#### Setting up

To initiate data forwarding using the Unigis protocol from Navixy, you need the following parameters:

<table><thead><tr><th width="281.6363525390625">Parameter</th><th>Explanation</th></tr></thead><tbody><tr><td>Destination server address and port</td><td>URL of endpoint and port that is used by Ungis TMS.<br><br>Most commonly:<br><br>* Address: http://unigis2.unisolutions.com.ar/HUB/UNIGIS/MAPI/SOAP/GPS/Service.asmx<br>* Port: 80</td></tr><tr><td>Login and password</td><td>Your Unigis login and password</td></tr><tr><td>External ID</td><td>License plate number of an individual vehicle</td></tr></tbody></table>

To set up data forwarding in the Unigis protocol:

1. Open the device settings from the main menu by clicking the gear icon on the bottom left of the screen.
2. Click the **Data forwarding** block.
3. Click Protocols.
4. This opens a pop-up where you input the required parameters by clicking the **+** button.

For the Unigis protocol, input the following information:

1. **Name:** Enter a name to make this retranslator easily identifiable
2. **Protocol:** Select the Unigis protocol from the dropdown
3. Unigis login and password
4. **Destination server address**, e.g. <http://unigis2.unisolutions.com.ar/HUB/UNIGIS/MAPI/SOAP/GPS/Service.asmx>
5. **Destination port**, e.g. 80

A Retranslation management screen should look like the following, with Unigis login and password. Make sure the **Enabled** button is checked and click the **Save** button to complete the process.

![](https://www.navixy.com/wp-content/uploads/2022/08/pasted-image-0-600x112.png)

Next, the retranslator will need to be linked to the device on the Unigis side. To do so, select the **Link** <img src="https://www.navixy.com/wp-content/uploads/2022/08/image-3.png" alt="link image" data-size="line"> button in the **Data forwarding** block. Select the retranslator to be connected, and click **Link** below.

Next, add the ID of the device in the 3rd-party system either by clicking the pencil icon or the external ID field. This value should be the license plate number on the Unigis side. Select **Save** once completed.

#### Managing

To edit or stop data from being forwarded, follow these steps:

1. Select the **Pencil** icon or click in the associated box to edit the external ID used to point to the device on the 3rd party system.
2. Click the **Trash** button to stop the data forwarding.
3. Acknowledge the change in the pop-up.
4. Click **Protocols** to change retranslator settings such as name, login information, or enabled status
5. This will open the retranslator management window. Select the row to edit and either click the pencil in the top left or double-click the row in question to allow editing. Save any changes.

![](https://www.navixy.com/wp-content/uploads/2022/08/pasted-image-0-1-600x96.png)

#### Troubleshooting

If data doesn't display on the 3rd-party Unigis system, make sure that:

* Username and password for Unigis are correctly entered
* URL was entered correctly
* Retranslator is enabled
* External ID matches the license plate on Unigis


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/user/guide/devices-and-settings/connectivity/data-forwarding/unigis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
