A common question is whether the version of FlexSim must match the version of AutoCAD, Inventor, Revit, Factory Design Utilities, or Vault.   The answer depends on whether you are importing a file or using a connected Autodesk product workflow.   Importing CAD drawings as model backgrounds   AutoCAD drawings can be imported into FlexSim as model backgrounds—for example, to provide a floor plan that helps you position simulation objects and accurately represent distances within a facility.   There is no requirement to create or resave a drawing in the same version of AutoCAD as FlexSim. In general, DWG imports are not tied to a matching AutoCAD annual release.   However, successful translation can still depend on the contents and version of the individual file. It is not possible to guarantee that every file produced by every historical version or third-party CAD application will translate identically. For the best results before importing a floor plan:   Remove unnecessary text, hatching, layers, and geometry. Check the drawing’s units and scale. Move relevant geometry reasonably close to the drawing origin. See Importing CAD Drawings and Floor Plans for additional guidance on DWG preparation and troubleshooting.   Importing CAD as the visual shape of a FlexSim object   CAD and 3D graphics files can also be used to change the visual appearance of an object in a FlexSim model. This is a file-import workflow rather than a live connection to the application that originally created the file.   In FlexSim versions 2024.2 to 2026, a separate AdskInterop module is required for Autodesk specific workflows. In Autodesk FlexSim 2027 and beyond, that functionality is baked into the software, no longer requiring a separate module.   Autodesk CAD formats that can be imported into FlexSim include:   .dwg .dxf .ipt .iam .rvt .3ds .fbx FlexSim also supports many non-Autodesk formats including:   .ac .dae .igs .jt .obj .skp .stp .usd For the comprehensive list of formats and additional information on working with 3D objects in FlexSim, refer to Creating and Importing Custom 3D Objects.   As with model backgrounds, these imports do not normally require the originating design application to have the same annual version as FlexSim. Compatibility is determined by the file format, the way the file was written, and the translation technology available in the installed FlexSim release.   Factory Design Utilities interoperability   Using Factory Design Utilities in conjunction with FlexSim is considered a connected product workflow, so its version requirements are different from ordinary file import. When using interoperability workflows such as connecting a layout between FlexSim and FDU, the version years need to match for each product involved. For example, when using FlexSim 2027, use:   Factory Design Utilities 2027 Inventor 2027 AutoCAD 2027 The annual versions should remain aligned. Using FlexSim 2027 with an earlier or later FDU installation is not a supported version combination. FlexSim releases will be updated as necessary to support the latest compatible Factory Design Utilities release.   This constraint does not apply to using the Factory Asset Browser within FlexSim. Using this feature does not require FDU to be installed at all, let alone matching versions. For more information about the FDU integration with FlexSim, please visit: FlexSim 2027 Help | Factory Design Utilities (FDU) | Autodesk   Vault interoperability   The FlexSim Vault integration is also considered a connected product workflow, so versions need to match between the products to access Vault features directly within FlexSim. For example, FlexSim 2027 should be used with Vault 2027. However, FlexSim models can be saved directly through the Vault interface, regardless of what version used.    The version requirement of using the built-in integration applies only to FlexSim and Vault Client. Vault Client and Vault Server compatibility vary slightly, where Vault Server may work with up to 2 earlier versions of Vault Client.   For more information about the Vault integration with FlexSim, please visit: FlexSim 2027 Help | Autodesk Vault | Autodesk   Summary   DWG or DXF model background: No matching AutoCAD annual release is required. Translation depends on the individual file. Imported custom 3D shape: No matching authoring-application release is generally required. Use a supported file format. Factory Design Utilities workflow: Match the annual release—FlexSim 2027 with FDU, Inventor, and AutoCAD 2027. Vault integration: Match the annual release—FlexSim 2027 with Vault 2027.

FlexSim 2026 Stable is now available for download.   You can view the Release Notes in the online user manual.   FlexSim 26.0.2 Stable Release Notes   If you have bug reports or other feedback on the software, please create a new post in FlexSim Forums.

