Product Updates
Process Simulator Update ProModel/MedModel/ServiceModel Update
Process Simulator 2007 version 5.3.1.336 Update available!
This update is available from the Automatic Update utility or can be downloaded from the Solutions Café. It contains the following enhancements and fixes:
Enhancements
- Drawing scales in Visio other than just 1:1 are now supported in Process Simulator.
- The Process Simulator stencil now contains a Multi-Cap shape which looks like the General Activity shape but has the simulation properties of “infinite” capacity for the activity with no buffer capacities defined.
- The default properties of the decision shape in the Process Simulator stencil have been modified so that the capacity is “infinite”, the buffers have no capacity, and there is no activity time.
- Clicking on “Convert to Simulation Model” will now search the active simulation document for any shapes that do not have simulation properties and then add them.
Fixes
- Clicking on the “Attach to” list box for an Attach routing would revert to selecting “Selected Entities Only” even though the original choice was “Any Entity” or “Creator”.
- A simulation translation error would occur if a blank line in any Logic window was commented out. The error message was similar to: “Error ‘Compiler Error’ Context: Process: For All Entities at Activity_:Operation line 1 Source /”
- The Keep checkbox was not remaining checked if immediately after checking it, another tab in the Activity properties window was clicked on.
- References to variables were not being properly tracked if the variable name did not have the exact case for each character in the name (e.g. ThisVar1 vs. thisvar1).
- References to variables were not being tracked in some places where the variable could be used (e.g. Activity Multi-Entity time, Activity Setup time, Storage Trigger Level, etc.). This could result in the variable being deleted without a prompt to remove or replace the instances in the model where the variable is used.
- Adding a second percentage routing to an activity was not properly changing the first routing percentage to 50%, which caused an error on both routing connections.
- Simulation properties would stop being added to shapes after a routing connection was added and then removed by using the Undo while the simulation properties window was open.
- If a shape is encountered that does not have simulation properties, properties will now be automatically added.
- Simulation properties would stop being added to shapes after changing Resource Units, closing the properties window, and then undoing the action.
- In some cases on computers with non-US regional settings, the Permanent Attach option was not saving when checked.
- A downtime was inadvertently being added to an activity if that activity was double-clicked on in the Simulation Object Explorer, which opens the activities properties.
- Undo would stop working in Visio when a shape was copied and pasted.
- In some cases Redo in Visio would stop working.
- When the same shape is added to the layout two or more times the default naming convention was “Shape”, “Shape 1”, “Shape 2”, etc. Now the naming convention follows “Shape”, “Shape 2”, “Shape 3”, etc.
- Simulation properties were not being added to a shape when placed on the layout if that shape had been previously saved to a stencil from the layout with simulation properties. Note: simulation properties are deleted when a shape is added to a stencil. Process Simulator does not currently support the saving of simulation properties with a shape added to a stencil.
- "Must have at least 1 entry for scheduled arrivals” error would appear 33 times if all scheduled arrival details were deleted and then another action was attempted like selecting another shape.
- The purchase button on the licensing and registration window was pointing to a non-existent web page.
- "The capacity must be larger than the initial level" message would appear 37 times after entering an initial level for a Buffer activity that is greater than the capacity. It now only appears once.
- “Value must be a number greater than or equal to zero..." message appeared 37 times after entering text, for example, in a numeric-only field of the Multi-Entity, Setup, or Downtimes tab for an Activity or Resource.
- "Unable to extract simulation data. Error: 5, Invalid procedure call or argument" error occurred when a resource group was defined in a submodel but not in the main model.
- The User Guide had references to other ProModel products names instead of Process Simulator.
Includes 3DR version 2.0.12.103 containing the following fixes:
- Total time in use is now collected for Resources and is reported as Work Time.
- Chart properties like the zoom or x axis time unit were being automatically reset when modifying the chart items. Now you are prompted whether or not to reset the chart properties.
- When running multiple replications, an informational or warning message will appear if data in a Time Series chart (Time-weighted, Simple, or Counts) is truncated to match the replication with the shortest run length. If all replications have the same run length, no data is truncated.
ProModel/MedModel/ServiceModel 7.5.2.317 Update available!
 This update is available using the Check for Updates feature or can be downloaded from the Solutions Café. It contains the following fixes:
- Setup statistics (found on the Setup tab of the General report in 3DR) were not being cleared at the end of a warmup period.
- Importing a background graphic with a path and filename greater than 126 characters was causing the application to crash.
- In certain cases, the Wait Until statement was not processing the entities in the same order as previous versions.
- When a Wait Until statement was used after a MOVE statement in Move Logic, the simulation would crash.
- Background text objects were disappearing when attempting to move them along with other object types (e.g. variable counters).
- In background graphics when panning using the hot keys (Ctrl + Shift + Right-click) the right-click menu would appear upon ending the panning.
- Defining arrays with more than 200 million cells was causing the application to crash when the simulation was started.
- When creating, splitting, unloading or ungrouping entities at a single capacity location (i.e. allowing temporary multi-capacity) the status light was not in sync with what the location state over time chart was showing in 3DR.
- When creating, splitting, unloading or ungrouping entities at a single capacity location (i.e. allowing temporary multi-capacity) the state of the location was not being consistently set. The priority for setting the state is given to entities processing Operation logic, then to entities Blocked in routing, and lastly to entities executing Move logic.
- Batches and Periods were numbered differently if a simulation run had a warmup that was defined in Simulation Properties versus using the Warmup statement in logic.
Includes 3DR version 2.0.12.103 containing the following fixes:
- Total time in use is now collected for Resources and is reported as Work Time.
- A database conversion error “File conversion error in ‘Getting Period Data’ section of the file” would occur if a space was included at the end of the report name parameter in the REPORT AS statement.
- Chart properties like the zoom or x axis time unit were being automatically reset when modifying the chart items. Now you are prompted whether or not to reset the chart properties.
- Batch Mean or Period names in charts (e.g. Location State) were not sorting correctly.
- A “No data available” message would appear in a category chart when attempting to graph series for <All> Periods.
- For Batch Mean or Period statistical reporting, the State and Utilization reports were incorrectly including periods in calculating the average where there was no Scheduled Time reported. This resulted in a State chart, for example, adding up to less than 100%.
- When running multiple replications, an informational/warning message will appear if data in a Time Series chart (Time-weighted, Simple, or Counts) is truncated to match the replication with the shortest run length. If all replications have the same run length, no data is truncated.
|
YouTube
Twitter
