Performance Target Entity

A performance target entity is a named population: the group of people one appraisal round covers. Factory Workers, Sales, Head Office. You name the group here, and the Evaluation Cycle then runs a round over it.

Where

Performance Management › Setup › Performance Target Entity

Who uses it

The implementation consultant, once per appraisal population. HR opens it again each round to read the coverage

When

Before the first Evaluation Cycle

Needs first

Employee Organization Assignment, Evaluation Template

What it is for

Every appraisal round has to answer one question before anything else: who is in it. This screen is that answer, and it is the only place the answer lives.

A man belongs to a population because his Organization Assignment names this target entity. That is the whole rule. HR sets the target entity on the person's assignment, the same place his department, position and reporting line are set, and he is then part of this group. He is not in the group because of anything typed on this screen.

The form he fills comes from his position. The Evaluation Template named on his position is the form he gets. If his position names no template, the cycle's own template is used. If neither resolves, he has no form, and the round will say so by name rather than quietly skip him.

The Population tab does carry an include and exclude column, and it is worth being clear about it: that column is not what decides the population. The tab is a written-down list of the people the system worked out from the assignments, refreshed each time a round is activated. You can add a line by hand to pull one extra person in, or to push one person out, and those hand lines are kept. Everything else on the tab is the result of the assignments, not a rule that produces them.

Nothing on this screen runs on a clock. A round starts when somebody presses Activate on the Evaluation Cycle.

Every field, in plain words

Basic Information

Field	What it means	What to put in it	Notes
Performance Target Entity	The short code for this population. It is what you pick on an employee's Organization Assignment and on a cycle	FACTORY	Keep it short and obvious. The people doing data entry read it
Name	The population in words	Factory Workers, Karachi Plant	Required

Population

One line per person the round covers. Resolved lines are rebuilt every time a cycle over this entity is activated. Hand lines are never rebuilt and never removed.

Field	What it means	What to put in it	Notes
Line #	Line number	Fills itself
Include or Exclude	On a hand line, whether this person is being pulled in or pushed out	Include	Required on a hand line. INC Include, pull this person in even though his assignment does not name this entity. EXC Exclude, keep this person out even though it does. A line the system resolved is always an include
Employee	The person	10427	Required. Pick it from the list
Name	His name	Fills itself. Ahsan Raza
Department, Department Name	The department he was in when the population was last worked out	Fills itself. Production	Read from his assignment at that moment, not typed
Position, Position Name	His position at that moment	Fills itself. Shift Supervisor
Evaluation Template, Template Name	The appraisal form he will get	Fills itself. Shop Floor Appraisal	Taken from his position, falling back to the template on the cycle. Blank here means he has no form and cannot be given a sheet
Criteria Status	Whether this person is clear to be appraised	Fills itself	OK Meets criteria, he will be activated. HLD Held back, something on the Criteria tab is not satisfied, and he is not activated until it is. EXC Excluded by hand, somebody put an exclude line against him
Hold Reason	Why he was held back	Fills itself, in words	Read this before arguing with the verdict
Line Source	Where the line came from	Fills itself	RUN Resolved from the assignments. MAN Added by hand on this screen. A resolved line is rebuilt next time, a hand line is not
Last Resolved	When the line was last worked out	Fills itself	If this is older than your last assignment change, activate the cycle again

People who have resigned or are no longer active are never population, whatever their assignment says.

Criteria

Optional. Extra conditions a person must satisfy before he is appraised. Somebody who fails one is marked Held back on the Population tab, with the reason, and is not activated.

Field	What it means	What to put in it	Notes
Line #	Line number	Fills itself
Screen, Grid	Where the value being tested is recorded	The screen holding the field
Field	The field being tested	Pick it from the list	Required
Condition	How it is tested	Is at least	Required. See the list below
Value	What it is tested against	6	Leave blank for Is filled in and Is blank

• GE Is at least, and LE Is at most, for a number or a date.
• GT Is more than, and LT Is less than, when the boundary itself should fail.
• EQ Is exactly, and NE Is anything but, for a code or a name.
• NEB Is filled in, and EMP Is blank, when you only care that something was recorded.

Leave this tab empty if everyone named on an assignment should be appraised. Most clients do.

Business Multiplier

