Leaderboard

I have attached a simple model using model states to illustrate. I think it should work in a similar fashion using entity states. First, I define the states: Then use those states as Sequence destinations: Until you provide each of those states a value, the Sequence will make no sense and the entity won't know where to go. So on the Source I use an Assign to initialize all the values. This will direct the entity sequentially through Servers 1-4, and then to the Sink: Finally, just to illustrate the technique, on the output node of Server3, I interrupt the normal sequence by Assigning it to instead go to Server5 as its 4th step: If you convert these states to Entity states instead (I was just lazy), I think it should work the same but allow you to selectively override any Sequence Step at any time. UsingStatesInSequences.spfx

This is problematic in Simio because Simio considers only entity length (not width) and only when on a Path or Conveyor. I think the first thing to do is fix the nose to tail problem. If you happen to use Conveyors to model this, there are built-in features to manage spacing while stopped and different spacing while moving. But unfortunately Conveyors are limited to a single direction, so are perhaps not appropriate if this is a bi-directional taxiway. If you are using Paths, you can fix this by making each plane longer when you draw it. For example, if you are drawing a plane that is 50M long and you want it to stay at least 10M behind the plane in front of it, place a nearly invisible dot about 10M in front of the plane's nose, making the total plane length (including safety spacing) be 60M. Although Simio will still put the entities nose to tail, there will be a 10M safety spacing between the physical planes. The problem of conflict at merge points is a bit more tedious to fix. I'd recommend a resource-based approach, like illustrated in the SimBit in Merging Conveyors Controlled by Gate. You can use this approach even when using Paths.

So lets say task B is dependent on Task A, hence Task A has sequence value 10 and Task B has sequence value 20 (Task A preceeds TaskB). Task A branch type should be conditional and for the condition formula should be written in to the "condition or probability" fieldç For Task B enter the processing time and other data as usual. If the auto-cancel trigger is set to "All immediate predecessors cancelled" (as it is by default), Task B will be cancelled if the condition for Task A didnt return true value. Hope this helps

Simio’s neural network implementation allows the import and export of ONNX files, which ensure that Simio is compatible with many machine learning frameworks. This format is well-documented, and there are many third-party packages and applications that can help you convert machine learning models to/from ONNX, or to open and view ONNX files. The attached document provides a basic summary for several of these packages, including tensorflow-onnx, onnx2pytorch, and Netron. Please note that none of these packages are affiliated with Simio, so any issues or limitations of these packages can be discussed on the package’s GitHub page. ONNX Format Utilities.pdf