Demonstrating Map Array Initialization and Population

FlexSim 2025 LTS is now available for download.   You can view the Release Notes in the online user manual.   FlexSim 25.0.12 Release Notes   If you have bug reports or other feedback on the software, please create a new post in FlexSim Forums.

FlexSim 2026 Stable is now available for download.   You can view the Release Notes in the online user manual.   FlexSim 26.0.1 Stable Release Notes   If you have bug reports or other feedback on the software, please create a new post in FlexSim Forums.

  When modeling arrivals or failures, it is common to reuse the inter-arrival time distribution as the one used to sample the time to first event. Except for memoryless processes (e.g., negative exponential), this is not statistically correct and introduces a left-bias where early events occur sooner than they should. The user command in the attached library generates a statistically valid time-to-first-event distribution from a definition of inter-arrival times.   Problem Being Addressed Inter-arrival distributions describe time between events, not time to the first event Reusing the same distribution biases early arrivals/failures Bias is most visible in: Short simulation runs Models without warm-up periods Models initialized with work-in-progress What the Command Does The command generates a sample set for time to first event using inter-arrival data provided as: A FlexScript distribution expression (string) An array of inter-arrival samples An existing Empirical Distribution object The process: Generates a timeline of events using inter-arrival samples Selects random observation points along the timeline Measures time to the next event Stores these values in a new Empirical Distribution object Runs the Fit function to suggest a best-fit distribution and parameters Output A new Empirical Distribution representing time to first event A fitted distribution expression (name + parameters) suitable for direct use Option to sample empirically or via the fitted distribution Typical Use Cases Time to first failure fields Arrival processes where warm-up is undesirable Short-term forecasting models Models requiring statistically defensible early-run behavior Why Use This Approach Avoids bias introduced by reusing inter-arrival distributions Produces statistically defensible results Reduces reliance on warm-up periods Especially beneficial when early statistics matter   How to Use the Command Loading the attached user library will auto-install the required user commands. The command createTTFeventDist creates an Empirical Distribution that represents the time to first event, derived from an inter-arrival time definition. Parameters P1 (string) Name of the new Empirical Distribution object to create. P2 (overloaded) Definition of the inter-arrival times. One of: A FlexScript distribution expression (string) An array of inter-arrival samples The name of an existing Empirical Distribution object P3 (optional integer) Number of time-to-first-event samples to generate and store in the new Empirical Distribution. (Default is suitable for most use cases.) P4 (optional integer) Number of inter-arrival samples used to construct the event timeline. (Larger values improve stability at the cost of run time.)   Example: Time to First Failure from a Weibull Inter-Arrival Process Assume failures follow a Weibull inter-arrival distribution, but the model starts at an arbitrary point in time and does not use a warm-up period. Instead of reusing the Weibull distribution directly for the first failure, generate a statistically correct time-to-first-failure distribution.  Open a script window and run this command with the example parameters: createTTFeventDist( "FirstFailureDist", "weibull(0,120, 1.8)", 5000, 100000);   This command: Generates a large inter-arrival timeline from 100000 samples of  the Weibull distribution Samples valid times to the next failure Creates an Empirical Distribution named FirstFailureDist Fits a theoretical distribution and reports suggested parameters (eg.  beta(-0.08, 356.54, 1.20, 4.89)) Using the Result in the Model You can now use the generated distribution in either of the following ways: Use the fitted distribution expression Copy the suggested distribution name and parameters into a Time to First Failure or arrival field. Reference the Empirical Distribution directly Sample from the Empirical object where a time-to-first-event value is required, choosing either: Fitted distribution sampling, or Empirical data sampling Both approaches ensure the first event is statistically consistent with the defined inter-arrival process.

FlexSim 2026 Beta is now available.   FlexSim 26.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 create a new post in FlexSim Forums.

En este video aprenderán a utilizar el objetivo visual Text para nombrar partes de un modelo de simulación o visualizar estadísticas de forma dinámica. Para más videos tutoriales pueden suscribirse al canal de YouTube de FlexSim Andina y acceder a nuestra lista de reproducción de FlexTips.

