HS stands for Environment, Health and Safety. The Goal of EHS is to protect employees, the public, the environment and to comply with applicable laws and protect the Company's reputation. EHS departments, of some companies are responsible for environmental protection, occupational health and safety.
This application described below concerns one of EHS goals : Reporting for Substance Volume Tracking (SVT)
In many countries, regulations state that, above a certain quantity of chemicals and other hazardous substances, you must register with the authorities the maximum quantities of these substances that you plan to purchase, import, produce, sell, or export within a certain period. Substance volume tracking helps you to comply with the relevant regulations by recording the quantities of substances needing to be tracked that you purchase, import, produce, sell, or export. By comparing the recorded quantities with the limit values, the system can warn you in good time before a limit value is exceeded
The SAP module is installed and used on Solvay/RCS legacy systems. The standard SVT does not bit business rules.
The SVT reporting is now based on a BW solution.
Tool Leader + IT leader of the application:
Describe the key User profiles that exist for the application.
General role/Viewer role:
Approver role:
Roles and access
Role Code | Role Description | Explanation |
|---|---|---|
Role Code | Role Description | Explanation |
| ZR_RCS_EHS_A07 | EHS – Substance Volume Tracking Application - End User Role | Role menu / Based on authorization object ZBI_SVT Caution: ZBI_SVT gives access to all C_PLANT including BUTA (CC ZFR9). As the roles where not ready it has been decided not to load Buta data in REACH cube (SVT Analysis - EU (Rhodia) / CREHS06) => the company code ZFR9 is filtered in both DTP. See below important information |
| ZR_RCS_CA_M48 | EHS – Substance Volume Tracking | Role menu which gives acces to all workbooks. |
| ZBI_JP_EHS_P06 | EHS – Substance Volume Tracking Japan | Role perimeter / Based on authorization object ZJPEHSP06 / Country JP |
| ZBI_KR_EHS_P06 | EHS – Substance Volume Tracking Korean | Role perimeter / Based on authorization object ZKREHSP06 / Country KR |
| ZBI_CN_EHS_P06 | EHS – Substance Volume Tracking China | Role perimeter / Based on authorization object ZCNEHSP06 / Country CN |
| ZBI_TR_EHS_P06 | EHS – Substance Volume Tracking Turkish | Role perimeter / Based on authorization object ZTREHSP06 / Country TR |
| ZBI_TOUT_EHS_P06 | EHS – Substance Volume Tracking ALL PERIMETER | Role perimeter / Based on authorization object ZALLEHSP06 / all countries |
| ZBI_EU_EHS_P06 | EHS – Substance Volume Tracking Europe | Role perimeter / Based on authorization object ZEUEHSP06 / Country of the REACH area FR, BE, DE... |
| ZBI_US_EHS_P06 | EHS – Substance Volume Tracking USA | Role perimeter / Based on authorization object ZUSEHSP06 / Gives access to country US Associated country and islands PR, GU, VI, AS , MP should also be part of the perimeter role. Currently it is not the case. |
| ZBI_CA_EHS_P06 | EHS – Substance Volume Tracking Canada | Role perimeter / Based on authorization object ZCAEHSP06 / Country CA |
Useful to know :
1- Menu Roles ZR_RCS_CA_M40 “EHS – Substance Volume Tracking Asia” and ZR_RCS_CA_M36 “EHS – Substance Volume Tracking North America” are now obsolete .
There are replaced by ZR_RCS_CA_M48.
2- Perimeter roles ZBI_RCS_EHS_P06 to ZBI_RCS_EHS_P12 are obsolete because Authorization Team has decided to use naming ZBI_xx_EHS_P06 (xx = country)
3- Perimeter roles ZR_RCS_EHS_P06 to P09 and P11, P13 to P15 are obsolete because old naming.
Useful to know concerning BUTA Chimie ( Company Code ZFR9) :
A filter on C_PLANT from authorization has been added in all SVT queries :
variable V_AUT_C_PLANT_0001 for EU report as the Plant is a selection criteria
variable V_C_PLANT_0001 for all other as the Plant is not a selection citeria
The C_PLANT will have to be removed in object ZBI_SVT (A pplication Role ZR_RCS_EHS_A07)
Following perimeter role will have to be managed for all EHS SVT users :
For all plants, except BUTA, use perimeter role ZR_TOUT_CA_P02 / object ZTOUTCAP02
- For BUTA plants, use perimeter role ZR_7866_CA_P02 / object Z7866CAP02
The BUTA data will have to be loaded in cube REACH ( SVT Analysis - EU (Rhodia) / CREHS06).
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 03.11.2023 | Abidemi Rajiu | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
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
Documentation:
The SVT bases its calculation on:
- Materials stock movements in the different SAP modules
- EHS specifications to which are attached materials on one side and substances to track on the other
- Scenarios: importation, production, sale, exportation… The scenarios are standard programs adaptable from SVT to identify the materials and quantities to track.
The SVT allows to :
- Automatically calculate pure substances volumes per legal entity, site, scenario, specification PRCO…
- Archive the Tracking results in BW to ease the reporting to the authorities.
- Create warning threshold when the tonnage bands are approached or reached.
- Create warning event when we export a substance for the first time in a country (example).
Contents
Europe REACH tracking Objectives Some products or substances fall under specific measures:
Thus calculation rules, according to the specific measures, were elaborated in order to obtain the relevant substances for the tracking in the “Standard REACH list”. SAP EHS
System where the reporting is done
> Refer to the training item: SVT Europe - REACh EU - Audit REACh Traceability IS Tools (ARTIST)This report complements the SVT report because it provides the full details of the REACH status entered in the PURE_SUB or raw material PROD_COM in SAP EHS. It provides a complete plant or GBU view of the REACH status of substances, ready to use for internal or external audit. Note that it is only available for WP1 plants at the moment (Rhodia legacy). >> Refer to the following presentations: |
Turkey |
North AmericaUSA1) TSCA 12b or pre export notification
Refer to the dedicated training item for more explanations and screenshots. 2) TSCA Chemical Data Reporting or CDRThe regulation:
What we implemented, concretely speaking: Because of the complexity of the reporting and the variability of the criteria from one reporting cycle to the other, the scope of tracking is deliberately very wide and local regulatory expertise is then required to filter out the data. CANADA1) Non DSL TrackingThe regulation:
What we implemented, concretely speaking:
2) Extended TrackingA full tracking report has also been developed in order to answer other types of reporting. In this BW report, there is no exclusion of substances that are on the DSL. All substances are tracked but water and impurities. In this report, there is no comparison with an authorized threshold. Refer to the dedicated training item for more explanations and screenshots. |
Korea
Annual Reporting of Chemicals
Objectives: The objective of this tracking is to notify the yearly amount of all Chemical substances.
There are no exemptions currently automatically managed, all substances are tracked for the annual reporting. Thus, the Standard composition (or Legal Composition if available in KR) have to be tracked, with all component types.
Users also need to report the usage of each substance.
All kind of flows have to be considered: importation, domestic purchase, production, exportation, sales. They shall be grouped into 2 types of flows:
- In-Flows: Manufactured substance + Imported substance + Domestic purchase
- Out-Flows: Domestic + export sales
The period relevant for tracking is one calendar year, from January 1st until December 31st. But the BW report can be launched for any period.
SAP EHS
- Specific composition: K-REACH composition as priority 1, standard composition as priority 2
- Rule: ZCP_KREACH
- Other PRCO classes to fulfill: Korea Usage for Annual Reporting
System where the tracking is done
- Business Warehouse (BW) - WBP
- Query : EHS - Substance Volume Tracking Asia > Korea > KR Annual Reporting (Core Workbook)
> Refer to the training item: SVT Korea 1 - Annual reporting of chemicals
Registration
Objectives
The objective of this tracking is to calculate the yearly amount of Substances that shall be registered according to K-Reach / ARECS (Act on the Registration and Evaluation of Chemical Substances).
The substances to track for the registration are:
- Designated existing substances : the MoE shall provided lists of so-called “Designated existing substances” that must be registered at first priority.These substances must be registered if the cumulative quantity of all flow is > 1 ton/year. However, the report will display all volume, even if below 1 ton/year.
- New chemical substances after 2015 - no threshold limits.
Exemptions : some substances are not subjected to Registration
- Substances covered by another regulation : Cosmetics, Narcotics, Pesticides, Feeds, etc.
- R&D substances
- Chemicals designated by Presidential Decree as exempted (list not yet published)
- Other exemptions like water, impurities, polymers… so far not know and no further information on the conditions.
For registration, only the following flows are considered :
- Manufacturing
- Importation
The period relevant for tracking is one calendar year, from January 1st until December 31st. But the BW report can be launched for any period.
SAP EHS
- Specific c omposition: K-REACH composition as priority 1, standard composition as priority 2
- Rule: ZCP_KREACH
- Other PRCO classes to fulfill: No
System where the tracking is done
- Business Warehouse (BW) - WBP
- Query : EHS - Substance Volume Tracking Asia > Korea > KR Registration (Core Workbook)
> Refer to the training item: SVT Korea 2 - Registration
Japan
Annual Reporting of Chemicals
Objectives
The objective of this tracking is to notify the yearly amount of all Chemical substances listed on the Chemical Substance Control Law (CSCL). Those substances can be distinguished between 3 types:
- General Chemical Substances (GCS) : not classified CSCL substance, that is to say any substance listed on the CSCL - Inventory of Existing and New Chemical Substances (ENCS) and that is not a Priority Assessment Chemical, nor a Monitoring Chemical Substance, nor a CSCL SVE/LPN.
- Priority Assessment Chemical substance (PACS)
- Monitoring Chemical substances (MCS)
The reporting has to be done per MITI number and not per CAS number.
Exclusion: Substances which have conditions below will be excluded from composition:
- PACS or MCS present as impurities <1% in a product.
- GCS present at <10% in a mixture (both intentional component and impurity)
- Substances regulated by other special law
For shipped product, users need to report the usage of each substance.
The volumes of Registered New Chemicals must be calculated for the following flows:
- Manufacturing
- Importation
- Shipment (Domestic and Export sales)
The period relevant for tracking is one calendar year, from April 1st of year Y-1 until March 31st of year Y. But the BW report can be launched for any period.
SAP EHS
- Specific composition: JP Compo for Annual Reporting
- Rule: ZCP_JP_SVT Japanese SVT Compo calculation
- Other PRCO classes to fulfill: Japan Usage for Annual Reporting
System where the tracking is done
- Business Warehouse (BW) - WBP
- Query : EHS - Substance Volume Tracking Asia > Japan > JP Annual Reporting (Core Workbook)
> Refer to the training item: SVT Japan 1 - Annual reporting of Chemicals
Annual reporting of Small Volume Exempted substance or Low Production Notified substances
Objectives
The objective of this tracking is to notify the yearly amount of all Small Volume Exemption (SVE) or Low Production Notification (LPN) of New Chemical substance.
Two regulations are involved:
- the Chemical Substance Control Law (CSCL)
- the Industrial Safety and Health Law (ISHL)
Among these lists, we can distinguish 3 types of new chemical substances:
- Small Volume exemption (SVE)
ISHL SVE : New chemical substances under ISHL, applied for SVE
CSCL SVE: New chemical substances under CSCL, applied for SVE
- Low Production Notification (LPN)
CSCL LPN: : New chemical substances under CSCL, applied for LPN
Each new chemical substance has an authorized volume allocated by authorities which cannot be exceeded.
Exclusion: Substances which have conditions below do not have to be reported.:
- ISHL SVE substance present as impurity <10% in a product.
- CSCL SVE/LPN substance present as impurity <1% in a productSubstances regulated by other special law
The volumes of SVE/LPN New Chemicals must be calculated for the following flows:
- Manufacturing
- Importation
- Shipment (Domestic and Export sales)
The period relevant for tracking is one calendar year, from April 1st of year Y -1 until March 31st of year Y. But the BW report can be launched for any period.
JP authorities allocate volumes to applicant of CSCL SVE or LPN. So applicants have to submit their reports before the fiscal year (April – March) starts.
SAP EHS
- Specific composition: JP Compo for Annual Reporting
- Rule: ZCP_JP_SVT Japanese SVT Compo calculation
- Other PRCO classes to fulfill: No
System where the tracking is done
- Business Warehouse (BW) - WBP
- Query : EHS - Substance Volume Tracking Asia > Japan > JP SVE-LPN Annual Reporting (Core Workbook)
> Refer to the training item: SVT Japan 2 - Annual reporting of SVE and LPN of chemicals
China
Tracking of Registered New Chemicals
Objective
The objective of this tracking is to notify the yearly amount of Registered New Chemicals, that is to say substances that are NOT listed on the Chinese Existing Chemical Inventory but that have been notified to Chinese authorities. These chemicals have a notification certificate and can be notified according to a simplified or a full notification process, with an allocated volume (different for each substance). If this authorized quantity is exceeded, the company needs to update the notification dossier.The Registered New Chemicals can be contained in mixtures and/or substances commercial products (PROD_COM).
For substance type PROD_COM, the notification of the volume can be made on the full PROD_COM* (main substance + impurities) or only on the main substance. It is thus not possible to make the calculation on the standard Composition.
The volumes of Registered New Chemicals must be calculated for the following flows:
- Manufacturing
- Importation
- Sales (Domestic sales and Exportation)
- Environmental release : cannot be tracked as information are not maintained in SAP – this flow will NOT be part of the BW report.
The period relevant for tracking is one calendar year, from January 1st of year Y until December 31st of year Y. But the BW report can be launched for any period.
The deadline for reporting is February 1st.
SAP EHS
- Specific composition: Z_EHS_CN_COMPO - CN Compo for Registered New Chemicals to be maintained if there are exemptions. Otherwise, the report will use the standard composition.
- Rule: No, the composition is manually filled
- Other PRCO classes to fulfill: No
System where the tracking is done
- Business Warehouse (BW) - WBP
- Query : EHS - Substance Volume Tracking Asia > China > CN Registered New Chemicals (Core Workbook)
> Refer to the training item : SVT China 1 - Registered new chemicals
Retro calculation
Composition changes:
- If the WP1 composition is modified during the year X and if you generate the report after this date, all the quantities will be calculated with this new composition for all the current calendar year
- Besides, compositions are frozen at the end of each calendar year in BW (December 31th) If you generate the report on the year X-1, the quantities will be calculated with the composition of the December 31th of the year X-1 and not with the current composition.
Log
In each report, there is a tab for the "log", this aims at highlighting potential data maintenance issues. The log tab contains data that could not appear in the report itself because of missing information:
- no composition maintained for the PROD_COM
- no regulation found for the PURE_SUB
- no usage found for the PROD_COM
- no link between material and PROD_COM
3.0 Application Feature Overview
N/A
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.
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.
Main queries
For EHS SVT, queries have been developped, but for each query, an analysis workbook has been settled => only one access mode.
All queries/workbooks are published in an unique role menu “ EHS – Substance Volume Tracking” ( ZR_RCS_CA_M48)
New Query: SVT Report-Notification of nanomaterials Europe (core query) => BW_QRY_MPR_EHS07_EU_0002
NB : Following queries are not yet available as workbook (not part of convergence project), a freshdesk has to be created by the Business Team.
- EHS - Imported Material without Composition (Core query) => BW_QRY_MPR_EHS02_0005
- EHS - Imports List by Material (Core query) => BW_QRY_MPR_EHS02_0004
- EHS - Imports list from GTS (Core query) => BW_QRY_MPR_EHS02_0002
- EHS - Imports List by Substance (Core query) => BW_QRY_MPR_EHS02_0006
All reports have following common filtrers
Country of Origin (C_CNTRY_O) = autorisation
Tracking Flag (C_TRCKFLG) = 'Y'
Component Type Exclusion (C_IMPFLG) = 'N'
Material Exclusion Flag (C_EXCLUSI) = 'N'
Chemical reaction <> 0 'NO'
All reports have following condition
- Quantites PRO >= 0
Here are the different filters for each report
Reg List (C_REG) | Cube (0INFOPROV) | Scenario (C_SCEN) | Others | ||
BW_WBK_EHS_SVT_GENERIC Generic SVT - Substance Level (Core Workbook) | BW_QRY_CPEHSV01_0002 EHS - SVT Generic reporting Query (Core) | All | ABEHSV02, ABEHSV04 (Composite Provider CPEHSV01: ) | All | |
BW_WBK_EHS_SVT_GENERIC Generic SVT - Product Level (Core Workbook) | BW_QRY_CPEHSV01_0003 EHS - SVT Generic reporting Synthesis Query (Core) | All | ABEHSV02, ABEHSV04 (Composite Provider CPEHSV01: ) | All | |
BW_WBK_EHS_SVT_CN_001 CN Registered New Chemicals (Core Workbook) | BW_QRY_MPR_EHS07_CN_0001 CN Registered new chemicals (Core Query) | ZCN_NEW_CH | CUB_EHS07, CREHS02 | all except PUR | Regulation Code ( C_REGCODE) / Type of substance = CN001 + '#' |
BW_WBK_EHS_SVT_CN_002 CN KECH Chemicals (Core Workbook) | BW_QRY_MPR_EHS07_CN_0002 CN Key environmental controlled haz. chemicals (Core Query) | ZCN_KECHC | CUB_EHS07, CREHS02 | PRO | Regulation Code ( C_REGCODE) / Type of subst. = CN002 + '#' |
BW_WBK_EHS_SVT_JP_001 JP Annual Reporting (Core Workbook) | BW_QRY_MPR_EHS07_JP_0001 JP Annual reporting of chemicals (Core Query) | ZJP_AN_REP | CREHS01, CUB_EHS06 | All excpect PUR | Regulation Code ( C_REGCODE) / Type of subst. = JP001, JP002, JP003, # |
BW_WBK_EHS_SVT_JP_002 JP SVE-LPN Annual Reporting (Core Workbook) | BW_QRY_MPR_EHS07_JP_0002 JP Annual reporting of SVE/LPN of new chemicals (Core Query) | ZJP_CSCL, ZJP_ISHL | CREHS01, CUB_EHS06 | EXP, IMP, PRO, ICI | Regulation Code ( C_REGCODE) / Type of subst. = JP004, JP005, JP006, # |
BW_WBK_EHS_SVT_KR_001 KR Annual Reporting (Core Workbook) | BW_QRY_MPR_EHS07_KR_0001 KR Annual reporting of chemicals (Core Query) | ZKR_AN_REP | CREHS03, CUB_EHS08 | all | Regulation Code ( C_REGCODE) / Type of subst. = KR001, KR002, #' |
BW_WBK_EHS_SVT_KR_002 KR Registration (Core Workbook) | BW_QRY_MPR_EHS07_KR_0002 KR Registration (Core Query) | ZKR_DESIGN, ZKR_NEW | CREHS03, CUB_EHS08 | PRO/ICI/IMP On devrait ajouter le filtre dans qry | Regulation Code ( C_REGCODE) / Type of subst. = KR003, KR004, # |
BW_WBK_EHS_SVT_TR_001 TR Substances Notification (Core Workbook) | BW_QRY_MPR_EHS07_TR_0001 TR Substances Notification (Core Query) | ZTR_CICR | CUB_EHS07, CREHS02 | ICI, SO | Regulation Code ( C_REGCODE) / Type of substance = TR001, # |
BW_WBK_EHS_SVT_EU_001 EU REACH (Core Workbook) | BW_QRY_MPR_EHS07_EU_0001 EU REACH (Core Query) | REACH | CREHS04, CREHS06 | ICI, PRO, IMP | |
BW_WBK_EHS_SVT_US_001 US TSCA CDR (Core Workbook) | BW_QRY_MPR_EHS07_US_0001 US TSCA CDR (Core Query) | TSCA | CREHS05, CREHS07 | IMP, ICI, PRO, EXP | |
BW_WBK_EHS_SVT_US_002 US TSCA 12b (Core Workbook) | BW_QRY_MPR_EHS07_US_0002 US TSCA 12b (Core Query) | ZUS_T12B | CREHS05, CREHS07 | EXP | |
BW_WBK_EHS_SVT_CA_001 Canada Non DSL Tracking (Core Workbook) | BW_QRY_MPR_EHS07_CA_0001 Canada Non DSL Tracking (Core Query) | ZCA_DSL | CREHS05, CREHS07 | IMP, PRO, ICI | Substance <> EXCLUDED |
BW_WBK_EHS_SVT_CA_002 Extended tracking for Canada (Core Workbook) | BW_QRY_MPR_EHS07_CA_0002 Extended tracking for Canada (Core Query) | ZCA_SVT | CREHS05, CREHS07 | IMP, ICI, PRO | |
BW_WBK_EHS_SVT_EU_003 SVT Report-Notification of nanomaterials Europe (core Work book) | BW_QRY_MPR_EHS07_EU_0002 SVT Report-Notification of nanomaterials Europe (core Query) | ZEU_NANO | CREHS04 CREHS06 | IMP, ICI, PRO | |
BW_WBK_EHS_SVT_AU_001 AU Annual Reporting (Core Workbook) | BW_QRY_MPR_EHS07_AU_0001 AU Annual reporting of chemicals - SO | ZAU_AICS | CREHS08 | SO | |
BW_QRY_MPR_EHS07_AU_0002 AU Annual reporting of chemicals - IMP+ICI | ZAU_AICS | CREHS08 | ICI, IMP | ||
BW_QRY_MPR_EHS07_AU_0003 AU Annual reporting of chemicals - PRO | ZAU_AICS | CREHS08 | PRO | ||
BW_QRY_MPR_EHS07_AU_0004 AU Annual reporting of chemicals - LOG | ZAU_AICS | CREHS08 | ALL | Log_ID = Non initial | |
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.
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
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 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.
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
Frequency, data, and time of the data refresh in the data product.

