EPM Results: HRIS Scenarios
Recommendation, 2007 April 15
Editor:
Chuck Allen, HR-XML Consortium, Inc.
Contributors:
Adam Amato, Data Solutions, Inc.; Kim Bartkus, HR-XML Consortium, Inc.; Dawn MacKay, Halogen Software; Sreenivasa Ampavati, Kenexa; Pramod Mathur, Lawson; Mark Weber, PDI; Paul Storfer, PDI; Peg Jermyn, Microsoft; Romuald Restout, Talent Technology Corp.; David B Turetsky, Workscape
Copyright © 2007 HR-XML Consortium, Inc.
Abstract
This document outlines integration scenarios between employee performance management systems and human resource information systems (HRIS), or in other words, “core” HR systems.
2 Scenario Description: EPM Summary Result to HRIS
2.6 Related XML Example Instances
2.7.1 GetEPMSummaryResult.wsdl
Appendix A - Document Version History
Appendix B – Related Documents
1 EPM Results: HRIS Scenarios
1.1 Overview
An HRIS or “core” HR system typically receives a “summary result” from an employee performance management (EPM) system. The HRIS receives the summary result to record that appraisal process is complete and to store at least a high-level performance rating for the particular employee. As the principal system of record for employee data, an HRIS typically retains at least some of the following data from the EPM process:
- Date of last performance appraisal;
- Beginning/end date of time period being reviewed;
- Type of appraisal;
- Overall appraisal score or rating;
- Position held at time of last appraisal;
- Name of manager who completed appraisal;
- Date of next performance appraisal.
With this data, the HRIS has basic information that may be required by other HR processes and to respond to common queries about performance management.
2 Scenario Description: EPM Summary Result to HRIS
This scenario focuses on the transfer of a high-level record of employee performance from an EPM system to an HRIS.
2.1 Trigger / Preconditions
The trigger for this scenario is the completion of a performance management process within an EPM system. This scenario assumes:
- A performance management process that is self-contained within an EPM system.
- The EPM system produces a result for each employee evaluated as part of an EPM process.
- All necessary steps within the EPM process (reviews, approvals, etc.) have been completed at the time a summary result is transferred to the HRIS.
2.2 Success / Error Cases
On success, the HRIS is provided with data to update the employee record with most recent employee appraisal data.
2.3 Scenario Sequence
1. The EPM process is launched. This could be for one or many employees depending on the type of process.
2. Employee appraisal is completed. This could involve any number of steps, reviews and approvals within the EPM system.
3. An employee appraisal is finalized, with e-signatures, and saved to PDF format.
4. When the finalized, approved result is stored on the EPM system, a summary result is sent to the HRIS system by calling a web service hosted by the HRIS.
2.4 Supporting WSDL Template
2.4.1 EPMSummaryResult.wsdl
This template defines an operation for submitting a summary result from an employee performance management (EPM) system to an HRIS or similar system.
Documentation
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/EPMSummaryResult_wsdl.html
WSDL
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/EPMSummaryResult.wsdl
2.5 Related XML Schema
See Section 3.1, EPMSummaryResult for documentation of the XML Schema related to this scenario.
2.6 Related XML Example Instances
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/EPMSummaryResult_example_1.xml
2.7 Scenario Alternative
The scenario described in Section 2.3, Scenario Sequence, assumes that the HRIS hosts a service that the EPM systems calls to submit the EPM result. A possible alternative is for the EPM system to hosts a service that the HRIS calls to retrieve a competed EPM result. The GetEPMSummaryResult WSDL template described in the section below is intended to support this alternative.
2.7.1 GetEPMSummaryResult.wsdl
This template defines an operation to support the retrieval of a summary result from an employee performance management (EPM) system.
2.7.1.1 Documentation
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/GetEPMSummaryResult_wsdl.html
2.7.1.2 WSDL
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/GetEPMSummaryResult.wsdl
3 Schema Design
3.1 EPMSummaryResult
The EPMSummaryResult schema is intended to communicate a summary result from a performance management system to an HRIS or other target system that does not require a full or detailed result.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel |
Definition |
|
/ |
- EPMSummaryResultType - (1/1) |
A summary result from a performance management process that might be suitable for an HRIS or other target system that requires an overall performance rating, but not a full detailed result. |
|
/ EPMSummaryResult/ |
- EntityIdType - S (0/1) |
An identifier for a performance management process result. |
|
/ EPMSummaryResult/ |
- LocalDateType - S (1/1) |
The date of the EPM result. Usually, the date the result received final approval. |
|
/ EPMSummaryResult/ |
- EPMPeriodType - S (0/1) |
Contains the beginning and end dates of the period for which performance was assessed. |
|
/ EPMSummaryResult/ |
- EntityIdType - S (0/1) |
A unique identifier for the provider. |
|
/ EPMSummaryResult/ |
- EPMPersonType - S (0/1) |
The person who approved or prepared the objective plan. |
|
/ EPMSummaryResult/ |
- EPMPersonType - S (1/1) |
Contains information identifying the person who is the subject of the performance management process. |
|
/ EPMSummaryResult/ |
- EPMReasonCodeType - S (0/1) |
Contains information identifying the person who is the subject of the performance management process. |
|
/ EPMSummaryResult/ |
- EPMScheduleType - S (0/1) |
In the case of a scheduled review, this element is used to identify the type of schedule. Allows for a choice of either standard enumerated values or a non-standard value. Standard values are: annual, mid-year, and probation. |
|
/ EPMSummaryResult/ |
- EPMSectionSummaryResultType - S (1/1) |
Provides an overall performance rating. Often this is a “roll-up” of detailed component scores within a performance management process. |
3.1.1 OverallRating
|
/ OverallRating |
- EPMOverallRatingType - (0/1) |
An overall rating for a performance management process. |
|
/ OverallRating/ |
- EntityIdType - S (0/1) |
A unique identifier of the overall rating score. |
|
/ OverallRating/ |
- xsd:boolean - S (0/1) |
A Boolean to indicate either a satisfactory or unsatisfactory rating. |
|
/ OverallRating/ |
- xsd:string - S (0/1) |
A description of the overall rating. |
|
/ OverallRating/ |
- NumericAndStringScoreType - S (0/1) |
The score of the overall rating. |
|
/ OverallRating/ |
- xsd:string - S (0/1) |
A name assigned to a place on a distribution curve of results. |
|
/ OverallRating/ |
- StackRankType - S (0/*) |
A collection of information about a "stack rank". In the context of a performance management process, a "stack rank" refers to a unique cardinal position for each person within an organization or designated comparison group. "Stack ranking" is also sometimes referred to as "forced ranking". |
|
/ OverallRating/
StackRankInfo/ |
- EntityIdType - S (0/1) |
An identifier for the organizational unit or comparison group within which the ranking is made. |
|
/ OverallRating/
StackRankInfo/ |
- xsd:string - S (0/1) |
The name of the organizational unit or comparision group within which the ranking is made. |
|
/ OverallRating/
StackRankInfo/ |
- xsd:integer - S (1/1) |
A unique cardinal position for each person within the comparison group subject to the ranking process. |
|
/ OverallRating/
StackRankInfo/ |
- xsd:integer - S (0/1) |
The number of people within the comparison group subject to the ranking process. |
|
/ OverallRating/ |
- EPMCommentsType - S (0/*) |
A rater’s comments on the overall rating. |
Appendix A - Document Version History
|
Date |
Description |
|
2007-Jan-22 |
First Draft |
|
2007-Feb-11 |
Revision |
|
2007-Feb-20 |
Updated to put in 2_5 release |
|
2007-Feb-27 |
Put in edits from review. |
|
2007-April-15 |
Approved by Consortium |
Appendix B – Related Documents