Product Updates

SC Navigator 26.8.1Date July 9, 2026 New Features A new Compare Results page has been added to the Results workflow. This page allows users to compare loaded results more easily and provides a clearer overview of differences between Results Datasets. For more information, see Compare Results. On the Center of Gravity page, we added five new filters in the side panel for filtering on Customers, Suppliers, Products, Periods and Fixed Locations. Improvements The performance of retrieving geocodes and distances based on addresses has been improved significantly. Transport Navigator now validates whether a leg duration exceeds 120 hours (5 days). Such legs cannot be planned by Transport Navigator and are typically caused by incorrect or swapped longitude/latitude values in the Locations sheet. Bug Fixes Some pages could have a gray background behind the tab area. This background is now white, consistent with the rest of the pages.

SC Navigator 26.7.1Date June 8, 2026 New Features There are two new attributes on the Production Routing sheet: Minimum Open and Maximum Open. This allows for adding a new type of count constraint to the model. You can now enforce how many production routing combinations must be active within a group. These new Minimum Open and Maximum Open attributes are also included in the Full Solution Export on sheet Production BOM. Improvements On the Transport Navigator map, the displayed routes are now colored differently to make it easier to distinguish them. Furthermore, when clicking on one of those routes, it gets highlighted such that it stands out clearly from the other routes. SENSAI switched to a more powerful model; it understands you better and it responds faster. The multilingual support is improved such that SENSAI always answers in the language of the question asked. SENSAI Pro now supports copying data between warehouses. The SENSAI History Filter button has been improved with a consistent icon, stable button size, and a clearer filtered state indicator. Bug Fixes In Transport Navigator, if Maximum Layover Duration was not specified, the Maximum Layover Duration would be set to 0 instead of being unlimited. In SENSAI Pro, a warehouse created from scratch was missing internal flags, which could cause incorrect behavior. In SENSAI Pro, copying a warehouse now correctly transfers all related data to the new warehouse. Undo in SENSAI Pro now correctly reverts all affected attributes (e.g. Force Open, Force Close) when making changes. In the maximized view, a widget without header could cause the navigation to get stuck in the maximized view. In the Full Solution Export, when using the same resource ID for both Production and Warehouse entries, the Production sheet could get missing. Production data is now correctly preserved in the generated Excel file. The Full Solution Export now includes Take or Pay Unit and Take or Pay Cost in the Transport Results sheet.

SC Navigator 26.6.1Date May 21, 2026New FeatureSENSAI Pro is now available for SC Navigator users. Stop clicking through menus — just ask. SENSAI Pro brings an AI-powered chat window to SC Navigator, so you can make data changes, run optimizations, and compare scenarios through conversation. Try questions like: "Add a warehouse in Berlin, similar to our Munich hub" — new location, attributes, and transport lanes configured automatically. "Increase LTL transport costs by 5% across all lanes in Germany" — update dozens of lanes in one command, with a one-click Undo if you change your mind. "Run the optimization with demand at -5%, +5%, and +10%" — generate and save multiple demand scenarios in a single request. "Which warehouses open or close, and how does volume shift across the network between scenarios?" — instant network comparison, no spreadsheet exports needed. "What changes have I made so far?" — full session transparency, always. Try SENSAI Pro for free until July 1st, 2026 — request a demo to get started. Read all the details in the SENSAI Pro documentation.

