EPM Results: LMS 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 describes scenarios involving the integration of training and development plans between employee performance management systems and learning management systems (LMS).
1 EPM Results: Learning Management System Scenarios
2 Scenario Description: Employee Development Plans
2.3.1 WSDL Template: EPMDevelopmentPlan.wsdl
2.4.1 WSDL Templates: GetEPMDevelopmentPlan.wsdl
2.6 Related XML Example Instance
3.1.1 EPMDevelopmentPlan / DevelopmentItem
Appendix A - Document Version History
Appendix B – Related Documents
1 EPM Results: Learning Management System Scenarios
1.1 Overview
This document describes the use of HR-XML's Employee Performance Management (EPM) Results Specification in supporting common integration scenarios between employee performance management (EPM) systems and learning management systems. See the separate document, EPM Results: Overview for information on the entire scope of the HR-XML EPM results specification.
Learning management systems (LMS) encompass a wide-range of functionality, ranging from administrative tasks (student registration, content management, etc.) to strategic ones (competency management, skills-gap analysis, etc.).
1.2 Scope
The current scope of this document focuses on integration scenarios involving the provision of employee development plans. Other EPM and LMS integration scenarios may be added to this document as they are identified.
In addition to, or instead of, receiving a development plan from an EPM system, an LMS also might receive from an EPM system a full result that includes developmental items associated with competency ratings. See the separate document EPM Results: Full Result Scenarios.
2 Scenario Description: Employee Development Plans
This scenario describes the communication of employee “development plans” from an employee performance management system (EPM) to a learning management system (LMS). Also, see Section 2.7, Alternatives.
The operations to support the integration of development plans have the potential to be “symmetrical” in the sense that there may be scenarios variations where either party – EPM or LMS – might assume the role of development plan supplier or consumer.
2.1 Trigger / Preconditions
This scenario assumes that:
- The performance management process is self-contained within an EPM system.
- A result for each employee is evaluated as part of an EPM process.
For purposes of this scenario, the trigger for the communication of a development plan is assumed to be the completion of a performance management process. Other triggers and patterns of communication also may be relevant. For example, in some cases, a draft or proposed development plan might be an input into to performance management or related process (for example, succession planning).
2.2 Success / Error Cases
On success, the LMS is provided with development goals and requirements that were set as part of an employee performance appraisal process.
2.3 Scenario Sequence
1. The EPM process is launched.
2. Employee appraisal is completed. This could involve any number of steps, reviews and approvals within the EPM system.
3. When finalized, an approved result is stored on the EPM system, results are sent to other relevant systems (for example, compensation systems), and a development plan is sent to the LMS by calling a web service hosted on that system. Should there be a need to manage the lifecycle of a development plan once transferred to the LMS, optional “update” or “cancel” operations might be used. See Figure 1, Development Plan Integration.
Figure 1, Development Plan Integration
2.3.1 WSDL Template: EPMDevelopmentPlan.wsdl
This template defines operations to create, update, and cancel employee development plans.operations.
Documentation
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/EPMDevelopmentPlan_wsdl.html
WSDL
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/EPMDevelopmentPlan.wsdl
2.4 Alternatives
An alternative is depicted in Figure 2: Alternative – Development Plan Retrieval, under which the development plan might be retrieved by the LMS by calling a web service hosted by the EPM system. See Section 2.4.1, WSDL Templates: GetEPMDevelopmentPlan.wsdl.
Figure 2: Alternative – Development Plan Retrieval
2.4.1 WSDL Templates: GetEPMDevelopmentPlan.wsdl
This template defines an operation for the retrieval of an employee development plan.
Documentation
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/GetEPMDevelopmentPlan_wsdl.html
WSDL
http://ns.hr-xml.org/2_5/HR-XML-2_5/ws/PerformanceManagement/GetEPMDevelopmentPlan.wsdl
2.5 Related XML Schema
See Section 6, Schema Design for documentation of the XML Schema related to this scenario:
http://ns.hr-xml.org/2_5/HR-XML-2_5/PerformanceManagement/EPMDevelopmentPlan.xsd
2.6 Related XML Example Instance
http://ns.hr-xml.org/2_5/HR-XML-2_5/PerformanceManagement/EPMDevelopmentPlan_eg1.xml
3 Schema Design
3.1 EPMDevelopmentPlan
The EPMDevelopmentPlan schema is intended to communicate a training or development plan.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition ** |
|
/ |
- EPMDevelopmentPlanType - (1/1) |
A plan describing training or developmental requirements. |
|
/ EPMDevelopmentPlan/ |
- EntityIdType - S (0/1) |
An identifier for a development plan. |
|
/ EPMDevelopmentPlan/ |
- xsd:date - S (0/1) |
The date on which the objective plan was approved or submitted. |
|
/ EPMDevelopmentPlan/ |
- EPMPersonType - S (0/1) |
The person who approved or prepared the development plan. |
|
/ EPMDevelopmentPlan/ |
- EPMPersonType - S (1/1) |
The employee who is the subject of the development plan. |
3.1.1 EPMDevelopmentPlan / DevelopmentItem
|
/ EPMDevelopmentPlan/ |
- EPMDevelopmentPlanItemType - S (0/*) |
An instruction or requirement for training; An item within a development or training plan. |
|
/ DevelopmentItem/ |
- EntityIdType - S (0/1) |
An identifier for a developmental requirement or instruction. |
|
/ DevelopmentItem/ |
- xsd:string - S (0/1) |
A name for a development item. This might be a course name or other label to describe the training or developmental requirement. |
|
/ DevelopmentItem/ |
- xsd:string - S (0/1) |
A description of a training or development requirement. |
|
/ DevelopmentItem/ |
- LearningObjectReferenceType - S (0/*) |
A reference to a course or other developmental tool. |
|
/ DevelopmentItem/
LearningObjectReference/ |
- EntityIdType - S (0/1) |
An identifier for a course or other developmental tool. |
|
/ DevelopmentItem/
LearningObjectReference/ |
- xsd:string - S (0/1) |
A name of a course or other developmental tool. |
|
/ DevelopmentItem/
LearningObjectReference/ |
- LearningObjectUseEnumType - S (0/1) |
Describes requirements regarding the use of the referenced learning object. Enumerated values are: required; recommended; or required or equivalent. |
|
/ DevelopmentItem/ |
- EPMStatusType - S (0/1) |
Values describing status of a performance management process component (e.g., an Objective, a development item, etc.). Enumerated values are: "in progress", "complete", "canceled", "not known", and "not applicable". |
|
/ DevelopmentItem/
DevelopmentItemStatus/ |
- EPMStatusEnumType - C (1/1) |
Enumerated values are: in progress; complete; canceled; not known; and not applicable |
|
/ DevelopmentItem/
DevelopmentItemStatus/ |
- xsd:string - C (1/1) |
A list of non-standard values. |
|
/ DevelopmentItem/ |
- xsd:date - S (0/1) |
A date for a reported status (e.g., "in progress", "complete", "canceled", "not known", and "not applicable"). |
|
/ DevelopmentItem/ |
- xsd:date - S (0/1) |
A projected or requested date associated with a goal or requirement. |
|
/ DevelopmentItem/ |
- EPMMetricType - S (0/*) |
A metric by which a development item result will be measured -- for example, a minimum score on a test or assessment. |
|
/ DevelopmentItem/
DevelopmentItemMetric/ |
- EntityIdType - S (0/1) |
An identifier for the measure. |
|
/ DevelopmentItem/
DevelopmentItemMetric/ |
- xsd:string - S (0/1) |
The name of the measure. Part of a pair of components for describing a type of measure (MeasureName and MeasureValue). |
|
/ DevelopmentItem/
DevelopmentItemMetric/ |
- NumericAndStringScoreType - S (0/1) |
Part of a pair of components for describing a type of measure (MeasureName and MeasureValue).. |
|
/ DevelopmentItem/ |
- EPMCommentsType - S (0/1) |
The comment of a rater or participant in a performance management process. |
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