Optional. A factor applied to what this population is paid, by department, business area or functional area. It never changes a score and never changes a review.

Field	What it means	What to put in it	Notes
Line #	Line number	Fills itself
Multiplier Basis	What the line is keyed on	Department	Required. DEPARTMENT match the employee's department. BUSINESSAREA match his business area. FUNCTIONALAREA match his functional area
Reference	The department, business area or functional area this line is for	Production	Required. Pick it from the list
Multiplier	The factor	1.10	Required. 1.00 changes nothing. 1.10 pays that group a tenth more

The first line that matches the employee's own assignment, in line order, is the one that pays. Somebody matching no line is paid at 1.

Run Coverage

Read only, and worth knowing about. Once a round has been activated this tab shows, half by half, who holds a goal sheet and who does not, and for everyone without one it names the first thing to fix. It is the page to open when a client says somebody was missed.

The screen also carries a Refresh Achievements action. It recomputes every computed measure on this entity's goal sheets. Lines whose period has already ended are frozen and are not recomputed, because a frozen figure is what the reviewers scored. Lines still inside their period are refreshed.

How to configure it

1. Make sure the Evaluation Template each group will use already exists, and that it is named on the Position records. The form follows the position.
2. Open the screen and give the entity a code and a name. FACTORY, Factory Workers, Karachi Plant.
3. Save. For a straightforward population there is nothing else to type.
4. Go to Employee Organization Assignment and set this target entity on every person the round should cover. This is the step that actually builds the population, and it is the step clients forget.
5. Only if the client has a genuine extra condition, add it on the Criteria tab. Otherwise leave that tab empty.
6. Only if the client pays one department more than another for the same score, add a Business Multiplier line. Otherwise leave it empty.
7. Create the Evaluation Cycle, name this entity on it, and press Activate there. Come back to the Population tab and read what resolved.
8. Check every line shows Meets criteria and carries a template name. Fix anything held back or without a form, then activate again.

Scenarios

"Managers and the shop floor are judged on different things"

That is two templates, not two target entities. Keep one population if one round covers them all, put the management template on the management positions and the shop floor template on the shop floor positions, and each man gets the right form from his own position. Use two target entities when the two groups are appraised on different dates, or by separate rounds.

"A man moved from the factory to the office in March"

Change his Organization Assignment, which is where the move is recorded anyway, and set the office target entity on it. The next activation drops him out of the factory population and picks him up in the office one. A sheet he already holds is not taken away from him.

"One person should not be appraised this year"

Add a line on the Population tab, set it to Exclude and name him. The line survives every later activation, so he stays out until somebody removes it. A resolved line is never written as an exclude, so if you see one, a person put it there.

"He joined in September and we appraise January to June"

Nothing to do. Run Coverage reports him as having joined after that half ended, so no sheet is due for it, and the Dashboard does not count him as overdue. He picks up the next half normally.

"He is in two populations"

Harmless in itself. What is not harmless is two live rounds covering the same period catching the same person, and the check before activation reports exactly that, per person, naming the other round's half. Fix it by excluding him from one of the two.

What it is connected to

• Employee Organization Assignment decides membership. Nothing on this screen does.
• Position decides which Evaluation Template a member fills.
• Evaluation Cycle names one target entity, and activating it freezes the member list onto the cycle.
• Employee Goal sheets are generated for the frozen members, half by half.
• Performance Payout reads the business multiplier from here, along with the Evaluation Increment Matrix bound to this population.
• Dashboard counts coverage, measurement and overdue cases against this population.

If something looks wrong

• "The tab says it resolves to zero employees" - no Organization Assignment names this target entity yet. The population is built there, not here.
• "Activate refuses and says to set a target entity on the cycle" - the cycle has no target entity on it. A cycle with no population has nobody to cover.
• "Somebody is on the list but shows no template name" - his position names no Evaluation Template and the cycle has none either. Set one, then activate again.
• "Somebody is held back" - the Hold Reason on his line says which criteria line he fails. If the criteria line itself is wrong, fix it there rather than excluding him.
• "A man we transferred still shows his old department" - the line is a snapshot from the last activation. Look at Last Resolved, then activate the cycle again.
• "One person has no sheet and no obvious reason" - open Run Coverage. For everyone without a sheet it names the first thing to fix, including people who joined after the half ended, for whom no sheet is due.