AI Assistants for Every AIMMS ApplicationA new library lets you transform any AIMMS application into something your users can interrogate with AI: ask questions, run scenarios, and get answers in plain language. It has already been tested on four complex use cases and models. You can get involved too.  Why this matters Business users can now talk to the optimization model in plain language and get answers in seconds, with no new tools, no Python, and no bolt-on chatbot.  The end-user experience in more detail Your planners open a conversation inside the AIMMS application and ask questions in plain language: "What happens if we lose this warehouse for a week?" or "Can we still meet demand if we cut the third shift?" The AI assistant orchestrates the interaction, the optimization model runs the math, and the planner gets an answer in seconds, all without leaving the tool they already use.  Here is what it looks like in practice:  "Which customers in the Nordics had more than 5% unmet demand last week?". The agent queries live optimization results and returns a filtered answer with the relevant numbers.  "Our Düsseldorf warehouse just lost a shift. Cut its daily throughput capacity by 30% and re-optimize". The agent modifies the input, re-runs the solver, and reports the cost and service level impact across the affected network.  "Compare our current plan with a version where we consolidate the Berlin and Prague DCs into one. Show me the cost delta and any customers that drop below 95% fill rate". The agent runs both scenarios, compares the results side by side, and highlights the trade-offs.  How you will add these AI-assistants The same library works across any AIMMS application. You import it into your project, provide configuration that teaches it your domain, and your application becomes AI-ready. From there, you control everything the AI can touch. As a developer, you decide exactly what the AI can see, what it can modify, and what requires user confirmation. You set this per identifier. That level of governance is what separates a production-grade AI assistant from a chatbot bolted onto a UI. We will publish detailed documentation on each of these as the capability moves into early access.  Built on real operations, not in a lab We are building this in workshops with customers, on real, large-scale optimization applications. Teams bring their actual models and their actual user pains, and we work together on development builds. Four workshops have been completed so far, across industries and geographies. Each one has surfaced problems that only show up at production scale and improved the product directly: edge cases in large indexed data, planner expectations, and the level of domain context the agent needs to give useful answers. The problems that matter most are the ones you only find in real operations, so that is where we are spending our effort.  Start preparing now If you build and maintain AIMMS applications, you can start preparing now:  Understand your users' pain points. The best AI experiences start from tasks that are multi-step, time-consuming, or error-prone for your business users. The AI assistant is most valuable where it replaces work that is manual, repetitive, or spread across multiple screens.  Think about what to expose. Walk through your model and identify the sets, parameters, and procedures that matter for the workflows your users care about. You stay in control of what the agent can access.   Plan your application prompt. The application-specific context you provide determines how well the agent understands your domain. Include what the optimization does, key terminology, and any constraints or assumptions your planners should be aware of.    Get involved We are running hands-on workshops with customers to add a working AI assistant directly into their AIMMS applications. If you want to explore this on your own application, or help shape what comes next, talk to your AIMMS contact or reply to this post. 

SC Navigator 26.5.1Date April 20, 2026 New Features Transport Navigator now allows many attributes, previously only available on the TN Locations sheet, to be defined at the vehicle level. This enables more flexible, heterogeneous fleet configurations where individual vehicles can have their own attribute values. Improvements Users can now see their SENSAI feedback with highlighted thumb icons that persist after clicking, and can cancel their rating by clicking the same thumb again to send neutral feedback. When uploading an Excel Template, only .xlsx files are now accepted. When trying to upload unsupported file formats, an error dialog will show up and no processing will take place. We have extended Transport Navigator with the ability to handle multiple Grouping Codes at one customer location. For instance, if a customer has demand for frozen products and demand for ambient products, the model will now route two trucks to this location, one for each type. Bug Fixes The documentation of the attribute ‘IsIntersection’ incorrectly stated that it was no longer in use. We updated its description and removed the statement indicating that it should not be used anymore.

SC Navigator 26.4.1Date March 30, 2026 New Features The SAP-IBP Connector has been introduced, enabling the creation of SC Navigator templates or datasets directly from SAP IBP data. This simplifies the data onboarding process by reducing manual data preparation and ensuring consistency with the SC Navigator data model. For detailed steps on how to configure and use the connector, please refer to the documentation SAP-IBP Connector. Improvements The performance of the various maps in the application has been improved by limiting the internal calculations to the nodes/arcs that are currently visible on a map. That means that when viewing maps on a world scale, the performance will be more or less the same as before. However, when zoomed in to regions with a more limited number of nodes/arcs visible, rendering, zooming and dragging should be faster. We have removed the following warnings from the model: WARNING: Product is available/created at a location, but outbound lane is missing WARNING: Product is available/needed at a location, but inbound lane is missing. We noticed that a reasonable amount of users received these warnings, while there was no problem in their model. Therefore, we decided that it was better if the model would not generate these warnings. The performance of calculating rate card-related data has been improved significantly. A color description has been added to the Cost to Serve Map documentation.

