anyLogistix
Font size

Connections of the GIS Map Elements

The connections of the supply chain elements are visualized on the GIS map and in the Structure view. These connections depict the sourcing that is defined by a user in the anyLogistix tables. By default the connections are not visualized.

A visualized connection is the connection that is properly defined in the basic anyLogistix tables (the set depends on the scenario type): Demand, Paths, Sourcing, Shipping, Inventory, Product Flows and Product Storages.

The default values of these tables allow connections to be created instantly on adding a new object to the scenario.
As for instance, when you add a new distribution center to the SIM scenario containing customers, the sourcing policy automatically (dynamically) detects customers that will be supplied by this distribution center. This set of customers is updated each time this distribution center is moved or another distribution center is added.

To enable connections on the map

  1. To visualize connections on the map do either of the following:
    • Click the Show connections icon to display connections as real roads.

    • Click Show straight connections to display connections between the objects as straight lines.

    anyLogistix will process data and show the connections on the map:

Processing data

Once you enable connections, anyLogistix will download data from the AnyLogic routes server (make sure it is not blocked) and build routes that will be shown on the map.

During this process the map shows the current status:

  • Processing connections — anyLogistix detects the required locations and connections between these locations for the current scenario, and sends this data to the AnyLogic routes server.
  • Loading distances (28/1000) — the server returns distances between the provided locations. anyLogistix creates a set of connections by updating the data with the obtained distances. The created set of connections is sent to the server, which returns the corresponding routes to obtain routes from it.

    This set of connections is stored in RAM on your workstation for up to 4 hours. RAM can store up to 5 sets of connections (one per supply chain scenario).

  • Loading routes (28/100) — the server returns routes that will be displayed as actual roads on the map. anyLogistix downloads only the routes that are required for the previously built set of connections. The obtained routes are stored in the user's database (and can be dropped).
    Each time the user requests visualization of connections on the map, anyLogistix compares the set of connections in RAM with the routes stored in the database. In case the existing routes in the database differ from the set of connections of the current supply chain structure, anyLogistix will repeat the process to obtain the missing routes in addition to the existing routes.

Reasons behind the missing connection on the map

The defined connections may not be shown on the GIS map because the defined data is either incorrect or affects connection visibility.

By default the records of these tables consider all objects and all possible connections between them, which eliminates the possibility of data inconsistency.

The possible issues may refer to:

  • Excluded object (or group of objects) from the supply chain. For example, if the Inclusion type of a customer is set to Excluded, this customer will not be shown on the GIS map, the connection leading to it will not be drawn.
  • Incorrect parameters of a custom sourcing policy. For example, a path is not defined for a pair of objects.
  • Missing product flow or product storage in case of the Network optimization scenario type.
  • Missing inventory or shipping in case of the Simulation scenario type.
  • Supply chain containing customers only.
  • Missing paths.
  • Absence of demand. If an object has no demand, a connection will not be created, since there is no need to make deliveries to it.
  • Incorrect product measurement unit in one of the tables. This may be the case when converting a scenario from the GFA type to NO and SIM types. The Paths and Vehicle Types tables acquire new data with the default measurement unit. So if your product is measured in e.g. pcs, anyLogistix will consider certain routes unavailable for this product.

    A missing conversion of a measurement unit to e.g. the used vehicle type's capacity unit may also be the issue.

How can we improve this article?