2.0 Business Process

This application supports the following business processes

XXXXXXXXXXXXX

CO Structure in Solvay:

PF1 Structure

WP1 Structure

Overview of the business process in Corporate Function Cost

Costs included in the report: 

The below costs are included in the Corporate Business 

• Actual costs only: Statistical costs are not taken into account
• IFRS rules only: Costs posted using local gaap accounts are excluded (Brazilian entities)
• Costs posted on CBS (Corporate Business Services) cost centers (directly or through orders or WBS). It corresponds to the cost centers included in the following groups of the cost centers hierarchy ZCBS: 

• • ZCBS-CORPO = Corporate
  • ZCBS-FUNCT = Function services
  • ZCBS-PROJ =Projects
  • ZCBS-ICO = Interco
• Costs are organized with the cost elements group ZRCS-FC
• Inter-company re-invoiced function service costs should be posted on cost centers of the group ZCBS-ICO

3.0 Application Feature Overview

For this scope we are using queries instead of workbooks. See below all the queries available:

1 - Solvay Group Fixed Costs

2 - Solvay Group detailed Fixed Costs

4.0 Functional Specification

4.1 General Data/Calculations 

For these reports, it is important to understand some general concepts which are transversal to all the reports which allows the users to work with the reports in the same way as the SAP system and BFC tool.

4.2 Process Detail 

4.2.1.  Report/Process Definition 

This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.

SAP BW High Level View

To see the data from the source systems see below how the information is organized in the BW perspective: 

5.0 Non-functional Descriptions 

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.

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.

5.3 Security

• All data will be encrypted in the dashboard
• Only authorised Users / Administrative Users will be able to access data.
• Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

5.4 Performance

Average performance

Depending on number of records loaded there is a variance between 30 seconds and 5 minutes.

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.   

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.  

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).

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).

5.9 Refresh of the Data

Loading frequency

Daily, twice a day.