We will soon release a completely new Sessions page in the AIMMS Cloud Portal. Here's a quick summary of what's new:Unified session list – All session types are now displayed in a single table More data at a glance – New columns including session kind, environment, app version, and timing metrics GbHour consumption – A long-requested feature! You can now see the GbHour usage per session directly in the table Filtering – Easily narrow down sessions using the new filter option Session Stats – A new dedicated tab giving you aggregated insights into session usage and performance across your applications More actions – Bulk actions and an improved per-row context menu give you greater control, including the new Session events option to view a timeline of events for any session.Find out more here or contact support@aimms.com.

SC Navigator 26.3.1Date March 19, 2026 New Features For Transport Navigator, the vehicle attribute ‘Route Ends at Last Stop’ has been added. Vehicles with this attribute enabled will not return to the depot after their last customer stop. Improvements On the Transport Results page, single and group volumes are now displayed in separate columns in the Primary, Secondary, Direct, Inter Resource, and Transport Results tables. Similarly, in the full solution export, the “Volume” column now contains only single values, and a new column has been added for group volumes. The following new columns have been introduced in the respective sheets: Primary Transport: Primary Group Volume Secondary Transport: Secondary Group Volume Direct Transport: Direct Group Volume Inter Resource Transport: Inter Resource Group Volume Transport Results: Group Volume

In AIMMS 26.1, following the earlier modernization of our MIP/LP generators, we've completed the same overhaul for the Nonlinear Programming (NLP) generator. This replaces the legacy code with the same modern architecture already powering linear model generation.Purpose of the modernizationThe legacy generator constrained how quickly we could evolve the platform. This is a significant step toward getting the entire model generation pipeline onto the modern codebase, enabling us to deliver improvements faster.What to expectThis change is not intended to have any significant impact on your experience. Two things worth noting:Solution differences are possible. The generated math program may differ slightly from the legacy generator (variable ordering, constraint ordering). Objective values will be the same if a global solver (e.g., BARON, Gurobi) is used, but might differ if a local solver (e.g., CONOPT, Knitro) is used. The specific optimal solution returned by the solver may also vary. This is normal behavior when the underlying matrix structure changes.Option: equals_bounds_imply_nonvar. The legacy generator applied this transformation automatically. The new generator makes it opt-in, since it adds overhead that isn't always justified. For NLP models in particular, we recommend enabling it. It can reduce both model size and the number of nonlinearities, which helps solver performance.As always, if you notice any unexpected behavior, let us know!

SC Navigator 26.2.1Date January 26, 2026 New Features A new feature is now available to retrieve transport cost information. High-level transport cost data is available via the Retrieve High-level Cost Data attribute, and detailed cost data can be requested through the Request Detailed Cost Data attribute. For more details on how to use these features, please refer to Transport Cost. Improvements In some situations when working with a big dataset, we have improved the performance of the preprocessing of the optimization model. Selecting routes on the Transport Navigator main page could take rather long. We improved the performance drastically. The performance in processing the results in the E2E lead time model has been improved. In Transport Navigator, the demand data validation message is improved. It now shows a clear list of allowed demand attribute combinations, preventing ambiguous interpretation. In Transport Navigator you will get an error when starting a TN Solve without having a warehouse selected. In case there are no warehouses to select, this error message is now more informative. The table headers on the Results - End To End and Cost To Serve pages have been updated to indicate whether they display values for all demand or per unit. In Transport Navigator, data validation has been added. The model now requires that each TN period has the same length. Various small performance improvements have been applied. Bug Fixes The data validation could incorrectly report missing Transportation Lead Time data when the data was actually present in the Transport Trip column. On page Results, the reference map displayed extra nodes when the reference dataset did not match the active dataset.

Need to securely store 'secrets' such as passwords or API keys for your application?We released a new service to cater for that. Your app secrets will be securely stored in an Azure Key Vault. Read more about it on: https://documentation.aimms.com/cloud/managing-secrets.html 

