Desktop Client: What does Time Conversion do in Run Setup, and when should it be used?

This article applies to iGrafx Process and iGrafx Process for Six Sigma Client tools

Time Conversion allows you to affect the behavior of time while running a simulation, but not for reporting. So Time Conversion is essentially only useful in Compressed mode and not Calendar mode. If you change these units, it can affect calculations of durations and interarrival generators, but not report results. In a real-life calendar, there are 24 hours/day and 7 days/week; and in Standard time conversion iGrafx treats a month as 30 days, or about 4.3 weeks. So for real-life models using a calendar, using the Standard time conversion is recommended.

As an example of how using a Custom time conversion can affect a model, consider an expression controlling a decision that is asking if 30 days have elapsed: "If(Days(ElapsedTime())  <= 30 ,Yes,No)". In custom time, if you set a day to 8 hours (e.g. with 5 days/week and 22 days/month), you are asking if 30 days of 8 hours each have passed; i.e. if 30 * 8 = 240 hours have passed. However, the reporting mechanism-- which includes the simulator progress window-- is still using 24 hour days. If you run a model with custom time (8 hours/day), you'll notice that after 10 calendar days (24 hours * 10 days = 240 hours) the expression is true. iGrafx is doing what you asked; it's recognizing that 240 hours, or 30 of the 8 hour days, have elapsed... However, be aware that the reporting mechanism won't use that time conversion. Also be aware that other areas that use time, such as an interarrival generator with an interval in Days, are also affected when using Custom time conversion settings.