Page 290 - ExtendSim User Guide
P. 290

264
Resources and Shifts
Resource requirements
2) Agroupfilteringconditionfiltersononespecifiedgroup property – either Skill Level or Resource Rank. (See “Group properties” on page 259.) There must be at least one group in the model to enable group filtering condi- tions.
Note that a group filtering condition is not associated with a particular group. Instead, it is a condition on the properties of group members generally. As discussed in “Using group filtering conditions” on page 267, a group filtering condition must have a corresponding resource filtering condition that limits the collection of resources to a specific group.
Creating a filtering condition
On the Requirements tab, check the Create/modify filtering conditions frame to enable it. Then either choose an existing filtering condition from the popup menu and modify it or create and name a new filtering condition.
Each filtering condition is composed of one conditional operator applied to one property. The conditional operators are: =, >, <, >=, <=, and != (not equal). The property can be a resource property or a group property. (See “Properties” on page 258). Note that group properties are only enabled if the model has at least one group of resources.
☞ Each filtering condition filters for one condition of one property.
Testing
Once the property and condition selections have been made, use the Test button to apply the selections to the model’s resources. This opens a table displaying all the resources that match the selected filtering condition. For a group filtering condition, every resource that has the specified group property will be displayed, no matter what group it is in.
For the definition of a filtering condition, select it in the Choose filtering condition popup menu of the Resource Manager’s Requirements tab. The settings will be for the selected filter- ing condition.
Saving
A new or modified filtering condition won’t be available for use until the Save or Save As but- ton has been clicked. Until the filtering condition is saved, its name will be displayed in red.
☞ Saving the filtering condition saves it to a database. To save the database, save the model.
Deleting a filtering condition
If you try to delete a filtering condition, it may give an error message that it is being used by a quantity expression. Before the filtering condition can be deleted, any quantity expressions that use it must also be deleted. And before those quantity expressions can be deleted, any resource requirements that use them must also be deleted.
Default filtering conditions
By default one filtering condition is automatically created for each pool that was created using a Resource Pool block; default filtering conditions are optional if pools or groups are created using the Resource Manager block. Default filtering conditions have “FC_” before the name of the pool or group. See “Default resource requirements” on page 268.
Examples of filtering conditions
Examples of filtering conditions include:
• FC#1–filterusingaresourcepropertyPoolthathasthecondition=Pool2
Discrete Event


































































































   288   289   290   291   292