SC Navigator 26.1.1Date January 8, 2026 New Features Transport Navigator has been extended with the ability to allow flexibility in the delivery day for each customer, through the attribute Pattern Group. This flexibility can be used to balance the warehouse effort through the attributes Minimum Relative Capacity and Maximum Relative Capacity. See Getting Started with Transport Navigator for details. Improvements A new Source Location Weight attribute has been added to the Locations sheet to extend the Maximum # of Source Locations constraint by allowing weighted source contributions. For more details, see the documentation Optimization Parameters and Constraints. On the COG Settings page, a counter has been added to the Fixed Location selector. In Transport Navigator, the readability of the main text on the Solve in Background dialog page is improved by adjusting the font color, which was previously too light and hard to read. In Transport Navigator, the titles on the KPI Summary page are now more consistent. In Transport Navigator, on page Results, tab Route Summary, some columns have been resized for better visibility. Additional data validation has been added for Transport Navigator. We now check whether a location serves both as a customer and a warehouse, and this is no longer allowed. The documentation now includes details on the Allow Base Case Volume Mismatch feature. Bug Fixes When deleting a scenario on the Manage Data page, the Conflicts message referred to Input Datasets instead of Scenarios. Running Constrained CoG optimization with only Suppliers, could previously produce incorrect results including zero costs and sub optimal CoG locations. Previously, load consolidation did not work correctly when used together with the Base Case, as minimum shipment requirements were not enforced. Now, minimum shipment constraints are properly respected in the Base Case as well. Routes displayed on the Transport Navigator map now respond correctly to Customer and Vehicle filters. All calculated routes remain visible at all times; only their selection state changes based on the applied filters. In Transport Navigator, routes are shown on a map. Each arc on the map represents a leg of a route. The label of the arc shows the number of the leg as part of a route. If an arc represents multiple legs of different routes, the numbers were previously summed in the label. Now they get listed, such that you can easily see that a leg is part of multiple routes.

SC Navigator 25.18.1Date December 15, 2025 Improvements The reading from Excel has been adjusted so that it will continue to read the file when empty rows were encountered. In the past, reading would stop (often with a warning), but now SC Navigator will continue to read the file. The solver performance has been improved for some rare cases where performance was unexpectedly slow. Data validation is added for transportation types for which a lead time was specified, but the Mode of Transport sheet didn’t contain a Speed value. In the Full Solution Export, the deprecated Transport Cost sheet has now been removed after its replacement by the Inter Resource Transport sheet. Several improvements in Transport Navigator: units are added to table headers and chart tooltips for better data clarity; better readability of some tooltips; preventing SC Navigator solves when using Transport Navigator-only templates; better streamlining of completed optimization notifications. In Transport Navigator, the “Show Routes” button is now only active, when there is route data loaded. SENSAI has been moved out of Beta release. The underlying architecture for communication between SENSAI and AIMMS Cloud sessions has been improved to facilitate future AI features. The product filter on the Results pages, has an new widget action that allows you to toggle whether or not the product selection should impact the location selection. This is useful if you have selected the locations (Supplier, Warehouse, Production) and you want to look at the results for different products. Previously it would change the selected location. This is no longer the case if the switch is set. The ‘Force Open (Inventory)’ attribute on the Inventory Product sheet now supports curly bracket grouping. Bug Fixes The Balance and Accuracy algorithms for Number of CoG solves, now support cases where all locations have the same demand. Data validations for the E2E Lead Time model are added to prevent unsupported configurations. The documentation section E2E Lead Time has been updated accordingly. The Maximum Capacity column has been restored in the Excel template on the Inventory Product sheet.

