RailWorks 23.0.1 is now available ( 24 January 2023). This version of RailWorks is intended for use with FlexSim 2023. All versions can be found in the Downloads section of your FlexSim account on the 3rd party modules tab. Please do not hesitate to report any bugs, usability improvements and feature requests to [email protected] About RailWorks The FlexSim Brasil RailWorks module consists of premade custom objects, designed to represent a real environment for the Rail problem modeling, with less configuration. Our approach is to unite 3D modeling with the Process Flow functionality, allowing object configuration and visualization through the native 3D FlexSim solution, and the rail system events to be triggered by the Process Flow, using not only defaults FlexSim Process Flow activities, but also new ones developed by our team. For any questions, please email [email protected] Release Notes The following is a list of features and fixes that have been included in the latest RailWorks releases. RailWorks 23.0.1 (24 January 2023) Release for FlexSim 2023.0 RailWorks 22.2.3 (24 January 2023) Bug Fix: Fixed various bugs affecting the locomotive movement. Feature: Added automatic train detection and anticipation of movement. Feature: Added a wait logic on locomotive to continue with movement when rail is not on use.RailWorks 21.2.4 Feature: Added GIS Portal object for integration with GIS Map. Release for FlexSim 2022 Update 2 All bug fixes in RailWorks 21.2.4 below. RailWorks 22.2.2 (12 December 2022) All bug fixes in RailWorks 21.2.3 below. RailWorks 22.2.1 (25 November 2022) Release for FlexSim 2022 Update 2 Bug Fix: Fixed various bugs affecting the definition of traveling routes Bug Fix: Fixed various bugs affecting the locomotive and wagon movement amongst the rail tracks Bug Fix: Fixed a bug affecting the usage of multiple locomotives at same railway Bug Fix: Fixed a bug affecting the offset distance in Control Points Bug Fix: Fixed a bug affecting the Decouple activity and Couple by another Locomotive Retroative Release: New versions released with bugs fixed from 2021.2 to 2022.2 All bug fixes in RailWorks 21.2.2 below. RailWorks 22.1.4 (24 January 2023) All bug fixes in RailWorks 21.2.4 below. RailWorks 22.1.3 (12 December 2022) All bug fixes in RailWorks 21.2.3 below. RailWorks 22.1.2 (23 November 2022) All bug fixes in RailWorks 21.2.2 below. RailWorks 22.1.1 (26 July 2022) Release for FlexSim 2022 Update 1 Refactor: Changed the model limit control and system functionality Feature: Added the PreCreate activity in ProcessFlow Bug Fix: Fixed various bugs affecting the locomotive and wagon movement. Bug Fix: Fixed a bug affecting the model limit creating new models. Bug Fix: Fixed a bug affecting the model limit window with multiple modules installed. All bug fixes in RailWorks 21.2.1 below. RailWorks 22.0.4 (24 January 2023) All bug fixes in RailWorks 21.2.4 below. RailWorks 22.0.3 (12 December 2022) All bug fixes in RailWorks 21.2.3 below. RailWorks 22.0.2 (23 November 2022) All bug fixes in RailWorks 21.2.2 below. RailWorks 22.0.1 (26 July 2022) Release for FlexSim 2022 Refactor: Changed the way that Rails can be resized and moved. Feature: Added the RailWorks manual to FlexSim. Feature: Added travel offset to the MoveTrain activity. Feature: Added speed profiles to the Locomotive. That means that you can now set the speed of a Locomotive based upon if it is coupled to a Wagon or not. Feature: Added acceleration and deceleration of locomotives. Feature: Added RailwayTimetable, providing observability for the model as it saves every important event in RailWorks, like the time when a locomotive arrived at a station, as an example. Feature: Added a new model to the Stations: Fuel Station. Feature: Added a new model to the Stations: Flow Station. Feature: Integration with FloWorks. Feature: Added loading modes to thee LoadWagon activity. Bug Fix: Fixed various bugs affecting the locomotive movement. Bug Fix: Fixed a bug affecting the load and unload actions. Bug Fix: Fixed a bug affecting the Experimenter. All bug fixes in RailWorks 21.2.1 below.

