| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Assessment per Appraisal Campaign Historical report This report contains data for performance and talent management, between 2018 and 2020. The datasource for this report is the You tool. You can find in this report, not only detailed information of Appraisal Campaign but also data to do the follow up of individual objectives and feedback culture. Note: For 2021 performance and talent reports are being developed in Success Factors report centre There is 1 report available for the following stakeholders:
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Describe the key User profiles that exist for the application. General role/Viewer role: HR and Managers (span of control) Approver role: | ||||||||
Key user profiles: HR Managers |
| Info | ||
|---|---|---|
| ||
Target Users: HR and manager ??managers |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 25.09.2023 | Emma Glasson | Initial draft |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
2.0 Business Process
Capture the business process that the application supports . This can be describe through a process diagram or a business capability model
You old tool decomission and transfer to success factor
3.0 Application Feature Overview
Information about the existent Workbooks and the respective BW queries.
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| Assessment per Appraisal Campaign | Having YOU tool as datasource, you can find in this report, not only detailed information of Appraisal Campaign but also data to do the follow up of individual objectives and feedback culture | Campaign Functional roles
| ???n.a | BW_QRY_CPHRAPCAMP_0001 |
4.0 Functional Specification
4.1 General Data/Calculations
This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.
Could be specific fields, closing activities, additional information to work and understand the reports.
Please find bellow general dimension, commun to all BW HR reports:
| Dimension | Definition |
Company Code | Company code to which an employee belongs on the time period selected in the report |
Country of the company | Country of company where the employee has his employment contract |
Calendar | Time dimensions available: Day, Month, Year, Year/Month |
Division (Entity) | Division (former entity) to which an employee belongs on the time period selected in the report |
Employee NR (NS) Employee PERN | Employee payroll number |
Employee status | Active, Active Leave, Inactive Leave Dormant, reported No Show Terminated, Inactive |
Employment status | Valid for historical data - the period before 1 November 2020. Equivalent to the current dimension Employee status |
Employee sub-group grouping (Gr) | Identification of employee by:
The employee sub-group grouping is a grouping definition of the employment type. |
Location Grp (Site) | Employee’s site |
Person ID | Unique identifier code for an employee. EC number. (person name available in the text option for this dimension) |
User Name | User account name (to access system/tool) |
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | Human Resources (HR) | ||||||
|---|---|---|---|---|---|---|---|
| Application | >insert name>BW Appraisal Query | ||||||
| Provider | SAPCPHRAPCAMP | ||||||
| Existing Documentation |
|
This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.
4.2.2. KPI's/Calculations/Indicators
Indicators available:
Indicatores/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
Nb of Assessments | Number of assessments that need to be performed. It's one assessment per employee. | count() |
Nb of performed assessments |
| Number of assessments completed. It's one assessment per employee. | count() |
| Nb of Score |
| 1 |
| Number of employee that were assess with a Score 1. | count() |
| Nb of Score |
| 2 |
| Number of |
| employee that were assess with a Score 2. | count() | |
| Nb of Score 3 | Number of employee that were assess with a Score 3. | count() |
| Nb of Score 4 | Number of employee that were assess with a Score 4. | count() |
| Nb of Score 5 | Number of employee that were assess with a Score 5. | count() |
| % Score 1 | % of employee that were assess with a Score 1. | avg in % |
| % Score 2 | % of employee that were assess with a Score 1. | avg in % |
| % Score 3 | % of employee that were assess with a Score 1. | avg in % |
| % Score 4 | % of employee that were assess with a Score 1. | avg in % |
| % Score 5 | % of employee that were assess with a Score 1. | avg in % |
Number of profiles | count() |
Indicatores/KPI's
Definition
Calculation/Extraction of data
Can be a field, a program, something that was created or the report
What are we looking for ? Why has this KPI been created/developed? What is the goal of monitoring this data ?
How is the calculation, or if it's a program what are the steps or how the data is extracted if it's by files
Nb of Assessments
Nb of performed assessments
Number of Employees (active in YOU) | Number of employee with an active profile on YOU tool. | count() |
Number of disclaimer with profile published only for HR | count() | |
Number of Objectives | Number of objectif set. An employee can set multiple objectives. | count() |
Number of Objectives completed | Number of objective completed by an employee. | count() |
Number of Objectives in progress | Number of objective in progress per employee. | count() |
Nb of feedback given | Number of feedback given/send by en employee to another. | count() |
Nb of feedback received | Number of feedback received per employee. | count() |
Nb of feedback requests | Number of feedback requested per employee. | count() |
Nb of Geographical Mobility | Number of employee that change region/ country as their resident adresse and that it was part of the mobility program. For exemple, change location France to Portugal. | count() |
Nb of Functional Mobility | count() |
5.0 Non-functional Descriptions
Please populate the relevant section and delete those that are not applicable.
5.1 Usability
Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system. In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required. Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.n.a
5.2 Regulatory Compliance
Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region. The software systems must be secure from unauthorized access. The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.GDPR compliant. Report that contain confidential data but no sensitive data.
5.3 Security
Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks. Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,
- All data will be encrypted in the dashboard
- Only authorised Users / Administrative Users will be able to access data.
- Maintenance data Data will be split between either SCO or ECO, and Users will only have authority to one Entity data.
5.4 Performance
Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload. In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now. Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers. n.a
5.5 Reliability
Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period. Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period. Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations. The Maintenance Dashboard will display data from the previous refresh of data.
n.a
5.6 Scalability
Scalability refers to the degree to which a solution can evolve to handle increased amounts of work. The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts. Historical report, no small enhancements will be performed and no new access except for new joiners in HR domain.
5.7 Compatibility
Interoperability is the degree to which the solution is compatible with other components. It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.
Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job. To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).Xtract and GCP compatible
5.8 Availability
Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).100% Week and Weekends
5.9 Refresh of the Data
N.A
Historical data loaded from YOU tool as datasource, you can find in this report historical information of Appraisal Campaign (2018-2020).
Note: For 2021 performance and talent reports are being developed in Success Factors report centre