Dear Community,We’re excited to announce that AIMMS WebUI 25.8 introduces a completely overhauled Gantt Chart widget type (GanttChart V2). This new widget type is a major upgrade of the existing Gantt chart widget, offering a more modern, flexible, and intuitive way to visualize time-based activities in your applications.  🆕What’s New in Gantt Chart v2Gantt Chart v2 brings most of the capabilities you’re familiar with from the exisitng Gantt, but with a cleaner and more consistent design. Rebuilding it also gave us the chance to fix some long-standing limitations and prepare for future improvements.Key Improvements include:Modernized visualization for tasks, and durations. Cleaner layout logic, improving readability in complex schedules More configuration options, enabling richer application specific views Stronger core foundation, making it easier to add future enhancementsThis version doesn’t introduce all possible interactions yet, but it puts us in a much better position to add them over time. 💡Why This MattersScheduling and planning tasks are core to many AIMMS applications. This update makes those insights easier to understand, clearer to present, and more interactive for end users.This update is also an important step in AIMMS’ ongoing code modernization efforts. By rebuilding the widget on a more robust and maintainable foundation, we gain:Better control over the underlying architecture A cleaner and more future-proof codebase Greater flexibility to deliver improvements faster A stronger platform for modern UI and UX enhancementsIn other words, Gantt chart v2 widget not only improves the experience today, it sets the stage for richer, more powerful functionality in upcoming releases. ❓Migration FAQIs there automatic migration from the existing Gantt to the new Gantt v2 widget?No. The new Gantt v2 is introduced as a separate widget type, and existing Gantt widgets will not automatically migrate. App developers will need to add the new Gantt chart v2 widget to their pages and configure it based on their existing data.Will migration support be added in the future?Possibly. If developers express significant interest or specific needs, AIMMS WebUI may consider adding support for migration from the older Gantt widget. For now, migration is manual.Does the old Gantt widget continue to work?Yes. Existing Gantt chart widgets will keep functioning as they do today, so you can transition to the new version at your own pace. 📘 Learn MoreYou can find details, and configuration instructions in the WebUI documentation (see the “Gantt Chart v2 Widget” page).  As always, your feedback and suggestions are highly valued. Feel free to explore the new features and share your thoughts with the community. Thanks,Team WebUI.

 We released several enhancements in User Management aimed at improving navigation, clarity, and overall usability. These will be rolled out to customer accounts in the next few days.Streamlined Creation ActionsTo enable quicker access, the Create Environment, Create Group, and Create User buttons have been moved to the top of their respective pages.Improved Search & FilteringWe have added search fields to both the Group and User lists, facilitating the easy location of specific entries.Optimized Data LoadingGroups and users will now be fetched only when you open their respective tabs within an environment. This enhancement removes the previous automatic prefetching, resulting in faster initial navigation and more intentional data loads.Updated User Roles ModelWe've replaced the Global Roles with a new, simplified Roles model:User roles can no longer be assigned directly; the Roles column is read-only. A user’s role is assigned automatically based on their membership in one of the system-defined groups. User roles are currently limited to two system-defined roles: Admin and App Publisher.Contact usIf you have feedback or questions, please reach us at support@aimms.com 

The latest PRO version on AIMMS Cloud includes MFA enforcement. Admin roles can now enforce MFA for all users. Please check the documentation for details.

SC Navigator 25.17.1Date November 7, 2025 New Features SC Navigator now includes End-to-End Lead Time Constraints. This feature enforces a limit on the total lead time across all supply chain stages (supplier, production, warehouse, transportation). For efficiency, constraints are applied iteratively only where violations occur, until all are resolved or the solution converges. This functionality is resource-intensive and disabled by default. See section E2E Lead Time for details. Improvements Calculating whether a lane links to a zone based rate card is made more efficient. This can result in a performance improvement when you use zone based rate cards. Bug Fixes The custom objective cost was not displayed on the Transport Results page when using customer rate cards. When opening Power BI from SC Navigator, a blank screen was displayed. The connection has been updated to ensure that Power BI loads correctly when launched from SC Navigator.

SC Navigator 25.16.1Date October 28, 2025 New Features We added Transport Navigator sheets to the Full Solution Export functionality. We added the following sheets to the export: ‘Vehicle Groups’, ‘TN Periods’, ‘TN Route Summary’, ‘TN Route Details’ and ‘TN Vehicle Summary’. Improvements The model now supports closing warehouses containing opening inventory. Previously, if your input data included both ‘Opening Inventory’ and ‘Force Close (Inventory)’, the model ignored the Opening Inventory. Now, the model includes the ‘Opening Inventory’. This means all ‘Opening Inventory’ will move out of the warehouse to the appropriate destination instead of being ignored. The documentation contained a description of attribute ‘Cost per Hour’. However, before the release this was replaced by ‘Cost per Hour Driving’ and ‘Cost per Hour Waiting’ in the application and template. Now, the documentation reflects this as well. The documentation contained different descriptions of ‘Duty Time’. We now have a unified description throughout the documentations, including descriptions in the template. We have made another improvement in the performance of SC Navigator. Bug Fixes If you tried to open a Transport Navigator run from a previous session, by clicking on the “All 0 runs completed” in the status bar, without having run a TN optimization run in this session, the results would not be loaded.