17 Mar: Bug fix releases 22.0.5, 22.2.3 and 23.0.1 are now available. FloWorks 23.0.0 is now available (06 January 2023). This version of FloWorks is intended for use with FlexSim 2023. If you are using FloWorks with FlexSim 2022 (LTS) you can upgrade to FloWorks version 22.0.4. If you are using FlexSim 2022 Update 2, you can upgrade to FloWorks version 22.2.2. All versions can be found in the Downloads section of your FlexSim account on the 3rd party modules tab. Please do not hesitate to report any bugs, usability improvements and feature requests to [email protected]. About FloWorks FloWorks is a 3rd party module developed and maintained by Talumis BV (talumis.com). It provides faster and more accurate modelling and calculation of fluid systems than the default FlexSim fluid library. It is especially useful within the oil, gas, and bulk industry both for production and supply chain optimization. This module requires a FloWorks license with active maintenance. For any questions, please email [email protected]. Release notes FloWorks 23.0.1 All bug fixes in FloWorks 22.0.5 below. FloWorks 23.0.0 (6 January 2023) Improvement: FlowConveyor snapping improved between conveyors. Improvement: Made FlowConveyor properties available in property tables. Improvement: Extra FlowConveyor options added, such as virtual length support. Improvement: Compare Properties enabled for all active FloWorks objects. Improvement: Toolbox items "Level Triggered Event" and "Time Series" support disabled icon. Improvement: MassFlowConveyor supports stacked products. All bug fixes in FloWorks 22.0.4 below (please note the Known Issues information there). FloWorks 22.2.3 All bug fixes in FloWorks 22.0.5 below. FloWorks 22.2.2 (6 January 2023) All bug fixes in FloWorks 22.0.4 below. FloWorks 22.0.5 Bug fix: Content issues when using warmup time. Bug fix: Input and output trigger ammount issues when using warmup time. Bug fix: Solver crashed with (large) networks that contains cycles. Improvement: Complete new solver mode added, that improves solver times. Improvement: OnEmpty and OnFull are now fired when setting the content using script or ProcessFlow activity. FloWorks 22.0.4 (6 January 2023) Bug fix: Solved FlexSim crashing when FlowControl had invalid references in member list. Bug fix: Legacy flow conveyors were (silently) failing in some cases. Bug fix: Flow Amount for ItemToFlow and FlowToItem can be set correctly. Bug fix: When copying an object it sometimes lost its Flow Control reference. Bug fix: Requesting statistics through FlowObject.stats raised an error. Bug fix: When setting flow content through code the state is now correctly updated. Improvement: Small wording fixes in the user manual. Improvement: Updated tutorials. Improvement: Updated several outdated or incorrect tooltips.

This small model shows how to batch various parts together to form 'valid' combinations as they become available. This differs from a regular combiner where the component quantities are set in advance of the components being accepted in the combiner (often based on the type of item on port 1 entry). The valid combinations are shown as the quantities required for a number of products in a global table "ProductPartQuantitiesGrid": By referencing the first picture and this table, you may be able to see that the model first constructs 4x Product2 followed by one product1 and a Product3. In the background process we are creating a token for each product which is then trying to pull all the parts needed while competing with the other products. This part of the process could be constrained in some way, for example where there is a target for the number of each product to produce over a time period. So these tokens are being created in the Object Process Flow of the object we're calling OpportunityCombiner at time zero based on the table shown above: Instead of the normal array generation this model creates a table label of the required parts for a product and stores it on the token. For Product1 that looks like this: Tables aren't quite fully supported as labels yet so the syntax is a little odd when using them - in this case we do it like this: Table(token.partsTable)[1]["Part"]  // evaluates to 'F' Setting the labels up so that syntax works is a bit more complex. Note that the partsTable label is actually a pointer to the data table label on the token - called partsTableData. To get the view shown above you need to right click on the label partsTabelData and select "Explore As Table". Hopefully in the future this may be more streamlined if more people start using labels as tables. The grid table doesn't play nice with sql, so another table creates itself at reset with a structure that is sql friendly: That means the label table can be created with this query: SELECT Part,Quantity FROM ProductPartQuantities WHERE Product=$1.product What remains for the product token just involves getting the parts (a subflow) and them moving the array of all items to the combiner (a queue in the example); stacking them together and releasing to the conveyor before looping back to try and produce another. Below you see the main flow with four tokens - one for each product defined in the grid. The subflow to get parts reads the token's table of parts for its product, and tries to get the correct quantities for each. This is similar to @Jordan Johnson 's solution for pulling from multiple lists, but is instead considering the table of parts from one list rather than arrays of resource lists and quantities. The key aspects of this flow are that 1. the first loop in the check section leaves the parts on the list, while the 'commit' section removes them 2. we exit the check loop by using the pull timeout when we fail to pull the required quantity of a part type 3. those that fail listen for pushes to the parts list 4. success full product pulls insert the items pulled to the tokens label 'allItems' for later use. Attached is the model. It should be relatively simple to transfer the process and tables to another model. OpportunisticCombiner.fsm

