This chapter describes the creation and structures of project teams within Oracle Project Resource Management.
This chapter covers the following topics:
You can staff project requirements based on competencies, advertisements and advertisement rules, and candidates. A set of competencies is defined for every requirement. The requirements are advertised both inside and outside an organization. Suitable candidates whose competencies match the advertisements are eligible for filling the requirements.
The specified role provides default values for the competencies and associated information. However, you can add, modify, or delete as necessary for the requirement.
If a requirement has assigned competencies, a structure exists in which you can perform competence matching to find potential candidates for requirements.
You define project requirements using the Requirement Detail page. The system copies the competencies of the project role to the requirement to which they can add, modify, or delete as meets their needs. Each competence determined to be mandatory for the requirement must have the required range of proficiency specified in that skill. This range is used for comparison during a resource search.
Note: You can assign global competencies to a requirement, as well as local competencies belonging to the business group of the requirement.
Related Topics
Project Teams and Team Roles, Oracle Projects Fundamentals
Defining Scheduled Team Members, Oracle Projects Fundamentals
Advertisement rules control the visibility of a requirement both inside and outside an organization. An advertisement rule contains actions that direct the channeling and timing of the requirement advertisement. See also: Auditing Advertisement Rules and Replacing an Advertisement Rule on a Requirement.
For more information about the creation and maintenance of project requirements, see Defining Scheduled Team Members, Oracle Projects Fundamentals.
The requirement uses the default advertisement rule of the project. However, you can add, update, or delete the advertisement rule actions, or replace the rule entirely. You also can stop the rule from further processing, and resume the processing when appropriate.
Each action of the advertisement has a qualifying condition. Therefore, in order for the action to occur, the associated condition must be met. The conditions are either the number of days since the advertisement rule was started on the requirement, the number of days remaining until the start date of the requirement, or a combination of the two.
Oracle Project Resource Management evaluates the open requirements that have an advertisement rule with a status of "Started" and performs all of the actions where the conditions are met. This evaluation process called Perform Action Rules is a concurrent program that is scheduled by your system administrator. See, Project Resource Management Processes, Oracle Project Fundamentals.
You can use the advertisement rule to control the escalation of a requirement as the current system date nears the requirement start date. To demonstrate the escalation of a requirement, the following table lists an advertisement rule with various actions:
| Condition | Action |
|---|---|
| Days since started: 0 | Publish to staffing managers on East Coast |
| Days since started: 7 | Publish to all resources on East Coast |
| Days since started: 14 or Days remaining: 14 |
Update staffing priority to Critical |
| Days since started: 21 or Days remaining: 7 |
Send notification to staffing owner of the project |
| Days since started: 30 | Cancel advertisement |
As the requirement ages, it becomes visible to more people and the staffing priority is set to Critical. As more time passes, the staffing owner of the requirement is alerted that the requirement is still open, and then, finally the advertisement for the requirement is canceled. When you fill a requirement, the advertisement rule on the requirement stops and does not perform any outstanding actions.
Each project has a default advertisement rule that is obtained from the project template. You can change this advertisement rule or accept it as is. Subsequently, this advertisement rule becomes the rule for every newly created requirement on the project.
For each requirement, you can either use the predefined actions of the default rule or change the actions to meet your needs. You cannot update performed actions. The actions are as follows:
Publish to All: Make advertisement visible to entire site, across all organizations on the Staffing Home, Requirement List, and Requirement Search Result pages.
Publish to Project Authority: Make requirement visible to people with project authority within a specified organization on the Staffing Home, Requirement List, and Requirement Search Result pages.
Publish to Organizations: Make requirement visible to everyone within a specified organization in a specified organization hierarchy on the Staffing Home, Requirement List, and Requirement Search Result pages.
Escalate to Next Level: Make the requirement visible to everyone in the next level within the organization hierarchy. This action is only valid if the previously defined action is Publish to Organizations.
Send Email: Send an email notice to a specific email address. You can use any external email address. You can also enter multiple email addresses separated by a comma.
Send Notification to Person: Send a notification to a specified person regarding the requirement.
Send Notification to Project Role: Send a notification to a specified role on the requirement-owning project.
Update Staffing Priority: Update the staffing priority of the requirement.
Cancel Advertisement: Remove visibility of the requirement in all pages and searches. This action automatically occurs when a requirement is filled.
You can indicate to either begin the advertisement rule automatically upon the requirement creation, or activate the rule manually for each requirement. You can pause the advertisement rule or resume at any time.
If you change the start date of the requirement or update the advertisement rule, the system re-evaluates and processes all of the advertisement rule actions as follows:
Reverses any actions that have been performed but do not meet the criteria.
Initiates any actions that have not been performed and do meet the criteria.
You can replace an advertisement rule on a requirement at any time. When you replace a started advertisement rule, Project Resource Management reverses any actions on that rule that have been performed. The system also performs any qualified actions of the new advertisement rule.
For example, you advertise a requirement to a particular division within the organization as a result of an advertisement rule action, and then, you replace the rule on the requirement. The system reverses that action and the requirement is no longer visible in requirement searches performed within that division. Then, the system evaluates the actions on the new rule and performs those where the conditions are met.
Every time the system performs an advertisement rule action on a requirement, a recording entry appears in the advertisement audit history of the requirement. The entry provides you with information on the action including the qualifying condition, the date the action was performed, and the result of the action.
Each action can generate multiple transactions, and therefore cause multiple entries in the audit history . For example, when the action Publish to Organizations occurs, then an entry appears for each organization in the hierarchy under the specified organization. If the specified organization has five suborganizations, then five entries appear.
Each audit entry includes an audit reason. The explanations of the reasons you may see are as follows:
Condition Met: The action was performed because the condition was met.
Deleted: The action was reversed because the action was deleted.
Updated: The action was reversed because the requirement start date was updated.
Rule Canceled: The action was reversed because the advertisement rule was canceled.
Rule Cancellation Deleted: The action is re-activated because the Cancel Advertisement action was deleted.
Note: If the system cannot perform an action, then an error explaining why the action failed appears in the audit history.
All active candidates for the requirement appear in the order of ranking value, then score. You can change the weighting values for the score on the Candidate Score and Search Settings page. Any change in these weightings is immediately reflected in the score of the current candidates.