SC Navigator 25.15.1Date September 25, 2025 New Features The transportation cost calculation has been enhanced with new attributes on the Transport Cost sheet: Minimum/Maximum Load Size and Minimum/Maximum # of Trips. These parameters determine how the Number of Trips is derived. When at least one of the four new attributes is defined, the total cost is calculated as: (Number of Trips × Cost per Trip) + (Cost per Distance × Distance). As a result, 6 new attributes are added to the Full Solution Export: Transport Minimum Load Size Transport Maximum Load Size Transport Actual Average Load Size Transport Minimum Number of Trips Transport Maximum Number of Trips Transport Actual Number of Trips Improvements Data validation is added for cases where a product is marked available for inventory in only some periods. To model inventory closure in specific periods, keep the product available in all periods and use the Force Close attribute instead. Bug Fixes In rare cases, when quickly zooming in and/or out on a map, the map could get ‘stuck’ between two zoom levels and jump back and forth infinitely. Mouse wheel zooming on maps did not take the current position of the mouse into account anymore. Instead of zooming in on that point, the map was zoomed in on the exact center of the displayed map. When moving between 2 pages which contained maps (e.g. between the Results and the CoG pages), the zoom level was not retained anymore. Instead, the map was reset to ‘World level’ again. Mouse wheel zooming on maps now takes the speed of the wheel into account. So, if you roll quickly, you zoom in/out more coarsely. When rolling slowly, the zoom in/out becomes very precise. Note that the step size can be influenced by your mouse scrolling settings specified for your machine.  

SC Navigator 25.14.1Date September 18, 2025 New Features On page Transport Navigator Results, a new tab is added: Route Distribution. It provides interactive histograms and a detailed data table for analyzing route performance. Users can filter by interval, view tooltips with route details, and compare attributes side by side. Improvements Transport Navigator can now handle demand data that exceeds vehicle capacities, enabling multiple shipments to fulfill customer demand. Page loading speed is improved among CoG pages. The improvement is noticeable when working with certain larger datasets, while smaller datasets may see less impact. The performance of the algorithm to solve Center of Gravity using “Max Drive Time” and “Constrained CoG” (when the objective is to minimize the number of CoGs) has been improved for some cases, along with the performance of the “Speed” option for the Number of CoGs algorithm. On page Center of Gravity, on the Node side panel, nodes of type CoG can now be (un)selected in Filter by Node Type. On both page Center of Gravity and page CoG Run Details, the CoG side panel is added. This allows you to filter on individual CoG nodes. On page CoG Run Details, the Customer Location side panel is also added. On page Results - Cost To Serve, Customer, Period and Product Groups have been added to the side panel. The Clear All Filters widget action has been added to multiple side panels. A warning is given before deleting all customizations when selecting Reset Map to Default. Labels and texts are updated in the UI for consistency. The documentation was updated to be more consistent with the app. On pages Results - Cost To Serve, and Results - End To End, the Period filter now works independently from the other Results pages. Bug Fixes The Number of Trips was not calculated when a Rate Card Drop Size was defined on either the Customer sheet or the Location Product sheet. In Transport Navigator, the solver ignored the Grouping Codes specified by the user. Now, the solver does take into account the Grouping Codes and they have been added to the Route Details, Route Summary and Vehicle Summary tabs. In Scenario Navigator, for Custom Objectives, the attributes Maximum Allowed and Minimum Required were not correctly used when solving the model.

SC Navigator 25.13.1Date September 11, 2025 New Features A new feature “Customer Reallocation” is added to the main map. You can interactively adjust [customer - source] assignments with greater control and flexibility. More information can be found in the section Customer Reallocation. The ability to provide feedback on SENSAI’s answers has been added. You can now give quick feedback using thumbs up/down buttons, available when hovering over a response in the SENSAI chat widget. Your feedback will help us further improve SENSAI’s ability to provide support. Improvements The Transport Navigator architecture has been improved, making it faster and more resource efficient. Because of this change the Overview of Solutions dialog has an extra tab Transport Navigator Runs Overview (NEW). Here you can load results created with this version. Results from previous versions can be retrieved from tab Transport Navigator Runs Overview. Bug Fixes On page Results - Transport, the transport costs in the Transport Results table were calculated wrong for customer rate card costing in case there were multiple customers on the same location. In the Inventory Planning app, the data validation no longer validates for available resource product data for products for which there is no demand at the warehouse. Loading multiple CoG Trade-Off results consecutively from the chart resulted in an error message. The Time Window End in Transport Navigator was sometimes set to the value of Period Start instead of the value provided in the Customer Product Data.

