Here are quick video summaries of some of the newest features of Simio 14.221. Detailed release notes are below.
There is a third library option below the Library objects. This is the Extras Library. We think you will find that this library establishes an excellent foundation and framework for manufacturing modeling.
Bay – A Bay defines a rectangular region over which Cranes may move.
Crane – A Crane is moved by a Cab and may pickup and drop-off entities at nodes that fall within the specified Bay.
Robot – A composite object that represents a robot. The Robot Hand is a transporter that can pickup and drop-off entities. Select the hand to edit its properties.
Rack – A Rack is used to hold entities for a specified storage time. A Rack can be used with a LiftTruck for placing items on different shelves within the Rack.
LiftTruck – A LiftTruck object may be used to transport entity objects between node locations. When used in conjunction with a Rack, the Lift on the LiftTruck will move vertically to the appropriate shelf height before executing a pickup or drop-off. Additionally, an ‘On Demand’ routing type LiftTruck may be used as a moveable resource that is seized and released for non-transport related tasks by model process logic.
Elevator – An Elevator is used to carry entities in a vertical direction between a collection of ElevatorNodes.
ElevatorNode – An ElevatorNode defines an entry and exit node for the entities that ride on an Elevator. Each ElevatorNode references its associated Elevator and each Elevator references a list of associated ElevatorNodes.
This customer requested feature allows the Units Per Resource property in Seize Step, Release Step, and Resource Availability Constraint Logic to be a resource-dependent value. This allows for easier modelling of secondary resource capacity unit requirements. For example, the requirements might be 4 capacity units if using Resource1, 8 capacity units if using Resource, or 12 capacity units if using Resource3.
Now, if using a data table to define the resource list members, the Units Per Resource property may be specified as another column in the table.
This highly requested feature allows users to place objects, animation graphics, and symbols in different Layers. You can then render certain Layers “Invisible” allowing for objects, animation graphics, and symbols to be hidden. This feature resides on the Visibility Tab. Each object only lives in one Layer and this could be useful for highlighting certain areas of a model or modelling multi-level designs.
This feature allows users to alter a global setting to turn on/off the automatic exporting of all bound tables and logs. This is best used while testing and debugging models where you wish to reduce time by not exporting tables and logs repeatedly.
Note: You can still manually export tables and logs even when this setting is false.
This customer requested feature allows users to copy an Experiment from one model to a different model. This is done by going into the Project Folder and either pressing the Copy and Paste buttons or by using Ctrl + C and Ctrl + V. After pasting, you will be able to select which model to paste the copied Experiment in to. This is useful for when you are often creating new models and want the Experiment to stay consistent through the different models.
This feature allows for a simpler way to copy a model’s definition. This feature can be used by right clicking on the model you wish to duplicate and then selecting “Duplicate Model”.
This user requested feature allows objects to appear where an invisible Queue is located. This per- Queue toggle is accessed by right-clicking on a Queue and clicking “Queue Line Externally Visible”, turning this toggle off will render the Queue invisible but objects will still appear in the Queue’s location in an external space.
This feature simplifies the expression needed when wanting to use a Server reference in a Task Sequence. Prior to Sprint 220, an expression had to reference the ModelEntity, for example, ‘ModelEntity.Location.Parent.Server.StateVariable>1’, and now you can use a simpler expression such as ‘Server.StateVariable>1’.
This feature was designed to improve the speed Simio runs when using a large “from-to-changeover matrix” directly in a data table that is mapped to the Changeover Logic’s Setup Transitions repeat group.
Note: If loading a model saved in Sprint 219 or earlier, the Always Use Property Parent Table References advanced compatibility bit will need to be set to ‘True’ to use the modelling approaches illustrated above.
This feature was implemented to improve the animation in Simio. This feature was intended to give you a more dynamic color selection throughout Simio as well as provide the ability for custom colors in your animation. Note: Custom colors can have transparency, however, proceed with caution as the behavior may not do exactly what you expect.
Constraint Logic – This SimBit contains three models demonstrating the use of Constraint Logic Elements for modelling constraint-driven situations.
Merging Conveyors Controlled By Gate – This SimBit contains three models demonstrating the use of a Resource as a gate for merging conveyors.
Transporting Varying Seized Entities – This SimBit contains two models demonstrating a modelling approach for considering an Entity’s size for loading on a Transporter with limit capacity.
AutoCreate Paths With Vertices – This SimBit contains one model that demonstrates a modelling approach for auto-creating links that have vertices in them.