question

I don't think there is an easy way to modify the values that are displayed in any of the default state charts in the Dashboard. However, you can manually retrieve the values that those charts are using in their calculations by using the getstat() command. You can also use this command in a Custom Chart from the Dashboard's library. I have included a sample model as an example (dashboard-customhoursutilizedperweek-example.fsm).

To set up a Custom Chart, you first add objects in the Associations tab just like you would add objects in any other State chart. Then, you define the data that will be displayed in the Data tab.

If you'd like to learn more about how Series and Categories are used in a Custom Chard, you can read more about them in the User Manual, under Charting and Reporting > The Dashboard > Concepts > Custom Chart. But since you only want to display one piece of information for each Operator, I have both set to 1 in the example model. The important part is the Data Point Value field, where I use this custom code:

double stat = getstat(current, "State", STAT_TIME_AT_VALUE, 0, STATE_UTILIZE)/3600;
double currentWeek = getmodelunit(CURRENT_DAY)/7;


if (currentWeek == 0)
	return 0;


return stat / currentWeek;

It is possible to condense this into fewer lines and possibly even one line, but I went ahead and separate it out for easier reading.

The gist of how I am using the getstate() command is it will retrieve the amount of time an object has been in a specified state. The current variable is a reference to the object(s) selected in the Associations tab of the chart. The "State" string means we want to look at the object's states when retrieving information (there are other possibilities that are outlined in the User Manual). The STAT_TIME_AT_VALUE means we want to get the current number for the specified state (again, there are other possible values that can be put here defined in the User Manual). The 0 is the state profile we want to look at (0 is the default state profile, but you can create custom profiles and reference them instead). And the STATE_UTILIZE is the state we want to get information from. I also divide by 3600 to give us that number in hours since my model is running in seconds.

If you would like to include more than just the utilize state, you'll need to use the getstate() command multiple times and add all the different states together to get the needed total. And if you are using different time units in your model, you'll want to change the 3600 accordingly to get that total in terms of hours.

The getmodelunit() command in the next line down can return a number of things. In this case, using the CURRENT_DAY macro means it will return the amount of time the model has been running in terms of days. So if you run the model for 43,200 seconds, this code will return 0.5. Running it to 50,000 will return about 13.88, running it to 86,400 will return a 1.0, and so forth. I also divide this number by 7 so we get the amount of time the model has run in terms of weeks.

Finally I make sure the currentWeek variable is not 0, because I am about to divide by that variable and if it is a 0, an error will be thrown. If it is a 0, I simply return a 0. Otherwise, I divide the two numbers and return that value.