SC Navigator 25.12.1Date August 25, 2025 New Features The Number of CoGs algorithm can now be run from multiple starting points, increasing the likelihood of higher-quality solutions and supporting more efficient network designs. The new CoG setting “Algorithm for # CoGs” allows selection between Speed, Balance, or Accuracy, depending on whether faster results or greater solution precision are required. By default, the algorithm uses the Balance option, the previous algorithm behavior can be reproduced by selecting Speed. Learn more about the new CoG algorithms here. The Transport Navigator Results page has been extended with a Routes Schedule tab. This tab shows the optimized schedule as a Gantt Chart, making it straightforward to get a clear overview of the schedule at a glance. Transport Navigator now supports warehouse service windows using two new attributes: Opening Time and Closing Time. See section Transport Navigator Sheets for details. A new attribute is added: Allow Base Case Volume Mismatch. This allows a mismatch between Base Case Volume inflow and outflow at warehouse locations. It can be set up in the SC Navigator template on sheet ‘Settings’, or in SC Navigator on page ‘Control Panel’. Improvements Next to the already extensive standard list of AIMMS icons, we have added 19 new icons specific for SC Navigator that you can configure for the nodes used on the map on the Results page. Their names start with ‘scn-’ instead of ‘aimms-‘. The Number of Trips calculation now uses the Rate Card Drop Size for rate card lanes, ensuring it is calculated for rate card lanes as well. On the Ratio related sheets in the Excel input template, links are added to the E-learning tutorials about ratios. The step size of a single zoom action in all maps in the app has been made about 3 times more granular. This allows you to more precisely zoom into the exact area on the map that you are interested in. If you want to use a step size comparable to the old situation, please press the SHIFT key when using either the + or the - zoom buttons on the map. Some improvements to the Full Solution Export have been made: Transport Results now includes Number of Trips, Distance and Duration. Furthermore, the Transport Cost sheet has been renamed to Inter Resource Transport. Both these sheets are kept temporarily, but the usage of Transport Cost is deprecated and it will be removed in 2 months time. This will allow you to adapt anything that depends on the old sheet name. On page Control Panel, Include in Objective checkboxes are now read only when the objective is not compatible with the model objective (e.g. Total Physical Revenue while minimizing cost). Combining trips by Transport Navigator has been slightly improved, resulting in a lower total cost. A new attribute Maximum Drive Time (in hours), has been added to the Transport Cost sheet. This allows limiting drive time in any lane, not just on the customer side. Lanes with drive times exceeding the defined Maximum Drive Time will be excluded from the model. The new blue color is now applied to the Period Slider and switches. In the CoG Trade-Off, similar to the regular Trade-Off, the Set Input Data dialog now hides the Run button instead of just making it inactive when invalid input is detected. Cells containing invalid values are now highlighted with a red border instead of a red background. Bug Fixes In rare cases Transport Navigator did not display all generated trips and served customers. Data validation is added for cases where Include in Model Objective is set to 1 while Scaling Factor is 0, as this configuration excludes the custom objective from the Model Objective. The table on the Custom Objective Settings dialog page no longer becomes empty after downloading an Excel input template without any custom objectives specified. The error “There is a base case lane with a source/destination location that does not support the necessary product(s).” was incorrectly generated for curly elements.

We have now released supported, documented versions of two libraries bridging the worlds of Python and AIMMS.These will allow you to benefit from (a) the ubiquity of the Python language and its vast library collection and (b) from the proven AIMMS functionality for supporting industrial optimization models.aimmspy This library supports ‘Python in the lead’ scenarios. A Python application interacts directly with an in process AIMMS model for manipulation of the AIMMS data and running optimizations. Primary use case for this is probably running AIMMS models ‘headless', for example as part of a larger application, in automated pipelines or for large-scale batch optimizations.   Key features:Interact with an AIMMS run-time from inside your Python script Read and write AIMMS identifier values Run procedures in AIMMS including solves Support for pandas and polars data frames Model declaration using AIMMS Developer Requires a valid AIMMS Developer licenseLearn more from our documentation or reach out to support@aimms.com.pyaimms This AIMMS library supports ‘AIMMS in the lead’ scenarios, calling Python from within an AIMMS model. Primary use case for this is probably outsourcing specialized calculations to Python. Think of Machine Learning, demand forecasting, data cleansing, data wrangling, etc. Key features:Execute Python scripts or single statements Read and write AIMMS identifier values in Python Support for pandas and polars data frames Specify the Python version and all dependencies required using Can run on AIMMS Cloud, using a pyproject.toml file to specify the Python version and all dependenciesLearn more from our documentation or reach out to support@aimms.com.

