Data Source Requirements

The main decision points when preparing your data for import into org.manager are:

1. What data will be charted for people / positions / departments?
   Employee, Leave balances, Salaries, Position, Occupancy, Cost Centre

2. What hierarchical structures will be built?
   Position, Org Unit, Both

3. What attributes will be used to find links between entities?
   Position reporting relationships, Nominal occupants of positions, Acting occupants of positions,
   Org unit assignation of positions

4. What attribute will be used as a unique identifier?

5. What attribute can be used to map people to photo files?

 

 

Hierarchical Structures

The information available from your source of truth and the way this information is stored will drive what data is available to org.manager. Each hierarchy will have a unique ID and a set of additional attributes for visualisation in org.manager. Typically, the data sources used to build organisational charts fall in one of the two scenarios described below:

Position Structures

• Hierarchy is built using Position IDs

• KPIs and other calculations are done based on Position hierarchy

• Position and Person are the main HR data fields included in the structure

 

 

Organisational Unit Structures

• Hierarchy is built using Org Unit IDs

• KPIs and other calculations are done based on Org Unit hierarchy

• Org Unit, Position and Person are the main HR data fields included in the structure

 

 

Data Source Format

Most data source types (except for SAP) require the data to meet the following formatting rules:

• Data to be stored in a tabular format (1 record per row, 1 attribute per column)

• First row can contain heading names

• Multiple files or database tables are allowed (1 per HR entity works well)

• Attributes storing dates must use a consistent format

• Information to determine hierarchical structures must be included

• Information to determine relationships amongst HR entities must be included

Employee/User Identifiers

Employee/User ID is a required field for integration with your identity provider. In general, this is used for the following purposes:

• Authentication for access to the charts

• To grant different levels of access for different users (e.g. general information/non sensitive information for employees, restricted access for HR with further position/employee details).

Mandatory Fields

There are a number of mandatory fields that must be included in your data sources. These are:

The above information is used to build the reporting lines and make the different links between positions, people, org units and other entities. In addition to these mandatory requirements, you can include an unlimited number of data fields.

For example:

• Personal details

• Contact details

• Remuneration details

• Leave balances

• Location details

• Compliance information (i.e. WWCC, Licence Info etc)

Photos

Each person's record can be linked to a picture file, allowing employee photos to be part of the data available for visualisation in the charts.

In org.manager cloud hosted environments, the picture files need to be transferred to the application server hosting org.manager.

To be able to include employee photos, the following requirements need to be met:

• All photos are accessible from the org.manager application server via the same location (directory path or URL). For Cloud Hosted picture files must be transferred to the hosting application server.

• Each photo file is named after a unique identifier available in the data source (typically employee ID)

• Each photo file is in a supported format (jpg, png, bmp)

• Each photo file must be in the same format (e.g. all jpg)

• All the individual photos zipped into a folder before transfer