Does your license server randomly stop serving your FlexSim seats? When you check the logs, do you see error messages like the following? 5:34:42 (flexsim) Trusted storage binding change detected! Vendor daemon is being shutdown. 5:34:42 (flexsim) EXITING DUE TO SIGNAL 65 Exit reason 42 5:34:47 (lmgrd) flexsim exited with status 65 (Trusted storage binding change detected.) 5:34:47 (lmgrd) Vendor daemon shutdown - trusted storage binding change detected. Hosting your license server on a VM Many organizations host their license servers on virtual machines and this is a perfectly fine and fully supported way to host your licenses. However, you should be aware that some common virtual machine workflows can disrupt your license server. For instance, you may encounter the errors above if you restored your VM's state to a live snapshot. A live snapshot takes a snapshot of memory as well as disk. Hyper-V is an example of a hypervisor that allows live snapshotting. If a virtual machine does a revert-to-live-snapshot operation, restoring the memory and disk to a previous state, it can interrupt the integrity of your server's trusted storage. To prevent any corruption of your Trusted Storage state, Trusted-Storage-based license servers poll Trusted Storage every 90 seconds to determine if a snapshot restore has occurred. Hence, within at least two minutes of a Trusted-Storage-based license server being reverted, it will shut down, with server log messages similar to the log block above. This shutdown helps preserve the integrity of your license server's local trusted storage. Restoring functionality As you can see at the bottom of the error message, the resultant state of your license server is that your vendor daemon is shut down. This means that your license server is no longer serving FlexSim seats. To restore full functionality, simply start (or restart) the service from Windows services: Or if you're hosting your licenses with lmadmin, start (or restart) the vendor daemon:

Receiving products from the bottled water manufacturing plant using 11 Rial Guide Vehicles (RGVs) for transportation to the Automated Storage and Retrieval System (ASRS), which serves all three production lines. The RGVs' operation works as follows: when products are placed in the receiving buffer with two available positions, the system immediately sends commands to the RGVs to pick up the products from the buffer. The RGVs prioritize picking up the nearest products first. Consequently, the production line located farthest away (Production Line 1) experiences the highest downtime from January to May 2566, with an average downtime of 449.48 minutes. Production Line 2 has an average downtime of 65.12 minutes, while Production Line 3 experiences 76.00 minutes of downtime during the same period. If a production line stops for more than 20 minutes, it requires a complete drainage of the ongoing production process, including scrapping all unfinished goods. This significantly increases the production costs. Consequently, conducting experiments to address this issue becomes complicated, as full-scale production is necessary to identify the causes and implement effective solutions. Thus, stopping production for testing purposes is not a viable approach in this case.

FlexSim 2025 Update 1 Beta is now available. FlexSim 25.1.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 create a new post in the Bug Report space or Development space.

FlexSim 2024 is now available for download. You can view the Release Notes in the online user manual. FlexSim 24.0.0 Release Notes For more in-depth discussion of the new features, check out the official software release page: FlexSim 2024: Workspaces, Person Visuals, USD Support, and more If you have bug reports or other feedback on the software, please email [email protected] or create a new idea in the Bug Report space or Development space.

Node-locked   Node-locked can only be activated once. Be sure that you install the license where you would like it to be installed for the next year. FlexSim can assist with one migration for extenuating circumstances, such as a crashed computer, but there will be fees for any additional migrations. Please contact your distributor to receive assistance with moving your license. The node-locked license feature of terminal server usage (remote desktop) is disabled and cannot be enabled.   Transferable   There is no limit to the number of times a license seat can be activated and returned. If the transferable license is not a network license, then by default the license feature of terminal server usage (remote desktop) is disabled.    Please reference other articles or our documentation for further information about licensing.

En este video aprenderán cómo crear rutas de viaje de Ejecutores de Tareas usando el Navegador de Red. Para más videos tutoriales pueden suscribirse al canal de YouTube de FlexSim Andina y acceder a nuestra lista de reproducción de FlexTips.