You can now download cloud session logs from the PRO Portal, so that you can analyze or troubleshoot your sessions. You can access the logs via the Sessions tab and the three vertical dots on the right-hand side. Please note the ‘download log’ option in the top-right-hand corner of the following screen shot.  

SC Navigator 25.11.1Date July 28, 2025 New Features A new attribute is added to the Custom Objective sheet: Percentage Based. It enables modeling tariffs, duties, and taxes. Furthermore, two new attributes were introduced on the Transport Cost and Transport Step Cost sheets for Percentage Based Custom Objectives: Value and Rate. The cost calculation for the Percentage Based Custom Objectives will be as follows: Volume * Value * Rate + Volume * Cost per UOM. The Charts tab on the Transport Navigator - Results page has been improved. Now the two top charts can also show the vehicles data (which was previously displayed in the two bottom charts). Furthermore, clicking on a location/period bar in either of the top charts will result in the bottom charts displaying the data for that location/period on a more detailed per hour basis. A new ‘Add Delay’ option in the Period Selector’s right-click menu lets users slow down playback by configuring a custom delay. Transport Navigator now supports mandatory driver breaks after extended continuous driving. ‘Maximum Drive Time Before Break’ sets the driving time limit, while ‘Break Time’ defines the required rest duration. Improvements On page Results - Transport, a widget action to control whether the number of trips is rounded up, was added to the relevant tables. A new result attribute ‘# of Customers Served’ is added to the Warehouse Results. This counts how many customers are served by the warehouse. It is visible in the Warehouse Throughput Usage table on the Warehouse Results page and in the Warehouse sheet of the Solution Report Excel. Data Validation now marks negative values in the Rate Card Drop Size column on the Transport Cost sheet as a FATAL error. The Bill of Routing table on the Production Results page now includes an Arrival Period column, when applicable. Upon startup, SC Navigator will perform a complete refresh of the available datasets in the “import” file system. This means that it will remove all existing import datasets from its memory, and rescan the contents of the import file system. Additionally, the widget action Refresh Import File Systems has been added to the table with datasets, on the “Load Data” dialog, as well as the “Manage Data” page. This allow you to do a refresh on demand. Unnecessary transport lane data is now removed during processing. In some cases, this can lead to significant improvements in memory consumption and performance when reading data. The performance of the data validation procedures has been improved. Bug Fixes If there was no data in the Location Period sheet, the Force Open and Close columns did not show, and the Show All Attributes widget action did not function for the Location Open/Close Data table on the Control Panel page. On page Results, Arc Customization is now also applied to the Reference Map. Data validation has been added in case a base case lane has a lead time shorter than the duration for that lane, or if it routes products to a destination that does not support those products. The solution provided by the Transport Navigator module would sometimes not visit all customers. In some cases, some data that should have been on the input Data pages, was not displayed there (although it was used in the model). This was data for which the Available flag was not set at that level. Now, the Data pages should show all input data that is in the model. In the Whiteboard and Manage Data Input Excel download there were faulty Transport Navigator attributes exported which caused reading errors. The “Select Reference Map” column was occasionally missing from the Results dialog. On some pages, the secondary page action button covered the primary page action button. The Production and Warehouse Group sheets were missing when the model was not authorized to use Transport Navigator, while the TN Vehicles sheet was included. Transport Navigator would fail if you ran the model twice, but after the first run you excluded a vehicle used in the solution. When comparing results data, the E2E table only displayed data for the active results. When creating Production Routing scenarios, binary attributes like Force Close were treated as non-binary in the interface, preventing them from being set to ‘off’. The lead time offset did not work correctly when the model contained period groups in between regular periods. In some cases, the Cost To Serve and End To End cost report were not correct when using Period Offset. The Production Routing Data table no longer omits the Period Offset after saving a dataset or loading a saved dataset (rather than Excel).