Here is a simple utility that will export your model to a text file (pipe delimited). Then you can modify the file and import the model back in. NOTE: Currently, this utility does not handle graphics in your model. There is also has capabilities to import and export lists and networks. Here are some quick instructions on how to setup this add-in. 1) Download the "ExportImportModelAddIn_DLL.zip" 2) Extract "ExportImportModelAddIn.dll" from the "ExportImportModelAddIn_DLL.zip" into a temp folder (e.g. c:\temp). 3) Right-click the assembly and select properties. Then choose to "unblock" button and press apply. (only needed for Windows 7 and later). 4) Copy "ExportImportModelAddIn.dll" into "C:\Users\<YourUserName>\Documents\SimioUserExtensions". You might need to add the SimioUserExtensions folder under MyDocuments (C:\Users\<YourUserName>\Documents) if it does not already exist. (e.g. C:\Users\GlenWirth\Documents\SimioUserExtensions). 5) Open Simio and load your model. 6) From the Project Home...Select Add-In button, select "Export Import Model" 7) Choose the function that you want to run (e.g. Export, Delete, Import, etc..). Note...If you export and then import the model without a delete, it will update the object data if the object already exists. Updated 2022-10-05....Updated the exports to sort the data first my name and then export. This ensures that the data exported is in a consistent order. Updated 2021-12-07....Added the ability to select a table and then remove the data from the selected table. If a table name is not selected, all the tables in the model will have their data removed. Updated 2021-09-20....Added Update Model Properties (CSV). With this new method, you can import model properties into your model. If the file contains 3 fields...First is name, then type and last is default value. The only valid types are real, datetime, boolean and everything else is string. If the model property already exists, it will only update the default value on the property. Note: The example assumes the field separator is a caret '^'. To change this , you need to change the delimiter field. Updated 2021-09-08....Updated the sequence of the exports, deletes and imports happen. When OK is pressed, first the exports are run, then deletes and finally the imports. With this change, I am able to Export Table to DB, Delete Table Data and Import Table from DB from in a single run. I typically do this when re-mapping auto create elements. Since the table data need to be removed and recreated before mapping of the elements are correctly mapped. Updated 2021-09-06....Upgraded to .NET 4.7.2. Also, fixed the windows form so it displays correctly. When opened, the form should no longer need to be expanded to see all the options. Updated 2018-11-08....Added Export To CSV, Export To DB and Import From DB. Export To DB will create a table in the SQL Server database with the same table name as the table in Simio. The data columns will be of type nvarchar(max) and the default value will be the same as the default value in the Simio table. It is assumed that Simio desktop will still do the data validation; not the database. This feature is used to save the Simio data into a database so it is backed up and can be shared across users. Each time the Export To DB, if the table already exists, it is dropped and a new table is created. This ensures that the data schemas match between the Simio model and the SQL Server database. Updated 2017-12-05....Fixed index issue with links import. Updated 2017-09-25....Fixed the import of lists. Updated 2017-07-14....Added the ability to auto generate and auto read files. Previously, the files need to be created prior to running the add-in. Now, they will created by the export. Also, the import will retrieve the same file generated by the export. These options are available when the "Auto Generate and Read Files" option is selected. Updated 2017-07-13....Added the ability to multi-select options. Now, more than one option can be initiated when the OK button is selected. This will streamline the process of exporting, deleting and importing. This tool is very helpful for testing out your model with various configurations to ensure that runs properly under various object and/or data configuration. Updated 2017-07-11....Now supports exporting and importing of model properties, exporting and importing of table properties and delete table data. Updated 2017-06-22....Now supports exporting and importing of data tables using using XML. This is simple way to export all the table data from one model and import the same data into a new model (assuming that the same tables schema exist in the new model). Updated 2017-01-27....Now supports exporting of object types using XML. This can be used with the new Configure Scheduling Resources in Simio 9.150 capabilities to define your own object type properties based on an XML document. Updated 2017-01-23....Now supports exporting and importing objects using XML. When using XML, property units are also exported and imported back in. Updated 2016-10-24....Updated files...Added support for repeating properties. ExportImportModel_Code.zip ExportImportModelAddIn_DLL.zip

I believe I got this working using the task sequence mentioned. Using a process with scan step seemed to do the trick so that the patient would block the ER until the OR freed. Thanks, Jim

1) You don't have to consistently move BySequence. You can take detours off the sequence. For example you may normally travel A-B-C-D but if you fail at B you might instead move (off sequence) to E. 2) You can use SetRow to change your sequence or the sequence step the entity is executing. 3) {Advanced concept alert}Unless you are using Enterprise Edition, each cell in a table is a property (e.g. Row 5, Column 3 is a property), but the contents of a cell can be defined as a state. Since its a property you cannot change the definition of a cell during runtime, but if that cell definition is referring to a state, you can change the value of that state. So you can create a model state of type NodeReferenceProperty called MyDest. Then in the destination column of the sequence table manually type in MyDest. Each time you execute that sequence step it will evaluate the current value of the state MyDest and send the entity to that location.

We would like to let everyone join Simio Insiders, but since some of the topics discuss unreleased competitive advantages, you must first agree that you won't "borrow" Simio ideas and share them with our competitors. If you can agree to that then please request membership in Simio Insiders at our signup page. Note that free emails such as hotmail and yahoo may not be accepted. We will contact you when your request to join Simio Insiders is approved. Welcome to the group.