Multi-dimensional array support has been added.
A Discrete State can be specified as an array or a matrix by changing the value of its Dimension property.
- If the Dimension property is set to 'Scalar', the State does not have a dimension and is therefore
a scalar Discrete State.
- If the Dimension property is set to 'Vector', the State is 1 dimensional and the Rows property
will determine the number of rows in the array.
- If the Dimension property is set to 'Matrix', the Rows and Columns properties will determine the
number of rows and columns in the matrix.
- Up to 10 dimensions are supported by setting Dimension to an integer from 0 to 10.
In order to reference a State Array, use the syntax "StateArrayName[Index1, Index2, Index3, ...]".
- For example you could specify StateArray, where StateArray is the name of the State variable
and 2 is the value of the row that is referenced.
- A multi dimensional State Array can be referenced similarly, such as StateArray[2,3] where 2,3 is
the index to the matrix in this 2 dimensional array.
- State Array indexing is 1 based.
- For now initialization may be done by applying the initial value to the entire array or by using
Read or Assigns. Additional initialization options will be made available in the next sprint.
The Workstation object is now out of beta, ready for use, and appears in the Standard
Below is a quick overview of the features in Workstation:
- Workstation may be used to model a constrained resource that has a capacity of one. The
Workstation may always be available (fixed capacity) or follow a schedule.
- Processing through the Workstation object is performed as a sequence of three activities: setup,
processing, and teardown. The sequence of activities is referred to as an operation. The setup
time can be Specific, Change-Dependent, or Sequence-Dependent. A Specific time can be a
constant or be product/order dependent by referencing a table. Change/Sequence dependent
times can be based on any characteristic of the product (e.g. size or color).
- The entity that is processed through the workstation represents a production lot. The data for a
production lot is typically held in data tables, and then referenced by the entity.
- The operation quantity specifies the number of "items" in the production lot that is represented
by each arriving entity. This value can be a constant or be product/order dependent by
referencing a table. The lot can be processed as a single production unit or can be broken into a
sequence of batches that are processed one at a time until the entire lot has been produced.
- Material or a Bill of material may be required to start the processing of each batch. Material or
a bill of material may also be produced at the end of each batch processing. A batch of
produced material may have a transfer time before it becomes available for consumption by
other workstations to easily model situations involving intermediate transfer batching.
- The workstation object is considered to be a primary resource that is required during the entire
operation: i.e. setup, the processing of all batches, and teardown. In addition, any number of
secondary resources may be required and held by each batch across one or more of the three
activities. Secondary resources can be specific resources or selected based on rules from a list
- A workstation has an input and output buffer. Either may be zero and contribute to blocking
between workstations. The next production lot to be processed can be selected based on both
a static ranking and a dynamic selection process.
- A production lot may have a maximum make span that limits when it can be started based on
the availability of the primary resource. The maximum make span may be a constant or
order/product dependent by referencing a table. The make span check verifies that that the
primary resource is available to complete the operation within the maximum make span.
- A workstation has failures based on calendar time, processing count, or event count.
- A workstation has add-on process triggers that allow a user to embed custom logic inside the
workstation (e.g. seize a worker prior to a repair). These add on processes can be used to alter
or extend the standard behavior of the workstation.
We made a series of changes to make the process window easier to use:
- All processes are now sorted alphabetically.
- A process can now be under a category. Categories are sorted alphabetically as well.
- Process categories are collapsible to allow hiding categories not of current interest.
- You can "zoom" an individual process to make it easier to read by clicking on it and using the "+"
and "-" keys on your keyboard.
- The display of Step instance names are now longer to improve process self-documentation
- Several other UI improvements and bug fixes
- SimBits are now documented in a consistent format to improve readability.
- SimBits are now described in the help. They can be found categorized on the main SimBit page
and listed alphabetically within the SimBit area.
- SimBit content is searchable, so now if you search a term (like Vehicle), you will not only find all
the help topics that discuss the term, but also all the SimBits that feature that term.
- We added nine new SimBits including examples of vehicle control, object protection, writing to a
file, and moveable resources.
- The "Composite" tab of the Schedule Data view now shows the composite schedule (repeating
Cycle with Exceptions laid over it) for a schedule.
- The alignment of objects in a queue can now be changed to follow the direction of the queue as
well as just always pointing to the left (as they do now).
- By popular demand, we changed the interface for drawing a line to make it more intuitive.
Right click no longer "commits" the point that you right-clicked for line, polyline, queue,
polygon, and closed curve. Instead, right click ends the line at the last point previously clicked.
- Provided additional model information for user-defined steps and elements.
- Added support for mapping repeating properties to other repeating properties for more flexible
- Added support for editing enumeration captions and list member captions for more flexible
- In property definitions category name fields can now be selected from a list of existing category
Do you want still more information? Examine the release notes for other recent releases.