This Kiva system demo model showcases some of the new AGV/AMR features that were added in FlexSim 2023, including new events and parameters to help with deadlock and allocation failure, and dynamic barrier management. You can update the layout through five parameters, and then click the “Build” button to re-build the system. FlexSim-2023-Kiva-System-Demo.fsm

Download the files Download FlexSim’s latest lmtools-related files here: https://flexs.im/lmtools-download You can browse archived versions of both lmtools and lmadmin here: https://flexs.im/licenseserver-archive Extract the download Once the download is complete, right-click the .zip archive and choose to Extract All… Save to a folder directly on your root drive. Your lmtools download folder Your extracted folder should end up looking something like this: In later instruction steps, any time we refer to the downloaded files, these are the files we're talking about. Note on location Technically you could save your download files in any folder, but we recommend right at the root drive level for convenience. If you choose to save your download folder in an alternate location, please make sure that the directory path doesn't include any folder named "FlexSim". Since Windows files are not case sensitive, this prohibition also applies to variations like "Flexsim" or "flexsim". We have seen instances where some versions of FlexNet licensing encounter errors when the name of the vendor daemon ("flexsim" in our case) is the same as a folder in the path. A folder that includes "FlexSim" as part of a larger name is fine. For example "FlexSim_Licensing" is a fine folder name. Examples of good paths: C:\FlexSim_LMTOOLS C:\licensing\vendors\FlexSim_LMTOOLS\ C:\Program Data\FlexSim_License\ Examples of bad paths (incompatible folder names bolded): C:\flexsim\ C:\licensing\vendors\Flexsim\ C:\Program Data\licensing\FlexSim\files\

Have you received this licensing error? Operations error: 7032 Invalid fulfillment ID: FID_ ... (entire fulfillment ID listed) You may encounter this error during an attempted license return. This error means that the license server has no record of your license activation, and therefore is not able to recognize the return action from your unknown activation. This error should only be encountered under a few rare circumstances: 1. Rollback on FlexSim's main license server FlexSim's main license server could be rolled back to an earlier time due to a necessary database restoration in order to mitigate database corruption or other unforeseen issues or circumstances. License actions, such as license activations or returns, that occurred after the last viable backup was saved, but before its restoration, will be lost. The solution for any license affected will consist of one or both of the following: If an activation occurred during the lost time period you would need to manually remove any un-returnable fulfillments. Standalone - Delete fulfillment License Server - Delete fulfillment If a license return occurred during the time period, you should contact your local FlexSim distributor to request a force-return. Explain the error and this situation. 2. Change to FlexSim's licensing infrastructure Your FlexSim product has reached End-of-Life and the license server under which your license was originally activated has been retired. This situation is outlined in FlexSim's End User License Agreement > Software End-of-life. As of this writing, FlexSim has never retired any of our FlexNet licensing infrastructure and we currently have no plans to do so. This item is included here for completeness' sake and in the event that such future licensing changes occur. If you are using software past its End-of-Life date and you think this problem may be affecting you, please contact your local FlexSim distributor.

