Product Updates

SC Navigator 25.7.1Date April 7, 2025New Features We have introduced SENSAI to SC Navigator. SENSAI is an AI assistant designed to help users by answering SC Navigator related questions, including guidance through SC Navigator functionality and process support to enhance user experience. You can read more about How to Get the Most Out of SENSAI in our documentation. Please note that this version of SENSAI is a Beta release. Any feedback is much appreciated and welcome via support@aimms.com. Bug Fixes In SC Navigator 25.4.1, we stopped placing input data files in the Export folder. This feature has now been restored, and the files will be placed there again. On page Results - End To End, the data in the tables and in the filters is now restricted to those products that matches the selected level elements. Previously, if a certain production facility was shown, it showed the data for all products for those customer locations that have at least one product connected to that production facility. Now, it is limited to the products that are connected to that production facility. In previous versions, the application could generate a message like “ReadFromFile: Error: Reading parquet file production-routing.parquet failed: The file only has 0 row groups, requested metadata for row group: -1 in Parquet table file ‘production-routing.parquet’” when the application was trying to read an empty file. This has been fixed and the application will now read such files without any problem.

We want to discover whether there is demand for adding PowerBI Embedded to Optimization Tooling. And if so, in what form. So we are looking for your views and we are looking for potential launching customers or partners.ContextPowerBI Embedded is an Azure service for providing PowerBI dashboard inside a web application. It has a subset of the features of PowerBI Desktop. We recently released PowerBI Embedded as optional module for our network design and planning product SC Navigator. Why would you care?It would allow you to provide PowerBI dashboards with all its visualization power and flexibility, as part of an AIMMS application.  Optionally you might allow your end users to customize these dashboards (of course they would have to have the necessary skills).How would it work?We would provide: A widget which embeds the PowerBI dashboard inside WebUI Azure PowerBI Embedded service to run inside that iframe widget. Alternatively you can provide that yourself. PowerBI license. Again, you can also provide that yourself.  A mechanism to synchronize data between PowerBI embedded and AIMMS (using Databricks service on Azure). Instructions how to get started. You would have to: Configure with DEX the functionality to export data from the AIMMS model to the Databricks service. We will provide instructions for that. Connect the PowerBI Embedded service to the right data inside that Databricks service. We will provide instructions for that. Build one or more dashboard/reports in PowerBI Embedded.  We would charge you for: the OT PowerBI Embedded module (subscription) the Azure services we buy for you (cost +) optionally: support in setting this up Interested?Would you like to learn more about this potential feature or tell us about your needs or be a launching customer? Please contact me, Jan-Willem van Crevel, on j.w.van.crevel@aimms.com.  

