ProModel Versions Historie
ProModel Versions Historie
Versions Historie
Inhaltsverzeichnis
10.12.224 Release | July 2022 3
10.11.197 Release | April 2022 3
10.11.187 Release | April 2022 3
10.10.143 Release | January 2022 3
10.9.124 Release | November 2021 4
10.9.112 Release | October 2021 4
10.8.81 Release | August 2021 4
10.7.53 Release | June 2021 4
10.6.36 Release | May 2021 4
10.5.2.3726 Release | March 2021 5
10.5.0.3688 Release | December 2020 5
10.4.2.3678 Release | October 2020 6
10.4.0.3594 Release | July 2020 6
10.3.1.3536 Release | April 2020 7
10.3.0.3502 Release | February 2020 7
10.2 Release SP3 | ProModel 2018 SP3 | 10.2.0.3428 | October 2019 7
10.1 Release SP2 | ProModel 2018 SP2 | 10.1.2.3366 | August 2019 8
10.0 Release SP1 | ProModel 2018 SP1 | 10.0.1.3260 | May 2019 8
10.0 Release | ProModel 2018 | 10.0.0.3218 | December 2017 9
9.3 Release SP1 | ProModel 2016 SP1 | 9.3.1.2081 | November 2016 10
9.3 Release | ProModel 2016 | 9.3.0.2051 | June 2016 11
9.2 Release SP3 | ProModel 2014 SP3 | 9.2.2.1900 | March 2016 11
9.2 Release SP2 | ProModel 2014 SP2 | 9.2.0.1860 | January 2015 12
9.1 Release SP1 | ProModel 2014 SP1 | 9.1.1.1658 | September 2014 12
9.1 Release | ProModel 2014 | 9.1.0.1639 | June 2014 13
8.6 Release SP4 | ProModel 2011 SP4 | 8.6.2.1036 | November 2012 16
8.6 Release SP3 | ProModel 2011 SP3 | 8.6.1.996 | April 2012 17
8.6 Release SP2 | ProModel 2011 SP2 | 8.6.0.963 | December 2011 18
8.5 Release SP1 | ProModel 2011 SP1 | 8.5.1.858 | June 2011 20
8.5 Release | ProModel 2011 | 8.5.0.847 | May 2011 20
8.1 Release SP2 | ProModel 2010 SP2 | 8.1.0.623 | March 2011 22
8.0 Release SP1 | ProModel 2010 SP1 | 8.0.1.566 | January 2011 23
8.0 Release | ProModel 2010 | 8.0.0.557 | November 2010 25
7.5.5.374 | November 2009 27
7.5.4.373 | August 2009 28
7.5.3.364 | April 2009 28
7.5.2.317 | February 2009 29
7.5.1.308 | November 2008 29
7.5 Release | August 2008 30
7.0.12.243 | September 2007 35
7.0.11.241 | May 2007 35
7.0.10.228 | December 2006 35
7.0.9.227 | September 2006 36
7.0.8.225 | August 2006 36
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 1/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 2/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 3/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 4/45
ProModel® und MedModel®
Versions Historie
NEW: Integration with ProModel AutoCAD® Edition | Requires additional subscription license
ProModel AutoCAD Edition now allows the user to build and simulate directly in AutoCAD 2019, 2020, 2021, and 2022 leveraging
Factory Design Utilities.
ProModel AutoCAD Edition allows the user to build directly within AutoCAD:
Locations
Conveyors
Process Flows
Resource
Path Networks
Build Scenarios
Push the model to ProModel for more advanced modeling capabilities
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 5/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 6/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 7/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 8/45
ProModel® und MedModel®
Versions Historie
Enhancements
New and updated hotkeys for fast access to key modules and application features.
Super Tooltips appear revealing hotkeys and help snippets when hovering over ribbon buttons, and selecting F1 opens online
context help for the given button.
Variable labels can be quickly created using the hotkey Ctrl+T and then clicking on the Layout.
SimRunner Input Factors have been expanded beyond the previous limit of 500.
Simultaneously run an optimization in SimRunner and continue editing your model.
Conveniently cycle through all open windows using Ctrl+Tab.
Name-Index Numbers are displayed in right-click context menus.
Selecting Continuous Trace now opens a window and begins tracing (like Step Trace Events).
When exporting your model to a text file, you are now prompted whether or not to open it right away.
Fixes
In some cases, a location was not able to go down for a Usage downtime if an earlier Usage downtime had preempted one of
the location’s previous Shift downtimes at some point.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 9/45
ProModel® und MedModel®
Versions Historie
Enhancements
When exporting Array data at the end of simulation, the replication number is no longer written out in the Excel Sheet name if
“Export after final replication only” is checked.
Minitab version 17.3 is now supported.
Fixes
After saving and closing a model, upon reopening it the Build menu would sometimes be disabled and prevent access to the
model elements needed to build the model.
Stat::Fit was crashing when attempting to execute an AutoFit for some customers.
In some cases, during installation, the Setup would fail saying that Sentinel drivers could not install.
Intellisense was not coming up when attempting to specify the 2nd dimension of an array being assigned to a local variable.
ProGraphic.xls was not creating a graphics library.
Output Viewer would open at the end of simulation, along with Minitab, even though it was unchecked in Simulation Options.
If Process Simulator 2016 was installed before ProModel 2016, the product licenses would be invalid.
3D Animator would throw an error when attempting to create a package file.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 10/45
ProModel® und MedModel®
Versions Historie
Fixes
Performing a search within a Logic window would sometimes cause the application to crash.
The font and font size for the Trace text were small and difficult to read.
Entering some unique text in the Notes window of the Variables table, would cause the application to crash.
Using the Expression Builder to enter a value in the Variation or Offset field in the First Time dialog of the Arrivals table, would
crash the application after the dialog was closed.
Text in an “Unable to simulate model” error message was being cut off.
Fixes
Various user interface elements should appear better under different Windows DPI settings.
GetResRate function was not being allowed in Subroutine Logic. The function is allowed in Operation and Move logic so it
should only be checked when in context from where the subroutine is called.
A crash would occur in a specific situation with cranes in a model.
The first record listed in the External Files table would be switched to be a Shift type when the model was simulated.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 11/45
ProModel® und MedModel®
Versions Historie
Fixes
Windows system memory was not being freed properly for models that contained EMF image files, which would continue to
increase each time the model was loaded.
A crash would occur after a shift carryover was initiated in a unique case where multiple units of a resource were re-captured
and the entity continued to the next statement in logic when it should have waited for additional resources to be captured prior
to moving on.
Initiating a Save As on models that contained a period “.” in the name and also output results (with a .pmov), would cause
Output Viewer to crash upon attempting to view the results of the new model.
Running an optimization in SimRunner on a model that had Model Instructions defined would cause the Model Instructions
window to open at the start of each new experiment.
Compiling a macro in a specific model caused the compiler to get stuck in an infinite loop.
Upgrading an existing installation of the program to a new version, in some cases, would fail saying that it needed SQL Native
Client x64 prerequisite installed.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 12/45
ProModel® und MedModel®
Versions Historie
Includes Output Viewer 4.5.1.1206 containing the following enhancements and fixes:
On a Turkish Windows OS, statistics for entities and locations were not displaying in Output Viewer.
Entity Cost table was incorrectly labeled Entity States.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 13/45
ProModel® und MedModel®
Versions Historie
Enhancements
All supported graphic formats can now be rotated and flipped.
Organize logic using the new #region and #endregion statements, which allow you to collapse whole sections of logic.
The Views panel can be set to display at the start of simulation by checking the option in the Simulation Options dialog.
Array import using Excel has been optimized to populate data faster when the same file is used to initialize several arrays.
Strings written out to text files using Write and Writeline statements now have the quotes removed.
Fixes
Changing an entity spot to an alignment spot in the Graphic Editor while the layout was zoomed other than 100% would cause
the alignment spot to be drawn in a different spot.
After adding an entity spot to a graphic in the Graphic Editor, you could only move the entity once.
Fixed a couple issues related to shift carryover, one of which prevented a resource from being freed in a Move With Then Free
statement if that resource was preempted to go on a break before arriving to fulfill a move assignment from another resource
that had been preempted for shift carryover.
If an entity was renamed to an entity that had no graphic defined, the application would crash if the renamed entity then at-
tempted to move with a resource.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 14/45
ProModel® und MedModel®
Versions Historie
Error flagging an undefined entity when reading an external arrival file now lists the row number in the file where the invalid
entity is located.
In some cases, the application would crash if the array import details did not specify an end cell.
The move time was being ignored in the statement “Move With <resource> For <time> Then Free” if the resource was already
owned by the entity.
If a file was open in Excel when the model attempted to export data to it at the end of the simulation, no data would be ex-
ported and the user would not be alerted. We now display a message.
A crash would occur if a tank location was created but the submodel was not merged into the model.
The Autosave interval in Tools | Options dialog was not being saved if larger than 60.
Number precision was being lost when assigning values from one expression array to another.
Simulation terminated prematurely after the first entity in an arrival immediately exited the system, even though that arrival
event had additional entities to process.
A conveyor with limited capacity was incorrectly accumulating %Wait statistics when an entity was blocked from moving to the
next conveyor because the load area was not cleared.
A crash was occurring during model translation when attempting to catch an error using an attribute in an activated subroutine.
Fixed a shift carryover issue with dynamic resources originally captured with a Jointly Get statement that was causing a “Usage
Downtime miscarried! Module simdown.cpp line 421” error.
A crash was occurring during simulation at a multi-unit location due to available capacity not being properly kept track of be-
tween entities en route and those actually at the multi-unit location.
Importing data into an array from a SQL 2012 database was not working.
A resource transporting an entity, both without a graphic defined, in some cases was causing the application to crash or display
“CreateCompatibleBitmap” and “SelectObject” errors.
Adding the % character in the Baseline scenario name would cause the application to crash when simulation was initiated.
Warmup length was not changing between scenario runs if a macro was entered and used as a scenario parameter.
“Failed to import data” error occurred when importing data into an array with exactly 700 columns of data.
PMOV and PMCAL files would become corrupted when selecting “No” to overwrite an existing file during Model Package in-
stallation.
“Internal Error: Wait completion event not found” due to an issue with a shift carryover.
A runtime error occurred if the frequency of a downtime was less than or equal to zero.
Some resources that took over work from other resources (due to a shift carryover), in some cases would not return to their
work after being preempted away for a break or other downtime.
A resource was not being properly freed and so the entity would produce a “resource still in use” error upon exiting. This would
occur when completing its work after the resource was preempted away and used in another resource’s downtime logic.
A “resource can’t be freed” error would occur is a specific situation related to shift carryover and other downtimes waiting to
occur.
An “Internal Error: Preempted event type mismatched” error occurred when an entity routed to a location with a preemptive
priority (and preempted the location) while at the same time a shift carryover attempted to interrupt the resource carrying the
entity.
Model crashed while stepping through the Trace window due to an invalid internal unit reference of a resource being used at
another resource’s downtime.
Opening a model with external files in the Silver Runtime edition would sometimes give an error stating that an external file
was changed.
Includes Output Viewer 4.5.0.1203 containing the following enhancements and fixes:
When a Report tab is created by adding a new chart, the name of the Report tab is based on the chart type added.
A Cumulative Line option has been added to Histogram charts.
Units in a Resource Usage chart were not being updated to select additional units introduced in new scenarios. Existing PMOV
files must be resaved for these changes to take effect.
New options for Tables in Output Viewer allow you to change the font and font size, bold the column headers, and center justify
the columns of data.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 15/45
ProModel® und MedModel®
Versions Historie
Log statement labels containing a dash “-“ in the name would truncate the characters to the right of the dash.
The title of a Location State time series chart was displaying the incorrect replication number.
“ChartFX Expired” message was displayed in place of charts.
Fixes
The Find and the Find and Replace dialogs were launching the wrong help topic.
The Help button in the Print Layout dialog would not open the help topic.
Attempting to cancel a change to the font for a variable counter or location label would still apply the changes.
Trying to create a model package with the Protect Model Data option checked would not work if the Windows UAC was turned
on.
“Internal Error: Resource type mismatched in simlogic:::Graphic() module. \simlogic.cpp Line 1914” would occur if a static re-
source (i.e. no path network defined) with three units only had two Layout Positions defined (i.e. Resource Points) and a Graphic
statement was called to change the graphic of the third unit.
A combination of capturing a resource through a GET, capturing two units of another resource in a USE, and then all resources
being preempted for shift carryover could produce a unique situation where a shift carryover would not be fulfilled.
A crash would happen if two resources owned by an entity were initially unavailable to be preempted for shift carryover and
then were later preempted for shift carryover once the entity was in a preemptable state. If only one resource resumed one of
the shift carryover preemptions, the crash would occur.
A crash could potentially happen in a unique situation where multiple resources were captured through first a GET and then a
USE, where some of the resources were preempted away while others were preempted for shift carryover and still other re-
sources were not yet captured.
A Microsoft Operating System update for Daylight Saving Time (see Knowledge Base article KB2633952) prevented some mod-
els from running in the Silver Runtime version. An error would occur stating that an external file was modified and so the model
cannot be simulated.
Simulation results were not being written out to the path specified in the Simulation Options dialog.
If resources were transferred to another entity through an Ungroup or a Create Take statement, a problem could occur later
for those resources when executing a shift carryover.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 16/45
ProModel® und MedModel®
Versions Historie
Scenario manager was not accepting numbers consistently like the rest of the ProModel application. Specifically, periods as
decimals in real numbers.
Tanks were still filling and emptying even though they were on a downtime, if the tanks were designated as the Tank_To tank
in tank transfer functions.
In a certain situation while executing a shift carryover, a “Wait completion event not found” error would occur.
A static resource (one not assigned to a path network) with no graphic selected for it would cause a crash at simulation time if
that resource had a Resource Point defined.
Fixes
In the Brazil time zone, a change from Standard to Daylight Saving Time would cause the CalHour() function to be off by an
hour for a 24 hour period.
Resources scheduled to change shifts during the hour of a Daylight Saving Time change were off by one hour; they either pro-
duced an hour gap or overlapped by an hour.
Resources scheduled to take a break during the hour change from Standard to Daylight Saving Time (DST) were not coming
back online again.
Scheduling a User Pause that crosses a DST change would sometimes cause the pause to occur an hour before or after the
specified time.
Breaks scheduled to occur during the “dead” hour of DST (i.e. when changing from Standard to DST, this is the time from 2 am
to 3 am that is skipped) are now ignored.
Simulation Options dialog was automatically adjusting the Calendar Date start and end times if one or more were set during the
“dead” hour of DST. Now you are prompted to change it.
Simulation Options dialog would not remain open if an error message occurred (due to an invalid entry) after clicking OK or
Run.
A resource was incorrectly being freed after a Move With (and keep) if the original resource was preempted away for a shift
carryover while traveling to fulfill the Move With.
Entities moving on a queue or conveyor with captured resources would cause a crash if the resources were attempted to be
preempted away for shift carryover.
An entity that requested 2 or more units of the same resource and was not able to capture all units, would later cause a crash
when capturing the other units if the originally captured units had been preempted away for shift carryover.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 17/45
ProModel® und MedModel®
Versions Historie
A crash occurred in a unique situation where multiple units of the same resource were preempted away for Shift Carryover at
the same time and other units were not immediately available to fulfill the shift carryover.
The caption in the Logic Builder for an Expression was displaying “??????”.
The caption for the message asking you if you want to copy saved reports and results during a Save As, has been changed from
a warning to more informative text.
If you opened Scenario Manager when no scenarios existed and clicked the Ok button rather than Cancel, you were prompted
that scenario results would be deleted (even though none existed).
A scenario wouldn’t appear to delete if no parameters existed.
Attempting to delete a scenario before a model is saved for the first time could lead to an application failure.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 18/45
ProModel® und MedModel®
Versions Historie
Fixes
Location status lights would show as idle after panning during simulation.
Resources captured with a Get or Jointly Get that already arrived at the location would not initiate a shift carryover if another
one of the resources was still en route and was preempted away to go off shift.
Incorrect reporting of %Waiting statistics for an entity if one of multiple resources captured by an entity with a USE statement
was preempted during the USE.
Output results were not being deleted when a scenario was renamed or deleted unless an Output Viewer reports (.pmov) file
existed for the model.
The Conveyor Only properties of an entity would take on the properties of a previous entity you were editing.
A “No scenarios defined” error was encountered if attempting to simulate scenarios even though the baseline scenario existed.
The error “Unknown class. Missing type qualifier” was encountered when opening 3D Animator if a resource graphic was de-
leted in the model and then synchronized with an existing setup file (.sup).
The Search Next (F3) functionality in the Expression Search would stop working after encountering an instance of the word in
the list of locations or resources in Shift Assignments.
An entity being accumulated at a location was starting a new “accum” group (instead of associating with an existing accum
group) if it was routed to another processing record for the same location.
Context-sensitive F1 help was not invoking the online help for Initialization and Termination logic.
Online help was not coming up for Scenario Manager and Six Sigma window help buttons for MedModel and ServiceModel
products.
The online help error “404 - File or directory not found” was encountered when pressing F1 with the Operation Logic window
active.
A resource preempted away from its own downtime, would cause the application to crash if it attempted to capture another
resource after having resumed its downtime.
In some models where locations had no associated graphics, the application would crash when moving all graphics at once.
In a specific case where a location Entry downtime also captured resources, the application would crash if attempting to take
that same location off shift.
On Windows XP, SimRunner would cause the application to terminate if the experiments or replications produced large
amounts of output data.
A “Wait completion event not found” error was occurring when a resource attempted to execute a downtime. This was the
result of multiple resources being captured by an entity and some of its resources initiating a shift carryover while others were
preempted to go off shift.
A shift carryover resource was not properly being freed if the resource it replaced on the previous shift was preempted to go
off shift as it was traveling to the entity that requested it.
The animation in 3D Animator would incorrectly resume after clicking OK to a Pause event that contained a message.
Other windows applications would move in front of 3D Animator after browsing and selecting an external file (e.g. a movie file).
Attempting to flood fill copy the <default> font for Labels in 3D Animator wasn’t working.
Double-clicking a .sup file was not loading the setup file into 3D Animator if it was already open.
Copying and pasting a row of data for Background Graphics in 3D Animator was not pasting the scale and rotation fields.
Entering a space in some fields of a 3D Animator table would clear out the subsequent values in that row of the table.
Attempting to save a 3D Animator setup file into a non-write accessible directory, caused an unhandled exception.
Changed the 3D Animator Navigation option label from “strafe” to “move”.
Some actions in 3D Animator would require you to select undo twice in order to undo a change.
In 3D Animator, pausing an animation and then attempting to click on the layout would cause the application to freeze.
Flood fill copy was not working for the Graphic filename column for the tables in the Objects section in 3D Animator. It was
attempting to give the files unique names instead of copying.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 19/45
ProModel® und MedModel®
Versions Historie
For Table charts, Time Unit choices in the Options section of the Filter Options panel now only display if they are applicable to
the table.
Double-clicking on an RDB file that is compressed in a ZIP file would produce an error when it attempted to open in Output
Viewer.
When adding a table, if only one scenario is selected in the Filter Options, then the table is displayed with the scenario column
hidden.
Sorting a table by clicking a column header and then changing the time units caused an exception.
Double-clicking the splitter on the Filter Options panel will collapse and expand the panel.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 20/45
ProModel® und MedModel®
Versions Historie
Enhancements
Simulate Scenarios - now you can initiate the running of your scenarios without opening the scenario manager. Quickly simulate
your scenarios by choosing Simulate Scenarios from the Simulation menu or toolbar.
Package installation directory - when a package is installed, the suggested directory to install it into now points to the same
directory where the package file exists.
Standardized hot keys - we now use the standard hot keys Ctrl+O and Ctrl+S for File Open and File Save actions, respectively.
We also now use Ctrl+A for Select All functionality in tables and logic windows. This means that we had to change the hot keys
for accessing the Subroutines (formerly Ctrl+S) and Arrivals (formerly Ctrl+A) modules, to be Ctrl+U and Ctrl+I, respectively.
Double-click to select element name - all element names, locations, entities, variables, subroutines, etc., are selected when
double-clicking on them in their respective edit tables. This enables quick access for copying of the names.
Data Grouping Interval for Statistic series - when viewing the raw data for time series charts, you can now set the grouping
interval if Statistic series are added to the chart.
Pooling time series statistics - Time Plot charts now have a pooling option that allows you to combine the values of the Items
selected and display their joint average in the chart. Series for Statistics are also automatically pooled for all items selected and
show as one joint Statistic, if the chart type has been set to stacked.
Fixes
Installation was not installing the .NET 4.0 framework on Windows XP 64bit.
In an isolated case, attempting to use the Debugger during simulation caused the application to crash.
Merging two resources using Model Collaborator would not properly create a shift assignment for the resulting resource (list
would be blank) and cause the application to crash when simulated.
Both the Query and Stored Procedure options would be selected in the Array Imports dialog when reopening the dialog after
Stored Procedures had been chosen and saved.
The application would crash when attempting to import an external arrival file whose path and filename exceeded 164 charac-
ters.
Normal Run was not being translated to “Execução Normal” for a model built in 7.5 or earlier and run in 8.0. This caused saved
views in 3DR to not display any data for that scenario.
Time-based path networks were not getting their shortest distance mappings properly calculated.
A Crane resource was not immediately being reclaimed if it was temporarily freed by the entity using it (because the entity was
preempted), and had started moving to a downtime node.
A memory leak was occurring when displaying a resource utilization dynamic plot.
Changing the PMCAL file for an existing Shift Assignment would appear to keep the old PMCAL file, but was actually an issue
with the table not properly refreshing to reflect the change.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 21/45
ProModel® und MedModel®
Versions Historie
Changing the Date/Time setting for the simulation clock (to show in hours, for example) would cause the date-based functions
CalHour, CalMin, CalDay, etc. to stop working.
Having “Adjust for Daylight Saving Time” checked in Simulation Options, even though it was disabled, was incorrectly affecting
simulations run in Weekly Time.
The hotkeys for changing views during simulation would not work sometimes.
Resources using an EMF graphic in a model built in 7.5, would disappear during simulation when run in 8.0.
If the simulation ended during a warmup period, the initial value for location contents was not being reported.
An error was thrown “Out of memory. Try reducing memory usage by simplifying your model (i.e. size of Arrays, number of
Entities, etc.) or closing other applications” when a model was loaded that had corrupted background bitmaps.
Variable counters sometimes would not display any values during simulation until the first time the variable changed
Enhancements
The simulation end date has been extended beyond the year 2037 to now be 2100.
The scenarios dialog allows you to select or unselect all checkboxes by pressing Shift + left-click.
Gold Runtime versions can now be updated through the Auto-update wizard.
In Output Viewer, pressing Ctrl + left-mouse click will select or deselect all items within a group of items instead of all items in
all groups, for example, in the Items list for Time Plots.
If an item name in the Filter Options pane in Output Viewer is too long that it can’t be viewed entirely, hovering over the name
displays a tooltip displaying the complete name.
In Output Viewer, a tooltip warning is displayed if entering an invalid value into the Custom Interval Time field for a time series
chart.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 22/45
ProModel® und MedModel®
Versions Historie
Histograms now display x axis labels as single values in between bars in Output Viewer instead of a range of values, which
makes the histogram easier to view and interpret.
Zooming and panning performance during model edit and simulation has been optimized.
Fixes
"Undefined entity in the arrival file" error would occur during simulation initialization if extra spaces were added to the entity
name in the Excel file.
Opening a model and then immediately launching Output Viewer from the menu or toolbar was not auto-loading pre-existing
simulation results into Output Viewer.
Closing the Trace window by using the Trace Off menu item was not keeping the simulation paused.
License Manager was not in the Tools menu if the application was licensed with a hardware key.
Spaces were not being allowed in the Dimensions field in the Arrays table.
If exporting array data to an XLS file, upon opening the file in Excel 2007 or 2010, a warning message would be displayed.
The Cancel button for the Path Color dialog for Path Networks was not actually canceling.
The Graphic Editor would save changes to a graphic library file (GLB) even though the file was marked as read only.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 23/45
ProModel® und MedModel®
Versions Historie
A resource wouldn’t exactly follow its assigned Calendar shift or would go off shift and not come back on shift if a warmup time
was specified for the model.
A change to the Output Path in the Simulation Options dialog was not persisting.
Status Light legend would only open and display in the primary monitor.
The error “Couldn’t save array export file <file path and name>. The file may already be in use or may have read-only attributes”
was thrown if attempting to export array data to Excel 2003.
License Manager may have crashed when accessing it if ProModel 7.5 was installed prior to version 8.0 and was licensed with a
software key.
Deleting a row in the table in the Six Sigma Configuration dialog would delete all the rows after it.
When selecting Database as the array import Source, in the Array Import File dialog, no option was being selected by default
for the “Access Data by:” option.
A scenario name with a % character would crash the application when running scenarios.
An array import error would occur if no End cell was defined in the array Excel Import dialog.
A version 7.5 model would crash upon loading in version 8.0 if a shift assignment record was defined but no shift file was spec-
ified.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 24/45
ProModel® und MedModel®
Versions Historie
Enhancements
Time series statistical data querying has been optimized so that data from larger RDT files can be read and displayed in the new
Output Viewer.
Scenario parameter values are included in the Simulation Info table in the Output Viewer.
Scenarios can now be enabled or disabled through a checkbox user interface element.
Hardware Key Number or Serial Number can be entered during installation and is used during the licensing process and dis-
played in the Help | About dialog for easy access.
Accelerator keys have been added for Background Graphics Behind Grid (Ctrl+G) and Reset Window Positions (Ctrl+W).
The standard “Normal Run” simulation run has been renamed to “Baseline” and can be modified through the Simulation Op-
tions dialog.
Array import database filepath is now automatically updated when a model package is installed.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 25/45
ProModel® und MedModel®
Versions Historie
DTLength - a new system function that returns the length of an off-shift and break downtime. (DTLeft has been changed to
return the remaining length of an off-shift or break downtime.)
Fixes
In certain cases, an entity waiting for resources requested through a JOINTLY GET statement could have captured those re-
sources before another entity that had been waiting longer.
The CalHour and CalMin functions were not returning the proper values for replications two and higher if they were used in the
Initial Value field of variables.
Expression array would not import properly if a start cell was specified but not the end cell.
A “Usage downtime miscarried” error occurred in certain cases involving simultaneous preemptive location downtimes.
A pending preemptive location downtime would not preempt an entity after the entity’s resources returned from performing
other tasks. The resources were performing these tasks because they had been freed due to the entity being preempted by
another event.
Routing to specific units of a multi-unit location, using the Load rule, at some point would stop routing entities to most of the
units.
An off-shift downtime was being skipped if a break downtime ran over into the off-shift period and “Skip Res DTs if off-shift”
was selected in Simulation Options.
Immediately after initiating a simulation run, the application would return back to edit mode. This was caused by an arrival
record that referenced an arrival cycle and also had variation, offset, or daily or weekly repetition defined in the First Time
arrivals dialog. Now an error message appears.
The application would crash in a specific case where a dynamic resource was captured by an entity, the entity then moved to a
location (not using the resource to perform the move) where there was no interface for the resource at that location, and then
the resource was preempted by a downtime.
A pending location Entry downtime would occur prematurely if a preemptive Usage downtime interrupted the currently pro-
cessing entity.
Reporting and Termination events were not occurring in this order: Periodic report, Warmup reset, Termination event. This
caused some inconsistencies in statistical reporting.
The application would lock up if around 64 KB of text was contained in a logic window and it was compiled.
In certain cases with multi-unit locations, the available capacity was not properly decrementing and thus putting a unit of the
location in a state where entities would not arrive or preemption would not occur.
Multiple Load routings to the same destination location in a routing block would cause the Loads not to occur properly.
When running a simulation with Common Random Numbers, seed values were not properly being reset after 200 replications.
The PercentUtil function was only returning a valid result during the warmup period if the model ran with warmup.
In some cases, if a resource returning to an entity it was preempted away from is again preempted before completely returning,
would never return to that entity.
The application would crash if attempting to install a model package in which the fully qualified path exceeded 252 characters.
An “Unable to create file” error now occurs.
In certain cases, a JOINTLY GET statement could preempt a resource while trying to determine if it could capture one of its
requested set of resources and then capture a set of resources that did not include the preempted resource.
The application crashed if a resource owned by a joining entity was preempted after the entity joined the base entity and trans-
ferred the resource.
Implicitly creating an entity (utilizing a Route statement in Operation logic) would put the location in a non-preemptable state.
The Simulation Layout window would not refresh properly if the application window was resized to extend beyond an individual
monitor’s screen resolution (i.e. extending the window across multiple monitors).
Selecting “No” to the “Do you want to see the results?” message at the end of simulation no longer exports array data.
If the Graphic Editor program was moved to a secondary monitor and then closed, upon reopening it the application window
size would very small.
An application crash would occur if an image was added as the second graphic for an entity when no graphic existed for its first
graphic.
Gradient fill was not being properly rendered during simulation.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 26/45
ProModel® und MedModel®
Versions Historie
The order of days listed in Weekly Time dialogs was inconsistent with the order used by the simulation engine. Sunday was
listed first when Monday should have been.
Right-clicking in the Import or Export field for an array would open the Logic Builder.
The View menu would be grayed out if the Layout window was maximized before running a simulation.
Exporting array data to an Excel file that contains VBA code in the Workbook_Open method, for example, would generate a
“file already exists in this location” error.
An “InsertGraphicToList” error would occur if a Continue routing rule was used at a Queue location.
A runtime error was not occurring if an entity was being split into its same entity type. The resulting split entities should be a
different entity type than the entity it is splitting from.
Time-based path networks were not using the time values to determine shortest distance between destinations.
Compiling logic that contained a User Distribution which did not add up to 100% would produce a misleading error message
about an undefined identifier.
Performing a Search or Replace would not search the array database connection strings.
If a week number greater than 52 was entered into the Simulation End week number field, the next time the week number
drop-down list was accessed, it would be blank.
A delayed routing to a specific unit of a multi-unit location by a Send, Join, or Load rule caused the routing entity properly initiate
the route but it would never actually arrive at the specific unit.
The Logic Builder now enforces the SAVE AS statement.
The RESOURCE() system function was incorrectly showing up in the Logic Builder for Node Entry, Node Exit, Operation, Move,
Arrival, and Macro logic.
Number of characters allowed in Warmup Time, Run Time, and Number of Replications fields in Simulation Options dialog has
been increased to allow for longer macro names.
Cost statistics collection is now enabled by default for new models.
Even though Cost statistics were disabled in Simulation Options, if cost statements or functions were used in logic incomplete
cost statistics would still show up in Cost tables.
Axis zoom settings were not being saved with dynamic plot configuration.
Changing the text of a label in a dynamic plot was not being saved.
Resources would remain blocked on a path network behind a node with its capacity set to one.
Specifying a resource unit as part of a dynamic plot was not being saved.
Resource Utilization of a parent resource displayed in a dynamic plot during simulation was not graphing the correct values.
In some cases, multi-capacity locations with preemptive downtimes that got delayed (due to the location being in a non-
preemptive state) were not being preempted when they finally got into a preemptive state.
At a multi-capacity location, if a resource was preempted away from an entity and a location downtime was waiting to occur,
the downtime would incorrectly be allowed to take the location down even though it was in a non-preemptable state, which
resulted in an application error.
During simulation, zooming in beyond a factor of 1000% was causing “CreateCompatibleBitmap” errors.
Priorities for a Crane in a MOVE WITH statement were not being considered if the Crane had been captured previously by the
entity and then used to perform the MOVE WITH.
Merging a model with an External File specified with a relative path would be replaced with an UNKNOWN.xxx in the resulting
merged model and cause an error at runtime.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 27/45
ProModel® und MedModel®
Versions Historie
Data imported from files created in Excel 2007 (using the Excel Import option for Array Import) were limited to the Excel 2003
limit of 256 columns by 65556 rows. Now with Excel 2007 files, you are only limited by the amount of memory that your Windows
Operating System can allocate.
The application crashed when the mouse cursor was moved over the Layout window if the resource Points window was open
for a static resource.
A resource per use cost was incorrectly added to an entity’s overall cost when the resource was preempted away and then
returned to resume processing the entity.
Fixes
If ProModel 7.5.2 was installed after Process Simulator 2009 (version 6.0), the 3DR Output Viewer would not run properly.
In some cases, an application crash would occur if a crane attempted to pick up another entity without moving from the position
it was currently in.
In some cases, a non-preemptive resource off-shift downtime caused the application to crash when the resource executed a
USE statement before going off-shift.
A location or resource would remain on-shift when it was supposed to go off-shift. This occurred when changing from one shift
file to another if the current shift file had work defined at the time the next shift file (in the shift list) was scheduled to start but
had no work defined at that time.
The debugger would stop working for a grouped entity that did not use the AS option in the GROUP statement.
In a specific case, an entity would not move to the end of a conveyor. This would occur if another entity would reach the end
of the conveyor and leave before the entity in question completed its WAIT statement at the beginning of the conveyor.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 28/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 29/45
ProModel® und MedModel®
Versions Historie
Panning
Functionality to click and drag the layout to pan to different areas of your model has been added to Edit mode and improved in
Simulation mode.
Ctrl + Shift + Right drag - pans the layout
Cursors
Dynamic changes to the mouse cursor have been made throughout the application to provide visual feedback when you are in
different modules graphically manipulating objects (such as moving or sizing locations) or defining objects (such as path net-
works and routing).
Fixes
In foreign language versions of the product, buttons in the Logic Builder were missing.
Search and Undo buttons in the Edit Logic window, which can be invoked to fix logic compiler errors during simulation, were
not working.
Buttons and other parts of the interface would turn black and would not reset unless the application was restarted.
Clicking the Compile button in Initialization or Termination Logic would set the cursor to the first line in logic rather than staying
on the line it was on before compiling.
Background graphics would disappear, if Snap to Grid was turned on, when moved to the top left corner of the Layout.
Graphics would disappear in the Graphic Editor if moved to the top left corner of the Layout.
Merging nodes in Path Networks didn’t always work.
Using the mouse scroll wheel or keyboard down arrow, several Attribute, Array, Subroutine, or Macro records could be mistak-
enly created.
You could not delete the last remaining Attribute, Array, Subroutine, or Macro record.
Could not change the color of an EMF graphic after selecting it for an Entity, Resource, or Location.
In some models where an entity activated a subroutine and then executed a WAIT UNTIL statement, the entity could mistakenly
assume the attribute values of a different entity.
If multiple LOAD statements were executed at the same location (in particular, when the location state does not change be-
tween LOAD statement executions), the IN <time> timeout value would only be triggered for the first LOAD statement exe-
cuted.
In some cases where a resource has a downtime and requests the use of another resource during the downtime, if the captured
resource is preempted away, when it returns to resume being used in the downtime the application may have crashed.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 30/45
ProModel® und MedModel®
Versions Historie
Fixes
A created entity (from the CREATE statement) that obtains a resource in Move Logic through a GET statement was incorrectly
setting the state of a single capacity location to Idle if the state of the location was Waiting at the time the created entity exited
the location.
When opening 3DR, a database conversion error was thrown that said, “File Conversion Error in ‘Getting Entity Activity Data’
section of the file: <filename>.rdb. Please contact technical support for assistance.” This only occurred in MedModel and was
due to an error not being caught where an entity, defined to have no stats collected, was renamed as another entity that was
defined to collect stats.
A compiler “Invalid or incomplete expression” error with context of “Resource Quantity: Line 0” was thrown after manually
changing the units of a resource and then clicking the Add resource button to add a resource to the layout.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 31/45
ProModel® und MedModel®
Versions Historie
If a Setup downtime required the use of a resource and that resource was preempted away, the time the location spent waiting
for the resource to return was counted as Operation instead of Waiting.
The time an entity spends waiting for a Setup downtime to complete was not being reported as %Waiting.
Implicitly split entities (using the Quantity field in the Routing dialog) with more than one routing record in the routing block
was causing the location’s blocked time to be reported incorrectly.
At a single capacity location, if multiple entities were unloaded or ungrouped (thus temporarily allowing additional capacity at
a single capacity location), the location’s state statistics were incorrectly collected if the entities could be routed to more than
one destination location.
State Values time series plot was not showing the correct state of a location if a resource was preempted away from the location
in order to be used during another resource’s downtime.
If a dynamic resource was being used by another resource during its downtime, the Trace would incorrectly state that the
resource being used “goes down at the current position” when it should say that it “is already available at this location”.
Entity statistics were not always being collected as %Waiting when an entity was in a preempted state.
The right-click menu would not appear in the Graphic Editor like it does when right-clicking on graphics in the Background
Graphics module.
The Build menu would become disabled after editing a model, saving the model with a different name using Save As, simulating,
and then re-opening the original model.
“Implicit Wait” and “Implicit Move For” warnings would appear and then WAIT and MOVE FOR statements would automatically
be added during compilation to logic that contained errors.
The RAND function was sometimes returning the upper limit value and never a zero which is contrary to the documentation.
For example, if RAND(10) was specified, a 10 would sometime be returned which is not correct.
A resource moving to be used by another resource during its downtime, was having its move time counted towards Travel to
Park statistics rather than Travel to Use.
Imported background graphics disappear if the graphic is moved to the top left corner of the layout.
The simulation would terminate without warning or error if a USE statement was found after a MOVE statement in Move Logic.
An error message explaining that a “USE statement is not allowed after the MOVE statement” now appears.
The Logic Builder was not allowing a paste of a “Move With OwnedResource()” statement without first providing an index
number specifying a resource.
The Arrays table Disable and Persist fields could not be toggled/set by using the space bar.
The conveyor Speed and Length fields were limited in the number of characters that could be entered. They now can handle
up to 512 characters.
When changing Views or zooming while in the Locations module, the locations would scale appropriately in size but the back-
ground would not. Similar behavior occurred in other modules.
When right-clicking in a Logic Window, the Logic Builder would appear rather than a menu with Cut, Copy, Paste, Select All, etc.
choices.
When compiling logic, the Logic Window would scroll to the top line of the logic rather than remain at the line of logic the cursor
was at beforehand.
The Tank_UpdateStats subroutine was in some cases not collecting the state statistics correctly.
The Tank_DoOperation subroutine was ignoring any downtimes defined for the tank location.
The incorrect graphic name would appear in the mouse tooltip when hovering over the buttons of graphic library icons.
A crash would occur when importing GIF files that were created in PowerPoint. Now an error message is displayed explaining
that GIF files with transparency are not currently supported.
Changing the entity graphic in Arrival Logic using the GRAPHIC statement had no effect during simulation until the entity moved
to the next location.
If multiple entities were attempting to preempt other entities (and switch them to their preemption logic) at a multi-capacity
location and the entities were in a non-preemptive state, only the first entity would get switched to its preemption logic (once
it got into a preemptive state). The other entities would ignore their preemptive requests.
Entities were not shown animating on their routing path if a MOVE FOR statement was included in a subroutine and that sub-
routine was called from Move Logic.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 32/45
ProModel® und MedModel®
Versions Historie
A crash would occur for a model with many variable counter graphics when attempting to pan the layout during the model
translation part of simulation.
A location’s state was not properly being counted as Waiting when an entity resumed processing (after having been
preempted) and was waiting to reclaim its resource (that was automatically freed due to the preemption).
The LocState function was returning the location’s state as Empty/Idle when it was really Waiting.
The Quantity field in the Arrival Qty dialog (where Arrival Cycles can be specified) in the Arrivals table, only allowed 17 characters
to be entered.
An error “Internal Error: Cannot find an available location unit” occurred when an entity arrives at a multi-unit location after
having preempted an entity that attempted to resume processing after having been preempted by previous entity.
An entity was incorrectly routing to one of its three possible route destinations when that route became available. The entity
should have remained and taken the route to the destination that it had already preempted after the entity it preempted fin-
ished executing its preemption logic.
Having a GET or USE statement in preemption logic caused a crash.
When an entity in operation at a location was preempted by another entity, the time spent in operation by the preempting
entity was being logged as Empty/Idle instead of in Operation for a Time Plot State Values chart.
A “None of the ROUTE statements were encountered in this execution pass” error occurred when an entity attempted to move
to its destination location after having been preempted and executed its preemption logic.
A Location’s state for the Time Plot State Values chart was not being properly logged as Waiting.
Some entities were executing their post move logic before they had finished moving to the end of an accumulating conveyor.
This was more likely to occur if a previous entity had been blocked for a short period of time at the end of the conveyor but
long enough for the next entity to stop moving and queue up behind it.
Some entities were loading onto the front of an accumulating conveyor before there was actual space to do so. In some situa-
tions, the animation revealed this. There was an error in the internal calculation versus graphical representation of the load
zone space.
An “Animate3.cpp” error occurred after zooming or changing Views during a simulation run where the model had many Variable
counter graphics.
The application might have crashed during a simulation where a Crane was captured by an entity and the Crane was already at
the same location the entity was at.
On Windows Vista, ProModel shortcuts were not being installed correctly into the ProModel Solutions\ProModel directory.
DTDELAY() function used in shift or break logic was incorrectly giving an 'improper usage' error.
Location Information for ALL locations was not showing location states as Down when Called downtimes were initiated by the
DOWN statement.
The application locked up when compiling logic in any Logic window where its text exceeded ~64 KB in size.
The Edit menu was being enabled after simulating a model even though no tables were open. Accessing the menu caused the
application to abruptly close.
The incorrect array record was being updated when selecting the import or export file.
Executing a CREATE TAKE statement in Operation Logic followed by a MOVE WITH statement using OWNEDRESOURCE() in
Move Logic would cause a crash if the resource involved was a crane.
A shift file consisting of seven 24-hr shifts (with no breaks) was causing the application to either crash or a resource assigned
to the shift to take random downtimes.
The RESOURCEUNIT() function was not properly working for the first resource listed in the Resource table.
If a downtime at a multi-capacity location preempted a processing entity, switching it to its preemption logic, once the entity
exited the location the downtime would not occur.
The application crashed in a special circumstance when a location downtime attempted to take a location down. This only
occurred after a first preemptive downtime completed but had been initially delayed due to an entity, which had captured the
location capacity, was traveling to the location. Once the entity arrived, it was properly switched to its preemption logic and
then exited the location allowing the first downtime to occur. Once this downtime completed, the location would appear to
come back online. However, when the second downtime attempted to take the location down, the application would crash.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 33/45
ProModel® und MedModel®
Versions Historie
The application crashed when an entity would exit a location it had incorrectly preempted and routed to. Having two destina-
tions to choose from, the entity should have waited and routed to the first destination it had preempted and had switched the
occupying entity to its preemption logic. However, while it waited for the preempted entity to complete its preemption logic,
the entity incorrectly preempted an entity at the second destination location (no preemption logic) and promptly routed to it.
In a special situation involving multi-unit locations and the LOAD statement, an entity ultimately arrived at the correct location
unit to be loaded but upon leaving the previous location would execute the move logic pertaining to a different location unit.
% Setup statistics were being collected as %Operation statistics if a Setup downtime was preempted by any Scheduled downtime
(clock or shift). The %Setup that occurred before the preemption was being included as %Operation.
When using a Macro to define the Empty or Full speed of a crane resource, the Hoist speed value was ignored and the Bridge
speed was used for the Hoist speed instead.
In a complex use of the USE statement where multiple resources were being requested, the incorrect resources were being
captured.
A translation error occurred when a macro was used in the Full and Empty Speed fields of a crane resource.
In a special case where the same resource was preempted multiple times by different accumulating requests, the resource was
captured by an entity that required an additional resource but the entity would incorrectly proceed to execute its logic without
acquiring the other resource.
If a resource was transporting an entity to a location when a preemptive downtime for the resource occurred, the resource
would not be preempted and go down when it arrived at the destination location but would have to wait until the entity freed
the resource.
A compiler error now occurs if a time value is specified in a MOVE WITH <res> FOR <time> statement and the resource being
used is a dynamic resource. “FOR” only applies to static resources.
External files selected by double-clicking the filename in the Open File dialog, could inadvertently save the file to the wrong
External File record.
In a special situation involving a GET and a USE statement, a “Wait completion event not found” error might have appeared.
The compiler now correctly gives an error if a System function is found on the left side of any Boolean condition in a WAIT UNTIL
statement (e.g. - “<system function> = 10” or “Var1 = 1 OR <system function> = 10”). They are only allowed on the right side of
a Boolean condition in a WAIT UNTIL (e.g. - WAIT UNTIL var1 = <system function>).
Resource State statistics were not adding up to %100 because the time designated as % Blocked in Travel was not properly being
added to either %Travel to Use and/or %Travel to Park statistics.
An “Internal error” would occur when a resource downtime was terminated (preempted) by another resource downtime while
the original downtime was attempting to GET a resource.
A Parameter button was showing up for the MOVE statement when the Logic Builder was opened from within Move Logic.
Waiting statistics in the Entity Activity and State tables contained negative values if entities in the model were grouped (not
renamed with AS option) and then later explicitly RENAMEd while still grouped.
A “Stack overflow pushing integer” error would occur if a MOVE WITH OWNEDRESOURCE() statement was executed without
the entity actually owning any resources.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 34/45
ProModel® und MedModel®
Versions Historie
Saved views were not persisting when first created (i.e. the IVD file was not generated) in the case where 3DR was left open
and a simulation was started (which triggers 3DR to be automatically closed).
The General table in the General Report was coming up blank if a saved view contained a Failed Arrivals table but the simulation
generated no failed arrivals.
Colors were incorrectly displayed in a State Values Time Plot chart containing series from multiple scenarios if the chart was
part of a saved view and the model was re-simulated with one of the scenarios disabled.
Downtime statistics were not being displayed for static resources that were listed before any dynamic resources in the Resource
table in ProModel
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 35/45
ProModel® und MedModel®
Versions Historie
The application was terminating at the start of a simulation run (during translation) when the Text field for a Macro was left
blank.
The events list in the simulation engine was not properly clearing out after each replication which resulted in unnecessary
memory accumulation.
In the Portuguese version of ProModel: o The word “Desabilitar” was misspelled as “Disabilitar”
o The “Custom Trace Options” window (accessed during simulation) did not have check boxes.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 36/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 37/45
ProModel® und MedModel®
Versions Historie
Anyone with “Power User” rights to their computer was not being prompted when an update became available.
The Portuguese version did not have the “Trace at Start” check box in the Simulation Options dialog.
Counters for Tanks were not showing their true fill level.
Table rows would not automatically move from the bottom of the table to the top when using the Enter key to scroll down the
table, which caused the highlighted row to go out of view.
Default animation speed was set to 100 instead of 55 when creating new models
Duplicate resource or location names in the shift assignments table were causing a crash at simulation.
Graphics | Dimension dialog in the Graphic Editor did not work.
The Universal Update was installing a network version file that is not needed.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 38/45
ProModel® und MedModel®
Versions Historie
Relative paths (instead of full paths) can be specified for all external files (graphic library, shifts, array xls import, read, write,
etc.)
Model package creation will retain the relative paths and folders of any external files and will create those relative folders when
the package is installed.
New HTML help system
Option to skip downtimes that occur during an off-shift period for a resource.
New software licensing wizard allowing automatic licensing using a serial number.
Expression and string array types (including import/export to Excel)
Comparison of strings in conditional logic.
Array import from a database using SQL connection string and query.
Arrays are no longer exported if the user chooses not to collect statistics at the end of a simulation.
Individual application settings for multiple user login to the same computer.
“End Simulation” option added to right-click menu during simulation.
XP themes are now supported.
The main application now has toolbars.
Logic windows have been redesigned with new toolbars and a status bar.
Tooltips showing graphic names in the Graphic Library.
PKG files can now be searched for and opened using the Open dialog.
Ctrl+H hotkey invokes the Search and Replace dialog.
ProModel will automatically check for available software updates when the application starts.
Time unit for simulation warm-up is now user-specified.
Fixes
Fixed a View Text issue when the number of lines exceeded 32768.
Fixed a View Text crash when a line of macro logic is greater than 1024 characters.
Fixed some issues with closing 3DR when simulation begins.
Fixed an output problem with time series charts when clock precision is in days.
Fixed some internal memory access issues.
Fixed a GRAPHIC statement issue in move logic after a move to a conveyor.
WAIT and WAIT UNTIL statements were not being properly restricted from use in Initialization and Termination logic.
Fixed problems with transparent counters not displaying correctly at runtime.
Optimization - changed compiler to only allocate memory for arrays during simulation translation, not at edit time.
Fixed a View Text crash in the Processing records section.
Fixed some issues with Portuguese language version.
Fixed an issue where the transparent frame setting on variables was not persisting.
Fixed the duplication of resource records in a 3D Animator script file.
Fixed a problem with the overwrite option for animation file synchronization
Fixed a crash in Logic Builder when viewing external files.
Fixed an issue in the array dimensions field if it contained a space.
Fixed an error message that made reference to ProModel version 3.5
Fixed an issue with resource home, break, and off-shift node selection not persisting if node names are arranged in a certain
way in the path network table.
Fixed an issue with the Edit menu being enabled when you first load a model.
Fixed an issue with double-clicking a .MOD file for automatic launching of ProModel and loading of the model if the model
named contained a “-“ in it.
Fixed a crash when more then 20 dimensions are entered in the array edit table.
Fixed an issue where users with limited write access to their computers could not run ProModel.
Fixed a crash that occurred when clicking Cancel in the Debug window after selecting Global Change and User Condition op-
tions.
Fixed an issue where costing statistics were not reset at the end of a warmup period.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 39/45
ProModel® und MedModel®
Versions Historie
Fixed an issue where extra time series statistics were being written out at the end of the simulation.
Fixed a problem where a text value was saved as a default for the Conveyor speed.
Fixed a crash when adding additional entity graphics out of sequence.
Fixed an issue with the COM interface where the Output Path contained in the Simulation Options dialog was not being properly
returned.
Fixed a problem where two View menus would appear in the application.
Fixed a crash when attempting to import a GIF file that was too large.
Fixed an issue with the Logic Builder where a Quantity button improperly appeared for a Tank subroutine.
Fixed several issues in the Logic Builder where clicking back and forth between statement parameter buttons would not
properly reset the list of options.
Fixed a crash with the variable() function when it receives a value of 0 as a parameter.
Fixed a crash due to multiple resource downtimes with priorities in the 900 level.
Fixed a problem where a resource usage DT would cease to occur if the frequency of the DT ever dropped lower than or equal
to the duration.
Fixed an issue where macro names do not update in the conveyor speed and length fields when their names are changed in
macros table.
Fixed a problem where the TimesUsed() function doesn't compile correctly in DISPLAY statement.
Fixed a crash with a model due to an infeasible mapping constraint.
Fix an issue with daylight savings time adjustment not applying correctly to resources on shifts.
Fixed a problem with the MOVE WITH THEN FREE statement duplicating the cost of a resource.
Fixed a crash when the ENTRIES() function is used for a location whose statistics collection option is set to None.
Fixed an issue where the cost of an entity incorrectly increases if a resource is preempted on its way to that entity.
Fixed a crash when the ENTITY() function is used on a grouped entity that was previously routing using a ROUTE statement.
Fixed a crash due to an arrival with the Occurrences evaluating to zero and the First Time set to Weekly or Calendar date with
either Repeat Weekly or Daily options checked.
Fixed a crash caused from a Preemption Process record not having any routing defined and the application finding a non-
preemption process record with routing.
Fixed an issue where the user-defined font did not apply to the Initialization and Termination logic windows.
Fixed an issue with the margin in logic windows not always being consistent.
Fixed a problem where the tab key did not work in Initialization and Termination logic.
Fixed an issue where a location record would be added to the table when selecting the location table window from the Window
menu.
Fixed a crash due to a resource downtime requesting another resource not assigned to the same path.
Fixed a crash if you try to run a simulation where an entity moves with a resource on a path network that has only nodes and
interfaces defined but path segments.
Fixed the Filtered Trace treeview icons to have a transparent background.
Fixed a statistics problem with a multi-unit location that joins an entity onto another.
Fixed a statistics problem where Average Time Waiting could show negative numbers for a conveyor location that was
preempted.
Fixed a problem where an incorrect compile error would appear if the user incorrectly used the PROMPT statement.
Fixed issues when ProModel is displayed in a secondary monitor and messages from ProModel would appear in the primary
monitor.
Fixed a problem where ProModel uses 100% of the CPU when the simulation was paused.
Fixed a COM issue where a critical error with a model that would normally cause the simulation to end, would be hidden and
allow the simulation to continue.
Fixed a problem with the Graphic Editor where reopening it after it was viewed in a secondary monitor would cause the appli-
cation window to be really wide.
Fixed an issue where the application window would begin to flash if two blank routing records were created.
Fixed the Output Path in Simulation Options to be automatically set to a valid path if the original path it contained was not valid.
Fixed a memory overwrite that happens when running scenarios with macro names longer than 49 characters.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 40/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 41/45
ProModel® und MedModel®
Versions Historie
This update also includes Hotfix 6.0.30 updates, which included the following changes and fixes:
Added Menu options to launch the License Manager and Check for Updates.
Updated ActiveX documentation, available in ActiveX.pdf file.
Fixed bug in model packages, where model packages that were created in 6.0.20 Professional versions, which contained exter-
nal files, were unable to run a simulation in Run-Time Silver versions of the software.
Fixed bug in Model Package Association, where the default path for installing the model package was shown as an incomplete
path.
Fixed bug in Output Viewer 3DR, where Scenario Labels displayed incorrectly.
Fixed bug, where ProModel PI could not detect a stand-alone hardware key after installing ProModel 6.0.20.
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 42/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 43/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 44/45
ProModel® und MedModel®
Versions Historie
GBU mbH
Rotenbergstraße 8 Telefon +49 (0)711.1662 450 www.gbumbh.de
D-70190 Stuttgart Telefax +49 (0)711.1662 451 [email protected]
© GBU mbH 2022, Stuttgart. Veröffentlichung, Kopie oder Nachdruck nur mit schriftlicher Genehmigung der GBU mbH. Stand: 12.07.2022 Seite 45/45