You may find occasion to check the status of your licenses. Perhaps you're trying to diagnose some issue, or you want to check which license is activated, or how many seats. Here we explain how to view the licenses activated to your license server, and their status. Assumed configurations All steps below assume that you followed the installation instructions as described in our license server installation instructions, and that all FlexSim's license server files were extracted to the location C:\FlexSim_LMTOOLS. Throughout these instructions we will reference files inside that folder. View License Rights On your license server, run the flexsimserveractutil.exe program (C:\FlexSim_LMTOOLS\flexsimserveractutil\flexsimserveractutil.exe) by right-clicking and selecting Run as Administrator. In the FlexSim ServerActUtil program, go to Tools > View License Rights. An information block is printed for each license activated to your license server. You will find listed the unique fulfillment ID for each activation, along with the license code (also called an activation ID and listed here as entitlement ID), its status (fully trusted/enabled, broken, etc.), the number of seats activated, and for timed licenses, an expiration date. Take Action Check the article Licensing Procedures under the Network Licensing heading for instructions if you need to repair or return your license or do any other sort of license maintenance.

FlexSim 2023 is now available for download. For more in-depth discussion of the new features, check out the official software release page: FlexSim 2023: Enhancements to Bonsai Integration (AI), Emulation, AGV/AMR, and more You can view the Release Notes in the online user manual. FlexSim 23.0.0 Release Notes If you have bug reports or other feedback on the software, please email [email protected] or create a new idea in the Development space.

This supply chain demonstration model shows both a visual and statistical representation of a company's stock and backorder from day-to-day. The goal of the model was to predict shortages and backorder trends due to COVID-related disruptions. FlexSim's 3D view is used in a novel way to visualize the current stock and demand for each product. Each queue represents a different product SKU and each box represents a product unit, with red indicating product demand and blue indicating product availability. This model also contains a comprehensive set of dashboards to help visualize and interpret the data. Logistics_Supply-Shortages-Stockouts_v22-2.fsm

A number of questions on the forum involve racks being service by a combination of shuttles and elevators. There are solutions involving network, Astar and AGV navigators, but for this example we’re just going to use TaskExecuter FlowItems and conveyors. The elevator system in particular, as described to me, seemed it would benefit from the flexibility conveyors offer – particularly spacing options, and the possibility of having dog/power-and-free based travel. For the pick face we can just use the slot and item locations to give the task executers travel command, and we can use kinematics for loading and unloading tasks. This removes the need for network nodes or control points at each location and allows fine positioning of a ‘two spot’ shuttle in front of the slot. The system has been put into a container to represent the cell/aisle and it is this object that is the instance member of the ShuttleSystemProcess process flow. The cell is designed to be duplicated with each cell becoming a new member instance of the single process flow. It comprises two racks, two elevators (conveyor loops), and a shuttle return queue (also a conveyor but with no roller visual). The system assumes that by the time an inbound item arrives at the pickup position it has been assigned a slot in one of the racks in the cell – so you should assign a slot in the normal way before it reaches a shuttle. You can additionally request items for picking out of the racks by pushing the item to the global list ItemsToPick. Currently each shuttle will store and/or pick one item in one trip with a dedicated position for each. When doing both in a single trip, the order in which this happens will depend where along the level the slots are located. In the event that there are no remaining tasks but items still need to exit the cell, the shuttles at the front of the queue will be asked to circulate empty through the system, thereby allowing the outbound items to advance to the exit position. The number of shuttles in the system is a process flow variable. In the example system there are elevators at each end of the rack(s) with a number of carriers to transport shuttles to the levels. Both elevators have a process flow variable for the number of carriers to be generated. Shuttles are not allowed to pick from the same level at the same time but in order to keep the up-elevator moving the carriers can unload the shuttle to the level even if another is active on that level. The shuttles only travel along the face of the rack in one direction towards the down-elevator and once are collected by a carrier the next shuttle on that level can start its operations. It is possible to run the system with only one rack should you wish to view the operations without the second rack obscuring your view. Since different applications will use different rack dimensions the cell has a label method called “configureToRack” which will align the conveyors and decision points to Rack1 based on the level heights and size of the racks that the user has set for Rack1. There may be some limits to very small sizes when the conveyor decision points overlap. The second rack will be configured during this method call to mirror Rack1. Here’s an example invocation of this method for an instance of the cell: Model.find("RackShuttleSystem").as(Object).configureToRack The shuttles need levels to be the same height along the length of the rack. Some effort was made to configure the system based on the shuttle and carrier sizes, so you can try adjusting those to suit your needs and hopefully the alignment will work as needed. The elevator conveyor and shuttle speeds are not set by the alignment method so you can edit those in the usual way. This is an example for both learning and perhaps as a starting point for any project should you find the approach suits your application, modelling style and skills. ShuttleLiftAndRack.fsm Time taken: 1 day to build the working model - plus another to work around holes api for auto-alignment code. 17Nov Updated: to initalize shuttles at the load point (via fast entry) added shuttleQheight label for use to set the returnQ height in the cell (used by the alignment method) added a process flow variable 'shuttleLoadTime' for the time to un/load items. aligned shuttle kinematics to the speed and acceleration of the TE FlowItem.

