anyLogistix
Expand
Font size

Release Notes

What's new in anyLogistix 2.15.2

  • Added a warning message when coordinates' autofill is not resolved.
  • Added a warning message when Site State Changes links to the Included sites in NO.
  • Added an error message when CPLEX stops optimization by time-out with no result found.
  • Removed by Facility Size option from Facility Expenses in the CO2 from Facilities table in NO.
  • Other bug fixes and improvements.

New example models

What's new in anyLogistix 2.15.1

  • Added links to example descriptions on Welcome Screen and in the Import Example dialog.
  • Updated examples. Improved descriptions.
  • Validation now checks if all objective members are disabled in the Objective Members table.
  • Other bug fixes and improvements.

What's new in anyLogistix 2.15

Import/Export scenario to/from database

Now you can host scenarios in an external DB on your own secure server, creating and updating scenarios in it with shared access managed by your IT team
The supported database engines are SQLite, SQL Server, PostgreSQL, and MySQL.

Network Optimization modeling improvements

  • Feasibility check in Custom Constraints for scenarios with contradicting constraints.
  • Enabling/Disabling expanding flows and storages by period.
  • Piecewise linear function is now supported in Custom Constraints.

New example models

All scenarios are updated, as well as two new examples are added:

Other improvements

  • Run experiments from command line.
  • Improved messages for import/export warnings and errors to simplify error tracing.
  • Manual proxy setting for ALX, for flexible security settings inside company networks.

What's new in anyLogistix 2.14

Advanced TO experiment

The Advanced TO experiment is discontinued. When importing scenarios of TO type you will get notification informing that the data referring to the Advanced TO was skipped.

Browser-based help

We are proud to introduce the new anyLogistix help system.

Find out more about style conventions.

It is available both:

  • Online at https://anylogistix.help (internet connection is required)
  • Offline. Choose Help > anyLogistix Help. The local copy will open in your browser

Import/Export

  • Column headers added for parameters of policies
  • Added support of Excel formulas
  • User-defined columns do not affect the import process
  • Error messages mention exact location in the Excel that causes the issue

Other improvements

  • Added CO2 cost data to Network Optimization statistics
  • Added Unicode support for the PostProcessor saving results to files
  • Added ability to create a group of facilities on a map
  • Update the built-in cities population database
  • Added cache for tabs with tables. The required tab will remain selected as you browse other scenarios or experiment settings

What's new in anyLogistix 2.13

Import/Export

New Excel data structure is introduced, which

  • Improves user experience while bulk editing in Excel
  • Provides better support for external scenario generation
  • Improves performance
  • Reduces memory footprint

Other improvements

  • Improved support of Postgres DB
  • Added option to skip scenario validation on experiment start
  • All statistics now can gather data by Period
  • The Demand Received statistics can now gather data by Destination
  • Improved MRP policy behavior

What's new in anyLogistix 2.12

Vehicles

  • It is obligatory now to specify a Vehicle type in the Paths table.
  • The default vehicle type with unlimited capacity is now created for every scenario except GFA

The Path Selection Mode table

  • Is removed from the NO scenario
  • Is replaced by the Vehicle Selection Mode table
  • Acquired new selection types

Simulation scenario

  • Acquired the new Shipping table that took part of the functionality from the Paths table, such as:
    • Transportation Policy (FTL / LTL)
    • Min load ratio (for FTL)
    • etc.
  • The Shipping table is now required to define shipping behavior between any pair of Source / Destination objects.
  • You can create several shipping polices for the same combination of Source / Destination / Vehicle Type to achieve the desired behavior (e.g. FTL + LTL with periodic check at the end of the week).
  • The behavior of the Periodic FTL policy changed (it replaced FTL with aggregate orders from the Paths table). The FTL check is performed after each period, but vehicles are not shipped unless min load ratio is reached. Consider using standard FTL with periodic LTL or pending orders policies.
  • FTL now ships only full vehicles, while in the previous version it was shipping all products if there was enough to fill at least one. New FTL also incorporates partial delivery by default.

Updating Project and importing old scenarios

  • Data for the Shipping table is generated automatically based on the existing paths.
  • If a vehicle is not set for a path, then the default vehicle type with unlimited capacity will be created and used in paths and shipping policies.

    If you use multiple measurement units, make sure that conversion rules are defined for every product (from the product unit to the vehicle’s capacity unit).

Extensions update

The following actions should be performed for any DC or supplier extension to maintain compatibility with the new version:

For DC:

  • In the shipmentReturned function replace shipmentGenerator.checkShipments() with shipmentGenerator.vehicleReturned(shipment.getVehicleType())
  • In the On at exit action of the processIncomingOrder block add checkWaitingOrders(agent.getProduct());
  • Update parameters of the shipmentGenerator block:
    • In the On order created parameter add inventory.reserve(order.getProduct(), order.getQuantity());
    • In the On order dropped parameter add:
      inventory.reserve(order.getProduct(), -order.getQuantity());
      ALX.statistics().orderStatusUpdate(order, OrderStatus.Dropped);
      order.getDestination().onOrderDropped(order);
    • In the Available inventory parameter add inventory.getAvailableInventory(product)
    • In the Fleet parameter add vehicles.getFleet(vehicleType)
  • In the checkAvailability function (3rd condition, line 8) replace
    if (ALX.getPath(this,destination, product) == null) with
    if (!ALX.canDeliver(this,destination, product))
  • In the On load parameter of the inventory element add shipmentGenerator.inventoryChanged(product);
  • Also, the name of the shipmentGenerator on exit changed to On shipment exit, so the old value could be lost. Make sure to add any custom code you have there.

For supplier:

  • In the shipmentReturned function replace
    shipmentGenerator.checkShipments() with
    shipmentGenerator.vehicleReturned(shipment.getVehicleType())
  • Update parameters of the shipmentGenerator block:
    • In the On order dropped parameter add:
      ALX.statistics().orderStatusUpdate(order,
      OrderStatus.Dropped);
      order.getDestination().onOrderDropped(order);
    • In the Available inventory parameter add Double.POSITIVE_INFINITY
    • In the Fleet parameter add vehicles.getFleet(vehicleType)
  • In the checkAvailability function (2nd condition, line 5) replace
    if (ALX.getPath(this,destination, product) == null) with
    if (!ALX.canDeliver(this,destination, product))
How can we improve this article?