HR-XML 3.0 Standards, 2009 September 23.
Menu: [ Home | Guidelines | BODs | Nouns | Global elements | WSDL | Packages | Code Lists | Master Index ]
Trace back: » ch09 | ch09s03 | ch10 | ch10s03 | ch11 »
Table of Contents
The OrganizationChart noun can be used in a variety of integration scenarios. A common use might be to provision a partner system (for example, a hosted talent management or performance management system) with information about organizational units, their "member positions" relationships among organizational units, and reporting and other relationships among positions. The schema also optionally allows the communication of brief information identifying position incumbents.
The OrganizationalChart specification can be used in combination with the HRMasterData noun and/or EPMParticipant noun. One approach is to provide information about the organization hierarchy and relationships among positions using OrganizationalChart and then to provide details about the incumbents (people in positions) using the IndicativeData or EPMParticipant messages. PositionID could be used as a key by the receiver to associate a position described in OrganizationChart with a person described in IndicativeData or EPMParticipant.
Note
Note while organizational charts can have complex hierarchical structures or express complex relationship mappings among nodes, the structure of the OrganizationalChart specification is flat and simple. An organizational unit is associated with its parent organization through an identifier (ParentOrganizationUnit/OrganizationUnitID). An organization unit can be associated with any other related organizational unit (so called "dotted lines") using RelatedOrganizationUnit/OrganizationID. MemberPositions are grouped within OrganizationalUnits. "ReportsToPosition," "ReportsToPerson," and "RelatedPosition" are components within MemberPosition to associate a position (and optionally its incumbent) with other positions and people.
Examples of events that could trigger the collaboration, include:
Outsourced Service Provider Provisioning. Many hosted and outsourced service providers need to be provided with information about the universe of employees or human resources that they will manage or for which they will provide related services. This involves providing the service provider with an initial build of organizational, position, and human resource data and often involves the communication of updates as business and life events change data provided in the initial build.
Employee Promotion or Position Transfer. The promotion or transfer of an employee to a new position obviously triggers a variety of associated changes (reporting relationships, pay and benefit changes, work location changes, etc.).
Hire. A "hire event" coincides with the point in time at which a person who has been a candidate becomes associated with an employer as an employee. Sometimes systems are pre-provisioned with information about an individual after he or she has accepted the offer, but before the employee enters-on-duty.
Organizational Events. A wide variety of organization events can trigger updates of human resource data or otherwise trigger interactions between HR service providers. Among those events are: layoff; location closure; merger; business reorganization; corporate relocation; acquisition; bankruptcy; and divestiture of operating units.