Remembering the proper credentials To log in to lmadmin's Administration area you need know the port number your license server manager is hosting on and your lmadmin admin password. lmadmin's default port number for serving its web-based user interface is 8090. There is a very good chance that your system is hosting lmadmin on its default port. On your license server, open a browser and go to http://127.0.0.1:8090 to see if this will open lmadmin's web-based interface. The default login information for lmadmin's Adminstration area is username admin and password admin. Upon your first logging in to the Administration area you would have been prompted to create your own new password consisting of at least 8 characters. If you have forgotten either the port number or your admin password, there is unfortunately no way to recover these. You will need to uninstall, then reinstall lmadmin. If you do not wish to do so at this time, you should be able to start serving your upgraded FlexSim licenses by restarting the lmadmin64 Windows service. Logging in to lmadmin Use a web browser to connect to the lmadmin service at https://127.0.0.1:8090 (specify a different custom port besides 8090, as necessary). The FLEXnet Publisher interface should open. Click on Administration to sign in. After logging in to the Administration portal, click the Vendor Daemon Configuration tab on the bottom left. Click on the flexsim daemon. Reread the license If there is a Start button, that means that your flexsim vendor daemon is currently stopped. Press the Start button to start the vendor daemon using your upgraded licenses. If there is a Reread License Files button, that means that your flexsim vendor daemon is currently running, and serving the old licenses. Press the Reread License Files to start serving your newly activated and upgraded licenses.

FlexSim 2023 Beta is now available. FlexSim 23.0.0 Release Notes To get the beta, log in to your account at https://account.flexsim.com, then go to the Downloads section, and click on More Versions. It will be at the top of the list. The More Versions button does not appear when logged in as a guest account. The beta is available only to licensed accounts and accounts that have a license shared with them. Learn more about downloading the best version of FlexSim for your license here. If you have bug reports or other feedback on the software, please email [email protected] or create a new idea in the Development space.