Introducing to you our new software development project ‘Python Bridge’.Goal: Combining the best of AIMMS Optimization Tooling and the Python eco-system.Python’s coding features, tools and popularity Python’s vast library ecosystem AIMMS’ features for math program formulation, development and execution AIMMS’ WebUI for rapidly building interactive scenario planning applications AIMMS Cloud for easy, secure, scalable deployment OR local deploymentSupported scenarios:Run a Python app, outsource tasks to AIMMS (math programming, solving, cloud, end-user interface, ...) Run an AIMMS app, outsource tasks to Python (leverage Python's coding power and library ecosystem)Approach:The goal is clear. We are learning how best to combine these two worlds. There is still a lot to discover. Therefore we are releasing libraries and features, building prototypes and meeting monthly with a Customer Sounding Board to collect inputs and feedback. Current status:We released aimmscloud.py for interacting with the REST service end points on AIMMS Cloud.  Outsourcing tasks to Python from within an AIMMS apps works, including deployment of a separate container in our cloud running Python. In fact, we just released a new module for SC Navigator, Transport Optimization, that uses this feature to run a Python program to interact with the Hexaly solver. Read this article or contact support@aimms.com if you want to know more. Also looking at calling into python from within AIMMS: in-process python execution. We have several prototypes of a Python library to run a model declared in AIMMS, including automated parameter declaration and data syncing. We are engaging with our Customer Sounding Board members to learn about the desirability of specific features and where to move next. We aim to release a first library to outsource optimization from a Python app to an AIMMS instance in the next few months.  A first pre-pre-pre-pre release is expected in a few weeks.Keen to get involved?We would love to hear about your use cases for combining the worlds of Python and AIMMS.  We are looking for people wanting to test our early releases for their projects. The more feedback the better. Please send an email to me, Jan-Willem, at j.w.van.crevel@aimms.com if you want to participate.  

SC Navigator 25.6.1Date March 24, 2025 New Features SC Navigator now offers SC Navigator ETL, a tool that automates data preparation via Microsoft Azure Data Factory by pushing transformed data into the application and eliminating the need for users to import Excel files or configure the REST API connection. This is available as an add-on module; please contact your account manager for more information. The results of the data validation are now stored when saving an input dataset. The stored data validation results will be read in when loading that dataset, instead of re-executing the data validation logic. This improves the performance of loading a dataset, especially when data validation takes some time. A result of this change is that a new column “data_validation_version” is added to file “_dataset_info.parquet”. This value can be left 0 when you upload your dataset directly to the Azure Data Lake. Improvements On page Power BI, the styling of the Edit/View Mode dropdown list has been improved, such that it no longer looks read-only. As part of an improvement to the UI and UX of the AIMMS WebUI, the two main font families, Roboto and Montserrat, have been replaced with Inter Variable. Bug Fixes When using the Customer filter, deselecting individual customers from different groups unintentionally removed all customer locations. The Warehouse filter was missing two widget actions (Switch to Location View, Clear All). The Supplier Group filter was displayed even when no supplier groups were present in the data. The change that was made in the previous release (“Limiting the number of source locations could result in an unexpected infeasibility when small Capacity Consumed numbers were used, relative to the amount of products produced.”) could negatively impact the performance for some datasets. In the release of February 10, 2025, the type of the column “sequence_order” was changed from string to int32. This was not in line with the documentation, and this new version will have the type changed back to “string”.

SC Navigator 25.5.1Date February 25, 2025 New Features The Infeasibility Analysis functionality now has a new option in the Violations table: “Allow Missing Lanes”. Improvements In case of an Infeasibility Analysis Demand Violation, a new reason type has been added: “Missing Lanes”. Data validation has been added to detect locations that are (at least from one direction) disconnected from the network. Any input dataset that is saved, now also contains a file (“parquet-input-definition.xlsx”) with an overview of all the attributes in that dataset. Bug Fixes Opening the Filters side panel would display an error message about an unknown identifier. On page Data - Transport, the Transportation Data table could be empty. In some cases, the data validation was not able to point out when Inventory Cover was used without available inventory at a warehouse. Limiting the number of source locations could result in an unexpected infeasibility when small Capacity Consumed numbers were used, relative to the amount of products produced. On page Infeasibility Analysis, the input data was not appearing in the tables.

Dear Community,We are excited to announce the release of the AIMMS WebUI Library 25.1.1 version, packed with exciting enhancements and improvements aimed at enhancing your user experience. Below is a detailed overview of what's new: The Advanced Table Editing feature, developed about three years ago, brought significant enhancements to the Table widget, allowing for efficient manipulation of tabular data. This included the ability to copy and paste data between WebUI tables and to external sources. In response to customer feedback, we've further expanded this functionality to support the direct pasting of data from external sources like Excel and Google Sheets into WebUI tables.   In the latest WebUI Library feature release, the Table (v2) widget has been upgraded with a "Read Only" feature, allowing you to display data as non-editable and prevent users from making changes. Initially offered as a per-identifier option, we've now responded to customer feedback by adding a "Read Only" option in the "Defaults" section of the Contents tab. By default, the per-identifier setting will inherit its value from this default, unless you choose to override it. This update simplifies the process by enabling you to set all content identifiers to "read-only" at the default level, improving both the process and user experience compared to setting this option individually for each identifier.    We hope these features enhance your applications and contribute to an even better user experience. Your feedback and suggestions are highly valued, so please share them in the comments. Thanks,Madhu KrishnappaAIMMS WebUI Product Owner

SC Navigator 25.4.1Date February 10, 2025 New Features The model has been extended with the ability to create a Power BI Embedded report, based on the data in the application. This is available as an extra module, please contact your account manager for more information. Improvements The exported results are also used in the new Power BI Embedded feature and therefore, the results have been extended with the sheet/files with the element description as well as the sheet/files with the group definitions. Also the following attributes have been added: Start Date and End Date to Period Definition/period-definition, Longitude and Latitude to Location Definition/location-definition, IsSKU, IsUnion, and IsIntersection to Product Definition/product-definition. The fields “adopted” and “active” in the _dataset_info.parquet file were written as int32. However, if the cell was empty, pandas would interpret this as NaN (Not a Number) and therefore as float. This lead to a situation, where the model was no longer consistent with the file specification. From now on, the model will actually write 0 to prevent this issue. Bug Fixes When using Bill of Materials that create two or more products, the Cost To Serve and End to End reports were incorrect. On page Control Panel for the table Min/Max Constraints, the Show All Attributes action was not working properly. In some cases, the constraint “Max # of Sources for Customers” in combination with product groups could result in an infeasible model.

SC Navigator 25.3.1Date January 28, 2025 New Features It is now possible to also run Center of Gravity in the background, allowing you to continue using SC Navigator without interruption, including starting additional solves. Once Center of Gravity runs are completed, a notification and/or dialog page will appear to inform you. If you prefer not to solve Center of Gravity in the background, you can turn off the ‘Solve in Background’ option on the Control Panel page in the Model Control table. Improvements The Take or Pay Costing documentation has been updated. It now includes a more detailed description and also a comparison with Stepwise Transport Costing. Bug Fixes On page Results - Production, the node colors on the map didn’t always reflect the production utilization status. When a location had both a warehouse and production, the node color reflected the utilization status of the warehouse instead. In SC Navigator 25.2.2 we introduced an improvement, designed to enhance the optimization model for certain datasets with minimum production capacities. However, this change inadvertently caused infeasible solutions for datasets without minimum production capacity.

SC Navigator 25.2.1Date January 16, 2025 New Features For (almost) all tables on all the Data pages, a new action is available in the three dots menu (top right corner of each table): Show All Attributes. This action allows you to view and edit all available columns/attributes, even if they currently contain no data. You can hide the columns without data, by using the action Only Show Attributes With Data. Improvements The Release information dialog that shows up the first time you start a new version of SC Navigator, has an improved look and now shows all the release notes of all previous SC Navigator versions, just like the Release Notes page in our documentation. The data validation for rate cards was inefficient. The code has been modified to speed up this process. Bug Fixes The calculated rate card cost could be wrong if you used a Rate Cards UOM that was different from Default/Base UOM, in combination with rate card attributes Cost Per Distance, Cost Per Trip, or Minimum Cost Per Trip. If you use this combination in your model, please contact us at support@aimms.com.

SC Navigator 25.1.1Date January 9, 2025 New Features Previously, every SC Navigator user had access to 1 solver. As of Monday January 6th 2025, we introduced Hyperscaling, which means that every user has access to 25 solvers at the same time. Instead of processing scenarios one-by-one (sequentially), multiple scenarios are now solved in parallel, significantly saving users time and boosting productivity when solving multiple scenarios at the same time. You can read more about Hyperscaling in this blog post. Improvements In the previous version, a user was not allowed to load a Results dataset that was created when the user had access to more modules than currently are allowed. This is now allowed without any restrictions, unless it contains data for attributes that are no longer allowed. In those cases, you will still be able to load the data, but you are not able to run and/or save it again. The documentation has been updated to include detailed instructions on How to customize your Login page?. Data validation is added to make sure that a ‘Default/Base UOM’ is given when multiple units are used in the input data. Data validation is added to make sure that Product and UOM combinations used in the Bill Of Material, have an unit conversion specified. The ‘Save’ buttons are renamed to ‘Save As’, to better match their functionality. The System Configuration app is by default only available for the Admin user. When other users were assigned access to it, these rights would be reset (removed) after a new release of the System Configuration app. Now, these rights are transferred to the new version of the app. Bug Fixes Circular dependencies in the Bill of Material data previously caused a fatal data validation error saying that the Capacity data is too large. This is resolved and circular dependencies now only trigger the warning about circular dependencies. In the Data Navigator application, selecting a dataset from the Dataset Overview table and pressing the ‘Load Selected Dataset’ button will no longer result in an error. The Infeasibility Analysis was not working correctly in combination with the new Solve in Background option turned on. Now the Infeasibility Analysis page correctly becomes visible with the results when viewed using the Overview of Solutions dialog. An input dataset that was saved, after a results dataset was saved, was not correct. It contained only very limited amount of data, and reading it in, would lead to data validation errors, that were not present before. In some rare cases with multiple production facilities at one location and inventory build up, the production cost could not be correct, and too much cost was assigned to the System Cost.

A Python library to make it really easy to use AIMMS Cloud REST servicesIn response to the rapid growth of the use of the REST services on AIMMS Cloud we launched: the AIMMScloud Python library for working with the AIMMS Cloud REST API.Why this matters:Easily extend your CI/CD pipelines to AIMMS apps to streamline publication and even testing of your applications Easily access the REST services for programmatically running large numbers of optimization runs for example for scenario studiesIntegration in minutes with AIMMScloudThe AIMMScloud Python library wraps the AIMMS Cloud REST API in easy-to-use Python classes. Allowing you to publish AIMMS applications, running optimization tasks and accessing results becomes straightforward with AIMMScloud. The library was designed to help you achieve results in minutes. To add it to your Python project just use  pip install AIMMScloud For more information see: https://pypi.org/project/AIMMScloud/ Additional informationhttps://how-to.aimms.com/Articles/571/571-publish-run-delete.html https://documentation.aimms.com/cloud/tasks.htmlNext stepsThe AIMMScloud Python library is under active development, and you can expect more releases in the coming months.SupportIf you have any questions or suggestions, please reach out to us at support@aimms.com.

SC Navigator 24.14.1Date December 12, 2024 New Features It is now possible to run optimizations in the background, allowing you to continue using SC Navigator without interruptions, including starting additional solves. Once all active optimization runs are completed, a notification and/or dialog page will appear to inform you. If you prefer not to solve an optimization in the background, you can turn off the ‘Solve in Background’ option on the Control Panel page in the Model Control table. Two new attributes are introduced on the ‘Transport Cost’ sheet: ‘Base Case Minimum Capacity’ and ‘Base Case Maximum Capacity’. These attributes allow for more flexibility in base case modeling. Another two attribute are introduced on the ‘Location Period’ sheet: ‘Receive into Warehouse’ and ‘Dispatch from Warehouse’. They indicate, respectively, whether all inflow and all outflow should be received/dispatched via a warehouse at the location. See Location Related Attributes for details. Several new attributes are introduced on the Production Routing sheet: ‘BOM Fixed Cost’, ‘Force Open’, ‘Force Close’, ‘Opening Cost’, ‘Closing Cost’, ‘Open as Group’, and ‘Initial Status Closed’. These attributes allow for more flexibility in Bill of Material modeling. When exporting results, the Production BOM results sheet will also have new attributes: ‘BOM Fixed Cost’, ‘BOM Variable Cost’, ‘Opening Cost’, ‘Closing Cost’, ‘Force Open’, ‘Force Close’, and ‘BOM In Use’. More information can be found in the section How the Bill of Material works in SC Navigator?. Bug Fixes When trying to download results from older datasets, an error could occur: “Something went wrong when creating the file.” Now, all Results Datasets can be downloaded. In previous versions, the ‘Grid Distance’ (in Center of Gravity) was not adjusted based on lead time and maximal driving time. This could lead to situations where the grid distance was too large for the given parameters. This version will adjust the ‘Grid Distance’ to make sure that this is always within the recommended upper and lower bound, by moving it to the nearest bound. Theses bounds will now also consider customer ‘Lead Time’. The “Refundable with Limit” functionality was not working correctly. A new version of the Inventory Planning app has been published. When starting the previous version (24.10.1), Inventory Planning raised an error. The error prevented you from loading a configuration and dataset.

 We have built a new version of the AIMMS Cloud user screens such as the login page and the app launch page: Users will notice a new look and some minor changes in how to perform some specific tasks such as uploading new applications and user management.  Behind the scenes we have replaced the old Scala code with modern Javascript/React code that will be easier to maintain and change for us. These two screen shots show you the new look. What remained the same and what changes?No changes to finding and launching apps  Only for administrators and app developers: small changes to publishing apps and to user managementWhat is the timing?Roll-out will start in December 2024. We are using a phased approach for roll-out to customers: some groups earlier than others. We are also using a phased approach for development and roll-out of different pages/features. As a result you may discover some less-frequently-used pages still have the ‘old’ look while the other pages have a the new look. We expect to have completely replaced the ‘old’ somewhere in 2025.The making ofAlthough on the surface this looks like a minor cosmetic change, this change is a bit like an iceberg; by far the biggest part lives below the surface.A team of software engineers have spent more than a year on a redesign of the technical architecture and 100% recoding of the portal application. All the design concepts were reviewed and redesigned where necessary. Contemporary coding standards and software engineering methods were applied. Also, many of the interfaces with the backend components were replaced with REST API calls, in preparation of the upcoming replacement of the many backend components. And then everything was rigorously tested of course.More informationFor more information and questions, please contact us at support@aimms.com.

Gurobi 12.0 has been recently released. In our eyes the most important enhancements are the performance improvements and support for (global) nonlinear optimization for models with integer variables (MINLP) or without (NLP). AIMMS 24.6 will contain a new version of our ‘Gurobi link’ that allows you benefit from these Gurobi 12.0 enhancements with your AIMMS projects. Important Notice on Global Nonlinear OptimizationGlobal nonlinear optimization involves identifying the absolute best solution across a complex solution space, often containing multiple local optima. This process is inherently more challenging than local nonlinear optimization, which focuses on finding the best solution within a specific region of the space. As a result, global optimization may require more sophisticated algorithms, computational resources, and time to achieve reliable results. Please keep these factors in mind when using a global optimization solver like Gurobi.More informationAnd if you have any questions, please contact our support team at support@aimms.com.

We're releasing our new and improved Math Program Generator (MPG), designed to accelerate the generation of LP and MIP models in AIMMS 24.6.Key Features and Benefits:Performance Boost: On average, expect 2x faster generation times for LP and MIP models. The impact on total solve time will depend on the model and the data. Compatibility Assurance: The new MPG automatically checks your model's compatibility. In cases where it's not supported, such as with Stochastic Programming and Robust Optimization, it'll seamlessly revert to the old MPG, alerting you (only the app developer, not the end user) with a warning. Flexible Opt-Out: If needed, you can easily disable the new MPG globally or for specific solve requests, giving you full control.Additional Insights: Our extensive testing across hundreds of models showed unchanged results with the new MPG. All future AIMMS versions will be equipped with the new MPG. End-users will not be notified about the MPG switch; we aim for a smooth and invisible transition, with you at the helm. We're proud of this complex project and its potential to reduce waiting times. We encourage you to share your experiences with us—your feedback is instrumental in our ongoing enhancement efforts. For technical details, opt-out instructions, or other inquiries, please reach out to support@aimms.com.

SC Navigator 24.13.1Date November 26, 2024 New Features The user experience for scenario planning in SC Navigator has undergone a significant overhaul. Key enhancements include a more intuitive layout for Scenario, Network Scenario, and Batch Optimization pages, a streamlined process for creating scenarios, improved visibility of scenario contents, and the ability to edit scenarios, among other upgrades. These improvements aim to simplify scenario planning, boosting user efficiency. Read more about the new Scenario, Network Scenario, and Batch Optimization functionality in our documentation. Bug Fixes Transport ratios specified for a period group (a regular group, not a curly bracket group) in the 'Period 2' column of sheet Transport Ratio, were not disaggregated correctly to all periods in that group. In the Load Data dialog page, you can click on Upload Excel File and then cancel the Excel file selection. If after that, you would load a dataset, a data issue was falsely raised about the file not having been read correctly. On page Control Panel, several column headers in the tables have been updated to match with the corresponding attribute names. On the KPI Results dialog page, the label Weight Factor has been renamed to Scaling Factor. On the KPI Results dialog page, the tables only showed data for the active scenario, not for the compared one(s). After loading a dataset, the warning "Attribute names have been replaced with newer names." no longer occurs. This warning will only occur in combination with loading an Excel template. On page Results - Transport, The highlighting in the Transport Ratio Results table didn't work when the data was close to the minimum or maximum value. If you unselected some warehouses on the Warehouse filter, that will also unselect the products that are only used by those warehouses on the Product filter. In that case the Product filter is now also marked as 'filtered'. Previously, when uploading files larger than 128 MB, SC Navigator would become unresponsive. Now you will get an error message indicating the maximum file size has been exceeded. The contents of the file "parquet-results-definition.xlsx" is now consistent with the generated files.

Dear Community,We are excited to share the upcoming improvements to the WebUI, aimed at enhancing its functionality and user experience. Following the recent upgrade to the Table widget, the Table V2, we are now further enhancing its capabilities with:Ability to hide Index information in Row and Column HeadersWe understand that, in some cases, the index information in the row and column headers may be unnecessary or provide little value. To enhance the intuitiveness and user-friendliness of the table headers, we’ve introduced the option to hide these indices. It’s important to note that this change does not affect the data in the grid; only the visibility of the indices in the row and column headers is impacted.This feature has been a long-requested enhancement, as we’ve seen many customers unintentionally experiencing issues with pivoting such indices into the Totals section when it was not possible to hide them.In the Table’s “Index Setting” options editor, there is now the ‘Visibility’ per-index option, which accepts the two literal values ‘Show’ and ‘Hide’, next to accepting an element parameter from the model containing either of those two values.As an illustration of the feature, see this Table widget:In its Index Setting option editor, you can find the Visibility option here:Setting the option to ‘Hide’ leaves us with the Table below, leaving out the not so helpful repetition of ‘SomeValue’ in the row header’s first column:  Additional Annotations on Aggregator CellsWe recognize that while aggregators are applied to the indices, they may not always be relevant for all content in the table. For instance, as shown in the image below, aggregators like Sum and Mean may be appropriate for some data but not for specific averages or percentage data. Similarly, aggregators don't apply to Longitude and Latitude data when listed alongside other information.We’ve now added additional annotations to each aggregator cell, indicating the type of aggregator and the identifier name.With these annotations and application-specific resources, you can now easily target and hide these aggregator cells as needed.As an illustration of the feature, you can apply the following custom CSS to a project that includes the table mentioned above:[data-widget\.uri='COG Detail - Location'] .annotation-total-CoG_Output_Lon .cell-wrapper,[data-widget\.uri='COG Detail - Location'] .annotation-total-CoG_Output_Lat .cell-wrapper { display: none;}[data-widget\.uri='COG Detail - Location'] .annotation-sum.annotation-total-CoG_Output_AverageDistance .cell-wrapper,[data-widget\.uri='COG Detail - Location'] .annotation-mean.annotation-total-CoG_Output_AverageDistance .cell-wrapper ,[data-widget\.uri='COG Detail - Location'] .annotation-sum.annotation-total-CoG_Output_AverageDriveTime .cell-wrapper ,[data-widget\.uri='COG Detail - Location'] .annotation-mean.annotation-total-CoG_Output_AverageDriveTime .cell-wrapper ,[data-widget\.uri='COG Detail - Location'] .annotation-sum.annotation-total-CoG_Output_MaxDriveTime .cell-wrapper ,[data-widget\.uri='COG Detail - Location'] .annotation-mean.annotation-total-CoG_Output_MaxDriveTime .cell-wrapper { display: none;}The table now looks as below  We recognise your excitement about the upcoming features and will keep you updated as the WebUI Library 24.13 version release is made.We believe that these improvements will improve your applications and provide a better overall user experience.Your feedback and suggestions are highly valued. Feel free to explore the new features and share your thoughts with the community. Thanks,Team WebUI.

SC Navigator 24.12.1Date October 11, 2024 New Features A new attribute has been created on the Customer Product Data sheet: ‘Minimum Lead Time Adherence’. This attribute determines what percentage of demand for a given customer, location, product, period combination must be fulfilled within the lead time. When you want the model to take this into account, you have to Relax Lead Time on the Control Panel page. Improvements The custom objectives of type “Risk” are no longer shown on the control panel page. There would never be data for those custom objectives, so keeping it there could lead to potential confusion. The Risk Analysis page is now initialized after a Risk Analysis is loaded. We received some feedback based on the changes implemented in SC Navigator 24.11.1, so we made some minor changes to the behavior of the “Filter by Node Type”: If you (un)select one of the four standard elements (Customer, Supplier, Warehouse, Production), it will (un)select all the groups of the type. This will now also happen if you have elements that do not belong to a subgroup. Elements that don’t belong to any group, can be shown by unchecking every subgroup, while keeping the related standard element checked. Groups for which only part of the locations are shown, will now have a gray background in the checkbox and a tooltip to indicate that only some of the related locations are shown. The full behavior is described in Node Filters. Bug Fixes After loading an Excel template (without saving it as a dataset), the widgets on page Data - Customer did not all update correctly when making demand adjustments. Now, the Selected Demand widget refreshes after each Adjust Demand iteration and the table Demand Adjustment updates correctly as well. For Risk Analysis, Profit Decrease is now the same as Cost Increase in case there is no revenue. Previously in this case the Profit Decrease was opposite to the Cost Increase. The attribute ‘Open As Group’ was not included in the template. Curly bracket support for ‘Mode of Transport’ was not working correctly for Custom Cost attributes. Curly bracket support for ‘To Location’ in Stepwise Transport Cost was not working correctly. When not applying variable cost for a warehouse that is at the same location as a production facility, users could get an error message after optimization: “A problem occurred during the optimization. (…)” Previously, when reading input from an Excel file, an empty cell in the first column of a sheet was not properly handled. SC Navigator would not give an error message, while it stopped reading the sheet. In this new version, it will give an error message, indicating that an empty cell was found. On page Data, in the Data Dashboard widget, Suppliers and Supplier groups were not counted correctly. The geocoding did not work correctly if you specified a Postal Code and Country, but not a country-code. In that case, the model was using a special postal-code setup, while that required a country code. This resulted in inaccurate results; in some cases the returned locations were even outside the requested country. The file “_dataset_info.parquet”, created as part of a results dataset, still contained capitals and spaces in the header names. In newly generated results, these headers will now only use lower case and underscores in the names. Some exported parquet files contained columns starting with “unit_of_” that were not expected. These columns will no longer be generated in exported results. In some cases with minimum production, the model could be incorrectly marked as infeasible or display the message “A problem occurred during the optimization.”

Dear Community,We are excited to share the upcoming enhancements to the WebUI, designed to enrich its features and capabilities.Introducing Table (Table V2) with Enhanced ControlsWe are thrilled to announce the launch of the enhanced Table widget, now equipped with modern option editors that allow per-identifier and per-index configurations. This upgrade provides greater control over settings like Decimal Places, Show Units, and Visibility for individual content identifiers while retaining all the existing Table functionalities.With these enhancements, you can now:Control Decimal Places and decide whether to show or hide units for each individual content identifier.We’ve also introduced the “Visibility” feature for content identifiers. In addition to the current behavior of showing only sparse data, this feature enables:Displaying cells for elements included in the table, even if the data is empty or zero. Hiding or excluding data for specific identifiers within the table.The Visibility feature is particularly useful when working with multiple identifiers in the table. You can control which cells are available for user input based on the elements from certain identifiers, allowing you to selectively enable input cells from other identifiers, thus offering more flexibility in data entry scenarios.These enhancements lay the groundwork for future improvements, such as:Hiding specific indices in table headers. Providing information about multiple selected cells.These updates are available as an experimental feature called Table V2. When the Table V2 feature flag is enabled, any new tables added to your application will use the upgraded version. Existing tables will automatically render with Table V2 as well.If needed, you can safely turn off the Table V2 feature and return to the earlier version, with all your tables rendering in their original state.We encourage you to try out Table V2 and share your feedback with us!Here’s an illustration of the upgraded Table widget. More detailed information about Table V2 and its features will be shared in the documentation.  Upgraded Text WidgetWe are excited to announce that the Text widget has been upgraded with a new version of its underlying library, bringing enhanced content editor controls to further elevate your experience.This upgrade offers new features such as: Headers: Organize your text with various header levels for clear structure. Indentation: Improve readability by indenting text to highlight nested information. Superscript and Subscript: Easily format text to display as superscript or subscript, useful for mathematical expressions and annotations. Code and Comments Support: Embed code snippets and comments seamlessly, aiding in providing clear technical instructions. Importantly, all your existing Text widget content will render seamlessly with this newer version, ensuring a smooth transition.These enhancements offer greater flexibility and precision in presenting information within your applications.Here’s an illustration of the upgraded Text widget content editor controls.  Promoting Widget Named Views feature, Diagram Widget type, and Tabbed Widget type to General AvailabilityWe are excited to announce that Widget Named Views feature, Diagram Widget, and Tabbed Widget types, previously released as experimental features, are now being promoted to general availability!Over the past months, we have gathered valuable feedback and implemented enhancements to these features. Based on your input and our continuous improvements, we are confident that these features are now ready for broader use.  We recognise your excitement about the upcoming features and will keep you updated as the WebUI Library 24.11 version release is made.We believe that these improvements will improve your applications and provide a better overall user experience.Your feedback and suggestions are highly valued. Feel free to explore the new features and share your thoughts with the community. Thanks,Team WebUI.

SC Navigator 24.11.1Date September 13, 2024 Improvements Upon completion of the optimization run, SC Navigator will now popup a system notification, indicating that the solver is ready. This is useful when solving the model takes a lot of time and your are doing something else in the mean time. You can turn this off on the Control Panel page. Please note that the first time, you have to select in your browser that you allow this page to send notifications. On page Results, on the View Options side panel, the behavior of the “Filter by Node Type” has been adjusted. The new behavior is as follows: SC Navigator shows those locations for which all groups, to which this element belongs, are checked. (In the past, it was primarily based on checking/unchecking one group, but it was not clear to the user which group that was.) If you (un)select one of the four standard elements (Customer, Supplier, Warehouse, Production), it will (un)select all the groups of the type. This will not happen if you have elements that do not belong to a subgroup. If you unselect a subgroup, it will not impact the related standard element. (If you do that, item 1 will turn them all off). The table no longer shows an icon for groups that have multiple node types. We changed this behavior to better handle the situation where multiple node types are located in one place, as well as the situation where groups contain multiple node types. For rate card input data, it is now possible to define negative values. This allows for defining a formula for your rate card cost with a negative component in it (e.g. ax - b). The resulting rate card lane unit cost do need to be non-negative. The data validation has been updated accordingly: instead of checking the input data itself, the rate card lane unit cost is calculated and only when that is negative, it will result in an error. We removed some unnecessary blank columns from the Excel Template. Furthermore, on sheets with an ‘Attribute’ column, the ‘Description of the attribute’ column is now aligned with the ‘Attribute’ column. During data validation, when an incorrect date format is used, the following error message will now be displayed: “The attributes ‘Start Date’ and ‘End Date’ need to be valid dates in a date format. That is not the case for date with name …”. The documentation on the Infeasibility Analysis has been improved. You can now read in more detail what you can do to find the cause of an infeasibility. The documentation on the End To End Results has been improved, such that it is more clear what the data in the table represents. Bug Fixes On page Results - Production, in the top-right corner, the Bill of Material filter is now applied to the production volume chart. This allows for a more granular view of production data based on specific Bill of Materials produced in a production resource. Previously, internal flows could occur at locations with two or more warehouses, even if those warehouses lacked inventory capabilities and the location did not have production facilities. This is no longer possible, as internal flows are now restricted under these conditions.

SC Navigator 24.10.1Date August 20, 2024 New Features A new attribute has been added to the Supplier, Supplier Product, Warehouse, Warehouse Product and Production sheets: Open As Group. This attribute allows you, in multi-period models, to indicate that the entity needs to be open or closed for the complete period. There are two benefits compared to how it could be done previously: It it easier to specify and it leads to faster performance. Improvements The documentation has been restructured for easier navigation. Data Validation will raise an error when the input data includes demand for a product that has no available supply, production, or opening inventory. For some of the rate card data validations, the maximum number of detailed data validation messages has been set to 10000 in order to limit time spent on data validation. In the Node Type filters, all customer groups are now by default colored with color “Customer Default”. The color of the groups can still be changed on the ‘Customize Nodes’ dialog page that you can open from the Map widget action ‘Customize Nodes’. Bug Fixes On page Results - End to End, the direct transport lanes (from supplier to customer) were not visible on the map. When running the infeasibility analysis for a model with multi-step suppliers that do not have capacities specified, the warning message “A problem occurred during the optimization” could appear. When running the infeasibility analysis for a model with customers that have attribute Maximum # of Source Locations set, the message “No solution found - The model is still infeasible” could appear. Now, this constraint is also handled properly in the Infeasibility Analysis. For curly production group data, previously the app raised a data validation warning if any step in the individual productions had missing availability data. However, it should only need the availability data for the first step. In some rare situations, a dataset saved with the previous version of SC Navigator, could no longer be loaded. This has been fixed in this new version of SC Navigator, but it requires you to save the dataset again, from the template. With this release a new version of Inventory Planning is released as well. In the Inventory Planning app, when exporting a scenario, the Work in Progress data is now saved to the data lake as well.

SC Navigator 24.9.1Date July 30, 2024 New Features If the model has Data Separation and the user is connected to multiple business units/groups, SC Navigator will now show a new item (Business Unit) on the status bar. Users can switch between their different groups using this item. Improvements We have improved the loading of results, for results saved in this version. The results of the selected CoG Trade-Off Analysis runs can now be exported. In “System Configuration”, we have removed the “Conversion to Data Lake” page as it is no longer needed. Additionally, the ability to change the data source by clicking on the status bar “Data Source” item has been disabled. A new option has been added to the Whiteboard Edit Node Info dialog, allowing users to disable the creation of groups for nodes that contain a single Supplier, Production, Warehouse, or Customer. The exported parquet files have new attributes names going forward, to allow for better support by data platforms like BigQuery and Databricks. The new attributes are all lower case letters (a-z) and underscores, so no more spaces and parentheses. In the generated input definition file “Parquet File Definition SC Navigator.xlsx” (see Download Parquet File Structure) and the generated output definition file “parquet-results-definition.xlsx”, both the old and the new attribute names are present. SC Navigator input parquet files support both names right now, while output files will only use the new names. Bug Fixes When running Trade-Off Analysis or CoG Trade-Off Analysis simultaneously with a Location Risk Analysis, the error message: “awf.data.aimms.session: There already exists a file or directory named…” will no longer appear.

Dear Community,We are excited to announce the release of AIMMS WebUI Library 24.9.1 version, featuring several exciting new enhancements and improvements designed to elevate your user experience. Here's a detailed overview of what's new: New “Iframe” widget type We have introduced a new widget type, called “Iframe Widget”. This widget makes it possible to embed external content, such as reports and other web pages, directly into your AIMMS WebUI application. For details about this widget, please see the documentation. Here is an example of a Power BI report embedded through the Iframe widget on the AIMMS WebUI page.   Support for “End-User Mode” preview We have learned that previewing the WebUI application from the end users' perspective while building or modifying it is neither quick nor convenient. To address this, we have introduced a new "End-User Mode Preview" button in the page header section. Clicking this button opens the current WebUI page in a new tab, displaying it from the end users' perspective.   Support for WebUI browser notification  The AIMMSWebUI library has been enhanced with a new   webui::RequestShowNotification(message, title)  procedure. This feature allows the WebUI to trigger operating system notifications directly from the browser window in which it is running. An example use case is that you can call this procedure after a solve action in an AIMMS procedure to notify the user that the optimization has been completed. Please note that both your system and the browser settings are configured to allow notifications for your WebUI application. See the documentation for more details.   Diagram widget enhancement: Support for Arcs restriction  We have recognized the importance of enhancing the customer experience by including restrictions on drawing arcs from certain source or destination nodes. This functionality is now achievable using the domain condition of the arc's identifier. Specifically: If a connection between two nodes is not within the index domain, the target node will not display any target feedback (e.g., a blue rectangle). If a certain node cannot have any outgoing connections, it will not be possible to create a new arc starting from that node.   We hope these features enhance your applications and contribute to an even better user experience. Your feedback and suggestions are highly valued, so please share them in the comments. Thanks,Madhu KrishnappaAIMMS WebUI Product Owner

SC Navigator 24.8.1Date July 19, 2024 Improvements The option ‘Results visible for everyone’ is now available when saving CoG Trade-Off results. On page Data - Production, 2 new tables were added with input attributes that were already in the template, but not yet visible in the app: Bill of Material Data and Production Routing Data. On page Data - Other, 3 new tables were added with input attributes that were already in the template, but not yet visible in the app: Bill of Material Groups, Mode of Transport Groups, and Use Description. On the Whiteboard, transport lanes that are not permitted, can no longer be drawn. E.g. lanes from warehouses to suppliers. Bug Fixes In version 24.7.1, attribute Inter Resource Number of Trips was added to sheet “Inter Resource Transport”, while it should have been added to sheet “Transport Cost”. It is now in that sheet, and the sheet “Inter Resource Transport” is not longer in the results file.

Dear Community,I’d like to highlight the WebUI enhancements introduced in the recent WebUI library releases. Here's a quick overview: Enhancements to Table widgetSupport for Store-Focus and Item-Actions on Header cellsThe store focus mechanism has been extended to include row and column header cells. Now, when you click on a row or column header cell, the element parameters of the indices present in the clicked header cell will be updated.Additionally, the Table widget now supports item actions when clicking in the row or column header of the table. For more details, refer to the documentation.Support for HTML data on TableBased on user feedback, we understood the need for presenting HTML content within tables. Previously, string content containing HTML tags was rendered as plain text, limiting the ability to display formatted information.To address this, we introduced the webui::IsHtml annotation for String parameters. When set to True, the Table widget interprets HTML tags within the content, rendering it according to the markup instructions. This results in properly formatted text being displayed, enhancing the presentation of table data. For more details, refer to the documentation.Additionally, we now support custom display text, including HTML content, for Identifiers and Indices. For more detailed information, refer to the documentation.Enhancement to the Copy-Paste functionalityThe Table widget now allows copying content from a single cell and pasting it onto a block of cells or multiple scattered cells.Support for Table filtering on Dialog pageIt is now possible to use Table filtering on Table widgets that are displayed on a Dialog page. New “Tabbed” widget typeWe have created a new widget type, called the ‘Tabbed Widget’. This widget allows you to show multiple pages inside a single widget, as separate tabs. This can serve as a cleaner solution than using hidden widgets on a page, as it allows you to display anything you need within the same space on a WebUI page, depending on the context. For full details, please see the documentation. OthersPre-defined identifier webui::ClientBrowserLanguageThe WebUI library now includes the webui::ClientBrowserLanguage pre-defined identifier, which provides information about the customer’s browser language. App developers can leverage this information to deliver language-specific content in the UI. For details, please see the documentation. We hope these features enhance your applications and contribute to an even better user experience. Your feedback and suggestions are highly valued, so please share them in the comments. Thanks,Madhu KrishnappaAIMMS WebUI Product Owner