Product Updates

Process Simulator is Officially Windows 7 Certified

ProModel's Process Simulator has passed Microsoft's stringent requirements to become officially Windows 7 Certified.  This certification reflects ProModel's dedication to remaining continually compatible and up-to-date on the changing landscape our users experience when performing business process, Lean and Six Sigma initiatives.

Even if your organization is not migrating to Windows 7, this accomplishment means easier deployment of Process Simulator and greater compatibility with any Microsoft Windows environment.

Process Simulator Becomes Another Windows 7 Front Runner for ProModel

By earning Windows 7 certification for Process Simulator, ProModel now has another product, along with Portfolio Simulator, recognized by Microsoft as an official Front Runner for Windows 7.  This designation means that Process Simulator is compatible with the latest Microsoft technology—and is among the first to market!

Process Simulator 2009 SP2 Available

This version is available using the Check for Updates feature or can be downloaded from the Solutions Café.  It contains the following changes:

Enhancements

• Process Simulator 2009 SP2 is Windows 7 Certified on both 32- and 64-bit versions.

Fixes

• Calendar files only specified in Arrivals would not be included when creating a package.
• Upon simulating, a compiler error stating “Two consecutive math operators encountered” would occur if a Conditional route had been imported from Excel.
• A variable could be deleted even though it was being used in the Units field for a resource.
• A Failed to Export error stating a “String cannot be of zero length” would occur when exporting a model to Excel with a “GroupQty()” (no name within the parentheses) function in Activity logic.
• Numeric values using commas as a decimal separator (non-US regional settings) were not being correctly exported to Excel for several simulation properties.
• If any invalid data was entered in Simulation Properties fields in Excel and then imported, the Import Errors window displays the incorrect row number.
• If invalid data was entered in the Simulation Properties – End Date field in Excel and then imported, the Import Errors window would specify that the data should be a “Time of Day” instead of a “Date.”
• In some cases, models built in version 5.3 were not able to have their variables or attributes deleted if they were referenced in Activity logic.
• Variable graphics would increase in size following a simulation run if a model referenced submodels in a separate VSD file. This did not occur for submodels within the same VSD file as the parent.
• When right-clicking on a column header in the Six Sigma Configuration dialog, an unhandled exception would occur and close the dialog.
• If themes were applied to the document, a background encompassing the entire diagram would appear during simulation that was the color of the theme.

ProModel/MedModel/ServiceModel 7.5 MR5 available

This version 7.5.5.374 update is available using the Check for Updates feature or can be downloaded from the Solutions Café.  It contains the following fixes:

Fixes

• In rare cases, during simulation the application would fail to find the USB key and force the application to be closed.
• Resource State statistics were incorrect if the simulation was ended while any Resources were blocked during travel due to the capacity of the next node in its path being full.
• 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.