The instructions below are for offline/Manual XML licensing. If your server successfully connects to the Internet and to FlexSim's main license server, you can try our simpler online license activation instructions. Getting ready If you're configuring a new license server, please stop now and follow the complete license server installation instructions. This shorter guide just focuses on one piece of the installation instructions: license activation. We've broken the activation step out into this standalone article for convenience in subsequent licensing procedures, like upgrading your license server. These instructions assume that: you followed the steps outlined in our license server installation instructions including download of all required files and installation of the FlexNet Licensing Service; FlexSim's license server files were extracted to the location C:\FlexSim_LMTOOLS. When should I use XML/offline licensing? If your license server cannot connect to the Internet or is blocked from direct communication with FlexSim's license activation servers then you will need to activate your license manually . This article guides you through the manual activation steps. If you're not sure, go ahead and try an online activation first. Activating your license server online is faster and simpler. If online activation fails due to communications on your license server being blocked, you can fall back to this offline activation guide. Activate your license NOTE: If this is the first time a license has been activated to this license server you must first configure trusted storage. On your license server, run the flexsimserveractutil.exe program (C:\FlexSim_LMTOOLS\flexsimserveractutil\flexsimserveractutil.exe) by right-clicking and selecting Run as Administrator. Create manual activation requests In the FlexSim ServerActUtil program, go to Tools > Manual Activation > Generate Request. Enter a valid Activation ID. Enter a Count (seat quantity) for your license. NOTE: If you have a 20-seat license but want to host 12 seats on this server and 8 seats somewhere else, you can do so. Simply enter 12 for the Count value. Browse to select an Output File. Press Generate. You've just saved a new XML activation request to the location you selected. Repeat steps 1-5 above to generate an activation request for all license codes you intend to activate on this license server. Submit your manual activation requests Transfer your XML activation requests to a computer with Internet access. From your Internet-connected computer, open a web browser and login to your FlexSim Account. Click the Licenses link in the header, then choose Manual XML in the Licenses submenu. Upload your XML files by dragging them onto the drop zone. Your uploaded XML requests will be processed. Upon completion, you will be prompted to download each XML response. Process your manual activation responses Transfer your downloaded XML activation responses to the offline license server you are licensing. In the FlexSim ServerActUtil program, go to Tools > Manual Activation > Process Response. Browse to an XML activation response file. Press Process. FlexSim should give you an indication of successful processing of your activation, and activation for that XML request will be complete. Successfully Processed Response Repeat steps 1-5 to process the XML activation responses for any other XML activation requests. Is this a license server upgrade? If this license activation is part of upgrading the license on your license server, don't forget to reread license files. If you have any questions or problems, please search our Answers Community for possible solutions. There is a good chance someone else has already asked your question. Still not finding what you're looking for? Submit a new question and we'll check it out. If you're including any confidential information, such as license codes, be sure to mark your question as private! You can also contact your local FlexSim distributor for live phone, web, or email help.

Have you received this licensing error? An error occurred in the activation request Operations error: 7174 Only deployed entitlement line item can be fulfilled. You may encounter this error if your license code is no longer valid or is in need of support. Here are some common scenarios where this might happen: If this was a timed license that has expired, it is no longer viable and was likely obsoleted. If the license was upgraded, you need to make sure you're using the latest version of the activation ID, as any older versions of the license code will not work once an upgrade of the same license has been used. If the license model was changed from standalone to license-server (or vice-versa) you may be trying to use an old license that was replaced. If your license was put into a support state and was not changed back. If you are encountering this error, please start a new Private Question and include your activation ID. We'll be able to look up the specific situation for your license. Or you can reach out to your local distributor for direct phone, email, or web support.

Introduction Several times per year we release a new feature-version of FlexSim Simulation Software. In order for your PCs to be able to run a licensed version of the upgraded software, you'll need to upgrade your standalone FlexSim license. Licenses with a current maintenance subscription are eligible to be upgraded to the new version. If you don't understand how licensing works for different FlexSim versions, please review our Answers article FlexSim Version Numbering. Overview After installing your new version of FlexSim, there are 3 main steps to upgrading your standalone license: Return the licenses you intend to upgrade Upgrade your licenses Activate the upgraded license Several of these steps have their own fully documented procedures. We'll link you to those resources below. 1. Return the licenses you intend to upgrade The steps to return a standalone license are fully documented. Choose the link below that best matches your needs, depending on whether your PC can connect to the Internet: Standalone - Return - Online Standalone - Return - XML / Offline Be sure to return ALL licenses you wish to upgrade. 2. Upgrade your licenses NOTE: Licenses with expired maintenance will not upgrade. Timed licenses do not upgrade. Only permanent (not timed) licenses under current maintenance can be upgraded. Log in to your FlexSim Account. If you were already logged in to your FlexSim Account, in the top navigation menu hover over your initials icon and choose Reload Account. Now in the top navigation menu, choose Licenses > List. Check that the available seat count is equal to the total. All of a license’s seats should be returned for it to upgrade. Click on the Upgrade Licenses button. If you have several licenses to upgrade and all are owned by or shared with your FlexSim Account, they will all be upgraded at once. Please be patient while the upgrade process works in the background. When the page refreshes, eligible licenses will have a new activation ID for the latest version of the software. Your license code indicates its version at the end of the code to help you know what versions your license will properly activate. Review license code format. You'll be able to use the upgraded license codes in the next step. 3. Activate the upgraded licenses The steps to activate a standalone license are fully documented. Choose the link below that best matches your needs, depending on whether your PC can connect to the Internet: Standalone - Activation - Online Standalone - Activation - XML / Offline If you have any questions or problems, please search our Answers Community for possible solutions. There is a good chance someone else has already asked your question. Still not finding what you're looking for? Submit a new question and we'll check it out. If you're including any confidential information, such as license codes, be sure to mark your question as private! You can also contact your local FlexSim distributor for live phone, web, or email help.

FloWorks 22.2.0 is now available (31 August 2022). This version of FloWorks is intended for use with FlexSim 2022 Update 2. If you are using FloWorks with FlexSim 2022 Update 1, please use FloWorks version 22.1.1. If you are using FlexSim 2022 (LTS) please use FloWorks version 22.0.2. All versions can be found in the Downloads section of your FlexSim account on the 3rd party modules tab. Please do not hesitate to report any bugs, usability improvements and feature requests to [email protected]. About FloWorks FloWorks is a 3rd party module developed and maintained by Talumis BV ( talumis.com). It provides faster and more accurate modelling and calculation of fluid systems than the default FlexSim fluid library. It is especially useful within the oil, gas, and bulk industry both for production and supply chain optimization. This module requires a FloWorks license with active maintenance. For any questions, please email [email protected]. Release notes FloWorks 22.2.0 New: Added a Flow Gauge object to measure and visualize the flow through a connection New: Added a Time Series object to the Toolbox as a source of daily, weekly or monthly changing values Improvement: Added several alternative shapes for Flow Source such as Plant and Well Improvement: Level Triggered Event now has an OnTriggerFired event that ProcessFlow can await Bug fix: Some additional issues with incorrect scaling when not using meters Bug fix: Flow tank level triggers issue with multiple levels (not) firing All bug fixes in FloWorks 22.0.2 below. Backwards Compatibility Note: The following change may change the way updated models behave. Flow Impact Event has been deprecated and may be removed in the future. Picklist options for applying impact factors have been added to FlexSim's own MTBF/MTTR and Timetable. As an improvement, the same picklist options are also available in Down Behaviors. FloWorks 22.1.1 All bug fixes in FloWorks 22.0.2 below. FloWorks 22.1.0 (12 May 2022) All bug fixes in FloWorks 22.0.1 below. FloWorks 22.0.2 Bug fix: FlowMixer.loadRecipe can handle re-ordered product tables Bug fix: Statistics are now correctly initialized for flow tanks created during run. FloWorks 22.0.1 (12 May 2022) Added support for Object Property Tables Bug fix: incorrect MassFlowConveyor content Bug fix: LoadingPoint issue with not-released positions (and status) Bug fix: Object created at incorrect scale when not using meters

RailWorks 22.1.0 is now available ( 26 July 2022). This version of RailWorks is intended for use with FlexSim 2022. All versions can be found in the Downloads section of your FlexSim account on the 3rd party modules tab. Please do not hesitate to report any bugs, usability improvements and feature requests to [email protected] About RailWorks The FlexSim Brasil RailWorks module consists of premade custom objects, designed to represent a real environment for the Rail problem modeling, with less configuration. Our approach is to unite 3D modeling with the Process Flow functionality, allowing object configuration and visualization through the native 3D FlexSim solution, and the rail system events to be triggered by the Process Flow, using not only defaults FlexSim Process Flow activities, but also new ones developed by our team. For any questions, please email [email protected] Release notes RailWorks 22.1.0 Release for FlexSim 2022 Update 1 Refactor: Changed the model limit control and system functionality Feature: Added the PreCreate activity in ProcessFlow Bug Fix: Fixed various bugs affecting the locomotive and wagon movement. Bug Fix: Fixed a bug affecting the model limit creating new models. Bug Fix: Fixed a bug affecting the model limit window with multiple modules installed.

RailWorks 22.0.0 is now available ( 25 July 2022). This version of RailWorks is intended for use with FlexSim 2022. All versions can be found in the Downloads section of your FlexSim account on the 3rd party modules tab. Please do not hesitate to report any bugs, usability improvements and feature requests to [email protected] About RailWorks The FlexSim Brasil RailWorks module consists of premade custom objects, designed to represent a real environment for the Rail problem modeling, with less configuration. Our approach is to unite 3D modeling with the Process Flow functionality, allowing object configuration and visualization through the native 3D FlexSim solution, and the rail system events to be triggered by the Process Flow, using not only defaults FlexSim Process Flow activities, but also new ones developed by our team. For any questions, please email [email protected] Release notes RailWorks 22.0.0 Release for FlexSim 2022 Refactor: Changed the way that Rails can be resized and moved. Feature: Added the RailWorks manual to FlexSim. Feature: Added travel offset to the MoveTrain activity. Feature: Added speed profiles to the Locomotive. That means that you can now set the speed of a Locomotive based upon if it is coupled to a Wagon or not. Feature: Added acceleration and deceleration of locomotives. Feature: Added RailwayTimetable, providing observability for the model as it saves every important event in RailWorks, like the time when a locomotive arrived at a station, as an example. Feature: Added a new model to the Stations: Fuel Station. Feature: Added a new model to the Stations: Flow Station. Feature: Integration with FloWorks. Feature: Added loading modes to thee LoadWagon activity. Bug Fix: Fixed various bugs affecting the locomotive movement. Bug Fix: Fixed a bug affecting the load and unload actions. Bug Fix: Fixed a bug affecting the Experimenter. RailWorks 21.2.0 Release for FlexSim 2021 Update 2 Feature: Added a new routing algorithm option, focused on preventing train collisions (Requires Python installed). Bug Fix: Fixed a bug in the model limit. RailWorks 21.1.0 Release for FlexSim 2021 Update 1 Feature: Added trigger - onCreate - to the SourceTrain object. Feature: Added triggers - onEntry, onExit - to the Rail object. Feature: Added triggers - onFuel, onLoad, onUnload - to the Station object. Feature: Added triggers - onLoad, onUnload - to the Crane object. Feature: Added trigger - onArrival - to the RailControlPoint object. Feature: Added tank wagon 3D Model option to the Wagon Object. Feature: Added custom dashboards to the module. Feature: Added auto-connect to SourceTrain to connect with the nearest ConnectPoint. Feature: Added the possibility to keep the FlowItems or create new ones when loading and unloading. Feature: Added the possibility to load FlowItems fractionally or discretely. Bug Fix: Fixed bugs on train movement. Bug Fix: Fixed bug on entry of task executer as flow item in Station. Bug Fix: Fixed a bug in the RailControlPoint. Refactor: Changed functionality of Rail's Connect Points. Style: Changed RailSystem model. Style: Added a new model to the Wagon Object: Gas Tank Wagon.

FlexSim 2022 Update 2 is now available for download. For more in-depth discussion of the new features, check out the official software release page: Official Software Release Page - FlexSim 2022 Update 2: AMR Modeling, AI with Bonsai, and more You can view the Release Notes in the online user manual. FlexSim 22.2.0 Release Notes If you have bug reports or other feedback on the software, please email [email protected] or create a new idea in the Development space.

"switch by case" is a stucture in many programming languages. It is a availbale in Flexscript. A case must be a number for a switch by case structure in Flexscript. A decide activity can switch even to string value cases. All you need is to rename the connector from a decision activity to a following activity. process_flow_by_case.fsm